Beacons reset status upon HASS/Bermuda restart
Open
- Dominant language
- Python
- Stars
- 2k
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
When restarting HASS, due to updates or whatever, some beacons flip to Home momentarily and then back to Away (if they are away). This causes any "just arrived" automations to fire unexpectedly.
Not sure if this is due to a restart of HASS or simply a reload of Bermuda. Is there a way we can filter those blips out?
Perhaps using the System Uptime and/or Bermuda's own internal uptime, ignoring any change in status when uptime is reset? Or persisting the previous state across reloads instead of defaulting to Home?
Contributor guide
Assessment
This issue has not been assessed yet.