# \[APP\]\[Pro\] Network Visualizer - See how your devices really reach each other, and where the signal struggles **URL:** \ **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:** 20\ **Page:** 4
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [September 25, 2026, 7:34pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/61 "2026-09-25T19:34:05Z")
Here’s a little background on the conflicts detection. I added detection for conflicting addresses in your Zigbee network, when a conflict is detected it will show this in the top bar, the indicator is clickable and it will highlight the conflicting devices ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/f/5f0d5262257e650101e2dacec5052de689cef90a.jpeg) When clicking on either device, it will show detailed information on the conflict: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/b/4b0c69ab62bb0b2d8142271ee62fb73c309714eb.png) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/9/49fd32da43aa7d6b4d213e1bd9fdd67edc427974.png) Clicking in ‘blank’ space or using the esc key will clear the selection. ---
**Author:** ![Arve\_Bjornerud](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arve_bjornerud/32/80977_2.png) [@Arve\_Bjornerud](https://community.homey.app/u/Arve_Bjornerud)\ **Post date:** [September 25, 2026, 7:36pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/62 "2026-09-25T19:36:57Z")
New version, v 1.3.1. I added a “dump” feature to the app in the bottom of the “Load” dialog: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/e/3ef83b2b70aadb56a5431a9215cc099a8232e1de.jpeg) It´s the little link in the bottom her ^ Please look over you data-dump before sharing, I don´t know how secrets are stored, so the wash during dumping might not catch all things you want to keep secret. ---
**Author:** ![Mike\_Nono](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@Mike\_Nono](https://community.homey.app/u/Mike_Nono)\ **Post date:** [September 25, 2026, 7:40pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/63 "2026-09-25T19:40:20Z")
> [@Drako74](#): > > Homey doesn’t return Thread node details like it does for Zigbee and Z-wave I think it some way to get the information from homey. But maybe we need some intel from ahtom 🙂 ---
**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 25, 2026, 8:10pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/65 "2026-09-25T20:10:52Z")
It won’t let me send it to you as an attachment (images only, and changing the extension doesn’t fool it) or as plain text (too many characters), and I doubt it would let me post it here either (not that I would) But I sent you a message… ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [September 26, 2026, 5:09am UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/66 "2026-09-26T05:09:13Z")
A route is a possible route (…) for sending messages to the network. Connected devices remember at least one device (either a router, or the controller itself) that it knows to send messages through. A binding is where two (or more) devices can send specific Zigbee commands to each other. For instance, a remote control bound to a light can tell that light to turn on, without anything (like a flow) in between. This doesn’t necessarily mean that the two devices also need to have a direct _route_ to each other. ---
**Author:** ![Arve\_Bjornerud](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arve_bjornerud/32/80977_2.png) [@Arve\_Bjornerud](https://community.homey.app/u/Arve_Bjornerud)\ **Post date:** [September 26, 2026, 7:52pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/67 "2026-09-26T19:52:22Z")
**Zigbee Visualizer is now Network Visualizer** I’ve renamed the app to **Network Visualizer**. The reason is that the App Store turned down Zigbee Visualizer: Athom said it was too close to an existing app, **Zigbee Insights** , and they don’t want two apps in the store doing the same job. So instead of staying a Zigbee-only tool, the app will grow to cover more of Homey’s networks. **Thread and Matter** are next, since Homey’s Web API exposes their mesh. **Z-Wave** is harder: the API response apps get is missing the data a correct graph needs, the neighbours and routes between devices. Homey’s own developer tools can read them, but apps don’t have permission to, so until Athom opens that up I can’t draw a correct Z-Wave map. The raw dump already asks for that data, so if a future Homey update allows it, the app will pick it up. **What you need to do:** the rename gave the app a new app ID, so Homey treats it as a separate app, and **Zigbee Visualizer won’t get any more updates**. To keep getting them, uninstall **Zigbee Visualizer** and install **Network Visualizer**. Nothing carries over from the old app: your snapshot history, saved dumps and settings stay behind. After installing, switch the Browser view and snapshots back on, and add the map widget to your dashboards again. Version 1.3.2 works the same as before, apart from the new name. Thanks to everyone who has tested it and sent dumps so far. If you’re on Thread or Matter, raw dumps from the Load dialog in the browser view are still very welcome. > **[Network Visualizer | Homey](https://homey.app/en-no/app/no.arvebjoe.network-visualizer/Network-Visualizer/test/)** > > See how your devices really reach each other, and where the signal struggles. ---
**Author:** ![Arve\_Bjornerud](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arve_bjornerud/32/80977_2.png) [@Arve\_Bjornerud](https://community.homey.app/u/Arve_Bjornerud)\ **Post date:** [September 26, 2026, 9:00pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/68 "2026-09-26T21:00:55Z")
**Network Visualizer 1.4.0: Thread & Matter and Z-Wave** Version 1.4.0 is out, and the app now draws more than Zigbee. There’s a network picker at the top of the settings page and the browser view, and in the widget’s settings. **Thread & Matter:** every Thread device with its route back to Homey and a quality grade on each link, from link quality and signal strength. Devices are named after your Matter devices in Homey, and Matter devices on Wi-Fi or Ethernet are shown too, straight from Homey. Snapshot history now covers Thread as well, with the Changes tab and route history per device. **Z-Wave:** every device, graded by how many of Homey’s messages got through. Homey doesn’t let apps read the Z-Wave routes, so each device is drawn straight from Homey for now. **I need your help:** I don’t have a Thread or Matter network myself. Everything on that map was built and tested from a network dump one of you kindly shared, so I’m hungry for feedback. Does your Thread map look right? Are devices in the right place, with the right names? Is anything missing or plain wrong? If something looks off, the easiest way to show me is a raw dump: switch on Browser view at the bottom of the settings page, open it, choose Load… and click “Download a raw dump of every network”. Network keys and other secrets are left out, but device names are in there, so have a look before you post it. Screenshots help too. Install or update here: [Network Visualizer | Homey](https://homey.app/en-no/app/no.arvebjoe.network-visualizer/Network-Visualizer/test/) ---
**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:** [September 26, 2026, 9:26pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/69 "2026-09-26T21:26:26Z")
It seems that the header is not fully displayed in Chrome on an iPad: ![IMG_3016](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/3/1399bbc8a9122bf988f51875fc13d33ea3e1615b.jpeg) ---
**Author:** ![Mike\_Nono](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@Mike\_Nono](https://community.homey.app/u/Mike_Nono)\ **Post date:** [September 26, 2026, 9:50pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/70 "2026-09-26T21:50:52Z")
It looks good but.. sorry to say but the thread/matter is not correct, but i can’t give any information. but Athom need to provide more info/intel how extract the information of the the thread/matter ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [September 27, 2026, 5:04am UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/71 "2026-09-27T05:04:20Z")
> [@Arve\_Bjornerud](#): > > and they don’t want two apps in the store doing the same job Meanwhile, there are at least 4 Tuya apps in the app store, 7 Yale apps, and if it suits Athom they will publish apps under their name that do the same as long-existing community apps 🤷🏼‍♂️ ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [September 27, 2026, 7:34am UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/72 "2026-09-27T07:34:52Z")
Hi @SunBeech, For the best experience, it is advised to use a browser on a computer. I wanted the information to be available in a (desktop) browser because the screensize of a mobile device just doesn’t cut it, that’s why I incorporated a webserver into the app. Imo development time is better spent on functionality to visualize the networks than adapting to mobile devices. ---
**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:** [September 27, 2026, 7:47am UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/73 "2026-09-27T07:47:39Z")
Yes, I agree: desktop provides the best experience. It was just an observation, as I was not sure whether the header was supposed to be swipable to make the hidden items visible. Thanks for your contribution to this neat app! 😀 👍. ---
**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\ **Post date:** [September 27, 2026, 8:38am UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/74 "2026-09-27T08:38:33Z")
> [@Arve\_Bjornerud](#): > > **Zigbee Insights** , and they don’t want two apps in the store doing the same job. Hahahaha Damn m8, do you know how many “duplicated” apps are in the store 🤣 Just check out timer-apps, VD-apps or logic-apps 😂 But to you: nice app! In the latest version it says something about Zwave, but it doesnt have zwave mapping it it yet right? At least i just installed the app and placed a widget, but only zigbee was showing (i have 2 zigbee devices, so no point for me in using that mapping). What does the latest changelog mean about adding zwave help? Edit: nevermind hahah, i should have first read the other posts 😉 ---
**Author:** ![Mike\_Nono](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@Mike\_Nono](https://community.homey.app/u/Mike_Nono)\ **Post date:** [September 27, 2026, 12:35pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/75 "2026-09-27T12:35:18Z")
The green and red one must be the same, but the green is normally in thread tools connected to device “köket” Like the red one is. But I have no idea what the red one is Also some devices are not directly connected to homey ![Visualizer](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/e/eec7102df849ca5464669eadc68be09c69e37684.jpeg) ---
**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 27, 2026, 1:34pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/76 "2026-09-27T13:34:48Z")
> [@Arie\_J\_Godschalk](#): > > In the latest version it says something about Zwave, but it doesnt have zwave mapping it it yet right? When you add the Widget to the dashboard you can select which network type to show. And you can add multiple Widgets, one to show each network type. ![IMG_7890](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/7/97d598813ecfcd77b27aba727db1b19be64846ca.jpeg) ![IMG_7891](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/4/e42f11788ec45fa5c4d832e84af2333e3cc170ec.png) ---
**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\ **Post date:** [September 27, 2026, 2:01pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/77 "2026-09-27T14:01:07Z")
> [@Drako74](#): > > When you add the Widget to the dashboard you can select which network type to show. Yeah thanks. After keeping reading i installed the new network app. Unfortuantly, its a shame it doesnt work the same for zwave, because i mainly have zwave devices and would love that mapping. @Doekse en @Emile could permission be added so zwave (node en networking) could be read the same way as zigbee is allowed to by app(developers)? ---
**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\ **Post date:** [September 27, 2026, 3:19pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/78 "2026-09-27T15:19:39Z")
I believe that should already be possible, @martijnpoppen has a script which does exactly that. ---
**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\ **Post date:** [September 27, 2026, 3:33pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/79 "2026-09-27T15:33:40Z")
> [@Doekse](#): > > I believe that should already be possible Well @Arve_Bjornerud , perhaps ask @martijnpoppen ? ---
**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\ **Post date:** [September 27, 2026, 6:30pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/80 "2026-09-27T18:30:23Z")
Zigbee: [[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) Zwave: [[HOW-TO][Pro][Cloud] - Z-Wave Route map](https://community.homey.app/t/how-to-pro-cloud-z-wave-route-map/105763) ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [September 27, 2026, 7:03pm UTC](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739/81 "2026-09-27T19:03:34Z")
Hi @Doekse, good to see you’re reading along and participating, and thanks @martijnpoppen for posting links to the scripts. Unfortunately, the script relies on `Homey.zwave.runCommand({ command: 'getNetworkTopology' })` but `runCommand` isn’t allowed from an app (Which is a good thing, there’re also commands like `factoryReset`…) So, Athom has to provide a method to retrieve the Z-Wave topology from an app before this is possible. [Previous page](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739.md?page=3) [Next page](https://community.homey.app/t/app-pro-network-visualizer-see-how-your-devices-really-reach-each-other-and-where-the-signal-struggles/159739.md?page=5)