How does this even happen?

[notamango]

This made me laugh, hysterically. This is the zwave node mesh path from the hub, it goes from the hub to node 71, then 59, then back to 71...

[aaiyar]

Possibly an SDK reporting glitch - just to confirm, have you applied the 7.17.1 radio update? A while ago I saw a route through a FLiRS device - which was also a reporting glitch.

You think you've seen some crazy z-wave routing? How about a non-repeater being used as a router?

While looking at my z-wave network using @tony.fleisher's app, I just noticed that a battery powered leak sensor was being used as a repeater for a Leviton outlet that I never use. [Screen Shot 2022-01-28 at 12.03.09] The route for device 0x04 indicates a 4-hop route with one of the hops being device 0x37 (the leak sensor). Here's the details for device 0x37, indicating it is functioning as a router (or at least the hub thinks it is functioning as a router). [Screen Shot 2022-01-28 at 12.02…

[notamango]

Yeah I don't have a zwave update button available on the zwave details screen. I verified with my zenstick that's the path, and sure enough, it reports there too. I'm going to remove 59, repair the mesh, and re-add it as it's just an aeon 6 repeater so I wouldn't have to update any rules, and I'll see where it goes from there.

[lcw731]

I had that happen a while ago. That time it was between 2 devices about 3 feet apart. I dont think i excluded anything, i just did a repair and it fixed it.