Closed TheTrueRandom closed 2 years ago
I'm not the developer but have played around with zwave battery devices quite a bit. I can't say this is not an issue, but in your testing the device needs to be fully initialized before you pull the battery out and you can't restart OH or the binding during the entire time the battery is out. How to tell? when you pull the battery out the time stamp on that node XML file in user/zwave has to be after the controller time stamp and has to stay after the controller for the entire test period.
That said, there are posts in the forum where others have solved your requirement in other ways. Again, not an expert, but I believe the expire binding was used. I do not have anything critical like a smoke detector, but link a datetime item to my daily battery update and have displayed in the UI Good luck
I think this is a duplicate of 1065 so propose to close.
If the problem is associated with a device, please provide the following -:
Expected Behavior
As stated in the documentation a battery device will be DEAD/OFFLINE "approximately twice the wakeup period".
Current Behavior
I use a FGSD002 Smoke Detector and a Aeotec AEOEZW090-C usb zwave stick. I added the controller and the device as a thing to openhab and it works perfectly. However, the device is always listed as ONLINE. By now I removed the batteries of the smoke detector for a week and the device is still listed at ONLINE.
Also I noticed that specifying wakeup_interval on the thing configuration is ignored. I can read the value on the UI though, which is set to 21600. So the device should be considered OFFLINE after approx. 12h. By now I removed the batteries for 168h.
Possible Solution
Steps to Reproduce (for Bugs)
Context
I would like to know when a smoke detector is not reachable anymore.
Your Environment
Version used: (e.g., openHAB and add-on versions) openHAB 3.2.0 Release Build Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...): *Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...): Raspberry Pi: Linux openhabian 5.10.63-v8+
sitenote: I created the issue on openhab addons https://github.com/openhab/openhab-addons/issues/12102 By now I put the batteries back. The XML is taken today, when the batteries are added again.