Qubino dimmer ZMNHDD1 / ZMNHDD ignoring param 66 and 65!?

I have about 8 of the Qubino Flush Dimmer ZMNHDD1 / ZMNHDDx.
Most of them have firmware label H1S2P2 and I have one that I bought yesterday that has firmware H1S3P5 which is the latest according to Qubino.

However, neither firmware models seems to follow the setting of parameter 66 (dimming speed) and parameter 65 (dimming speed to off and on). No matter what value I set to param 65 and 66, the ZMNHDD1 just completely ignores it or actually, sees it as its default values. That is param 66 = 3 seconds dimming speed up and down and param 65 = 100 which equals to 1 seconds, each step is 10 ms.

Can anyone else of you test param 66 and param 65 on your ZMNHDDx dimmers and see if you can get a VERY slow up and down dimming speed by setting param 66 to for example 20 which should mean that dimming from zero up to 100 should take 20 seconds when keeping a momentary push button connected to I1 pressed.

Please try also with setting the parameter 65 to for example 255 which means that time from max down to zero when clicking the push button to shut off the lamp should take 255 * 10 ms = 2.5 seconds.

I have contacted Qubino a month ago but they just can't to replicate this bug and they claim that param 65 and 66 works as they should when they test.
I initially thought it was a firmware bug with H1S2P2 but I got quite disappointed when the brand new one I bought yesterday with H1S3P5 firmware has exactly the same problem.

I have verified that param 65 and 66 are indeed set to new values which can be seen in the device output log:

Indigo Z-Wave Version: 2.0.111
Node ID: 111
Model: Flush Micro Dimmer (ZMNHDD)
Model ID: 00010051
Manufacturer: Qubino
Manufacturer ID: 0159
Protocol Version: 4.05
Application Version: 3.07
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 71v1 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: 3, 4, 6, 8, 12, 32, 49, 107
Associations: 1:[1] 2:[] 3:[] 4:[1] 5:[] 6:[] 7:[] 8:[] 9:[] 10:[] 11:[1]
Config Values: 1:0 2:0 3:0 4:0 65:255 66:20 20:0 21:0 30:0 100:0 101:0 110:32536 120:5 60:1 61:99

Ok this IS indeed an issue with Indigo?!

I have been discussing back and forth with Qubino for about 3 weeks now and they just can't replicate this issue.

I decided to test with Open ZWave Coptrol Panel and the latest Open Z-Wave library (1.4.2757).
I disabled the ZWave.ME UZB1 controller on my MAC dev machine and started up OZWCP and connected it to the controller.

I currently have only device in my dev environment and it is one of my ZMNHDD1 that is running on the latest firmware (H1S3P5 on the label on the device).

I can see the ZMNHDD1 in my OZWCP and when I check what the current parameters are for parameter 65 and 66 then OZWCP reports back 100 and 3 which are the default values?!?!
As you can see in my post above I HAD set the values to 255 for param 65 (time in milliseconds * 10 for on/off) and 20 for param 66 (time to dim up and down in seconds)

VERY STRANGE that it indeed looks like in Indigo that I have set new values but when starting another platform like OZWCP and when it reads the parameter values from the device they are still on their default values (param 65 has 100 as default and param 66 has 3 as default)?!

Ok, so I decided to set parameter 66 to 20 seconds via OZWCP and then tested the device and IT WORKS NOW!! Dimming from 0% up to 100% takes now 20 seconds.
If I change the parameter to 5 seconds then dimming up and down from max to min takes 5 seconds so it does indeed work as intended when using OZWCP AND the same USB controller as I am using in Indigo.

So I decided to test to set parameter 65 to 255 which means that time to shut off lamp when just clicking on push button on I1 is 2.55 seconds and it works too.
I kept parameter 66 at 5.

I now shut down OZWCP and re-enabled the USB Z-Wave controller in Indigo. I run the get configuration command and I get this in the log:

Code: Select all

