Nrf54L15 Matter device frequently shows “No Response” in Home app after adding the Power Source cluster

[simon3panda]

Hi Team,
I tried adding battery reporting to the Matter bulb demo based on the nRF54L15DK. The device was successfully added to the Apple Home app, but I’ve noticed that it often shows “No Response” in the Home app. (Triggering an on/off command on the DK temporarily restores normal status.)

This issue typically occurs when the HomePod mini sends the command Type:0001:02 to the DK.
How can I prevent the “No Response” issue from appearing in the Home app?

The test code is attached.
Thanks in advance!

light_bulb_demo.zip

[Marte Myrvold]

Hi,

Which version of the nRF Connect SDK are you using?

What changes did you make to the sample?
I do not see the Power Source cluster enabled when I open the light_bulb.zap file in the ZAP tool.

Please share application logs from the device.

The “No Response” could be due to incomplete or slow handling of battery cluster read requests if the Apple Home tries to send a read request, or session/subscription instability after adding the Power Source cluster. I recommend double-checking your battery cluster implementation. It would also be helpful to check with chip-tool if you can interact with the Power Source cluster.

Best regards,
Marte

[simon3panda]

Thank you for reply!

sdk is 2.9.0
Power source has been add into zap-generated directory.

Yeah. That is my question. I'm not very clear about what interface sdk used to response the read request and how to modify.

I was capable to manually report batterypercentageremain to hub. 
the interface.zap.zip

[simon3panda]

3513.log.txt
Log for "No Response". Please check the last part of the log.

[Marte Myrvold]

Hi,

simon3panda said:

Power source has been add into zap-generated directory.

Can you try adding the cluster as described in our Adding clusters to Matter application guide?

Best regards,
Marte