Future of the Network Map

[Botched1]

Are there any plans to update/change the network map? On large networks it really isn't very useful as you can either see only small parts of the mesh, or if zoomed out to see the whole thing then you can't read any of the node text.

Example - Here is my network of 98 nodes, not a very useful graph. A table view may be better for large networks, or maybe a more traditional node drawing like the one in the node-red zwavejs2mqtt nodes.

[robertsLando]

That's the result of another question where everyone has expose their idea of network map, I'm open to suggestions but I would like to have the final solution and not an alternative to it

[kpine]

Maybe this is why the simple matrix topology seems to be popular (PC-Controller, Hubitat, Homeseer, SmartThings?). It communicates what the current graph is really showing, that is just the node neighbors, in a simple fashion. It also scales better for large networks.

@robertsLando In case you forgot about it, the same subject was discussed in quite detail in #384.

[robertsLando]

Yep exactly, that's the issue I was referencing in my first answer :) Seems that the actual implementation was the most voted but it doesn't fit very well for large networks

[blhoward2]

What about just allowing the user to filter by location and other criteria, then display those and their connections? There really isn't a need to view the entire network at once if it's unreadable.

Or go with a grid...though I find that matrix garish.

Something like:
Node -> hop -> hop ->controller RSSI etc. in a row and don't try to draw a map at all.

[AlCalzone]

I'm still working on it but if we don't show all neighbor relations but rather the routes from and to the controller, the mesh view might be usable.

[robertsLando]

I personally like @blhoward2 idea about filtering nodes in the mesh