Z-Wave Debug                    SENT readConfigValue: 01 0A 00 13 06 03 70 05 42 25 F1 00
Z-Wave Debug                    RCVD requestConfigVal: 01 0C 00 04 00 06 06 70 06 42 02 00 05 C4
Z-Wave Debug                    . .  requestConfigVal: node 006, parm index 66, value 5 (size 2)
Z-Wave                          retrieved parameter 66 "Button down duration" is 5 seconds
Z-Wave Debug                    SENT setConfigVal: 01 0C 00 13 06 05 70 04 42 01 FF 25 F2 FC
Z-Wave                          device "006 - Dimmer" parameter 66 "Button down duration" changed to 255 seconds (was 5 seconds)
Z-Wave Debug                    . .  pushNewValToNode: node 006, combined config vals: 1:0 2:0 3:0 100:0 101:0 65:255 66:255 110:32536 20:0 21:0 120:5 4:0 60:1 61:99 30:0

So Indigo reverts back the value to the last known value I had when I set parameter 66 to 255 before moving over to OZWCP....

Ok one final test:

Still in Indigo I now set parameter 66 to 10 seconds and re-read device config and see that Indigo at least thinks that parameter 66 is now 10 seconds:

Code: Select all

Z-Wave Debug                    SENT setConfigVal: 01 0C 00 13 06 05 70 04 42 01 0A 25 FA 01
Z-Wave                          device "006 - Dimmer" parameter 66 "Button down duration" changed to 10 seconds
Z-Wave Debug                    . .  pushNewValToNode: node 006, combined config vals: 1:0 2:0 3:0 100:0 101:0 65:255 66:10 110:32536 20:0 21:0 120:5 4:0 60:1 61:99 30:0


Re-reading back the value and it is indeed now 10 seconds according to Indigo:

Code: Select all

Z-Wave Debug                    SENT readConfigValue: 01 0A 00 13 06 03 70 05 42 25 FB 0A
 Z-Wave Debug                    RCVD requestConfigVal: 01 0C 00 04 00 06 06 70 06 42 02 00 05 C4
 Z-Wave Debug                    . .  requestConfigVal: node 006, parm index 66, value 5 (size 2)
 Z-Wave                          retrieved parameter 66 "Button down duration" is 5 seconds
 Z-Wave Debug                    SENT setConfigVal: 01 0C 00 13 06 05 70 04 42 01 0A 25 FC 07
 Z-Wave                          device "006 - Dimmer" parameter 66 "Button down duration" changed to 10 seconds (was 5 seconds)
 Z-Wave Debug                    . .  pushNewValToNode: node 006, combined config vals: 1:0 2:0 3:0 100:0 101:0 65:255 66:10 110:32536 20:0 21:0 120:5 4:0 60:1 61:99 30:0

Testing to dim from 0 to 100 but it still takes only the default 3 seconds instead of the wanted 10 seconds...

Ok so I disable Z-Wave controller in Indigo and start up OZWCP again and check what I see as the value for parameter 66:

Code: Select all

2017-12-15 15:45:39.170 Detail, Node006,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x06, 0x06, 0x70, 0x06, 0x42, 0x02, 0x00, 0x05, 0xc4
2017-12-15 15:45:39.170 Info, Node006, Received Configuration report: Parameter=66, Value=5
2017-12-15 15:45:39.170 Detail, Node006,   Expected reply and command class was received
2017-12-15 15:45:39.170 Detail, Node006,   Message transaction complete
2017-12-15 15:45:39.170 Info, Notification: Value Changed Home 0x0161eb65 Node 6 Genre config Class CONFIGURATION Instance 1 Index 66 Type short
2017-12-15 15:45:39.171 Info, Node006, Sending (Query) message (Callback ID=0x30, Expected Reply=0x04) - ConfigurationCmd_Get (Node=6): 0x01, 0x0a, 0x00, 0x13, 0x06, 0x03, 0x70, 0x05, 0x43, 0x25, 0x30, 0xc0
2017-12-15 15:45:39.176 Detail, Node006,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-12-15 15:45:39.176 Detail, Node006,   ZW_SEND_DATA delivered to Z-Wave stack


Back to the value 5 that I set via OZWCP before I went back to Indigo. Indigo does indeed something wrong when it is sending the values for parameter 65 and 66 on ZMNHDD1 devices since they are not stored in the device.
Parameter 1 (I1 input type) and for example parameter 21 (double-click = max light) works fine though.

As soon as I set the wanted value for parameter 66 via OZWCP then dimming speed works as intended BOTH in Indigo and OZWCP.

This is very strange but Indigo is indeed doing something wrong when setting the parameter 65 and 66 on ZMNHDD1 devices?

[matt (support)]

