I have a Z-Wave JS UI setup with the Homeassistant Connect ZWA-2 as my controller.
I have a bunch of Zooz devices setup around the house and want to use direct association with them but every node (On/Off switches, remotes, etc…) only has the lifeline group.
The devices are all S2_authenticated and the groups show up in the zwave-js.io database link for them. I have also tried re-interviewing the nodes but no new groups ever show up.
Any help would be appreciated.
What do you mean by “don’t show up”? You have to create the associations yourself: Control Panel → Select the source node → Select Groups tab → Select “ADD” → Select the source node/endpoint and Group, then target.
I have to slowly add images as it will only let me embed one at a time. This is the associations available for the On/Off Zooz switch:
Thanks, that’s much more clear as to the problem.
I presume you’re on the latest version of Z-Wave JS UI available?
What version of firmware is your switch at? 700 or 800 series?
What’s odd is that I have the same switch (ZEN71 on v3.30.0), but I also have an extra group 3 not shown in the device DB. I think the node interview can append/overwrite the Groups defined in the DB.
You may need to capture driver debug logs during the interview to see if there is a problem interviewing the Association CCs.
Latest version on ZWave JS UI. Here is the switch information and there is no firmware update available:
I captured the logs awhile ago while interviewing and if I remember correctly the associations dictionary was empty but I will re-interview and capture that information for you.
Here are (from what I can tell) the relevant debug logs from the re-interview:
11:37:06.847 CNTRLR [Node 261] Interviewing Association...
11:37:06.847 CNTRLR » [Node 261] querying number of association groups...
11:37:06.848 DRIVER » [Node 261] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 115
└─[Security2CCMessageEncapsulation]
│ sequence number: 157
└─[AssociationCCSupportedGroupingsGet]
11:37:06.848 SERIAL » 0x011c00a9000101050e9f039d004961082bfa9f4e60a644250000000073b4 (30 bytes)
11:37:06.854 SERIAL « [ACK] (0x06)
11:37:06.856 SERIAL « 0x010401a90152 (6 bytes)
11:37:06.856 SERIAL » [ACK] (0x06)
11:37:06.856 DRIVER « [RES] [SendDataBridge]
was sent: true
11:37:06.872 SERIAL « 0x011d00a97300000100aa7f7f7f7f030306000000000401000000a600b1a324 (31 bytes)
11:37:06.872 SERIAL » [ACK] (0x06)
11:37:06.872 DRIVER « [REQ] [SendDataBridge]
callback id: 115
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
ACK RSSI: -86 dBm
ACK channel no.: 3
TX channel no.: 3
TX power: 0 dBm
measured noise floor: -90 dBm
ACK TX power by destination: 0 dBm
measured RSSI of ACK from destination: -79 dBm
measured noise floor by destination: -93 dBm
11:37:06.885 SERIAL « 0x011d00a800000101050f9f03cf0014e54217b33cc2d09fde8800a900fea317 (31 bytes)
11:37:06.885 SERIAL » [ACK] (0x06)
11:37:06.886 CNTRLR [Node 261] [+] [Association] groupCount: 1 [Endpoint 0] [internal]
11:37:06.886 DRIVER « [Node 261] [REQ] [BridgeApplicationCommand]
│ RSSI: -87 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 207
│ security class: S2_Authenticated
└─[AssociationCCSupportedGroupingsReport]
group count: 1
11:37:06.886 CNTRLR « [Node 261] supports 1 association groups
11:37:06.886 CNTRLR » [Node 261] querying association group #1...
11:37:06.886 DRIVER » [Node 261] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 116
└─[Security2CCMessageEncapsulation]
│ sequence number: 158
└─[AssociationCCGet]
group id: 1
11:37:06.886 SERIAL » 0x011d00a9000101050f9f039e00e7f74f464126cba3b5d60325000000007464 (31 bytes)
11:37:06.892 SERIAL « [ACK] (0x06)
11:37:06.895 SERIAL « 0x010401a90152 (6 bytes)
11:37:06.895 SERIAL » [ACK] (0x06)
11:37:06.895 DRIVER « [RES] [SendDataBridge]
was sent: true
11:37:06.911 SERIAL « 0x011d00a97400000100a87f7f7f7f0303060000000004010000ffa6ffc4a651 (31 bytes)
11:37:06.911 SERIAL » [ACK] (0x06)
11:37:06.911 DRIVER « [REQ] [SendDataBridge]
callback id: 116
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
ACK RSSI: -88 dBm
ACK channel no.: 3
TX channel no.: 3
TX power: -1 dBm
measured noise floor: -90 dBm
ACK TX power by destination: -1 dBm
measured RSSI of ACK from destination: -60 dBm
measured noise floor by destination: -90 dBm
11:37:06.923 SERIAL « 0x012000a80000010105129f03d000b1bdba07027caea5d2c875bfeae100a500fba (34 bytes)
6cb
11:37:06.923 SERIAL » [ACK] (0x06)
11:37:06.924 CNTRLR [Node 261] [+] [Association] nodeIds[1]: 1 [Endpoint 0] [internal]
11:37:06.924 CNTRLR [Node 261] [+] [Association] maxNodes[1]: 1 [Endpoint 0] [internal]
11:37:06.924 DRIVER « [Node 261] [REQ] [BridgeApplicationCommand]
│ RSSI: -91 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 208
│ security class: S2_Authenticated
└─[AssociationCCReport]
group id: 1
max # of nodes: 1
node IDs: 1
reports to follow: 0
11:37:06.924 CNTRLR « [Node 261] received information for association group #1:
maximum # of nodes: 1
currently assigned nodes: 1
11:37:06.924 CNTRLR [Node 261] AssociationCC: delaying configuration of lifeline associations unti
l after Multi Channel Association interview...
11:37:06.924 CNTRLR [Node 261] [+] [Association] interviewComplete: true [Endpoint 0] [internal]
11:37:06.924 CNTRLR [Node 261] Interviewing Multi Channel Association...
11:37:06.924 CNTRLR » [Node 261] querying number of multi channel association groups...
11:37:06.925 DRIVER » [Node 261] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 117
└─[Security2CCMessageEncapsulation]
│ sequence number: 159
└─[MultiChannelAssociationCCSupportedGroupingsGet]
11:37:06.925 SERIAL » 0x011c00a9000101050e9f039f0004eb7cb583d07bfaf52625000000007535 (30 bytes)
11:37:06.931 SERIAL « [ACK] (0x06)
11:37:06.933 SERIAL « 0x010401a90152 (6 bytes)
11:37:06.933 SERIAL » [ACK] (0x06)
11:37:06.933 DRIVER « [RES] [SendDataBridge]
was sent: true
11:37:06.951 SERIAL « 0x011d00a97500000100a87f7f7f7f0303060000000004010000fea6fec4a85e (31 bytes)
11:37:06.951 SERIAL » [ACK] (0x06)
11:37:06.951 DRIVER « [REQ] [SendDataBridge]
callback id: 117
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
ACK RSSI: -88 dBm
ACK channel no.: 3
TX channel no.: 3
TX power: -2 dBm
measured noise floor: -90 dBm
ACK TX power by destination: -2 dBm
measured RSSI of ACK from destination: -60 dBm
measured noise floor by destination: -88 dBm
11:37:06.964 SERIAL « 0x011d00a800000101050f9f03d10044c07ca9fd9d72c301122b00a500faa842 (31 bytes)
11:37:06.964 SERIAL » [ACK] (0x06)
11:37:06.965 CNTRLR [Node 261] [+] [Multi Channel Association] groupCount: [Endpoint 0] [internal]
1
11:37:06.965 DRIVER « [Node 261] [REQ] [BridgeApplicationCommand]
│ RSSI: -91 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 209
│ security class: S2_Authenticated
└─[MultiChannelAssociationCCSupportedGroupingsReport]
group count: 1
11:37:06.965 CNTRLR « [Node 261] supports 1 multi channel association groups
11:37:06.965 CNTRLR » [Node 261] querying multi channel association group #1...
11:37:06.966 DRIVER » [Node 261] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 118
└─[Security2CCMessageEncapsulation]
│ sequence number: 160
└─[MultiChannelAssociationCCGet]
group id: 1
11:37:06.966 SERIAL » 0x011d00a9000101050f9f03a0008845fbfabc951a86e5b3b7250000000076b6 (31 bytes)
11:37:06.972 SERIAL « [ACK] (0x06)
11:37:06.974 SERIAL « 0x010401a90152 (6 bytes)
11:37:06.974 SERIAL » [ACK] (0x06)
11:37:06.974 DRIVER « [RES] [SendDataBridge]
was sent: true
11:37:06.990 SERIAL « 0x011d00a97600000100aa7f7f7f7f0303060000000004010000ffa5ffc4aa5e (31 bytes)
11:37:06.990 SERIAL » [ACK] (0x06)
11:37:06.990 DRIVER « [REQ] [SendDataBridge]
callback id: 118
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
ACK RSSI: -86 dBm
ACK channel no.: 3
TX channel no.: 3
TX power: -1 dBm
measured noise floor: -91 dBm
ACK TX power by destination: -1 dBm
measured RSSI of ACK from destination: -60 dBm
measured noise floor by destination: -86 dBm
11:37:07.003 SERIAL « 0x012000a80000010105129f03d2005e196068953e17e8e7238f68479700a500fba (34 bytes)
a32
11:37:07.004 SERIAL » [ACK] (0x06)
11:37:07.004 CNTRLR [Node 261] [+] [Multi Channel Association] endpoints[1 [Endpoint 0] [internal]
]:
11:37:07.004 CNTRLR [Node 261] [+] [Multi Channel Association] nodeIds[1]: [Endpoint 0] [internal]
1
11:37:07.004 CNTRLR [Node 261] [+] [Multi Channel Association] maxNodes[1] [Endpoint 0] [internal]
: 1
11:37:07.004 DRIVER « [Node 261] [REQ] [BridgeApplicationCommand]
│ RSSI: -91 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 210
│ security class: S2_Authenticated
└─[MultiChannelAssociationCCReport]
group id: 1
maximum # of nodes: 1
node ids: 1
endpoints:
11:37:07.004 CNTRLR « [Node 261] received information for multi channel association group #1:
maximum # of nodes: 1
currently assigned nodes: 1
currently assigned endpoints:
11:37:07.004 CNTRLR [Node 261] Checking/assigning lifeline groups: 1
supports classic associations: true
supports multi channel associations: true
11:37:07.004 CNTRLR [Node 261] Configuring lifeline group #1:
group supports multi channel: true
configured strategy: auto
must use node association: true
must use endpoint association: false
11:37:07.004 CNTRLR [Node 261] Lifeline group #1 is already assigned with a node association
11:37:07.004 CNTRLR [Node 261] [+] [Association] hasLifeline: true [Endpoint 0] [internal]
11:37:07.004 CNTRLR [Node 261] [+] [Multi Channel Association] interviewCo [Endpoint 0] [internal]
mplete: true
11:37:07.005 CNTRLR [Node 261] Interviewing Association Group Information...
11:37:07.005 CNTRLR » [Node 261] Association group #1: Querying name...
11:37:07.005 DRIVER » [Node 261] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 119
└─[Security2CCMessageEncapsulation]
│ sequence number: 161
└─[AssociationGroupInfoCCNameGet]
group id: 1
11:37:07.005 SERIAL » 0x011d00a9000101050f9f03a1004a7fdffb21f891694ca8d02500000000772a (31 bytes)
11:37:07.011 SERIAL « [ACK] (0x06)
11:37:07.013 SERIAL « 0x010401a90152 (6 bytes)
11:37:07.013 SERIAL » [ACK] (0x06)
11:37:07.013 DRIVER « [RES] [SendDataBridge]
was sent: true
11:37:07.029 SERIAL « 0x011d00a97700000100ac7f7f7f7f030306000000000401000002a502b3ab2f (31 bytes)
11:37:07.029 SERIAL » [ACK] (0x06)
11:37:07.029 DRIVER « [REQ] [SendDataBridge]
callback id: 119
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
ACK RSSI: -84 dBm
ACK channel no.: 3
TX channel no.: 3
TX power: 2 dBm
measured noise floor: -91 dBm
ACK TX power by destination: 2 dBm
measured RSSI of ACK from destination: -77 dBm
measured noise floor by destination: -85 dBm
11:37:07.043 SERIAL « 0x012600a80000010105189f03d3000a0a805be54a73cec3dc63d753200dc19a57c (40 bytes)
24100ac0002abb5
11:37:07.043 SERIAL » [ACK] (0x06)
11:37:07.043 CNTRLR [Node 261] [+] [Association Group Information] name[1] [Endpoint 0] [internal]
: "Lifeline"
11:37:07.043 DRIVER « [Node 261] [REQ] [BridgeApplicationCommand]
│ RSSI: -84 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 211
│ security class: S2_Authenticated
└─[AssociationGroupInfoCCNameReport]
group id: 1
name: Lifeline
11:37:07.043 CNTRLR « [Node 261] Association group #1 has name "Lifeline"
11:37:07.043 CNTRLR » [Node 261] Association group #1: Querying command list...
11:37:07.044 DRIVER » [Node 261] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 120
└─[Security2CCMessageEncapsulation]
│ sequence number: 162
└─[AssociationGroupInfoCCCommandListGet]
group id: 1
allow cache: true
11:37:07.044 SERIAL » 0x011e00a900010105109f03a20069b2666b89ec55a217238f5725000000007896 (32 bytes)
11:37:07.050 SERIAL « [ACK] (0x06)
11:37:07.052 SERIAL « 0x010401a90152 (6 bytes)
11:37:07.052 SERIAL » [ACK] (0x06)
11:37:07.053 DRIVER « [RES] [SendDataBridge]
was sent: true
11:37:07.068 SERIAL « 0x011d00a97800000100ae7f7f7f7f030306000000000401000004a604b5a925 (31 bytes)
11:37:07.068 SERIAL » [ACK] (0x06)
11:37:07.068 DRIVER « [REQ] [SendDataBridge]
callback id: 120
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
ACK RSSI: -82 dBm
ACK channel no.: 3
TX channel no.: 3
TX power: 4 dBm
measured noise floor: -90 dBm
ACK TX power by destination: 4 dBm
measured RSSI of ACK from destination: -75 dBm
measured noise floor by destination: -87 dBm
11:37:07.083 SERIAL « 0x012800a800000101051a9f03d4005ab49f30f07b7fb61ad67abe92824b3407dc1 (42 bytes)
25f112c00ad0003a9e0
11:37:07.083 SERIAL » [ACK] (0x06)
11:37:07.083 CNTRLR [Node 261] [+] [Association Group Information] issuedC [Endpoint 0] [internal]
ommands[1]: [object Map]
11:37:07.084 DRIVER « [Node 261] [REQ] [BridgeApplicationCommand]
│ RSSI: -83 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 212
│ security class: S2_Authenticated
└─[AssociationGroupInfoCCCommandListReport]
group id: 1
commands:
· Central Scene: 0x03, 0x06
· Binary Switch: 0x03
· Indicator: 0x03
· Device Reset Locally: 0x01
11:37:07.084 CNTRLR » [Node 261] Association group #1: Querying info...
11:37:07.084 DRIVER » [Node 261] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 121
└─[Security2CCMessageEncapsulation]
│ sequence number: 163
└─[AssociationGroupInfoCCInfoGet]
group id: 1
refresh cache: false
11:37:07.084 SERIAL » 0x011e00a900010105109f03a300ed8a9eec0780823ddbe7ac9125000000007912 (32 bytes)
11:37:07.090 SERIAL « [ACK] (0x06)
11:37:07.093 SERIAL « 0x010401a90152 (6 bytes)
11:37:07.093 SERIAL » [ACK] (0x06)
11:37:07.093 DRIVER « [RES] [SendDataBridge]
was sent: true
11:37:07.109 SERIAL « 0x011d00a97900000100af7f7f7f7f030306000000000401000005a805b7a828 (31 bytes)
11:37:07.109 SERIAL » [ACK] (0x06)
11:37:07.109 DRIVER « [REQ] [SendDataBridge]
callback id: 121
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Resort to Direct
ACK RSSI: -81 dBm
ACK channel no.: 3
TX channel no.: 3
TX power: 5 dBm
measured noise floor: -88 dBm
ACK TX power by destination: 5 dBm
measured RSSI of ACK from destination: -73 dBm
measured noise floor by destination: -88 dBm
11:37:07.122 SERIAL « 0x012400a80000010105169f03d50082d7c736c4c7d38744c9996c9428037247330 (38 bytes)
0ad0003a81d
11:37:07.123 SERIAL » [ACK] (0x06)
11:37:07.123 CNTRLR [Node 261] [+] [Association Group Information] hasDyna [Endpoint 0] [internal]
micInfo: false
11:37:07.123 CNTRLR [Node 261] [+] [Association Group Information] info[1] [Endpoint 0] [internal]
: {"mode":0,"profile":1,"eventCode":0}
11:37:07.124 DRIVER « [Node 261] [REQ] [BridgeApplicationCommand]
│ RSSI: -83 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 213
│ security class: S2_Authenticated
└─[AssociationGroupInfoCCInfoReport]
is list mode: false
has dynamic info: false
groups:
· Group #1
mode: 0
profile: 1
event code: 0
11:37:07.124 CNTRLR « [Node 261] Received info for association group #1:
info is dynamic: false
profile: General: Lifeline
11:37:07.124 CNTRLR [Node 261] [+] [Association Group Information] intervi [Endpoint 0] [internal]
ewComplete: true
Looks like your device is reporting the wrong information. Not sure I want to upgrade past v3.30. 
08:55:04.772 SERIAL « 0x011d00a800000100410f9f039300a84c7a0267b6743e8c54bb00c0007f7fae (31 bytes)
08:55:04.775 SERIAL » [ACK] (0x06)
08:55:04.776 CNTRLR [Node 065] [+] [Association] groupCount: 3 [Endpoint 0] [internal]
08:55:04.778 DRIVER « [Node 065] [REQ] [BridgeApplicationCommand]
│ RSSI: -64 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 147
│ security class: S2_Authenticated
└─[AssociationCCSupportedGroupingsReport]
group count: 3
08:55:04.778 CNTRLR « [Node 065] supports 3 association groups
I would contact Zooz tech support, although their first response is to usually blame Z-Wave JS. You could try creating a discussion on GitHub to see if they can help (either with Zooz or see if there’s some override). https://github.com/zwave-js/zwave-js/discussions
Gotcha. Thanks for the help, I will do that.
Just for clarification, what is wrong in that screenshot you provided? Doesn’t it say 3 groups which should show up in Z-Wave JS UI or am I misinterpreting that?
Nothing’s wrong with it, AFAIK. I just noticed the DB doesn’t have the 3rd group. Not needed in this case since the device provides the info, although nice to have for documentation.
Just in case someone finds this and is running into the same issue, Zooz gave me this information:
Based on the node ID number (over 232) and that beaming (repeating) is false in the logs, this indicates you have the device included via Z-Wave Long Range, which by default cannot support direct association programming.
So make sure it is not included as Z-Wave Long Range.
Interesting, I didn’t pick up on the node number, nor did I even think of the device reporting differently in that case, TIL!
Would be nice if Z-Wave JS UI could indicate that somehow, e.g. when trying to add a group has a warning it’s in LR mode so no other associations are possible.