pub struct RequiredCluster {
pub id: ClusterId,
pub name: &'static str,
pub server: bool,
pub conform: Conform,
pub features: &'static [(&'static str, Conform)],
pub attributes: &'static [(&'static str, Conform)],
pub commands: &'static [(&'static str, Conform)],
pub events: &'static [(&'static str, Conform)],
}Expand description
A cluster a device type requires or allows on the endpoint.
Fields§
§id: ClusterIdThe cluster’s id.
name: &'static strThe readable name — “On/Off”.
server: boolWhether it is the server side. A client cluster is a binding target the endpoint talks to, not something it serves, so a validator must not demand it in the endpoint’s own cluster list.
conform: ConformWhether the endpoint must have it.
features: &'static [(&'static str, Conform)]Feature bits the device type demands beyond the cluster’s own conformance, by the cluster’s own short codes.
This is the part a cluster list alone cannot express: On/Off Light does not merely
require On/Off, it requires On/Off with Lighting, and a light that serves the
cluster without the feature has no StartUpOnOff — so it comes back on at whatever
state it was in, which is the behaviour the device type exists to rule out.
attributes: &'static [(&'static str, Conform)]Attributes the device type demands beyond the cluster’s own conformance, by name.
commands: &'static [(&'static str, Conform)]Commands it demands, by name.
events: &'static [(&'static str, Conform)]Events it demands, by name.