XCTU Network Map icon changes from Coordinator to Router when encryption is enabled

XBee & XBee Gateway XBee - Zigbee
,
1

I am experiencing a consistent visualization issue in XCTU’s Network Viewer when enabling security on my Zigbee mesh (XBee3 modules) from the Digi Xbee Zigbee Mesh Kit.

The Setup:

  • Coordinator: CE=1, NJ =FF, AP=1, EE=1, EO=1, KY=[Secret Key].

  • Routers: CE=0, JV = 1, AP=1, EE=1, KY=[Matching Key].

The Issue: When EE (Encryption Enable) is set to 0 (unsecured), the XCTU Network Viewer correctly identifies the Coordinator with the “C” icon and the Routers with “R.”

However, as soon as I enable EE=1 on all modules and perform a network reset (NR1), the Network Viewer misidentifies the Coordinator as a Router.

  • The hardware behavior remains correct: the Coordinator’s MY address is still 0x0000.

  • Communication between nodes is successful (solid green LQI lines).

  • The “Role” only flips in the visual map once encryption is active.

Has anyone else seen this “Identity Swap” in XCTU when moving from unsecured to secured Zigbee 3.0? Is there a specific timeout or “Node Descriptor” setting I should adjust to ensure the Trust Center is identified correctly in the GUI?

2

Do you see this same issue in the XBee Studio application?

What version of firmware are you working?

3
  1. I do see the devices in XBee Studio, but they are not appearing in a mesh topology. Instead, they show up as individual nodes connected to the computer, with no visible association or link between the Coordinator and the Routers.
  2. I am using the latest firmware for the Digi XBee3 Zigbee 3.0 function set, which is version 1014.
4

Following up on this I now see the Mesh topology, better visualization within Xbee Studio Application. However its still reading the Coord as a router

5

This is where you will want to submit a Support case by going to either my.digi.com and logging in or by going to Contact Digi Technical Support | Digi International and opening a support case.