# Developers tool

**URL:** <https://community.homey.app/t/developers-tool/147537>\
**Category:** Questions & Help\
**Created:** [December 21, 2025, 5:38pm UTC](https://community.homey.app/t/developers-tool/147537 "2025-12-21T17:38:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lasse\_K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lasse_k/32/149831_2.png) [@Lasse\_K](https://community.homey.app/u/Lasse_K)\
**Post date:** [December 21, 2025, 5:38pm UTC](https://community.homey.app/t/developers-tool/147537/1 "2025-12-21T17:38:31Z")

</div>

I’ve upgraded from 2019 to 2023. Using developers tool when having 2019 I used to see the Zigbee path for each device. Using 2023 the path for each device is not there anymore Any chance of reverting back to the one with path visible inside developers tool still on 2023.

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [December 21, 2025, 5:40pm UTC](https://community.homey.app/t/developers-tool/147537/2 "2025-12-21T17:40:48Z")

</div>

The Zigbee route info is not available on the Homey Pro 2023 or newer models. That’s why the Zigbee section in the Developer Tools does not include that info.

---

<div class="post-metadata">

**Author:** ![Lasse\_K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lasse_k/32/149831_2.png) [@Lasse\_K](https://community.homey.app/u/Lasse_K)\
**Post date:** [December 21, 2025, 5:53pm UTC](https://community.homey.app/t/developers-tool/147537/3 "2025-12-21T17:53:10Z")

</div>

Ok, thanks. Any reason why it was taken out? I loved that feature.

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [December 21, 2025, 6:01pm UTC](https://community.homey.app/t/developers-tool/147537/4 "2025-12-21T18:01:32Z")

</div>

If I recall correctly, that information was unreliable. It also displayed the last known route, not necessarily the current route. Search this forum for more info.

---

<div class="post-metadata">

**Author:** ![Lasse\_K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lasse_k/32/149831_2.png) [@Lasse\_K](https://community.homey.app/u/Lasse_K)\
**Post date:** [December 21, 2025, 6:16pm UTC](https://community.homey.app/t/developers-tool/147537/5 "2025-12-21T18:16:39Z")

</div>

Ok, thanks for your help.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [December 21, 2025, 6:25pm UTC](https://community.homey.app/t/developers-tool/147537/6 "2025-12-21T18:25:44Z")

</div>

You can’t influence the used routes anyway, only by “forcing”: re-pair a device right next to it’s closest zigbee router.  
But, it isn’t static. When it decides to use an other route, it will → and it’s often not very logical to us. I’ve devices downstairs using a router upstairs which is connected to zigbee2mqtt downstairs 🤔

If you like stats and control, move your zigbee devices to zigbee2mqtt and be amazed (and ehm, yes you’ll have to rebuild your zigbee mesh from scratch).