I have an Aeotec recessed door sensor, and the battery level shows as 100 until the battery dies. Does anyone know why this is the case or able to fix it?
I’ve checked the config in the Z-Wave settings screen in HA and it shows ‘101: Low Battery Check Enable’ set to ‘Enable’.
The battery lasts a few months, but then just suddenly dies, and I don’t notice until one of my door automation stops working. It’s part of my security system, so would really like to know when it dies or is about to die.
I also have a MultiSensor 6, and that too says 100 for the battery, although, it’s not died on me yet but I suspect it’s going to have the same behavior.
I have two of these sensors also and they’ve been installed for the better part of a year. Battery level is still indicating 100% on both plus 3 of 4 window sensors. 4th window sensor is at 74%.
The doors are open / closed from twice to dozens of times a day depending on the day.
Why is it you think the batteries are flat If they are indicating 100% ?
Same problem here… months in a row at 100% and then just dies.
I believe this problem wasn’t there in it first year and is introduced after a firmware update.
Same issue here; Aeotec recessed gen5’s battery level reports a constant 100%, then after a while suddenly drops straight to 0% and the device stops working. There’s some related discussion about this ST:
I have one of these in a high traffic door; it has gone through 2 batteries in 6 months! I didn’t even find out the battery is dead until I either check the server and see the 0%, or observe a related automation that stops working (a “door was left open” beeper). These sensors also tend to miss open states when the battery starts getting low. So a percentage is really needed for these to be reliable.
I have since temporized around this problem by running an automation that will send me a telegram text as soon as a battery goes to 0%. That lets me know right away when the battery dies, but that doesn’t prevent the missing states leading up to it finally dying, and it precludes sensors from being trusted with a critical application (safety/security)… unless you like replace the batteries every 2 months and keep fingers crossed, lol.
If anyone has come up with a fix, or could point to some info that may lead to a fix, please share
Edit: fwiw, in my ozw page, the sensors all show “101: Low Battery Check Enable” is set to ‘Enabled’ (greyed out). However I noticed on openzwave code (main github, not hassio adaptation) the config for these devices seems to have it defaulted to off (aeotec/zw089 line 47 has… value=“0”). I have already tried setting to enable with the webui and waking with the button to no avail. I may try editing the config to value=“1”, then reboot, exclude, reinclude, and see if that works. Anyone else try that?
FWIW, to use and edit the latest ozw code with hassos, you have to clone the repo to a “zwave” folder in /config, and add the line " config_file: config/zwave/config" to the zwave section in your configuration.yaml. I actually did this to get other sensors working, then realized it may be be an opportunity to fix this aeotec batter level issue.
Some devices don’t “push” battery level updates out. You could enable polling on the battery level but it will only refresh when the device wakes up (usually every 24 hours on a lot of devices)