Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

coral TPU not detected after upgrade to v0.14.0 #183

Open
Matthiasfranck opened this issue Aug 30, 2024 · 8 comments
Open

coral TPU not detected after upgrade to v0.14.0 #183

Matthiasfranck opened this issue Aug 30, 2024 · 8 comments

Comments

@Matthiasfranck
Copy link

I use frigate full access in HAS. After upgrading from 0.13.2 to 0.14.0, my coral edge TPU is not detected anymore.

The issue looks very similar to blakeblackshear/frigate#3890

I downgraded frigate using a HAS backup and everything started to work as normal.

I want to share this as people are probably not yet aware of the issue.

@NickM-27
Copy link
Contributor

nothing changed in terms of how the coral is interacted with, another user posted something similar and it was because they forgot to disable protected mode and they were using the full access addon

@Matthiasfranck
Copy link
Author

I was also running without protected mode.

@StefanTT
Copy link

StefanTT commented Sep 4, 2024

I am also fighting with this problem.

Home-Assistant with the Frigate addon freshly installed, version 0.14.1.
Disabled protected mode.

The detector configuration is like this:

detectors:
  coral:
    type: edgetpu
    device: usb

TPU is not detected and Frigate stops.

Running frigate on the same machine in an LXC container worked for months now, so the TPU is reachable and working. I stopped the frigate LXC container before testing.

@StefanTT
Copy link

StefanTT commented Sep 4, 2024

I found the issue. I read somewhere that the Edge TPU is very picky about the power supply. So I unplugged the external USB devices (bluetooth and thread adapter) and now Frigate finds the TPU.

@Matthiasfranck maybe that's your issue too?

@Matthiasfranck
Copy link
Author

I have a zwave and zigbee dongle attached. I can however use a powered usb hub to plug the tpu in.

Anyway it is still strange that it only happens when updating to newer version.

@StefanTT
Copy link

StefanTT commented Sep 6, 2024

The update might have changed how Frigate interacts with the TPU on startup, drawing a bit more power now on start. I did some testing. All works fine when I unplug bluetooth and thread on boot and plug them in later. I will use a powered hub for the two sticks as the TPU is inside the server.

@Matthiasfranck
Copy link
Author

@NickM-27 wrote

nothing changed in terms of how the coral is interacted with

But ok, I will test it later again. I have an usb coral, so only thing I can do is use powered USB hub and add my zigbee, zwave and coral to it.

@tung256
Copy link

tung256 commented Oct 1, 2024

@Matthiasfranck it's a shame there is no way to revert to a older versions. i updated from v12 to v14 and instantly regretted. i do have a hard drive back up with v12 and HA OS, but that was almost 2 years ago. a lot of things have changed in my house since then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants