State change from 100 to 0 and back to 100

[KnC (André Krause)]

Hello everybody

I am new in our community, but I am reading a lot in your forum. I had set up my “Smart Home” half a year ago. But since a couple of weeks I have an issue, which i do not understand. I reset the whole system, reinstall it, took out the items and things and made it all new, but one of my blind controls make some trouble. I had also search here in this forum for such an issue, but I didn’t got any answers. Hopefully, someone of you can give me a hind.

This is my system which I am running:

• Platform information:
  • Hardware: Synology NAS, Aeotec zwave USB Stick and a Fibaro RollerShutter 2
  • OS: DSM 6.2.1-23824 Update 4
  • Java Runtime Environment: Java 8
  • openHAB version: openhab 2.3.0.005

It all went quite good for a period of half of a year. But now the problem is that. If I want to move the Roller Shutter down to an other state, it won’t do it at the first time. For example: when it has a state of 100 and I want to bring it to 0, after 2 seconds it will fall back to 100. Sometimes I have to do it 3 or 4 times and then it will follow my trigger. I also have a rule behind it and this is why I had recognise this fault.

Here is also the log of a typical fall back:

2019-01-28 23:13:44.640 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Command received zwave:device:b99c62c5:node5:blinds_control --> 0
2019-01-28 23:13:44.646 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 5: Creating new message for command SWITCH_MULTILEVEL_SET
2019-01-28 23:13:44.651 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2019-01-28 23:13:44.651 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2019-01-28 23:13:44.654 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 05 03 26 01 00 25 A8 4A
2019-01-28 23:13:44.657 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 5: Sending REQUEST Message = 01 0A 00 13 05 03 26 01 00 25 A8 4A
2019-01-28 23:13:44.667 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2019-01-28 23:13:44.670 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2019-01-28 23:13:44.673 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
2019-01-28 23:13:44.675 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
2019-01-28 23:13:44.677 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
2019-01-28 23:13:44.679 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 5: Sent Data successfully placed on stack.
2019-01-28 23:13:44.685 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 A8 00 00 02 41
2019-01-28 23:13:44.688 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2019-01-28 23:13:44.690 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 A8 00 00 02 00 00 4F
2019-01-28 23:13:44.692 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 A8 00 00 02 00 00 4F
2019-01-28 23:13:44.694 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=A8 00 00 02
2019-01-28 23:13:44.696 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 5: SendData Request. CallBack ID = 168, Status = Transmission complete and ACK received(0)
2019-01-28 23:13:44.698 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Starting initialisation from DONE
2019-01-28 23:13:44.700 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@44d035 already registered
2019-01-28 23:13:44.703 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=5, callback=168, payload=05 03 26 01 00
2019-01-28 23:13:44.705 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=A8 00 00 02
2019-01-28 23:13:44.707 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=168, expected=SendData, cancelled=false transaction complete!
2019-01-28 23:13:44.709 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2019-01-28 23:13:44.710 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2019-01-28 23:13:44.712 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Response processed after 53ms/2830ms.
2019-01-28 23:13:46.744 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 05 03 26 03 0A DB
2019-01-28 23:13:46.747 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2019-01-28 23:13:46.749 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 05 03 26 03 0A DB
2019-01-28 23:13:46.751 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 05 03 26 03 0A DB
2019-01-28 23:13:46.753 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 03 26 03 0A
2019-01-28 23:13:46.755 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 5: Application Command Request (ALIVE:DONE)
2019-01-28 23:13:46.757 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Starting initialisation from DONE
2019-01-28 23:13:46.759 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@44d035 already registered
2019-01-28 23:13:46.761 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 5: Incoming command class SWITCH_MULTILEVEL
2019-01-28 23:13:46.763 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 5: Received SWITCH_MULTILEVEL command V3
2019-01-28 23:13:46.764 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 05 06 31 05 04 22 00 00 E6
2019-01-28 23:13:46.765 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 5: Switch Multi Level report, value = 10
2019-01-28 23:13:46.767 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2019-01-28 23:13:46.769 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-01-28 23:13:46.771 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_MULTILEVEL, value = 10
2019-01-28 23:13:46.774 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:b99c62c5:node5:blinds_control to 10 [PercentType]
2019-01-28 23:13:46.778 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=5, callback=168, payload=05 03 26 01 00
2019-01-28 23:13:46.784 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 03 26 03 0A
2019-01-28 23:13:46.787 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=168, expected=SendData, cancelled=false MISMATCH
2019-01-28 23:13:46.789 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2019-01-28 23:13:46.793 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 04 00 05 06 31 05 04 22 00 00 E6
2019-01-28 23:13:46.797 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 00 05 06 31 05 04 22 00 00 E6
2019-01-28 23:13:46.800 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 06 31 05 04 22 00 00
2019-01-28 23:13:46.802 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 5: Application Command Request (ALIVE:DONE)
2019-01-28 23:13:46.803 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Starting initialisation from DONE
2019-01-28 23:13:46.805 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@44d035 already registered
2019-01-28 23:13:46.807 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 5: Incoming command class SENSOR_MULTILEVEL
2019-01-28 23:13:46.808 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 5: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V2
2019-01-28 23:13:46.810 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 5: Sensor Multi Level REPORT received
2019-01-28 23:13:46.812 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 5: Sensor Type = Power(4), Scale = 0
2019-01-28 23:13:46.814 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 5: Sensor Value = 0E+1
2019-01-28 23:13:46.816 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2019-01-28 23:13:46.818 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2019-01-28 23:13:46.819 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 0E+1
2019-01-28 23:13:46.821 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:b99c62c5:node5:sensor_power to 0 [DecimalType]
2019-01-28 23:13:46.825 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=5, callback=168, payload=05 03 26 01 00
2019-01-28 23:13:46.828 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 06 31 05 04 22 00 00
2019-01-28 23:13:46.830 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=168, expected=SendData, cancelled=false MISMATCH

[sihui]

@KnC

2.3.0.005

This version is much too old. Please update to the latest zwave snapshot 2.5 binding.
There have been many changes to the FGR222 in the database. I had similar issues with that device which was solved removing the basic messages from the multilevel channels.

Don’t forget to read

ZWave binding updates

I have now merged the development version of the ZWave binding into master, so it will be available in the 2.4 snapshot version. If you are using the ZWave binding, please read this post as the binding contains some breaking changes so you will need to manually update your configuration. Firstly though - the major enhancements (there are tons more smaller updates) -: Security has been added using the S0 security class. This should allow all devices supporting security to be included into the…