States Reset to 0 after HA restart #22062
Replies: 2 comments 3 replies
-
|
Based on the available sources, there isn't explicit documentation about occupancy sensor state persistence across Home Assistant restarts. The occupancy sensors provided by the Frigate Home Assistant integration rely on real-time detection updates rather than pulling historical state from Frigate when Home Assistant restarts(1). The integration requires MQTT to be configured and Frigate must be connected to the same MQTT server as Home Assistant for the entities to function properly(1). The occupancy sensors update based on MQTT messages published to topics like When Home Assistant restarts, the sensors reset because they depend on receiving new MQTT messages to update their state. Since Frigate publishes messages when objects change (new detections, updates, or when objects end), a stationary object that hasn't changed won't trigger a new MQTT message to update the sensor after your Home Assistant restart(2). For automations requiring more accurate state tracking that matches Frigate's actual detections, it's recommended to use MQTT sensors based on the 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
Follow this feature request: #11314 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
After I restart HA, all of my occupanct sensors are set to 0 until they update again. For example, frigate still knows there’s a car in my garage, but the HA integration is back at not detected until I leave and come back again. Is there a way to have it pull states from frigate when HA restarts so these are accurate?
Beta Was this translation helpful? Give feedback.
All reactions