Okay I wasn´t aware of that. I just noticed the ZP3102 manual mention a specific voltage.
The specific voltage used is likely to be different for different devices since ultimately DoD is what is important, and while voltage is a poor proxy, it is the one most often used. However, whatever method (voltage, or DoD, or …) is used, the point is that in all cases the notification is the same.
Hmm then I´m back to my original answer, cause I dont get it.
The manual of the ZP3102 says it will send auto report if the battery votages falls below x.xx Volt, I would assume this would be a switch going Toggle ON or OFF.
If another device (not ZP3102) have a simular function (Low Battery switch), but this will Toggle at y.yy Volt.
I fail to see how the use of Battery Level (Number channel) can make up from using a Low Battery Switch. Unless the user create a rule for each an very device.
Well, I don’t understand why can’t you just use a group of numbers and select the minimum battery level - isn’t it the same thing?
I dont see how, if the minimum levels are different from one device to another. How to know at what level to trigger the Group-alarm?
Forget the level - as I said, this is not relevant. What matters is when the device decides its battery is low - when it does this, it will have a battery level of 0%. That might be 1.2 volts, it might be 120 volts - who cares. The point is that the device has decided the level is now low, and it is now reporting 0%.
The commands being sent ensure that this is reported in a standard way!
Ahh, Now I get it…
The device will change to 0% Battery Level (and still be running cause its not completely empty) when Battery is low ?
Ofcouse!, If this is the same for all devices, then it could be used in groups insted of using an specific Low Battery switch…
Sorry I didn´t quite get that before…
I just updated to the latest nightly build looks like the change for tamper is now working. The Change for alarm_motion didn’t make it into the nightly build yet, so i will keep an eye out for next database merge.
I´ll give it a try later tonight
EDIT…
I just updated zwave binding. For the Vision ZP3102, neither Tamper sensor or Alarm (buglar) seems to have any effect.
EDIT - Tamper works now… Guess I had to remove and add the device to get the tamper. Alarm Buglar doesn work thouh.
Yup, waiting for the next nightly build, there was a DB update yesterday https://github.com/openhab/org.openhab.binding.zwave/pulls?q=is%3Apr+is%3Aclosed but there doesn’t appear to be a snap shot since the 15th of jan
Should all be working now
Sorry for waking up this old thread.
I have never before looked at the device database so my question may be irrelevant.
From what I know, battery operated devices cannot be used as repeaters or routers for zwave as they are sleeping most of the time.
Now in the device DB there is an attribute called “zwave_routing”, shouldn’t this be set to false with this device?