Z-Wave associationGet for Group > 1 Not Working

🚧 Developers Broken-code
1

I'm having some interesting results with Z-Wave associations. Setting an association seems to work great. Getting an association report for anything over group 1 isn't quite working right. For example, if I send the following:

cmds << zwave.associationV2.associationGet(groupingIdentifier:1)
cmds << zwave.associationV2.associationGet(groupingIdentifier:2)
cmds << zwave.associationV2.associationGet(groupingIdentifier:3)

I get:

AssociationReport(groupingIdentifier:null, maxNodesSupported:null, reportsToFollow:null, nodeId:null)
AssociationReport(groupingIdentifier:null, maxNodesSupported:null, reportsToFollow:null, nodeId:null)
AssociationReport(groupingIdentifier:1, maxNodesSupported:5, reportsToFollow:0, nodeId:1)

Seems like a small bug. Hoping it can get fixed. :slight_smile:

2

Thanks, we'll have a look!

1 Like
3

@ericm
I reviewed our association report implementation and its not obvious why it's doing this.
Can you post the data coming into parse that's causing the null reports?

4

Here you go. Raw description for the 1st group (which comes in ok). Then the raw description for the failed groups.

Parsed AssociationReport(groupingIdentifier:null, maxNodesSupported:null, reportsToFollow:null, nodeId:null) to [null]
Associations for Group null: []
zw device: 4C, command: 8503, payload: 03 05 00
Parsed AssociationReport(groupingIdentifier:null, maxNodesSupported:null, reportsToFollow:null, nodeId:null) to [null]
Associations for Group null: []
zw device: 4C, command: 8503, payload: 02 05 00
Parsed AssociationReport(groupingIdentifier:1, maxNodesSupported:5, reportsToFollow:0, nodeId:1) to [null]
Associations for Group 1: [01]
zw device: 4C, command: 8503, payload: 01 05 00 01

1 Like
5

this will be fixed in the next release, or rather it is fixed, and will be available in the next release LOL

1 Like
6

That is awesome. Thank you so much. I have a similar issue with the protection command class. I debated messaging about it here, but since it has similar results, maybe it will get fixed too with this update.

So first setting protection doesn't seem to work:

zwave.protectionV2.protectionSet(localProtectionState : 2, rfProtectionState: 0)

Getting the protection report returns the same null info as mentioned above:

zwave.protectionV2.protectionGet()

Returns:

ProtectionReport(localProtectionState:null, rfProtectionState:null)
'zw device: 4D, command: 7503, payload: 00 02 ' parsed to null

Anyway, this one is low priority, but just wanted to make you aware in case it is related to this association problem.

Thanks for everything!

7

It isn't, I mean each one of these is a separate method, so the problems with them are specific to the command

8

If you can batch these up it's easier for me to track and fix, i need to get out of current mode whatever that is and enter zwave mode if you follow.