Qubino ZMNHDD Slow

I've replaced a (faulty) Fibaro Dimmer 2 with a Qubino Flush dimmer. Dimming etc is working perfect but there is +- 2 seconds delay between an 'on' command and when the lamp actually turns on. In the living room, this isn't a big issue but I also have a qubino flush dimmer installed in the dressing and there it takes too long...
When I turned on a light with the Fibaro Dimmer 2, it's instant.

Anyone experiencing the same problem?

[matt (support)]

I don't have one, but I have heard they can be slow to broadcast out changes. You can turn on the debug Z-Wave logging checkbox (via the Interfaces->Z-Wave->Configure... menu item) then watch the log while you control it to see if any messages are coming in faster. Might be hard to tell though if it isn't in the same room unless you have a MacBook you can take to the switch.

Have you looked at the parameters? I think I remember that you can set the timing it takes to go to the required dimming level. I think it is parameter 65

Bjarne


Sent from my iPhone using Tapatalk Pro

Yeah, I've tried to play with the parameters but that didn't change the on-delay.
I found something strange: If the light is off and I define 15%, the light won't turn on. If I set it to 60% and then I dim it to 15%, it's working.
I've tried to play with the minimal % parameters, but that didn't change anything...

Can you do a "Write Device Details to Event Log" and paste them here.
Mine looks like this:

Indigo Z-Wave Version: 2.0.68
Node ID: 52
Model: Flush Micro Dimmer (ZMNHDD)
Model ID: 00010051
Manufacturer: Qubino
Manufacturer ID: 0159
Protocol Version: 4.05
Application Version: 1.01
Model Definition Version: 5
Library Type: 3
Class Name: Dimmable Power Switch
Class Hierarchy: 04 : 11 : 01
Command Class Base: 26
Command Versions: 20v1 60v4 30v1 25v1 86v1 27v1 72v1 8Ev1 70v1 31v7 32v4 73v1 59v1 5Av1 26v3 5Ev1 85v1
Encryption Status: Not Supported
Multi-Endpoint Types: 1:(11 : 01), 2:(20 : 00), 3:(20 : 00), 4:(21 : 01)
Multi-Endpoint Classes: 1:[5E 86 20 27 25 26 32 85 8E 59], 2:[5E 86 20 30 71 85 8E 59], 3:[5E 86 20 30 71 85 8E 59], 4:[5E 86 31 85 8E 59]
Multi-Instance Counts: - none -
Features: routing, beaming, energyMeter
Neighbors: 10
Associations: 1:[1] 2:[] 3:[] 4:[1] 5:[] 6:[] 7:[] 8:[] 9:[] 10:[] 11:[1]
Config Values: 1:0 2:0 3:0 100:9 101:9 65:100 66:3 110:32536 20:0 21:1 120:5 4:0 60:1 61:99 30:0

Can you also look what part number you have on the back?
Mine has ZMNHDD1 H1S2P1
I can see it was previously H1S1P1 but I had all my ZMNHDD:s sent to Qubino for upgrading firmware to firmware version 1.01 so Qubino has manually written over the S1 with an ink pen to S2.

Exactly the same here... ZMNHDD1 H1S2P1, manually overwritten the 2.

Code: Select all

Indigo Z-Wave Version: 2.0.68
Node ID: 29
Model: Flush Micro Dimmer (ZMNHDD)
Model ID: 00010051
Manufacturer: Qubino
Manufacturer ID: 0159
Protocol Version: 4.05
Application Version: 1.01
Model Definition Version: 5
Library Type: 3
Class Name: Dimmable Power Switch
Class Hierarchy: 04 : 11 : 01
Command Class Base: 26
Command Versions: 20v1 25v1 86v1 27v1 72v1 8Ev1 70v1 32v4 73v1 59v1 5Av1 26v3 5Ev1 85v1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, beaming, energyMeter
Neighbors: 5, 6, 11, 12, 13, 14, 15, 18, 19, 22, 24, 26, 28
Associations: 1:[1] 2:[] 3:[] 4:[1] 5:[] 6:[] 7:[] 8:[] 9:[] 10:[] 11:[1]
Config Values: 1:0 2:0 3:0 100:9 101:9 65:50 66:1 110:32536 20:0 21:1 120:5 4:0 60:20 61:99 30:0


Hmmm strange indeed!

When you get the 2 second delay from hitting on to when the light actually turns on are you doing it
1. via Indigo GUI
2. via mono-stable switch connected to I1?
3. via a radio button directly associated with the ZMNHDDx?

As Matt wrote above, can you enable debug logging and do dimming on/off via I1 and also via Indigo GUI and post your results here?
(Even better if you could open the debug log in text editor and paste the results from there since then we will have the time stamps as well.)

I´ll do some more checking with my ZMNHDD1 dimmers when I am back home tonight but I haven't seen those kind of delay issues with my devices and we do indeed seem to have the same firmware versions.

The +- 2s delay is happening both from L1 and via Indigo...

