# xbee coordinators **URL:** \ **Category:** XBee & XBee Gateway\ **Tags:** xbee-api-mode, zigbee\ **Created:** [June 24, 2022, 5:56am UTC](https://forums.digi.com/t/xbee-coordinators/23131 "2022-06-24T05:56:57Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![nimbusgb](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@nimbusgb](https://forums.digi.com/u/nimbusgb)\ **Post date:** [June 24, 2022, 5:56am UTC](https://forums.digi.com/t/xbee-coordinators/23131/1 "2022-06-24T05:56:57Z")
I have a large mesh of s2c Xbee’s running zigbee ( currently most on 4061 software or the one preceding it ) I am having challenges with the mesh ‘breaking up’ and forming clusters of random meshes. Somehow I get a router transform into a co-ordinator and I see bunches of routerss jump across to the new meshes, leaving the ‘real’ mesh. We have tried varying approaches, the XBEE’s have a profile applied at build time and the embedded device they are connected to never does any AT configuration so I am convinced that the devices are not being asked to become co-ords. We do send out some remote AT messages from the central PC tied to all this but it is limited to ‘NI’ messages so I fail to see how that can become a co-ordinator enable message. Getting things back onto one mesh is a right pain too especially as the XBee’s have a resistance to co-ordinator swaps. It has to be done in a very distinct order or you end up with orphaned devices that you can’t get back in touch with without unplugging them and using a laptop and programming adaptor ( USB - XBEE ) What can I look for? How the hell are routers becoming co-ordinators. ---
**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\ **Post date:** [June 27, 2022, 7:56am UTC](https://forums.digi.com/t/xbee-coordinators/23131/2 "2022-06-27T07:56:37Z")
The ONLY way a router or any other node can become a coordinator is by setting the CE command either from the UART or from a remote AT command. There is no other way. Try setting the NW to a non 0 value. That will allow routers to perform a network reset on their own looking for the coordinator if they do not receive a message from the Coordinator after 3x NW value.