Frigate entities all unavailable

Third party integrations
1

Hello everyone,

I have a lot of problems with frigate atm.

First, the coral was not recognized anymore. That I fixed by using the frigate (full access) add on instead and disabling protection mode.

frigate.app INFO: Starting Frigate (0.16.3)
peewee_migrate.logs: migrations completed 001–030
detector.coral INFO: Starting detection process
frigate.detectors.plugins.edgetpu_tfl INFO: TPU found
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.

However, all my frigate entities are unavailable. Is it possible that this is related to my copying over my config from the old add on to the full access version? My database was also corrupted but I think I fixed that by renaming the old, broken one.

Frigate seems to connect to my mqtt broker just fine according to my understanding of the logs.

2025-12-07 16:05:27: New client connected from IP as frigate (p2, c1, k60, u'frigate').

The add on also starts without issues and the camera streams are visible in frigate.

My setup:
HA OS
Frigate 0.16.3
google coral als TPU
MQTT broker Mosquitto

I have no idea where to look or what to change.

Can anyone help or at least point me in the direction?

Thank you!!

2

blakeblackshear/frigate · Discussions · GitHub is the official Frigate support hub and is another good place to get help with Frigate if you don’t get an answer here.

2 Likes
3

this is usually an MQTT issue

4

Any idea what kind? My cameras do show up in mqtt explorer and also send messages.

Clicking on “visit” in the frigate camera device area, tries to open a URL, that does not connect though. So that might also be related.

5

In the end, my problem was an incorrect link in the frigate integration. For the full access version “-fa” needs to be added to the link.