"MB: Dressing - Licht" is the Qubino
"MB - Licht" is the Fibaro Dimmer 2

Code: Select all

2017-02-10 10:11:56.109   Z-Wave   received "MB: Dressing - Licht" status update brightness 51
2017-02-10 10:11:56.110   Z-Wave Debug   queueing energy request of "029 - MB: Dressing - Licht" (activity detected)
2017-02-10 10:11:56.895   Z-Wave Debug   RCVD requestDimmerStatus: 01 09 00 04 00 1D 03 26 03 32 FB
2017-02-10 10:11:56.896   Z-Wave Debug   . .  requestDimmerStatus: node 029, endpoint None, value 50
2017-02-10 10:12:01.388   Z-Wave Debug   polling status of node "029 - MB: Dressing - Licht" (post-activity energy request)
2017-02-10 10:12:01.423   Z-Wave Debug   SENT requestMeterLevel: 01 0A 00 13 1D 03 32 01 00 25 DB 35
2017-02-10 10:12:01.713   Z-Wave Debug   RCVD requestMeterLevel: 01 14 00 04 00 1D 0E 32 02 21 24 00 00 00 01 00 01 00 00 00 01 C8
2017-02-10 10:12:01.715   Z-Wave Debug   . .  requestMeterLevel: node 029, endpoint None, meterType 01, raw value 2400...
2017-02-10 10:12:01.715   Z-Wave Debug   . .  requestMeterLevel: 0.1 kWh (float: 0.100000)
2017-02-10 10:12:01.716   Z-Wave Debug   SENT requestMeterLevel: 01 0A 00 13 1D 03 32 01 10 25 DC 22
2017-02-10 10:12:02.004   Z-Wave Debug   RCVD requestMeterLevel: 01 10 00 04 00 1D 0A 32 02 21 34 00 00 00 46 00 00 9F
2017-02-10 10:12:02.005   Z-Wave Debug   . .  requestMeterLevel: node 029, endpoint None, meterType 01, raw value 3400...
2017-02-10 10:12:02.005   Z-Wave Debug   . .  requestMeterLevel: 7.0 W (float: 7.000000)
2017-02-10 10:12:02.006   Z-Wave   received "MB: Dressing - Licht" power load to 7.0 W
2017-02-10 10:12:03.159   Z-Wave Debug   RCVD dimmerSetLevel: 01 0A 00 04 00 1D 04 26 01 00 00 CF
2017-02-10 10:12:03.160   Z-Wave Debug   . .  dimmerSetLevel: node 029, endpoint None, value 0
2017-02-10 10:12:03.161   Z-Wave   received "MB: Dressing - Licht" status update is off
2017-02-10 10:12:03.162   Z-Wave Debug   queueing energy request of "029 - MB: Dressing - Licht" (activity detected)
2017-02-10 10:12:03.952   Z-Wave Debug   RCVD requestDimmerStatus: 01 09 00 04 00 1D 03 26 03 00 C9
2017-02-10 10:12:03.953   Z-Wave Debug   . .  requestDimmerStatus: node 029, endpoint None, value 0
2017-02-10 10:12:08.459   Z-Wave Debug   polling status of node "029 - MB: Dressing - Licht" (post-activity energy request)
2017-02-10 10:12:08.482   Z-Wave Debug   SENT requestMeterLevel: 01 0A 00 13 1D 03 32 01 00 25 DD 33
2017-02-10 10:12:08.772   Z-Wave Debug   RCVD requestMeterLevel: 01 14 00 04 00 1D 0E 32 02 21 24 00 00 00 01 00 01 00 00 00 01 C8
2017-02-10 10:12:08.773   Z-Wave Debug   . .  requestMeterLevel: node 029, endpoint None, meterType 01, raw value 2400...
2017-02-10 10:12:08.774   Z-Wave Debug   . .  requestMeterLevel: 0.1 kWh (float: 0.100000)
2017-02-10 10:12:08.774   Z-Wave Debug   SENT requestMeterLevel: 01 0A 00 13 1D 03 32 01 10 25 DE 20
2017-02-10 10:12:09.062   Z-Wave Debug   RCVD requestMeterLevel: 01 10 00 04 00 1D 0A 32 02 21 34 00 00 00 00 00 00 D9
2017-02-10 10:12:09.063   Z-Wave Debug   . .  requestMeterLevel: node 029, endpoint None, meterType 01, raw value 3400...
2017-02-10 10:12:09.064   Z-Wave Debug   . .  requestMeterLevel: 0.0 W (float: 0.000000)
2017-02-10 10:12:09.064   Z-Wave   received "MB: Dressing - Licht" power load to 0.0 W
2017-02-10 10:12:15.262   Z-Wave Debug   SENT setMultiLevelValue: 01 0A 00 13 12 03 26 01 FF 25 DF D5
2017-02-10 10:12:15.295   Z-Wave   sent "MB - Licht" on
2017-02-10 10:12:15.296   Z-Wave Debug   queueing energy request of "018 - MB - Licht" (activity detected)
2017-02-10 10:12:15.910   Z-Wave Debug   RCVD requestDimmerStatus: 01 09 00 04 00 12 03 26 03 3B FD
2017-02-10 10:12:15.911   Z-Wave Debug   . .  requestDimmerStatus: node 018, endpoint None, value 59
2017-02-10 10:12:16.109   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 12 06 31 05 04 22 00 1E EF
2017-02-10 10:12:16.110   Z-Wave Debug   . .  requestVarSensorStatus: node 018, endpoint None, type 4, raw value 2200...
2017-02-10 10:12:16.111   Z-Wave Debug   . .  requestVarSensorStatus: 3.0 W (float: 3.000000)
2017-02-10 10:12:16.111   Z-Wave Debug   received "MB - Licht" power load to 3.0 W
2017-02-10 10:12:20.522   Z-Wave Debug   SENT setMultiLevelValue: 01 0A 00 13 12 03 26 01 00 25 E0 15
2017-02-10 10:12:20.554   Z-Wave   sent "MB - Licht" off
2017-02-10 10:12:20.555   Z-Wave Debug   ignoring duplicate energy request of "018 - MB - Licht" (activity detected)
2017-02-10 10:12:21.111   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 12 06 31 05 04 22 00 47 B6
2017-02-10 10:12:21.112   Z-Wave Debug   . .  requestVarSensorStatus: node 018, endpoint None, type 4, raw value 2200...
2017-02-10 10:12:21.112   Z-Wave Debug   . .  requestVarSensorStatus: 7.1 W (float: 7.100000)
2017-02-10 10:12:21.113   Z-Wave Debug   received "MB - Licht" power load to 7.1 W
2017-02-10 10:12:21.252   Z-Wave Debug   RCVD requestDimmerStatus: 01 09 00 04 00 12 03 26 03 00 C6
2017-02-10 10:12:21.253   Z-Wave Debug   . .  requestDimmerStatus: node 018, endpoint None, value 0
2017-02-10 10:12:25.629   Z-Wave Debug   polling status of node "018 - MB - Licht" (post-activity energy request)
2017-02-10 10:12:25.664   Z-Wave Debug   SENT requestMeterLevel: 01 0A 00 13 12 03 32 01 00 25 E1 00
2017-02-10 10:12:25.956   Z-Wave Debug   RCVD requestMeterLevel: 01 10 00 04 00 12 0A 32 02 21 44 00 00 00 3E 00 00 98
2017-02-10 10:12:25.958   Z-Wave Debug   . .  requestMeterLevel: node 018, endpoint None, meterType 01, raw value 4400...
2017-02-10 10:12:25.958   Z-Wave Debug   . .  requestMeterLevel: 0.62 kWh (float: 0.620000)
2017-02-10 10:12:25.959   Z-Wave Debug   SENT requestMeterLevel: 01 0A 00 13 12 03 32 01 10 25 E2 13
2017-02-10 10:12:26.245   Z-Wave Debug   RCVD requestMeterLevel: 01 0E 00 04 00 12 08 32 02 21 32 00 47 00 00 8B
2017-02-10 10:12:26.246   Z-Wave Debug   . .  requestMeterLevel: node 018, endpoint None, meterType 01, raw value 3200...
2017-02-10 10:12:26.246   Z-Wave Debug   . .  requestMeterLevel: 7.1 W (float: 7.100000)
2017-02-10 10:12:26.247   Z-Wave Debug   SENT setMultiLevelValue: 01 0A 00 13 1D 03 26 01 FF 25 E3 E6
2017-02-10 10:12:26.277   Z-Wave   sent "MB: Dressing - Licht" on
2017-02-10 10:12:26.279   Z-Wave Debug   queueing energy request of "029 - MB: Dressing - Licht" (activity detected)
2017-02-10 10:12:26.544   Z-Wave Debug   RCVD dimmerSetLevel: 01 0A 00 04 00 1D 04 26 01 32 00 FD
2017-02-10 10:12:26.545   Z-Wave Debug   . .  dimmerSetLevel: node 029, endpoint None, value 50
2017-02-10 10:12:27.093   Z-Wave Debug   RCVD requestDimmerStatus: 01 09 00 04 00 1D 03 26 03 32 FB
2017-02-10 10:12:27.094   Z-Wave Debug   . .  requestDimmerStatus: node 029, endpoint None, value 50
2017-02-10 10:12:31.074   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 12 06 31 05 04 22 00 00 F1
2017-02-10 10:12:31.075   Z-Wave Debug   . .  requestVarSensorStatus: node 018, endpoint None, type 4, raw value 2200...
2017-02-10 10:12:31.076   Z-Wave Debug   . .  requestVarSensorStatus: 0.0 W (float: 0.000000)
2017-02-10 10:12:31.076   Z-Wave Debug   received "MB - Licht" power load to 0.0 W
2017-02-10 10:12:33.710   Z-Wave Debug   polling status of node "029 - MB: Dressing - Licht" (post-activity energy request)
2017-02-10 10:12:33.756   Z-Wave Debug   SENT requestMeterLevel: 01 0A 00 13 1D 03 32 01 00 25 E4 0A
2017-02-10 10:12:34.046   Z-Wave Debug   RCVD requestMeterLevel: 01 14 00 04 00 1D 0E 32 02 21 24 00 00 00 01 00 01 00 00 00 01 C8
2017-02-10 10:12:34.048   Z-Wave Debug   . .  requestMeterLevel: node 029, endpoint None, meterType 01, raw value 2400...
2017-02-10 10:12:34.048   Z-Wave Debug   . .  requestMeterLevel: 0.1 kWh (float: 0.100000)
2017-02-10 10:12:34.049   Z-Wave Debug   SENT requestMeterLevel: 01 0A 00 13 1D 03 32 01 10 25 E5 1B
2017-02-10 10:12:34.337   Z-Wave Debug   RCVD requestMeterLevel: 01 10 00 04 00 1D 0A 32 02 21 34 00 00 00 42 00 00 9B
2017-02-10 10:12:34.338   Z-Wave Debug   . .  requestMeterLevel: node 029, endpoint None, meterType 01, raw value 3400...
2017-02-10 10:12:34.338   Z-Wave Debug   . .  requestMeterLevel: 6.6 W (float: 6.600000)
2017-02-10 10:12:34.339   Z-Wave   received "MB: Dressing - Licht" power load to 6.6 W
2017-02-10 10:12:34.592   Z-Wave Debug   SENT setMultiLevelValue: 01 0A 00 13 1D 03 26 01 00 25 E6 1C
2017-02-10 10:12:34.625   Z-Wave   sent "MB: Dressing - Licht" off
2017-02-10 10:12:34.626   Z-Wave Debug   queueing energy request of "029 - MB: Dressing - Licht" (activity detected)
2017-02-10 10:12:34.889   Z-Wave Debug   RCVD dimmerSetLevel: 01 0A 00 04 00 1D 04 26 01 00 00 CF
2017-02-10 10:12:34.890   Z-Wave Debug   . .  dimmerSetLevel: node 029, endpoint None, value 0
2017-02-10 10:12:35.149   Z-Wave Debug   RCVD requestDimmerStatus: 01 09 00 04 00 1D 03 26 03 00 C9
2017-02-10 10:12:35.150   Z-Wave Debug   . .  requestDimmerStatus: node 029, endpoint None, value 0
2017-02-10 10:12:39.770   Z-Wave Debug   polling status of node "029 - MB: Dressing - Licht" (post-activity energy request)
2017-02-10 10:12:39.793   Z-Wave Debug   SENT requestMeterLevel: 01 0A 00 13 1D 03 32 01 00 25 E7 09
2017-02-10 10:12:40.083   Z-Wave Debug   RCVD requestMeterLevel: 01 14 00 04 00 1D 0E 32 02 21 24 00 00 00 01 00 01 00 00 00 01 C8
2017-02-10 10:12:40.085   Z-Wave Debug   . .  requestMeterLevel: node 029, endpoint None, meterType 01, raw value 2400...
2017-02-10 10:12:40.085   Z-Wave Debug   . .  requestMeterLevel: 0.1 kWh (float: 0.100000)
2017-02-10 10:12:40.086   Z-Wave Debug   SENT requestMeterLevel: 01 0A 00 13 1D 03 32 01 10 25 E8 16
2017-02-10 10:12:40.374   Z-Wave Debug   RCVD requestMeterLevel: 01 10 00 04 00 1D 0A 32 02 21 34 00 00 00 00 00 00 D9
2017-02-10 10:12:40.375   Z-Wave Debug   . .  requestMeterLevel: node 029, endpoint None, meterType 01, raw value 3400...
2017-02-10 10:12:40.375   Z-Wave Debug   . .  requestMeterLevel: 0.0 W (float: 0.000000)
2017-02-10 10:12:40.376   Z-Wave   received "MB: Dressing - Licht" power load to 0.0 W
2017-02-10 10:12:43.346   Z-Wave Debug   RCVD requestAlarmSensorStatus: 01 10 00 04 00 20 0A 71 05 00 00 00 FF 07 00 01 08 44
2017-02-10 10:12:43.347   Z-Wave Debug   . .  requestAlarmSensorStatus: node 032, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
2017-02-10 10:12:43.347   Z-Wave Debug   . .  requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
2017-02-10 10:12:43.348   Z-Wave Debug   . .  requestAlarmSensorStatus: defnStatusByte 0

