[SUPPORT] blakeblackshear - Frigate

[NewDisplayName]

Sorry, then i didnt see it. (probbaly because you ahve to scroll, cant you add that to the "overview"?)

 

Heres my config like i said, if i were you, couldnt you provide a "standard" config with the installer? And or post these config on your first forum thread? So people can learn from it themselfs?

 

Installation:

1.) Choose the template with Nvidia

2.) add --runtime=nvidia to extra parameter

3.) move this config.yml to your config directory

4.) change pw user port and url to your camera

5.) run this command (inside the trt directory) in shell: 

Quote

 

mkdir trt-models
wget https://github.com/blakeblackshear/frigate/raw/master/docker/tensorrt_models.sh
chmod +x tensorrt_models.sh
docker run --gpus=all --rm -it -v `pwd`/trt-models:/tensorrt_models -v `pwd`/tensorrt_models.sh:/tensorrt_models.sh nvcr.io/nvidia/tensorrt:22.07-py3 /tensorrt_models.sh
 

 

If u get errors about 16 bit something then run this command instead (or just run it again, if the above fails)

 

Quote

mkdir trt-models
wget https://github.com/blakeblackshear/frigate/raw/master/docker/tensorrt_models.sh
chmod +x tensorrt_models.sh
docker run -e USE_FP16=False --gpus=all --rm -it -v `pwd`/trt-models:/tensorrt_models -v `pwd`/tensorrt_models.sh:/tensorrt_models.sh nvcr.io/nvidia/tensorrt:22.07-py3 /tensorrt_models.sh

config.yml

Edited August 15 by nuhll

[NeoDude]

What's the general consensus or best practice with whether or not to have recordings going via SSD Cache Pool or Straight to array? Is SSD wear with constant writes still a consideration with modern drives?

[mikey6283]

 How do I increase the tmpfs file from 94M to 2GB unRaid Frigate as do not have enough space. On the github frigate issue page,  I have been informed to Either need more allocated or don't access so many clips?

 

  Please could anyone advise how to achieve this in the container.

 

Thanks

[NewDisplayName]

look for the only tmpfs command in this docker and change it accordingly

[yayitazale]

12 hours ago, mikey6283 said:

 How do I increase the tmpfs file from 94M to 2GB unRaid Frigate as do not have enough space. On the github frigate issue page,  I have been informed to Either need more allocated or don't access so many clips?

 

  Please could anyone advise how to achieve this in the container.

 

Thanks

You can change it the extra commands under advanced view

[yayitazale]

On 8/18/2023 at 11:26 AM, NeoDude said:

What's the general consensus or best practice with whether or not to have recordings going via SSD Cache Pool or Straight to array? Is SSD wear with constant writes still a consideration with modern drives?

Use cache unless you have a specific NVR HDD.

[NewDisplayName]

Someone know if night detection is working somehow? Ive googled abit around and it just seems to be old posts...? My cam has night vision...

[yayitazale]

Just now, nuhll said:

Someone know if night detection is working somehow? Ive googled abit around and it just seems to be old posts...? My cam has night vision...

Theorically yes but in my experience, it doesn't work as good as in normal mode.

[mikey6283]

7 minutes ago, yayitazale said:

You can change it the extra commands under advanced view

 Thank you, I found it and changed tmpfs size to 200000000 is that correct or should it be 2GB

[NewDisplayName]

Just now, mikey6283 said:

 Thank you, I found it and changed tmpfs size to 200000000 is that correct or should it be 2GB

https://www.google.com/search?q=tmpfs+2gb

[The Transplant]

Noobie - got my .11 version up and running in the docker and have been using it for some time now.  Trying to figure out how to move to .12?  At the beginning of the thread it says to uninstall the current app and reinstall it.  In other words, reinstall the same app again and it will then pull the .12 version?

 

Also, I backup my dockers regularly using the Backup/Restore AppData.  Is this sufficient in case everything goes wrong?  Thanks.

[yayitazale]

41 minutes ago, The Transplant said:

Noobie - got my .11 version up and running in the docker and have been using it for some time now.  Trying to figure out how to move to .12?  At the beginning of the thread it says to uninstall the current app and reinstall it.  In other words, reinstall the same app again and it will then pull the .12 version?

 

