On a Debian 12 host running Home Assistant Supervised, the installer (linux.sh -> strix-frigate.sh) deploys its own Frigate + go2rtc with network_mode: host. They grab the ports the HA Frigate add-on needs (5000/8971/1984/8554), so the add-on gets stuck in Created and Supervisor goes supported: false.
Environment:
Debian 12, Docker 29.5.2, HA Supervised (Supervisor 2026.05.1, Core 2026.5.4), HA Frigate add-on 0.17.1 already installed.
What happens:
- Installer creates
strix, frigate (frigate:stable), go2rtc in /opt/strix, all host-network.
- Existing
addon_ccab4aaf_frigate cannot bind its ports -> stuck Created.
ha supervisor info shows supported: false.
Root cause:
detect.sh does not detect HA Supervisor. On a Supervised host the installer should not deploy its own Frigate/go2rtc (HA already runs them) and should not take host ports.
Suggested fix:
- Add an HA detection check in
detect.sh (ha CLI / /usr/share/hassio / hassio_supervisor container).
- If HA is detected, the installer should NOT install anything. Instead it should stop and tell the user to set Strix up through the Home Assistant UI (add-on / integration), since HA already manages Frigate/go2rtc and installing on the host breaks Supervisor.
- Document a clean uninstall (remove
strix/frigate/go2rtc + /opt/strix, then ha supervisor repair).
Manual recovery that worked:
docker compose -f /opt/strix/docker-compose.yml down, remove leftover containers, rm -rf /opt/strix, ha supervisor repair. Add-on Frigate then came up healthy.
On a Debian 12 host running Home Assistant Supervised, the installer (
linux.sh->strix-frigate.sh) deploys its own Frigate + go2rtc withnetwork_mode: host. They grab the ports the HA Frigate add-on needs (5000/8971/1984/8554), so the add-on gets stuck inCreatedand Supervisor goessupported: false.Environment:
Debian 12, Docker 29.5.2, HA Supervised (Supervisor 2026.05.1, Core 2026.5.4), HA Frigate add-on 0.17.1 already installed.
What happens:
strix,frigate(frigate:stable),go2rtcin/opt/strix, all host-network.addon_ccab4aaf_frigatecannot bind its ports -> stuckCreated.ha supervisor infoshowssupported: false.Root cause:
detect.shdoes not detect HA Supervisor. On a Supervised host the installer should not deploy its own Frigate/go2rtc (HA already runs them) and should not take host ports.Suggested fix:
detect.sh(haCLI //usr/share/hassio/hassio_supervisorcontainer).strix/frigate/go2rtc+/opt/strix, thenha supervisor repair).Manual recovery that worked:
docker compose -f /opt/strix/docker-compose.yml down, remove leftover containers,rm -rf /opt/strix,ha supervisor repair. Add-on Frigate then came up healthy.