Troubleshooting latency to decrease delays

Hi, I'm aware some delay is inevitable. But I'm curious as to what is considered baseline. Mine is usually under 100ms, which is acceptable. However it is not consistent. Sometimes it can go up to 300-500ms and in some rare cases (happened 1-2 times for 3 months) it took more then a second, seemingly.

As of now I have around 10 devices all are within 10 meters from the hub. The observed delay happens between Aqara Opple buttons and Sonoff BasicZBR3 switches.

Can I do anything about that?

I may not be the best person to troubleshoot all aspects of this, but a few things I can contribute would be:

I would suggest you first understand where the delay is occurring, is it in the communications from the buttons to the HE hub, the HE hub to the switches, or is it in the operations of the app / drivers on the HE hub.

If it's in the communications with devices, then you should start to understand how the communications are occurring, i.e. if they are going through certain repeaters and what their performance is like.

If the delay is in apps or drivers on the HE hub, then you need to work through that with the developers, whether that be HE staff or Community developers. That said, load on the HE hub could also be a contributing factor.... So it may be worth understanding that as well. Given your comment about the infrequent nature of the slow response, this may be the place to start.

Hope this helps...

1 Like

Thanks for the replay. Can you point me towards some resources on debugging hubitat integrations?

In terms of performance of the hub in general, from the Logs page you can see Device Stats and App Stats to get an understanding of the devices and Apps that are consuming the most resources on the HE hubs, though there is some interpretation to be made here, it's not always as clear cut as it may seem.

In terms of Zigbee communications, again, with some interpretation, some details can be found here:

http:// << HE-Hub-IP >> /hub/zigbee/getChildAndRouteInfo

Others can normally comment more on this than me.

1 Like

In addition to the great points @sburke781 already provided, I might add that screening the past Logs tab following a delay event would give you a better understanding of what was going on in your hub, at the time the delay occurred. Bare in mind that you may not be able to see what an app or device was doing, as many have debug logging that needs to be enabled from within the respective app or device before anything shows in the Logs/past Logs.

1 Like