3.2.9. Association Group Information (AGI) Command Class, version 2¶
The Association Group Information (AGI) Command Class allows a node to advertise the capabilities of each association group supported by a given application resource.
3.2.9.1. Compatibility considerations¶
The Association Group Information (AGI) Command Class, version 2 introduces the Profile category “Meter”.
The Association Group Information (AGI) Command Class, version 2 defines no new command fields or changes to the interpretation of Association Group Information (AGI) Command Class, version 1.
All sections and commands not described in this version remain unchanged from version 1.
3.2.9.2. The Association Group Information¶
\requirement{CC:0059.02.00.13.001}{0} \requirement{CC:0059.02.00.12.001}{4}
A device MAY implement one or more association groups. If the device implements association groups, the device SHOULD provide an Association Group Information (AGI) table as described in in Table 3.25.
3.2.9.2.1. Profile¶
The profile identifiers are referenced in Table 3.36. The profiles category “Meter” introduced in version 2 is described in Section 3.2.9.2.1.1.
3.2.9.2.1.1. Meter profiles¶
“Meter” profiles are intended for association groups of which commands are triggered by meter readings. As an example, a two-phase meter product could comprise three electric meters: one for each phase and one for the total consumption.
Meter profile identifiers are constructed by prepending the Meter Command Class identifier (referred to with AGI_PROFILE_METER) to a meter type defined in the Meter Command Class. The values in Table 3.36 only serve as examples to illustrate the construction of AGI Meter Profile identifiers. For the full list of available meter types, refer to the Meter Command Class.
\requirement{CC:0059.02.00.12.002}{0}
In case of multiple logical functions in a device, the device SHOULD implement one Multi Channel End Point for each logical function; e.g. each meter instance. Table 3.35 gives an example of a Multi Channel Meter device with two normal and one aggregated meter functions.
Root Device: |
|||
|---|---|---|---|
Group identifier |
Profile 2 bytes |
Command Class & Command (list) N bytes |
Group Name (UTF-8) M bytes |
1 |
General: Lifeline |
Meter Report Device Reset Locally Notification |
Lifeline |
2 |
Meter:Electric |
Basic Set |
On/Off control (Phase 1) |
3 |
Meter:Electric |
Basic Set |
On/Off control (Phase 1) |
4 |
Meter:Electric |
Basic Set |
On/Off control (Total Consumption) |
End Point 1: |
|||
Group identifier |
Profile 2 bytes |
Command Class & Command (list) N bytes |
Group Name (UTF-8) M bytes |
1 |
Meter:Electric |
Meter Report |
Phase 1 via Lifeline |
2 |
Meter:Electric |
Basic Set |
On/Off control (Phase 1) |
End Point 2: |
|||
Group identifier |
Profile 2 bytes |
Command Class & Command (list) N bytes |
Group Name (UTF-8) M bytes |
1 |
Meter:Electric |
Meter Report |
Phase 1 via Lifeline |
2 |
Meter:Electric |
Basic Set |
On/Off control (Phase 1) |
End Point 3 (aggregated): |
|||
Group identifier |
Profile 2 bytes |
Command Class & Command (list) N bytes |
Group Name (UTF-8) M bytes |
1 |
Meter:Electric |
Meter Report |
Total Consumption via Lifeline |
2 |
Meter:Electric |
Basic Set |
On/Off control (Total Consumption) |
The Profile identifier is Meter:Electric for all End Points but the Group Name allows a user to determine which End Point and which association group to use in order to configure the phase 2 meter to control an alarm lamp.
The Root Device in the above example advertises the Meter Report Command in the Lifeline group. Residing in a Multi Channel device, the Root Device does not actually implement any application functionality. The Meter Report command is a feature of the End Points which is advertised for backwards compatibility with legacy devices not supporting the Multi Channel Command Class.
Likewise, the Root device advertises the Basic Set Command in association groups 2..4. This is also a feature of the End Points. Refer to the Multi Channel Command Class for details on backwards compatibility.
End Points 1..3 in the above example advertise the Meter Report Command in association group 1. By advertising that zero NodeIDs are supported for association group 1, End Points indicate that this command is sent via the Root Device Lifeline group if a Multi Channel association is created for the Root Device Lifeline group.
