Expand description
Binding, cluster 0x001E (Core §9.6).
A binding is “a persistent relationship between an endpoint and one or more other local or remote endpoints” — how a switch is told which bulbs it controls. The cluster lives on the client endpoint, and §9.6 is careful that it only records an intention:
A binding does not require that the relationship exists. It is up to the node application to set up the relationship.
So this stores and validates the table; acting on it — opening a CASE session to the target, sending the command — is the application’s.
§The three fields are mutually exclusive in a way that matters
§9.6.5.1’s TargetStruct has Node, Group, Endpoint and Cluster, and its conformance
column is the whole design:
NodeisEndpoint— required when an endpoint is named.Groupis!Endpoint— and an endpoint is!Group. A binding is either unicast (node + endpoint) or groupcast (group), never both.Clusteris optional, and narrows whichever of the two it is.
A table that accepted both at once would describe a target with no meaning, and the node
would have to guess at send time — which is exactly the moment there is nobody to ask.
Target::is_valid refuses it at the door instead.
Structs§
Constants§
- BINDING
Binding(§9.6.6) —list[TargetStruct],RW VM F,N, mandatory.- FABRIC_
INDEX_ FIELD - The global
FabricIndexfield of a fabric-scoped struct (§7.19.1.9). - ID
0x001E(§9.6.4).- REVISION
- The revision §9.6.2’s table ends on.
Functions§
- cluster
- The descriptor for this cluster.