Replies: 1 comment 11 replies
-
@GrizzlyAK The last seen and last updated time in nodes and values are managed on z2m side (nont from zwavejs driver) so I dunno what you mean here as I dunno how hass handles them. About the wrong battery reports I dunno how this could be improved, maybe a priodic call to refreshValue or pollValue (with an high timeout) could be a possible fix but I let @AlCalzone answer to this |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
As far as I know, there is no way to know in HA what the value of Last Active in the rightmost column of the CP is for a particular device. The
last_updated
andlast_changed
state object properties are lacking if you want to know if a battery powered device has checked in without it actually reporting a change.I'm assuming that this Last Active includes these "check in" times, as well as any other communication with a device, including reports. I don't expect it will ever be state property of a device, but perhaps it could be retrieved with a service call to fetch the value from zwave-js? Maybe it's possible now, idk. But for checking if a battery device is dead, especially for someone like me who has them set to wake up every 2 hours, it would be extremely useful data. I've found that only a small percentage of my battery powered devices actually report battery levels correctly. I've had some reporting as high as 90%, even though completely dead and the device inoperable. Only one or two have EVER shown 0% when they quit working. It seems the only real way to know is to see if it checks in.
Beta Was this translation helpful? Give feedback.
All reactions