Qubino module cant sync after inclusion

Hello everybody,

Trying to use the Qubino ZMNHJD1 module to control my heaters from Indigo. I managed to include it but there’s always a timeout message at sync step.
I’ve already read many messages on this forum which could potentially correspond to my issue, especially this topic:
viewtopic.php?f=58&t=17257
Where Matts suggests a special 3 steps procedure (exclusion-wait 30sec-new inclusion) which is supposed to work for some users, but wont work in any way for me.
I’ve also read that Matt released a Zwave beta plugin for some Qubino devices experinving this issue, but the discussion is from around 2016/2017 so i was just wondering if i should install this plugin, or does the Indigo 7.4 version already includes it?

FYI i just bought another Qubino module, thinking the previous one had an issue, but the 2nd module experiences exatly same issues as the first, which means i’m really stuck at the sync step for good.

Any help would be greatly appreciated!

Thanks

[matt (support)]

Did you try all the detailed steps mentioned on that thread here (from a user that got it to work)? Be sure you don't use encryption during the inclusion (that will just make the process more complicated / error prone).

The beta plugin mentioned is now old (and that functionality is in v7.4), so no need to try installing that.

If the problem persists (from that thread it sounds like some users had success after several attempts at the long list of steps), then copy/paste the Event Log results of the sync into a reply for me. First turn on Indigo's Z-Wave debug logging checkbox via the Interfaces->Z-Wave->Configure... menu item. I'll can then at least verify if you are seeing the same problem or not.

Hi Matt,

Thank you for your quick response.
Indeed, the thread you mention is the same which I followed suggestions from, besides the fact that I can't test OFF/ON since I can't pass the sync step.But then I exclude the module from the controller, wait 60 sec, and reinclude it as mentioned in the thread, and did it more than a dozen times already.
Maybe something else is happening in my case, so here a copy/paste of the Log window as you requested, hope this clarifies a bit.
Thank you


11 déc. 2019 à 11:12:22
Z-Wave Debug SENT enterExclusionMode: 01 04 00 4B 81 31
Z-Wave Debug RCVD enterExclusionMode: 06 (ACK)
Z-Wave started controller exclusion mode
Z-Wave Debug RCVD exclusionMode ready: 01 07 00 4B 02 01 00 00 B0
Z-Wave Debug RCVD exclusionMode node found: 01 07 00 4B 02 02 00 00 B3
Z-Wave Debug RCVD exclusionMode removing slave node: 01 1B 00 4B 02 03 1A 14 04 11 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 B4
Z-Wave Debug RCVD exclusionMode finished: 01 1B 00 4B 02 06 1A 14 04 11 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 B1
Z-Wave Debug . . exclusionMode node removed: 026
Z-Wave controller excluded module: 026 - Dimmable Power Switch
Z-Wave Debug SENT exitExclusionMode: 01 04 00 4B 05 B5
Z-Wave Debug RCVD exitExclusionMode: 06 (ACK)
Z-Wave stopped controller exclusion mode
Z-Wave Debug RCVD requestReply1: 01 08 00 04 00 1A 02 5A 01 B0 (hex)
Z-Wave Debug RCVD requestReply1: 01 08 00 04 00 1A 02 5A 01 B0 (hex)