[matt (support)]

Your module, unlike CrazyFin's, is not reporting that is supports the endpoint commands (Command Versions should have a 60v4 in it). This is because you have to first enable that option. With the Qubinos the steps are complicated, but CrazyFin on another thread reports that this works:

1. Enable both the Input 2 Notification and Input 3 Notification checkboxes in the device settings dialog.
2. Exclude the module by doing a factory reset exclusion – press the service button for MORE than 6 seconds while controller is in exclusion mode (read the manual at ZMNBHDx manual about soft and hard reset).
3. Turn off power to the device and wait at least 30 seconds.
4. Put controller into inclusion mode without encryption.
5. Turn on power to the device and wait and after 5-15 seconds the device will sync itself into the controller.
6. Do a re-sync in Indigo and post your debug log results here if it still does not work properly.

Those steps will get the Qubino to report that is supports endpoint commands. At that point your module should behave identically to CrazyFin's, so will hopefully not have the delay. If it does then copy/paste the Event Log results showing both the define/sync as well as the delay problem again.

Hi Matt,

I followed the steps but no luck

Code: Select all

Indigo Z-Wave Version: 2.0.68
Node ID: 33
Model: Flush Micro Dimmer (ZMNHDD)
Model ID: 00010051
Manufacturer: Qubino
Manufacturer ID: 0159
Protocol Version: 4.05
Application Version: 1.01
Model Definition Version: 5
Library Type: 3
Class Name: Dimmable Power Switch
Class Hierarchy: 04 : 11 : 01
Command Class Base: 26
Command Versions: 20v1 25v1 86v1 27v1 72v1 8Ev1 70v1 32v4 73v1 59v1 5Av1 26v3 5Ev1 85v1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
[b]Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -[/b]
Features: routing, beaming, energyMeter
Neighbors: 5, 6, 11, 12, 13, 15, 18, 19, 22, 24, 26
Associations: 1:[1] 2:[] 3:[] 4:[1] 5:[] 6:[] 7:[] 8:[] 9:[] 10:[] 11:[1]
Config Values: 1:0 2:0 3:0 100:0 101:0 65:100 66:3 110:32536 20:0 21:0 120:5 4:0 60:1 61:99 30:0

