Why my HomeAssistant can't recognize google Coral accelerator

Configuration Zigbee
1

For some time now, I’ve been trying to set up a local AI-based video surveillance system using Home Assistant running on a Raspberry Pi, together with Frigate as an NVR solution. The idea was simple: offload object detection to a Google Coral TPU to reduce CPU load and improve performance.

On paper, everything looks straightforward — install Frigate, configure it in Home Assistant, add the Coral hardware accelerator, and everything should just work. However, in practice, I ran into issues almost immediately.

What I did

My Home Assistant instance is running on a Raspberry Pi, and everything else works fairly stable. I installed Frigate and started with the basic configuration. The goal was to enable the Google Coral as the AI accelerator for object detection.

But the problem started right at device detection.

The issue

No matter how I configure it, Frigate cannot “see” the Google Coral. The accelerator simply does not appear in the available options, or it fails to initialize.

I tried:

  • checking the USB device connection
  • restarting Home Assistant
  • reviewing the Frigate YAML configuration
  • inspecting logs for errors

But the result is always the same — the Coral is not detected as an available accelerator.

Current state

Home Assistant runs normally on the Raspberry Pi, and Frigate starts without issues, but everything falls back to CPU processing because hardware acceleration cannot be enabled.

In practice, this means:

  • higher CPU load on the Raspberry Pi
  • slower video stream processing
  • no benefit from the Coral TPU as intended

Conclusion

For now, I’m sticking with CPU-based detection until I figure out the root cause of the issue. It could be related to drivers, USB detection problems with the Coral device, or the Frigate configuration within the Home Assistant setup on Raspberry Pi.

If anyone has a similar setup and knows what might be causing this problem — any help would be appreciated.

2

Try this "search string" in Firefox#Google
( Frigate cannot “see” the Google Coral in ha )

Do to curiosity i did

The Raspberry Pi 4 has known limitations when it comes to delivering enough power via its USB ports.

Follow these specific steps for Raspberry Pi 4 to solve the problem:

1. Move Coral to a powered USB hub (Important)

Raspberry Pi 4 can deliver 1200mA total to all USB ports together. A Google Coral USB pulls extremely much power under load and crashes or disconnects immediately if it doesn't get enough.

Solution: Connect your Google Coral to a externally powered USB 3.0 hub (a hub with its own power cable in the wall), then connect the hub to Pi 4.

Port: Make sure the hub is plugged into one of the Blue USB 3.0 ports on your Pi 4.

2. Turn off "Protection Mode" in Home Assistant

If you are running Frigate as an Add-on (add) in Home Assistant OS, the system blocks hardware access by default.

Go to Settings > Additions > Frigate.

Click on the tab Configuration (or info depending on the version).

Find the switch for Protection mode (Protection mode) and hit OFF the one.

Start over Frigate add-on.

3. Check config (frigate.yml)

For a USB-connected Coral on a Raspberry Pi, your configuration should look exactly like this. Do not add any extra lines as "model":

yaml

detectors:
  coral:
    type: edgetpu
    device: usb


Use the code with caution.

4. Replace the USB cable

The original cable that comes with Google Coral is apparently of quite low quality and has difficulty with the power supply of a Pi 4. Try switching to a stable, short USB-C to high-quality USB-A cable (labeled for USB 3.0/Data transfer).

And here is my second Search
RPI 4 + Frigate + Coral TPU not detected . ( First in this Forum )

3

In addition to the excellent points mentioned by @boheme61, can you actually see the Coral device listed if you search for it under Settings > System > Hardware > System Hardware? It should probably be listed under dev/tty or dev/acm if it's a USB device.

If HA can't see the device, then neither can Frigate.

4

Turn OFF Protection mode !!! Restart Frigate !