# Best way to determine all nodes in a mesh network?

**URL:** <https://forums.digi.com/t/best-way-to-determine-all-nodes-in-a-mesh-network/19384>\
**Category:** XBee & XBee Gateway\
**Tags:** meshnetwork\
**Created:** [April 17, 2018, 6:47am UTC](https://forums.digi.com/t/best-way-to-determine-all-nodes-in-a-mesh-network/19384 "2018-04-17T06:47:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jackalope\_Bill](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@Jackalope\_Bill](https://forums.digi.com/u/Jackalope_Bill)\
**Post date:** [April 17, 2018, 6:47am UTC](https://forums.digi.com/t/best-way-to-determine-all-nodes-in-a-mesh-network/19384/1 "2018-04-17T06:47:40Z")

</div>

I am using XBee Pro Module - ZB Series 2 in API mode and for my application the number of routers and endpoints will change from use to use. It is my understanding that the coordinator finds all member nodes at initialization and then will periodically recheck. Can I access this list of members that the coordinator recognizes or do I need to broadcast an AT node discovery command to the entire network and then tally up a list of responding nodes? Ideally, I just want the NI parameter as I’ll be using it to describe system functionality associated with a particular node.

---

<div class="post-metadata">

**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:** [April 17, 2018, 9:39am UTC](https://forums.digi.com/t/best-way-to-determine-all-nodes-in-a-mesh-network/19384/2 "2018-04-17T09:39:27Z")

</div>

I think you have that a little backwards. The Coordinator establish a network. Then the routers and end devices join the coordinator. The only list that the coordinator keep track of is the end device list. That list can be queried using a ZDO command (Child table).

The other is best used by issuing a Node Discovery.