frigate: [Config Support]: Google Coral USB not found by FRIGATE
Describe the problem you are having
I am not able to make the FRIGATE detect my GOOGLE CORAL USB, for all the attempts I made it always appears written: No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
What I noticed in some forums was the detail referring to the HARDWARE ID of the pendrive is different from what FRIGATE looks for when it tries to locate a GOOGLE CORAL USB, the ID that is searched for would be the number: 18d1:9302 , since what is detected in my PC (I use UNRAID SERVER system) is the number : 1a6e:089a Global Unichip Corp.
How can I make FRIGATE be able to locate the GOOGLE CORAL USB flash drive plugged into the machine?
Version
Current version: 3.1
Frigate config file
mqtt:
host: 192.168.0.213
port: 1883
topic_prefix: frigate
client_id: frigate
user: roger561
password: roger561
stats_interval: 60
detectors:
coral:
type: edgetpu
device: usb
database:
path: /media/frigate/frigate.db
cameras:
back:
ffmpeg:
inputs:
- path: rtsp://admin:x1x2x3x4x5@192.168.0.65:554/Streaming/Channels/102/
roles:
- detect
Relevant log output
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2022-07-14 16:42:34] frigate.app INFO : Starting Frigate (0.10.1-83481af)
[2022-07-14 16:42:34] frigate.app INFO : Creating directory: /tmp/cache
Starting migrations
[2022-07-14 16:42:34] peewee_migrate INFO : Starting migrations
There is nothing to migrate
[2022-07-14 16:42:34] peewee_migrate INFO : There is nothing to migrate
[2022-07-14 16:42:34] frigate.app INFO : Output process started: 215
[2022-07-14 16:42:34] frigate.app INFO : Camera processor started for back: 218
[2022-07-14 16:42:34] ws4py INFO : Using epoll
[2022-07-14 16:42:34] frigate.app INFO : Capture process started for back: 219
[2022-07-14 16:42:34] ws4py INFO : Using epoll
[2022-07-14 16:42:34] detector.coral1 INFO : Starting detection process: 214
[2022-07-14 16:42:34] frigate.edgetpu INFO : Attempting to load TPU as usb
[2022-07-14 16:42:34] frigate.edgetpu ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
Process detector:coral1:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate
delegate = Delegate(library, options)
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in __init__
raise ValueError(capture.message)
ValueError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/opt/frigate/frigate/edgetpu.py", line 136, in run_detector
object_detector = LocalObjectDetector(
File "/opt/frigate/frigate/edgetpu.py", line 44, in __init__
edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate
raise ValueError('Failed to load delegate from {}\n{}'.format(
ValueError: Failed to load delegate from libedgetpu.so.1.0
Frigate stats
No response
Operating system
HassOS
Install method
HassOS Addon
Coral version
USB
Any other information that may be helpful
The camera image even appears even with this error, but the image is locked and I don’t realize that Google Coral is working, since it was not located.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 19
You will need to create the config.yaml file if you haven’t already. The Unraid app defaults it to /appdata/frigate/config.yaml checkout https://docs.frigate.video to setup
This is not true, every addon in HA OS is also in the Unraid app store. and the docker app for example supports all the same features
I use this with Unraid as well, is there any reason you are using frigate inside of the addon instead of through the frigate docker container? It will most likely be a lot easier that way since it doesn’t need to go through the VM