I have the frigate add-on connecting to an instance that runs elsewhere in my homelab. I have about 6 cameras of the Tapo/Reolink variety. I noticed that my recorder database was filling up and isolated it to frigate states being updated every second even when there is not a state change. I can live without many of the sensors, but it looks like the device is reloading every second so there is an underlying problem. If you can imagine the screenshot everything flickers every second as the time stamps are updated. I have MQTT setup, probably unnecessarily, and can post the HA frigate diagnostic configuration in a later reply.
I also didn’t mention that when I go into the device and flick the switch to disable a configuration like detect, motion, recordings, snapshots it flips back. This is probably because in my separate instance those are the only things I have activated and it reloads the connection.
I have Frigate on another machine but do not see the behavior you describe. My Frigate is version 15.2 (latest is 16.2) so that might be a difference. I do see the switches flipping back behavior. If they are meant to be readonly then they should have been sensors, not switches imho.
Things I can imagine that might cause frequent updates is maybe frequent motion? Did you mask plants etc that move in the wind?
I think I already publish to the IP address but I will check that. I can’t remember, does the frigate integration use MQTT (which is probably why I added it to my frigate standalone configuration)
Thanks @Edwin_D. With your prompts I figured it out.
I just migrated from one server to another… And had both instances still running. So the HA MQTT broker was getting hit twice at slightly different times and that must have thrown the state tracking for a loop.
