search

project-chip / connectedhomeip

Matter (formerly Project CHIP) creates more connections between more objects, simplifying development for manufacturers and increasing compatibility for consumers, guided by the Connectivity Standards Alliance.
https://buildwithmatter.com
Apache License 2.0
7.33k stars 1.97k forks source link

Occupancy Sensing: all timing attributes should be marked non-volatile in all examples #35043

Open tcarmelveilleux opened 3 weeks ago

tcarmelveilleux commented 3 weeks ago

The spec implied in "7.12.1. Persistence":

Cluster attributes that represent configuration data SHALL be persistent data unless otherwise specified.

For example: a writable attribute that persistently changes the behavior (or mode) of the cluster.

Examples of non-configuration data: device state data, data that is calculated or comes from an external source, such as a sensor value, a time value, etc.

Many clusters define persistent data that is not surfaced as attributes, but is managed by commands. Commissioning or configuration data that is created to allow the cluster to perform its function is persistent data. A group table entry and binding entries are both persistent data across a restart.

All the occupancy settings like XxxOccupiedToUnoccupiedDelay and XxxUnoccupiedToOccupiedDelay are obvious configuration data that need to be stored across reset, but this was not reflected in the samples.

Everyone working on occupancy sensors should be reminded to store these values persistently if the attributes are supported.

See also https://github.com/CHIP-Specifications/connectedhomeip-spec/pull/10222

leorozendaal commented 3 weeks ago

spec issue to clarify the spec text on persistence vs. N plus do a walkhthrough of all clusters: https://github.com/CHIP-Specifications/connectedhomeip-spec/issues/10221

tcarmelveilleux commented 1 week ago

Not a SVE blocker