OH2 ZWave 'Rollershutter' (blinds) channel

I’ve added a new channel to the ZWave binding -:

  • blinds_control: This can be linked to a Rollershutter item. It uses the multi-level switch class with a new feature to start and stop movement.

I have no rollershutters or blinds on which to test this, so please let me know if it works ok, or not! The database will need to be updated with this channel for roller shutter devices. Generally, for roller shutter devices, there will currently be a channel type switch_dimmer and this should be changed to blinds_control.

Note that I have changed the multi-level switch class which not only controls roller shutters, but also dimmers, so there’s always the possibility that I might have introduced a bug in the state conversion as this has changed significantly. Any problems, please let me know (dimmers are working fine here, so hopefully it will be ok).

Excellent. I was trying to get rollershutter working with my window actuator yesterday but was only able to use a dimmer and the operation is not that user friendly. I will test today and report back.

@chris

What snapshot was this change in? I have tried to load the snapshot today but there seems to be a problem with. I might wait for the next build.

Also, does the database entry for the Fakro ZWS12 need to be change before I can test with the Rollershutter option. I am using an item file.

I only added this yesterday so it should be in today’s snapshot.

I believe I changed the Fakro to use this new channel, but would need to check to be sure.

I just confirmed this was updated to use the new channel in last nights build.

Thanks Chris, will be back on to this tomorrow.

Thanks - if it doesn’t work, please send a debug log… Since this is a new ZWave command, there’s a reasonable chance it will have issues…

Hello Chris,

I have a Qubino Flush Shutter ZMNHCD1 for tests available. I checked the device database and found a command class SWITCH_MULTILEVEL with a Blinds control “remark”. Does this mean the channel type of the device has been adapted already?

Yes, if it says “Blinds control” under the command class then it has been adapted… I went through and changed most devices that had a device type of “MOTOR CONTROL” to this, and probably picked this up at that time…

Tested with my Somfy ZRTSI controller and it works great! The only thing to note is that i needed to inverse the direction which i don’t think I needed in 1.x, but thankfully you provided an “inverse” function.

Thanks for getting this in so quickly :slight_smile:

Great - thanks for the feedback. This uses a different feature than OH1. OH1 set the position to 0 or 99% - in OH2 I’ve implemented a new feature which uses an increase/decrease feature which also allows setting the speed.

So long as the direction and position read back are aligned, it should be ok…

Cheers
Chris

Hi,
I’ve got a qubino flush shutter dc (ZMNHOD1), but I can’t get it working.
In the inbox it is unknown:
Unknown Device
Z-Wave Node 32 (0159:0003:0053:1.1)

The database entry for it seems incomplete.
What can I do to get it working? It created a xml in zwave-folder.

Sine you have the XML, please create an account on the database site, then let me know and I’ll give you edit rights. Then upload the XML to the database - select the device, then click tools menu (top right of the page) and click “Update Device” and load the XML.

Hopefully that will solve most things.

Awesome. My username is “hazze”.
This xml also include the optional temperature sensor.
Also I’ve got another device which is marked as incomplete in the database. Should I upload that xml as well?
It’s a NodOn soft remote (CRC-3-6-0x) http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/250

Thanks - I’ve set the edit rights - any problems, please let me know…

Yes please :slight_smile:

@hazze what do the different endpoints do on this device? Does endpoint 0 (ie the root) and endpoint 1 control the same motor? I’m just trying to work out if we need both channels?

I’ll likely make them both shutter channels, and we can remove one if needed.

