Coral M.2 Dual Edge TPU PCIe on Raspberry 5, HAOS 14.2 & frigate AddOn stopped #3867
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
Describe the issue you are experiencing
I have installed Coral M.2 Dual Edge TPU PCIe on Raspberry 5, after than I installed HAOS with frigate Add-on, for the first time.
Problem:
I start frigate in HAOS-Add-on, after a few minutes frigate stopped.
See logs below.
What can I do?
HAOS_frigate_AddOn_SystemInfo.txt
ccab4aaf_frigate-fa_2025-02-09T23-45-05.log
frigate-Configuration
/homeassistant/frigate.yml
Multiple PCIE/M.2 Corals
detectors:
coral1:
type: edgetpu
device: pci:0
coral2:
type: edgetpu
device: pci:1
The same configuration works fine in a Frigate-Docker without HAOS.
HAOS – Einstellungen - System – Hardware – gesamte Hardware
http://:8123/config/hardware
Subsystem:
apex
Gerätepfad:
/dev/apex_0
Attribute:
DEVNAME: /dev/apex_0
DEVPATH: >-
/devices/platform/axi/1000110000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/0000:02:03.0/0000:03:00.0/apex/apex_0
MAJOR: '120'
MINOR: '0'
SUBSYSTEM: apex
Subsystem:
apex
Gerätepfad:
/dev/apex_1
Attribute:
DEVNAME: /dev/apex_1
DEVPATH: >-
/devices/platform/axi/1000110000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/0000:02:07.0/0000:04:00.0/apex/apex_1
MAJOR: '120'
MINOR: '1'
SUBSYSTEM: apex
What operating system image do you use?
rpi5-64 (Raspberry Pi 5 64-bit OS)
What version of Home Assistant Operating System is installed?
14.2
Did the problem occur after upgrading the Operating System?
No
Hardware details
System environment:
HAOS & Frigate (Full Access) Add-On
rpi5-64
8 GB RAM
Coral M.2 Dual Edge TPU
Home Assistant
Core 2025.2.0
Supervisor 2025.02.0
Operating System 14.2
Frontend 20250205.0
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
2025-02-10 00:10:09.862 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete 2025-02-10 00:10:09.862 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running 2025-02-10 00:10:09.862 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete 2025-02-10 00:10:15.840 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:10:15.907 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:10:20.867 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:10:25.905 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:11:00.853 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:11:00.863 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:11:00.867 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:11:00.871 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:11:00.875 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:11:00.879 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:11:01.125 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Connection timeout to host http://172.30.33.2:5000/ws 2025-02-10 00:11:04.437 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:11:08.981 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:11:08.987 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:11:08.992 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:5000 ssl:default [Connect call failed ('172.30.33.2', 5000)] 2025-02-10 00:39:43.051 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token 2025-02-10 00:43:27.161 WARNING (MainThread) [supervisor.docker.addon] Frigate (Full Access) running with disabled protected mode! 2025-02-10 00:43:27.169 INFO (SyncWorker_7) [supervisor.docker.manager] Cleaning addon_ccab4aaf_frigate-fa application 2025-02-10 00:43:27.708 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/blakeblackshear/frigate with version 0.15.0 2025-02-10 00:43:27.845 INFO (MainThread) [supervisor.api.middleware.security] /network/interface/default/info access from ccab4aaf_frigate-fa 2025-02-10 00:44:31.486 ERROR (SyncWorker_2) [supervisor.docker.manager] Container addon_ccab4aaf_frigate-fa is not running 2025-02-10 00:44:52.205 WARNING (MainThread) [supervisor.api.addons] Changing protected flag for ccab4aaf_frigate-fa! 2025-02-10 01:09:11.531 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running 2025-02-10 01:09:11.531 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/systemAnything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Network Configuration
Recorder
Additional information
No response
The text was updated successfully, but these errors were encountered: