Google Coral

Installation
1

Hello

I have a problem with installation with Google Coral.
Let me tell what I know. I have a Odroid N2+
That’s all

I’m from the DOS generation.
I know DOS, Basic, Pascal and Assembler but I know nothing to a little of Linux.
So if you ask me what OS I have and version, the answer is: I don’t know.
If you ask it, tell me how I can get this info.
And be a little patient with me, at my age it goes a little slower (74)

Now the problem:
I have Frigate wordking but get the warning:
CPU detectors are not recommended and should only be used for testing or for trial purposes.

I bought the Google Coral and want to install it.

In “Terminal” I enter: echo “deb Index of /apt// coral-edgetpu-stable main” | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list

The reply is: tee: /etc/apt/sources.list.d/coral-edgetpu.list: No such file or directory
deb Index of /apt// coral-edgetpu-stable main

Schermafbeelding 2022-11-27 160318
Schermafbeelding 2022-11-27 1603181346×146 39.5 KB

So I’m missing something.
Do I something wrong?

I will be very thankfull when you help me trou the problem(s).

Jos

2

Specifically, which Google coral do you have? The instructions are different.

3

If you ask it, tell me how I can get this info.

On the website where I bought, I read:

Google Edge TPU ML accelerator coprocessor (?)

4

The two main types are USB or PCIE of some form factor.

5

The question not understood.
It’s USB

6

You don’t need to do any of that to run the USB coral, just edit your frigate config

detectors:
  coral:
    type: edgetpu
    device: usb
2 Likes
7

Thanks working.

I thought I did it ones.
You see it’s the age.

Thanks again.

2 Likes
8

Hello everyone,
I have the same issue as Strikky.
I am not sure that I do not need any drivers or specific configuration with Home Assistant Terminal, but when I run Frigate (Full Access) the processor usage is very high (62%-90%). I have google accelerator (Get started with the USB Accelerator | Coral) which is connectet by USB 3.0 to the odroid N2+.
How the odroid N2+ or Frigate (Full Access) know which processor resorces should use?

My frigate.yml has included

Detectors:
coral:
type: edgetpu
device: usb

but maybe this information should be in specific order?
I will be grateful for any help.

Rafal

9

Hello. I have a PCIe M2 Coral TPU. ¿How can install the drivers on HASSIO?

10

they are already installed

11

frigate.detectors.plugins.edgetpu_tfl ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors

I’m using a NUC11 with a Celeron. The TPU is connected to the port where the WiFi module was previously connected. Is it necessary to configure anything else in the BIOS parameters? During the first boot, I lost the LAN connection, so I entered the BIOS and disabled the WiFi.

12

Make sure the device shows up in the hardware list

13

Okay, I checked the hardware list and the Coral device is not showing up. Maybe a BIOS parameter needs to be changed?

14

I’m completely lost on this issue. If I disable the Bluetooth and WiFi controllers in the BIOS, the HAOS starts correctly, but the Coral TPU is not detected. If I enable the Bluetooth and WiFi controllers in the BIOS setup, the HAOS starts, but I lose the Ethernet connection. When I enter the command “net info” in the CLI, this is the result:

IMG_2894
IMG_28941920×2560 206 KB

15

I’m not sure this is correct? My Coral USB worked without it showing in the hardware list (although I did look for it for a day in the hardware list before checking the Frigate “system” tab only to find it there?

16

Fixed after some time spent reinstalling HAOS and restoring a complete backup.

17

Can i ask how you fixed it.
I have the coral m2 inserted in de slot for the wifi module and enabled it it in the bios.
I cannot see it in the hardware list.
I run hoas in a vm on truenas in priveliged mode.
I can see it if n truenas as pci 00:05:00,when i put in pci: 5 in the config it is still not reconized.

18

Hi,
I’ve bought a google coral USB.
Connected it to the HA Server and altered the frigate config as red on many posts.
But… frigate claims: No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
Could you help me?
I’ve tried another USB port and another USB cable. Nothing works…
Soma say I should see it in HW list. I couldn’t find it there eighter…

19

what is the host device? also, what is your frigate config

20

Had a heck of a time with this as well but got it working. TLDR solution: cold boot TPU and device Frigate is installed on. If this doesn’t work, maybe there is a gem below:

Equipment and software used: Home Assistant Yellow, raspberry pi CM5 (Core 2025.7.4 Supervisor 2025.08.1 Operating System 15.2 Frontend 20250702.3).
Frigate version 0.16.0 (16Aug2025) - Installation using “Frigate (Full Access)” version with “Protection Mode” disabled so Frigate can access the TPU. Special note: Also in Aug2025 Home Assistant made a major upgrade to it’s core and OS - which also broke Frigate and a fix is pending from Frigate’s side. It’s recommended to never upgrade HA core/OS to major version changes for 3-6 months. Standard operating procedure for major OS changes really. Also note: “The Frigate config directory for add-on users was changed from the Home Assistant config directory to the add-on config directory. With this change, the Frigate config file and database are now part of the add-on backup taken by Home Assistant, no longer needing to backup them manually. Note that only backups after 0.16 will benefit of this change.… In the new directory, the Frigate config file will be named config.yml rather than frigate.yml.”

Adding the TPU:
Plugged in google coral TPU to a powered hub** using stock USB cable it came with. Coral TPU shows a solid white light meaning it’s powered. Added code to frigate’s “config.yml” file:

"

detectors:
  coral:
    type: edgetpu
    device: usb

"

Rebooted HA. Nothing in Frigate logs mentioning “frigate.detectors”. Unplug TPU, reboot HA, plug back in TPU, reboot HA. Still nothing.

Checked HA hardware list. Google Coral TPU should show as “1a6e:089a Global Unichip Corp. device.” (source). I search 1a6e and it comes up as “1a6e_089a”. So I know HA sees it. According to Frigate documentation: "Once an application like Frigate runs an inference, the device will be initialized and should be listed with the Google Inc. ID 18d1:9302. "

In the final hail-mary I cold boot*** everything; Home assistant yellow and powered USB hub. Voila! Frigate detects it in the system page. “Detect Inference Speed” and “Detector CPU usage” previously showed as “cpu” now shows as “coral”.

CPU usage down from 120% “screaming” down to coral’s 22%. Inference speed was previously in the 300-450ms range, is now down to about 45-55ms (single camera). My understanding is because Home Assistant Yellow is USB 2.0, that’s probably the best I’ll ever see. And likely max camera usage I can have is maybe 5-6 cameras (fine for my purposes but in the future I’ll be purchasing a better carrier board!!). Overall system CPU usage down from 80-100% all the time for one camera even when not detecting anything back down to a more reasonable 40-50%. HA hardware list now shows “18d1_9302” showing that Frigate initialized it.

Frigate’s logs showing detection of TPU:

2025-08-23 15:36:21.093265946  [2025-08-23 09:36:21] detector.coral                 INFO    : Starting detection process: 265
2025-08-23 15:36:21.095092657  [2025-08-23 09:36:21] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2025-08-23 15:36:25.728167660  [2025-08-23 09:36:25] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found

Frigate’s system page also now shows “System is healthy” in bottom right hand corner.

** Hub: Waveshare 4-Ch USB 3.2 Gen1, powered from PoE+ splitter 12V output 5.5x2.1mm barrel plug 2A (24W) - apparently max TPU draw is 900mA or 4.5W at 5V.
*** The cold boot; IT’s super power. It’s amazing how often this fixes things. I’m still amazed after 25+ years :joy:.