Code: Select all

  Z-Wave Debug                    SENT setMultiLevelValue: 01 0A 00 13 21 03 26 01 FF 25 72 4B
   Z-Wave                          sent "MB: Dressing: Licht" on
   Z-Wave Debug                    queueing energy request of "033 - MB: Dressing: Licht" (activity detected)
   Z-Wave Debug                    RCVD dimmerSetLevel: 01 0A 00 04 00 21 04 26 01 63 00 90
   Z-Wave Debug                    . .  dimmerSetLevel: node 033, endpoint None, value 99
   Z-Wave Debug                    RCVD requestDimmerStatus: 01 09 00 04 00 21 03 26 03 63 96
   Z-Wave Debug                    . .  requestDimmerStatus: node 033, endpoint None, value 99
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 21 0A 32 02 21 34 00 00 00 1E 00 00 FB
   Z-Wave Debug                    . .  requestMeterLevel: node 033, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 3.0 W (float: 3.000000)
   Z-Wave                          received "MB: Dressing: Licht" power load to 3.0 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 21 0A 32 02 21 34 00 00 00 4B 00 00 AE
   Z-Wave Debug                    . .  requestMeterLevel: node 033, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 7.5 W (float: 7.500000)
   Z-Wave                          received "MB: Dressing: Licht" power load to 7.5 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 21 0A 32 02 21 34 00 00 00 5C 00 00 B9
   Z-Wave Debug                    . .  requestMeterLevel: node 033, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 9.2 W (float: 9.200000)
   Z-Wave                          received "MB: Dressing: Licht" power load to 9.2 W
   Z-Wave Debug                    polling status of node "033 - MB: Dressing: Licht" (post-activity energy request)
   Z-Wave Debug                    SENT requestMeterLevel: 01 0A 00 13 21 03 32 01 00 25 73 A1
   Z-Wave Debug                    RCVD requestMeterLevel: 01 14 00 04 00 21 0E 32 02 21 24 00 00 00 00 00 01 00 00 00 00 F4
   Z-Wave Debug                    . .  requestMeterLevel: node 033, endpoint None, meterType 01, raw value 2400...
   Z-Wave Debug                    . .  requestMeterLevel: 0.0 kWh (float: 0.000000)
   Z-Wave Debug                    SENT requestMeterLevel: 01 0A 00 13 21 03 32 01 10 25 74 B6
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 21 0A 32 02 21 34 00 00 00 5B 00 00 BE
   Z-Wave Debug                    . .  requestMeterLevel: node 033, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 9.1 W (float: 9.100000)
   Z-Wave                          received "MB: Dressing: Licht" power load to 9.1 W
   Z-Wave Debug                    SENT setMultiLevelValue: 01 0A 00 13 21 03 26 01 00 25 75 B3
   Z-Wave                          sent "MB: Dressing: Licht" off
   Z-Wave Debug                    queueing energy request of "033 - MB: Dressing: Licht" (activity detected)
   Z-Wave Debug                    RCVD dimmerSetLevel: 01 0A 00 04 00 21 04 26 01 00 00 F3
   Z-Wave Debug                    . .  dimmerSetLevel: node 033, endpoint None, value 0
   Z-Wave Debug                    RCVD requestDimmerStatus: 01 09 00 04 00 21 03 26 03 00 F5
   Z-Wave Debug                    . .  requestDimmerStatus: node 033, endpoint None, value 0
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 21 0A 32 02 21 34 00 00 00 4A 00 00 AF
   Z-Wave Debug                    . .  requestMeterLevel: node 033, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 7.4 W (float: 7.400000)
   Z-Wave                          received "MB: Dressing: Licht" power load to 7.4 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 21 0A 32 02 21 34 00 00 00 1E 00 00 FB
   Z-Wave Debug                    . .  requestMeterLevel: node 033, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 3.0 W (float: 3.000000)
   Z-Wave                          received "MB: Dressing: Licht" power load to 3.0 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 21 0A 32 02 21 34 00 00 00 01 00 00 E4
   Z-Wave Debug                    . .  requestMeterLevel: node 033, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 0.1 W (float: 0.100000)
   Z-Wave                          received "MB: Dressing: Licht" power load to 0.1 W
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 10 00 04 00 1E 0A 71 05 00 00 00 FF 07 00 01 08 7A
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 030, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
   Z-Wave Debug                    . .  requestAlarmSensorStatus: defnStatusByte 0
   Z-Wave                          received "Living: Tamper - Achteraan" status update is off
   Z-Wave Debug                    RCVD sensorSetLevel: 01 09 00 04 08 1E 03 20 01 00 C6
   Z-Wave Debug                    . .  sensorSetLevel: node 030, endpoint None, cmdClass 20, value 0
   Z-Wave Debug                    received "Living: Motion Sensor - Achteraan" status update is off
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 10 00 04 00 15 0A 71 05 00 00 00 FF 07 00 01 08 71
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 021, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
   Z-Wave Debug                    . .  requestAlarmSensorStatus: defnStatusByte 0
   Z-Wave Debug                    received "Keuken: Tilt/Tamper" status update is off
   Z-Wave Debug                    RCVD sensorSetLevel: 01 09 00 04 00 1E 03 20 01 00 CE
   Z-Wave Debug                    . .  sensorSetLevel: node 030, endpoint None, cmdClass 20, value 0
   Z-Wave Debug                    filtering duplicate command -- old: 20, 0, 0, new: 20, 0, 0 (0.0023 secs)
   Z-Wave Debug                    RCVD sensorSetLevel: 01 09 00 04 08 15 03 20 01 00 CD
   Z-Wave Debug                    . .  sensorSetLevel: node 021, endpoint None, cmdClass 20, value 0
   Z-Wave Debug                    received "Keuken: Motion Sensor" status update is off
   Z-Wave Debug                    RCVD sensorSetLevel: 01 09 00 04 00 15 03 20 01 00 C5
   Z-Wave Debug                    . .  sensorSetLevel: node 021, endpoint None, cmdClass 20, value 0
   Z-Wave Debug                    filtering duplicate command -- old: 20, 0, 0, new: 20, 0, 0 (0.0009 secs)
   Z-Wave Debug                    polling status of node "033 - MB: Dressing: Licht" (post-activity energy request)
   Z-Wave Debug                    SENT requestMeterLevel: 01 0A 00 13 21 03 32 01 00 25 76 A4
   Z-Wave Debug                    RCVD requestMeterLevel: 01 14 00 04 00 21 0E 32 02 21 24 00 00 00 00 00 01 00 00 00 00 F4
   Z-Wave Debug                    . .  requestMeterLevel: node 033, endpoint None, meterType 01, raw value 2400...
   Z-Wave Debug                    . .  requestMeterLevel: 0.0 kWh (float: 0.000000)
   Z-Wave Debug                    SENT requestMeterLevel: 01 0A 00 13 21 03 32 01 10 25 77 B5
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 21 0A 32 02 21 34 00 00 00 00 00 00 E5
   Z-Wave Debug                    . .  requestMeterLevel: node 033, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 0.0 W (float: 0.000000)
   Z-Wave                          received "MB: Dressing: Licht" power load to 0.0 W

