[SOLVED] Z-Wave binding - sporadic "double" change events

Since a while seeing repeating item change events from Danalock v2 lock, connected through ZWave.
Not sure when it started … maybe ~month ago, with upgrade to 2.5 openhab.

e.g. I have rule “on every change” to print out item state. When change item state in habpanel from OF to ON get three entries in the log file (seen the same also when doing the change from the lock on the door)
changed to ON
changed to OFF
changed to ON

There are moments when I get only one change event, as expected. Seems like doubling is more often for change from OFF to ON.

Switched on debug log for ZWave and tried to repeat - first ON and OFF went well, single events, but on second attempt both were “doubled”. Attaching ZWave log (Node77 is the lock in question).
Not that literate in reading it. Maybe @chris can help translating - is it something with binding itself or rather my instance of openhab (e.g. inclusion of lock or linking between things/items)?

ZWave_debug_Node77.log (593.4 KB)
Thank You in advance!

Changed to ON

Changed to OFF
2019-01-08 15:06:42.222 [INFO ] [ipse.smarthome.model.script.DoorOpen] - state change to  OFF

Changed to ON
2019-01-08 15:06:50.002 [INFO ] [ipse.smarthome.model.script.DoorOpen] - state change to ON
2019-01-08 15:06:53.145 [INFO ] [ipse.smarthome.model.script.DoorOpen] - state change to OFF
2019-01-08 15:06:53.765 [INFO ] [ipse.smarthome.model.script.DoorOpen] - state change to ON

Changed to OFF
2019-01-08 15:07:02.762 [INFO ] [ipse.smarthome.model.script.DoorOpen] - state change to OFF
2019-01-08 15:07:04.624 [INFO ] [ipse.smarthome.model.script.DoorOpen] - state change to ON
2019-01-08 15:07:05.427 [INFO ] [ipse.smarthome.model.script.DoorOpen] - state change to OFF

Version information
180 x Active x 90 x x openHAB Core
231 x Active x 80 x x ZWave Binding

In HABmin, try changing the Command Poll Period on the Device Configuration tab. I’ve found that the default of 1500 milliseconds is too short for locks. So, the repoll happens before the lock has had a chance to change state. Either make it longer (I have it set at 6000 for my lock), or disable it completely.


changed to 5000 and so far have not seen the issue. will hope it is gone.
Thank You so much @mhilbush for the quick response and solution!

1 Like