Zwave Plug-Switches turn on by itself short time after switched off via rule (?)

I have a strange observation with recent builds of snapshot release. Not sure since when but i see the following behavior on several items (plug switches) that irregularly is shown…So i swithc off via rule, the switch goes OFF but after here 15mins it goes ON again…any idea what is going on?

Here some examples:

2017-12-12 21:00:00.012 [ome.event.ItemCommandEvent] - Item ‘MaxKalk_Switch’ received command OFF
2017-12-12 21:00:00.019 [vent.ItemStateChangedEvent] - MaxKalk_Switch changed from ON to OFF
2017-12-12 21:15:25.871 [vent.ItemStateChangedEvent] - MaxKalk_Switch changed from OFF to ON

2017-12-12 18:00:00.014 [ome.event.ItemCommandEvent] - Item ‘MaxKalk_Switch’ received command ON
2017-12-12 18:00:00.027 [vent.ItemStateChangedEvent] - MaxKalk_Switch changed from OFF to ON
2017-12-12 18:15:25.802 [vent.ItemStateChangedEvent] - MaxKalk_Switch changed from ON to OFF

Did you manage to find a solution for this? I’m experiencing the same problem but with turn off. If I turn on the light with the switch then the motion sensor turns it off immediate

no - since that point in time it happens every other day that especially in the evening arround 6pm to 8pm several items GO on without a reason. As @chris said, in my logs there was no evidence that any information came via the controller/openhab. so the only logical reason “must be” an zwave device that directly triggers this behavior.

My hope was that somehow a swap of the controller stick would solve the problem - as anyhow i wanted to switch towards GEN5 USB-stick, but still even after this massive transition it did not solve the issue. I also tried to check all configs of the items if there is any ALL-ON parameter set wrongly - but was not the case.
So since that point in time i have not full believe in my home system - was thinking of a rule that observes such behavior to inform me or even turn these items OFF.

Lets see if i find the bad item…but hard as i have arround 45 zwave devices. sorry - no better feedback right now.

If you have patience enough maybe you can disconnect one zwave controller every other day, going one by one (or two by two to accelerate). At some point (maybe it will take couple of months) you will have checked them all. I would start by shutting down the controller first

I am having exactly the same problem. It’s a big problem because I am controlling the watering by a Z wave switch. Any updates on this?

2020-05-29 18:00:00.051 [ome.event.ItemCommandEvent] - Item 'zwave_device_Razberry_node3_switch_binary' received command ON

2020-05-29 18:00:00.072 [nt.ItemStatePredictedEvent] - zwave_device_Razberry_node3_switch_binary predicted to become ON

2020-05-29 18:00:00.105 [vent.ItemStateChangedEvent] - zwave_device_Razberry_node3_switch_binary changed from OFF to ON

2020-05-29 18:00:30.047 [ome.event.ItemCommandEvent] - Item 'zwave_device_Razberry_node3_switch_binary' received command OFF

2020-05-29 18:00:30.050 [nt.ItemStatePredictedEvent] - zwave_device_Razberry_node3_switch_binary predicted to become OFF

2020-05-29 18:00:30.066 [vent.ItemStateChangedEvent] - zwave_device_Razberry_node3_switch_binary changed from ON to OFF

2020-05-29 18:00:31.754 [vent.ItemStateChangedEvent] - zwave_device_Razberry_node3_switch_binary changed from OFF to ON

I had a strange issue with this option

Configuration Parameters
1: “Always On” mode

After turning this option to active and back the issue seemed to be gone. I think there might be a bug in the Fibaro firmware. Very annoying.