ZWave items automatically reverting from 'ON' to 'OFF' after sendCommand()

Currently have many zwave devices running on ‘OH 3.1 Release Build’ on a Linux CentOS 7.x machine. I have several rules that trigger properly and send ‘ON’ or ‘OFF’ events to my binary devices. I’m seeing many items reverting from ‘ON’ after a sendCommand() to ‘OFF’ automatically. An example from my rules file is:


The results (sometimes) looks like this from my events.log:

2021-10-23 17:19:00.013 [INFO ] [openhab.event.ItemCommandEvent ] - Item ‘ZWaveNode004ZW1001SmartOutlet_Switch’ received command ON
##REDACTED…other log entires about other ‘Items’…
2021-10-23 17:19:00.036 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item ‘ZWaveNode004ZW1001SmartOutlet_Switch’ predicted to become ON
##REDACTED…other log entires about other ‘Items’…
2021-10-23 17:19:00.056 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘ZWaveNode004ZW1001SmartOutlet_Switch’ changed from OFF to ON
##REDACTED…other log entires about other ‘Items’…
2021-10-23 17:21:27.703 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘ZWaveNode004ZW1001SmartOutlet_Switch’ changed from ON to OFF

Note the revert back to ‘OFF’ state. Any thoughts?

To understand the ‘predicted’ and first change event within a few milliseconds, see here -

in other words these are internal to openHAB and not related to real device behaviour.

The reversion to OFF two minutes later most likely comes from the device, you might need to look at your configuration and/or get some debug info from the binding.

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.