#[non_exhaustive]pub enum Defect {
Missing(Element),
Disallowed(Element),
UnknownFeature(u8),
WrongRevision {
found: u16,
expected: u16,
},
ResponseAccepted(CommandId),
Provisional(Element),
}Expand description
Something a device’s configuration got wrong.
#[non_exhaustive] because the list has grown twice — ResponseAccepted and then
Provisional, each because a rule turned out not to be checked anywhere — and a match in
an integrator’s build should not break the next time the specification gives this crate a
reason to notice something new.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
Missing(Element)
A mandatory element the device does not serve.
Disallowed(Element)
An element the device serves that its feature map disallows.
UnknownFeature(u8)
A feature bit the device claims that this cluster revision does not define.
WrongRevision
The descriptor’s ClusterRevision is not the one the specification defines.
ResponseAccepted(CommandId)
A response command in the accepted list, which is a command the server sends.
Provisional(Element)
An element the specification marks provisional, on a build that did not ask for them.
Core §2.13 — and the Application Cluster and Device Library specifications’ own lists —
mark a mechanism provisional when it is “not certifiable and may change”. Serving one is
a deliberate act, and the provisional Cargo feature is where the deliberation goes; a
build without it that furnishes a P element is a node that cannot be certified for a
reason nobody chose.