In our application, we can have multiple equivalent but overlapping networks. As it is okay for a device to join any of these networks, we have the same PAN ID, security etc. Currently the joining device picks the router with the best/strongest response. It is possible that a network reaches the capacity of the coordinator to manage the traffic and thus needs to reject devices that may have otherwise successfully joined at a ZigBee level.
In the XBee3 user manual under 'Manage multiple Zigbee networks' -> 'Application messaging framework', there is a brief discussion about handling this type of situation using 'application messaging'. That approach would seem a good fit for us.
My question is if an XBee3 is forced to leave the network (NR) as a result of such application messaging, how can I be sure it will try to rejoin other available networks before attempting to rejoin the one it was originally on? Ideally it would be possible to actually prevent (at least for a period of time) a successful join to that network?
ZigBee joins when there are multiple overlapping networks and application messaging is to be used to ensure the correct network is used. In my situation, both networks are suitable for