im sure that someone already mentioned this “issue” but i just cannot find a proper thread for this, because this and the other topics are stated way too generic.
I have several Zigbee devices and I am already monitoring Battery life at some degree.
But sometimes they die at 50%, staying unnoticed, because Battery life stays above the threshhold unnoticed.
Therefore Id like to “force” devices to go “unavailable” or “unknown” if they lost power.
Currently they stay at the last known read value, making my automations a bit messy.
See example:
Best would be if I could add a “timeout” in HA/Z2M to make them automatically unavailable
I dont want an automation/helper to “check” this because I then would need to add this routine for every Automation I have forcing me into super pesky micromanagement.
I looked into HA if I could find something but I could not find anything related to it…
Any idea?
Enable that & restart Z2M. Further down that screen are the options for Active timeout (mains powered devices) and Passive timeout (battery & no neutral devices). These default to 10 minutes and 25 hours respectively.
You could reduce the battery value to something less than 25 hours (1500 minutes), but be aware that the lower you set it, the more you will increase battery consumption.
The equivalent setting in ZHA is set to 6 hours, which I believe is too low, but something like 12 hours (720 minutes) should be a fair compromise between timely reporting & battery consumption.
It is also common that some devices ignore that value and just keep on going with the value they are born with, which means you might see devic s go unavailable and then become available again after some time over and over again.
Never experienced that myself, but I’ve seen reports here on Sonoff devices taking more than 6h to check in.
If someone’s on ZHA with default values, then what you described is indeed possible.
