[SUPPORT] blakeblackshear - Frigate


Recommended Posts

23 minutes ago, yayitazale said:

 

 

As far as I read on these closed issues on github, it looks like a MQTT connection problem. Please use the IP instead of the FQDN.

 

https://github.com/blakeblackshear/frigate/issues/2066

https://github.com/blakeblackshear/frigate/issues/2094

 

If that doesn't works please open an issue on github, this doesn't look like a an error related with Unraid template.

Thank you, I did get Frigate running on the first try now. I have been looking through the issue's on the Frigate github, but couldn't find it. Thank you for helping out.

  • Like 1
Link to comment

I'm very new to Unraid and Frigate, and just trying to get started.  With the Coral accelerator TPU drivers installed from the community apps, I was assuming I could go into Unraid's tools > system hardware and then see that my M.2 Coral was recognized.  So far, this doesn't seem to be the case (see screenshot below).  For you guys that have this same setup, where should the M.2 coral show up once the drivers are installed?

 

1355328592_Unraidsystemdevices.thumb.png.761d7ce9972f0e04a727f2253755cd70.png

Link to comment
7 hours ago, jonathanmarshall said:

I'm very new to Unraid and Frigate, and just trying to get started.  With the Coral accelerator TPU drivers installed from the community apps, I was assuming I could go into Unraid's tools > system hardware and then see that my M.2 Coral was recognized.  So far, this doesn't seem to be the case (see screenshot below).  For you guys that have this same setup, where should the M.2 coral show up once the drivers are installed?

 

1355328592_Unraidsystemdevices.thumb.png.761d7ce9972f0e04a727f2253755cd70.png

You have the answer here https://forums.unraid.net/topic/98064-support-blakeblackshear-frigate/?do=findComment&comment=1043782

Link to comment

Thanks in advance, I've been reading and trying to get the coral to work for days.

I'm really new as well and trying to get the M.2 coral working.

I am running unraid 6.9.2 with the unraid Coral accelerator module drivers, Home assistant 6.6 as a VM and frigate NVR 2.3

 

settings page for Coral accelerator module drivers

 

Status: ALIVE
Temperature: 38.05 °C
Operating Frequency: 500 MHz
Driver Version: 1.1
Framework Version: 1.1.2

Set Temperatur Limits:
Interrupt Temperature: 99.80 °C
Status: DISABLED

Shutdown Temperature: 104.80 °C
Status: ENABLED

Trottle Temperatures:
84.80 °C - 89.80 °C - 94.80 °C

 

My coral shows up under unraid system devices as

IOMMU group 28:[1ac1:089a] 04:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU (tried both on and off "Bind selected to VFIO at Boot")

 

The modules are loaded in unraid

lsmod

apex                   16384  0
gasket                 90112  1 apex

 

Tried many variants of

detectors:

  coral:

    type: edgetpu

    device: pci:0

 

detectors:

  coral_pci:

    type: edgetpu

    device: pci:

 

 

Frigate log with no detectors

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2021-11-02 11:24:09] frigate.app                    INFO    : Starting Frigate (0.9.4-26ae608)
[2021-11-02 11:24:09] frigate.app                    INFO    : Creating directory: /tmp/cache
Starting migrations
[2021-11-02 11:24:09] peewee_migrate                 INFO    : Starting migrations
There is nothing to migrate
[2021-11-02 11:24:09] peewee_migrate                 INFO    : There is nothing to migrate
[2021-11-02 11:24:09] frigate.mqtt                   INFO    : MQTT connected
[2021-11-02 11:24:09] frigate.app                    INFO    : Output process started: 242
[2021-11-02 11:24:09] detector.cpu                   INFO    : Starting detection process: 241
[2021-11-02 11:24:09] ws4py                          INFO    : Using epoll
[2021-11-02 11:24:09] frigate.edgetpu                WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
[2021-11-02 11:24:09] frigate.app                    INFO    : Camera processor started for Front: 247
[2021-11-02 11:24:09] frigate.app                    INFO    : Camera processor started for Back: 249
[2021-11-02 11:24:09] frigate.app                    INFO    : Camera processor started for living room: 250
[2021-11-02 11:24:09] frigate.app                    INFO    : Capture process started for Front: 252
[2021-11-02 11:24:09] frigate.app                    INFO    : Capture process started for Back: 255
[2021-11-02 11:24:09] frigate.app                    INFO    : Capture process started for living room: 261
[2021-11-02 11:24:09] ws4py                          INFO    : Using epoll

 

