[Support]: Coral disconnects #20799
Replies: 4 comments
-
|
Based on the error logs, Frigate is failing to detect your USB Coral TPU after 24-48 hours of operation. The error Common USB Coral Detection IssuesSeveral factors can cause USB Coral detection to fail: Power IssuesThe USB Coral can draw up to 900mA, which may be too much for some USB ports(1). Try these steps:
Device Access in DockerWhen running Frigate in Docker, you must ensure both device IDs are mapped (the Coral has different IDs when uninitialized vs initialized)(1). Your current configuration maps Cable QualitySome users have reported that switching from the included cable to a different one fixed intermittent detection issues entirely(1). Recommended Actions
Since the issue started with version 0.16.2 and wasn't present in 0.16.0/0.16.1, you may also want to check the Frigate release notes for any changes related to EdgeTPU detection between these versions. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
A reboot of the physical host has brought Frigate back up but with even stranger disk usage, du -sh is still showing a 4.0TB recordings directory.
|
Beta Was this translation helpful? Give feedback.
-
|
sync recordings seems to have brought the usage to something realistic. Now I'll wait for another crash. |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
For context this is a docker install running on a physical machine, this is not a Home Assistant Add-on (seen similar issues with HA add-ons). Frigate was running reliably on 16 and 16.1, running Coral as a USB TPU.
Every day or two with 16.2 Frigate crashes, it looks like its failing to detect the TPU.
Rebooting Frigate doesn't help, rebooting the physical host temporarily fixes it,
Steps to reproduce
Reboot the physical client.
Wait 24-48 hours.
All camera feeds down, webUI difficult to view due to restarts
Version
16.2
In which browser(s) are you experiencing the issue with?
Chrome 141.0.7390.125, Chrome for Android
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Can't see these due to the constant reboots during the crash.Operating system
Other Linux
Install method
Docker Compose
Network connection
Wired
Camera make and model
Hikvision mainly
Screenshots of the Frigate UI's System metrics pages
Not accessible during the crash
Any other information that may be helpful
lsusb shows the Coral
Beta Was this translation helpful? Give feedback.
All reactions