[Detector Support]: Coral stopped working on 0.16.1

[iBobik]

Describe the problem you are having

I’ve just updated from 0.16.0 to 0.16.1 and Coral stopped working and Frigate is in the restart loop.

Version

0.16.1-e664cb2

Frigate config file

Cannot get it without Frigate started.

docker-compose file or Docker CLI command

HA OS addon

Relevant Frigate log output

2025-09-17 13:45:28.022665542  [2025-09-17 15:45:28] frigate.app                    INFO    : Starting Frigate (0.16.1-e664cb2)
2025-09-17 13:45:28.025501743  [2025-09-17 15:45:28] frigate.app                    INFO    : Creating directory: /tmp/cache
2025-09-17 13:45:28.093978622  [2025-09-17 15:45:28] peewee_migrate.logs            INFO    : Starting migrations
2025-09-17 13:45:28.100046238  [2025-09-17 15:45:28] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-09-17 13:45:28.128490503  [2025-09-17 15:45:28] frigate.app                    INFO    : Recording process started: 502
2025-09-17 13:45:28.157993822  [2025-09-17 15:45:28] frigate.app                    INFO    : Review process started: 511
2025-09-17 13:45:28.176141836  [2025-09-17 15:45:28] frigate.app                    INFO    : go2rtc process pid: 113
2025-09-17 13:45:28.235605230  [2025-09-17 15:45:28] detector.coral                 INFO    : Starting detection process: 527
2025-09-17 13:45:28.245910231  [2025-09-17 15:45:28] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2025-09-17 13:45:28.303774980  [2025-09-17 15:45:28] frigate.app                    INFO    : Output process started: 546
2025-09-17 13:45:31.596729491  2025/09/17 15:45:31 [error] 219#219: *34 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2025-09-17 13:45:31.596801241  2025/09/17 15:45:31 [error] 219#219: *34 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2025-09-17 13:45:32.184003091  2025/09/17 15:45:32 [error] 219#219: *36 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "ccab4aaf-frigate-fa:5000"
2025-09-17 13:45:32.184075425  2025/09/17 15:45:32 [error] 219#219: *36 auth request unexpected status: 502 while sending to client, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", host: "ccab4aaf-frigate-fa:5000"
2025-09-17 13:45:32.294379264  [2025-09-17 15:45:32] frigate.app                    INFO    : Camera processor started for front: 614
2025-09-17 13:45:32.327622085  [2025-09-17 15:45:32] frigate.app                    INFO    : Camera processor started for left: 616
2025-09-17 13:45:32.362892597  [2025-09-17 15:45:32] frigate.app                    INFO    : Camera processor started for right: 617
2025-09-17 13:45:32.479995852  [2025-09-17 15:45:32] frigate.app                    INFO    : Camera processor started for rear: 628
2025-09-17 13:45:32.584206993  [2025-09-17 15:45:32] frigate.app                    INFO    : Capture process started for front: 659
2025-09-17 13:45:32.624975780  [2025-09-17 15:45:32] frigate.app                    INFO    : Capture process started for left: 669
2025-09-17 13:45:32.676379154  [2025-09-17 15:45:32] frigate.app                    INFO    : Capture process started for right: 678
2025-09-17 13:45:32.808849346  [2025-09-17 15:45:32] frigate.app                    INFO    : Capture process started for rear: 689
2025-09-17 13:45:33.820384656  [2025-09-17 15:45:33] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-09-17 13:45:35.227763646  [2025-09-17 15:45:35] frigate.api.fastapi_app        INFO    : FastAPI started
2025-09-17 13:45:52.844843534  127.0.0.1 - - [17/Sep/2025:15:45:52 +0200] "" 400 0 "-" "-" "-"
2025-09-17 13:45:53.852238741  [2025-09-17 15:45:53] frigate.detectors.plugins.edgetpu_tfl ERROR   : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
2025-09-17 13:45:53.864728054  Process detector:coral:
2025-09-17 13:45:53.864740888  Traceback (most recent call last):
2025-09-17 13:45:53.864744679    File "/usr/local/lib/python3.11/dist-packages/tflite_runtime/interpreter.py", line 166, in load_delegate
2025-09-17 13:45:53.864747304      delegate = Delegate(library, options)
2025-09-17 13:45:53.864749638                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-09-17 13:45:53.864752846    File "/usr/local/lib/python3.11/dist-packages/tflite_runtime/interpreter.py", line 104, in __init__
2025-09-17 13:45:53.864755179      raise ValueError(capture.message)
2025-09-17 13:45:53.864756929  ValueError
2025-09-17 13:45:53.864758388  
2025-09-17 13:45:53.864761305  During handling of the above exception, another exception occurred:
2025-09-17 13:45:53.864762763  
2025-09-17 13:45:53.864764805  Traceback (most recent call last):
2025-09-17 13:45:53.864768013    File "/usr/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap
2025-09-17 13:45:53.864769763      self.run()
2025-09-17 13:45:53.864772680    File "/opt/frigate/frigate/util/process.py", line 41, in run_wrapper
2025-09-17 13:45:53.864774721      return run(*args, **kwargs)
2025-09-17 13:45:53.864908306             ^^^^^^^^^^^^^^^^^^^^
2025-09-17 13:45:53.864913265    File "/usr/lib/python3.11/multiprocessing/process.py", line 108, in run
2025-09-17 13:45:53.864917056      self._target(*self._args, **self._kwargs)
2025-09-17 13:45:53.864919973    File "/opt/frigate/frigate/object_detection/base.py", line 112, in run_detector
2025-09-17 13:45:53.864923181      object_detector = LocalObjectDetector(detector_config=detector_config)
2025-09-17 13:45:53.864926098                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-09-17 13:45:53.864930765    File "/opt/frigate/frigate/object_detection/base.py", line 57, in __init__
2025-09-17 13:45:53.864933390      self.detect_api = create_detector(detector_config)
2025-09-17 13:45:53.864935723                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-09-17 13:45:53.864994349    File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector
2025-09-17 13:45:53.864998141      return api(detector_config)
2025-09-17 13:45:53.865000474             ^^^^^^^^^^^^^^^^^^^^
2025-09-17 13:45:53.865003391    File "/opt/frigate/frigate/detectors/plugins/edgetpu_tfl.py", line 42, in __init__
2025-09-17 13:45:53.865008932      edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
2025-09-17 13:45:53.865012141                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-09-17 13:45:53.865015641    File "/usr/local/lib/python3.11/dist-packages/tflite_runtime/interpreter.py", line 168, in load_delegate
2025-09-17 13:45:53.865082142      raise ValueError('Failed to load delegate from {}\n{}'.format(
2025-09-17 13:45:53.865086808  ValueError: Failed to load delegate from libedgetpu.so.1.0
2025-09-17 13:45:53.865088558  
2025-09-17 13:46:03.817310995  [2025-09-17 15:46:03] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting Frigate...

Install method

Home Assistant Add-on

Object Detector

Coral

Screenshots of the Frigate UI's System metrics pages

It stops before I was able to do anything in the UI.

Any other information that may be helpful

Tried to power off whole system.

[inkeep-ai-assistant[bot]]

Your log shows Frigate is unable to detect the Coral Edge TPU and throws a "Failed to load delegate from libedgetpu.so.1.0" error, which causes the process to exit and restart. This type of error can occur if the Coral device is not passed through properly, the driver is missing, or the device is not initialized by the OS(1)(2)(3)(4).

Recommended steps:

1. Check Coral Connection: Ensure the Coral is securely connected to the host and visible to the OS. If USB, try unplugging and replugging, or a different port. For PCIe/M.2, confirm it appears in the device list(1)(2).

2. Restart Host: Sometimes, especially on some NAS and embedded systems, a full reboot (not just a container restart) is needed to properly initialize the Coral(5).

3. Home Assistant Add-on: Make sure you have hardware access configured. For USB Coral, the add-on must have access to the USB device; for PCIe/M.2 Coral, the PCI device must be mapped(1)(2).

4. Config Example: For a USB Coral, the detector config should look like:

   detectors:
     coral:
       type: edgetpu
       device: usb

   For PCIe/M.2:

   detectors:
     coral:
       type: edgetpu
       device: pci

   Multiple Corals require unique names and device assignments (e.g., usb:0, pci:0)(1)(2).

5. Troubleshooting: If the Coral is detected only after unplug/replug, or after a reboot, this is a known hardware/driver initialization issue on some systems (especially older kernels or NAS devices). The workaround is to leave the TPU plugged in, reboot the system, and then start the container(5).

6. If all else fails: Temporarily switch to CPU detection to restore Frigate operation:

   detectors:
     cpu1:
       type: cpu
       num_threads: 3

   This is not recommended for performance, but can help you regain access(2).

If you need further help, check these resources:

• Supported Hardware
• Recommended hardware
• Documentation update for Synology NAS + Coral TPU to resolve coral not connecting for older NAS's running DSM 7.2.1

Would you like a general answer based on my knowledge instead?

📚 Sources:

1. Supported Hardware
2. Supported Hardware
3. [Detector Support]: ValueError: Failed to load delegate from libedgetpu.so.1.0
4. [Detector Support]: "TPU found" followed by "No EdgeTPU was detected"
5. Documentation update for Synology NAS + Coral TPU to resolve coral not connecting for older NAS's running DSM 7.2.1

---

Have another question? Just tag @inkeep.

[NickM-27]

If you are using the full access addon then you need to disable protected mode

[iBobik]

Thank you for quick and correct answer:-)

[hawkeye217]

See the FAQ, Upgrade issues question 3.