At first, I also had problems getting HA Blue to recognize the USB. Maybe try once again but the disable protection mode. If still not recognized, try another port.
OK so that’s seems to be normal then, still not clear why HA can’t see the TPU
Thanks for your support!
Have you tried disabling protection mode?
Okay. I suggest you post your problem here-
Maybe others have also experienced the same problem with you and know how to solve it.
Will do thanks for your time and support!
1 Like
Any luck with this? I have the m.2 stick in a case and plugged in via USB. HA Blue hasn’t seen it yet.
Did you happen to get anything from your question on that thread? I’m having the same issue and also posted there. Not sure how to further diagnose the issue.
Ran into this while setting up mine just now. Worked after I disabled protection mode under Settings/Add-ons/Frigate
1 Like
Hello,
tell me how did you get it to work? I have an odroid m2+, same as HA blue, but can’t get the TPU to work. Not even with an external USB hub.
Thanks
Hello,
any tips on how to get the Coral USB working?
Even frigates without protection mode does not recognize the TPU?
Thanks
I’m having a similar problem. I am running HA on an old MacPro and VirtualBox. The device is seen by VB however when I include the detector in Frigate, it says it’s not there.
[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-11-01 05:33:57] frigate.app INFO : Starting Frigate (0.11.1-2eada21)
[2022-11-01 05:33:57] frigate.app INFO : Creating directory: /tmp/cache
Starting migrations
[2022-11-01 05:33:57] peewee_migrate INFO : Starting migrations
There is nothing to migrate
[2022-11-01 05:33:57] peewee_migrate INFO : There is nothing to migrate
[2022-11-01 05:33:57] frigate.app INFO : Output process started: 213
[2022-11-01 05:33:57] frigate.mqtt INFO : Turning off detection for Dining via mqtt
[2022-11-01 05:33:57] frigate.mqtt INFO : Turning on snapshots for Front-door via mqtt
[2022-11-01 05:33:57] ws4py INFO : Using epoll
[2022-11-01 05:33:57] detector.coral INFO : Starting detection process: 212
[2022-11-01 05:33:57] frigate.edgetpu INFO : Attempting to load TPU as usb
[2022-11-01 05:33:57] frigate.mqtt INFO : Turning on snapshots for Garten-house via mqtt
[2022-11-01 05:33:57] frigate.mqtt INFO : Turning on snapshots for Garage via mqtt
[2022-11-01 05:33:57] frigate.app INFO : Camera processor started for Dining: 219
[2022-11-01 05:33:57] frigate.mqtt INFO : Turning on snapshots for Drive-way via mqtt
[2022-11-01 05:33:57] frigate.app INFO : Camera processor started for Garage: 222
[2022-11-01 05:33:57] frigate.edgetpu ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
Process detector:coral:
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.9/multiprocessing/process.py”, line 315, in _bootstrap
self.run()
File “/usr/lib/python3.9/multiprocessing/process.py”, line 108, in run
self._target(*self._args, **self._kwargs)
File “/opt/frigate/frigate/edgetpu.py”, line 135, in run_detector
object_detector = LocalObjectDetector(
File “/opt/frigate/frigate/edgetpu.py”, line 43, 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
[2022-11-01 05:33:57] frigate.app INFO : Camera processor started for Front-door: 223
[2022-11-01 05:33:57] frigate.mqtt INFO : Turning on snapshots for Patio via mqtt
[2022-11-01 05:33:57] frigate.app INFO : Camera processor started for Garten-house: 225
[2022-11-01 05:33:57] frigate.app INFO : Camera processor started for Drive-way: 227
[2022-11-01 05:33:57] frigate.app INFO : Camera processor started for Patio: 229
[2022-11-01 05:33:57] frigate.app INFO : Capture process started for Dining: 232
[2022-11-01 05:33:57] frigate.app INFO : Capture process started for Garage: 233
[2022-11-01 05:33:57] frigate.app INFO : Capture process started for Front-door: 236
[2022-11-01 05:33:57] frigate.app INFO : Capture process started for Garten-house: 246
[2022-11-01 05:33:57] frigate.app INFO : Capture process started for Drive-way: 253
[2022-11-01 05:33:57] frigate.app INFO : Capture process started for Patio: 258
[2022-11-01 05:33:57] ws4py INFO : Using epoll
Thought I had this working. Found that I had to load the VBox Extension Pack to get USB 3.0 loaded. Doesn’t seem to matter though.
If I delete the USB device Filters, no difference.
If I disable protection mode, no difference
Help!
I’m running HA on a HA blue. In order for Frigate addon to recognize my Coral USB I had to:
- Uninstall “Frigate” addon and replace it with “Frigate (Full Access)” addon.
- Unselect “Protection mode” on the Frigate (Full Access) addon page configuration->addons->Frigate (Full Access)
(I do not have any power issues. I’m running Coral on the top left USB and a Z-Wave controller on the bottom right.)
Also, remember that Frigate (Full Access) addon uses a different URL than the standard addon. The integration must probably be reinstalled in order to change the URL to http://ccab4aaf-frigate-fa:5000
1 Like
Thank you. I’m also running Full Access. My system is now working correctly. Seems the MacPro was cycling the USB port for some reason.
I alsao have the same issu, the Google coral is not reconized in Hardware…
