No events from a Qubino ZMNHSD DIN Rail Dimmer

Add-ons Bindings
,
1

Hi,

I am trying to use a Qubino DIN Dimmer with openhab2 (snapshots on an raspberrypi 3). The thing is found, sending state changes from openhab to the device works and with polling I can get the state of the dimmer. However, when pressing a button connected I don’t see any events. I associated the controller in group 1 (and all other ones, just to be sure). In debug mode I see reports like this when pressing my wall switch:

2017-03-29 17:20:30.570 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 10 07 60 0D 01 00 20 01 FF 53 
2017-03-29 17:20:30.575 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-29 17:20:30.578 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0D 00 04 00 10 07 60 0D 01 00 20 01 FF 53 
2017-03-29 17:20:30.580 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0D 00 04 00 10 07 60 0D 01 00 20 01 FF 53 
2017-03-29 17:20:30.584 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 10 07 60 0D 01 00 20 01 FF 
2017-03-29 17:20:30.585 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 16: Application Command Request (ALIVE:DONE)
2017-03-29 17:20:30.588 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 16: Starting initialisation from DONE
2017-03-29 17:20:30.591 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1fd4f3c already registered
2017-03-29 17:20:30.594 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 16: Incoming command class MULTI_INSTANCE
2017-03-29 17:20:30.596 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 16: Received MULTI_INSTANCE command V0
2017-03-29 17:20:30.599 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 16: Requested Command Class = BASIC (0x20)
2017-03-29 17:20:30.602 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 16: Endpoint 1 not found. Cannot set command classes.
2017-03-29 17:20:30.605 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=16, callback=45, payload=10 03 26 01 00 
2017-03-29 17:20:30.609 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 10 07 60 0D 01 00 20 01 FF 
2017-03-29 17:20:30.611 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=45, expected=SendData, cancelled=false      MISMATCH
2017-03-29 17:20:30.971 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 10 07 60 0D 01 00 20 01 00 AC 
2017-03-29 17:20:30.977 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-29 17:20:30.981 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0D 00 04 00 10 07 60 0D 01 00 20 01 00 AC 
2017-03-29 17:20:30.984 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0D 00 04 00 10 07 60 0D 01 00 20 01 00 AC 
2017-03-29 17:20:30.987 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 10 07 60 0D 01 00 20 01 00 
2017-03-29 17:20:30.990 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 16: Application Command Request (ALIVE:DONE)
2017-03-29 17:20:30.993 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 16: Starting initialisation from DONE
2017-03-29 17:20:30.996 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1fd4f3c already registered
2017-03-29 17:20:30.998 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 16: Incoming command class MULTI_INSTANCE
2017-03-29 17:20:31.001 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 16: Received MULTI_INSTANCE command V0
2017-03-29 17:20:31.004 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 16: Requested Command Class = BASIC (0x20)
2017-03-29 17:20:31.007 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 16: Endpoint 1 not found. Cannot set command classes.
2017-03-29 17:20:31.011 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=16, callback=45, payload=10 03 26 01 00 
2017-03-29 17:20:31.014 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 10 07 60 0D 01 00 20 01 00 
2017-03-29 17:20:31.017 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=45, expected=SendData, cancelled=false      MISMATCH
2017-03-29 17:20:31.878 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 00 10 08 60 0D 01 00 26 01 3F 01 98 
2017-03-29 17:20:31.880 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-29 17:20:31.882 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0E 00 04 00 10 08 60 0D 01 00 26 01 3F 01 98 
2017-03-29 17:20:31.884 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0E 00 04 00 10 08 60 0D 01 00 26 01 3F 01 98 
2017-03-29 17:20:31.886 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 10 08 60 0D 01 00 26 01 3F 01 
2017-03-29 17:20:31.887 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 16: Application Command Request (ALIVE:DONE)
2017-03-29 17:20:31.889 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 16: Starting initialisation from DONE
2017-03-29 17:20:31.890 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1fd4f3c already registered
2017-03-29 17:20:31.891 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 16: Incoming command class MULTI_INSTANCE
2017-03-29 17:20:31.892 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 16: Received MULTI_INSTANCE command V0
2017-03-29 17:20:31.894 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 16: Requested Command Class = SWITCH_MULTILEVEL (0x26)
2017-03-29 17:20:31.895 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 16: Endpoint 1 not found. Cannot set command classes.
2017-03-29 17:20:31.897 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=16, callback=45, payload=10 03 26 01 00 
2017-03-29 17:20:31.899 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 10 08 60 0D 01 00 26 01 3F 01 
2017-03-29 17:20:31.900 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=45, expected=SendData, cancelled=false      MISMATCH

Unfortunately I know nothing about these things so I would be happy if anyone could tell me what’s going on.

Thanks in advance
Tobias

2

I have the same problem in my environment (Rasp 3 and RaZberry)! I opened a ticket to Qubino and wait for a solution.

Martin

3

Does no one have any idea how to fix this? Are more debug logs needed? Or is this some limitation of the dimmers?

4

I had a email conversation with Qubino. After some try and error actions, here’s how I managed to fix the issue:

in expert UI unter Configuration -> Expert Commands -> Assotiation -> Group 1, Node: Z-Way 1 -> Remove
Configuration -> Expert Commands -> MultiChannelAssotiation -> Group 1, Node: Z-Way, Instance 1 -> Remove

in expert UI unter Configuration -> Expert Commands -> Assotiation -> Group 1, Node: Z-Way 1 -> Set
Configuration -> Expert Commands -> MultiChannelAssotiation -> Group 1, Node: Z-Way, Instance 1 -> Set

5

I am not sure that I understand. I don’t have an “expert UI” to configure things, just Paper and HABmin. In both I tried removing and re-adding the controller to the association groups but nothing helped.

1 Like
6

you need to configure that in the z-wave.me UI. You should reach the expert version via:
http://yourIPadress:8083/expert/
then go to the Configuration Tab -> Expert commands
select the DIN dimmer in the dropdown field and here you can execute the commands

7

I see. Well, I do not have the z-wave.me software. :worried:

8

what z-Wave device do you use? An USB stick or the Razberry board

9

The UZB stick. I wonder if the serial protocol is specified somewhere to send the commands directly to the stick?

10

Sorry I can’t help you here, lets try contact Qubino direkt.

11

No - the serial protocol is not publicly released and would be very complex to implement.

You should be able to do the same thing in HABmin - the zwave binding should use the multi-channel association to configure the associations if it’s available, and that should ensure that the Qubino devices start reporting.

12

Where can I configure that? I couldn’t find anything with google, and clicking around in HABmin doesn’t show anything either. I’m sorry for these basic questions but I am really new to this.

Thanks in advance
Tobias

13

Hmmm - there should be an associations configuration for the device in HABmin. If you don’t get the device configuration, then there’s something a bit more fundamental wrong I suspect.

14

This is all I can see for configuring the associations:

Screenshot_20170405_143329.png1077×635 20.2 KB

15

Yep - that’s the page your after.

However I’ve just realised there’s no way to remove an association from a group that only has 1 association allowed and you need to do that here so I’ll have to update the binding to resolve this.

1 Like
16

I’ll keep an eye on updates to the binding then. :slight_smile:

17

I’m having the same problem with the Qubino DIN dimmers.
@chris If there’s anything I (we) can do to help/support/test, please give a shout. Thanks in advance!

18

The missing Qubino status updates are also discussed here.