Hi,
We are encountering a problem with an STM32WB55-based Zigbee router we have developed, where, in some cases, the Zigbee end device connected via the router becomes unreachable for requests sent from the coordinator.
Specifically, when the STM32WB55 acts as a Zigbee Router, a network configuration can be reached where it does not send a RREC command on behalf of its end-device child. The problem manifests itself if the end-device child changes parents at some point after joining, with the STM32WB55 device being the new parent. If the Coordinator needs to send a packet to the end device, it does not have an up-to-date route and sends packets to the original parent router instead.
We initially contacted Exegin, our coordinator Zigbee stack supplier, for support. They helped identify the root cause and confirmed that the STM32WB55-based Zigbee router does not send Route Records to the coordinator, causing the end device to become unreachable after a parent change to the STM32WB55 router.
We have observed this issue with the following configurations: stack version stm32wb5x_Zigbee_FFD_fw.bin v1.17.3 and v1.21.0 (also tested the Zigbee_APS_Router example).
Please let me know if you need additional details or packet captures to help diagnose the problem.
Thank you for your support!
Best regards,
d-serj
