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
When clicking on either device, it will show detailed information on the conflict:
Clicking in ‘blank’ space or using the esc key will clear the selection.
I think it some way to get the information from homey.
But maybe we need some intel from ahtom 
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…
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.
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 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
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
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 
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.
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! 
.
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 
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)?
I believe that should already be possible, @martijnpoppen has a script which does exactly that.
Well @Arve_Bjornerud , perhaps ask @martijnpoppen ?
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.