Also, I backup my dockers regularly using the Backup/Restore AppData.  Is this sufficient in case everything goes wrong?  Thanks.

Yes but read the docs carefully since there are some breaking changes.

 

For a more safe deployment and to be able to rollback to v11 as many times as you need:

• Create a new folder on appdata called frigate-new or something like that.
• Create a new media folder again with a different name.
• Just stop v11 frigate, don't delete.
• Create a new config file with the new requirements in the new folder
• Launch the new frigate 12 with a different name, like "frigate12" and change the path of the config file and media path to the new ones. In this way you can have both old and new frigate (only one running but both containers).
• You can make trials to make v12 to work, but if you don't make it in just one try, you can just stop the frigate 12 and start the 11 as many times as you need.
• When you are ready to move to v12 definitely, stop and remove the v11 app, delete de v11 config file, move the v12 config to original frigate config folder, rename the v12 app to just frigate, and launch it pointing to the original appdata and media paths.

Edited August 26 by yayitazale

[MasterOfPuppets111]

is the docker update to 0.13 already planned?

 

Best regards

Pierre

[The Transplant]

20 hours ago, yayitazale said:

Yes but read the docs carefully since there are some breaking changes.

 

For a more safe deployment and to be able to rollback to v11 as many times as you need:

• Create a new folder on appdata called frigate-new or something like that.
• Create a new media folder again with a different name.
• Just stop v11 frigate, don't delete.
• Create a new config file with the new requirements in the new folder
• Launch the new frigate 12 with a different name, like "frigate12" and change the path of the config file and media path to the new ones. In this way you can have both old and new frigate (only one running but both containers).
• You can make trials to make v12 to work, but if you don't make it in just one try, you can just stop the frigate 12 and start the 11 as many times as you need.
• When you are ready to move to v12 definitely, stop and remove the v11 app, delete de v11 config file, move the v12 config to original frigate config folder, rename the v12 app to just frigate, and launch it pointing to the original appdata and media paths.

Thanks - very helpful.  I got everything working and even discovered that I had a snapshot command twice in the same camera.  Although it appears to be working I am getting the following error repeatedly:

 

frigate.comms.dispatcher       ERROR   : Recordings must be enabled in the config to be turned on via MQTT.

 

The message seems obvious but I have recordings turned on.  I've attached the config in case it is helpful.  Thanks.

 

frigate config

[BlackAndChrome]

Does anyone use Nginx Proxy Manager with iPhone devices for Frigate?

I have everything working well through NPM for Windows and Android devices but with IOS (multiple devices, Safari OR Chrome) I get repeated credential prompt anytime that I load a page with a live camera feed, although entering the credentials will show the feed as expected. Opening the config file shows the code blocks from Frigate Docs. Pasted below with some of the gratuitous line breaks removed.

 

# ------------------------------------------------------------
# frigate.[domain].com
# ------------------------------------------------------------

