I have an ID Lock 150 with a zwave module. I have been using it for years without any issues.
A few months ago I noticed that the batteries were being drained quite fast and I had to replace them more and more often.
By checking the Zwave node status in HA I can see that node is always alive, which is bad for battery life.
I use the latest firmware in the lock and the latest HA core and Zwave JS. I have also tried resetting the lock and including it again.
Any ideas?
Locks are âfrequently listeningâ devices (FLIRS). Unlike regular battery nodes which have a (usually) configurable wake-up interval, FLIRS devices are constantly waking, either every 250ms or 1000ms (1 sec). Thus, they are similar to mains powered devices and donât actually go to sleep. A FLIRS device will have alive/dead status, so itâs normal and not an indication of the problem youâre having.
Perhaps something changed in the network and the device is sending more data unnecessarily (e.g. bad connection). You would have to track the statistics sensors or check the driver logs for activity, or use the Z-Wave JS UI network map for troubleshooting. Also make sure youâre using the correct type of battery.
1 Like
Locks will stay âAliveâ, battery performance is affected by nearby AC powered devices. What probably changed is either you moved an AC powered ZWAVE device or one has failed.
I improve the battery life and communication with my Zwave and Zigbee devices by putting a buffering repeater\extender (AC power device) near all my battery power devices.