only-university6482 Posted March 19 Share Posted March 19 (edited) 7 minutes ago, awediohead said: I do not have Portainer installed - in fact I had no idea you could install Portainer on Unraid ! While I will investigate Portainer further in future, but just now it seems like another steep learning curve when I'm already a bit overwhelmed with variables - and Frigate should work without Portainer right? I found this Reddit thread helpful as my three cameras are all Reolink - though I only have one wired up and installed right now. Here's my error logs: 2024-03-19 13:52:52.409885798 [INFO] Preparing Frigate... 2024-03-19 13:52:52.420791575 [INFO] Starting Frigate... 2024-03-19 13:52:53.723144268 [2024-03-19 13:52:53] frigate.app INFO : Starting Frigate (0.13.2-6476f8a) 2024-03-19 13:52:53.754498105 [2024-03-19 13:52:53] peewee_migrate.logs INFO : Starting migrations 2024-03-19 13:52:53.761128965 [2024-03-19 13:52:53] peewee_migrate.logs INFO : There is nothing to migrate 2024-03-19 13:52:53.767830216 [2024-03-19 13:52:53] frigate.app INFO : Recording process started: 584 2024-03-19 13:52:53.770085464 [2024-03-19 13:52:53] frigate.app INFO : go2rtc process pid: 89 2024-03-19 13:52:53.793262819 [2024-03-19 13:52:53] frigate.app INFO : Output process started: 595 2024-03-19 13:52:53.804977095 [2024-03-19 13:52:53] frigate.app INFO : Camera processor started for e1frontdoor: 603 2024-03-19 13:52:53.812644825 [2024-03-19 13:52:53] frigate.app INFO : Capture process started for e1frontdoor: 605 2024-03-19 13:52:53.836449259 [2024-03-19 13:52:53] frigate.video ERROR : e1frontdoor: Unable to read frames from ffmpeg process. 2024-03-19 13:52:53.836532504 [2024-03-19 13:52:53] frigate.video ERROR : e1frontdoor: ffmpeg process is not running. exiting capture thread... 2024-03-19 13:52:56.409451884 [2024-03-19 13:52:53] detector.coral INFO : Starting detection process: 593 2024-03-19 13:52:56.413665756 [2024-03-19 13:52:53] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-19 13:52:56.413962714 [2024-03-19 13:52:56] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-03-19 13:53:13.842880802 [2024-03-19 13:53:13] watchdog.e1frontdoor ERROR : Ffmpeg process crashed unexpectedly for e1frontdoor. 2024-03-19 13:53:13.843266663 [2024-03-19 13:53:13] watchdog.e1frontdoor ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-03-19 13:53:13.843625848 [2024-03-19 13:53:13] ffmpeg.e1frontdoor.detect ERROR : DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument 2024-03-19 13:53:13.843850708 [2024-03-19 13:53:13] ffmpeg.e1frontdoor.detect ERROR : Assuming 131072kB available aperture size. 2024-03-19 13:53:13.844088541 [2024-03-19 13:53:13] ffmpeg.e1frontdoor.detect ERROR : May lead to reduced performance or incorrect rendering. 2024-03-19 13:53:13.844255022 [2024-03-19 13:53:13] ffmpeg.e1frontdoor.detect ERROR : get chip id failed: -1 [22] 2024-03-19 13:53:13.844452915 [2024-03-19 13:53:13] ffmpeg.e1frontdoor.detect ERROR : param: 4, val: 0 2024-03-19 13:53:13.844676862 [2024-03-19 13:53:13] ffmpeg.e1frontdoor.detect ERROR : [AVHWDeviceContext @ 0x560671d1d540] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed 2024-03-19 13:53:13.844904200 [2024-03-19 13:53:13] ffmpeg.e1frontdoor.detect ERROR : [AVHWDeviceContext @ 0x560671d1d540] Failed to initialise VAAPI connection: 18 (invalid parameter). 2024-03-19 13:53:13.845005861 [2024-03-19 13:53:13] ffmpeg.e1frontdoor.detect ERROR : Device creation failed: -5. 2024-03-19 13:53:13.845178704 [2024-03-19 13:53:13] ffmpeg.e1frontdoor.detect ERROR : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Input/output error 2024-03-19 13:53:13.845337806 [2024-03-19 13:53:13] ffmpeg.e1frontdoor.detect ERROR : Error parsing global options: Input/output error 2024-03-19 13:53:13.864092082 [2024-03-19 13:53:13] frigate.video ERROR : e1frontdoor: Unable to read frames from ffmpeg process. 2024-03-19 13:53:13.864222820 [2024-03-19 13:53:13] frigate.video ERROR : e1frontdoor: ffmpeg process is not running. exiting capture thread... and here's my config.yml mqtt: enabled: False detectors: coral: type: edgetpu device: usb ffmpeg: hwaccel_args: preset-intel-qsv-h264 input_args: preset-rtsp-restream output_args: record: preset-record-generic-audio-copy go2rtc: streams: e1frontdoor: - rtsp://admin:<password>@10.0.44.101:554/h264Preview_01_main e1frontdoor_sub: - rtsp://admin:<password>@10.0.44.101:554/h264Preview_01_sub #oldcam: # - rtsp://<username>:<password>@<camera_ip>:554/h264Preview_01_main #oldcam_sub: #- rtsp://<username>:<password>@<camera_ip>:554/h264Preview_01_sub cameras: e1frontdoor: enabled: true ffmpeg: inputs: - path: rtsp://10.0.44.2:8554/e1frontdoor hwaccel_args: preset-intel-qsv-h264 roles: - record - path: rtsp://10.0.44.2:8554/e1frontdoor_sub roles: - detect detect: width: 640 height: 360 fps: 7 objects: track: - person I've tried substituing VAAPI for QSV and the generic vs restream for hwaccel and input arguments respectively. I also tried changing the iHD to i965 without any benefit. Hope someone can see what I'm doing wrong? Thanks Portainer is not needed as it's just a nice gui to access the containers. Just handy as it's user friendly. This is all I have in my config. I do not have any ffmpeg configs before go2rtc. At the camera level all I have in regards to ffmpeg is: ffmpeg: hwaccel_args: preset-vaapi anything else I added to this broke it Edited March 19 by only-university6482 1 Quote Link to comment
awediohead Posted March 19 Share Posted March 19 1 hour ago, only-university6482 said: Portainer is not needed as it's just a nice gui to access the containers. Just handy as it's user friendly. This is all I have in my config. I do not have any ffmpeg configs before go2rtc. At the camera level all I have in regards to ffmpeg is: ffmpeg: hwaccel_args: preset-vaapi anything else I added to this broke it So are you saying that - at the camera level - where I have (since just changing back to preset-vaapi) cameras: e1frontdoor: enabled: true ffmpeg: inputs: - path: rtsp://10.0.44.2:8554/e1frontdoor hwaccel_args: preset-vaapi roles: - record - path: rtsp://10.0.44.2:8554/e1frontdoor_sub roles: - detect detect: width: 640 height: 360 fps: 7 objects: track: - person you just have cameras: e1frontdoor: enabled: true ffmpeg: hwaccel_args: preset-vaapi detect: width: 640 height: 360 fps: 7 objects: track: - person or even less than this? Thanks a million 1 Quote Link to comment
only-university6482 Posted March 19 Share Posted March 19 (edited) 5 minutes ago, awediohead said: So are you saying that - at the camera level - where I have (since just changing back to preset-vaapi) cameras: e1frontdoor: enabled: true ffmpeg: inputs: - path: rtsp://10.0.44.2:8554/e1frontdoor hwaccel_args: preset-vaapi roles: - record - path: rtsp://10.0.44.2:8554/e1frontdoor_sub roles: - detect detect: width: 640 height: 360 fps: 7 objects: track: - person you just have cameras: e1frontdoor: enabled: true ffmpeg: hwaccel_args: preset-vaapi detect: width: 640 height: 360 fps: 7 objects: track: - person or even less than this? Thanks a million Just got this: cameras: gate: enabled: true ffmpeg: hwaccel_args: preset-vaapi inputs: - path: rtsp://127.0.0.1:8554/gate_sub?video=copy input_args: preset-rtsp-restream roles: - detect - record - rtmp detect: width: 704 height: 480 fps: 5 objects: track: - person .... Edited March 19 by only-university6482 Quote Link to comment
snowy00 Posted March 22 Share Posted March 22 (edited) Hi, I have those error messages mostly at night in my frigate los. Is that a configuration issue or it results due to unstable stream? Error 2024-03-22 01:50:27.305718991 [2024-03-22 01:50:27] ffmpeg.doorbird.detect ERROR : Last message repeated 1 times 2024-03-22 01:50:32.425703756 [2024-03-22 01:50:32] frigate.video ERROR : doorbird: Unable to read frames from ffmpeg process. 2024-03-22 01:50:32.425705908 [2024-03-22 01:50:32] frigate.video ERROR : doorbird: ffmpeg process is not running. exiting capture thread... 2024-03-22 01:50:37.319557649 [2024-03-22 01:50:37] watchdog.doorbird ERROR : Ffmpeg process crashed unexpectedly for doorbird. 2024-03-22 01:50:37.319567635 [2024-03-22 01:50:37] watchdog.doorbird ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-03-22 01:50:37.319611590 [2024-03-22 01:50:37] ffmpeg.doorbird.detect ERROR : rtsp://127.0.0.1:8554/doorbird: Invalid data found when processing input 2024-03-22 01:50:40.358113961 [2024-03-22 01:50:40] frigate.video ERROR : doorbird: Unable to read frames from ffmpeg process. 2024-03-22 01:50:40.358220082 [2024-03-22 01:50:40] frigate.video ERROR : doorbird: ffmpeg process is not running. exiting capture thread... 2024-03-22 01:50:47.325184697 [2024-03-22 01:50:47] watchdog.doorbird ERROR : Ffmpeg process crashed unexpectedly for doorbird. 2024-03-22 01:50:47.325202542 [2024-03-22 01:50:47] watchdog.doorbird ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-03-22 01:50:47.325211543 [2024-03-22 01:50:47] ffmpeg.doorbird.detect ERROR : [rtsp @ 0x5586f00bd100] method DESCRIBE failed: 404 Not Found 2024-03-22 01:50:47.325331886 [2024-03-22 01:50:47] ffmpeg.doorbird.detect ERROR : rtsp://127.0.0.1:8554/doorbird: Server returned 404 Not Found 2024-03-22 07:38:37.857388889 [2024-03-22 07:38:37] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 07:38:37.857399654 [2024-03-22 07:38:37] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 07:39:07.887486615 [2024-03-22 07:39:07] root INFO : Detection process didnt exit. Force killing... 2024-03-22 07:39:07.890948093 [2024-03-22 07:39:07] root INFO : Detection process has exited... 2024-03-22 07:39:07.901002708 [2024-03-22 07:39:07] detector.coral INFO : Starting detection process: 23549 2024-03-22 07:39:07.908221679 [2024-03-22 07:39:07] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 07:39:10.726405811 [2024-03-22 07:39:10] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-03-22 09:06:47.964609337 [2024-03-22 09:06:47] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 09:06:47.964611572 [2024-03-22 09:06:47] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 09:07:17.994352506 [2024-03-22 09:07:17] root INFO : Detection process didnt exit. Force killing... 2024-03-22 09:07:18.002138068 [2024-03-22 09:07:18] root INFO : Detection process has exited... 2024-03-22 09:07:18.012648975 [2024-03-22 09:07:18] detector.coral INFO : Starting detection process: 6156 2024-03-22 09:07:20.620061572 [2024-03-22 09:07:18] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 09:07:20.622411381 [2024-03-22 09:07:20] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-03-22 11:20:48.104918569 [2024-03-22 11:20:48] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 11:20:48.104946957 [2024-03-22 11:20:48] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 11:21:18.115158164 [2024-03-22 11:21:18] root INFO : Detection process didnt exit. Force killing... 2024-03-22 11:21:18.121643469 [2024-03-22 11:21:18] root INFO : Detection process has exited... 2024-03-22 11:21:18.132285625 [2024-03-22 11:21:18] detector.coral INFO : Starting detection process: 28132 2024-03-22 11:21:20.740620712 [2024-03-22 11:21:18] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 11:21:20.742499265 [2024-03-22 11:21:20] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found frigate config: mqtt: enabled: true host: 192.168.178.32 user: *************** password: ****************** topic_prefix: frigate birdseye: enabled: False detectors: coral: type: edgetpu device: usb objects: track: - person - car - cat - dog - motorcycle - bicycle - umbrella filters: person: min_area: 5000 max_area: 24000000 go2rtc: streams: # doorbird: # - rtsp://******:**********@192.168.178.125:554/mpeg/media.amp doorbird: - rtsp://************:***********@192.168.178.125:554/mpeg/1080p/media.amp cameras: doorbird: enabled: true ffmpeg: hwaccel_args: preset-vaapi output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/doorbird input_args: preset-rtsp-restream roles: - detect - record detect: enabled: true width: 1920 height: 1080 stationary: interval: 50 threshold: 50 max_frames: objects: car: 1000 record: enabled: true retain: days: 5 mode: all events: required_zones: - zone_hof - zone_street retain: default: 15 snapshots: enabled: true required_zones: - zone_hof - zone_street retain: default: 20 zones: zone_hof: coordinates: 1920,1080,1920,744,1764,737,1664,778,751,833,269,783,0,834,0,1080 objects: - person - car - cat - dog - motorcycle - bicycle - umbrella filters: car: threshold: 0.75 zone_street: coordinates: 574,833,1331,804,1863,684,1863,598,210,603,213,748,281,780 objects: - person motion: mask: - 0,0,299,786,0,843 - 0,0,1920,0,1920,427,1920,613,1256,614,211,578 I also see those messages in the unraid log, that the coral sometimes connected and disconnected from the usb port. Is there any connection between the errors? Mar 22 07:39:09 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 07:39:09 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Mar 22 08:15:06 Tower emhttpd: read SMART /dev/sdc Mar 22 08:37:31 Tower emhttpd: spinning down /dev/sdc Mar 22 09:07:19 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 09:07:19 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Mar 22 09:20:06 Tower emhttpd: read SMART /dev/sdc Mar 22 09:42:28 Tower emhttpd: spinning down /dev/sdc Mar 22 10:25:07 Tower emhttpd: read SMART /dev/sdc Mar 22 10:47:25 Tower emhttpd: spinning down /dev/sdc Mar 22 11:21:19 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 11:21:19 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Edited March 22 by snowy00 Quote Link to comment
awediohead Posted March 22 Share Posted March 22 So I've literally spent days on this and I'm going slightly mad. I'd really appreciate some help as I'm just going round in circles. I have a single 4K Reolink E1 Outdoor PoE camera installed for now. With two Reolink 520A cameras waiting to be installed. I can get VLC to show a nice clear image via: rtsp://admin:[email protected]:8554/h264Preview_01_main this also works as: rtsp://admin:[email protected]:8554/h265Preview_01_main (where obviously I'm substituting 'PASSWORD' for the actual password - which does not have any special characters!) but the same URL entered into Frigate just generates a series of errors: In the Log files I get things like: 2024-03-22 11:27:25.320784970 [rtsp @ 0x24c9e40] method DESCRIBE failed: 404 Not Found ERROR : e1frontdoor: Unable to read frames from ffmpeg process. 2024-03-22 11:27:25.426632987 [2024-03-22 11:27:25] frigate.video ERROR : e1frontdoor: ffmpeg process is not running. exiting capture thread... ERROR : Ffmpeg process crashed unexpectedly for e1frontdoor In the VAINFO section I get: VAINFO OUTPUT Return Code: 3 Process Error: error: XDG_RUNTIME_DIR is invalid or not set in the environment. error: can't connect to X server! libva info: VA-API version 1.17.0 libva info: User environment variable requested driver 'iHD' libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 18 vaInitialize failed with error code 18 (invalid parameter),exit Changing from iHD to i965 makes no difference I've started from scratch so many times now I think there's something even more fundamental going on. I'd really appreciate some help figuring out what that is? My current hardware is a z490 +i510400 CPU so the onboard iGPU should be working in parallel with the USB Coral I have - which is at least being recognised in both Unraid and the Frigate logs. Hope someone can help. Thanks Quote Link to comment
awediohead Posted March 23 Share Posted March 23 Update: Turns out my BIOS had somehow reset the GPU aspect of itself (or didn't retain settings) such that the Intel iGPU wasn't working, while the Nvidia 1050 was, though only for transcoding in Plex. So as soon as I added the hwaccel_args (any type) Frigate crashed because it was trying to find something that wasn't there. And obviously iHD or i965 weren't going to make any difference either! At least now I can plough through the Frigate docs in a somewhat meaningful way. Are there any extra parameters I should be adding above and beyond the defaults for the 10400's iGPU? Quote Link to comment
yayitazale Posted March 23 Author Share Posted March 23 2 hours ago, awediohead said: Update: Turns out my BIOS had somehow reset the GPU aspect of itself (or didn't retain settings) such that the Intel iGPU wasn't working, while the Nvidia 1050 was, though only for transcoding in Plex. So as soon as I added the hwaccel_args (any type) Frigate crashed because it was trying to find something that wasn't there. And obviously iHD or i965 weren't going to make any difference either! At least now I can plough through the Frigate docs in a somewhat meaningful way. Are there any extra parameters I should be adding above and beyond the defaults for the 10400's iGPU? You should check https://docs.frigate.video/configuration/camera_specific/#reolink-cameras Quote Link to comment
yayitazale Posted March 23 Author Share Posted March 23 On 3/22/2024 at 12:47 PM, snowy00 said: Hi, I have those error messages mostly at night in my frigate los. Is that a configuration issue or it results due to unstable stream? Error 2024-03-22 01:50:27.305718991 [2024-03-22 01:50:27] ffmpeg.doorbird.detect ERROR : Last message repeated 1 times 2024-03-22 01:50:32.425703756 [2024-03-22 01:50:32] frigate.video ERROR : doorbird: Unable to read frames from ffmpeg process. 2024-03-22 01:50:32.425705908 [2024-03-22 01:50:32] frigate.video ERROR : doorbird: ffmpeg process is not running. exiting capture thread... 2024-03-22 01:50:37.319557649 [2024-03-22 01:50:37] watchdog.doorbird ERROR : Ffmpeg process crashed unexpectedly for doorbird. 2024-03-22 01:50:37.319567635 [2024-03-22 01:50:37] watchdog.doorbird ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-03-22 01:50:37.319611590 [2024-03-22 01:50:37] ffmpeg.doorbird.detect ERROR : rtsp://127.0.0.1:8554/doorbird: Invalid data found when processing input 2024-03-22 01:50:40.358113961 [2024-03-22 01:50:40] frigate.video ERROR : doorbird: Unable to read frames from ffmpeg process. 2024-03-22 01:50:40.358220082 [2024-03-22 01:50:40] frigate.video ERROR : doorbird: ffmpeg process is not running. exiting capture thread... 2024-03-22 01:50:47.325184697 [2024-03-22 01:50:47] watchdog.doorbird ERROR : Ffmpeg process crashed unexpectedly for doorbird. 2024-03-22 01:50:47.325202542 [2024-03-22 01:50:47] watchdog.doorbird ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-03-22 01:50:47.325211543 [2024-03-22 01:50:47] ffmpeg.doorbird.detect ERROR : [rtsp @ 0x5586f00bd100] method DESCRIBE failed: 404 Not Found 2024-03-22 01:50:47.325331886 [2024-03-22 01:50:47] ffmpeg.doorbird.detect ERROR : rtsp://127.0.0.1:8554/doorbird: Server returned 404 Not Found 2024-03-22 07:38:37.857388889 [2024-03-22 07:38:37] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 07:38:37.857399654 [2024-03-22 07:38:37] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 07:39:07.887486615 [2024-03-22 07:39:07] root INFO : Detection process didnt exit. Force killing... 2024-03-22 07:39:07.890948093 [2024-03-22 07:39:07] root INFO : Detection process has exited... 2024-03-22 07:39:07.901002708 [2024-03-22 07:39:07] detector.coral INFO : Starting detection process: 23549 2024-03-22 07:39:07.908221679 [2024-03-22 07:39:07] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 07:39:10.726405811 [2024-03-22 07:39:10] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-03-22 09:06:47.964609337 [2024-03-22 09:06:47] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 09:06:47.964611572 [2024-03-22 09:06:47] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 09:07:17.994352506 [2024-03-22 09:07:17] root INFO : Detection process didnt exit. Force killing... 2024-03-22 09:07:18.002138068 [2024-03-22 09:07:18] root INFO : Detection process has exited... 2024-03-22 09:07:18.012648975 [2024-03-22 09:07:18] detector.coral INFO : Starting detection process: 6156 2024-03-22 09:07:20.620061572 [2024-03-22 09:07:18] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 09:07:20.622411381 [2024-03-22 09:07:20] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-03-22 11:20:48.104918569 [2024-03-22 11:20:48] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 11:20:48.104946957 [2024-03-22 11:20:48] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 11:21:18.115158164 [2024-03-22 11:21:18] root INFO : Detection process didnt exit. Force killing... 2024-03-22 11:21:18.121643469 [2024-03-22 11:21:18] root INFO : Detection process has exited... 2024-03-22 11:21:18.132285625 [2024-03-22 11:21:18] detector.coral INFO : Starting detection process: 28132 2024-03-22 11:21:20.740620712 [2024-03-22 11:21:18] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 11:21:20.742499265 [2024-03-22 11:21:20] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found frigate config: mqtt: enabled: true host: 192.168.178.32 user: *************** password: ****************** topic_prefix: frigate birdseye: enabled: False detectors: coral: type: edgetpu device: usb objects: track: - person - car - cat - dog - motorcycle - bicycle - umbrella filters: person: min_area: 5000 max_area: 24000000 go2rtc: streams: # doorbird: # - rtsp://******:**********@192.168.178.125:554/mpeg/media.amp doorbird: - rtsp://************:***********@192.168.178.125:554/mpeg/1080p/media.amp cameras: doorbird: enabled: true ffmpeg: hwaccel_args: preset-vaapi output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/doorbird input_args: preset-rtsp-restream roles: - detect - record detect: enabled: true width: 1920 height: 1080 stationary: interval: 50 threshold: 50 max_frames: objects: car: 1000 record: enabled: true retain: days: 5 mode: all events: required_zones: - zone_hof - zone_street retain: default: 15 snapshots: enabled: true required_zones: - zone_hof - zone_street retain: default: 20 zones: zone_hof: coordinates: 1920,1080,1920,744,1764,737,1664,778,751,833,269,783,0,834,0,1080 objects: - person - car - cat - dog - motorcycle - bicycle - umbrella filters: car: threshold: 0.75 zone_street: coordinates: 574,833,1331,804,1863,684,1863,598,210,603,213,748,281,780 objects: - person motion: mask: - 0,0,299,786,0,843 - 0,0,1920,0,1920,427,1920,613,1256,614,211,578 I also see those messages in the unraid log, that the coral sometimes connected and disconnected from the usb port. Is there any connection between the errors? Mar 22 07:39:09 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 07:39:09 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Mar 22 08:15:06 Tower emhttpd: read SMART /dev/sdc Mar 22 08:37:31 Tower emhttpd: spinning down /dev/sdc Mar 22 09:07:19 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 09:07:19 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Mar 22 09:20:06 Tower emhttpd: read SMART /dev/sdc Mar 22 09:42:28 Tower emhttpd: spinning down /dev/sdc Mar 22 10:25:07 Tower emhttpd: read SMART /dev/sdc Mar 22 10:47:25 Tower emhttpd: spinning down /dev/sdc Mar 22 11:21:19 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 11:21:19 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Not sure but looks like normal for me, I sometimes have some stability issues for the streams. 1 Quote Link to comment
awediohead Posted March 23 Share Posted March 23 40 minutes ago, yayitazale said: You should check https://docs.frigate.video/configuration/camera_specific/#reolink-cameras Oh I have - dozens of times by now! The problem is that states: Quote caution The below configuration only works for reolink cameras with stream resolution of 5MP or lower, 8MP+ cameras need to use RTSP as http-flv is not supported in this case. As the camera I need to get working is 4K the example given is pretty much useless and I've had to search elsewhere for answers. Still, I'm getting gradually more familiar with the terminology and broad principles - but as many others have said, the Frigate documentation assumes a hell of a lot of knowledge. Even so with a working iGPU at least I can trial and error the process and make a little progress. If the built in .config editor wasn't checking syntax I'd have given up long ago. Quote Link to comment
yayitazale Posted March 23 Author Share Posted March 23 9 minutes ago, awediohead said: Oh I have - dozens of times by now! The problem is that states: As the camera I need to get working is 4K the example given is pretty much useless and I've had to search elsewhere for answers. Still, I'm getting gradually more familiar with the terminology and broad principles - but as many others have said, the Frigate documentation assumes a hell of a lot of knowledge. Even so with a working iGPU at least I can trial and error the process and make a little progress. If the built in .config editor wasn't checking syntax I'd have given up long ago. So then you should use rstp as you are using. Yes the docs are complex among other things because of its wide compatibility with many different systems. It is not a product, it is a free software project and believe me they have made and continue to make a great effort to simplify things. In any case, you can always contribute your grain of sand proposing improvements or changes in the documentation. 1 Quote Link to comment
BrandonG777 Posted March 24 Share Posted March 24 So turns out my server locks up were not tied to the USB Coral device I was trying to use but rather out of memory issues that seem to be related to the ffmpeg process. Not sure where I've gone wrong, it works for days/weeks and then at the most inconvenient times it hard locks. mqtt: host: 10.0.0.3 port: 1883 topic_prefix: frigate client_id: frigate user: frigate password: **CENSORED** stats_interval: 60 ffmpeg: hwaccel_args: preset-nvidia-h264 detectors: cuda: type: tensorrt model: path: /config/model_cache/tensorrt/yolov4-tiny-416.trt labelmap_path: /labelmap.txt input_tensor: nchw width: 416 height: 416 record: enabled: true retain: days: 7 mode: motion events: retain: default: 5 mode: active_objects pre_capture: 3 post_capture: 10 snapshots: enabled: true retain: default: 30 timestamp: true bounding_box: true birdseye: enabled: false restream: true width: 1280 height: 720 quality: 8 mode: motion go2rtc: streams: driveway: - rtsp://frigate:**CENSORED**@10.0.0.8:554/cam/realmonitor?channel=1&subtype=0 driveway_sub: - rtsp://frigate:**CENSORED**@10.0.0.8:554/cam/realmonitor?channel=1&subtype=2 front: - rtsp://frigate:**CENSORED**@10.0.0.6:554/cam/realmonitor?channel=1&subtype=0 front_sub: - rtsp://frigate:**CENSORED**@10.0.0.6:554/cam/realmonitor?channel=1&subtype=2 front_door: - rtsp://frigate:**CENSORED**@10.0.0.5:554/cam/realmonitor?channel=2&subtype=0 garage: - rtsp://frigate:**CENSORED**@10.0.0.7:554/cam/realmonitor?channel=1&subtype=0 garage_sub: - rtsp://frigate:**CENSORED**@10.0.0.7:554/cam/realmonitor?channel=1&subtype=2 livingroom: - rtsp://homeassistant:**CENSORED**@10.0.0.9:554/cam/realmonitor?channel=1&subtype=0 north_deck: - rtsp://frigate:**CENSORED**@10.0.0.5:554/cam/realmonitor?channel=4&subtype=0 south_deck: - rtsp://frigate:**CENSORED**@10.0.0.5:554/cam/realmonitor?channel=3&subtype=0 cameras: driveway: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/driveway_sub roles: - detect - path: rtsp://127.0.0.1:8554/driveway roles: - audio - record detect: width: 1280 height: 720 fps: 5 objects: track: - person - bicycle - car - cat - dog filters: car: mask: - 1280,0,1280,440,992,296,569,331,708,720,0,720,0,0 birdseye: mode: continuous zones: driveway_top: coordinates: 687,720,561,321,955,294,1280,481,1259,528,1160,720 motion: mask: - 1243,659,1243,701,831,699,831,663 front: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/front_sub roles: - detect - path: rtsp://127.0.0.1:8554/front roles: - audio - record detect: width: 1280 height: 720 fps: 5 motion: mask: - 1243,659,1243,701,831,699,831,663 objects: track: - person - bicycle - cat - dog filters: person: mask: - 728,720,931,720,887,615,746,469,632,499 zones: driveway_top: coordinates: 238,227,580,161,463,148,218,194 front_lawn: coordinates: 364,255,256,290,745,511,925,720,1280,720,1280,345,1112,276,844,194,637,145,564,165,355,210,312,227 front_patio: coordinates: 0,720,894,720,747,507,233,305,0,412 front_porch: coordinates: 0,407,344,253,231,254,195,105,0,178 birdseye: mode: continuous front_door: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/front_door roles: - detect - record detect: width: 960 height: 480 fps: 5 objects: track: - person - cat - dog zones: front_lawn: coordinates: 588,144,734,221,795,0,351,0,365,44,506,50 front_porch: coordinates: 223,480,960,480,960,160,743,202,588,138,541,81,291,70 motion: mask: - 377,16,383,53,16,45,17,17 garage: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/garage_sub roles: - detect - path: rtsp://127.0.0.1:8554/garage roles: - audio - record detect: width: 1280 height: 720 fps: 5 objects: track: - person - bicycle - car - cat - dog zones: garage_floor: coordinates: 21,263,182,619,428,673,463,720,1280,720,1280,216,967,21,437,26 objects: - person - bicycle - car - cat - dog birdseye: mode: continuous motion: mask: - 430,13,432,44,12,45,12,8 north_deck: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/north_deck roles: - detect - record detect: width: 1280 height: 720 fps: 5 objects: track: - person - cat - dog motion: mask: - 1188,22,1188,55,825,53,828,27 south_deck: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/south_deck roles: - detect - record detect: width: 1280 height: 720 fps: 5 objects: track: - person - cat - dog motion: mask: - 1188,22,1188,55,825,53,828,27 zones: backyard: coordinates: 0,442,715,171,821,133,995,93,604,0,297,0,0,46 deck: coordinates: 0,720,1280,720,1280,0,1202,0,1154,170,908,114,0,433 livingroom: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/livingroom roles: - detect - record detect: width: 1280 height: 720 fps: 5 objects: track: - person - cat - dog zones: kitchen: coordinates: 178,272,780,280,773,117,195,88 livingroom_area: coordinates: 0,720,1280,720,1280,60,890,77,794,115,802,282,0,340 motion: mask: - 1227,30,1227,60,906,60,906,31 birdseye: enabled: false ui: live_mode: mse z-diagnostics-20240322-0532.zip Quote Link to comment
yayitazale Posted March 25 Author Share Posted March 25 19 hours ago, BrandonG777 said: So turns out my server locks up were not tied to the USB Coral device I was trying to use but rather out of memory issues that seem to be related to the ffmpeg process. Not sure where I've gone wrong, it works for days/weeks and then at the most inconvenient times it hard locks. mqtt: host: 10.0.0.3 port: 1883 topic_prefix: frigate client_id: frigate user: frigate password: **CENSORED** stats_interval: 60 ffmpeg: hwaccel_args: preset-nvidia-h264 detectors: cuda: type: tensorrt model: path: /config/model_cache/tensorrt/yolov4-tiny-416.trt labelmap_path: /labelmap.txt input_tensor: nchw width: 416 height: 416 record: enabled: true retain: days: 7 mode: motion events: retain: default: 5 mode: active_objects pre_capture: 3 post_capture: 10 snapshots: enabled: true retain: default: 30 timestamp: true bounding_box: true birdseye: enabled: false restream: true width: 1280 height: 720 quality: 8 mode: motion go2rtc: streams: driveway: - rtsp://frigate:**CENSORED**@10.0.0.8:554/cam/realmonitor?channel=1&subtype=0 driveway_sub: - rtsp://frigate:**CENSORED**@10.0.0.8:554/cam/realmonitor?channel=1&subtype=2 front: - rtsp://frigate:**CENSORED**@10.0.0.6:554/cam/realmonitor?channel=1&subtype=0 front_sub: - rtsp://frigate:**CENSORED**@10.0.0.6:554/cam/realmonitor?channel=1&subtype=2 front_door: - rtsp://frigate:**CENSORED**@10.0.0.5:554/cam/realmonitor?channel=2&subtype=0 garage: - rtsp://frigate:**CENSORED**@10.0.0.7:554/cam/realmonitor?channel=1&subtype=0 garage_sub: - rtsp://frigate:**CENSORED**@10.0.0.7:554/cam/realmonitor?channel=1&subtype=2 livingroom: - rtsp://homeassistant:**CENSORED**@10.0.0.9:554/cam/realmonitor?channel=1&subtype=0 north_deck: - rtsp://frigate:**CENSORED**@10.0.0.5:554/cam/realmonitor?channel=4&subtype=0 south_deck: - rtsp://frigate:**CENSORED**@10.0.0.5:554/cam/realmonitor?channel=3&subtype=0 cameras: driveway: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/driveway_sub roles: - detect - path: rtsp://127.0.0.1:8554/driveway roles: - audio - record detect: width: 1280 height: 720 fps: 5 objects: track: - person - bicycle - car - cat - dog filters: car: mask: - 1280,0,1280,440,992,296,569,331,708,720,0,720,0,0 birdseye: mode: continuous zones: driveway_top: coordinates: 687,720,561,321,955,294,1280,481,1259,528,1160,720 motion: mask: - 1243,659,1243,701,831,699,831,663 front: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/front_sub roles: - detect - path: rtsp://127.0.0.1:8554/front roles: - audio - record detect: width: 1280 height: 720 fps: 5 motion: mask: - 1243,659,1243,701,831,699,831,663 objects: track: - person - bicycle - cat - dog filters: person: mask: - 728,720,931,720,887,615,746,469,632,499 zones: driveway_top: coordinates: 238,227,580,161,463,148,218,194 front_lawn: coordinates: 364,255,256,290,745,511,925,720,1280,720,1280,345,1112,276,844,194,637,145,564,165,355,210,312,227 front_patio: coordinates: 0,720,894,720,747,507,233,305,0,412 front_porch: coordinates: 0,407,344,253,231,254,195,105,0,178 birdseye: mode: continuous front_door: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/front_door roles: - detect - record detect: width: 960 height: 480 fps: 5 objects: track: - person - cat - dog zones: front_lawn: coordinates: 588,144,734,221,795,0,351,0,365,44,506,50 front_porch: coordinates: 223,480,960,480,960,160,743,202,588,138,541,81,291,70 motion: mask: - 377,16,383,53,16,45,17,17 garage: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/garage_sub roles: - detect - path: rtsp://127.0.0.1:8554/garage roles: - audio - record detect: width: 1280 height: 720 fps: 5 objects: track: - person - bicycle - car - cat - dog zones: garage_floor: coordinates: 21,263,182,619,428,673,463,720,1280,720,1280,216,967,21,437,26 objects: - person - bicycle - car - cat - dog birdseye: mode: continuous motion: mask: - 430,13,432,44,12,45,12,8 north_deck: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/north_deck roles: - detect - record detect: width: 1280 height: 720 fps: 5 objects: track: - person - cat - dog motion: mask: - 1188,22,1188,55,825,53,828,27 south_deck: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/south_deck roles: - detect - record detect: width: 1280 height: 720 fps: 5 objects: track: - person - cat - dog motion: mask: - 1188,22,1188,55,825,53,828,27 zones: backyard: coordinates: 0,442,715,171,821,133,995,93,604,0,297,0,0,46 deck: coordinates: 0,720,1280,720,1280,0,1202,0,1154,170,908,114,0,433 livingroom: ffmpeg: input_args: preset-rtsp-restream inputs: - path: rtsp://127.0.0.1:8554/livingroom roles: - detect - record detect: width: 1280 height: 720 fps: 5 objects: track: - person - cat - dog zones: kitchen: coordinates: 178,272,780,280,773,117,195,88 livingroom_area: coordinates: 0,720,1280,720,1280,60,890,77,794,115,802,282,0,340 motion: mask: - 1227,30,1227,60,906,60,906,31 birdseye: enabled: false ui: live_mode: mse z-diagnostics-20240322-0532.zip 240.45 kB · 0 downloads Not your fault, it is a known issue: https://github.com/blakeblackshear/frigate/issues/8470 I'm having the exact same problems. Quote Link to comment
BrandonG777 Posted March 29 Share Posted March 29 (edited) These hard lock ups are killing me. @yayitazale Thoughts on using the yolov8n model? Looks like others are having better luck with it, reading through the gitlub issue link you posted. Also, I attempted limit the memory this container has to 4GB but that didn't help. I have also verified that it is limiting the memory. I thought this would keep it from using too much and killing off critical system processes but no. If anyone could please explain this behavior I would greatly appreciate it. The other attempt I made was restarting the container on a schedule but this most recent lock up happened within 4 hours so don't see this bandaid working without getting in the way of the events within frigate. I have to figure this out, I love Frigate. I'm finally able to accomplish what I was after when I first started purchasing security cams, to know whats happening around my home but not get notified everytime a leaf blows through my yard or the sun decides to come out. UPDATE: Nevermind, got home and realized there must have been some sort of power outage because one of my UPSs was screaming. Will continue with this 4GB limit and see what happens. Edited March 29 by BrandonG777 Never assume Quote Link to comment
yayitazale Posted March 30 Author Share Posted March 30 22 hours ago, BrandonG777 said: These hard lock ups are killing me. @yayitazale Thoughts on using the yolov8n model? Looks like others are having better luck with it, reading through the gitlub issue link you posted. Also, I attempted limit the memory this container has to 4GB but that didn't help. I have also verified that it is limiting the memory. I thought this would keep it from using too much and killing off critical system processes but no. If anyone could please explain this behavior I would greatly appreciate it. The other attempt I made was restarting the container on a schedule but this most recent lock up happened within 4 hours so don't see this bandaid working without getting in the way of the events within frigate. I have to figure this out, I love Frigate. I'm finally able to accomplish what I was after when I first started purchasing security cams, to know whats happening around my home but not get notified everytime a leaf blows through my yard or the sun decides to come out. UPDATE: Nevermind, got home and realized there must have been some sort of power outage because one of my UPSs was screaming. Will continue with this 4GB limit and see what happens. I have updated to ipvlan and from then, I only had one hard lock. I have activated syslog so let's see if the problem is solved or not. Quote Link to comment
slashgob Posted April 2 Share Posted April 2 On 2/12/2024 at 5:56 PM, BrandonG777 said: Well, everything has been going fine for me using GPU detector but I have not been able to get my USB Coral device to detect within the container. Early this morning my entire unRAID hard locked on me. Something I have not seen before plugging in this sketchy USB Coral device in. I've mapped /dev/bus/usb and granted the container priviledged access. Beyond this, I can't find anything that I'm missing. Unless someone can point out something I've missed I think I'm throwing in the towel on the USB Coral. You can see my full config above. I have the exact same issue. I know the Coral USB device is working fine because it works through Codeproject.ai and Agent-DVR. I would like to move over to Frigate though, but I won't unless this issue is fixed. It's obviously something to do with Frigate. I've done all the same things you have but still I get the TPU not detected error in Frigate Quote Link to comment
only-university6482 Posted April 2 Share Posted April 2 9 minutes ago, slashgob said: I have the exact same issue. I know the Coral USB device is working fine because it works through Codeproject.ai and Agent-DVR. I would like to move over to Frigate though, but I won't unless this issue is fixed. It's obviously something to do with Frigate. I've done all the same things you have but still I get the TPU not detected error in Frigate I even had luck with the coral tpu m2 wifi card. Slotted it in, changed config in frigate to pcie:0 and up working straight away. Not sure what else to suggest. Must be a passthrough issue in the iommu groups or something like that. Can you see the device in settings> System Devices? Under the groups? Quote Link to comment
slashgob Posted April 2 Share Posted April 2 6 minutes ago, only-university6482 said: I even had luck with the coral tpu m2 wifi card. Slotted it in, changed config in frigate to pcie:0 and up working straight away. Not sure what else to suggest. Must be a passthrough issue in the iommu groups or something like that. Can you see the device in settings> System Devices? Under the groups? Yes, It's there in System Devices. Like I said, it works fine in the codeproject.ai docker... It's just Frigate doesn't seem to be able to detect it Quote Link to comment
yayitazale Posted April 2 Author Share Posted April 2 16 minutes ago, slashgob said: Yes, It's there in System Devices. Like I said, it works fine in the codeproject.ai docker... It's just Frigate doesn't seem to be able to detect it Can you post a screenshot of how are you launching the template and the config file? Quote Link to comment
slashgob Posted April 2 Share Posted April 2 1 hour ago, yayitazale said: Can you post a screenshot of how are you launching the template and the config file? This is the error log: 2024-04-02 17:15:12.021315823 [INFO] Preparing Frigate... 2024-04-02 17:15:12.023112484 [INFO] Starting NGINX... 2024-04-02 17:15:12.039387243 [INFO] Preparing new go2rtc config... 2024-04-02 17:15:12.045838987 [INFO] Starting Frigate... 2024-04-02 17:15:12.637535936 [INFO] Starting go2rtc... 2024-04-02 17:15:12.779023571 17:15:12.778 INF go2rtc version 1.8.4 linux/amd64 2024-04-02 17:15:12.779721917 17:15:12.779 INF [rtsp] listen addr=:8554 2024-04-02 17:15:12.779760480 17:15:12.779 INF [api] listen addr=:1984 2024-04-02 17:15:12.780113123 17:15:12.780 INF [webrtc] listen addr=:8555 2024-04-02 17:15:15.042371804 [2024-04-02 17:15:15] frigate.app INFO : Starting Frigate (0.13.2-6476f8a) 2024-04-02 17:15:22.022403552 [INFO] Starting go2rtc healthcheck service... 2024-04-02 17:15:26.894930195 2024/04/02 17:15:26 [error] 154#154: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", upstream: "http://127.0.0.1:5001version", host: "127.0.0.1:5000" 2024-04-02 17:15:35.099098999 [2024-04-02 17:15:35] peewee_migrate.logs INFO : Starting migrations 2024-04-02 17:15:35.108366159 [2024-04-02 17:15:35] peewee_migrate.logs INFO : There is nothing to migrate 2024-04-02 17:15:35.119447329 [2024-04-02 17:15:35] frigate.app INFO : Recording process started: 482 2024-04-02 17:15:35.125390858 [2024-04-02 17:15:35] frigate.app INFO : go2rtc process pid: 98 2024-04-02 17:15:35.167602286 [2024-04-02 17:15:35] detector.coral INFO : Starting detection process: 491 2024-04-02 17:15:35.171784312 [2024-04-02 17:15:35] frigate.app INFO : Output process started: 493 2024-04-02 17:15:35.198245197 [2024-04-02 17:15:35] frigate.app INFO : Camera processor started for Garden: 499 2024-04-02 17:15:35.210373077 [2024-04-02 17:15:35] frigate.app INFO : Camera processor started for Front: 502 2024-04-02 17:15:35.222677398 [2024-04-02 17:15:35] frigate.app INFO : Camera processor started for Side: 505 2024-04-02 17:15:35.239248230 [2024-04-02 17:15:35] frigate.app INFO : Capture process started for Garden: 508 2024-04-02 17:15:35.251558369 [2024-04-02 17:15:35] frigate.app INFO : Capture process started for Front: 511 2024-04-02 17:15:35.263551027 [2024-04-02 17:15:35] frigate.app INFO : Capture process started for Side: 516 2024-04-02 17:15:37.824430472 [2024-04-02 17:15:35] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-04-02 17:15:37.826667536 Process detector:coral: 2024-04-02 17:15:37.826742679 [2024-04-02 17:15:37] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-04-02 17:15:37.827044855 [2024-04-02 17:15:37] frigate.detectors.plugins.edgetpu_tfl ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. 2024-04-02 17:15:37.829317565 Traceback (most recent call last): 2024-04-02 17:15:37.829413360 File "/usr/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap 2024-04-02 17:15:37.829420736 self.run() 2024-04-02 17:15:37.829425892 File "/usr/lib/python3.9/multiprocessing/process.py", line 108, in run 2024-04-02 17:15:37.829435494 self._target(*self._args, **self._kwargs) 2024-04-02 17:15:37.829471948 File "/opt/frigate/frigate/object_detection.py", line 102, in run_detector 2024-04-02 17:15:37.829477049 object_detector = LocalObjectDetector(detector_config=detector_config) 2024-04-02 17:15:37.829481993 File "/opt/frigate/frigate/object_detection.py", line 53, in __init__ 2024-04-02 17:15:37.829486382 self.detect_api = create_detector(detector_config) 2024-04-02 17:15:37.829492015 File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector 2024-04-02 17:15:37.829537086 return api(detector_config) 2024-04-02 17:15:37.829542505 File "/opt/frigate/frigate/detectors/plugins/edgetpu_tfl.py", line 43, in __init__ 2024-04-02 17:15:37.829548939 self.interpreter = Interpreter( 2024-04-02 17:15:37.829553570 File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 348, in __init__ 2024-04-02 17:15:37.829558394 _interpreter_wrapper.CreateWrapperFromFile( 2024-04-02 17:15:37.829595433 ValueError: Model provided has model identifier ' Quote Link to comment
slashgob Posted April 2 Share Posted April 2 This is the config: mqtt: enabled: false ffmpeg: hwaccel_args: preset-nvidia-h264 detectors: coral: type: edgetpu device: usb # tensorrt: # type: tensorrt # device: 0 #This is the default, select the first GPU model: path: /config/model_cache/tensorrt/yolov7-320.trt input_tensor: nchw input_pixel_format: rgb width: 320 height: 320 cameras: Garden: # <--- Reolink enabled: true ffmpeg: output_args: record: preset-record-generic-audio-copy inputs: - path: rtsp://viewer:[email protected]:554/h264Preview_01_sub # <-- Low-res roles: - detect - path: rtsp://viewer:[email protected]:554/h264Preview_01_main # <-- Hi-res roles: - record detect: enabled: true record: enabled: true retain: days: 14 mode: all events: required_zones: - zone_0 retain: default: 30 mode: active_objects zones: zone_0: coordinates: 0,480,400,480,578,156,411,80,0,148 inertia: 3 objects: track: - person Front: enabled: true ffmpeg: inputs: - path: rtsp://10.0.0.81:554/12 # <-- Low-res roles: - detect - path: rtsp://10.0.0.81:554/11 # <-- Hi-res roles: - record detect: enabled: true # stationary: # interval: 20 # threshold: 50 record: enabled: true retain: days: 14 mode: all events: required_zones: - zone_1 retain: default: 30 mode: active_objects objects: track: - person # - car zones: zone_1: coordinates: 100,0,297,0,602,182,575,317,34,226 Side: enabled: true ffmpeg: inputs: - path: rtsp://10.0.0.80:554/12 # <-- Low-res roles: - detect - path: rtsp://10.0.0.80:554/11 # <-- Hi-res roles: - record detect: enabled: true # stationary: # interval: 20 # threshold: 50 record: enabled: true retain: days: 14 mode: all events: required_zones: - zone_2 retain: default: 30 mode: active_objects objects: track: - person # - car zones: zone_2: coordinates: 355,0,553,123,398,360,220,360,144,293,39,156,0,99,0,59,56,0 timestamp_style: # Optional: Position of the timestamp (default: shown below) # "tl" (top left), "tr" (top right), "bl" (bottom left), "br" (bottom right) position: "tl" # Optional: Format specifier conform to the Python package "datetime" (default: shown below) # Additional Examples: # german: "%d.%m.%Y %H:%M:%S" format: "%d/%m/%Y %H:%M:%S" # Optional: Color of font color: # All Required when color is specified (default: shown below) red: 255 green: 255 blue: 255 # Optional: Line thickness of font (default: shown below) thickness: 2 # Optional: Effect of lettering (default: shown below) # None (No effect), # "solid" (solid background in inverse color of font) # "shadow" (shadow for font) go2rtc: streams: Garden_Camera: - rtsp://viewer:[email protected]:554/h264Preview_01_sub # <-- Low-res Quote Link to comment
only-university6482 Posted April 2 Share Posted April 2 (edited) 2 hours ago, slashgob said: this i show i run the docker: First thing I don't see in your unraid config is the /dev/bus/usb. Extra params also: --gpus=all --shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=100000000 --restart unless-stopped Try these 2 changes first. Make sure your CPAI is not sharing the usb also. frigate: detectors: #coral: # type: edgetpu # device: usb coral1: type: edgetpu device: pci:0 mqtt: host: user: password: logger: # Optional: default log level (default: shown below) default: debug #info go2rtc: streams: gate_sub: - rtsp://user:[email protected]:554/Channel/102 frontyard_sub: - rtsp://user:[email protected]:554/Channel/102 rear_sub: - rtsp://user:[email protected]:554/Channel/102 front_sub: - rtsp://user:[email protected]:554/Channel/102 backyard_sub: - rtsp://user:[email protected]:554/Channel/ drive_sub: - rtsp://user:[email protected]:554/Channel/102 webrtc: candidates: - 192.168.1.244:8555 cameras: gate: enabled: true ffmpeg: hwaccel_args: preset-vaapi inputs: - path: rtsp://127.0.0.1:8554/gate_sub?video=copy input_args: preset-rtsp-restream roles: - detect - record - rtmp Edited April 2 by only-university6482 adding notes Quote Link to comment
yayitazale Posted April 2 Author Share Posted April 2 (edited) 2 hours ago, slashgob said: this i show i run the docker: You are missing the usb passtrough. I suggest you to start again with a clean template without deleting this: Also, I see in the config file that you are trying to use a yolo model with the coral and that is not posible. As you can read in the docs, the best option is to use the default model that is just fine, so you should comment or delete this part: model: path: /config/model_cache/tensorrt/yolov7-320.trt input_tensor: nchw input_pixel_format: rgb width: 320 height: 320 Yolo models are great for nvidia or openvino detectors, but the coral is a different chip that has its own requirements to create a model. If you want to use another custom modelwith the coral, it must be a tflite model. You can find here most of the pretrained models. Edited April 2 by yayitazale 1 Quote Link to comment
neleh Posted April 3 Share Posted April 3 Latest Frigate HASS plugin is requiring a higher version but unraid frigate seems to be still on 0.12.1. Is an update coming or is this unmaintained from now on? Thanks. Quote Link to comment
yayitazale Posted April 3 Author Share Posted April 3 39 minutes ago, neleh said: Latest Frigate HASS plugin is requiring a higher version but unraid frigate seems to be still on 0.12.1. Is an update coming or is this unmaintained from now on? Thanks. Frigate template is pointing to the "latest" tag so yo you should check if you have change that. Any way, you should reads the changelog and the updated docs to find out what changes you need to make to your settings has there are many new things. Also it is recommended to ensure that you are using all the required new variables in the template or reinstall it from scratch deleting you actual container. 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.