#ZHA Zigbee network painfully slow to respond to command's for months.

1 messages · Page 1 of 1 (latest)

proven pecan
#

Over the last few months, I've been having intermittent issues with Zigbee with HA. at least two/three times a day Zigbee devices (Remotes/lights) will be very slow to respond to commands.
Sometimes to 1-2 seconds, but sometimes much longer (5-10 seconds)

In the HA logs, I can see repeated 'Timeout Errors' (attached).

Most of the devices are Hue bulbs, along with Hue remotes. A small number of Ikea bulbs, a tiny number of Xiami door sensors as well as a single miliwave motion sensor.

This has been going on for quite a while and I've tried the following troubleshooting steps already:

Changing Wifi network to clear up Zigbee channels, as well as checking the channels nearby for the quietest options: (My Wifi is now on Channel 6/11) and Zigbee is configured for Channel 20.

Rebuilt the network from scratch, and migrated from Zigbee2MQTT to ZHA.

Replaced the Coordinator from a Zigbee Llama to a SLBZ-06

Rebuild HA from scratch (This seemed to fix the problem, for a short while but has started to reoccur)

I've checked the hardware HA is running on, and CPU/RAM usage is pratically nothing (12% usage) and its running on a
Dell OptiPlex 7040 Micro Mini PC, i5-6500T, 16GB RAM, 256GB SSD

I'm running out of ideas on what the issue is or how to fix it 😦

balmy lion
#

It looks like you have a bunch of clusters of devices and a huge gap in between each cluster. Is that accurate to your actual physical network? You can see a lot of devices with poor connection.

Also, its always possible to be certain devices. A troubleshooting tactic if you think it's a problem with the network is to bring the devices close to the hub, remove the device and readd it while you're close to the hub, and see if you still have the same issues. If you do, that probably indicates it's not an issue with your network.
(Also, in general you want to pair a device in the location where you plan on using it)

#

Another possibility is Network interference near the zigbee stick. In my old home I had my zigbee stick next to my Wi-Fi and a bunch of other Wireless Electronics, the biggest things that helped with my network stability were simply putting my stick on an extension cable and moving it a few feet away from the other devices. Changed the network from somewhat unreliable to Rock Solid

#

Assuming you don't have interference connections from neighbors, Zigbee channel 20 and WiFi channel 6 and 11 arent exactly the ideal scenario, as Zigbee channel 20 is getting interference from wider channels in the 6-11 range

proven pecan
#

Hi, Sorry Been distracted with other issues.. TRying to come back to this to pick it up again as the issue isnt going away. The network looks like this if I turn on live view . I've tried moving the Zigbee stick to different locations around my home without much success or change (A slight problem si that often the network is fine for hours at a time then will just stop responding to button-presses etc, then queue up all the actions and execut them all at once, at which point the network seems to return to normal)

#

The affected devices seem to be everything all at once, really, I'll opne a door or hit a light switch and nothing will happen, no other operations work for 15 seconds then it all comes back to life

#

I can try and move the channel but, I'll double check the configuration

#

It is a fairly big Zigbee network, each room has 3-5 Hue LED lights, battery powered remote + door sensor, then there is a miniwave usb powered moition sensor in 'most' rooms

proven pecan
#

Jus tto throw a bit more data into this, I've found a tool with my Unifi setup that does a RF scann. Shows on all AP's (two across the property) that Wifi Channel 10 (2447-2467Mhz) has the lowest noise out of all the channels, whichs is about Zigbee Channel 20 according to that Metageek webpage right? (Zigbee channel 20 - 2450Mhz)

#

Adn this is the nonsenes that shows up in the logs when the network is 'not responding correctly'

acoustic pond
#

So the nature of the issue is that the ZigBee devices do eventually respond, but it may be delayed? Do any of them just don't respond at all or drop off the network?

#

At 21:12 when the choking occurred, was HA doing anything particularly heavy? Eg. Processing some voice command or image recognition.

proven pecan
#

The seem to eventually respond, its usually 5-15 delay, then all the actions all execute in order (Lights on, off etc) I dont think I've seen devices drop off the network? at 21:12 nothing would have been happening we were cooking dinner so the system should have been pretty idle

balmy lion
#

for my part, not entirely sure what's going on. certainly could be a ha slowdown problem or a problem with the network. try turning on debug mode for ZHA, if its a coordinator/network problem maybe that will provide more info?

proven pecan
#

Hm, okay, I'll leave debug mode on for a few days see if I can catch the error in action

acoustic pond
#

Yeah judging from what you've tried, it is not a ZHA/Z2M issue, a coordinator hardware issue, a WiFi interference issue. It could be something in HA itself.

#

Do these delays only affect devices in a certain location, or random devices everywhere?

acoustic pond
#

Do they occur at specific time? When the delays occur, are you trying to control multiple ZigBee devices at the same time?

fluid void
#

Have you tried the scan feature on the SLZB dashboard? it shows the lowest energy channels. The ZHA integration recommended channel 20 but my scan shows 24 as the lowest energy channel.