Fibaro double switch sometimes ignores commands

Hello, everyone, this is my first topic. And after a lot of searching, I couldn’t find out what is the problem because everything looks fine.
Here is my item:

//Fibaro Switch
Switch ZWaveNode2_Switch1"Outdoor Lights" <lightbulb> [ "Switchable" ]

and I have created the rules from the paper UI I don’t know how to put it here. But I think the rules are fine because the lights always go off when nuticDawn Start and goes ON when civilDusk Start. The Problem is sometimes I wake up in the morning I found the lights still on.

and here is the event log when the problem happened and no errors:

2018-10-19 05:18:00.016 [vent.ChannelTriggeredEvent] - astro:sun:local:nauticDawn#event triggered START
2018-10-19 05:18:00.021 [.event.RuleStatusInfoEvent] - 1ed4c2ef-91df-48b9-bca9-bb316b700dd0 updated: RUNNING
2018-10-19 05:18:00.028 [ome.event.ItemCommandEvent] - Item 'ZWaveNode2_Switch1' received command OFF
2018-10-19 05:18:00.039 [.event.RuleStatusInfoEvent] - 1ed4c2ef-91df-48b9-bca9-bb316b700dd0 updated: IDLE
2018-10-19 05:18:00.045 [vent.ItemStateChangedEvent] - ZWaveNode2_Switch1 changed from ON to OFF
2018-10-19 05:29:26.407 [vent.ItemStateChangedEvent] - ZWaveNode2_ElectricMeterKWh changed from 39.76 to 39.81

And this at the dusk when the lights goes on with no problem:

2018-10-19 17:40:00.017 [vent.ChannelTriggeredEvent] - astro:sun:local:civilDusk#event triggered START
2018-10-19 17:40:00.029 [.event.RuleStatusInfoEvent] - 7d48c7de-070a-46f3-b2e3-61b22822fcfa updated: RUNNING
2018-10-19 17:40:00.038 [ome.event.ItemCommandEvent] - Item 'ZWaveNode2_Switch1' received command ON
2018-10-19 17:40:00.047 [.event.RuleStatusInfoEvent] - 7d48c7de-070a-46f3-b2e3-61b22822fcfa updated: IDLE
2018-10-19 17:40:00.053 [vent.ItemStateChangedEvent] - ZWaveNode2_Switch1 changed from OFF to ON
2018-10-19 17:59:26.397 [vent.ItemStateChangedEvent] - ZWaveNode2_ElectricMeterKWh changed from 40.32 to 40.36

Please help

There are a few things you can check:

  1. Verify that you z-wave network heal time is not conflicting:

  2. Check that your node has some neighbours and that the last heal time is recent:

If your node is a leaf node, you might consider a repeater node to improve mesh coverage.

  1. The Z-Wave binding has received a major overhaul into the 2.4 Snapshot branch. If you are not already on it, consider updating. (be sure to check out the actions necessary for using the new z-wave binding)

  2. Hint for future posts: always state what version you are running.

You should get a debug log to see what is happening. It might just be that the device is marginal with its range, and it might therefore miss the occasional command. If this is the case, then you should be able to fill the gap by adding an additional mains powered device to improve the meshing.

As @OMR said - you should also ensure you have the latest binding (2.4 M4 or snapshot).