Zigbee Feature Request: Create API to access binding table

[Peter K.]

Hi guys, 

for a current project, we need access to the local Zigbee binding table of the device (getting information about the binding of the current device).

I've spend quite some time searching the forum for the proper API calls to use for this and eventually found a workaround described here:  ZigBee: Accessing local binding table on end device . However, the used variable "gc_aps_bind_src_table" doesn't seem to be documented anywhere and directly accessing it causes many bugs, for instance duplicate entries and entries not disappearing even though an unbind has happened.

I'd kindly ask you to provide documentation for the binding table behaviour or provide further APIs to access the binding table.

While searching the forum, I've found plenty of threads asking for the same feature, but eventually run into the void:

 Reverse finding and binding role, initiator and target. 

 Creating a Binding locally on a Zigbee device 

 Is ZB_APS_ADDR_MODE_BIND_TBL_ID actually supported? 

 Binding an nrf52 Zigbee light switch to a light bulb 

 Generate command from Zigbee Client Cluster based on local binding table 

 ZigBee: Accessing local binding table on end device 

Kind regards, Peter

[Simonr]

Hi

Just to make sure I understand, the actual workaround is described in the link you provided where Marte explains the binding tables, correct? And you want a feature request to add this to the Zigbee nRF5 SDK?

The nRF5 SDK as explained in this statement is moved to maintenance mode, so I can't guarantee that this feature will be added any time soon, but I'll definitely make the request to our development team.

Best regards,

Simon

[Peter K.]

Hi Simon, thanks for your quick answer.

The workaround described by Marte is certainly some kind of workaround, but not a proper way to access the Zigbee binding table. The workaround accesses an internal variable (

gc_aps_bind_src_table

) of the ZBOSS library that is not mentioned or documented anywhere and doesn't show any reliable behaviour.

This issue is for the ZBOSS library which is included in both the nRF Connect SDK and nRF5 SDK, so I don't suppose that maintenance mode is a problem.

Kind regards,

Peter