It looks like the problem is Indigo's device definition for this module (and the ZMNHDA) specifies that those two configuration parameters are 1 byte in size, but they are actually 2. I'll get the device definition corrected for 7.1.2.

As usual, good detective work.

Oooh that is wonderful!! I've been nagging quite much at Qubino about this issue but it was wonderful that we finally nailed it.

How come that Indigo reports that parameter as changed to my desired value even though it has not been stored within the device?

For example if I do the command "Interfaces->Modify configuration Parameter" and then actually read the value of parameter 66 from the device? Shouldn't this command return the actual value stored within the device which in this case would always have been the value 3 since the change of the parameter to my deisred test values 10 and 20 never were saved within the device?

I also tried to send the modify parameter command as a raw Z-Wave command but never succeeded with it. I guess I am using the wrong command sequence so can you show me an example please?

[matt (support)]

I don't know why that is occurring. Most devices, I think, are forgiving if you use the wrong value size (especially in the direction of using a smaller size). That is, if I set a value to 10 using length 1 but the length value supported is really 2, then it still sets it to 10 correctly. But this Qubino appears to have the odd behavior of reporting the value has been stored when in fact it hasn't. It is as if it is storing it somewhere else in its memory than the correct location (and thus when Indigo reads it out, again with the shorter value length of 1 byte instead of 2, it shows the value Indigo set). I don't think I've ever seen a module do that before but based on your description that appears to be what is happening.

[matt (support)]

Indigo 7.2.0 is now available for download and should fix this configuration command problem.

Wohoooo! This is wonderful!
I can confirm that my Qubino ZMNHDD dimmers are now dimming up and down at the speed set by parameter 66.

Same here. Perfect. I'll retract some of my earlier dismissal of their devices, I presumed it was their firmware, not indigo !


Sent from my iPhone using Tapatalk

A thread from a while ago but I thought I would add in a slight conundrum I have got with a Qubino dimmer ZMNHDD1.

About 18 months ago we experienced a mains power failure and due to voltage fluctuations, this wrecked some equipment:. This was my Smappee Energy Monitor which is near the consumer unit in the garage. I got it replaced and it is now on a small UPS.

However the other problem was that a couple of my Qubino Dimmers (ZMNHDA) stated issuing messages to the Indigo Event Log of the form:

Z-Wave Error received "021 - Dimmer" energy total value out-of-bounds -214748364.8 kWh (ignored)

So I purchased a couple of replacement dimmers: Qubino ZMNHDD1

Eighteen months later, I have finally got round to replacing them. However I have a problem in that the Momentary Switch to toggle the light off doesn't work. When I turn on or off the dimmer from Indigo, that works OK but the brightening and dimming takes a number of seconds. Suspecting that it could be my installation (which is essentially a one-for-one replacement), I double checked the wiring but still no joy with the switch working.

One other interesting thing with using this new dimmer is that when it is on at 100% and I turn it off, it takes a number of seconds to dim down and turn off but whilst it is doing so reports say 65% dimming so even though it is physically off, Indigo shows it as On. If I do a Send Status Request, Indigo then sees that it is off with 0% brightness.

Next step was to reinstall the original ZMNHDA and lo and behold: the switch works again - so not my wiring. Also the dimming when turning On and Off is quick.

I am wondering whether using the original device definition and re-syncing the new device on top of the existing use is causing a problem. Maybe the ZMNHDD1 is defective.

Given this thread, I am wondering whether I am missing a trick somewhere?

I am close to chucking the Qubinos in the bin and Clicking the Buy button on my Amazon basket which contains a couple of Fibaro Dimmer 2s.

Additional Info; Sync of ZMNHDA:

