Z-wave latency after C7 upgrade to C8 pro

🎬 Get Started Using C-8 Pro
1

After moving from C7 to C8 pro I'm seeing high latency to my two z wave devices, e.g. this is a dome siren.

I sent a beep command and it took 8 seconds for the Sirens to react. In the z-wav diagram, I see a loop from the hub to itself (don't know if it was there before).

dev:692024-10-12 14:18:26.031infoseqNo: 187, routeChanged: false, transmissionTime: 129ms, repeaters: None, rssi: [-71 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1
dev:692024-10-12 14:18:24.728infoseqNo: 187, routeChanged: false, transmissionTime: 147ms, repeaters: None
dev:692024-10-12 14:18:24.527infoseqNo: 186, routeChanged: false, transmissionTime: 147ms, repeaters: None, rssi: [-71 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1
dev:692024-10-12 14:18:23.124infoseqNo: 186, routeChanged: false, transmissionTime: 110ms, repeaters: None
dev:692024-10-12 14:18:22.915infoseqNo: 185, routeChanged: false, transmissionTime: 110ms, repeaters: None, rssi: [-71 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1
dev:692024-10-12 14:18:14.294infoseqNo: 185, routeChanged: false, transmissionTime: 63ms, repeaters: None
2

How long after moving? It can take 3 to 5 days for the mesh to settle after migration.

3

One day after, but I only have two z-wave devices, both in LOS of the hub. According to the mesh graph, they are directly connected.

4

Assuming you did a hub replacement, if only two devices, I would remove and re-add them.

5

One of them is a Schlage lock that really hates the pairing process. And it would be a good occasion to squash migration bugs anyways. Another interesting thing is that the region is set to US-LR and if I try to change US, it goes back to US-LR.

6

Well, I decided to bite the bullet and try to remove and re-add . It took several times to exclude the dome siren (which, of course, also deletes the device :frowning: ) . However, re-adding it doesn’t work, the status is stuck on “found a device, initializing”. But then it just fails. I tried keeping the siren at different distances from the hub but it didn’t change a thing.

But then, there are two entries for the Siren now under the z-wave radio details, associated to previously existing z-wave devices that were unconnected but still in the device table. My fault for not having removed unused devices. The “loop” in the graph also disappeared.

Anyways, I removed the ghost siren device and I now only have one, but the latency didn’t improve a bit. Interestingly, the device graph/topology still show the extra device, but a reboot fixed that, but not the latency.

The lock is also having an hard time reporting the open/closed status back to the hub: when I lock/unlock manually, it takes several seconds for the hub UI to react, and sometimes it’s not reported at all.

I guess my next best option is to go back to the C7 and have Amazon replace the hub, maybe it’s just faulty.

7

Before you do that, could you please send me a private message so we can check out its engineering log to confirm that replacing the hub might help.

1 Like
8

This is starting to sound awfully similar to the documented problems the C8 has with PoE splitters which provide unstable voltages.

1 Like
9

Not using POE but can certainly try a no power reboot.

1 Like
10

I would also try swapping the antennas in case one is defective. And do as Bobby asked with sending him the hub ID so they can check the logs.

2 Likes
11

The no power reboot seems to have solved the issue (fingers crossed), thanks! I would have never guessed it. Maybe an option could be added to reboot the radio too.

Latency is back in the 1-2 sec range and updates from the lock are ~1 sec.

12

Topology is still fishy:
0B is the lock, 0D the siren
image

13

According to that the lock has no neighbors. It may re-discover them in the next couple of days. You could try doing a repair on it (if FLIRS locks let you do repairs).

What does the route show for the lock on the z-wave details?

14

I tried a repair before, but got an error message. Trying again now.

Stage: Repair Running - Group: 1
Z-Wave Node 0B: Repair timed out updating neighbors
Failed Nodes: 0B

image
image3908Ă—580 188 KB

15

Its direct connected and working, so I would not worry about the topology or repair too much.

Test physical activations on the device and then also from the hub, if both work and report status back to the hub you are good to go.

1 Like
16

Mine seems to...if he did the repair I suspect he'd want to ensure it's awake by doing an unlock/lock from the device page and then hit the Repair button on the Z-Wave Details page.

image
image1150Ă—128 17.3 KB

Oops...just saw your follow-up, Jeff.

17

Tried both ways but repair still fails. Status is reported correctly but commands from the hub are not getting to the devices anymore. I've been a bit busy, will try another reboot tomorrow. Maybe different fw on the lock.

18

How do neighbors look at this point? Any change?

19

Not just reboot, shut down and unplug for 30 seconds then re-plug.
That restarts the radio.

2 Likes
21

No changes, same as before.