Skip to main content

Module groups

Module groups 

Source
Expand description

Groups, cluster 0x0004 (Application Cluster §1.3).

The Groups cluster manages, per endpoint, the content of the node-wide Group Table that is part of the underlying interaction layer.

What makes “turn off the kitchen” one message rather than six. An endpoint joins a group, and a groupcast to that group reaches every member at once.

§The table is per endpoint and scoped to a fabric

Two scopes at once, and both matter. Per endpoint, because a two-gang switch has two endpoints and they belong to different rooms. Per fabric, because §1.3 says so — “group IDs referenced by attributes or other elements of this cluster are scoped to the accessing fabric” — and a device that let one ecosystem see or remove another’s groups would leak the layout of somebody’s house to whoever commissioned it second.

§A groupcast gets no answer

Every command here says the same thing: “If the … command was received as a groupcast, the server SHALL NOT generate a … Response command.” Six lights answering one multicast is six unicasts the client did not ask for, arriving at once — the classic broadcast storm, and the reason Groups::invoke consults InteractionContext’s group destination rather than always replying.

§What this cluster is not

It does not route anything. §1.3: “configuration of group addresses for outgoing commands is achieved using the Message Layer mechanisms where the Group Table is not involved.” This is the membership list; delivering a groupcast is crate::msg’s.

Re-exports§

pub use spec_groups::attribute::NAME_SUPPORT;
pub use spec_groups::command::ADD_GROUP;
pub use spec_groups::command::ADD_GROUP_IF_IDENTIFYING;
pub use spec_groups::command::ADD_GROUP_RESPONSE;
pub use spec_groups::command::GET_GROUP_MEMBERSHIP;
pub use spec_groups::command::GET_GROUP_MEMBERSHIP_RESPONSE;
pub use spec_groups::command::REMOVE_ALL_GROUPS;
pub use spec_groups::command::REMOVE_GROUP;
pub use spec_groups::command::REMOVE_GROUP_RESPONSE;
pub use spec_groups::command::VIEW_GROUP;
pub use spec_groups::command::VIEW_GROUP_RESPONSE;
pub use spec_groups::ID;
pub use spec_groups::NameSupportBitmap;
pub use spec_groups::PICS;
pub use spec_groups::REVISION;
pub use spec_groups::feature;

Structs§

Groups
The Groups cluster’s table.
Membership
One membership.
NeverIdentifying
A device with no Identify cluster, for which AddGroupIfIdentifying never applies.

Constants§

NAME_MAX
§1.3.7.1’s constraint on GroupName: “max 16”.

Traits§

GroupMembership
What the Scenes Management cluster needs from the Group Table (§1.4.9’s step 1).
Identifying
What the endpoint must tell the cluster for AddGroupIfIdentifying to work.