BrandonG777 Posted February 13 Share Posted February 13 3 hours ago, yayitazale said: Can you test any of the examples using another computer? https://coral.ai/examples/ It is the best way to see if you have a faulty device. I do. I'll see what I can do with those examples but even if I am successful, I feel like I'm out of options for making it work with my target Frigate system (HP z840 workstation). Maybe it's a result of multiple USB dongles like my Zigbee & Bluetooth dongles. Quote Link to comment
awediohead Posted February 18 Share Posted February 18 I won't claim to have read every single post in the 43 pages of this thread, but I've read an awful lot of it, watched a bunch of videos and read (if not understood) quite a bit of https://coral.ai/docs/ and the troubleshooting section for the TPU (so I've tried multiple USB cables for e.g.) . . . and I'm still utterly clueless (and not a little overwhelmed!) as to where to begin with Frigate on Unraid specifically. The posts and videos I've read or watched aren't using Unraid and I just can't join the dots - doubtless because of fundamental gaps in my understanding of Unraid! So 1) Do I need to follow the instructions to Install the Edge TPU runtime on Unraid's console before I do anything else? 2) Do I then need to install the PyCoral library? 3) My USB coral never seems to initialise and change from 1a6e:089a Global Unichip Corp to Google Inc. - whats the quickest way of checking whether it's a factory dud? I assume I'll be plugging it into a Linux distro - I have a POP OS install on a PC, would that be close enough to being Debian/Ubuntu based to give me accurate feedback as to whether or not the TPU is functional? Any other quicker ways to determine this since I'd prefer to put most of my time and energy into figuring out how to get this working on Unraid! 4) I thought I had created a very basic config.yml file just to get Frigate started so I could modify the config from within Frigate as is recommended - but with the USB Coral TPU plugged in starting Frigate up and looking at the logs, the logs window flickers for a fraction of a second and then disappears far too quickly to read anything. That said am I right in thinking I need to be seeing the device as Google Inc in lsusb before I can hope to launch Frigate successfully? I appreciate I have a ton to learn to get things working, but I just can't seem to find anything that assumes my kinda level of ignorance! Quote Link to comment
Bruceflix Posted February 18 Share Posted February 18 2 hours ago, awediohead said: So 1) Do I need to follow the instructions to Install the Edge TPU runtime on Unraid's console before I do anything else? 2) Do I then need to install the PyCoral library? 3) My USB coral never seems to initialise and change from 1a6e:089a Global Unichip Corp to Google Inc. - whats the quickest way of checking whether it's a factory dud? 4) I thought I had created a very basic config.yml file just to get Frigate started so I could modify the config from within Frigate as is recommended - but with the USB Coral TPU plugged in starting Frigate up and looking at the logs, the logs window flickers for a fraction of a second and then disappears far too quickly to read anything. That said am I right in thinking I need to be seeing the device as Google Inc in lsusb before I can hope to launch Frigate successfully? 1) No 2) No 3) Mine shows as Google Inc. Probably thats enough to show that you have a dud. I hope you purchased from an official store that has warranty. 1 Quote Link to comment
awediohead Posted February 18 Share Posted February 18 Thanks Bruceflix - accepting it's a dud probably explains why nothing else I've done has worked, assuming Frigate is looking for something that isn't there when the docker starts because that's what's in the config.yml ! I'll start a return and see what happens with the replacement. Cheers Quote Link to comment
yayitazale Posted February 18 Author Share Posted February 18 (edited) 17 hours ago, awediohead said: Thanks Bruceflix - accepting it's a dud probably explains why nothing else I've done has worked, assuming Frigate is looking for something that isn't there when the docker starts because that's what's in the config.yml ! I'll start a return and see what happens with the replacement. Ch You can test the coral with any of the examples here using another computer: https://coral.ai/examples/ If the card is still unresponsive or gives you only some time-to-time responses you should return it. If everything is OK, a usb coral must be almost plug&play in unraid frigate using the usb pass through (remember to test also with privileged mode). Edited February 19 by yayitazale 1 Quote Link to comment
yayitazale Posted February 19 Author Share Posted February 19 On 2/13/2024 at 12:47 PM, BrandonG777 said: I do. I'll see what I can do with those examples but even if I am successful, I feel like I'm out of options for making it work with my target Frigate system (HP z840 workstation). Maybe it's a result of multiple USB dongles like my Zigbee & Bluetooth dongles. I also have a Zigbee dongle and it doesn't affect at all. Quote Link to comment
BrandonG777 Posted February 19 Share Posted February 19 7 hours ago, yayitazale said: I also have a Zigbee dongle and it doesn't affect at all. I gave up on the USB Coral. Couldn't get it to do anything useful. RMA'd for being DOA. I'll order a PCIe version and give that a go... maybe. I've just read so many problems with these devices, even if you do make it work, I've read numerous reports where it stops working after a few months. Hard for me to get excited about a device this inconsistent. Nvidia products while much more expensive actually work from my experience. Quote Link to comment
yayitazale Posted February 19 Author Share Posted February 19 51 minutes ago, BrandonG777 said: I gave up on the USB Coral. Couldn't get it to do anything useful. RMA'd for being DOA. I'll order a PCIe version and give that a go... maybe. I've just read so many problems with these devices, even if you do make it work, I've read numerous reports where it stops working after a few months. Hard for me to get excited about a device this inconsistent. Nvidia products while much more expensive actually work from my experience. As I told you, I have been using a USB Coral device for more than 4 year with none stop and it never give me any single problem. You have been unlucky, like some others here also with PCIe versions. But yes you are right, QC of this products are a bit shameful. Quote Link to comment
awediohead Posted February 20 Share Posted February 20 9 hours ago, yayitazale said: As I told you, I have been using a USB Coral device for more than 4 year with none stop and it never give me any single problem. You have been unlucky, like some others here also with PCIe versions. But yes you are right, QC of this products are a bit shameful. Thanks - very useful real world info. So having just returned a dud USB coral TPU - would you recommend trying another of the USB type? I'm wondering because it's only an extra £10 on top of the USB unit's price for the dual TPU (https://amzn.eu/d/0ab2ffc) - though I assume I'd also need to buy some kind of adapter to fit a regular motherboard M.2 slot. That said I don't use any M.2 SSDs or NVME drives on my server (mostly for ease of access as my 2.5" SSDs are in front loading bays) so I'm pretty sure I should have enough PCIe lanes. The counter argument is that I also really like that the USB model would be very flexible - i.e. if I can't get it to work on Unraid (my Ryzen system has no iGPU and my GTX 1050 does transcoding on Plex) I could set it up on a spare 10th Gen Intel build that does have an iGPU and use that as a dedicated CCTV PC / NVR - without having to completely dismantle my Unraid server to make the swap ! Any other pros and cons to consider - assuming this is specifically for use with Frigate? Quote Link to comment
yayitazale Posted February 20 Author Share Posted February 20 5 hours ago, awediohead said: Thanks - very useful real world info. So having just returned a dud USB coral TPU - would you recommend trying another of the USB type? I'm wondering because it's only an extra £10 on top of the USB unit's price for the dual TPU (https://amzn.eu/d/0ab2ffc) - though I assume I'd also need to buy some kind of adapter to fit a regular motherboard M.2 slot. That said I don't use any M.2 SSDs or NVME drives on my server (mostly for ease of access as my 2.5" SSDs are in front loading bays) so I'm pretty sure I should have enough PCIe lanes. The counter argument is that I also really like that the USB model would be very flexible - i.e. if I can't get it to work on Unraid (my Ryzen system has no iGPU and my GTX 1050 does transcoding on Plex) I could set it up on a spare 10th Gen Intel build that does have an iGPU and use that as a dedicated CCTV PC / NVR - without having to completely dismantle my Unraid server to make the swap ! Any other pros and cons to consider - assuming this is specifically for use with Frigate? This is up to you. The dual TPU has some fire harzard as they get quite hot. It's is a good idea to put a heatsink and a fan to keep the temp low and stable. The USB it is the most versatile and that's why I bought it back in the day but then when I installed frigate I didn't unplug it from the PC for 4 years.... 1 Quote Link to comment
doubleopinter Posted February 20 Share Posted February 20 Just updated Unraid to 6.12.8 from 6.11.5 and update frigate to 0.13.2 from 0.12.x. Cannot start. I've been using my RTX 2060 for frigate, seems like something around that is broken right now. Trying to start gives me this text error warn system array login s6-rc: info: service nginx-log successfully started s6-rc: info: service go2rtc-log successfully started s6-rc: info: service go2rtc: starting s6-rc: info: service frigate-log successfully started s6-rc: info: service go2rtc successfully started s6-rc: info: service go2rtc-healthcheck: starting s6-rc: info: service frigate: starting s6-rc: info: service go2rtc-healthcheck successfully started s6-rc: info: service frigate successfully started s6-rc: info: service nginx: starting s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service nginx: stopping s6-rc: info: service go2rtc-healthcheck: stopping s6-rc: info: service go2rtc-healthcheck successfully stopped s6-rc: info: service nginx successfully stopped s6-rc: info: service nginx-log: stopping s6-rc: info: service frigate: stopping s6-rc: info: service nginx-log successfully stopped 2024-02-20 16:01:18.482511101 [INFO] Preparing Frigate... 2024-02-20 16:01:18.484724421 [INFO] Preparing new go2rtc config... 2024-02-20 16:01:18.487565996 [INFO] Starting NGINX... 2024-02-20 16:01:18.507874744 [INFO] Starting Frigate... 2024-02-20 16:01:18.874916467 [INFO] Starting go2rtc... 2024-02-20 16:01:18.970936212 16:01:18.970 INF go2rtc version 1.8.4 linux/amd64 2024-02-20 16:01:18.971461057 16:01:18.971 INF [rtsp] listen addr=:8554 2024-02-20 16:01:18.971507921 16:01:18.971 INF [api] listen addr=:1984 2024-02-20 16:01:18.971725449 16:01:18.971 INF [webrtc] listen addr=:8555 2024-02-20 16:01:19.961878556 [2024-02-20 16:01:19] frigate.app INFO : Starting Frigate (0.13.2-6476f8a) 2024-02-20 16:01:22.205178677 2024/02/20 16:01:22 [error] 154#154: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.101.195, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "192.168.101.198:5001" 2024-02-20 16:01:27.203162963 2024/02/20 16:01:27 [error] 154#154: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.101.195, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "192.168.101.198:5001" 2024-02-20 16:01:28.483323782 [INFO] Starting go2rtc healthcheck service... 2024-02-20 16:01:30.735092299 [2024-02-20 16:01:30] peewee_migrate.logs INFO : Starting migrations 2024-02-20 16:01:30.744011537 [2024-02-20 16:01:30] peewee_migrate.logs INFO : There is nothing to migrate 2024-02-20 16:01:30.754203654 [2024-02-20 16:01:30] frigate.app INFO : Recording process started: 619 2024-02-20 16:01:30.756668686 [2024-02-20 16:01:30] frigate.app INFO : go2rtc process pid: 98 2024-02-20 16:01:30.787144780 [2024-02-20 16:01:30] detector.tensorrt INFO : Starting detection process: 629 2024-02-20 16:01:30.798494557 [2024-02-20 16:01:30] frigate.app INFO : Output process started: 632 2024-02-20 16:01:30.916849564 [2024-02-20 16:01:30] frigate.detectors.plugins.tensorrt INFO : Loaded engine size: 13 MiB 2024-02-20 16:01:31.052494849 [2024-02-20 16:01:31] frigate.detectors.plugins.tensorrt ERROR : 1: [stdArchiveReader.cpp::StdArchiveReader::42] Error Code 1: Serialization (Serialization assertion stdVersionRead == serializationVersion failed.Version tag does not match. Note: Current Version: 232, Serialized Engine Version: 213) 2024-02-20 16:01:31.063680272 [2024-02-20 16:01:31] frigate.detectors.plugins.tensorrt ERROR : 4: [runtime.cpp::deserializeCudaEngine::66] Error Code 4: Internal Error (Engine deserialization failed.) 2024-02-20 16:01:31.065394010 Process detector:tensorrt: 2024-02-20 16:01:31.066177617 Traceback (most recent call last): 2024-02-20 16:01:31.066202689 File "/usr/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap 2024-02-20 16:01:31.066204469 self.run() 2024-02-20 16:01:31.066205639 File "/usr/lib/python3.9/multiprocessing/process.py", line 108, in run 2024-02-20 16:01:31.066206650 self._target(*self._args, **self._kwargs) 2024-02-20 16:01:31.066213860 File "/opt/frigate/frigate/object_detection.py", line 102, in run_detector 2024-02-20 16:01:31.066214970 object_detector = LocalObjectDetector(detector_config=detector_config) 2024-02-20 16:01:31.066216010 File "/opt/frigate/frigate/object_detection.py", line 53, in __init__ 2024-02-20 16:01:31.066216930 self.detect_api = create_detector(detector_config) 2024-02-20 16:01:31.066218891 File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector 2024-02-20 16:01:31.066221911 return api(detector_config) 2024-02-20 16:01:31.066222911 File "/opt/frigate/frigate/detectors/plugins/tensorrt.py", line 221, in __init__ 2024-02-20 16:01:31.066241333 self.input_shape = self._get_input_shape() 2024-02-20 16:01:31.066251093 File "/opt/frigate/frigate/detectors/plugins/tensorrt.py", line 93, in _get_input_shape 2024-02-20 16:01:31.066252314 binding = self.engine[0] 2024-02-20 16:01:31.066253474 TypeError: 'NoneType' object is not subscriptable 2024-02-20 16:01:31.066282416 Exception ignored in: <function TensorRtDetector.__del__ at 0x147c26336c10> 2024-02-20 16:01:31.066292897 Traceback (most recent call last): 2024-02-20 16:01:31.066294367 File "/opt/frigate/frigate/detectors/plugins/tensorrt.py", line 239, in __del__ 2024-02-20 16:01:31.066439730 if self.outputs is not None: 2024-02-20 16:01:31.066535718 AttributeError: 'TensorRtDetector' object has no attribute 'outputs' 2024-02-20 16:01:31.075520771 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for driveway: 654 2024-02-20 16:01:31.089611724 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for shedsouth: 656 2024-02-20 16:01:31.101789522 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for shedwest: 664 2024-02-20 16:01:31.113922867 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for doorbell: 666 2024-02-20 16:01:31.123676776 2024/02/20 16:01:31 [error] 155#155: *4 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-02-20 16:01:31.128786856 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for driveway: 669 2024-02-20 16:01:31.141811307 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for shedsouth: 673 2024-02-20 16:01:31.152635609 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for shedwest: 676 2024-02-20 16:01:31.166414685 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for doorbell: 684 2024-02-20 16:01:51.338649529 [2024-02-20 16:01:51] frigate.watchdog INFO : Detection appears to have stopped. Exiting Frigate... 2024-02-20 16:01:51.353163748 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15) 2024-02-20 16:01:51.390329037 [INFO] Service NGINX exited with code 0 (by signal 0) 2024-02-20 16:01:51.392743125 [2024-02-20 16:01:51] frigate.app INFO : Stopping... 2024-02-20 16:01:51.393062562 [2024-02-20 16:01:51] frigate.events.cleanup INFO : Exiting event cleanup... 2024-02-20 16:01:51.393342556 [2024-02-20 16:01:51] frigate.record.cleanup INFO : Exiting recording cleanup... 2024-02-20 16:01:51.393893554 [2024-02-20 16:01:51] frigate.storage INFO : Exiting storage maintainer... 2024-02-20 16:01:51.394247894 [2024-02-20 16:01:51] frigate.stats INFO : Exiting stats emitter... 2024-02-20 16:01:51.404968067 [2024-02-20 16:01:51] frigate.ptz.autotrack INFO : Exiting autotracker... 2024-02-20 16:01:51.412022154 [2024-02-20 16:01:51] frigate.watchdog INFO : Exiting watchdog... 2024-02-20 16:01:51.412285637 [2024-02-20 16:01:51] frigate.object_processing INFO : Exiting object processor... 2024-02-20 16:01:51.621805971 [2024-02-20 16:01:51] frigate.events.maintainer INFO : Exiting event processor... 2024-02-20 16:01:51.783135497 [2024-02-20 16:01:51] frigate.comms.ws INFO : Exiting websocket client... 2024-02-20 16:01:52.767713382 [2024-02-20 16:01:52] peewee.sqliteq INFO : writer received shutdown request, exiting. 2024-02-20 16:01:52.774181768 [2024-02-20 16:01:52] watchdog.doorbell INFO : Terminating the existing ffmpeg process... Quote Link to comment
yayitazale Posted February 20 Author Share Posted February 20 (edited) 17 minutes ago, doubleopinter said: Just updated Unraid to 6.12.8 from 6.11.5 and update frigate to 0.13.2 from 0.12.x. Cannot start. I've been using my RTX 2060 for frigate, seems like something around that is broken right now. Trying to start gives me this text error warn system array login s6-rc: info: service nginx-log successfully started s6-rc: info: service go2rtc-log successfully started s6-rc: info: service go2rtc: starting s6-rc: info: service frigate-log successfully started s6-rc: info: service go2rtc successfully started s6-rc: info: service go2rtc-healthcheck: starting s6-rc: info: service frigate: starting s6-rc: info: service go2rtc-healthcheck successfully started s6-rc: info: service frigate successfully started s6-rc: info: service nginx: starting s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service nginx: stopping s6-rc: info: service go2rtc-healthcheck: stopping s6-rc: info: service go2rtc-healthcheck successfully stopped s6-rc: info: service nginx successfully stopped s6-rc: info: service nginx-log: stopping s6-rc: info: service frigate: stopping s6-rc: info: service nginx-log successfully stopped 2024-02-20 16:01:18.482511101 [INFO] Preparing Frigate... 2024-02-20 16:01:18.484724421 [INFO] Preparing new go2rtc config... 2024-02-20 16:01:18.487565996 [INFO] Starting NGINX... 2024-02-20 16:01:18.507874744 [INFO] Starting Frigate... 2024-02-20 16:01:18.874916467 [INFO] Starting go2rtc... 2024-02-20 16:01:18.970936212 16:01:18.970 INF go2rtc version 1.8.4 linux/amd64 2024-02-20 16:01:18.971461057 16:01:18.971 INF [rtsp] listen addr=:8554 2024-02-20 16:01:18.971507921 16:01:18.971 INF [api] listen addr=:1984 2024-02-20 16:01:18.971725449 16:01:18.971 INF [webrtc] listen addr=:8555 2024-02-20 16:01:19.961878556 [2024-02-20 16:01:19] frigate.app INFO : Starting Frigate (0.13.2-6476f8a) 2024-02-20 16:01:22.205178677 2024/02/20 16:01:22 [error] 154#154: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.101.195, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "192.168.101.198:5001" 2024-02-20 16:01:27.203162963 2024/02/20 16:01:27 [error] 154#154: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.101.195, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "192.168.101.198:5001" 2024-02-20 16:01:28.483323782 [INFO] Starting go2rtc healthcheck service... 2024-02-20 16:01:30.735092299 [2024-02-20 16:01:30] peewee_migrate.logs INFO : Starting migrations 2024-02-20 16:01:30.744011537 [2024-02-20 16:01:30] peewee_migrate.logs INFO : There is nothing to migrate 2024-02-20 16:01:30.754203654 [2024-02-20 16:01:30] frigate.app INFO : Recording process started: 619 2024-02-20 16:01:30.756668686 [2024-02-20 16:01:30] frigate.app INFO : go2rtc process pid: 98 2024-02-20 16:01:30.787144780 [2024-02-20 16:01:30] detector.tensorrt INFO : Starting detection process: 629 2024-02-20 16:01:30.798494557 [2024-02-20 16:01:30] frigate.app INFO : Output process started: 632 2024-02-20 16:01:30.916849564 [2024-02-20 16:01:30] frigate.detectors.plugins.tensorrt INFO : Loaded engine size: 13 MiB 2024-02-20 16:01:31.052494849 [2024-02-20 16:01:31] frigate.detectors.plugins.tensorrt ERROR : 1: [stdArchiveReader.cpp::StdArchiveReader::42] Error Code 1: Serialization (Serialization assertion stdVersionRead == serializationVersion failed.Version tag does not match. Note: Current Version: 232, Serialized Engine Version: 213) 2024-02-20 16:01:31.063680272 [2024-02-20 16:01:31] frigate.detectors.plugins.tensorrt ERROR : 4: [runtime.cpp::deserializeCudaEngine::66] Error Code 4: Internal Error (Engine deserialization failed.) 2024-02-20 16:01:31.065394010 Process detector:tensorrt: 2024-02-20 16:01:31.066177617 Traceback (most recent call last): 2024-02-20 16:01:31.066202689 File "/usr/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap 2024-02-20 16:01:31.066204469 self.run() 2024-02-20 16:01:31.066205639 File "/usr/lib/python3.9/multiprocessing/process.py", line 108, in run 2024-02-20 16:01:31.066206650 self._target(*self._args, **self._kwargs) 2024-02-20 16:01:31.066213860 File "/opt/frigate/frigate/object_detection.py", line 102, in run_detector 2024-02-20 16:01:31.066214970 object_detector = LocalObjectDetector(detector_config=detector_config) 2024-02-20 16:01:31.066216010 File "/opt/frigate/frigate/object_detection.py", line 53, in __init__ 2024-02-20 16:01:31.066216930 self.detect_api = create_detector(detector_config) 2024-02-20 16:01:31.066218891 File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector 2024-02-20 16:01:31.066221911 return api(detector_config) 2024-02-20 16:01:31.066222911 File "/opt/frigate/frigate/detectors/plugins/tensorrt.py", line 221, in __init__ 2024-02-20 16:01:31.066241333 self.input_shape = self._get_input_shape() 2024-02-20 16:01:31.066251093 File "/opt/frigate/frigate/detectors/plugins/tensorrt.py", line 93, in _get_input_shape 2024-02-20 16:01:31.066252314 binding = self.engine[0] 2024-02-20 16:01:31.066253474 TypeError: 'NoneType' object is not subscriptable 2024-02-20 16:01:31.066282416 Exception ignored in: <function TensorRtDetector.__del__ at 0x147c26336c10> 2024-02-20 16:01:31.066292897 Traceback (most recent call last): 2024-02-20 16:01:31.066294367 File "/opt/frigate/frigate/detectors/plugins/tensorrt.py", line 239, in __del__ 2024-02-20 16:01:31.066439730 if self.outputs is not None: 2024-02-20 16:01:31.066535718 AttributeError: 'TensorRtDetector' object has no attribute 'outputs' 2024-02-20 16:01:31.075520771 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for driveway: 654 2024-02-20 16:01:31.089611724 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for shedsouth: 656 2024-02-20 16:01:31.101789522 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for shedwest: 664 2024-02-20 16:01:31.113922867 [2024-02-20 16:01:31] frigate.app INFO : Camera processor started for doorbell: 666 2024-02-20 16:01:31.123676776 2024/02/20 16:01:31 [error] 155#155: *4 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-02-20 16:01:31.128786856 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for driveway: 669 2024-02-20 16:01:31.141811307 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for shedsouth: 673 2024-02-20 16:01:31.152635609 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for shedwest: 676 2024-02-20 16:01:31.166414685 [2024-02-20 16:01:31] frigate.app INFO : Capture process started for doorbell: 684 2024-02-20 16:01:51.338649529 [2024-02-20 16:01:51] frigate.watchdog INFO : Detection appears to have stopped. Exiting Frigate... 2024-02-20 16:01:51.353163748 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15) 2024-02-20 16:01:51.390329037 [INFO] Service NGINX exited with code 0 (by signal 0) 2024-02-20 16:01:51.392743125 [2024-02-20 16:01:51] frigate.app INFO : Stopping... 2024-02-20 16:01:51.393062562 [2024-02-20 16:01:51] frigate.events.cleanup INFO : Exiting event cleanup... 2024-02-20 16:01:51.393342556 [2024-02-20 16:01:51] frigate.record.cleanup INFO : Exiting recording cleanup... 2024-02-20 16:01:51.393893554 [2024-02-20 16:01:51] frigate.storage INFO : Exiting storage maintainer... 2024-02-20 16:01:51.394247894 [2024-02-20 16:01:51] frigate.stats INFO : Exiting stats emitter... 2024-02-20 16:01:51.404968067 [2024-02-20 16:01:51] frigate.ptz.autotrack INFO : Exiting autotracker... 2024-02-20 16:01:51.412022154 [2024-02-20 16:01:51] frigate.watchdog INFO : Exiting watchdog... 2024-02-20 16:01:51.412285637 [2024-02-20 16:01:51] frigate.object_processing INFO : Exiting object processor... 2024-02-20 16:01:51.621805971 [2024-02-20 16:01:51] frigate.events.maintainer INFO : Exiting event processor... 2024-02-20 16:01:51.783135497 [2024-02-20 16:01:51] frigate.comms.ws INFO : Exiting websocket client... 2024-02-20 16:01:52.767713382 [2024-02-20 16:01:52] peewee.sqliteq INFO : writer received shutdown request, exiting. 2024-02-20 16:01:52.774181768 [2024-02-20 16:01:52] watchdog.doorbell INFO : Terminating the existing ffmpeg process... You should recreate the nvidia models inside the frigate container (you have the info in the docs). The Cuda version is not the same so the models can't be used. Pd: I suggest you to delete and create a new container of frigate too, the template has been updated to accommodate the new environmental arguments needed to create the models directly inside frigate container instead using tensorrt containers. Edited February 20 by yayitazale Quote Link to comment
CykloneFij Posted February 22 Share Posted February 22 Hi. I have a shell command in HA that will create a recording using the HTTP API: shell_command: backyard_force_record: 'curl -d "duration=30&include_recording=true" -H "Content-Type: application/x-www-form-urlencoded" -X POST http://xxx.xxx.xxx.xxx:5000/api/events/backyard/forced/create' It works, an event is created in Frigate on the camera. However, it is only a snapshot. There is no video. The response from the above command is: stdout: >- {"event_id":"1708645049.409679-gi943a","message":"Successfully created event.","success":true} stderr: "% Total % Received % Xferd Average Speed Time Time Time Current\n Dload Upload Total Spent Left Speed\n\r 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0\r100 129 100 95 100 34 472 169 --:--:-- --:--:-- --:--:-- 645" returncode: 0 Grateful for any assistance. Quote Link to comment
yayitazale Posted February 23 Author Share Posted February 23 6 hours ago, CykloneFij said: Hi. I have a shell command in HA that will create a recording using the HTTP API: shell_command: backyard_force_record: 'curl -d "duration=30&include_recording=true" -H "Content-Type: application/x-www-form-urlencoded" -X POST http://xxx.xxx.xxx.xxx:5000/api/events/backyard/forced/create' It works, an event is created in Frigate on the camera. However, it is only a snapshot. There is no video. The response from the above command is: stdout: >- {"event_id":"1708645049.409679-gi943a","message":"Successfully created event.","success":true} stderr: "% Total % Received % Xferd Average Speed Time Time Time Current\n Dload Upload Total Spent Left Speed\n\r 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0\r100 129 100 95 100 34 472 169 --:--:-- --:--:-- --:--:-- 645" returncode: 0 Grateful for any assistance. This is out of scope of this forum. I only maintain the unraid template. You should open a issue on github. Quote Link to comment
CykloneFij Posted February 23 Share Posted February 23 9 hours ago, yayitazale said: This is out of scope of this forum. I only maintain the unraid template. You should open a issue on github. Ah yes, thank you. Quote Link to comment
CoZ Posted March 1 Share Posted March 1 (edited) Anyone else have an issue with recordings not being deleted as set up by the config file? For instance, I have record: enabled: True events: retain: default: 2 snapshots: enabled: True But, I've still got 7+ days of recordings. Looking at this again, maybe it's just the snapshots / thumbnails that aren't being automatically deleted? Do I have to add a 'retain: default: 2' under the snapshots entry as well? Edited March 2 by CoZ Added some info Quote Link to comment
yayitazale Posted March 2 Author Share Posted March 2 14 hours ago, CoZ said: Anyone else have an issue with recordings not being deleted as set up by the config file? For instance, I have record: enabled: True events: retain: default: 2 snapshots: enabled: True But, I've still got 7+ days of recordings. Looking at this again, maybe it's just the snapshots / thumbnails that aren't being automatically deleted? Do I have to add a 'retain: default: 2' under the snapshots entry as well? https://docs.frigate.video/configuration/reference Default for snapshots is 10 days. Quote Link to comment
CoZ Posted March 2 Share Posted March 2 5 hours ago, yayitazale said: https://docs.frigate.video/configuration/reference Default for snapshots is 10 days. So then, yes, add the 'retain / default' entry to the Snapshots as well. 1 Quote Link to comment
usTrUcX Posted March 8 Share Posted March 8 (edited) Hi, thank you for this amazing template. Please can anyone enlighten me where exactly, with uttermost precision, the config.yml file must be created, considering how the container is set up by default in Unraid? NVM, going like `sudo nano /mnt/user/appdata/frigate/config.yml` from Unraid terminal did it, it just wont recognize my nvidia gpu, I followed the instructions from the description (If you want to use a NVidia card to image decoding and/or detection, you must first install the drivers from CA app (thanks to @ich777), add "--runtime=nvidia" as extra parameter under advanced view and set the "Nvidia Visible Devices" variable with your "GPU UUID" as the value. - If you want to use the NVidia TensorRT Detector, you have to select the correspondig NVIDIA branch.) but it says "Hardware acceleration has not been setup, see the docs to setup hardware acceleration.". NVM, all it needed was: ``` ffmpeg: hwaccel_args: preset-nvidia-h264 ``` on the config file. Edited March 8 by usTrUcX Quote Link to comment
yayitazale Posted March 14 Author Share Posted March 14 On 3/9/2024 at 6:10 AM, usTrUcX said: Hi, thank you for this amazing template. Please can anyone enlighten me where exactly, with uttermost precision, the config.yml file must be created, considering how the container is set up by default in Unraid? NVM, going like `sudo nano /mnt/user/appdata/frigate/config.yml` from Unraid terminal did it, it just wont recognize my nvidia gpu, I followed the instructions from the description (If you want to use a NVidia card to image decoding and/or detection, you must first install the drivers from CA app (thanks to @ich777), add "--runtime=nvidia" as extra parameter under advanced view and set the "Nvidia Visible Devices" variable with your "GPU UUID" as the value. - If you want to use the NVidia TensorRT Detector, you have to select the correspondig NVIDIA branch.) but it says "Hardware acceleration has not been setup, see the docs to setup hardware acceleration.". NVM, all it needed was: ``` ffmpeg: hwaccel_args: preset-nvidia-h264 ``` on the config file. Did you check the compatibility of your card? Did you restart the server after installing the nvidia driver? Can you post the screenshot of how are you filling the template and the config file? Quote Link to comment
only-university6482 Posted March 16 Share Posted March 16 Works great with the coral USB But I'm trying to get tailscale client working in the docker container. Can install it using the linux command but running 'tailscope up' does nothing, Says it fails to connnect. Now my other frigate lxc container on proxmox ran fine with tailscale. No extra config was required. Any ideas how I can get tailscale working in this container? Thanks Quote Link to comment
yayitazale Posted March 17 Author Share Posted March 17 14 hours ago, only-university6482 said: Works great with the coral USB But I'm trying to get tailscale client working in the docker container. Can install it using the linux command but running 'tailscope up' does nothing, Says it fails to connnect. Now my other frigate lxc container on proxmox ran fine with tailscale. No extra config was required. Any ideas how I can get tailscale working in this container? Thanks No idea, maybe you can ask on github Quote Link to comment
awediohead Posted March 18 Share Posted March 18 So having sent back a dud USB Coral TPU, I got a replacement and it's being seen on Bus 002 Device 003 Port 2-1 as. ID 18d1:9302 Google Inc. where the previous one never changed from the generic. Since I last posted on this thread, I've also changed my Unraid set up from being Ryzen based to using a z490 + i5 10400 Being at the, "doing what Ed (of SpaceInvaderOne fame) tells me to do, but being otherwise fairly clueless", end of the Unraid user spectrum and feeling pretty confused trying to make sense of the Frigate documentation, and having searched in vain for Unraid specific tutorials, written or video based . . . . 1) Can someone please tell me what order to work through the setting up of the configuration file? 2) Is there anything specific to Unraid that doesn't apply to Docker on, for e.g. Debian, I should be aware of? Knowing this will help me extrapolate info from tutorials for other systems. 3) I have a 10th gen (i5 10400) CPU with an iGPU - do I need or should I be making this available to Frigate in terms of hardware acceleration to work in partnership with the Google Coral TPU. I think this is so the TPU does object detection, while the iGPU does everything else more efficiently than the CPU? 4) Is it best practice to save and restart Frigate after making a change / addition to the config or to get all sections of the config set up as best I can before saving and testing? i.e. how interdependent are the various sections? Would the absence of a particular section cause it to crash or simply not work optimally? Thanks Quote Link to comment
only-university6482 Posted March 18 Share Posted March 18 (edited) 38 minutes ago, awediohead said: So having sent back a dud USB Coral TPU, I got a replacement and it's being seen on Bus 002 Device 003 Port 2-1 as. ID 18d1:9302 Google Inc. where the previous one never changed from the generic. Since I last posted on this thread, I've also changed my Unraid set up from being Ryzen based to using a z490 + i5 10400 Being at the, "doing what Ed (of SpaceInvaderOne fame) tells me to do, but being otherwise fairly clueless", end of the Unraid user spectrum and feeling pretty confused trying to make sense of the Frigate documentation, and having searched in vain for Unraid specific tutorials, written or video based . . . . 1) Can someone please tell me what order to work through the setting up of the configuration file? 2) Is there anything specific to Unraid that doesn't apply to Docker on, for e.g. Debian, I should be aware of? Knowing this will help me extrapolate info from tutorials for other systems. 3) I have a 10th gen (i5 10400) CPU with an iGPU - do I need or should I be making this available to Frigate in terms of hardware acceleration to work in partnership with the Google Coral TPU. I think this is so the TPU does object detection, while the iGPU does everything else more efficiently than the CPU? 4) Is it best practice to save and restart Frigate after making a change / addition to the config or to get all sections of the config set up as best I can before saving and testing? i.e. how interdependent are the various sections? Would the absence of a particular section cause it to crash or simply not work optimally? Thanks Have you installed portainer app? I'd advise doing that so you can easily view all the paths, env variables and settings easily. Much easier to make updates. Add device in the unraid frigate app settings as /dev/bus/usb (in portainer you can make sure this is mapped) and extra parameters: --gpus=all --shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=100000000 --restart unless-stopped config.yaml: detectors: coral: type: edgetpu device: usb Not sure if I did much else to get the tpu usb going tbh. Edited March 18 by only-university6482 1 Quote Link to comment
awediohead Posted March 19 Share Posted March 19 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 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.