3.2.4. Association Command Class, version 2¶

The Association Command Class is used to manage associations to NodeID destinations. A NodeID destination may be a simple device or the Root Device of a Multi Channel device.

The following sections specify commands which were extended or added in version 2.

3.2.4.1. Compatibility Considerations¶

\requirement{CC:0085.02.00.21.001}{0}

A device supporting this command class version MUST also support the Association Command Class, version 1.

This version introduces - New methods for the removal of associations via the Association Remove Command - New commands

Association Specific Group Get Command

Association Specific Group Report Command

The considerations of Section 3.2.3.1 also apply to this version.

3.2.4.2. Z-Wave Plus Considerations¶

The considerations of Section 3.2.3.2 also apply to this version.

3.2.4.3. Security Considerations¶

The considerations of Section 3.2.3.3 also apply to this version.

3.2.4.4. Association Remove Command¶

The Association Remove Command is used to remove NodeID destinations from a given association group.

\requirement{CC:0085.02.04.11.001}{0}

If the node supports the Multi Channel Association Command Class the node MUST NOT remove End Point destinations in response to this command.

Table 3.14 Association Remove Command¶
7	6	5	4	3	2	1	0
Command Class = COMMAND_CLASS_ASSOCIATION (0x85)
Command = ASSOCIATION_REMOVE (0x04)
Grouping Identifier
NodeID 1
…
NodeID N

Grouping identifier (8 bits)

This field is used to specify from which association group the specified NodeID destinations are to be removed.

\requirement{CC:0085.02.04.11.002}{0}

This field MUST be interpreted in combination with the NodeID field.

\requirement{CC:0085.02.04.11.003}{0}

A node that receives an unsupported Grouping Identifier MUST ignore this command; with the exception of Grouping Identifier 0, which MUST be accepted. Refer to Table 3.15.

NodeID (N bytes)

\requirement{CC:0085.02.04.11.004}{4}

This field specifies a list of NodeID destinations that are to be removed. The Grouping Identifier and NodeID fields MUST be interpreted as indicated in Table 3.15:

Table 3.15 Association Remove, V2::Parameter Interpretation¶
Grouping Identifier	Number of NodeIDs	Interpretation
> 0	> 0	Remove destination NodeIDs from association group (MANDATORY V1, MANDATORY V2)
> 0	= 0	Remove all destination NodeIDs from association group (RECOMMENDED V1, MANDATORY V2)
= 0	> 0	Remove destination NodeIDs from all association groups (Reserved V1, MANDATORY V2)
= 0	= 0	Remove all destination NodeIDs from all association groups (Reserved V1, MANDATORY V2)

3.2.4.5. Association Specific Group Get Command¶

This command allows a portable controller to interactively create associations from a multi-button device to a destination that is out of direct range.

\requirement{CC:0085.02.0B.12.001}{0} \requirement{CC:0085.02.0B.11.001}{4} \requirement{CC:0085.02.0B.12.002}{8}

It is OPTIONAL for a device to support this functionality. However, a receiving device MUST always return the Association Specific Group Report Command in response to this command. If the device does not support this functionality, a Group parameter value of 0 SHOULD be advertised in the Association Specific Group Report Command that is returned in response to this command.

This functionality allows a supporting multi-button device to detect a key press and subsequently advertise the identity of the key. The following sequence of events takes place:

The user activates a special identification sequence and pushes the button to be identified
The device issues a Node Information frame (NIF)
The NIF allows the portable controller to determine the NodeID of the multi-button device
The portable controller issues an Association Specific Group Get Command to the multi-button device
The multi-button device returns an Association Specific Group Report Command that advertises the association group that represents the most recently detected button

\requirement{CC:0085.02.0B.12.003}{8}

The Association Group Information (AGI) Command Class provides a centralized alternative for the discovery of available association groups and the capabilities of these groups. A device supporting this functionality SHOULD also support the Association Group Information (AGI) Command Class.

\requirement{CC:0085.02.0B.11.002}{0} \requirement{CC:0085.02.0B.11.003}{4}

This command MUST NOT be issued via multicast addressing. A receiving node MUST NOT return a response if this command is received via multicast addressing. The Z-Wave Multicast frame, the broadcast NodeID and the Multi Channel multi-End Point destination are all considered multicast addressing methods.

Table 3.16 Association Specific Group Get Command¶
7	6	5	4	3	2	1	0
Command Class = COMMAND_CLASS_ASSOCIATION (0x85)
Command = ASSOCIATION_SPECIFIC_GROUP_GET (0x0B)

Clarification: Previous text revisions of this specification presented conflicting guidelines for the Association Specific Group Get Command when received by non-supporting devices.

\requirement{CC:0085.02.0B.12.004}{4}

The values 0 and 1 were both suggested for the Group field of the Association Specific Group Report Command. It is RECOMMENDED that the value 0 is returned by non-supporting devices.

3.2.4.6. Association Specific Group Report Command¶

This command is used to advertise the association group that represents the most recently detected button.

Table 3.17 Association Specific Group Report Command¶
7	6	5	4	3	2	1	0
Command Class = COMMAND_CLASS_ASSOCIATION (0x85)
Command = ASSOCIATION_SPECIFIC_GROUP_REPORT (0x0C)
Group

Group (8 bits)

This field is used to advertise the association group that represents the most recently detected button.

\requirement{CC:0085.02.0C.11.001}{0}

The value of this field MUST be in the range 0..255.

\requirement{CC:0085.02.0C.11.002}{0} \requirement{CC:0085.02.0C.12.001}{4}

If a supporting device implements a multi-button device, the Group field MUST advertise an association group which represents the most recently activated button. The actual association group SHOULD be able to control an actuator device, e.g. via the Basic Command Class.

\requirement{CC:0085.02.0C.12.002}{0}

This field SHOULD be set to 0 if the functionality is not supported or if the most recent button event does not map to an association group.

Clarification: Previous text revisions of this specification presented conflicting guidelines for the Association Specific Group Get Command when received by non-supporting devices.

\requirement{CC:0085.02.0C.12.003}{0}

The values 0 and 1 were both suggested for the Group field of the Association Specific Group Report Command. It is RECOMMENDED that the value 0 is returned by non-supporting devices.