[matt (support)]

The log is showing the steps didn't "take", as it still is not reporting that the module supports the endpoint command class. I know the module can be very picky about the reset steps, so you might want to try them again. CrazyFin might chime in here as well with tips/suggestions as he is the expert on resetting these modules.

Ok, I will try it again begin next week - any tips/experiences are appreciated! Thanks for the support!

@Woetjes:
Yepp, Matt is correct. You have not been able to do the "soft-reset" properly since your re-sync still shows:

"Command Versions: 20v1 25v1 86v1 27v1 72v1 8Ev1 70v1 32v4 73v1 59v1 5Av1 26v3 5Ev1 85v1"

If you have done it properly it should show:
Command Versions: 20v1 60v4 30v1 25v1 86v1 27v1 72v1 8Ev1 70v1 31v7 32v4 73v1 59v1 5Av1 26v3 5Ev1 85v1

Most important steps are in your particular case:

1. In Indigo go to Edit Device Settings and set Input 2 Notifications and Input 3 Notifications to Enabled.
2. Initiate an Exclude Device in Indigo and then press service button S on device for 3-6 seconds. VERY IMPORTANT: NO MORE THAN 6 SECONDS because if you do that then you do a Factory Reset of the device to default values/settings instead of a "soft reset". I usually press it for like 3-4 seconds and then release and watch the debug log in Indigo to verify that the device has been excluded.
3. Turn off power to the device and wait 30 seconds minimum.
4. After 30 seconds wait, put Indigo into Include Device mode (no encryption).
5. Enable power to the device and after 5-10 seconds auto-inclusion will complete.
6. Now re-sync device in Indigo and verify that you see the command version 60v4 and 30v1 as I shown above.

