Zigbee Power Config Cluster binding failure

[sjf]

Hi,

We have been working with a coordinator and an end device based on nRF52840 with nRF5_SDK_for_Thread_and_Zigbee_v4.0.0_dc7186b

Both devices are Zigbee 3.0 and implement Install Codes.

The End Device (low power device powered by batteries) tries to create some automatic bindings from itself to the coordinator by calling the function  zb_zdo_bind_req() to enable automatic reporting.

This process is invoked in the same way for the same endpoint (1) with clusters:

• Thermostat (0x201)
• OnOff (0x06)
• PowerConfig(0x01)

Thermostat and OnOff clusters always are successfully bound, but every time we try to bind PowerConfig cluster, the zigbee stack gets stucked. On every reset it starts working and gets stucked after some seconds.

The only solution is to erase config and avoid binding Power Config cluster.

Is there any known issue about PowerConfig binding? Is there something done out of specs from our side?

Thanks in advance,

Santiago

[Edvin]

Hello,

Do you have a project where PowerConfig is set up and used that I can use to reproduce this issue?

Have you tried to capture a sniffer trace of the network when you try to enable binding on the power config?

What command do you use to enable binding on the Power Config cluster? If you are not already doing so, can you please try to use the CLI example to enable binding? Does that work?

[sjf]

Hi,

The last 8 parameters of ZB_ZCL_DECLARE_POWER_CONFIG_BATTERY_ATTRIB_LIST_EXT were set to NULL and that was the root cause of this issue.

Thanks for your support.