Node has 4 hops, but graph shows connection to node with only 1 hop?

[stephanvierkant]

I've changed the location of some of my devices and now my network is terribly slow. One device ('Bureau') even loses connection frequently. I've rebuild the 2network but that didn't make any change.

So I looked at my network graph:

Blue means 1 hop, green 2 hops, yellow 3 hops and orange 4 hops. I see 'Lamp' has only one hop, but Bureau has 4.

How does this work?

[robertsLando]

Blue means 1 hop, green 2 hops, yellow 3 hops and orange 4 hops. I see 'Lamp' has only one hop, but Bureau has 4.

Based on the graph seems Bureau is actually routing like: Bureau --> Lamp --> ??? (the one cropped under lamp) --> Keukenkastje --> Controller.

What I suggest is to change priority route manually to make Bureau to only use Lamp as Repeater so it will have one single hop instead of 3 in order to reach controller. You can do the same if needed with return route

[stephanvierkant]

You're right! But why does Bureau (3rd floor) take a detour, while Lamp (3rd floor, next to Bureau) is directly connected to the Controller (1st floor)?

I've tried to set a Priority route, but nothing happens (other than a successfull 'new route set' message)

Now it looks like this:

Lamp, Bureau Anouk and Bureau Stephan are on the 3rd floor, Keukenkastje and Controller are on the first floor. Why doesn't it use any of the many nodes on the 2nd floor? I've got 22 Z-Wave devices well-distributed in my house, so I expect a stronger network.

The only think I can think of: Bureau (2x) and Keukenkastje are all Greenwave nodes, which are not Z-Wave Plus devices.

[robertsLando]

But why does Bureau (3rd floor) take a detour, while Lamp (3rd floor, next to Bureau) is directly connected to the Controller (1st floor)?

Explaining why the zwave network decides to do this is hard, we can only make some guess, mesh is automatically handled by the protocol and sometimes it is known to do some weird thing like this. This is why we added the possibility to customize priority routes so you can override default ones assigned by protocol. Be aware that calling "rebuild routes" against that node will cause it to loose all the priority routes you added

[robertsLando]

I've tried to set a Priority route, but nothing happens (other than a successfull 'new route set' message)

You have set a priorirty RETURN ROUTE, you should set also the other above that (that is the most important one)

For reference: priority route is the route from controller to node, the return route is the route packets follow from node to the controller