Hello Gerd Busker

You can capture the EZSP trace with Network Analyzer and check what's happened during the initiation.

Best Regards,

Lei Sun

Hello UnicycleBloke

Why you want to implement the function? I can't see any useful info about it. Can you explain more about your purpose?

Best Regards,

Lei Sun

Hello Gauthier Dewulf

Here is a example with the CLI command:

> raw 0x0000 "1234567890"

> send 0xFFFF 1 1

raw (args)
   <uint16_t>  two byte cluster id
   <string>  ZCL message, including ZCL header and payload
 

send (args)
   <uint16_t>  short id of the device to send the message to
   <uint8_t>  The endpoint to send the message from
   <uint8_t>  The endpoint to send the message to
 

You can do the same thing with APIs.

Best Regards,

Lei Sun

Hello Shreekant Prasad,

The easier way is to use a custom token to implement your requirement.

https://www.silabs.com/documents/public/application-notes/an1154-tokens-for-non-volatile-storage.pdf

Best Regards,

Lei Sun

Hello Nguyen Quoc Viet,

For Zigbee stack, there is no sample for using the sensors on Thunderboard Sense 2. But you can feel free to add the sensor related code based on the Zigbee samples. For Zigbee sample, these sensor are the peripheral so you can feel free to add them if needed.

Best Regards,

Lei Sun

Hello Nguyễn Cao Bái

Sort answers for reporting, you need fill the reporting table and binding table for the destination. 

Best Regards,

Lei Sun

Hello Ricky,

Can you confirm what's your operation for this packet trace? Does it come from the same device? Do you see it(twice beacon request) every time?

You can do some more testing and attach the packet trace on here.

Best Regards,

Lei Sun