I have all of a sudden starting having serious issues with my zigbee devices not responding that quickly, if at all, which would explain all these errors in the log:
2023-12-31 22:03:28.817 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 192, Status: TXStatus.SUCCESS
2023-12-31 22:03:40.088 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:6a sequence
2023-12-31 22:03:40.272 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 211, Status: TXStatus.SUCCESS
2023-12-31 22:03:40.356 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 211, Status: TXStatus.SUCCESS
2023-12-31 22:03:48.088 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 216, Status: TXStatus.SUCCESS
2023-12-31 22:03:52.551 WARNING (Thread-13) [pychromecast.socket_client] [Guest Room speaker(10.0.1.181):8009] Heartbeat timeout, resetting connection
2023-12-31 22:04:28.722 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:fe sequence
2023-12-31 22:04:28.835 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 10, Status: TXStatus.SUCCESS
2023-12-31 22:04:58.697 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:46 sequence
2023-12-31 22:04:58.807 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:50 sequence
2023-12-31 22:04:58.816 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 33, Status: TXStatus.SUCCESS
2023-12-31 22:05:08.659 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.air_freshener_plug_active_power is taking over 10 seconds
2023-12-31 22:05:08.659 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.commando_socket_summation_delivered is taking over 10 seconds
2023-12-31 22:05:08.659 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.tesla_charger_socket_power is taking over 10 seconds
2023-12-31 22:05:28.657 WARNING (MainThread) [homeassistant.components.sensor] Updating zha sensor took longer than the scheduled update interval 0:00:30
2023-12-31 22:05:58.658 WARNING (MainThread) [homeassistant.components.sensor] Updating zha sensor took longer than the scheduled update interval 0:00:30
But my house is detached and fairly remote with more than enough zigbee devices to relay communication. I also have the Conbee II on a 2M USB 2.0 extension cable, away from my WiFi router, that runs 2.4Ghz and 5Ghz separately (2.4Ghz on channel 1).
I haven’t changed any hardware, updated any software, or recently updated HA?? What gives rise to the sudden huge problem do you reckon??
Pretty common scenario , although i have hard to interpret your wifi-channel settings ( beside they looks (wrong/bad)
One. Common thing is, various brands Zigbee-coordinators chooses their Channels ( By default , some are changeable ) … So people have to choose ( Manually Setting ) in the Router, to avoid over lap … i.e a Router with Auto settings , will change wifi channels whenever it feels suitable, regardless of Zigbee-signals (obviously)
No not a common scenario I think. It worked perfect before.
As mentioned in the post of windowsdan, @ some point HA starting showing error logs and for example Zigbee lights are not responding or with a delay.
I think my WiFi settings are perfect on the 2.4GHz channels
Please contact me if you wan’t me to understand why not.
I stated, there was no problem before.
I don’t want to discuss my WiFi settings on this topic because it is a good setup for my house in combination with all the smart WiFi devices connected to it.
ok, i also never said that the errors was directly caused by your wifi-settings ( seems like you use all wifi channels )
so you have alot WiFi-zignals, on the 2.4ghz frequency , beside your zigbbe-devices, and all other household devices who runs/disturb the 2.4 frequency
So what happens when an i.e zigbee-router on your stable zigbee-network glitches or get turned of/unplugged ?, zigbee-devices(signals have to find another Route) first attempt failed because it choose a (bad) route, try again, another route, and so it keeps on ( depending upon how many routers you have ) and how many (hotspots) 2.4ghz choked/disturbed areas in your house
Not really, they tend to live their own life, maybe you can “bind” some devices to a certain “router” , but as it’s airborne signals, they will “flow” around, and hopefully not “choke” 1 specific router-device (they should regulate this them self, depending upon how many devices/connection they can handle)
Best would be to not have routers involved who get turned on and of, so when the zigbee network has stabilized it stays that way
PS: If i had major issues, i would try to wipe all, and then turn on the zigbee-routers first in order-distance from the controller, then enable the “children” and let them/integration choose the route … can take days/usage until this has stabilized
Fortunately i’ve have still not ended in this scenario, and im actually not feeling comfortable with the “topology” as i prefer to know which route each device have at any specific time/scenario ( yes you can call me control freak ) , so i’ve only have 2 who function as router, to reach/help 1st floor and basement devices, and im about to swap the basement with 868Mhz devices (Tapo) for the same reason
I have this exact same problem too. I think it started around the 2023.12 release but I’m not sure. It’s definitely within the last couple of months. I’ve also added some new devices so maybe it’s this.
Everything is working but I don’t like having hundreds of warnings.
No-one of you guys have reported which integration you are using( among other things ), i see “traces” of coordinators.( beside OP’s tag ( ZHA ) which you sometimes can read about in release notes.
So i believe you would get better “result” searching Topics related to your specific Integration
MQTT/ZHA whatever , but ofcause still have the basic understanding of Zigbee( weak signal in common ) in a crowded 2.4ghz environment
Some people tend to trow in more and more on this frequency, with no “common” sense … Bluetooth, Wifi, usb3 , Huge NAS, with 2-4 spinning disk , next to their Pi, with Bluetooth, and a USB dongle( 1 meter above ) for Zigbee … Yes i works fine ( running/occupying WIFI on ALL channels ) , until it doesn’t
Ethernet-connected Zigbee coordinators, is not much more expensive than others 10-15 euro/dollars, but imagine the convenience with the ability to place the zigbee-coordinator, basically where ever you want, and, is it cool with your TV connected to WIFI ? …nooo, not only is it a huge source of “disturbance”, it’s constant on, if you don’t turn of the power or plug, your tv will also use about 10-20W( wired tv, about 1-2W ), just for this purpose ! listening/waiting for “commands” requesting update-news, Apps updates etc … everything that can be wired, should be wired
( yes you can call me control freak ) , so i’ve only have 2 who function as router, to reach/help 1st floor and basement devices, and im about to swap the basement with 868Mhz devices (Tapo) for the same reason