Zwave + Qubino Dimmer and mono-stable switch (Push-Button)

I use the qubino dimmer with openhab2 and latest zwave build. All works fine with bi-stable switch, but when I use a pushbutton it is not possible to turn the light off when on and the other way around.

Is this a known issue a bug or by design?

  • OH2 Version: 2.0.0, 2017-01-20T15:52:06

  • Device name: Flush Dimmer Plus (ZMNHDD)

  • Device version: H1S3P3

  • Link to database:

Probably you have to configure the device - for most devices there is an option to use a mono or bistable switch - you should check that this is correct for your configuration in the device parameters. Have a read of the manual - it should say there.

Chris, i did configure the device and the hardware works just fine. When I push the button the lights go on and off. In openHAB it reports the dimmer status correctly. The problem is that the switch and dimmer in openHAB cannot turn the lights off when they are on and on when they are off. The light flashes en returns (slowly) to the previous state. I looks like the zwave binding acts like a bi-state switch…

Ok - that’s not clear from your report! When you say you use a pushbutton - do you mean that this is a pushbutton in the UI or a physical pushbutton :confused:?

:slight_smile: I use a physical push button.

http://www.abb.com/SmartLinks/Default.aspx?gid=ABB2CKA001413A0517

Ok - now I’m more confused…

So you can turn it on and of if you use a physical bistable button?

But it doesn’t work when you use a physical pushbutton?

If we’re just talking about physical buttons, then isn’t this a physical problem?

Can you provide a debug log please. The commands normally sent are simply ON and OFF, so it should be down to the device to interpret that appropriately.

Let me try again.

If I use a bi-stable physical switch connected to the dimmer on L1 everything works as expected. Light turn on/off with the physical switch and via the virtual dimmer/switch in openHAB.

When I change the physical bi-state switch for a physical mono-stable switch (push-button) and configure the device accordingly the physical part works. The light go on after one push an turn off after another push of the physical button. Now the tricky part begins. The virtual switch/dimmer do not work in combination with the physical push button. If I turn on the light with the physical switch and try to turn it off with the virtual switch the light turn off quickly and return to the on state dimmed/slowly. Where I expect it to dim slowly to the off state.

I will send the log.

17:37:26.813 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_device_688ad3c3_node5_switch_binary' received command ON
17:37:26.815 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_688ad3c3_node5_switch_binary changed from OFF to ON
17:37:28.656 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_device_688ad3c3_node5_switch_binary' received command OFF
17:37:28.658 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_688ad3c3_node5_switch_binary changed from ON to OFF
17:37:30.293 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_device_688ad3c3_node5_switch_binary' received command ON
17:37:30.295 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_688ad3c3_node5_switch_binary changed from OFF to ON
17:37:32.340 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_device_688ad3c3_node5_switch_dimmer' received command ON
17:37:32.343 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_688ad3c3_node5_switch_dimmer changed from 0 to 100
17:37:34.163 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_device_688ad3c3_node5_switch_dimmer' received command OFF
17:37:34.165 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_688ad3c3_node5_switch_dimmer changed from 100 to 0
17:37:37.456 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_device_688ad3c3_node5_switch_dimmer' received command ON
17:37:37.458 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_688ad3c3_node5_switch_dimmer changed from 0 to 100

I debug mode:

20:35:41.904 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_device_688ad3c3_node5_switch_dimmer' received command OFF
20:35:41.905 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Command received zwave:device:688ad3c3:node5:switch_dimmer --> OFF
20:35:41.905 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 5: Creating new message for command SWITCH_MULTILEVEL_SET
20:35:41.905 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 3. Queue={}
20:35:41.907 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_688ad3c3_node5_switch_dimmer changed from 100 to 0
20:35:47.910 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_device_688ad3c3_node5_switch_dimmer' received command ON
20:35:47.910 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Command received zwave:device:688ad3c3:node5:switch_dimmer --> ON
20:35:47.910 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 5: Creating new message for command SWITCH_MULTILEVEL_SET
20:35:47.911 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 4. Queue={}
20:35:47.912 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_688ad3c3_node5_switch_dimmer changed from 0 to 100

