@mirekmal wrote:
Strange behavior of motion/presence sensors I noticed recently:
I have 4 IKEA motion sensors and 9 Aqara motion sensors
Phoscon shows all of them after hassio restart and all of them seems to report proper state (active, at moment of restart usually no move detected)
hassio (Developer Tools -> States) similarly shows all of them and as being off
In my Lovelace UI I have one history-graph card that shows all of them, so I can check history… and now strange things starts:
- just after restart all of these sensors are reported by history-graph card as unavailable (even if States shows off)
- if I move around to trigger them, they start to report proper state - in States status is changed to on, but history-graph shows it as Detected. It goes after a while to off/Clear, so also OK.
- from the moment the first move is detected history-graph properly shows sensor status as available and off/Clear (but part of history until then remains as unavailable)
- after 1 hour (my default history period) reported status changes to off/Clear, even if there was no move detected and sensor starts to look OK on graph.
- if I change history period from default 1 hour to 2 hours or more, it goes to previous situation, proper state until moment of restart and then sensor is shown as unavailable.
- In meantime all automations, that are based on motion sensors status change work perfectly fine, so clearly sensors are available in the ZigBee network and it is not first status change that bring them back to life.
To me it look that history graph has some issues with proper reading of initial state of sensors after hassio restart, but perhaps there is another catch that I did not yet figured out… Anyone noticed similar behavior? Any idea how to get this fixed?
Posts: 1
Participants: 1