I’m not that experienced with zwave but I’ll try to answer what I can see in the manual.
0 and 1 is controlling the same motor (the device only have one “motor UP” and one “motor DOWN” output. Endpoint 0 has two extra groups: 8 (triggers at change of slats tilting position), 9 (sensor report, triggers at change of temperature sensor.
Endpoint 2, I don’t know. It has two groups, group 2 is triggered at change of slats tilting position.
Endpoint 3 is for the temperature sensor I guess (GENERIC_TYPE_SENSOR_MULTILEVEL)

Hope that answer your question.

@Chris

Confirming that this works with the Fakro ZWS12.

Thanks,
Mike

p.s. while it seems to be working OK, I am getting a few error messages that might be work looking into.

NODE 19 is the relevant node. NODE 18 was its’ earlier designation (this is from an item link that I am unable to remove - probably until I rename the item in question - I might try that tomorrow)

2016-07-02 15:52:37.649 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Initialising Thing Node...
2016-07-02 15:53:01.309 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Initialising Thing Node...
2016-07-02 15:53:12.981 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Command for unknown channel zwave:device:1541dc5a0e6:node19:switch_dimmer with UpDownType
2016-07-02 15:53:12.981 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate command 'DOWN' for item 'Window1_GF_mancave' to handler for channel 'zwave:device:1541dc5a0e6:node18:switch_dimmer', because no thing with the UID 'zwave:device:1541dc5a0e6:node18' could be found.
2016-07-02 15:53:12.981 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'DOWN' for item 'Window1_GF_mancave' to handler for channel 'zwave:device:1541dc5a0e6:node18:switch_dimmer', because no thing with the UID 'zwave:device:1541dc5a0e6:node18' could be found.
2016-07-02 15:53:14.164 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Command for unknown channel zwave:device:1541dc5a0e6:node19:switch_dimmer with UpDownType
2016-07-02 15:53:14.164 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate command 'UP' for item 'Window1_GF_mancave' to handler for channel 'zwave:device:1541dc5a0e6:node18:switch_dimmer', because no thing with the UID 'zwave:device:1541dc5a0e6:node18' could be found.
2016-07-02 15:53:14.164 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'UP' for item 'Window1_GF_mancave' to handler for channel 'zwave:device:1541dc5a0e6:node18:switch_dimmer', because no thing with the UID 'zwave:device:1541dc5a0e6:node18' could be found.
2016-07-02 15:53:16.654 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Command for unknown channel zwave:device:1541dc5a0e6:node19:switch_dimmer with StopMoveType
2016-07-02 15:53:16.654 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate command 'STOP' for item 'Window1_GF_mancave' to handler for channel 'zwave:device:1541dc5a0e6:node18:switch_dimmer', because no thing with the UID 'zwave:device:1541dc5a0e6:node18' could be found.
2016-07-02 15:53:16.722 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.IllegalArgumentException: Value must be between 0 and 100
    at org.eclipse.smarthome.core.library.types.PercentType.validateValue(PercentType.java:46)[97:org.eclipse.smarthome.core:0.9.0.201607011456]
    at org.eclipse.smarthome.core.library.types.PercentType.<init>(PercentType.java:31)[97:org.eclipse.smarthome.core:0.9.0.201607011456]
    at org.openhab.binding.zwave.internal.converter.ZWaveMultiLevelSwitchConverter.handleEvent(ZWaveMultiLevelSwitchConverter.java:84)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:1074)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:540)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveMultiLevelSwitchCommandClass.handleApplicationCommandRequest(ZWaveMultiLevelSwitchCommandClass.java:99)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:241)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:207)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:201)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1278)[198:org.openhab.binding.zwave:2.0.0.201607010102]
2016-07-02 15:53:17.908 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Command for unknown channel zwave:device:1541dc5a0e6:node19:switch_dimmer with UpDownType
2016-07-02 15:53:17.908 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate command 'DOWN' for item 'Window1_GF_mancave' to handler for channel 'zwave:device:1541dc5a0e6:node18:switch_dimmer', because no thing with the UID 'zwave:device:1541dc5a0e6:node18' could be found.
2016-07-02 15:53:17.909 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'DOWN' for item 'Window1_GF_mancave' to handler for channel 'zwave:device:1541dc5a0e6:node18:switch_dimmer', because no thing with the UID 'zwave:device:1541dc5a0e6:node18' could be found.
2016-07-02 15:53:21.686 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 19: Timeout while sending message. Requeueing - 2 attempts left!
2016-07-02 15:53:21.686 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 19: Got an error while sending data. Resending message.
2016-07-02 15:53:21.755 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.IllegalArgumentException: Value must be between 0 and 100
    at org.eclipse.smarthome.core.library.types.PercentType.validateValue(PercentType.java:46)[97:org.eclipse.smarthome.core:0.9.0.201607011456]
    at org.eclipse.smarthome.core.library.types.PercentType.<init>(PercentType.java:31)[97:org.eclipse.smarthome.core:0.9.0.201607011456]
    at org.openhab.binding.zwave.internal.converter.ZWaveMultiLevelSwitchConverter.handleEvent(ZWaveMultiLevelSwitchConverter.java:84)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:1074)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:540)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveMultiLevelSwitchCommandClass.handleApplicationCommandRequest(ZWaveMultiLevelSwitchCommandClass.java:99)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:241)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:207)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:201)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1278)[198:org.openhab.binding.zwave:2.0.0.201607010102]
2016-07-02 15:53:26.719 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 19: Timeout while sending message. Requeueing - 1 attempts left!
2016-07-02 15:53:26.719 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 19: Got an error while sending data. Resending message.
2016-07-02 15:53:26.758 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '0' for item 'Window1_GF_mancave' to handler for channel 'zwave:device:1541dc5a0e6:node18:switch_dimmer', because no thing with the UID 'zwave:device:1541dc5a0e6:node18' could be found.

Thanks - I’d like to see the received data which needs the debug log. I can probably make a good guess what might be the issue, but it would be better to be sure if you can get a debug log of this?

@Chris, it looks like the problem is with the STOP command: The UP and DOWN command do not generate the same error message.

Following is an extract from the log file. Let me know if you need more.

