I am Vinay, from Samsung. Currently I am trying to understand the rejoin behavior of router devices.
I currently have a coordinator and a router device in my zigbee network. For the router to rejoin, I switched off the router and I changed the channel of the existing router and waited for the router to rejoin for > 30 minutes. The router did not rejoin. I am not sure if this is the right behavior to see the rejoin requests from the router.
I read in this documentation https://www.silabs.com/documents/public/user-guides/UG105.pdf that
the rejoin behavior if
due to a weak/missing connection between parent and child, changed PAN ID, changed network key, or changed channel
Kindly enlighten me about reproducing the rejoin behavior for router zigbee devices.
Could you detail the method of how you change the channel of the current network, and how you perform the rejoin (APIs or CLI used, etc.)?
Thanks for the reply.
I can Telnet to the coordinator. Since I have information of the present channel, I can send a command to the coordinator to change the channel to a new one.
Here are the details steps from scratch:
1) Join the Router to the coordinator.
2) Power of the Router.
3) Power off the coordinator for 20 minutes.
4) Power on the coordinator.
5) Change the channel of the coordinator once it is on line .( By telnet command )
6) Start sniffing in the new channel .
7) Power on the router device .
Expected result :
Router device tries to search for the coordinator with the same PAN in a new channel.
Actual result :
Router device does not rejoin and stays in the old channel.
There is no control over routers as they are devices from Market. We cant do anything here.
So we wanted to understand how to rejoin the router to coordinator.
If these steps wont help, we need your help in providing guidance for bringing rejoin of routers.
Can anybody help us here ? This is an important step for Samsung to understand the behavior of zigbee devices.
Zigbee router doesn't scan channel during power on if it had joined a Zigbee network. Before coordinator changes channel, it should send notification to all of devices including router in the network.
Thank for the response.
By looking at YK's comments we cant see the rejoin of routers by changing the channel.
So what is the method for forcing the router to rejoin.?
I am basically looking for
a) How the network should be formed like how many routers should be in place
b) should the coordinator be switched off for a particular duration etc
c) should the router be moved to a farther location etc .
Since the routers are from different manufacturers we need a plan / steps which would help
us to see this rejoin behaviour. ( We are trying to see rejoin messages in the Sniffer )
So we need help in formulating a method for rejoin behaviour for these router devices.
We have devices from different manufacturers namely
Jasco, Osram, Sengled etc .
I suggest you to search Mgmt_NWK_Update_notify and Mgmt_NWK_Update_req in Zigbee spec to study the channel interference and change topic.
Thank you @YK We will go through the topics.
However is there any way to make the router rejoin ?
@YK: ok by resetting the router we are making sure it looses its previous link key, PAN info etc and hence it would search in all the channels. We would try this method. Thank you.
I have another question here
Does the router rejoin without making any of these changes to it ? Because we have been trying
different possibilities like move coordinator to a farther location , or switch off the coordinator for a long time and switch it on again or like disconnecting the router under test for a day or two and connect it back to the network. In all these methods the router was able to talk to ZC all the time as if nothing has changed.