Let me know how it goes.

By the way, which Z-Wave controller/stick are you using?

Thanks CrazyFin and Matt! That did the trick (no more than 6 seconds).
The delay is better now (still not as fast as the Fibaro ones though) but I can live with it

Hi,
I have a similar problem on recently installed Qubino dimmers. Amazingly I got both wired in first time (only took an hour to get the wiring neat enough to get them both to fit inside a double gang socket. I have them controlled with a 3-position momentary switch, using the parameter 20 from the GUI and have a push switch connnected to I3 on both.
I updated the receive notifications for I3 and excluded and included again, and Indigo recognises the switches being pressed, albeit on I2 but that is fine.
However, it takes up to 5 seconds holding the switch down for Indigo to receive the notification, which as I want to use it to toggle other lights on or off is not going to be acceptable to my users (aka my wife) .
Should it be that slow?

This is the sync details from when I included it.

Z-Wave Syncing - started for "020 - Dimmable Power Switch"
Z-Wave Syncing - retrieved module neighbors list: 2, 3, 4, 6, 8, 13, 18
Z-Wave Syncing - assigning return route to "020 - Dimmable Power Switch"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Qubino - 0159, Flush Micro Dimmer (ZMNHDD) - 00010051
Z-Wave Syncing - retrieved protocol version 4.05, app version 3.05
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Mulitlevel Switch : Dimmable Power Switch (04 : 11 : 01, base 26)
Z-Wave Syncing - retrieved command classes: 20v1 85v1 86v1 8Ev1 59v1 5Av1 5Ev1 60v4 30v1 25v1 26v3 27v1 72v1 70v1 71v1 32v4 73v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Syncing - retrieved multi-endpoint types: 1:(11 : 01), 2:(20 : 00)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 85 8E 59 27 25 26 32 71], 2:[5E 85 8E 59 30 71]
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - retrieved group 4 associations: []
Z-Wave Syncing - retrieved group 5 associations: []
Z-Wave Syncing - retrieved group 6 associations: []
Z-Wave Syncing - retrieved group 7 associations: []
Z-Wave Syncing - retrieved group 8 associations: []
Z-Wave Syncing - retrieved group 9 associations: []
Z-Wave Syncing - retrieved group 10 associations: []
Z-Wave Syncing - retrieved group 11 associations: []
Z-Wave Syncing - added group 1 multi association to interface
Z-Wave Syncing - added group 4 multi association to interface
Z-Wave Syncing - added group 11 multi association to interface
Z-Wave Syncing - retrieved parameter 30 "Power up state" is 0 "Last State"
Z-Wave Syncing - retrieved parameter 100 "Input 2 notifications" is 0 "Disabled"
Z-Wave Syncing - retrieved parameter 101 "Input 3 notifications" is 9 "Enabled"
Z-Wave Syncing - retrieved parameter 1 "Input 1 mode" is 0 "Momentary"
Z-Wave Syncing - retrieved parameter 2 "Input 2 mode" is 0 "Momentary"
Z-Wave Syncing - retrieved parameter 3 "Input 2 type" is 0 "Normally Open"
Z-Wave Syncing - retrieved parameter 4 "Input 3 type" is 0 "Normally Open"
Z-Wave Syncing - retrieved parameter 20 "Enable 3-way switch mode" is true
Z-Wave Syncing - retrieved parameter 21 "Enable double-click to maximum brightness" is true
Z-Wave Syncing - retrieved parameter 60 "Minimum value" is 1
Z-Wave Syncing - retrieved parameter 61 "Maximum value" is 99
Z-Wave Syncing - retrieved parameter 65 "Button tap duration" is 100 * 10 milliseconds
Z-Wave Syncing - retrieved parameter 66 "Button down duration" is 3 seconds
Z-Wave Syncing - retrieved parameter 110 "Temperature offset" is 32536 * 0.1 degrees
Z-Wave Syncing - retrieved parameter 120 "Temperature sensitivity" is 5 * 0.1 degrees
Z-Wave Syncing - changed device "Kitchen spots 1" address from undefined to 020
Z-Wave Syncing - changed device "014 - Input 2" address from undefined to 020
Z-Wave Syncing - changed device "014 - Input 3" address from undefined to 020
Z-Wave Syncing - changed device "014 - Temperature" address from undefined to 020
Z-Wave Syncing - complete