11 déc. 2019 à 11:13:25
Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Debug SENT enterInclusionMode: 01 04 00 4A C1 70
Z-Wave Debug RCVD enterInclusionMode: 06 (ACK)
Z-Wave started controller inclusion mode
Z-Wave Debug RCVD inclusionMode ready: 01 07 00 4A 02 01 00 00 B1
Z-Wave Debug RCVD inclusionMode node found: 01 07 00 4A 02 02 00 00 B2
Z-Wave Debug RCVD inclusionMode adding slave node: 01 1B 00 4A 02 03 1B 14 04 11 01 5E 86 72 5A 73 20 27 25 26 31 60 85 8E 59 70 EF 20 8F
Z-Wave Debug RCVD inclusionMode node respondCmds: 5E 86 72 5A 73 20 27 25 26 31 60 85 8E 59 70
Z-Wave Debug RCVD inclusionMode node added: 01 07 00 4A 02 05 1B 00 AE
Z-Wave Debug SENT exitInclusionMode: 01 04 00 4A 05 B4
Z-Wave Debug RCVD exitInclusionMode: 06 (ACK)
Z-Wave Debug RCVD inclusionMode finished: 01 07 00 4A 02 06 1B 00 AD
Z-Wave Debug SENT getNodeProtocolInfo: 01 04 00 41 1B A1
Z-Wave Debug RCVD getNodeProtocolInfo: 01 09 01 41 D3 9C 01 04 11 01 EC
Z-Wave Debug . . getNodeProtocolInfo: node 027, class name: Dimmable Power Switch
Z-Wave Debug . . getNodeProtocolInfo: class hierarchy: Routing Slave : Mulitlevel Switch : Dimmable Power Switch (04 : 11 : 01)
Z-Wave Debug . . getNodeProtocolInfo: base class command: 26
Z-Wave Debug . . getNodeProtocolInfo: supported class commands: 20 60 25 86 27 8E 70 31 72 73 59 5A 26 5E 85
Z-Wave Debug . . getNodeProtocolInfo: encrypt class commands:
Z-Wave Debug . . getNodeProtocolInfo: features: routing, beaming
Z-Wave controller included module: 027 - Dimmable Power Switch
Z-Wave stopped controller inclusion mode
Z-Wave Syncing - started for "027 - Dimmable Power Switch"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 1B 01 01 62
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 1C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 42
Z-Wave Debug . . getNodeNeighbors: nodeId 027, neighbors: 3, 4, 5
Z-Wave Syncing - retrieved module neighbors list: 3, 4, 5
Z-Wave Syncing - assigning return route to "027 - Dimmable Power Switch"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 1B 01 A6
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 027, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 1B 24 2E 88
Z-Wave Debug RCVD nodeInfoFrame: 01 1A 00 49 84 1B 14 04 11 01 5E 86 72 5A 73 20 27 25 26 31 60 85 8E 59 70 EF 20 08
Z-Wave Debug . . nodeInfoFrame: node 027, combined class list: 20v1 60v1 25v1 86v1 27v1 8Ev1 70v1 31v1 72v1 73v1 59v1 5Av1 26v1 5Ev1 85v1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 1B 02 72 04 25 2F 80
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 1B 08 72 05 01 59 00 04 00 51 9C
Z-Wave Debug . . requestManufactureInfo: node 027, manufacturerId 0159, productId 00040051
Z-Wave Debug . . requestManufactureInfo: Qubino, Dimmable Power Switch
Z-Wave Syncing - retrieved manufacture and model names: Qubino - 0159, Dimmable Power Switch - 00040051
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 1B 02 86 11 25 30 7E
Z-Wave Debug RCVD requestVersInfoGen: 01 11 00 04 00 1B 0B 86 12 03 05 03 02 00 01 01 01 00 68
Z-Wave Debug . . requestVersInfoGen: node 027, protoVers 5.03, appVers 2.00
Z-Wave Syncing - retrieved protocol version 5.03, app version 2.00
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 1B 03 86 13 60 25 31 1F
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 1B 04 86 14 60 04 18
Z-Wave Debug . . requestVersInfoCmdClass: node 027, class command 60 using version 4
Z-Wave Debug . . requestVersInfoCmdClass: node 027, combined class list: 20v1 60v4 25v1 86v1 27v1 8Ev1 70v1 31v1 72v1 73v1 59v1 5Av1 26v1 5Ev1 85v1
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 1B 03 86 13 31 25 32 4D
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 1B 04 86 14 31 03 4E
Z-Wave Debug . . requestVersInfoCmdClass: node 027, class command 31 using version 3
Z-Wave Debug . . requestVersInfoCmdClass: node 027, combined class list: 20v1 60v4 25v1 86v1 27v1 8Ev1 70v1 31v3 72v1 73v1 59v1 5Av1 26v1 5Ev1 85v1
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 1B 03 86 13 26 25 33 5B
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 1B 04 86 14 26 03 59
Z-Wave Debug . . requestVersInfoCmdClass: node 027, class command 26 using version 3
Z-Wave Debug . . requestVersInfoCmdClass: node 027, combined class list: 20v1 60v4 25v1 86v1 27v1 8Ev1 70v1 31v3 72v1 73v1 59v1 5Av1 26v3 5Ev1 85v1
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 60v4 25v1 86v1 27v1 8Ev1 70v1 31v3 72v1 73v1 59v1 5Av1 26v3 5Ev1 85v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Debug SENT requestMultiEndPointInfo: 01 09 00 13 1B 02 60 07 25 34 8A
Z-Wave Debug RCVD requestMultiEndPointInfo: 01 0B 00 04 00 1B 05 60 08 00 03 00 85
Z-Wave Debug . . requestMultiEndPointInfo: node 027, numEndPoints 3, sameClass False, notStatic False
Z-Wave Debug SENT requestMultiEndPointDetails: 01 0A 00 13 1B 03 60 09 01 25 35 86
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 14 00 04 00 1B 0E 60 0A 01 20 00 5E 86 20 30 85 8E 59 EF 20 E4
Z-Wave Debug . . requestMultiEndPointDetails: node 027, endPoint 1, notStatic False, class hierarchy 20 : 00
Z-Wave Debug . . requestMultiEndPointDetails: node 027, combined multi-endpoint types: 1:(20 : 00)
Z-Wave Debug . . requestMultiEndPointDetails: node 027, combined multi-endpoint classes: 1:[5E 86 20 30 85 8E 59]
Z-Wave Debug SENT requestMultiEndPointDetails: 01 0A 00 13 1B 03 60 09 02 25 36 86
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 14 00 04 00 1B 0E 60 0A 02 20 00 5E 86 20 30 85 8E 59 EF 20 E7
Z-Wave Debug . . requestMultiEndPointDetails: node 027, endPoint 2, notStatic False, class hierarchy 20 : 00
Z-Wave Debug . . requestMultiEndPointDetails: node 027, combined multi-endpoint types: 1:(20 : 00), 2:(20 : 00)
Z-Wave Debug . . requestMultiEndPointDetails: node 027, combined multi-endpoint classes: 1:[5E 86 20 30 85 8E 59], 2:[5E 86 20 30 85 8E 59]
Z-Wave Debug SENT requestMultiEndPointDetails: 01 0A 00 13 1B 03 60 09 03 25 37 86
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 14 00 04 00 1B 0E 60 0A 03 20 00 5E 86 20 30 85 8E 59 EF 20 E6
Z-Wave Debug . . requestMultiEndPointDetails: node 027, endPoint 3, notStatic False, class hierarchy 20 : 00
Z-Wave Debug . . requestMultiEndPointDetails: node 027, combined multi-endpoint types: 1:(20 : 00), 2:(20 : 00), 3:(20 : 00)
Z-Wave Debug . . requestMultiEndPointDetails: node 027, combined multi-endpoint classes: 1:[5E 86 20 30 85 8E 59], 2:[5E 86 20 30 85 8E 59], 3:[5E 86 20 30 85 8E 59]
Z-Wave Syncing - retrieved multi-endpoint types: 1:(20 : 00), 2:(20 : 00), 3:(20 : 00)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 86 20 30 85 8E 59], 2:[5E 86 20 30 85 8E 59], 3:[5E 86 20 30 85 8E 59]
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 1B 02 85 05 25 38 61
Z-Wave Error rcvd incomplete interface packet: 01 08 00 04 00 1B 02 85 06 69 (missing 1 bytes)
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 1B 02 85 05 25 39 60
Z-Wave Error rcvd incomplete interface packet: 01 08 00 04 00 1B 02 85 06 69 (missing 1 bytes)
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 1B 02 85 05 25 3A 63
Z-Wave Error rcvd incomplete interface packet: 01 08 00 04 00 1B 02 85 06 69 (missing 1 bytes)
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug maximum retry count exceeded waiting reply from module
Z-Wave Error Syncing - failed
Z-Wave Error Timeout waiting for "027 - Dimmable Power Switch". Module might be asleep, or is unreachable.
Z-Wave Debug terminatingSyncUI