Z-Wave Syncing - retrieved module neighbors list: 2, 3, 4, 5, 6, 7, 16, 20, 22, 23, 26, 27, 28, 30, 31, 32, 33, 34, 35, 61, 62, 71, 82, 85, 93, 94, 108, 127, 128, 146
Z-Wave Syncing - assigning return route to "021 - Dimmable Power Switch"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Qubino - 0159, Flush Micro Dimmer (ZMNHDA) - 00010001
Z-Wave Syncing - retrieved protocol version 3.67, app version 1.12
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 60v3 25v1 26v3 27v1 32v3 70v1 31v3 72v1 73v1 86v1 85v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Syncing - retrieved multi-endpoint types: 1:(20 : 00), 2:(20 : 00)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[30 20], 2:[30 20]
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - retrieved group 4 associations: [1]
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - group 4 association to interface already exists (skipping)
Z-Wave Syncing - retrieved parameter 30 "Power up state" is 1 "Off"
Z-Wave Syncing - retrieved parameter 1 "Input 1 mode" is 0 "Momentary"
Z-Wave Syncing - retrieved parameter 2 "Input 2 type" is 0 "Normally Open"
Z-Wave Syncing - retrieved parameter 3 "Input 3 type" is 0 "Normally Open"
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 255 seconds
Z-Wave Syncing - device "021 - Dimmable Power Switch" parameter 66 "Button down duration" changed to 3 seconds (was 255 seconds)
Z-Wave Syncing - created device "021 - Dimmer"
Z-Wave Syncing - created device "021 - Input 2"
Z-Wave Syncing - created device "021 - Input 3"
Z-Wave Syncing - created device "021 - Temperature"
Z-Wave Syncing - complete

Sync of ZMNHDD1 (including Z-Wave Watcher debug):

