I'd like to get some guidance on diving into ZWave lock issues. I've read the whitepaper on ZWave FLiRS, but nothing in there is explaining the issues I'm seeing. I had some ghosts that I've now cleaned up. My hub is in a central location free of metal obstructions. My house has 30+ mains powered switches acting as repeaters. So, in short, I don't think I have any lingering network-wide issues.
Basically, they barely work. A few of the issues I notice:
Nightly rule to lock all doors rarely works. Very inconsistent on locking doors.
Commands to send new codes to the doors either take forever to sync or don't work at all
Commands sent from Hubitat to lock/unlock generally work once, but any follow-up actions are usually unresponsive.
I'm really confused as to what's going on here. Anyone experienced this or can otherwise offer some guidance?
I love it when I see RTT <10ms per hop at 40k. My 'zero hop' (aka direct) lock shows 2ms. The other is showing over 100 per hop. There's a refrigerator in direct line of sight, so I am willing to accept a couple of hops.
But, as @rlithgow1 offered, your Route changes are higher than what we'd like to see for a mesh described as: "I don't think I have any lingering network-wide issues." You have some unaccounted delays. This screen cap doesn't show device 0x12 which is the intermediate hop for your basement door, It seems the most likely source of delay, given what we can see. On the other hand, you have great Neighbor counts. One of them should be an excellent hop. The route changes imply that things that interfere are causing the routing to jump around between those neighbors.
Low PER, high Neighbor count and decent RSSI values are all positives. High RTT and high Route Changes are the negatives and suggest that the locks or the devices between, can't take advantage or the positives.
