yayitazale Posted September 10, 2021 Author Share Posted September 10, 2021 8 minutes ago, antwick said: OK - I took the frigate.yml file i had setup and essentially copied it and put it on to appdata/frigate/config.yml and was able to get it up and running. now i just need to figure out how to get it into HA from here. Just install the frigate Hass integration: https://github.com/blakeblackshear/frigate-hass-integration You can add it from HACS o just install it manually. Quote Link to comment
nwootton Posted September 20, 2021 Share Posted September 20, 2021 (edited) So I've had Frigate running on my unRAID for ages without any issues. Home Assistant on a separate box was connected and working as expected. System is happily using a Corel USB adapter and a single camera. At some point last week, I noticed that the container had stopped and was erroring on re-start. I've made sure that the correct USB is selected for the Corel device, that no GPU has snuck back into the settings and that there's space available. I've now completely wiped the image and settings and started again, but I am still getting the same situation. Frigate starts up, runs for a few minutes and then aborts and shuts down with a python error. Anyone advise? Frigate.log config.yml Edited September 20, 2021 by nwootton Spelling Quote Link to comment
yayitazale Posted September 21, 2021 Author Share Posted September 21, 2021 18 hours ago, nwootton said: So I've had Frigate running on my unRAID for ages without any issues. Home Assistant on a separate box was connected and working as expected. System is happily using a Corel USB adapter and a single camera. At some point last week, I noticed that the container had stopped and was erroring on re-start. I've made sure that the correct USB is selected for the Corel device, that no GPU has snuck back into the settings and that there's space available. I've now completely wiped the image and settings and started again, but I am still getting the same situation. Frigate starts up, runs for a few minutes and then aborts and shuts down with a python error. Anyone advise? Frigate.log 6.41 kB · 1 download config.yml 2.51 kB · 0 downloads First of all, you don't need to specify the USB, just use the /dev/bus/usb as device and frigate will find the USB. Then, to use CORAL you must start the container as privileged, there is no other way for now. As I see you unselected this option. Select it again and try if it works. Quote Link to comment
nwootton Posted September 21, 2021 Share Posted September 21, 2021 @yayitazale Thanks for that. Changing to privileged made no difference, neither did amending the USB path to use the ' /dev/bus/usb' path. The docker still fails with a python error Fatal Python error: Aborted and this is generally proceeded by this line: F :1150] HandleQueuedBulkIn transfer in failed. Unknown: USB transfer error 1 [LibUsbDataInCallback] The system tells me that the TPU has been detected: detector.coral INFO : Starting detection process: 36 frigate.app INFO : Camera processor started for drive: 39 frigate.app INFO : Capture process started for drive: 40 frigate.edgetpu INFO : Attempting to load TPU as usb frigate.edgetpu INFO : TPU found I've also changed the port that the TPU is plugged into and checked that the LED on it is on. Quote Link to comment
yayitazale Posted September 21, 2021 Author Share Posted September 21, 2021 13 minutes ago, nwootton said: @yayitazale Thanks for that. Changing to privileged made no difference, neither did amending the USB path to use the ' /dev/bus/usb' path. The docker still fails with a python error Fatal Python error: Aborted and this is generally proceeded by this line: F :1150] HandleQueuedBulkIn transfer in failed. Unknown: USB transfer error 1 [LibUsbDataInCallback] The system tells me that the TPU has been detected: detector.coral INFO : Starting detection process: 36 frigate.app INFO : Camera processor started for drive: 39 frigate.app INFO : Capture process started for drive: 40 frigate.edgetpu INFO : Attempting to load TPU as usb frigate.edgetpu INFO : TPU found I've also changed the port that the TPU is plugged into and checked that the LED on it is on. Did you have more USBs pluged in into the same group of ports? It can be a lack of power, try with another cable and unplugging all the other USB (except the boot usb of unraid of course). There is a closed issue with your same problem on github that you can reopen: https://github.com/blakeblackshear/frigate/issues/325 Quote Link to comment
nwootton Posted September 21, 2021 Share Posted September 21, 2021 @yayitazale Power shouldn't be an issue, it's been running fine up until now. No other devices on the USB except the OS - and that is direct onto the motherboard. Neither USB2 or USB3 make any difference to this. I guess it's an issue internal to the docker, rather than unRAID -> docker. Thanks for your help. I'll chase Blake via GitHub/HomeAssistant. 1 Quote Link to comment
yayitazale Posted September 21, 2021 Author Share Posted September 21, 2021 4 minutes ago, nwootton said: @yayitazale Power shouldn't be an issue, it's been running fine up until now. No other devices on the USB except the OS - and that is direct onto the motherboard. Neither USB2 or USB3 make any difference to this. I guess it's an issue internal to the docker, rather than unRAID -> docker. Thanks for your help. I'll chase Blake via GitHub/HomeAssistant. Finger cross is not a tpu failure Quote Link to comment
nwootton Posted September 21, 2021 Share Posted September 21, 2021 @yayitazale Just installed the getting started parrot model detection routine onto my Mac and it runs fine, so it looks like the TPU hasn't failed. https://coral.ai/docs/accelerator/get-started/ 1 Quote Link to comment
Darg Posted September 25, 2021 Share Posted September 25, 2021 I am having an interesting problem where my Coral M.2 works fine after a reboot but after some time, a few days the first time, an hour just today but it had been running fine for a week before that it just stops being available to Frigate and I get: frigate.edgetpu ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. This shuts down the container and restarting the container will just print that error again and then bail. "/dev/apex_0" is still available in an Unraid shell but just stops working in Frigate after working fine for some time. I believe this might be related to an issue some people have reported with the M.2 version where it goes to sleep and cannot be woken again as described here: https://www.reddit.com/r/VFIO/comments/l5awg0/using_google_coral_mpcie_tpu_in_qemu_vm/ and here: https://github.com/blakeblackshear/frigate/issues/1020 I am trying to add options vfio-pci ids=1ac1:089a disable_idle_d3=1 to /etc/modprobe.d/blacklist-apex.conf I was just wondering if anyone else with the M.2 version has had similar problems and is there another solution that worked in case this doesn't fix it for me? I can't currently restart Unraid as I am running a 20 hour preclear on a new 4tb drive. I assume the TPU will work fine after reboot so it's a matter of just waiting and seeing if it fails again. Quote Link to comment
anti Posted September 26, 2021 Share Posted September 26, 2021 (edited) I'm trying to get the new frigate RC4 running and I just can't seem to get it. I pulled that tag and it starts but crashes when it detects anything. what's weird is it runs on home assistant beta version but can't get it on unraid. anyone try or get it working? Edited September 26, 2021 by anti spelling 1 Quote Link to comment
yayitazale Posted September 27, 2021 Author Share Posted September 27, 2021 14 hours ago, anti said: I'm trying to get the new frigate RC4 running and I just can't seem to get it. I pulled that tag and it starts but crashes when it detects anything. what's weird is it runs on home assistant beta version but can't get it on unraid. anyone try or get it working? I didn't have time to tinker with RC's yet, I will give a try this week to prepare the modifications needed on the templates. Quote Link to comment
Darg Posted September 27, 2021 Share Posted September 27, 2021 15 hours ago, anti said: I'm trying to get the new frigate RC4 running and I just can't seem to get it. I pulled that tag and it starts but crashes when it detects anything. what's weird is it runs on home assistant beta version but can't get it on unraid. anyone try or get it working? RC4 is working fine for me. I just upped the image number and restarted the docker, no problems. The issue I am having with the Coral going to sleep were happening in rc3... still waiting to see if it stops again. 1 Quote Link to comment
yayitazale Posted September 28, 2021 Author Share Posted September 28, 2021 On 9/26/2021 at 7:56 PM, anti said: I'm trying to get the new frigate RC4 running and I just can't seem to get it. I pulled that tag and it starts but crashes when it detects anything. what's weird is it runs on home assistant beta version but can't get it on unraid. anyone try or get it working? On 9/27/2021 at 11:04 AM, Darg said: RC4 is working fine for me. I just upped the image number and restarted the docker, no problems. The issue I am having with the Coral going to sleep were happening in rc3... still waiting to see if it stops again. RC4 tested for 2 hours with no issue. Just needed to change some entrys on config.yml according to the breaking changes explained on RC4: https://github.com/blakeblackshear/frigate/releases/tag/v0.9.0-rc4 Detection is working, recording is working, API is working, Web UI is working, nearly same CPU usage. I will update the templates with the instructions and the minnor changes of the docker commands as soon as the final release is publish. Quote Link to comment
bigbangus Posted October 6, 2021 Share Posted October 6, 2021 Anybody update to 0.9.1 yet? I've followed the documentation to fix all the breaking changes in my config, but I get some warnings. For each camera I get this on startup: [2021-10-06 12:10:20] frigate.app WARNING : Camera XXXXXX has record enabled, but record is not assigned to an input. And when I try to use birdseye view in the GUI, some of my cameras are blank and show this warning in the log: [2021-10-06 13:09:08] frigate.output WARNING : Unable to copy frame XXXXXXX1633536757.444885 to birdseye. Otherwise, all my person detection with Home Assistant still works as intended so I have no issues. Just some warnings and not sure why. Config below: mqtt: host: x.x.x.x port: xxxx topic_prefix: frigate client_id: frigate user: mqtt password: xxxxxxxxxxx stats_interval: 60 cameras: uvc_cam1: detect: enabled: true width: 1920 height: 1080 fps: 5 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 objects: person: 30 ffmpeg: inputs: - path: rtsp://xxxxxxxxx roles: - detect - rtmp motion: mask: - 0,370,483,366,487,201,654,204,980,215,988,0,0,0 - 1352,1080,1555,695,1419,606,1309,667,1205,785,1122,850,947,819,764,715,419,1080 zones: driveway: coordinates: 1561,1080,1634,872,1685,695,906,459,589,545,215,435,0,390,0,1080 uvc_cam2: detect: enabled: true width: 1920 height: 1080 fps: 5 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 objects: person: 30 ffmpeg: inputs: - path: rtsp://xxxxxxxxx roles: - detect - rtmp motion: mask: - 0,85,395,85,395,0,0,0 - 1920,0,1920,275,1781,224,1617,250,1450,191,1276,171,1074,156,982,52,778,0 zones: patio: coordinates: 1920,1080,0,1080,0,366,468,208,915,247,1126,126,1589,178,1694,196,1920,258,1920,265 objects: track: - person - dog - cat uvc_cam3: detect: enabled: true width: 1920 height: 1080 fps: 5 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 objects: person: 30 ffmpeg: inputs: - path: rtsp://xxxxxxxx roles: - detect - rtmp motion: mask: - 0,385,220,222,470,174,631,150,712,0,348,0,0,0 - 1920,0,1920,213,1830,222,1773,297,1696,295,1566,231,1559,119,1418,115,1242,96,1099,96,972,42,953,0 - 1632,1080,1439,735,1267,621,1096,568,919,562,745,571,553,646,354,766,237,904,204,1080 zones: backyard: coordinates: 190,132,0,464,0,1080,137,1080,263,797,510,629,750,562,1025,535,1309,577,1643,1015,1840,906,1623,575,1570,441,1607,335,1531,243,1556,117,1429,86,764,137,216,222 objects: track: - person - dog - cat uvc_cam4: detect: enabled: true width: 1920 height: 1080 fps: 5 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 objects: person: 30 ffmpeg: inputs: - path: rtsp://xxxxxxxx roles: - detect - rtmp motion: mask: - 0,83,350,86,348,0,0,0 zones: sidegate: coordinates: 720,1080,1169,1080,854,240,728,137,631,147,644,257 objects: track: - person - dog - cat uvc_cam5: detect: enabled: true width: 1920 height: 1080 fps: 5 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 objects: person: 30 ffmpeg: inputs: - path: rtsp://xxxxxxxxx roles: - detect - rtmp motion: mask: - 0,83,350,86,348,0,0,0 zones: sidefence: coordinates: 609,1080,1337,1080,741,309,567,287 objects: track: - person - dog - cat record: enabled: true retain_days: 0 events: max_seconds: 300 pre_capture: 2 post_capture: 2 retain: default: 10 objects: track: - person - car - dog - cat ffmpeg: hwaccel_args: - -c:v - h264_cuvid detectors: coral: type: edgetpu device: usb Quote Link to comment
Snakesms Posted October 6, 2021 Share Posted October 6, 2021 I've upgraded from the latest release 0.8.4 to 0.9.1 and made required config changes, so that part was processed well according to the log, however every time I do call Frigate to start it fails with an error in the log: frigate Invalid cross-device link: '/media/frigate/clips/frigate.db' -> '/media/frigate/frigate.db' Any ideas why need to be changed or why its complaining in all 0.9.X versions, but does work fine with the version 0.8.4 Thank you in advance Quote Link to comment
nau Posted October 7, 2021 Share Posted October 7, 2021 (edited) 8 hours ago, Snakesms said: I've upgraded from the latest release 0.8.4 to 0.9.1 and made required config changes, so that part was processed well according to the log, however every time I do call Frigate to start it fails with an error in the log: frigate Invalid cross-device link: '/media/frigate/clips/frigate.db' -> '/media/frigate/frigate.db' Any ideas why need to be changed or why its complaining in all 0.9.X versions, but does work fine with the version 0.8.4 Thank you in advance i've added this to config and it started sucessfully database: path: /media/frigate/clips/frigate.db Edited October 7, 2021 by nau Quote Link to comment
yayitazale Posted October 7, 2021 Author Share Posted October 7, 2021 (edited) 8 hours ago, nau said: i've added this to config and it started sucessfully database: path: /media/frigate/clips/frigate.db This is not needed If you don't have changed the Database from the original location. Edited October 7, 2021 by yayitazale Quote Link to comment
yayitazale Posted October 7, 2021 Author Share Posted October 7, 2021 19 hours ago, bigbangus said: Anybody update to 0.9.1 yet? I've followed the documentation to fix all the breaking changes in my config, but I get some warnings. For each camera I get this on startup: [2021-10-06 12:10:20] frigate.app WARNING : Camera XXXXXX has record enabled, but record is not assigned to an input. And when I try to use birdseye view in the GUI, some of my cameras are blank and show this warning in the log: [2021-10-06 13:09:08] frigate.output WARNING : Unable to copy frame XXXXXXX1633536757.444885 to birdseye. Otherwise, all my person detection with Home Assistant still works as intended so I have no issues. Just some warnings and not sure why. Config below: mqtt: host: x.x.x.x port: xxxx topic_prefix: frigate client_id: frigate user: mqtt password: xxxxxxxxxxx stats_interval: 60 cameras: uvc_cam1: detect: enabled: true width: 1920 height: 1080 fps: 5 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 objects: person: 30 ffmpeg: inputs: - path: rtsp://xxxxxxxxx roles: - detect - rtmp motion: mask: - 0,370,483,366,487,201,654,204,980,215,988,0,0,0 - 1352,1080,1555,695,1419,606,1309,667,1205,785,1122,850,947,819,764,715,419,1080 zones: driveway: coordinates: 1561,1080,1634,872,1685,695,906,459,589,545,215,435,0,390,0,1080 uvc_cam2: detect: enabled: true width: 1920 height: 1080 fps: 5 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 objects: person: 30 ffmpeg: inputs: - path: rtsp://xxxxxxxxx roles: - detect - rtmp motion: mask: - 0,85,395,85,395,0,0,0 - 1920,0,1920,275,1781,224,1617,250,1450,191,1276,171,1074,156,982,52,778,0 zones: patio: coordinates: 1920,1080,0,1080,0,366,468,208,915,247,1126,126,1589,178,1694,196,1920,258,1920,265 objects: track: - person - dog - cat uvc_cam3: detect: enabled: true width: 1920 height: 1080 fps: 5 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 objects: person: 30 ffmpeg: inputs: - path: rtsp://xxxxxxxx roles: - detect - rtmp motion: mask: - 0,385,220,222,470,174,631,150,712,0,348,0,0,0 - 1920,0,1920,213,1830,222,1773,297,1696,295,1566,231,1559,119,1418,115,1242,96,1099,96,972,42,953,0 - 1632,1080,1439,735,1267,621,1096,568,919,562,745,571,553,646,354,766,237,904,204,1080 zones: backyard: coordinates: 190,132,0,464,0,1080,137,1080,263,797,510,629,750,562,1025,535,1309,577,1643,1015,1840,906,1623,575,1570,441,1607,335,1531,243,1556,117,1429,86,764,137,216,222 objects: track: - person - dog - cat uvc_cam4: detect: enabled: true width: 1920 height: 1080 fps: 5 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 objects: person: 30 ffmpeg: inputs: - path: rtsp://xxxxxxxx roles: - detect - rtmp motion: mask: - 0,83,350,86,348,0,0,0 zones: sidegate: coordinates: 720,1080,1169,1080,854,240,728,137,631,147,644,257 objects: track: - person - dog - cat uvc_cam5: detect: enabled: true width: 1920 height: 1080 fps: 5 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 objects: person: 30 ffmpeg: inputs: - path: rtsp://xxxxxxxxx roles: - detect - rtmp motion: mask: - 0,83,350,86,348,0,0,0 zones: sidefence: coordinates: 609,1080,1337,1080,741,309,567,287 objects: track: - person - dog - cat record: enabled: true retain_days: 0 events: max_seconds: 300 pre_capture: 2 post_capture: 2 retain: default: 10 objects: track: - person - car - dog - cat ffmpeg: hwaccel_args: - -c:v - h264_cuvid detectors: coral: type: edgetpu device: usb On your config you have record enables but you are not using it on the roles of any of the cameras 1 Quote Link to comment
Snakesms Posted October 7, 2021 Share Posted October 7, 2021 (edited) 8 hours ago, yayitazale said: This is not needed If you don't have changed the Database from the original location. I didn't change anything at all in the original template, but as you can see its failing. I can confirm that the real database location is here: /media/frigate/clips/frigate.db and '/media/frigate/frigate.db' does not exist Edited October 7, 2021 by Snakesms Quote Link to comment
yayitazale Posted October 7, 2021 Author Share Posted October 7, 2021 2 minutes ago, Snakesms said: I didn't change anything at all in the original template, but as you can see its failing You are using a old template, the error comes because you have separate folder mappings for clips and recordings media. You have to remove the container and use the new template just installing the app again. The only mapping you need for media is "/media/frigate" This a the same issue reported on github: https://github.com/blakeblackshear/frigate/issues/1936 As you can see on the template the only mapping for media is "/media/frigate": https://github.com/yayitazale/unraid-templates/blob/main/yayitazale/frigate-amd64.xml Quote Link to comment
Snakesms Posted October 7, 2021 Share Posted October 7, 2021 10 hours ago, nau said: i've added this to config and it started sucessfully database: path: /media/frigate/clips/frigate.db Thank you, it helps me as well Quote Link to comment
Snakesms Posted October 7, 2021 Share Posted October 7, 2021 3 minutes ago, yayitazale said: You are using a old template, the error comes because you have separate folder mappings for clips and recordings media. You have to remove the container and use the new template just installing the app again. The only mapping you need for media is "/media/frigate" This a the same issue reported on github: https://github.com/blakeblackshear/frigate/issues/1936 As you can see on the template the only mapping for media is "/media/frigate": https://github.com/yayitazale/unraid-templates/blob/main/yayitazale/frigate-amd64.xml Thank you, will try to update template, I didn't know there is new version exist Quote Link to comment
yayitazale Posted October 7, 2021 Author Share Posted October 7, 2021 (edited) 32 minutes ago, Snakesms said: Thank you, will try to update template, I didn't know there is new version exist I try to change the template as little as possible, but this project is growing and some changes are needed. Unraid does not alert the user about template changes so there is no way to notify the users to delete and reinstall the containers. Edited October 7, 2021 by yayitazale Quote Link to comment
bigbangus Posted October 7, 2021 Share Posted October 7, 2021 2 hours ago, yayitazale said: On your config you have record enables but you are not using it on the roles of any of the cameras Ah thank you. Another case of RTFM. # Required: list of roles for this stream. valid values are: detect,record,rtmp # NOTICE: In addition to assigning the record, and rtmp roles, # they must also be enabled in the camera config. 1 Quote Link to comment
DanielWWS Posted October 8, 2021 Share Posted October 8, 2021 using unraid and seem to be getting a constant error popping up at every detection: Quote [2021-10-08 17:34:31] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... [2021-10-08 17:34:31] root INFO : Waiting for detection process to exit gracefully... [2021-10-08 17:34:31] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... [2021-10-08 17:34:31] root INFO : Waiting for detection process to exit gracefully... [2021-10-08 17:35:01] root INFO : Detection process didnt exit. Force killing... [2021-10-08 17:35:01] detector.coral1 INFO : Starting detection process: 476 [2021-10-08 17:35:01] frigate.edgetpu INFO : Attempting to load TPU as usb:0 [2021-10-08 17:35:04] frigate.edgetpu INFO : TPU found [2021-10-08 17:35:01] frigate.edgetpu INFO : Attempting to load TPU as usb:0 [2021-10-08 17:35:04] frigate.edgetpu INFO : TPU found [2021-10-08 17:35:41] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... [2021-10-08 17:35:41] root INFO : Waiting for detection process to exit gracefully... ## the start up process looks okay to me but im a novice. below log from start up ## Quote [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-10-08 17:42:09] frigate.app INFO : Starting Frigate (0.9.1-800f33e) Starting migrations [2021-10-08 17:42:09] peewee_migrate INFO : Starting migrations There is nothing to migrate [2021-10-08 17:42:09] peewee_migrate INFO : There is nothing to migrate [2021-10-08 17:42:09] detector.coral1 INFO : Starting detection process: 233 [2021-10-08 17:42:09] detector.coral2 INFO : Starting detection process: 235 [2021-10-08 17:42:09] frigate.app INFO : Output process started: 236 [2021-10-08 17:42:09] ws4py INFO : Using epoll [2021-10-08 17:42:09] frigate.edgetpu INFO : Attempting to load TPU as usb:0 [2021-10-08 17:42:09] frigate.edgetpu INFO : Attempting to load TPU as usb:1 [2021-10-08 17:42:09] frigate.app INFO : Camera processor started for back: 243 [2021-10-08 17:42:12] frigate.edgetpu INFO : TPU found [2021-10-08 17:42:13] frigate.edgetpu INFO : TPU found [2021-10-08 17:42:09] frigate.app INFO : Camera processor started for front: 245 [2021-10-08 17:42:09] frigate.app INFO : Camera processor started for side: 247 [2021-10-08 17:42:09] frigate.mqtt INFO : MQTT connected [2021-10-08 17:42:09] frigate.app INFO : Camera processor started for gate: 268 [2021-10-08 17:42:09] frigate.app INFO : Capture process started for back: 270 [2021-10-08 17:42:09] frigate.app INFO : Capture process started for front: 271 [2021-10-08 17:42:09] frigate.app INFO : Capture process started for side: 276 [2021-10-08 17:42:09] frigate.app INFO : Capture process started for gate: 286 [2021-10-08 17:42:09] ws4py INFO : Using epoll this is my config.yml file: Quote mqtt: host: 192.168.1.208 user: xxxx password: xxxx detectors: coral1: type: edgetpu device: usb:0 coral2: type: edgetpu device: usb:1 cameras: back: ffmpeg: inputs: - path: rtsp://admin:xxxx@@192.168.1.108:554/cam/realmonitor?channel=3&subtype=1 roles: - detect - rtmp - path: rtsp://admin:xxxx@@192.168.1.108:554/cam/realmonitor?channel=3&subtype=0 roles: - record detect: width: 704 height: 480 fps: 5 motion: mask: - 163,262,331,140,569,271,604,167,704,160,704,0,486,0,0,0,0,274 objects: track: - person - cat - dog record: enabled: true retain_days: 2 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 mqtt: enabled: true timestamp: true bounding_box: true objects: track: - person - cat - dog front: ffmpeg: inputs: - path: rtsp://admin:xxxx@@192.168.1.108:554/cam/realmonitor?channel=2&subtype=1 roles: - detect - rtmp - path: rtsp://admin:xxxx@@192.168.1.108:554/cam/realmonitor?channel=2&subtype=0 roles: - record detect: width: 704 height: 480 fps: 5 motion: mask: - 138,63,146,147,329,163,557,173,704,163,704,0,486,0,0,0,0,73 objects: track: - person - cat - dog record: enabled: true retain_days: 2 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 mqtt: enabled: true timestamp: true bounding_box: true objects: track: - person - cat - dog side: ffmpeg: inputs: - path: rtsp://admin:xxxx@@192.168.1.108:554/cam/realmonitor?channel=1&subtype=0 roles: - detect - rtmp - path: rtsp://admin:xxxx@@192.168.1.108:554/cam/realmonitor?channel=1&subtype=0 roles: - record detect: width: 2688 height: 1520 fps: 5 motion: mask: - 0,198,0,166,85,168,89,196 objects: track: - person - cat - dog record: enabled: true retain_days: 2 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 mqtt: enabled: true timestamp: true bounding_box: true objects: track: - person - cat - dog gate: ffmpeg: inputs: - path: rtsp://admin:xxxx@@192.168.1.108:554/cam/realmonitor?channel=5&subtype=0 roles: - detect - rtmp - path: rtsp://admin:xxxx@@192.168.1.108:554/cam/realmonitor?channel=5&subtype=0 roles: - record detect: width: 1280 height: 720 fps: 5 motion: mask: - 377,287,771,354,839,407,881,406,1280,521,1280,0,704,0,486,0,0,0,0,274 objects: track: - person - cat - dog - car record: enabled: true retain_days: 2 rtmp: enabled: true snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 mqtt: enabled: true timestamp: true bounding_box: true objects: track: - person - cat - dog - car Ive installed the coral drivers but the TPU's are USB's and ive tried just one or the other and we get the same results. Its when a detection happens this starts. The usb's are both in USB3 ports and its got 32gb ddr3 memory // [email protected] processor and ive built this machine pretty much just to test and run this (from old parts but its all good.) Version: DEBUG 0.9.1-800F33E coral1 = inference speed - 10 coral2 = inference speed - 29.9 Does anyone have any ideas how to stop this reoccuring error? can it be added for someone to look into dealing with it if its a bug in unraid? Quote Link to comment
Recommended Posts
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.