frigate log with detectors

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2021-11-02 11:28:56] frigate.app                    INFO    : Starting Frigate (0.9.4-26ae608)
[2021-11-02 11:28:57] frigate.app                    INFO    : Creating directory: /tmp/cache
Starting migrations
[2021-11-02 11:28:57] peewee_migrate                 INFO    : Starting migrations
There is nothing to migrate
[2021-11-02 11:28:57] peewee_migrate                 INFO    : There is nothing to migrate
[2021-11-02 11:28:57] detector.coral_pci             INFO    : Starting detection process: 241
[2021-11-02 11:28:57] frigate.mqtt                   INFO    : MQTT connected
[2021-11-02 11:28:57] ws4py                          INFO    : Using epoll
Process detector:coral_pci:
[2021-11-02 11:28:57] frigate.edgetpu                INFO    : Attempting to load TPU as pci
[2021-11-02 11:28:57] frigate.edgetpu                ERROR   : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate
    delegate = Delegate(library, options)
  File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in __init__
    raise ValueError(capture.message)
ValueError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
    self.run()
  File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/opt/frigate/frigate/edgetpu.py", line 156, in run_detector
    object_detector = LocalObjectDetector(
  File "/opt/frigate/frigate/edgetpu.py", line 64, in __init__
    edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
  File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate
    raise ValueError('Failed to load delegate from {}\n{}'.format(
ValueError: Failed to load delegate from libedgetpu.so.1.0
[2021-11-02 11:28:57] frigate.app                    INFO    : Output process started: 243
[2021-11-02 11:28:57] frigate.app                    INFO    : Camera processor started for Front: 249
[2021-11-02 11:28:57] frigate.app                    INFO    : Camera processor started for Back: 251
[2021-11-02 11:28:57] frigate.app                    INFO    : Camera processor started for living room: 253
[2021-11-02 11:28:57] frigate.app                    INFO    : Capture process started for Front: 255
[2021-11-02 11:28:57] frigate.app                    INFO    : Capture process started for Back: 256
[2021-11-02 11:28:57] frigate.app                    INFO    : Capture process started for living room: 266
[2021-11-02 11:28:57] ws4py                          INFO    : Using epoll
[2021-11-02 11:29:17] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting frigate...
[2021-11-02 11:29:17] frigate.app                    INFO    : Stopping...
[2021-11-02 11:29:17] ws4py                          INFO    : Closing all websockets with [1001] 'Server is shutting down'
[2021-11-02 11:29:17] frigate.stats                  INFO    : Exiting watchdog...
[2021-11-02 11:29:17] frigate.events                 INFO    : Exiting event cleanup...
[2021-11-02 11:29:17] frigate.record                 INFO    : Exiting recording maintenance...
[2021-11-02 11:29:17] frigate.watchdog               INFO    : Exiting watchdog...
[2021-11-02 11:29:17] frigate.record                 INFO    : Exiting recording cleanup...
[2021-11-02 11:29:17] frigate.events                 INFO    : Exiting event processor...
[2021-11-02 11:29:17] frigate.object_processing      INFO    : Exiting object processor...
[2021-11-02 11:29:17] peewee.sqliteq                 INFO    : writer received shutdown request, exiting.
[2021-11-02 11:29:17] root                           INFO    : Waiting for detection process to exit gracefully...
[cmd] python3 exited 0
/usr/lib/python3.8/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 9 leaked shared_memory objects to clean up at shutdown
  warnings.warn('resource_tracker: There appear to be %d '
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal

 

Edited by craigc
Link to comment
18 hours ago, jonathanmarshall said:

I'm very new to Unraid and Frigate, and just trying to get started.  With the Coral accelerator TPU drivers installed from the community apps, I was assuming I could go into Unraid's tools > system hardware and then see that my M.2 Coral was recognized.  So far, this doesn't seem to be the case (see screenshot below).  For you guys that have this same setup, where should the M.2 coral show up once the drivers are installed?

 

1355328592_Unraidsystemdevices.thumb.png.761d7ce9972f0e04a727f2253755cd70.png

 

 

My coral shows up under unraid system devices as

IOMMU group 28:[1ac1:089a] 04:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU

Link to comment
4 hours ago, craigc said:

Thanks in advance, I've been reading and trying to get the coral to work for days.

I'm really new as well and trying to get the M.2 coral working.

I am running unraid 6.9.2 with the unraid Coral accelerator module drivers, Home assistant 6.6 as a VM and frigate NVR 2.3

 

settings page for Coral accelerator module drivers

 

Status: ALIVE
Temperature: 38.05 °C
Operating Frequency: 500 MHz
Driver Version: 1.1
Framework Version: 1.1.2

Set Temperatur Limits:
Interrupt Temperature: 99.80 °C
Status: DISABLED

Shutdown Temperature: 104.80 °C
Status: ENABLED

Trottle Temperatures:
84.80 °C - 89.80 °C - 94.80 °C

 

My coral shows up under unraid system devices as

IOMMU group 28:[1ac1:089a] 04:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU (tried both on and off "Bind selected to VFIO at Boot")

 

The modules are loaded in unraid

lsmod

apex                   16384  0
gasket                 90112  1 apex

 

Tried many variants of

detectors:

  coral:

    type: edgetpu

    device: pci:0

 

detectors:

  coral_pci:

    type: edgetpu

    device: pci:

 

 

Frigate log with no detectors

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2021-11-02 11:24:09] frigate.app                    INFO    : Starting Frigate (0.9.4-26ae608)
[2021-11-02 11:24:09] frigate.app                    INFO    : Creating directory: /tmp/cache
Starting migrations
[2021-11-02 11:24:09] peewee_migrate                 INFO    : Starting migrations
There is nothing to migrate
[2021-11-02 11:24:09] peewee_migrate                 INFO    : There is nothing to migrate
[2021-11-02 11:24:09] frigate.mqtt                   INFO    : MQTT connected
[2021-11-02 11:24:09] frigate.app                    INFO    : Output process started: 242
[2021-11-02 11:24:09] detector.cpu                   INFO    : Starting detection process: 241
[2021-11-02 11:24:09] ws4py                          INFO    : Using epoll
[2021-11-02 11:24:09] frigate.edgetpu                WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
[2021-11-02 11:24:09] frigate.app                    INFO    : Camera processor started for Front: 247
[2021-11-02 11:24:09] frigate.app                    INFO    : Camera processor started for Back: 249
[2021-11-02 11:24:09] frigate.app                    INFO    : Camera processor started for living room: 250
[2021-11-02 11:24:09] frigate.app                    INFO    : Capture process started for Front: 252
[2021-11-02 11:24:09] frigate.app                    INFO    : Capture process started for Back: 255
[2021-11-02 11:24:09] frigate.app                    INFO    : Capture process started for living room: 261
[2021-11-02 11:24:09] ws4py                          INFO    : Using epoll

 

frigate log with detectors

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2021-11-02 11:28:56] frigate.app                    INFO    : Starting Frigate (0.9.4-26ae608)
[2021-11-02 11:28:57] frigate.app                    INFO    : Creating directory: /tmp/cache
Starting migrations
[2021-11-02 11:28:57] peewee_migrate                 INFO    : Starting migrations
There is nothing to migrate
[2021-11-02 11:28:57] peewee_migrate                 INFO    : There is nothing to migrate
[2021-11-02 11:28:57] detector.coral_pci             INFO    : Starting detection process: 241
[2021-11-02 11:28:57] frigate.mqtt                   INFO    : MQTT connected
[2021-11-02 11:28:57] ws4py                          INFO    : Using epoll
Process detector:coral_pci:
[2021-11-02 11:28:57] frigate.edgetpu                INFO    : Attempting to load TPU as pci
[2021-11-02 11:28:57] frigate.edgetpu                ERROR   : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate
    delegate = Delegate(library, options)
  File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in __init__
    raise ValueError(capture.message)
ValueError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
    self.run()
  File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/opt/frigate/frigate/edgetpu.py", line 156, in run_detector
    object_detector = LocalObjectDetector(
  File "/opt/frigate/frigate/edgetpu.py", line 64, in __init__
    edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
  File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate
    raise ValueError('Failed to load delegate from {}\n{}'.format(
ValueError: Failed to load delegate from libedgetpu.so.1.0
[2021-11-02 11:28:57] frigate.app                    INFO    : Output process started: 243
[2021-11-02 11:28:57] frigate.app                    INFO    : Camera processor started for Front: 249
[2021-11-02 11:28:57] frigate.app                    INFO    : Camera processor started for Back: 251
[2021-11-02 11:28:57] frigate.app                    INFO    : Camera processor started for living room: 253
[2021-11-02 11:28:57] frigate.app                    INFO    : Capture process started for Front: 255
[2021-11-02 11:28:57] frigate.app                    INFO    : Capture process started for Back: 256
[2021-11-02 11:28:57] frigate.app                    INFO    : Capture process started for living room: 266
[2021-11-02 11:28:57] ws4py                          INFO    : Using epoll
[2021-11-02 11:29:17] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting frigate...
[2021-11-02 11:29:17] frigate.app                    INFO    : Stopping...
[2021-11-02 11:29:17] ws4py                          INFO    : Closing all websockets with [1001] 'Server is shutting down'
[2021-11-02 11:29:17] frigate.stats                  INFO    : Exiting watchdog...
[2021-11-02 11:29:17] frigate.events                 INFO    : Exiting event cleanup...
[2021-11-02 11:29:17] frigate.record                 INFO    : Exiting recording maintenance...
[2021-11-02 11:29:17] frigate.watchdog               INFO    : Exiting watchdog...
[2021-11-02 11:29:17] frigate.record                 INFO    : Exiting recording cleanup...
[2021-11-02 11:29:17] frigate.events                 INFO    : Exiting event processor...
[2021-11-02 11:29:17] frigate.object_processing      INFO    : Exiting object processor...
[2021-11-02 11:29:17] peewee.sqliteq                 INFO    : writer received shutdown request, exiting.
[2021-11-02 11:29:17] root                           INFO    : Waiting for detection process to exit gracefully...
[cmd] python3 exited 0
/usr/lib/python3.8/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 9 leaked shared_memory objects to clean up at shutdown
  warnings.warn('resource_tracker: There appear to be %d '
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal

 

Please use the search box, this have been answered 2 times, the last time just 2 posts upper than yours.

 

 

Edited by yayitazale
Link to comment

Thanks, I've spent 2 days going through the 11 pages of this forum and several other sites. If I don't know what the problem is and I didn't see anything in the 11 pages that specifically mentions the same problem or if it was solved then I'm just shooting in the dark.

Edited by craigc
Link to comment

Hey folks. I've been using Frigate for a month or two and it's been really solid until recently. 

Today, I found myself unable to login and it was because frigate filled /tmp/frigate with recordings on the unraid installation.

SSHing in and deleting them fixed the situation, but it's still filling tmp with recordings. Was this always happening? is some cleanup mechanism broken?

Link to comment
3 hours ago, blackgold9 said:

Hey folks. I've been using Frigate for a month or two and it's been really solid until recently. 

Today, I found myself unable to login and it was because frigate filled /tmp/frigate with recordings on the unraid installation.

SSHing in and deleting them fixed the situation, but it's still filling tmp with recordings. Was this always happening? is some cleanup mechanism broken?

I have exact same issue but I though It was just me. There is a ongoing issue here https://github.com/blakeblackshear/frigate/issues/2006

 

I just posted that some unraid users are experiencing this issue.

Link to comment
22 hours ago, yayitazale said:

I have exact same issue but I though It was just me. There is a ongoing issue here https://github.com/blakeblackshear/frigate/issues/2006

 

I just posted that some unraid users are experiencing this issue.

 

I have also seen this, I assumed it was me "faffing" with TS change ffmpeg options, then the reversion back.

 

Luckily I've got frigate cache set to /dev/shm therefore it can never kill anything in the UnRAID GUI etc.

 

Flubster 

  • Like 1
Link to comment

I'm being a bit n00b but I cannot get the container to even start.

Running the NVIDIA version and I can see it has the --runtime=nvidia argument already there.

 

I added config.yaml file that looks like:

mqtt:
  host: 10.0.0.12
  user: mqtt
  password: xx

detectors:
  cpu1:
    type: cpu
    num_threads: 3
  cpu2:
    type: cpu
    num_threads: 3

cameras:
  entrance: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: rtsps://10.0.0.11:7441/XwEWYTw8qGj76R9w?enableSrtp # <----- Update for your camera
          roles:
            - detect
            - rtmp
    detect:
      width: 1920 # <---- update for your camera's resolution
      height: 1080 # <---- update for your camera's resolution

 

No matter where I put the config.yaml in the appdata/frigate-nvidia/config.yaml or appdata/frigate-nvidida/config/config.yaml

I keep getting: [Errno 2] No such file or directory: '/config/config.yml'

 

Can someone guide me if my config is wrong, or if I'm placing it somewhere wrong?

Link to comment
15 minutes ago, SavellM said:

I'm being a bit n00b but I cannot get the container to even start.

Running the NVIDIA version and I can see it has the --runtime=nvidia argument already there.

 

I added config.yaml file that looks like:

mqtt:
  host: 10.0.0.12
  user: mqtt
  password: xx

detectors:
  cpu1:
    type: cpu
    num_threads: 3
  cpu2:
    type: cpu
    num_threads: 3

cameras:
  entrance: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: rtsps://10.0.0.11:7441/XwEWYTw8qGj76R9w?enableSrtp # <----- Update for your camera
          roles:
            - detect
            - rtmp
    detect:
      width: 1920 # <---- update for your camera's resolution
      height: 1080 # <---- update for your camera's resolution

 

No matter where I put the config.yaml in the appdata/frigate-nvidia/config.yaml or appdata/frigate-nvidida/config/config.yaml

I keep getting: [Errno 2] No such file or directory: '/config/config.yml'

 

Can someone guide me if my config is wrong, or if I'm placing it somewhere wrong?

Your file is yaml and it has to be yml

  • Like 1
Link to comment
1 minute ago, SavellM said:

Sorry next question: 

I have some Unifi cameras, just hooked it in, and its REALLY grainy. 

Does anyone have any idea how I can reduce the grainyness? 

Using Unifi is pretty sweet and looks good. Through Frigate it looks like I'm in a thunderstorm

I don't have unify cameras but with some other brands, they use to have two different streams: one high res and one low res. Check the manual/docs of your camera to see if there is another stream avaiable or any way to select the stream quality on the configuration..

Link to comment
Just now, yayitazale said:

I don't have unify cameras but with some other brands, they use to have two different streams: one high res and one low res. Check the manual/docs of your camera to see if there is another stream avaiable or any way to select the stream quality on the configuration..

Thanks I did try to check that and I grabbed the 1080p stream which is the highest my cam does.

 

Will keep investigating 

  • Thanks 1
Link to comment

I'm using unifi on my Frigate instance.

 

What resolution have you set the rtsp to?

 

I have detect pointing at one, and record set at a higher res

 

cameras:
  front:
    ffmpeg:
      inputs:
        - path: rtsp://link (medium)
          roles:
            - detect
        - path: rtsp://link (High)
          roles:
            - record
    detect:
      width: 1024
      height: 576
      fps: 5

 

Link to comment
27 minutes ago, Flubster said:

I'm using unifi on my Frigate instance.

 

What resolution have you set the rtsp to?

 

I have detect pointing at one, and record set at a higher res

 

cameras:
  front:
    ffmpeg:
      inputs:
        - path: rtsp://link (medium)
          roles:
            - detect
        - path: rtsp://link (High)
          roles:
            - record
    detect:
      width: 1024
      height: 576
      fps: 5

 

The resolution has to be defined only for the detect stream as ffmpeg need to know that information to perform the transformation to the resolution that fits the Corals model. This resolution if you are using the builtin model ssd mobilnet 1 is 300*300 https://coral.ai/models/object-detection/ so the way to make your system as efficient as possible is using the low res stream for detecting and high res for recording and rtmp restreaming

Edited by yayitazale
Link to comment

 Hi just started with unRaid a total newbie i am having many problems with the Edge TPU  creating many errors regarding ffmeg. 

 I have started off with a simple config which works with the CPU but not with the Coral TPU.  i have created configs for my type of camera Reolink as per the Frigate information with out success. i have attached  error report from unraid dockers logs and config.yml

 

 any help would be appreciated.

Frigate ffmpeg error.rtf config.yml

Link to comment
1 hour ago, mikey6283 said:

 Hi just started with unRaid a total newbie i am having many problems with the Edge TPU  creating many errors regarding ffmeg. 

 I have started off with a simple config which works with the CPU but not with the Coral TPU.  i have created configs for my type of camera Reolink as per the Frigate information with out success. i have attached  error report from unraid dockers logs and config.yml

 

 any help would be appreciated.

Frigate ffmpeg error.rtf 92.03 kB · 0 downloads config.yml 1.87 kB · 0 downloads

First of all, can you attach a screenshot of the configuration of the container? Witch model of coral do you have? It is a PCI one? Did you installed the driver from the plugins of unraid?

 

Then, on your config you have a mistake:

 

detectors:
 coral:
   type: edgetpu
   device:pci

 

must be:

detectors:
 coral:
   type: edgetpu
   device: pci

 

You have MQTT defined twice.

 

This is wrong:

 

cameras:
  front_driveway
  reolink:
    ffmpeg:

Must delete relonik line and end the name of the camera with double colon like this:

 

cameras:
  front_driveway:
    ffmpeg:

 

Same there:

 

reolink:
  garage_driveway
    ffmpeg:

Must be:

  garage_driveway:
    ffmpeg:

 

Did you followed the https://docs.frigate.video/guides/getting_started ????

 

 

Finally, about FFMPEG, I'm not ffmpeg expert so I can't help you on that, but I think that you are not configuring properly (you are defining input_args only, no hwaccel_args and no output args... I recommend you to start with a minimal config of "hwaccel_args" following the docs https://docs.frigate.video/configuration/hardware_acceleration.

 

There is some info on github for reolink: https://github.com/blakeblackshear/frigate/issues/1974

 

 

 

Edited by yayitazale
Link to comment

Hi yayitazale    Yes i  did install the drivers from unraid and are installed As i have seem that TPU is installed and found

. I  have  PCI Dual edgetpu installed, I realize that i will be only able to use 1 unit.

Thanks for the reply , i have followed your instruction and made the adjustment and  I have  looked at the link provide previously however I have a different error regarding mqtt ?

 

 I am unable to solve this config as i have serval time in the last hour.

 

If and when i  am to get Frigate  working  how can storage the clips and recordings  to disks 2 in my array would the path be /mnt/disks2/frigate/clips /mnt/disks/frigate/recordings to path  /media/frigate ? or something elsee

 

 

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2021-11-18 19:11:01] frigate.app INFO : Starting Frigate (0.9.4-26ae608)
*************************************************************
*************************************************************
*** Your config file is not valid! ***
*** Please check the docs at ***
*** https://docs.frigate.video/configuration/index ***
*************************************************************
*************************************************************
*** Config Validation Errors ***
*************************************************************
4 validation errors for FrigateConfig
mqtt
field required (type=value_error.missing)
detectors -> mqtt -> host
extra fields not permitted (type=value_error.extra)
detectors -> mqtt -> password
extra fields not permitted (type=value_error.extra)
detectors -> mqtt -> user
extra fields not permitted (type=value_error.extra)
*************************************************************
*** End Config Validation Errors ***
*************************************************************
[cmd] python3 exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

 

 

mqtt:
  host: 192.168.0.81
# user: mikey
# password: mqtt6283

detectors:
  coral:
    type: edgetpu
    device: pci

database:
  path: /media/frigate/frigate.db 

cameras:
  front_driveway:
    ffmpeg:
      hwaccel_args:
        - -hwaccel
        - vaapi
        - -hwaccel_device
        - /dev/dri/renderD128
        - -hwaccel_output_format
        - yuv420p
      input_args:
        - -avoid_negative_ts
        - make_zero
        - -fflags
        - nobuffer+genpts+discardcorrupt
        - -flags
        - low_delay
        - -strict
        - experimental
        - -analyzeduration
        - 1000M
        - -probesize
        - 1000M
        - -rw_timeout
        - "5000000"
      inputs:
        - path: http://reolink_192.168.0.48/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=Front1
          roles:
            - record
            - rtmp
        - path: http://reolink_192.168.0.48/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=Front1
          roles:
            - detect
    detect:
      width: 640
      height: 480
      fps: 7

  garage_driveway:
    ffmpeg:
      hwaccel_args:
      - -hwaccel
      - vaapi
      - -hwaccel_device
      - /dev/dri/renderD128
      - -hwaccel_output_format
      - yuv420p
      input_args:
      - -avoid_negative_ts
      - make_zero
      - -fflags
      - nobuffer+genpts+discardcorrupt
      - -flags
      - low_delay
      - -strict
      - experimental
      - -analyzeduration
      - 1000M
      - -probesize
      - 1000M
      - -rw_timeout
      - "5000000"
      inputs:
        - path: http://reolink_192.168.0.51/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=Garage
          roles:
            - record
            - rtmp
        - path: http://reolink_192.168.0.51/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=Garage1
          roles:
            - detect
      output_args:
        record: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy
    detect:
      width: 640
      height: 480
      fps: 7
    record:
      enabled: True
      retain_days: 0
      events:
        retain:
          default: 10

 

Link to comment
11 hours ago, mikey6283 said:

Hi yayitazale    Yes i  did install the drivers from unraid and are installed As i have seem that TPU is installed and found

. I  have  PCI Dual edgetpu installed, I realize that i will be only able to use 1 unit.

Thanks for the reply , i have followed your instruction and made the adjustment and  I have  looked at the link provide previously however I have a different error regarding mqtt ?

 

 I am unable to solve this config as i have serval time in the last hour.

 

If and when i  am to get Frigate  working  how can storage the clips and recordings  to disks 2 in my array would the path be /mnt/disks2/frigate/clips /mnt/disks/frigate/recordings to path  /media/frigate ? or something elsee

 

 

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2021-11-18 19:11:01] frigate.app INFO : Starting Frigate (0.9.4-26ae608)
*************************************************************
*************************************************************
*** Your config file is not valid! ***
*** Please check the docs at ***
*** https://docs.frigate.video/configuration/index ***
*************************************************************
*************************************************************
*** Config Validation Errors ***
*************************************************************
4 validation errors for FrigateConfig
mqtt
field required (type=value_error.missing)
detectors -> mqtt -> host
extra fields not permitted (type=value_error.extra)
detectors -> mqtt -> password
extra fields not permitted (type=value_error.extra)
detectors -> mqtt -> user
extra fields not permitted (type=value_error.extra)
*************************************************************
*** End Config Validation Errors ***
*************************************************************
[cmd] python3 exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

 

 

mqtt:
  host: 192.168.0.81
# user: mikey
# password: mqtt6283

detectors:
  coral:
    type: edgetpu
    device: pci

database:
  path: /media/frigate/frigate.db 

cameras:
  front_driveway:
    ffmpeg:
      hwaccel_args:
        - -hwaccel
        - vaapi
        - -hwaccel_device
        - /dev/dri/renderD128
        - -hwaccel_output_format
        - yuv420p
      input_args:
        - -avoid_negative_ts
        - make_zero
        - -fflags
        - nobuffer+genpts+discardcorrupt
        - -flags
        - low_delay
        - -strict
        - experimental
        - -analyzeduration
        - 1000M
        - -probesize
        - 1000M
        - -rw_timeout
        - "5000000"
      inputs:
        - path: http://reolink_192.168.0.48/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=Front1
          roles:
            - record
            - rtmp
        - path: http://reolink_192.168.0.48/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=Front1
          roles:
            - detect
    detect:
      width: 640
      height: 480
      fps: 7

  garage_driveway:
    ffmpeg:
      hwaccel_args:
      - -hwaccel
      - vaapi
      - -hwaccel_device
      - /dev/dri/renderD128
      - -hwaccel_output_format
      - yuv420p
      input_args:
      - -avoid_negative_ts
      - make_zero
      - -fflags
      - nobuffer+genpts+discardcorrupt
      - -flags
      - low_delay
      - -strict
      - experimental
      - -analyzeduration
      - 1000M
      - -probesize
      - 1000M
      - -rw_timeout
      - "5000000"
      inputs:
        - path: http://reolink_192.168.0.51/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=Garage
          roles:
            - record
            - rtmp
        - path: http://reolink_192.168.0.51/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=Garage1
          roles:
            - detect
      output_args:
        record: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy
    detect:
      width: 640
      height: 480
      fps: 7
    record:
      enabled: True
      retain_days: 0
      events:
        retain:
          default: 10

 

First of all, dual edge coral is not PCI, is M.2. Anyway, this model is not fully supported by the creator of the driver package plugin as you can read here:

 

About the media mounting, I'm not sure why do you want to write directly into the disk 2. This is not best practice, you should use a share instead of the disk: https://wiki.unraid.net/Manual/Shares

 

I'm attaching you a proper config file created using your variables and the original template of the docs.

 

 

config.yml

Edited by yayitazale
Link to comment
2 hours ago, yayitazale said:

this model is not fully supported by the creator of the driver package plugin as you can read here:

Generally speaking it is fully supported but you need a slot with two separate PCIe lanes for the Dual Edge TPU so that both TPUs are recognized.

 

Some manufacturers are not using the official specifications for these slot because it is mostly used for WiFi Cards, most of the time only one TPU is working because there is only one PCIe lane available in these slots.

 

Hope this makes sense... :)

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.