server {
  set $forward_scheme http;
  set $server         "192.168.1.100";
  set $port           5000;

  listen 80;
listen [::]:80;

listen 443 ssl http2;
listen [::]:443 ssl http2;


  server_name frigate.[domain].com;


  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-1/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-1/privkey.pem;

proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


  access_log /data/logs/proxy-host-4_access.log proxy;
  error_log /data/logs/proxy-host-4_error.log warn;

  location / {
 
    # Authorization
    auth_basic            "Authorization required";
    auth_basic_user_file  /data/access/1;
    
    proxy_set_header Authorization "";

    # Access Rules: 0 total
    
    deny all;

    # Access checks must...
    
    satisfy any;
    
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    
    # Proxy!
    include conf.d/include/proxy.conf;
  }


  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

 

[yayitazale]

On 8/26/2023 at 10:40 PM, MasterOfPuppets111 said:

is the docker update to 0.13 already planned?

 

Best regards

Pierre

You find out by yourself:

 

https://github.com/blakeblackshear/frigate/releases

[yayitazale]

18 hours ago, The Transplant said:

Thanks - very helpful.  I got everything working and even discovered that I had a snapshot command twice in the same camera.  Although it appears to be working I am getting the following error repeatedly:

 

frigate.comms.dispatcher       ERROR   : Recordings must be enabled in the config to be turned on via MQTT.

 

The message seems obvious but I have recordings turned on.  I've attached the config in case it is helpful.  Thanks.

 

frigate config 4.68 kB · 1 download

You don't have recordings turned on. You should put a specific entry as a global config (in the same way/level as detectors) inside the config as you can see here:

 

https://docs.frigate.video/configuration/record

 

I also suggest you to try to use FFMPEG hardware acceleration as you will see a noticeable decrease of the CPU usage.

[yayitazale]

5 hours ago, BlackAndChrome said:

Does anyone use Nginx Proxy Manager with iPhone devices for Frigate?

I have everything working well through NPM for Windows and Android devices but with IOS (multiple devices, Safari OR Chrome) I get repeated credential prompt anytime that I load a page with a live camera feed, although entering the credentials will show the feed as expected. Opening the config file shows the code blocks from Frigate Docs. Pasted below with some of the gratuitous line breaks removed.

 

# ------------------------------------------------------------
# frigate.[domain].com
# ------------------------------------------------------------

server {
  set $forward_scheme http;
  set $server         "192.168.1.100";
  set $port           5000;

  listen 80;
listen [::]:80;

listen 443 ssl http2;
listen [::]:443 ssl http2;


  server_name frigate.[domain].com;


  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-1/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-1/privkey.pem;

proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


  access_log /data/logs/proxy-host-4_access.log proxy;
  error_log /data/logs/proxy-host-4_error.log warn;

  location / {
 
    # Authorization
    auth_basic            "Authorization required";
    auth_basic_user_file  /data/access/1;
    
    proxy_set_header Authorization "";

    # Access Rules: 0 total
    
    deny all;

    # Access checks must...
    
    satisfy any;
    
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    
    # Proxy!
    include conf.d/include/proxy.conf;
  }


  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

 

Sorry I don't have frigate exposed to the outside, I use home assistant webrtc integration.

[The Transplant]

On 8/28/2023 at 2:31 AM, yayitazale said:

You don't have recordings turned on. You should put a specific entry as a global config (in the same way/level as detectors) inside the config as you can see here:

 

https://docs.frigate.video/configuration/record

 

I also suggest you to try to use FFMPEG hardware acceleration as you will see a noticeable decrease of the CPU usage.

 

I will look into FFMPEG - I haven't found any how-tos so will see if I can figure that out.

 

Before doing that I wanted to get it running cleanly.  Right now I can only see clips in UI when in progress.  Some show the clip link as greyed out or others report "The media could not be loaded, either because the server or network failed or because the format is not supported."

 

Probably related, I noticed that the media folder frigate12 I configured has nothing in it.  But the frigate folder set up for the original docker is still showing new files.  The old Frigate docker is not started.  The media path is setup - but I think something is getting crossed here?

 

 

I captured what I think are the log entries when I try to play a clip that returns the error.

 

2023-09-04 09:43:51.189378806  [2023-09-04 09:43:51] frigate.http                   ERROR   : No recordings found for the requested time range
2023-09-04 09:43:51.709133133  2023/09/04 09:43:51 [error] 172#172: *275 ngx_child_request_wev_handler: upstream returned a bad status 404 while sending to client, client: 192.168.2.201, server: , request: "GET /vod/event/1693824835.69601-0uhrev/master.m3u8 HTTP/1.1", host: "192.168.2.110:5000", referrer: "http://192.168.2.110:5000/events"
2023-09-04 09:43:51.709171127  192.168.2.201 - - [04/Sep/2023:09:43:51 -0400] "GET /vod/event/1693824835.69601-0uhrev/master.m3u8 HTTP/1.1" 502 559 "http://192.168.2.110:5000/events" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.5735.106 Safari/537.36 WebCatalogPhoton/34.2.0" "-"
2023-09-04 09:43:51.736153730  [2023-09-04 09:43:51] frigate.http                   ERROR   : Event does not have recordings: 1693824835.69601-0uhrev
2023-09-04 09:43:51.736772756  2023/09/04 09:43:51 [error] 172#172: *275 ngx_child_request_wev_handler: upstream returned a bad status 404 while sending to client, client: 192.168.2.201, server: , request: "GET /vod/event/1693824835.69601-0uhrev/master.m3u8 HTTP/1.1", host: "192.168.2.110:5000", referrer: "http://192.168.2.110:5000/events"
2023-09-04 09:43:51.736777945  192.168.2.201 - - [04/Sep/2023:09:43:51 -0400] "GET /vod/event/1693824835.69601-0uhrev/master.m3u8 HTTP/1.1" 502 559 "http://192.168.2.110:5000/events" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.5735.106 Safari/537.36 WebCatalogPhoton/34.2.0" "-"
2023-09-04 09:43:58.377046426  192.168.2.113 - - [04/Sep/2023:09:43:58 -0400] "GET /api/stats HTTP/1.1" 200 4241 "-" "HomeAssistant/2023.8.3 aiohttp/3.8.5 Python/3.11" "-"

 

And my config:

 

mqtt:
  host: 192.168.2.110
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: frigate
  password: depeche6667
  stats_interval: 60
detectors:
  coral:
    type: edgetpu
    device: usb
record:
  enabled: true
  retain:
    days: 30
    mode: all
birdseye:
  enabled: True
  mode: continuous
cameras:
  garage:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - record
            - detect
    objects:
      track:
        - person
        - car
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 30
        mode: all
      events:
        pre_capture: 2
        post_capture: 2
    motion:
      mask:
        - 0,720,441,720,643,308,573,129,1168,131,1168,0,513,0,0,0
  back_garden:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - record
            - detect
    objects:
      track:
        - person
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 30
        mode: all
      events:
        pre_capture: 2
        post_capture: 2
    motion:
      mask:
        - 441,707,437,671,11,676,11,710
    zones:
      back_step:
        coordinates: 979,720,1122,720,1086,564,1059,533,965,533
  front_door:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - record
            - detect
    objects:
      track:
        - person
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 30
        mode: all
      events:
        pre_capture: 2
        post_capture: 2
    motion:
      mask:
        - 14,676,437,672,439,704,16,703
    zones:
      front_step:
        coordinates: 0,361,244,225,664,720,253,720
  porch:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - record
            - detect
    objects:
      track:
        - person
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 30
        mode: all
      events:
        pre_capture: 2
        post_capture: 2
    motion:
      mask:
       - 442,707,442,664,14,665,12,711
  front_garden:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - record
            - detect
    objects:
      track:
        - person
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 30
        mode: all
      events:
        pre_capture: 2
        post_capture: 2
    motion:
      mask:
        - 12,705,439,703,437,666,11,671
        - 0,0,1280,0,1280,274,908,292,351,354,0,452  
  kitchen:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - detect
    detect:
      enabled: false
    motion:
      mask:
        - 0,720,433,720,433,677,0,676
        - 856,123,1193,125,1222,505,1193,720,700,720,735,530,851,521,854,315,730,306,732,141
  #living_room:
  #  ffmpeg:
  #    inputs:
  #      - path: rtsp://192.168.2.110:8554/livingroom
  #        roles:
  #          - rtmp
  #          - detect
  #  detect:
  #    enabled: false
  #  birdseye:
  #    enabled: False
  #  motion:
  #    mask:
  #      - 8,713,428,715,429,668,7,666
  home_office:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554/live
          roles:
            - rtmp
            - detect
    detect:
      enabled: false
    birdseye:
      enabled: False
    motion:
      mask:
        - 918,718,1251,716,1253,664,915,669
  home_theater:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554/live
          roles:
            - rtmp
            - detect
    detect:
      enabled: false
    birdseye:
      enabled: False
    motion:
      mask:
        - 920,712,1255,712,1253,666,916,666

 

[yayitazale]

16 hours ago, The Transplant said:

 

I will look into FFMPEG - I haven't found any how-tos so will see if I can figure that out.

 

Before doing that I wanted to get it running cleanly.  Right now I can only see clips in UI when in progress.  Some show the clip link as greyed out or others report "The media could not be loaded, either because the server or network failed or because the format is not supported."

 

Probably related, I noticed that the media folder frigate12 I configured has nothing in it.  But the frigate folder set up for the original docker is still showing new files.  The old Frigate docker is not started.  The media path is setup - but I think something is getting crossed here?

 

 

I captured what I think are the log entries when I try to play a clip that returns the error.

 

2023-09-04 09:43:51.189378806  [2023-09-04 09:43:51] frigate.http                   ERROR   : No recordings found for the requested time range
2023-09-04 09:43:51.709133133  2023/09/04 09:43:51 [error] 172#172: *275 ngx_child_request_wev_handler: upstream returned a bad status 404 while sending to client, client: 192.168.2.201, server: , request: "GET /vod/event/1693824835.69601-0uhrev/master.m3u8 HTTP/1.1", host: "192.168.2.110:5000", referrer: "http://192.168.2.110:5000/events"
2023-09-04 09:43:51.709171127  192.168.2.201 - - [04/Sep/2023:09:43:51 -0400] "GET /vod/event/1693824835.69601-0uhrev/master.m3u8 HTTP/1.1" 502 559 "http://192.168.2.110:5000/events" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.5735.106 Safari/537.36 WebCatalogPhoton/34.2.0" "-"
2023-09-04 09:43:51.736153730  [2023-09-04 09:43:51] frigate.http                   ERROR   : Event does not have recordings: 1693824835.69601-0uhrev
2023-09-04 09:43:51.736772756  2023/09/04 09:43:51 [error] 172#172: *275 ngx_child_request_wev_handler: upstream returned a bad status 404 while sending to client, client: 192.168.2.201, server: , request: "GET /vod/event/1693824835.69601-0uhrev/master.m3u8 HTTP/1.1", host: "192.168.2.110:5000", referrer: "http://192.168.2.110:5000/events"
2023-09-04 09:43:51.736777945  192.168.2.201 - - [04/Sep/2023:09:43:51 -0400] "GET /vod/event/1693824835.69601-0uhrev/master.m3u8 HTTP/1.1" 502 559 "http://192.168.2.110:5000/events" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.5735.106 Safari/537.36 WebCatalogPhoton/34.2.0" "-"
2023-09-04 09:43:58.377046426  192.168.2.113 - - [04/Sep/2023:09:43:58 -0400] "GET /api/stats HTTP/1.1" 200 4241 "-" "HomeAssistant/2023.8.3 aiohttp/3.8.5 Python/3.11" "-"

 

And my config:

 

mqtt:
  host: 192.168.2.110
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: frigate
  password: depeche6667
  stats_interval: 60
detectors:
  coral:
    type: edgetpu
    device: usb
record:
  enabled: true
  retain:
    days: 30
    mode: all
birdseye:
  enabled: True
  mode: continuous
cameras:
  garage:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - record
            - detect
    objects:
      track:
        - person
        - car
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 30
        mode: all
      events:
        pre_capture: 2
        post_capture: 2
    motion:
      mask:
        - 0,720,441,720,643,308,573,129,1168,131,1168,0,513,0,0,0
  back_garden:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - record
            - detect
    objects:
      track:
        - person
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 30
        mode: all
      events:
        pre_capture: 2
        post_capture: 2
    motion:
      mask:
        - 441,707,437,671,11,676,11,710
    zones:
      back_step:
        coordinates: 979,720,1122,720,1086,564,1059,533,965,533
  front_door:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - record
            - detect
    objects:
      track:
        - person
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 30
        mode: all
      events:
        pre_capture: 2
        post_capture: 2
    motion:
      mask:
        - 14,676,437,672,439,704,16,703
    zones:
      front_step:
        coordinates: 0,361,244,225,664,720,253,720
  porch:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - record
            - detect
    objects:
      track:
        - person
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 30
        mode: all
      events:
        pre_capture: 2
        post_capture: 2
    motion:
      mask:
       - 442,707,442,664,14,665,12,711
  front_garden:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - record
            - detect
    objects:
      track:
        - person
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 30
        mode: all
      events:
        pre_capture: 2
        post_capture: 2
    motion:
      mask:
        - 12,705,439,703,437,666,11,671
        - 0,0,1280,0,1280,274,908,292,351,354,0,452  
  kitchen:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554//h264Preview_01_main
          roles:
            - rtmp
            - detect
    detect:
      enabled: false
    motion:
      mask:
        - 0,720,433,720,433,677,0,676
        - 856,123,1193,125,1222,505,1193,720,700,720,735,530,851,521,854,315,730,306,732,141
  #living_room:
  #  ffmpeg:
  #    inputs:
  #      - path: rtsp://192.168.2.110:8554/livingroom
  #        roles:
  #          - rtmp
  #          - detect
  #  detect:
  #    enabled: false
  #  birdseye:
  #    enabled: False
  #  motion:
  #    mask:
  #      - 8,713,428,715,429,668,7,666
  home_office:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554/live
          roles:
            - rtmp
            - detect
    detect:
      enabled: false
    birdseye:
      enabled: False
    motion:
      mask:
        - 918,718,1251,716,1253,664,915,669
  home_theater:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554/live
          roles:
            - rtmp
            - detect
    detect:
      enabled: false
    birdseye:
      enabled: False
    motion:
      mask:
        - 920,712,1255,712,1253,666,916,666

 

In the folders mapping you should have this, as inside the container there is no difference between the dockers. That is the point of using containers, that for the container itself everything is where it has to be but you can tinker the things from outside.

 

 

[dopeytree]

@yayitazale would you be interested in adding WhosAtMyFeeder https://github.com/mmcc-xx/WhosAtMyFeeder to the unraid app store? I'm playing with https://hub.docker.com/r/zarguell/whosatmyfeeder/ as a compose but not got it set up right yet. I'm sure you could throw a template together easily.

 

Edited September 6 by dopeytree

[yayitazale]

3 hours ago, dopeytree said:

@yayitazale would you be interested in adding WhosAtMyFeeder https://github.com/mmcc-xx/WhosAtMyFeeder to the unraid app store? I'm playing with https://hub.docker.com/r/zarguell/whosatmyfeeder/ as a compose but not got it set up right yet. I'm sure you could throw a template together easily.

 

Very nice recommendation, I didn't know about this project. I have added a template and you have it already available in the CA store. If you see something to be changed you can just make PRs here: https://gitlab.com/yayitazale/unraid-templates/-/blob/main/yayitazale/whosatmyfeeder.xml

[NewDisplayName]

On 8/26/2023 at 5:02 PM, yayitazale said:

Yes but read the docs carefully since there are some breaking changes.

 

For a more safe deployment and to be able to rollback to v11 as many times as you need:

• Create a new folder on appdata called frigate-new or something like that.
• Create a new media folder again with a different name.
• Just stop v11 frigate, don't delete.
• Create a new config file with the new requirements in the new folder
• Launch the new frigate 12 with a different name, like "frigate12" and change the path of the config file and media path to the new ones. In this way you can have both old and new frigate (only one running but both containers).
• You can make trials to make v12 to work, but if you don't make it in just one try, you can just stop the frigate 12 and start the 11 as many times as you need.
• When you are ready to move to v12 definitely, stop and remove the v11 app, delete de v11 config file, move the v12 config to original frigate config folder, rename the v12 app to just frigate, and launch it pointing to the original appdata and media paths.

You should post this genereall tutorials inside your first post. Why answer these questions over and over again?

 

Also you could use my tut i wrote there. 

[dopeytree]

Took me a few days but finally got Whosinmyfeeder working. 

 

 

Frigate

 

The problem was I was putting the MQQT port on the end of the IP.

For anyone else looking this is what the config should look like for Whosinmyfeeder

 

NOTE: Only frigate needs a port no on the end of the IP

 

Whosinmyfeeder config.yml

frigate:
  frigate_url: http://192.168.22.2:5000
  mqtt_server: 192.168.22.2
  mqtt_auth: false
  mqtt_username: 
  mqtt_password: 
  main_topic: frigatea
  camera:
    - barn_inside
  object: bird
classification:
  model: model.tflite
  threshold: 0.6
webui:
  port: 7766
  host: 0.0.0.0

 

Edited September 9 by dopeytree

[maxistviews]

I recently purchased a USB Coral and tried installing it onto unraid with a new frigate install. I first plugged it into my PC and installed the Windows drivers, turning on the full power mode. Then when I inserted into my unraid box, it showed up as "Global" which I know to be correct, but shortly after this, it no longer appears. No google or global USB devices. Has anyone else had this issue? Was there a driver update I was supposed to do on top of this or something?