Electrical Power Measurement Cluster Added via ZAP in SDK 3.2.0-preview Not Showing in Controllers (e.g., Home Assistant)

[sbehnam3]

Hello,

I recently migrated to SDK version 3.2.0-preview, which supports Matter 1.4.x.

When I use ZAP and add a new endpoint to the light_bulb example under the name Electrical Sensor, I include clusters from the Measurement & Sensing category, specifically the Electrical Power Measurement cluster. However, after building and flashing the device, no UI appears for this cluster in controllers such as the latest version of Home Assistant.

Interestingly, if I add other clusters, for example Air Quality, they are displayed correctly in the UI.

Could you please help me understand why the Electrical Power Measurement cluster is not displayed in the UI? Is there a known limitation or additional configuration required for this cluster to be recognized by controllers?

Thank you very much for your guidance.

[Marte Myrvold]

Hi,

Are you able to interact with the cluster using chip-tool? 

It could be that the Electrical Sensor device type is not supported in Home Assistant. I believe there is a channel dedicated to Matter on the Home Assistant Discord, so you can try asking there: https://discord.com/invite/home-assistant.

Best regards,
Marte

[sbehnam3]

Hi Martte
Thank you for your respond and thank you for your suggestion regarding chip-tool testing. I haven’t tested the cluster using chip-tool yet, but I plan to do so soon and will share the results with you.

In the meantime, while observing the logs during Home Assistant’s attempt to interact with my development kit, I noticed repeated errors like:

Fail to retrieve data ... clusterId: 0x0090 / 0x0091, attributeId: ... err = 501 

These cluster IDs correspond to the Electrical Power Measurement cluster. Based on my understanding, the 0x501 status indicates Unsupported Cluster / Unsupported Attribute.

Could you please clarify whether these errors suggest that the issue is on our side (in the device implementation) or if they are originating from Home Assistant?

Thank you very much for your guidance.

[Marte Myrvold]

Hi,

Are these logs from the device or Home Assistant?

Can you share the complete log?

Best regards,
Marte

[sbehnam3]

Hi Marte,

When I built and flashed the Light Bulb example with an additional Electrical Sensor configured as endpoint 2 (generated using ZAP), the device started advertising successfully on the nRF52840 DK.

I'm connecting to it through Home Assistant Green, which acts as the border router with a Thread dongle connected via USB. The commissioning and control are done through the Home Assistant app.

The logs I previously shared are taken directly from the nRF52840 DK nrf serial terminal — they are not from Home Assistant.
Below, I’ve included the part of  log captured from the DK’s COM port for your reference.

