Skip to content

electrical_utility_meter type / MeterIdentification cluster: Attribute is not managed by esp matter data model (CON-1907) #1636

@lboue

Description

@lboue

Describe the bug

I ran a quick test of the electrical_utility_meter type using the all_device_types_app example.
The MeterIdentification cluster is created correctly, but no value is returned. On the client side I am getting this error: {"TLVValue":null,"Reason":"InteractionModelError: Failure (0x1)"}.

The enpoint is started here:

case ESP_MATTER_ELECTRICAL_UTILITY_METER: {
esp_matter::endpoint::electrical_utility_meter::config_t electrical_utility_meter_config;
endpoint = esp_matter::endpoint::electrical_utility_meter::create(node, &electrical_utility_meter_config, ENDPOINT_FLAG_NONE, NULL);
break;
}

The cluster is created here with CLUSTER_FLAG_SERVER flag:

esp_err_t add(endpoint_t *endpoint, config_t *config)
{
esp_err_t err = add_device_type(endpoint, get_device_type_id(), get_device_type_version());
VerifyOrReturnError(err == ESP_OK, err);
cluster::meter_identification::create(endpoint, &(config->meter_identification), CLUSTER_FLAG_SERVER);
return ESP_OK;
}

It shoud return attributes 1, 2, 3 values defined here:

/* Attributes managed internally */
global::attribute::create_feature_map(cluster, 0);
attribute::create_meter_type(cluster, 0);
attribute::create_point_of_delivery(cluster, NULL, 0);
attribute::create_meter_serial_number(cluster, NULL, 0);

Environment

  • ESP-Matter Commit Id: 2e20fa0

  • ESP-IDF Commit Id: 4c2820d377d1375e787bcef612f0c32c1427d183

  • SoC (eg: ESP32 or ESP32-C3): ESP32-C6

  • Device Logs (Please attach the log file):
    esp32c6- MeterIdentification.log

  • Host Machine OS:

  • Host Machine Python version:

  • Commissioner app and versions if present: iOS 26

  • Home hub app and versions if present:

  • Commissioner's logs if present:

Any additional details

I (452587) chip[IM]: Received status response, status is 0x00
I (452607) chip[EM]: <<< [E:9682r S:29017 M:216423633 (Ack:160469227)] (S) Msg TX from 0000000000000003 to 3:000000000001B669 [269A] [UDP:[FE80::EC28:DB1F:6506:3C00%st1]:46683] --- Type 0001:05 (IM:ReportData) (B:1190)
I (452617) chip[EM]: ??1 [E:9682r S:29017 M:216423633] (S) Msg Retransmission to 3:000000000001B669 scheduled for 343ms from now [State:Active II:500 AI:300 AT:4000]
I (452747) chip[EM]: >>> [E:9682r S:29017 M:160469228 (Ack:216423633)] (S) Msg RX from 3:000000000001B669 [269A] to 0000000000000003 --- Type 0001:01 (IM:StatusResponse) (B:42)
I (452757) chip[IM]: Received status response, status is 0x00
E (452767) data_model: get_val_internal(927): Attribute is not managed by esp matter data model
E (452777) chip[DMG]: Fail to retrieve data, roll back and encode status on clusterId: 0x0000_0B06, attributeId: 0x0000_0000err = 501
E (452787) data_model: get_val_internal(927): Attribute is not managed by esp matter data model
E (452787) chip[DMG]: Fail to retrieve data, roll back and encode status on clusterId: 0x0000_0B06, attributeId: 0x0000_0001err = 501
E (452797) data_model: get_val_internal(927): Attribute is not managed by esp matter data model
E (452807) chip[DMG]: Fail to retrieve data, roll back and encode status on clusterId: 0x0000_0B06, attributeId: 0x0000_0002err = 501

...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions