temperature_sensor (Thread): Feature ID 5001 mapped to wrong cluster 0x0406 instead of 0x0402

[herrniffler]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

Calling low_code_feature_update_to_system() with LOW_CODE_FEATURE_ID_TEMPERATURE_SENSOR_VALUE (5001) writes to Cluster 0x0402 (TemperatureMeasurement), so a temperature entity appears in Matter controllers like Home Assistant.

Actual behavior (suspected bug)

The value is written to Cluster 0x0406 (OccupancySensing) which does not exist in the data model, resulting in:

E esp_matter_core: Cluster cannot be NULL.
E esp_matter_attribute: Could not find Endpoint 0x0001's Cluster 0x00000406's Attribute 0x00000000

No temperature entity appears in Home Assistant. The data_model_thread.zap and generated data_model.bin correctly contain TemperatureMeasurement (0x0402), so the bug is in the pre-built binary (low_code_lp_core_maincore.bin, Dec 15 2025) which incorrectly maps Feature ID 5001 to Cluster 0x0406.

Hardware: ESP32-C6-DevKitM-1, Firmware: 1.1.0-b3023eed, Connection: Thread, Matter Controller: Home Assistant OHF Matter Server. Note: socket product works correctly over Thread.

Error logs or terminal output

app_driver: Fake temperature: 2743 (x100 C)
E esp_matter_core: Cluster cannot be NULL.
E esp_matter_core: Attribute cannot be NULL
E esp_matter_core: Cluster cannot be NULL.
E esp_matter_attribute: Could not find Endpoint 0x0001's Cluster 0x00000406's Attribute 0x00000000
W esp_matter_attribute: Endpoint 0x0001's Cluster 0x00000406's Attribute 0x00000000 is <invalid type: 0>

Steps to reproduce the behavior

1. Select product: temperature_sensor, chip: ESP32-C6: Thread
2. Click Prepare Device
3. Click Upload Configuration
4. Click Upload Code (with LOW_CODE_FEATURE_ID_TEMPERATURE_SENSOR_VALUE in app_driver.cpp)
5. Commission device via Matter (Home Assistant)
6. Wait 10 seconds for the timer callback to fire
7. See error in console - cluster 0x0406 instead of 0x0402

Project release version

1.1.0-b3023eed (main branch, latest)

System architecture

Intel/AMD 64-bit (modern PC, older Mac)

Operating system

Windows

Operating system version

Windows 11

Shell

ZSH

Additional context

• The data_model_thread.zap correctly defines TemperatureMeasurement (Cluster 1026 = 0x0402) on Endpoint 1 with device type MA-tempsensor (code 770)
• The generated data_model.json and data_model.matter also correctly contain TemperatureMeasurement
• LOW_CODE_FEATURE_ID_TEMPERATURE_SENSOR_VALUE = 5001 in low_code.h
• LOW_CODE_FEATURE_ID_OCCUPANCY_SENSOR_VALUE = 6001 in low_code.h
• The bug maps 5001 -> 0x0406 (Occupancy) instead of 0x0402 (Temperature)
• The socket product works correctly over Thread (ON/OFF confirmed in Home Assistant)
• Matter controller: Home Assistant with OHF Matter Server (Beta)
• OTBR: Home Assistant OpenThread Border Router (ha-thread-1cea, Channel 15)
• Subcore compiled: Dec 19 2025 09:08:36
• Maincore compiled: Dec 15 2025 10:38:58

[herrniffler]

Workaround found:
The bug is in the pre-built HP Core binary which incorrectly maps LOW_CODE_FEATURE_ID_TEMPERATURE_SENSOR_VALUE (5001) to Cluster 0x0406 (OccupancySensing) instead of 0x0402 (TemperatureMeasurement).
The workaround is to bypass the Feature ID mapping entirely by using the low_level.matter union in low_code_feature_details_t to directly address the correct cluster and attribute:

static void app_driver_report_temperature(int16_t temp)
{
    low_code_feature_data_t update_data = {
        .details = {
            .endpoint_id = 1,
            .feature_id = LOW_CODE_FEATURE_ID_UNHANDLED,
            .low_level = {
                .matter = {
                    .cluster_id = 0x00000402,   // TemperatureMeasurement
                    .attribute_id = 0x00000000, // MeasuredValue
                    .command_id = 0,
                }
            }
        },
        .value = { .type = LOW_CODE_VALUE_TYPE_INTEGER, .value_len = sizeof(int16_t), .value = (uint8_t*)&temp },
    };
    low_code_feature_update_to_system(&update_data);
}

[shreyash-b]

Hi @herrniffler
Sorry for the delay.

There was a minor issue relating to the cluster mapping between LowCode Feature ID and Matter Cluster ID.
We are working on fix and will release it shortly.

Thanks for the report.