D: 207208 [IN]UDP Message Received packet nb : 60 SrcAddr : fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2[47953] DestAddr : fd6c:c98b:e90b:1:5e69:660a:a976:1297[5540] Payload Length 42
I: 207224 [EM]>>> [E:14636r S:21075 M:176490579 (Ack:258267128)] (S) Msg RX from 2:000000000001B669 [DC11] to 0000000000000060 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 207239 [IM]Received status response, status is 0x00
I: 207269 [EM]<<< [E:14636r S:21075 M:258267129 (Ack:176490579)] (S) Msg TX from 0000000000000060 to 2:000000000001B669 [DC11] [UDP:[fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2]:47953] --- Type 0001:05 (IM:ReportData) (B:1203)
I: 207290 [EM]??1 [E:14636r S:21075 M:258267129] (S) Msg Retransmission to 2:000000000001B669 scheduled for 1904ms from now [State:Active II:500 AI:300 AT:4000]
D: 207415 [IN]UDP Message Received packet nb : 61 SrcAddr : fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2[47953] DestAddr : fd6c:c98b:e90b:1:5e69:660a:a976:1297[5540] Payload Length 42
I: 207432 [EM]>>> [E:14636r S:21075 M:176490580 (Ack:258267129)] (S) Msg RX from 2:000000000001B669 [DC11] to 0000000000000060 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 207447 [IM]Received status response, status is 0x00
I: 207473 [EM]<<< [E:14636r S:21075 M:258267130 (Ack:176490580)] (S) Msg TX from 0000000000000060 to 2:000000000001B669 [DC11] [UDP:[fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2]:47953] --- Type 0001:05 (IM:ReportData) (B:1199)
I: 207494 [EM]??1 [E:14636r S:21075 M:258267130] (S) Msg Retransmission to 2:000000000001B669 scheduled for 1833ms from now [State:Active II:500 AI:300 AT:4000]
D: 207620 [IN]UDP Message Received packet nb : 62 SrcAddr : fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2[47953] DestAddr : fd6c:c98b:e90b:1:5e69:660a:a976:1297[5540] Payload Length 42
I: 207636 [EM]>>> [E:14636r S:21075 M:176490581 (Ack:258267130)] (S) Msg RX from 2:000000000001B669 [DC11] to 0000000000000060 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 207651 [IM]Received status response, status is 0x00
E: 207658 [DMG]Fail to retrieve data, roll back and encode status on clusterId: 0x0000_0090, attributeId: 0x0000_0000err = 501
E: 207670 [DMG]Fail to retrieve data, roll back and encode status on clusterId: 0x0000_0090, attributeId: 0x0000_0001err = 501
E: 207682 [DMG]Fail to retrieve data, roll back and encode status on clusterId: 0x0000_0090, attributeId: 0x0000_0002err = 501
E: 207693 [DMG]Fail to retrieve data, roll back and encode status on clusterId: 0x0000_0090, attributeId: 0x0000_0008err = 501
E: 207707 [DMG]Fail to retrieve data, roll back and encode status on clusterId: 0x0000_0091, attributeId: 0x0000_0000err = 501
I: 207725 [EM]<<< [E:14636r S:21075 M:258267131 (Ack:176490581)] (S) Msg TX from 0000000000000060 to 2:000000000001B669 [DC11] [UDP:[fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2]:47953] --- Type 0001:05 (IM:ReportData) (B:777)
I: 207746 [EM]??1 [E:14636r S:21075 M:258267131] (S) Msg Retransmission to 2:000000000001B669 scheduled for 1908ms from now [State:Active II:500 AI:300 AT:4000]
D: 207834 [IN]UDP Message Received packet nb : 63 SrcAddr : fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2[47953] DestAddr : fd6c:c98b:e90b:1:5e69:660a:a976:1297[5540] Payload Length 34
I: 207851 [EM]>>> [E:14636r S:21075 M:176490582 (Ack:258267131)] (S) Msg RX from 2:000000000001B669 [DC11] to 0000000000000060 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34)
D: 208681 [IN]UDP Message Received packet nb : 64 SrcAddr : fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2[47953] DestAddr : fd6c:c98b:e90b:1:5e69:660a:a976:1297[5540] Payload Length 66
I: 208697 [EM]>>> [E:14637r S:21075 M:176490583] (S) Msg RX from 2:000000000001B669 [DC11] to 0000000000000060 --- Type 0001:08 (IM:InvokeCommandRequest) (B:66)
I: 208713 [ZCL]OpCreds: Received an UpdateFabricLabel command
I: 208745 [FP]Metadata for Fabric 0x2 persisted to storage.
I: 208752 [EM]<<< [E:14637r S:21075 M:258267132 (Ack:176490583)] (S) Msg TX from 0000000000000060 to 2:000000000001B669 [DC11] [UDP:[fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2]:47953] --- Type 0001:09 (IM:InvokeCommandResponse) (B:70)
I: 208773 [EM]??1 [E:14637r S:21075 M:258267132] (S) Msg Retransmission to 2:000000000001B669 scheduled for 1862ms from now [State:Active II:500 AI:300 AT:4000]
D: 208803 [IN]UDP Message Received packet nb : 65 SrcAddr : fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2[47953] DestAddr : fd6c:c98b:e90b:1:5e69:660a:a976:1297[5540] Payload Length 34
I: 208820 [EM]>>> [E:14637r S:21075 M:176490584 (Ack:258267132)] (S) Msg RX from 2:000000000001B669 [DC11] to 0000000000000060 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34)
D: 208954 [IN]UDP Message Received packet nb : 66 SrcAddr : fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2[47953] DestAddr : fd6c:c98b:e90b:1:5e69:660a:a976:1297[5540] Payload Length 57
I: 208970 [EM]>>> [E:14638r S:21075 M:176490585] (S) Msg RX from 2:000000000001B669 [DC11] to 0000000000000060 --- Type 0001:03 (IM:SubscribeRequest) (B:57)
D: 208984 [IM]Received Subscribe request
I: 209036 [DMG]Final negotiated min/max parameters: Min = 1s, Max = 60s
E: 209125 [DL]Long dispatch time: 156 ms, for event type 3
I: 209161 [EM]<<< [E:14638r S:21075 M:258267133 (Ack:176490585)] (S) Msg TX from 0000000000000060 to 2:000000000001B669 [DC11] [UDP:[fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2]:47953] --- Type 0001:05 (IM:ReportData) (B:1200)
I: 209182 [EM]??1 [E:14638r S:21075 M:258267133] (S) Msg Retransmission to 2:000000000001B669 scheduled for 1909ms from now [State:Active II:500 AI:300 AT:4000]
D: 209317 [IN]UDP Message Received packet nb : 67 SrcAddr : fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2[47953] DestAddr : fd6c:c98b:e90b:1:5e69:660a:a976:1297[5540] Payload Length 42
I: 209333 [EM]>>> [E:14638r S:21075 M:176490586 (Ack:258267133)] (S) Msg RX from 2:000000000001B669 [DC11] to 0000000000000060 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 209348 [IM]Received status response, status is 0x00
I: 209386 [EM]<<< [E:14638r S:21075 M:258267134 (Ack:176490586)] (S) Msg TX from 0000000000000060 to 2:000000000001B669 [DC11] [UDP:[fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2]:47953] --- Type 0001:05 (IM:ReportData) (B:1207)
I: 209407 [EM]??1 [E:14638r S:21075 M:258267134] (S) Msg Retransmission to 2:000000000001B669 scheduled for 1868ms from now [State:Active II:500 AI:300 AT:4000]
D: 209528 [IN]UDP Message Received packet nb : 68 SrcAddr : fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2[47953] DestAddr : fd6c:c98b:e90b:1:5e69:660a:a976:1297[5540] Payload Length 42
I: 209544 [EM]>>> [E:14638r S:21075 M:176490587 (Ack:258267134)] (S) Msg RX from 2:000000000001B669 [DC11] to 0000000000000060 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 209559 [IM]Received status response, status is 0x00
E: 209571 [DMG]Fail to retrieve data, roll back and encode status on clusterId: 0x0000_002B, attributeId: 0x0000_0001err = 501
I: 209606 [EM]<<< [E:14638r S:21075 M:258267135 (Ack:176490587)] (S) Msg TX from 0000000000000060 to 2:000000000001B669 [DC11] [UDP:[fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2]:47953] --- Type 0001:05 (IM:ReportData) (B:1191)
I: 209627 [EM]??1 [E:14638r S:21075 M:258267135] (S) Msg Retransmission to 2:000000000001B669 scheduled for 1870ms from now [State:Active II:500 AI:300 AT:4000]
D: 209785 [IN]UDP Message Received packet nb : 69 SrcAddr : fd6c:c98b:e90b:1:cccb:c9d1:7ea9:54c2[47953] DestAddr : fd6c:c98b:e90b:1:5e69:660a:a976:1297[5540] Payload Length 42
I: 209802 [EM]>>> [E:14638r S:21075 M:176490588 (Ack:258267135)] (S) Msg RX from 2:000000000001B669 [DC11] to 0000000000000060 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 209817 [IM]Received status response, status is 0x00
I: 209885 [EM]<<< [E:14638r S:21075 M:258267136 (Ack:176490588)] (S) Msg TX from 0000000000000060 to 2:000000000001B669 [DC11] 

[sbehnam3]

Hi Marte,

Regarding your question: “Are you able to interact with the cluster using chip-tool?”

I have set up the Matter environment and chip-tool on Linux and was able to connect to the nRF52840 DK development board via Bluetooth. I collected some logs, but these logs only cover the initial commissioning and connection phase.

Immediately after commissioning, the device switches to Thread for stable communication. Since my system does not have Thread connectivity, the connection drops, and I cannot use chip-tool to send requests or read the cluster data.

To interact reliably via chip-tool, I would need a device that supports both Bluetooth commissioning and Thread communication, so it can maintain a stable connection with the development board.

I’m wondering if there’s any alternative way to capture logs or interact with the board using chip-tool without needing an additional Thread-capable device?