Qubino horrible. I am in the process of replacing 4 of them with Aeotec due to how unstable they are.

JP

Hi JP,

Unfortunately Qubino is the only brand I know which offers Zwave wire driver modules for heaters. So I'm stuck with it so far...But besides this particular one, I tend to use Figaro devices instead, which works perfectly with Indigo most of the times.

The problem is they all have bespoke functionality so one bend might be more reliable but not always best for an application. Fibaro I use for a standard module. They do scenes that others dont and do din rail mounts.
Qubino do 3 inputs into their dimmers to allow up down momentary switches and another.
As said qubino do the heater modules.
I'm sure there is more.

Apparently the only error message in the log i copied above is about "1 byte missing":

"Z-Wave Error rcvd incomplete interface packet: 01 08 00 04 00 1B 02 85 06 69 (missing 1 bytes)"
Strange, uh?
I'm really curious about how Matt would interpret from this.

[matt (support)]

Definitely looks like it is misbehaving and not returning the full report reply (COMMAND_CLASS_ASSOCIATION / ASSOCIATION_GROUPINGS_REPORT according to spec should always return a byte with the number of association groups supported, but it isn't there). I could modify Indigo so that it doesn't fail in this case and tries to continue on with the sync, which might get it working. If you want to try that then email us (support AT indigodomo DOT com) and I'll get you a beta version that is more tolerant of that command not being valid.

Thank you for this feedback Matt, you should have received my email by now.
Hoping this may help other Qubino users too.
Greg

[matt (support)]

Indigo 7.4.1 is now available and improves support of Qubino ZMNHJD1 so that the sync can complete.