Z-Wave Syncing - started for "Landing Ceiling Lights"
Z-Wave Syncing - retrieved module neighbors list: 2, 3, 5, 9, 16, 20, 22, 23, 26, 27, 28, 29, 30, 31, 33, 34, 35, 62, 71, 82, 85, 86, 93, 100, 108
Z-Wave Syncing - assigning return route to "149 - Landing Ceiling Lights"
Z-Wave received "Power - Washing Machine" power load to 63.8 W
Z-Wave Syncing - assigned return route
Z-Wave Watcher Debug Raw command sent (Node 149): 01 06 00 60 95 24 16 3E (True)
Z-Wave Watcher Debug Raw command sent (Node 149): 01 09 00 13 95 02 72 04 25 17 36 (True)
Z-Wave Syncing - retrieved manufacture and model names: Qubino - 0159, Flush Micro Dimmer (ZMNHDD) - 00010051
Z-Wave Watcher Debug Raw command received (Node 149): 01 0E 00 04 00 95 08 72 05 01 59 00 01 00 51 17
Z-Wave Watcher Debug Raw command sent (Node 149): 01 09 00 13 95 02 86 11 25 18 D8 (True)
Z-Wave Syncing - retrieved protocol version 4.05, app version 3.07
Z-Wave Watcher Debug Raw command received (Node 149): 01 11 00 04 00 95 0B 86 12 03 04 05 03 07 04 01 03 06 E6
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 86 13 60 25 19 B9 (True)
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 86 13 26 25 1A FC (True)
Z-Wave Watcher Debug Raw command received (Node 149): 01 0A 00 04 00 95 04 86 14 60 04 96
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 86 13 31 25 1B EA (True)
Z-Wave Watcher Debug Raw command received (Node 149): 01 0A 00 04 00 95 04 86 14 26 03 D7
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 86 13 32 25 1C EE (True)
Z-Wave Watcher Debug Raw command received (Node 149): 01 0A 00 04 00 95 04 86 14 31 07 C4
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 71v1 8Ev1 59v1 5Av1 5Ev1 60v4 25v1 26v3 27v1 72v1 70v1 31v7 32v4 73v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Watcher Debug Raw command received (Node 149): 01 0A 00 04 00 95 04 86 14 32 04 C4
Z-Wave Watcher Debug Raw command sent (Node 149): 01 09 00 13 95 02 60 07 25 1D 2D (True)
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 60 09 01 25 1E 23 (True)
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 60 08 00 02 00 0A
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 60 09 02 25 1F 21 (True)
Z-Wave Syncing - retrieved multi-endpoint types: 1:(11 : 01), 2:(21 : 01)
Z-Wave Watcher Debug Raw command received (Node 149): 01 16 00 04 00 95 10 60 0A 01 11 01 5E 85 8E 59 27 25 26 32 71 EF 26 B1
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 85 8E 59 27 25 26 32 71], 2:[5E 85 8E 59 31]
Z-Wave Watcher Debug Raw command received (Node 149): 01 10 00 04 00 95 0A 60 0A 02 21 01 5E 85 8E 59 31 01
Z-Wave Watcher Debug Raw command sent (Node 149): 01 09 00 13 95 02 85 05 25 20 F7 (True)
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 01 25 21 F2 (True)
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 09 00 04 00 95 03 85 06 0B EC
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 02 25 22 F2 (True)
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 01 01 00 E6
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 03 25 23 F2 (True)
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 02 10 00 F4
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 04 25 24 F2 (True)
Z-Wave Syncing - retrieved group 4 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 03 10 00 F5
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 05 25 25 F2 (True)
Z-Wave Syncing - retrieved group 5 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 04 10 00 F2
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 06 25 26 F2 (True)
Z-Wave Syncing - retrieved group 6 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 05 10 00 F3
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 07 25 27 F2 (True)
Z-Wave Syncing - retrieved group 7 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 06 10 00 F0
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 08 25 28 F2 (True)
Z-Wave Syncing - retrieved group 8 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 07 10 00 F1
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 09 25 29 F2 (True)
Z-Wave Syncing - retrieved group 9 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 08 10 00 FE
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 0A 25 2A F2 (True)
Z-Wave Syncing - retrieved group 10 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 09 10 00 FF
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 85 02 0B 25 2B F2 (True)
Z-Wave Syncing - retrieved group 11 associations: []
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 0A 10 00 FC
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0D 00 13 95 06 8E 01 01 00 01 01 25 2C F5 (True)
Z-Wave Syncing - added group 1 multi association to interface
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0D 00 13 95 06 8E 01 04 00 01 01 25 2D F1 (True)
Z-Wave Syncing - added group 4 multi association to interface
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0D 00 13 95 06 8E 01 0B 00 01 01 25 2E FD (True)
Z-Wave Syncing - added group 11 multi association to interface
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 85 03 0B 10 00 FD
Z-Wave Watcher Debug Raw command sent (Node 149): 01 09 00 13 95 02 32 03 25 2F 49 (True)
Z-Wave Watcher Debug Raw command received (Node 149): 01 0A 00 04 00 95 04 32 04 A1 05 F2
Z-Wave Watcher Debug Raw command sent (Node 149 Endpoint 1): 01 0D 00 13 95 06 60 0D 01 01 32 03 25 30 3B (True)
Z-Wave Watcher Debug Raw command received (Node 149 Endpoint 1): 01 0A 00 04 00 95 04 32 04 A1 05 FF
Z-Wave Watcher Debug Raw command received (Node 149): 01 0E 00 04 00 95 08 60 0D 01 01 32 04 A1 05 97
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 1E 25 31 0F (True)
Z-Wave Syncing - retrieved parameter 30 "Power up state" is 1 "Off"
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 64 25 32 76 (True)
Z-Wave Syncing - retrieved parameter 100 "Input 2 notifications" is 0 "Disabled"
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 1E 01 01 08
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 65 25 33 76 (True)
Z-Wave Syncing - retrieved parameter 101 "Input 3 notifications" is 0 "Disabled"
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 64 01 00 73
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 01 25 34 15 (True)
Z-Wave Syncing - retrieved parameter 1 "Input 1 mode" is 0 "Momentary"
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 65 01 00 72
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 02 25 35 17 (True)
Z-Wave Syncing - retrieved parameter 2 "Input 2 mode" is 0 "Momentary"
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 01 01 00 16
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 03 25 36 15 (True)
Z-Wave Syncing - retrieved parameter 3 "Input 2 type" is 0 "Normally Open"
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 02 01 00 15
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 04 25 37 13 (True)
Z-Wave Syncing - retrieved parameter 4 "Input 3 type" is 0 "Normally Open"
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 03 01 00 14
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 14 25 38 0C (True)
Z-Wave Syncing - retrieved parameter 20 "Enable 3-way switch mode" is false
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 04 01 00 13
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 15 25 39 0C (True)
Z-Wave Syncing - retrieved parameter 21 "Enable double-click to maximum brightness" is true
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 14 01 00 03
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 3C 25 3A 26 (True)
Z-Wave Syncing - retrieved parameter 60 "Minimum value" is 1
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 15 01 01 03
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 3D 25 3B 26 (True)
Z-Wave Syncing - retrieved parameter 61 "Maximum value" is 99
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 3C 01 01 2A
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 41 25 3C 5D (True)
Z-Wave Syncing - retrieved parameter 65 "Button tap duration" is 100 * 10 milliseconds
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 3D 01 63 49
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 42 25 3D 5F (True)
Z-Wave Syncing - retrieved parameter 66 "Button down duration" is 3 seconds
Z-Wave Watcher Debug Raw command received (Node 149): 01 0C 00 04 00 95 06 70 06 41 02 00 64 35
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 6E 25 3E 70 (True)
Z-Wave Syncing - retrieved parameter 110 "Temperature offset" is 0 * 0.1 degrees
Z-Wave Watcher Debug Raw command received (Node 149): 01 0C 00 04 00 95 06 70 06 42 02 00 03 51
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 78 25 3F 67 (True)
Z-Wave Syncing - retrieved parameter 120 "Temperature sensitivity" is 5 * 0.1 degrees
Z-Wave Watcher Debug Raw command received (Node 149): 01 0C 00 04 00 95 06 70 06 6E 02 00 00 7E
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 78 01 05 6A
Z-Wave Syncing - complete

