# Zigbee Coordinator Short Address not 0x0000 after firmware update (XBee3 FW 1014)

**URL:** <https://forums.digi.com/t/zigbee-coordinator-short-address-not-0x0000-after-firmware-update-xbee3-fw-1014/37940>\
**Category:** XBee - Zigbee\
**Created:** [October 23, 2025, 1:31pm UTC](https://forums.digi.com/t/zigbee-coordinator-short-address-not-0x0000-after-firmware-update-xbee3-fw-1014/37940 "2025-10-23T13:31:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JIriarte](https://avatars.discourse-cdn.com/v4/letter/j/a4c791/32.png) [@JIriarte](https://forums.digi.com/u/JIriarte)\
**Post date:** [October 23, 2025, 1:31pm UTC](https://forums.digi.com/t/zigbee-coordinator-short-address-not-0x0000-after-firmware-update-xbee3-fw-1014/37940/1 "2025-10-23T13:31:05Z")

</div>

Hi everyone,

I’ve been using DIGI modules in Zigbee networks for many years, and one behavior I’ve always relied on is that the coordinator’s short address is 0x0000.

However, since updating the firmware of several XBee3 modules to version 1014, I’ve noticed that the coordinator often takes a different short address — not 0x0000 — which is causing issues in my network logic.

Here are the details:

Hardware version: 0x424C

Firmware version: 0x1014

Key configuration parameters:

ATCE = 1

ATID = 1

ATZS = 2

ATNJ = FF

ATEE = 1

ATEO = 0

Has anyone else experienced this behavior with FW 1014?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![JIriarte](https://avatars.discourse-cdn.com/v4/letter/j/a4c791/32.png) [@JIriarte](https://forums.digi.com/u/JIriarte)\
**Post date:** [October 23, 2025, 2:22pm UTC](https://forums.digi.com/t/zigbee-coordinator-short-address-not-0x0000-after-firmware-update-xbee3-fw-1014/37940/2 "2025-10-23T14:22:11Z")

</div>

Hi again,

Sorry, after further investigation, I’ve realized that the issue is not related to the firmware version after all. The unexpected short address assignment for the coordinator only occurs when I set **ATEO = 0** , meaning distributed Trust Center.  
Is that the expected behaviour?

---

<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:** [October 24, 2025, 11:43am UTC](https://forums.digi.com/t/zigbee-coordinator-short-address-not-0x0000-after-firmware-update-xbee3-fw-1014/37940/3 "2025-10-24T11:43:12Z")

</div>

Yes, that is the expected behavior.

---

<div class="post-metadata">

**Author:** ![JIriarte](https://avatars.discourse-cdn.com/v4/letter/j/a4c791/32.png) [@JIriarte](https://forums.digi.com/u/JIriarte)\
**Post date:** [October 24, 2025, 12:11pm UTC](https://forums.digi.com/t/zigbee-coordinator-short-address-not-0x0000-after-firmware-update-xbee3-fw-1014/37940/4 "2025-10-24T12:11:58Z")

</div>

Thanks for the quick reply.  
I had tried the same configuration many times on a ConnectPort X2, and the coordinator address was always 0. That’s what confused me. Does that mean the behavior of XBee3 and S2C differs when the coordinator is not acting as a centralized trust center?

---

<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:** [October 24, 2025, 12:14pm UTC](https://forums.digi.com/t/zigbee-coordinator-short-address-not-0x0000-after-firmware-update-xbee3-fw-1014/37940/5 "2025-10-24T12:14:52Z")

</div>

Yes it is. The simple reason is the central trust center function is different in the two Zigbee standards. The S2C is using the Zigbee PRO standard where by the XBee 3 is using the Zigbee 3.0 standard.