ZHA Zigbee deconz warnings

arkpoah · January 10, 2024, 11:20am

Hi

My Zigbee network is configured via ZHA on a Conbee2 controler for over 2 years and all worked perfectly.
Homeassistant is deployed on a raspberry 4 with Docker.

Since I upgraded to last 2023.11 release, some deconz warning appeared and sometimes I get few lags on Zigbee network.
Here are the errors :

homeassistant    | 2024-01-10 12:05:56.494 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:24 sequence
homeassistant    | 2024-01-10 12:05:56.503 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:25 sequence
homeassistant    | 2024-01-10 12:05:56.526 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:26 sequence
homeassistant    | 2024-01-10 12:05:56.598 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:2c sequence
homeassistant    | 2024-01-10 12:05:56.602 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 240, Status: TXStatus.SUCCESS
homeassistant    | 2024-01-10 12:05:56.625 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 240, Status: TXStatus.SUCCESS
homeassistant    | 2024-01-10 12:05:56.638 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:31 sequence
homeassistant    | 2024-01-10 12:06:06.469 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.prise_lave_linge_active_power is taking over 10 seconds
homeassistant    | 2024-01-10 12:06:26.466 WARNING (MainThread) [homeassistant.components.sensor] Updating zha sensor took longer than the scheduled update interval 0:00:30
homeassistant    | 2024-01-10 12:06:56.467 WARNING (MainThread) [homeassistant.components.sensor] Updating zha sensor took longer than the scheduled update interval 0:00:30
homeassistant    | 2024-01-10 12:07:26.507 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:52 sequence
homeassistant    | 2024-01-10 12:07:26.530 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:54 sequence
homeassistant    | 2024-01-10 12:07:26.554 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 252, Status: TXStatus.SUCCESS
homeassistant    | 2024-01-10 12:07:26.625 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 254, Status: TXStatus.SUCCESS
homeassistant    | 2024-01-10 12:07:26.657 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:5d sequence
homeassistant    | 2024-01-10 12:07:56.510 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:77 sequence
homeassistant    | 2024-01-10 12:07:56.560 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:7a sequence
homeassistant    | 2024-01-10 12:07:56.581 WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:7d sequence
homeassistant    | 2024-01-10 12:07:56.585 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 11, Status: TXStatus.SUCCESS
homeassistant    | 2024-01-10 12:08:06.473 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.prise_lave_vaisselle_active_power is taking over 10 seconds
homeassistant    | 2024-01-10 12:08:06.473 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.prise_lave_linge_active_power is taking over 10 seconds
homeassistant    | 2024-01-10 12:08:26.471 WARNING (MainThread) [homeassistant.components.sensor] Updating zha sensor took longer than the scheduled update interval 0:00:30
homeassistant    | 2024-01-10 12:08:56.472 WARNING (MainThread) [homeassistant.components.sensor] Updating zha sensor took longer than the scheduled update interval 0:00:30

Since I upgraded to last HA 2023.12 release, but nothing better.
Zigbee & Wifi channels are already configured to avoid interferences and I don’t see any changes in my configuration which can explains theses errors.

If anyone has suggestions, thx

marxkus · January 10, 2024, 6:36pm

I think the problem is the ConBee 2 stick. I have the same problems here.

I think SkyConnect Stick is better for ZHA or SonOff for 2MQTT. I am currently thinking about changing.

arkpoah · January 11, 2024, 10:05am

According this thread, I can confirm I get no more of theses warnings after 2024.1.2 upgrade.
Regarding the Conbee2 key, I also wonder, I will keep on eye it

marxkus · January 12, 2024, 8:33am

The same issue after installing 2024.1.2

Logger: zigpy_deconz.zigbee.application
Source: runner.py:188
First occurred: 11. Januar 2024 um 21:39:33 (1 occurrences)
Last logged: 11. Januar 2024 um 21:39:33

Unexpected transmit confirm for request id 204, Status: TXStatus.SUCCESS

woempiej · January 12, 2024, 7:52pm

Hi,

Yes I also caught 1 error in the log but, did you notice any delay or other problems with your setup regarding to the error?

marxkus · January 14, 2024, 1:06pm

No, but in my feelings the reaction time is sometimes not so gut.

marxkus · February 24, 2024, 11:23am

Hey Guys, i still have this problem with Conbee II and ZHA. There is this entry in my logs every day:

Logger: zigpy_deconz.zigbee.application
Source: runner.py:188
First occurred: 23. Februar 2024 um 20:12:15 (3 occurrences)
Last logged: 08:21:27
Unexpected transmit confirm for request id 122, Status: TXStatus.SUCCESS
Unexpected transmit confirm for request id 248, Status: TXStatus.SUCCESS
Unexpected transmit confirm for request id 7, Status: TXStatus.SUCCESS

Where is the problem? Can someone help me? Thx

On my Test PI with Hue Bridge I don’t have any issues

woempiej · February 26, 2024, 8:13pm

Is everyone using Philips Hue devices? I do

marxkus · February 28, 2024, 7:26am

I use some hue devices, too.

Hedda · April 9, 2024, 10:51am

At least some of those messages sounds related to this pull request for zigpy-deconz radio library:

github.com/zigpy/zigpy-deconz

Change log level to debug for unexpected transmit

zigpy:dev ← mbo18:patch-1

opened 08:43AM - 08 Apr 24 UTC

mbo18

+2 -2

Change log level for unexpected transmit to debug. I don’t really know why this …is useful for users. For example I have in my log multiple times per day: ``` Logger: zigpy_deconz.zigbee.application Source: runner.py:189 First occurred: 00:26:55 (3 occurrences) Last logged: 08:16:49 Unexpected transmit confirm for request id 11, Status: TXStatus.SUCCESS Unexpected transmit confirm for request id 175, Status: TXStatus.SUCCESS Unexpected transmit confirm for request id 163, Status: TXStatus.SUCCESS ``` Remark: it is not possible to filter these logs in HA with: ``` logger: default: warning logs: zigpy_deconz.zigbee.application: error ``` And I don’t know why.

Note! Regardless of setup and environment, to avoid errors and problems related to EMF interference (a.k.a. EMI/RMI), be sure to always use a long USB extension cable with good shirlding (either a USB 2.0 extension cable to any USB port or a USB 3.0 extension cable to a USB 2.0 port) to try to get the Zigbee Coordinator radio adapter as far away from possible sources of EMF interference (which other than WiFi, USB 3.0 ports and USB 3.x devices are infamous for being the source of), see → Zigbee networks: how to guide for avoiding interference + optimizing using Zigbee Router devices (repeaters/extenders) to get best possible range and coverage

PS: Off-topic but you should also understand that the radio chip used inside the ConBee II adapter is quite outdated and the firmware is relatively old as have not been getting any major updates for years, so you might want to consider replacing it with a newer more modern Zigbee Coordinator adapter. Suggest you check out this community guide → Zigbee buyer's guide

Summary:

If using ZHA integration buy/use a new Texas Instruments or Silicon Labs based USB adapter.
If use the Zigbee2MQTT software buy/use a new Texas Instruments based USB adapter.
If use deCONZ/Phoscon software buy/use the new ConBee III (ConBee 3) USB adapter.