As There are fast dev for OH2, I wanted to know where could I ask this feature. On OH2 or zwave binding.
It could be usefull when you wants to know if your zwave devices are functionnal. Example: someone try to use a jammer on your zwave sensor. As an alarm rule is on, 3 polls are done every minute on all listed devices. If a device don’t answer after 3 polls then do something.
Another example ( a real): my zwave device which command my pool pump is offline, if not an interactive poll in a rule, I can’t see if it’s working.
This is not something that will be supported in the zwave binding in OH2. It is not generally inline with the concepts of OH as the interaction with hardware should be kept within the binding.
It is already possible to do what you want by configuring the refresh_interval and then monitoring the info to see if the device goes DEAD. This will happen if the device doesn’t respond to a single poll - not 3.
Sorry Gilles,
I just checked the code, and the DEAD info item should only return true if the device is considered DEAD or FAILED. If the device is just off, then it shouldn’t return true here (unless by ‘off’ you mean it’s completely powered off as in this case the controller will think it’s DEAD).
true should equate to ON, and false should equate to OFF. So, if the device is DEAD, then the item should show ON, and if it’s ok, then it should show OFF.
I don’t use this, but looking through the code, this should be fine.
You need to remember that this item is not looking at the state of the device - it’s the state of the DEAD status.
When you did this, what did HABmin show? Did it show a red icon, or was it still ok? It might take some time for it to show DEAD - depending on polling etc.
I see that the dead information is sent every 5 seconds.
If problem on some devices which are checked, every five seconds information will be sent from many devices. That mean my server will get a certain load for CPU.
Being as the goal is to not allow polling from the rules, something that I feel would be super beneficial from the binding then is the ability to poll shortly after a change. My problem case is with GE dimmers (and I think other dimmers have the same issue): When they change, they just report the start value and current value (i.e. dim from 0 to 6), and not the end value. It makes it very difficult to do some rules; I’m currently in a mess of logic to properly determine if they are turned “ON” or “OFF”. Sure, I can try and use refresh_interval, but I’d need to set it pretty low to be useful and I only need the data once, so it’s silly to flood the whole zwave queue for something that’s only needed once. Or perhaps a better solution is to build in a poll following SWITCH_MULTILEVEL commands.
@chris, Are you aware of the RefreshType.REFRESH command, which is meant to allow exactly such a behavior? It might not be technically feasible to implement on all devices, but where it is possible, the bindings should support it.