How do I debug latency that happens sometimes

I have a C8 Pro, but this was happening on my C7 before.

Sometimes, things are slow, the hub is delayed in responding. Happened again last night.

At 7:30pm, two lights are supposed to go off, LivingLampLeft, and Buffet Cans.

In the logs from last night, I see the app turning off LivingLampLeft perfectly. - Simple Automation Rule 1.1, with both app events and logging on.
But, no app log for the Buffet Cans, just double checked, app logging is on - Simple Automation Rule 1.2, logging on, there is no option for app events in 1.2, it seems. And, I see the day before, that a good run doesn't show any app logs for this app either. Other SAR 1.2 rules ARE logging... Strange.

Because I was there at the time, and noticed that the Buffet Cans did not turn off at the same time as LivingLampLeft, I went over to the kitchen, and tried my most often noticed latency problem switch, a Zooz Zen32 Scene Controller, I pressed button 4, at 7:30.33. Then, nothing happened, so I pressed it again, 7 seconds later at 7:30:40. Then, 6 seconds later, lights started to go off, which is what is supposed to happen with button 4 scene. And, somewhere during that, the Buffet Cans turned off too (they are not in the scene, so that must be the app finally catching up). Seems that Buffet Cans is always about 33 seconds behind... Strange. I also see that the button 4 that I pushed twice, did everything twice, expected.

Any ideas on what's going on with my hubs that I get 7+ second latency - but only sometimes. Most of the time everything is very responsive.

Any other logs or info I can check, or turn on for next time?

Thanks!

Logs from 3/6:

dev:314 2024-03-06 07:30:48.783 Kitchen Counter was turned off
dev:316 2024-03-06 07:30:48.683 Dining Cans was turned off
dev:316 2024-03-06 07:30:48.682 Dining Cans was set to 0
dev:313 2024-03-06 07:30:48.536 Kitchen Pendants was turned off
dev:313 2024-03-06 07:30:48.535 Kitchen Pendants was set to 0
dev:313 2024-03-06 07:30:47.565 Kitchen Pendants was turned off
dev:313 2024-03-06 07:30:47.563 Kitchen Pendants was set to 0
dev:314 2024-03-06 07:30:47.098 Kitchen Counter was turned off
dev:451 2024-03-06 07:30:46.857 Buffet Cans was turned off
dev:451 2024-03-06 07:30:46.855 Buffet Cans was set to 0
dev:316 2024-03-06 07:30:46.640 Dining Cans was turned off
dev:316 2024-03-06 07:30:46.639 Dining Cans was set to 0
dev:318 2024-03-06 07:30:46.615 Cooking indicator off
dev:314 2024-03-06 07:30:46.563 Kitchen Counter was turned off
dev:314 2024-03-06 07:30:40.763 Kitchen Counter button 4 pushed
dev:314 2024-03-06 07:30:33.794 Kitchen Counter button 4 pushed
dev:47 2024-03-06 07:30:00.306 LivingLampLeft power is 0W
dev:47 2024-03-06 07:30:00.278 LivingLampLeft was turned off [digital]
app:83 2024-03-06 07:30:00.165 Turn On LivingLampLeft at sunset -45 anti-Turn On
app:581 2024-03-06 07:30:00.155 act: anti-Turn On & Set Level

Logs from 3/5:

dev:451 2024-03-05 07:30:34.819 Buffet Cans was turned off
dev:451 2024-03-05 07:30:34.817 Buffet Cans was set to 0
dev:47 2024-03-05 07:30:00.266 LivingLampLeft was turned off [digital]
dev:47 2024-03-05 07:30:00.257 LivingLampLeft power is 0W
app:83 2024-03-05 07:30:00.148 Turn On LivingLampLeft at sunset -45 anti-Turn On
app:581 2024-03-05 07:30:00.148 act: anti-Turn On & Set Level

Logs from 3/4:

dev:451 2024-03-04 07:30:33.095 Buffet Cans was turned off
dev:451 2024-03-04 07:30:33.094 Buffet Cans was set to 0
dev:47 2024-03-04 07:30:00.228 LivingLampLeft power is 0W
dev:47 2024-03-04 07:30:00.211 LivingLampLeft was turned off [digital]
app:581 2024-03-04 07:30:00.143 act: anti-Turn On & Set Level
app:83 2024-03-04 07:30:00.070 Turn On LivingLampLeft at sunset -45 anti-Turn On

One possibility is that your zwave network is slow or glitchy, or its the zigbee network, depending on the devices involved. Both is also possible too. There are lots of long threads to read about those problems. Some repeaters are better than others.

Power monitoring can be costly to zigbee and zwave throughput so if you are using that feature set the reporting time period to as far out as you can live with. Lots of threads with that advice too.

On the Devices page for the device is an Events button which lists the last few events for that device.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.