[matt (support)]

I am wondering whether using the original device definition and re-syncing the new device on top of the existing use is causing a problem. Maybe the ZMNHDD1 is defective.

I don't believe that should be a problem, but wouldn't hurt to create a new Device just to check and see (exclude, re-include, and sync to a new device). When the sync is done Indigo will disable the communication with the other (older) device that also uses that node ID, but after you do the test (and presuming new device also shows the problem) you can re-enable the older device by just re-syncing it. That will also disable the comm on the new device which you can then delete it.

Your parameters look good to me:

Z-Wave Syncing - retrieved parameter 65 "Button tap duration" is 100 * 10 milliseconds
Z-Wave Watcher Debug Raw command received (Node 149): 01 0B 00 04 00 95 05 70 06 3D 01 63 49
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 42 25 3D 5F (True)
Z-Wave Syncing - retrieved parameter 66 "Button down duration" is 3 seconds
Z-Wave Watcher Debug Raw command received (Node 149): 01 0C 00 04 00 95 06 70 06 41 02 00 64 35
Z-Wave Watcher Debug Raw command sent (Node 149): 01 0A 00 13 95 03 70 05 6E 25 3E 70 (True)

But did you try decreasing both of them even more? Lowest value for both should be 1.

Also try setting parameter 68 (no UI for it so use the generic modify config parameter menu) to 0 (should be default) and 1 just to see if that makes difference. All of this is based on the PDF manual I have for the ZMNHDD which may be old, so you might want to check the latest one you can find.

Hi Matt,
I tried with a second new Qubino ZMNHDD1 dimmer I had and that didn't work either - no switch control.
This was before I had even included it into the Z-stick and it should work! Even after I included it and sync'd it and made sure the options were correct it wouldn't operate form the switch. Maybe the units were defective?

Anyway, I have given up with these new Qubino devices and binned them.

I have now purchased a number of Fibaro FGD-212 Dimmer 2 and FGB-002 Bypass 2 to replace the existing Qubinos.
One bonus is that the Fibaros are Z-Wave 500 and so should help provide better and stronger mesh coverage - I hope.

The first replacement works as expected. Although how you wire up the Fibaro is slightly different to the Qubino, luckily the change was easy to accommodate. As far as the dimmer for my landing down-lights is concerned which is situated in the loft, the only thing I have lost is the Qubino remote temperature sensor. I have now put one of my new Zigbee2MQTT temperature sensors in the loft, so not a problem.

@autolog:
I can happily pay the shipping cost for your Qubino ZMNHDD1:s if you are willing to ship them to Sweden.
Can you check what firmware the label indicates on the back of the device?

I have multiple of these installed here and I am experiencing no problems with using a momentary switch to toggle the light on/off as well as to manipulate the dimming up/down speed with parameter 66.

Jon I definitely prefer the fibaros too in almost all cases other than the lack of 3 inputs.
The fact the multi end point association doesn’t work on my Units is another negative mark.
I’ve also almost come a cropper with the different wiring too

... if you are willing to ship them to Sweden. ...

No problem, I rescued them from the bin together with their packaging!

Qubino ZMNHDD1 x 2

Qubino_ZMNHDD1_x_2.jpg (78.51 KiB) Viewed 5723 times

The one pictured on the left has a slightly damaged button.

Given the discussion above, they are not guaranteed to work for you but you may be lucky.

If you still want them, PM me your contact details and I will mail them to you.

Cool! Very much appreciated and I fully understand that I might have no luck at all with them.

Looks like yours have an old firmware: H1S3P5
My ZMNHDD-devices have H1S4P5

I'll PM you with my details now.