Need to visually manage Mesh-Z-wave network

[vtminhvt (VoThanhMinh(𝕄𝕀))]

-Although, there are tools|Repair Z-Wave network| to fix the z-wave network.
-I see, when making large systems need to visually manage this Mesh-Z-wave network.
-What do you think?

[Kjamsek]

Manually overriding the routing tables, if this is what you mean by saying “visually manage” the network, will only lead to problems down the line, UNLESS you are 100% sure of the routing that should take place.

On Z-Wave this isn’t really needed if, and i need to state this clearly, you include devices AFTER they have been placed into their final physical location. Each device can then “ping” it’s direct neighbors via NOP commands and report this to the central controller, resulting in a functioning mesh network since the controller knows which nodes are in direct range of eachother.

[kevin]

Some info here (you need to use a secondary controller like z-stick)…

FAQ: Is there a way to see the Zwave mesh network map?

That’s a standard topology map. The device ID should be the same is the “device network ID” on your SmartThings account, which you can see in the IDE. Remember that Z wave allows for dynamic routing, it’s not that there’s a single pathway so you’re not going to see lines the way you would if you were tracking a specific message. It’s just showing you which nodes can reach which other nodes in one hop. A blue square means the node for that row and the node for that column can communicate in one hop. A Red Square means they can’t. The white square is where the same device is in both the row and column. For example, node 3, a sensor, can only communicate with your hub. Node 23, which is a binary switch, has a bunch of routing choices: it can communicate in one hop with your hub, swit…