# \[APP\]\[Pro\] Network Visualizer - See how your devices really reach each other, and where the signal struggles

**URL:** <https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739>\
**Category:** Apps\
**Tags:** app, community-app\
**Created:** [September 18, 2026, 6:58am UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739 "2026-09-18T06:58:38Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\
**Post date:** [September 18, 2026, 5:23pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/4 "2026-09-18T17:23:43Z")

</div>

This looks similar to what @martijnpoppen did here:

> [@\[HOW-TO\]\[Pro\]\[Cloud\] - Zigbee Route map (Homey Pro / Homey SHS / Homey Bridge)](https://community.homey.app/t/how-to-pro-cloud-zigbee-route-map-homey-pro-homey-shs-homey-bridge/104966):
>
> Hi, I saw this [thread](https://community.homey.app/t/mesh-map-of-zigbee-network/91010) and was inspired to create a script which can do this for you. I made 2 variants: [Zigbee Variant](https://community.homey.app/t/104966)[Zwave Variant](https://community.homey.app/t/105763) Instructions: Run this script in the [WebAPI playground](https://tools.developer.homey.app/tools/api-playground): (make sure to empty the text area first) const main = async function () { console.log("Starting main function..."); const zigbeeUpdate = await Homey.zigbee.runCommand({ command: 'UPDATE\_NODES' }).catch((err) =\> { console.error("Error updating Zigbee nodes:", err); }); const data = await H…

Are there specific reasons these need to live on GitHub, and couldn’t be made in to a Homey App, with a widget you could add to a Dashboard to show the map?

I quite like this app, but it doesn’t have a map widget, only a table showing device type and last seen time:

> **[Zigbee Insights | Homey](https://homey.app/en-gb/app/com.all.zigbee/Zigbee-Insights/)**
>
> Your whole Zigbee network at a glance.

Don’t get me wrong, this is helpful. But I would love to see an app that had these features combined, so you could create a Dashboard that would help when you had issues… but also just be cool for the inner geek that loves those sort of details.

 ![Zigbee debug](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/4/c4682c8ebc223c654f5a8d3de32ef91a2597257e.jpeg)

Would also be nice if like in the screenshot, it showed the Zigbee channel in a spectrum bar chart, but in grey in the background showed the WiFi channels that overlap (and maybe even which WiFi channel your Homey Pro/Bridge was using).

It baffles me why these aren’t standard features, either in the Homey web interface, or the developer tools interface. That table it provides is terrible when you’re trying to find faults or improve your network. Or am I asking too much of Homey?

EDIT:

Can anyone else answer this, as I’m at a loss… I bought a Homey Bridge to strengthen my Zigbee and Thread mesh networks, as it was advertised on the Athom web site as being able to do this. But for a while now, no matter how I view it (this script, the Zigbee Insights app, Homey’s dev tools) it shows the Bridge as not being connected. But it is added to my Homey Pro, and the device card shows as “Homey Bridge works properly and lets you connect with more devices”. Yet I have Zigbee end devices in that same room showing as weak signal. Is it just a fancy RGB paperweight, or is it just excluded from these tools somehow?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/8/78e8b4951fc5da1eed8cc705f73bf2c727564ec2.png)

---

_[View the full topic](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739)._