2016-07-03 13:53:46.813 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 19: Application Command Request (ALIVE:DONE)
2016-07-03 13:53:46.813 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 19: Starting initialisation from DONE
2016-07-03 13:53:46.813 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@6de0803 already registered
2016-07-03 13:53:46.813 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 19: Incoming command class SWITCH_MULTILEVEL
2016-07-03 13:53:46.813 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 19: Received Switch Multi Level Request
2016-07-03 13:53:46.813 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 19: Switch Multi Level report, value = 254
2016-07-03 13:53:46.813 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-07-03 13:53:46.813 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-07-03 13:53:46.813 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_MULTILEVEL, value = 254
2016-07-03 13:53:46.813 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.IllegalArgumentException: Value must be between 0 and 100
    at org.eclipse.smarthome.core.library.types.PercentType.validateValue(PercentType.java:46)[97:org.eclipse.smarthome.core:0.9.0.201607011456]
    at org.eclipse.smarthome.core.library.types.PercentType.<init>(PercentType.java:31)[97:org.eclipse.smarthome.core:0.9.0.201607011456]
    at org.openhab.binding.zwave.internal.converter.ZWaveMultiLevelSwitchConverter.handleEvent(ZWaveMultiLevelSwitchConverter.java:84)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:1074)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:540)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveMultiLevelSwitchCommandClass.handleApplicationCommandRequest(ZWaveMultiLevelSwitchCommandClass.java:99)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:241)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:207)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:201)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1278)[198:org.openhab.binding.zwave:2.0.0.201607010102]
2016-07-03 13:53:51.776 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 19: Timeout while sending message. Requeueing - 0 attempts left!
2016-07-03 13:53:51.776 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 19: Got an error while sending data. Resending message.
2016-07-03 13:53:51.776 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-07-03 13:53:51.776 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-07-03 13:53:51.776 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 13 02 26 02 25 BD 48 
2016-07-03 13:53:51.776 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 19: Sending REQUEST Message = 01 09 00 13 13 02 26 02 25 BD 48 
2016-07-03 13:53:51.787 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2016-07-03 13:53:51.789 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-07-03 13:53:51.789 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
2016-07-03 13:53:51.789 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
2016-07-03 13:53:51.789 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
2016-07-03 13:53:51.789 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 19: Sent Data successfully placed on stack.
2016-07-03 13:53:51.804 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 BD 00 00 02 54 
2016-07-03 13:53:51.806 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-07-03 13:53:51.806 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 BD 00 00 02 00 00 5A 
2016-07-03 13:53:51.806 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 BD 00 00 02 00 00 5A 
2016-07-03 13:53:51.806 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=BD 00 00 02 
2016-07-03 13:53:51.806 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 19: SendData Request. CallBack ID = 189, Status = Transmission complete and ACK received(0)
2016-07-03 13:53:51.806 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 19: Starting initialisation from DONE
2016-07-03 13:53:51.806 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@6de0803 already registered
2016-07-03 13:53:51.806 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=19, callback=189, payload=13 02 26 02 
2016-07-03 13:53:51.806 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=BD 00 00 02 
2016-07-03 13:53:51.806 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=189, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
2016-07-03 13:53:51.813 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 13 03 26 03 FE 39 
2016-07-03 13:53:51.815 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-07-03 13:53:51.815 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 13 03 26 03 FE 39 
2016-07-03 13:53:51.815 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 13 03 26 03 FE 39 
2016-07-03 13:53:51.815 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 13 03 26 03 FE 
2016-07-03 13:53:51.815 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 19: Application Command Request (ALIVE:DONE)
2016-07-03 13:53:51.815 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 19: Starting initialisation from DONE
2016-07-03 13:53:51.815 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@6de0803 already registered
2016-07-03 13:53:51.815 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 19: Incoming command class SWITCH_MULTILEVEL
2016-07-03 13:53:51.815 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 19: Received Switch Multi Level Request
2016-07-03 13:53:51.815 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 19: Switch Multi Level report, value = 254
2016-07-03 13:53:51.816 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-07-03 13:53:51.816 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-07-03 13:53:51.816 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_MULTILEVEL, value = 254
2016-07-03 13:53:51.816 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.IllegalArgumentException: Value must be between 0 and 100
    at org.eclipse.smarthome.core.library.types.PercentType.validateValue(PercentType.java:46)[97:org.eclipse.smarthome.core:0.9.0.201607011456]
    at org.eclipse.smarthome.core.library.types.PercentType.<init>(PercentType.java:31)[97:org.eclipse.smarthome.core:0.9.0.201607011456]
    at org.openhab.binding.zwave.internal.converter.ZWaveMultiLevelSwitchConverter.handleEvent(ZWaveMultiLevelSwitchConverter.java:84)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:1074)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:540)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveMultiLevelSwitchCommandClass.handleApplicationCommandRequest(ZWaveMultiLevelSwitchCommandClass.java:99)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:241)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:207)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:201)[198:org.openhab.binding.zwave:2.0.0.201607010102]
    at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1278)[198:org.openhab.binding.zwave:2.0.0.201607010102]
2016-07-03 13:53:56.779 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 19: Too many retries. Discarding message: Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=19, callback=189, payload=13 02 26 02