question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Coral USB not detected during boot of PI4 (0.80/Home Assistant) - requires manual restart of Frigate

See original GitHub issue

I’m running HASSOS (x64) on PI4 booting from SSD. Frigate Beta 0.8

Coral config:

detectors:
  coral:
    type: edgetpu
    device: usb

When I reboot HASSOS, the coral device is not detected:

 * Starting nginx nginx
   ...done.
Matplotlib is building the font cache; this may take a moment.
frigate.app                    INFO    : Creating directory: /tmp/cache
frigate.app                    INFO    : Camera processor started for Voordeur: 37
detector.coral                 INFO    : Starting detection process: 35
frigate.edgetpu                INFO    : Attempting to load TPU as usb
frigate.app                    INFO    : Capture process started for Voordeur: 39
ffmpeg.Voordeur.clips          ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono
ffmpeg.Voordeur.detect         ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x5583d2ec10] moov atom not found
/media/frigate/recordings/Voordeur-20201215093539.mp4: Invalid data found when processing input
frigate.record                 INFO    : bad file: Voordeur-20201215093539.mp4
frigate.edgetpu                INFO    : No EdgeTPU detected. Falling back to CPU.

Just restarting frigate will solve the problem:

 * Starting nginx nginx
   ...done.
frigate.app                    INFO    : Creating directory: /tmp/cache
detector.coral                 INFO    : Starting detection process: 36
frigate.app                    INFO    : Camera processor started for Voordeur: 39
frigate.edgetpu                INFO    : Attempting to load TPU as usb
frigate.edgetpu                INFO    : TPU found
frigate.app                    INFO    : Capture process started for Voordeur: 41
ffmpeg.Voordeur.clips          ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono
ffmpeg.Voordeur.detect         ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x55b10edc10] moov atom not found
/media/frigate/recordings/Voordeur-20201215094501.mp4: Invalid data found when processing input
frigate.record                 INFO    : bad file: Voordeur-20201215094501.mp4

Not sure if it is possible to do some retries when a previous run instance was using a coral device

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:16 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
blakeblackshearcommented, Dec 22, 2020

Simple enough. I can add a fallback_to_cpu option that defaults to true if you dont have anything defined and defaults to false if you have the edge tpu defined.

0reactions
blakeblackshearcommented, Jan 23, 2021

RC4 will now completely exit the container if the detection process stops

Read more comments on GitHub >

github_iconTop Results From Across the Web

frigate Coral USB not detected during boot of PI4 (0.80/Home ...
frigate Coral USB not detected during boot of PI4 (0.80/Home Assistant) - requires manual restart of Frigate Python. I'm running HASSOS (x64) on...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found