Not that I’m complaining. I love HA… It would just be really handy to be able to visualize the network using the officially supported Zwave integration.
Zwave JS doesn’t offer the ability to find this information out. Zwave JS UI makes a visualization from assumed data and is often incorrect. Simply put, this isn’t possible until Zwave JS adds the functionality.
1 Like
Thanks for highlighting the upstream issue, however, shouldn’t it stand as a “I should be able to but I cannot”. Just based on the current state of HA from an end user perspective? I used to have the functionality with the old Zwave using a script someone built.
That old functionality was wrong also 
. It just showed closest neighbors. Zwave has never had a proper “This is my routing map”.
Anyways, you can get this “closest neighbor” functionality right now using Zwave JS UI. But remember, the information is 100% useless.
I think getting the map of closest visible neighbor(s) would be valuable for troubleshooting in some instances. for instance I have a node that for some reason cannot see another node in the same room.
But just to clarify, the Zwave network connection map (or possible connection based on closest neighbor) unknowable as you cannot glean any information about it from HA via any method, because all the information in currently HA is useless for troubleshooting, so why bother visualizing it?
This won’t tell you that. That’s what you aren’t understanding. It’s a 100% useless graph. We need ZwaveJS to create a function that maps the routes to see that information.
All the information in HA is what would be used to make the map… so if that’s useless in HA then it would be useless in a map as well.
Just to put this into perspective. I have a solid Zwave Mesh. My graph using Zwave JS UI shows that every device is directly connected to the controller. I know that is not true because my controller is on one side of my house and I have devices on the opposite side.
Blockquote
This won’t tell you that. That’s what you aren’t understanding. It’s a 100% useless graph. We need ZwaveJS to create a function that maps the routes to see that information.
Asking questions is what leads to understanding. I now understand is that the data is there but ZwaveJS does not provide it.
One last question, if you have a moment. Is the Zwave JS to MQTT visualization, that I’ve seen postings about, similar in that the data on network map is not fit for any purpose? Just wondering if I should follow the standard replies of “you should use * to MQTT instead”…
The data is not there, Zwave Js has to come up with a way to generate the data in order to create the graphs. The data that we have from nodes is a neighboor’s list, that’s it. You can infer what the route might be, but it most likely isn’t the route that was taken.
It only shows you a pretty map of your network and it largely serves no purpose. It confuses everyone because they assume it’s the actual routes that the devices take. I don’t even look at the map.
There was a guy who recently spent 2 days trying to make his routes better using that map… he was not happy when we told him the map was not correct.
2 Likes
To add to What @petro said. Even though the map is nigh useless. ZWaveJS UI (Zwavejs2mqtt’s new name) is VERY useful for managing ZWave specific devices in a single console and offers many other features that Mae it well worth it. Highly recommend if it works in your installation…
…And I also ignore the map.
3 Likes