Origin of INVALID_VALUE message

Developer Programs Support
1

I am communicating with an ESP32-H2.
Sometimes I get an INVALID_VALUE line in the logs.
For example, when I send a message to increase the heatingSetpoint.

2025-02-17T19:44:45.230378662+01:00 INFO Espressif Airco Control <ZigbeeDevice: 9763dd9f-71e7-42e1-9963-aee010751371 [0xD301] (Espressif Airco Control)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD301, src_endpoint: 0x08, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xFF, rssi: -68, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x31, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: INVALID_VALUE, AttributeId: 0x0012 > > > >

Is the above message sent from the ESP32 device?
I guess so since I see: “src_addr: 0xD301, src_endpoint: 0x08”. But I want to be sure since I do not see anything of activity on the ESP32 device.

So, can I be sure that the above message is sent by the ESP32 device, or is there a possibility that this message is generated by the Smartthings Hub itself?

Thanks

2

Hi, @mvermand
Could you please share the command you sent in the driver’s code and its log of ZigbeeMessageTx to see how it was sent to the device?
In the logs you sent above I can only see the received message. It’s my understanding the hub cannot generate a ZigbeeMessageRx without actually receiving a Zigbee message but after you send the info requested, I’ll ask the engineering team.

1 Like