I was told that zwave has a hop limit of 4. But after moving my hub location, I found a route going 5 hops. The device can still be controlled, but attempts at repairing just says device unreachable. Power-cycling doesn't help. This is not the first time I saw something like this, but previous times the issue resolved itself after a while. Just wondering what's going on and how long I should wait for it to fix itself.
that's a 4 hop
The reality is.. ZWave is source routed.. meaning the Hub sends a packe with the hops predefined. There is a source nodeID, and a destination nodeID with 4 "slots" for hops.
So in your case... 1A, 67, 6E and 74 are the nodeIDs that fill up the 4 possible slots.
3 Likes
The route is still kind of weird though. There's a direct route from 01 - > 74. But this one bounced around before reaching 74.
1 Like
1 Like
This all happens at the SDK layer.. All we do here is report what the SDK is telling us.
1 Like
Hey, you guys are alliance members. Go the them the 7.xx routing is wack, and that they should fix it. 
4 Likes
Do I cross my fingers and wait for it to fix itself or is there a way to force a re-route?
If it’s z-wave plus it will eventually find another route.. But you can repair the node and it will most likely update
Since repair failed I guess I just have to wait?
Hey looks like it's fixing itself as I type. I guess the waiting period is about a day or so.