This is the zwave debug log showing the switch connected to I3 (end point 2) being pressed. I had to hold if for 5 seconds to see anything. Second is the results from turning off the light using the other switch connected to I1&I2. That responds immediately.

Z-Wave Debug RCVD multiEndPointPacket: 01 0D 00 04 00 15 07 60 0D 02 01 30 03 FF 46
Z-Wave Debug . . multiEndPointPacket: node 021, endPoint 2
Z-Wave Debug RCVD requestBinarySensorStatus: 01 09 00 04 00 15 03 30 03 FF FF
Z-Wave Debug . . requestBinarySensorStatus: node 021, endpoint 2, value 255
Z-Wave Debug RCVD requestMeterLevel: 01 18 00 04 00 02 12 32 02 21 64 00 00 14 FD 02 58 00 00 14 FD 00 00 00 00 DC
Z-Wave Debug . . requestMeterLevel: node 002, endpoint None, meterType 01, raw value 6400...
Z-Wave Debug . . requestMeterLevel: 5.373 kWh (float: 5.373000)
Z-Wave Debug RCVD requestMeterLevel: 01 18 00 04 00 02 12 32 02 21 74 00 00 00 00 00 00 00 00 00 00 00 00 00 00 96
Z-Wave Debug . . requestMeterLevel: node 002, endpoint None, meterType 01, raw value 7400...
Z-Wave Debug . . requestMeterLevel: 0.000 W (float: 0.000000)
Z-Wave Debug RCVD multiEndPointPacket: 01 13 00 04 00 15 0D 60 0D 02 01 71 05 00 00 00 FF 07 08 00 1A
Z-Wave Debug . . multiEndPointPacket: node 021, endPoint 2
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 15 09 71 05 00 00 00 FF 07 08 00 FF
Z-Wave Debug . . requestAlarmSensorStatus: node 021, endpoint 2, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
Z-Wave Debug RCVD multiEndPointPacket: 01 0D 00 04 00 15 07 60 0D 02 01 30 03 00 B9
Z-Wave Debug . . multiEndPointPacket: node 021, endPoint 2
Z-Wave Debug RCVD requestBinarySensorStatus: 01 09 00 04 00 15 03 30 03 00 FF
Z-Wave Debug . . requestBinarySensorStatus: node 021, endpoint 2, value 0
Z-Wave Debug RCVD multiEndPointPacket: 01 13 00 04 00 15 0D 60 0D 02 01 71 05 00 00 00 FF 07 00 00 12
Z-Wave Debug . . multiEndPointPacket: node 021, endPoint 2
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 15 09 71 05 00 00 00 FF 07 00 00 FF
Z-Wave Debug . . requestAlarmSensorStatus: node 021, endpoint 2, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
Z-Wave Debug RCVD requestMeterLevel: 01 10 00 04 00 08 0A 32 02 21 44 00 00 58 A4 00 00 40
Z-Wave Debug . . requestMeterLevel: node 008, endpoint None, meterType 01, raw value 4400...
Z-Wave Debug . . requestMeterLevel: 226.92 kWh (float: 226.920000)

