This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Migrating some methods from nRF Zigbee & Thread SDK to NCS

Hi,

We are porting our application from nRF Zigbee & Thread SDK to NCS.

On the ZIgbee side, we have been using this methods:

1. zb_zdo_find_bind_src(): to check if a binding was already stored in the local bindings table

2. bdb_load_factory_new_flag(): called before the method zb_bdb_is_factory_new() to update the returned value.

Is there any new alternative method or procedure to get the same result in 1)?

Is still bdb_load_factory_new_flag() necessary on NCS?

Regards,

Santiago

Parents
  • Hi

    There doesn't seem to be a similar API in NCS, but you can implement the reading device's binding table and look for an entry associated with a specific device. Pleasse take a look at a CLI example for how it can be implemented:

    • zdo mgmt_bind. Have a CLI command read the binding table from a device, then the device can ask itself for a binding table.
    • cmd_zb_mgmt_bind_cb(). Have a callback function that parses and prints received entries of a binding table.

    You can also use the Zigbee CLI to test this solution, so for example, the coordinator device can read its own binding table:

    uart:~$ zdo short 
    0000
    Done
    uart:~$ zdo mgmt_bind 0x0000
    [idx] src_address      src_endp cluster_id dst_addr_mode dst_addr         dst_endp
    [  0] f4ce361fe8ab4e51       10     0x0001           003 f4ce36f71a6cab56      010
    Total entries for the binding table: 1
    Done

    Best regards,

    Simon

Reply
  • Hi

    There doesn't seem to be a similar API in NCS, but you can implement the reading device's binding table and look for an entry associated with a specific device. Pleasse take a look at a CLI example for how it can be implemented:

    • zdo mgmt_bind. Have a CLI command read the binding table from a device, then the device can ask itself for a binding table.
    • cmd_zb_mgmt_bind_cb(). Have a callback function that parses and prints received entries of a binding table.

    You can also use the Zigbee CLI to test this solution, so for example, the coordinator device can read its own binding table:

    uart:~$ zdo short 
    0000
    Done
    uart:~$ zdo mgmt_bind 0x0000
    [idx] src_address      src_endp cluster_id dst_addr_mode dst_addr         dst_endp
    [  0] f4ce361fe8ab4e51       10     0x0001           003 f4ce36f71a6cab56      010
    Total entries for the binding table: 1
    Done

    Best regards,

    Simon

Children
No Data
Related