Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Home Assistant report wrong state for person occupancy after restart
See original GitHub issueVersion of the custom_component
v3.0.0
Configuration
Describe the bug
When Home Assistant start it reports no person occupancy even if frigate is reporting a person (validated using frigate debug option). The value is not updated until there is a change in the scene (i.e. the person leaves the scene and comes back, or a different person is detected)
Debug log
Issue Analytics
- State:
- Created 10 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Sensor settings and incorrect data when restarting the router
Hi, I'm a novice user, but Home Assistant is great. I bought a Shelly 3EM to measure the energy consumed. Everything works great...
Read more >What the heck is with the 'latest state change' not being kept ...
' Retain last state change data of a sensor after reboot. Persistent version of "last-changed" for the UI?
Read more >[monitor] Reliable, Multi-User, Distributed Bluetooth ...
The system is useful for mqtt-based home automation. Script here. ... I will try to use these, to avoid having Unknown state after...
Read more >[monitor] Reliable, Multi-User, Distributed Bluetooth ...
Hi guys,. Monitor is working great, the onlything is when I reboot HA all monitor sensors have the stats on unknown.
Read more >Xiaomi Human / Body / Motion Sensor - Timeout - Configuration
When using a Xiaomi Aqara zigbee (2019) sensor it just reports back ... NOT the sensor) sends occupancy off so that homeassistant thinks...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That would be somewhat awkward to architect for the way frigate works currently. We’re looking at replacing MQTT with websocket to frigate anyway so that’ll probably solve it
A message to request the current state of all sensors/states would solve the problem as an automation could be created to send it after HA has started, not sure if there is anything similar available