Turning off light

Z-Wave Debug RCVD multiEndPointPacket: 01 0E 00 04 00 14 08 60 0D 01 01 26 01 00 00 A3
Z-Wave Debug . . multiEndPointPacket: node 020, endPoint 1
Z-Wave Debug RCVD dimmerSetLevel: 01 0A 00 04 00 14 04 26 01 00 00 FF
Z-Wave Debug . . dimmerSetLevel: node 020, endpoint 1, value 0
Z-Wave Debug RCVD multiEndPointPacket: 01 0D 00 04 00 14 07 60 0D 01 01 26 03 00 AD
Z-Wave Debug . . multiEndPointPacket: node 020, endPoint 1
Z-Wave Debug RCVD requestDimmerStatus: 01 09 00 04 00 14 03 26 03 00 FF
Z-Wave Debug . . requestDimmerStatus: node 020, endpoint 1, value 0
Z-Wave Debug RCVD multiEndPointPacket: 01 18 00 04 00 14 12 60 0D 01 01 32 02 21 34 00 00 00 00 00 00 00 00 00 00 AD
Z-Wave Debug . . multiEndPointPacket: node 020, endPoint 1
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 14 0E 32 02 21 34 00 00 00 00 00 00 00 00 00 00 FF
Z-Wave Debug . . requestMeterLevel: node 020, endpoint 1, meterType 01, raw value 3400...
Z-Wave Debug . . requestMeterLevel: 0.0 W (float: 0.000000)