Jon Smirl

chip-tool temperaturemeasurement read measured-value 0x7394 0x1 Reads it once on-demand If you set up a subscription it will send a message whenever it changes

Don't sit in a polling loop on your client doing: chip-tool temperaturemeasurement read measured-value 0x7394 0x1 That is what subscriptions are for.

Read about chip-tool interactive mode. https://docs.espressif.com/projects/esp-matter/en/latest/esp32/developing.html#commissioning-and-control

We use sensor chips which generate an interrupt when the temp changes. TI HDC2010 family. Get the interrupt, read the sensor chip, update the attribute. You can also capture the...

Calling binding_init() before matter start gets the binding manager started. ~~~ client::binding_init(); err = esp_matter::start(app_event_cb); ~~~ But.... attrib 0 on my bindings clusters is still not getting reported. ~~~ I...

It is calling Read in AttributeAccessInterface, but it is not reporting... ~~~ I (7863) esp_matter_attribute: ********** R : Endpoint 0x0003's Cluster 0x00000062's Attribute 0x00000001 is 16 ********** BindingTableAccess::Read 65532 I...

This message in log is probably bad: ~~~ I (2061) chip[SVR]: Cannot load binding table: a0 ~~~ ... that is not fatal. The problem is: When I do a wildcard...

The problem is this: ~~~ client::binding_init(); err = esp_matter::start(app_event_cb); ~~~ Because my endpoints are dynamically created through the bridge code binding_init() never gets called. When I manually start binding_init everything...

Don't descriptor and identify have to be on every endpoint? If so, you could combine them with create endpoint.

Using this cluster is very painful. Just turn on the standard NTP client via menuconfig which is 1000 times easier.