Ok - understood. I use a number of Qubino devices, and a lot of Fibaro - all with pushbuttons, and they work fine.

I guess you trimmed this down - I don’t see any information about the data being sent - can you provide the full log around this time please?

I just locked myself out of my openhab server. Will set up a test first thing tomorrow morning and will send you the complete log files.

Back up and running:

Here is the log for the following case:

Physical mono-stable switch, light is off. I try to turn the light on in openhab, light flashes on and then dims back to the off state.

10:52:27.300 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_device_688ad3c3_node5_switch_binary' received command ON
10:52:27.301 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Command received zwave:device:688ad3c3:node5:switch_binary --> ON
10:52:27.301 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 5: Creating new message for application command SWITCH_BINARY_SET
10:52:27.301 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
10:52:27.301 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
10:52:27.301 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 05 03 25 01 FF 25 28 36 
10:52:27.302 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 5: Sending REQUEST Message = 01 0A 00 13 05 03 25 01 FF 25 28 36 
10:52:27.303 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_688ad3c3_node5_switch_binary changed from OFF to ON
10:52:27.307 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
10:52:27.307 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:52:27.307 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
10:52:27.307 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
10:52:27.307 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
10:52:27.307 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 5: Sent Data successfully placed on stack.
10:52:27.326 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 28 00 00 02 C1 
10:52:27.327 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:52:27.327 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 28 00 00 02 00 00 CF 
10:52:27.327 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 28 00 00 02 00 00 CF 
10:52:27.327 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=28 00 00 02 
10:52:27.327 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 5: SendData Request. CallBack ID = 40, Status = Transmission complete and ACK received(0)
10:52:27.327 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Starting initialisation from DONE
10:52:27.327 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@3c08f29d already registered
10:52:27.327 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=5, callback=40, payload=05 03 25 01 FF 
10:52:27.327 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=28 00 00 02 
10:52:27.327 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=40, expected=SendData, cancelled=false        transaction complete!
10:52:27.327 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
10:52:27.327 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
10:52:27.327 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Response processed after 25ms/4135ms.

replaced the physical mono-stable switch with a bi-stable switch. Changed the config (1) for mono to bi-stable. The light is off and send the on command via the virtual switch; resulting in the light turning on slowly:

10:57:35.239 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_device_688ad3c3_node5_switch_binary' received command ON
10:57:35.240 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Command received zwave:device:688ad3c3:node5:switch_binary --> ON
10:57:35.240 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 5: Creating new message for application command SWITCH_BINARY_SET
10:57:35.240 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
10:57:35.240 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
10:57:35.240 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 05 03 25 01 FF 25 2E 30 
10:57:35.240 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 5: Sending REQUEST Message = 01 0A 00 13 05 03 25 01 FF 25 2E 30 
10:57:35.241 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_688ad3c3_node5_switch_binary changed from OFF to ON
10:57:35.246 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
10:57:35.246 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:57:35.246 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
10:57:35.246 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
10:57:35.246 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
10:57:35.246 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 5: Sent Data successfully placed on stack.
10:57:35.265 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 2E 00 00 03 C6 
10:57:35.266 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:57:35.266 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 2E 00 00 03 00 00 C8 
10:57:35.266 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 2E 00 00 03 00 00 C8 
10:57:35.266 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=2E 00 00 03 
10:57:35.266 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 5: SendData Request. CallBack ID = 46, Status = Transmission complete and ACK received(0)
10:57:35.266 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Starting initialisation from DONE
10:57:35.266 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@3c08f29d already registered
10:57:35.266 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=5, callback=46, payload=05 03 25 01 FF 
10:57:35.266 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=2E 00 00 03 
10:57:35.266 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=46, expected=SendData, cancelled=false        transaction complete!
10:57:35.266 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
10:57:35.266 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
10:57:35.266 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Response processed after 25ms/4135ms.

Problem solved! I connected the mono-stable switch in NC mode, all works fine in NO mode. Thanks for your help!

@RPJacobs how do you use the qubino flush Dimmer with a two stable Switch? I can’t get it work properly.

Can you please list your Parameter settings?

Thanks