ZHA delays with Tuya mmWave sensors #107200

a-d-r-i-a-n-d · 2024-01-04T23:54:52Z

The problem

Since I've upgraded to 2024.1.0 my ZigBee devices (lights, switches, fans etc) are having a few seconds/minutes delay in responding to commands. I have tried to restore to previous versions but the issue still persist, no matter the version I am restoring to. I have also tried restarting in safe mode, but it didn't helped. Any help is much appreciated!

What version of Home Assistant Core has the issue?

core-2024.1.0

What was the last working version of Home Assistant Core?

core-2023.12.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

config_entry-zha-1122b1901b65684e9e9a05c89bd2a54d.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.zha.core.cluster_handlers
Source: components/zha/core/cluster_handlers/__init__.py:537
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 23:36:04 (7 occurrences)
Last logged: 23:40:47

[0xEA69:1:0x0702]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0xEA69:1:0x0b04]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0x85AF:1:0x0702]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0x85AF:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0x85AF:1:0x0b04]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]

Additional information

System Information

version	core-2024.1.0
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.6
os_name	Linux
os_version	6.1.63-haos
arch	x86_64
timezone	Europe/London
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4955
Installed Version	1.33.0
Stage	running
Available Repositories	1371
Downloaded Repositories	7
HACS Data	ok

Home Assistant Cloud

logged_in	true
subscription_expiration	22 January 2024 at 00:00
relayer_connected	true
relayer_region	eu-central-1
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	false
remote_server	eu-central-1-9.ui.nabu.casa
certificate_status	ready
instance_id	8bf80b83acdc431081381385ed2692e2
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 11.2
update_channel	stable
supervisor_version	supervisor-2023.12.1
agent_version	1.6.0
docker_version	24.0.7
disk_total	58.0 GB
disk_used	12.2 GB
healthy	true
supported	true
board	generic-x86-64
supervisor_api	ok
version_api	ok
installed_addons	EMQX (0.3.0), Samba share (12.2.0), Studio Code Server (5.14.2), openWakeWord (1.8.2), Advanced SSH & Web Terminal (17.0.1)

Dashboards

dashboards	2
resources	1
views	12
mode	storage

MercedesME 2020

websocket_connection_state	connected
api_endpoint_reachable	ok

Recorder

oldest_recorder_run	21 December 2023 at 17:55
current_recorder_run	4 January 2024 at 23:22
estimated_db_size	308.77 MiB
database_engine	sqlite
database_version	3.41.2

home-assistant · 2024-01-04T23:54:58Z

Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

zha documentation
zha source
_{^{(message by IssueLinks)}}

puddly · 2024-01-04T23:56:56Z

I have tried to restore to previous versions but the issue still persist, no matter the version I am restoring to.

This sounds like an environmental problem.

Is your coordinator on a USB extension cable and away from 2.4GHz interference sources such as any USB 3.0 port or device, SSD, etc.?

a-d-r-i-a-n-d · 2024-01-05T00:15:27Z

Hi @puddly ,

Thanks for getting back so quick. Yes it is. I have 95 Zigbee devices connected and never had any issues in years.

puddly · 2024-01-05T00:19:09Z

I have 95 Zigbee devices connected and never had any issues in years.

If downgrading doesn't change anything, it's not a software problem. Your debug log says that channel 15 has a utilization of 86%, which is probably why you're having delays. Something in your environment changed recently and is causing noise and interference. It may have been neighbors.

If you are 100% certain no nearby devices could be interfering, change the ZHA channel from the configuration page. Leave the channel selection dialog on Auto so that ZHA picks the best channel for you (likely 20):

a-d-r-i-a-n-d · 2024-01-05T00:24:53Z

Thanks, will change the channel as per your advice. Does this change require commissioning the devices again?

a-d-r-i-a-n-d · 2024-01-05T00:48:41Z

I tried several times to change the channel but the blue wheel keeps spinning and no changes are applied, even after reboot it's still 15.

puddly · 2024-01-05T00:49:26Z

Changing the channel takes about a minute. How long did you wait?

a-d-r-i-a-n-d · 2024-01-05T00:57:01Z

I've had to unplug the coordinator and plug back in, after that the change has been applied. The channel is now 25. Here are some errors I see in the logs:

Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:610
Integration: Sensor (documentation, issues)
First occurred: 00:53:13 (26 occurrences)
Last logged: 00:53:13

Platform zha does not generate unique IDs. ID a4:c1:38:b5:e0:e0:f7:97-1-2820-rms_voltage already exists - ignoring sensor.guest_bedroom_trv_voltage
Platform zha does not generate unique IDs. ID a4:c1:38:b5:e0:e0:f7:97-1-1794-summation_delivered already exists - ignoring sensor.guest_bedroom_trv_summation_delivered
Platform zha does not generate unique IDs. ID a4:c1:38:d5:3d:87:92:f3-1-2820-rms_current already exists - ignoring sensor.master_bedroom_trv_current
Platform zha does not generate unique IDs. ID a4:c1:38:d5:3d:87:92:f3-1-2820-rms_voltage already exists - ignoring sensor.master_bedroom_trv_voltage
Platform zha does not generate unique IDs. ID a4:c1:38:d5:3d:87:92:f3-1-1794-summation_delivered already exists - ignoring sensor.master_bedroom_trv_summation_delivered

and

Logger: zigpy.zcl
Source: runner.py:188
First occurred: 00:51:55 (11219 occurrences)
Last logged: 00:53:14

[0xBCE4:1:0xef00] Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/zigpy/zcl/__init__.py", line 411, in reply return await self._endpoint.reply( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/endpoint.py", line 278, in reply return await self.device.reply( ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 483, in reply return await self.request( ^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 317, in request await send_request File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 833, in request await self.send_packet( File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 868, in send_packet status, _ = await self._ezsp.sendUnicast( ^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'sendUnicast'
[0x61BF:1:0xef00] Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/zigpy/zcl/__init__.py", line 411, in reply return await self._endpoint.reply( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/endpoint.py", line 278, in reply return await self.device.reply( ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 483, in reply return await self.request( ^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 317, in request await send_request File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 833, in request await self.send_packet( File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 868, in send_packet status, _ = await self._ezsp.sendUnicast( ^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'sendUnicast'
[0x07A8:1:0xef00] Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/zigpy/zcl/__init__.py", line 411, in reply return await self._endpoint.reply( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/endpoint.py", line 278, in reply return await self.device.reply( ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 483, in reply return await self.request( ^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 317, in request await send_request File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 833, in request await self.send_packet( File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 868, in send_packet status, _ = await self._ezsp.sendUnicast( ^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'sendUnicast'
[0x5289:1:0xef00] Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/zigpy/zcl/__init__.py", line 411, in reply return await self._endpoint.reply( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/endpoint.py", line 278, in reply return await self.device.reply( ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 483, in reply return await self.request( ^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 317, in request await send_request File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 833, in request await self.send_packet( File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 868, in send_packet status, _ = await self._ezsp.sendUnicast( ^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'sendUnicast'
[0xE160:1:0xe001] Unknown cluster command 225 b'\n\xfc\x00*-;\x00\x00\x00:\x00\x00\x009\x00\x00\x008\x00\x00\x006\x00\x00\x004\x00\x00\x002\x00\x00\x000\x00\x00\x00/\x00\x00\x00.\x00\x00\x00\x01'

a-d-r-i-a-n-d · 2024-01-05T00:57:45Z

Changing the channel takes about a minute. How long did you wait?

Much more than that.

a-d-r-i-a-n-d · 2024-01-05T01:09:06Z

Utilization on channel 15 in the past has always been between 80% - 90% and it was working just fine. It looks like on channel 25 has been reduced to 78.25% but still having the same delay issue.

Logger: zigpy.application
Source: components/zha/core/gateway.py:211
First occurred: 01:03:47 (2 occurrences)
Last logged: 01:03:47

Zigbee channel 25 utilization is 78.25%!
If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.

a-d-r-i-a-n-d · 2024-01-05T01:24:43Z

Now is down to 75.96%! by repositioning the coordinator. Issue still persist so if you have other ideas please let me know.

ChristophCaina · 2024-01-05T05:28:28Z

honestly, I am facing similar issues for a couple of days now...
For me, everything seemed to start on the day, two things have changed:

Installed 2024.1. beta 0b0
Paired another 2.4GHz device which is not using the zigbee protocoll, but working on the default channel 15 (afaik)

The issues became more worse each day - until nothing has worked anymore - resulting in a complete rebuild of the Network and switching to Channel 25.

Now, I have a feeling, that the issues slowly comming back... right now, most devices seem to respond, but I am already getting warnings in the logs as you have shared... Zigbee channel utilization is pretty high, devices do not respond (right now, only one...)

I need to investigate into this further over the weekend, because right now I have some ideas what might cause this - but need to change the location of some devices and monitor the behave after such changes...

Comming back to your topic:

Has something changed on your network?
Did you add another Wireless device?
is there a particular device responding slow? or are all of them affected?

If it is one device in particular, you can try to remove this one - to see, if it could be a defect on the device itself...

marc4s · 2024-01-05T08:44:13Z

same issue here since 2024.1
NO environment changes!

after a full reboot of HAOS it is lightning-fast but is getting slower and slower after a few minutes . after some hjours horrible slow

a-d-r-i-a-n-d · 2024-01-05T09:26:58Z

Current usb extension cable is only 2 meters long so have ordered a 5 meters which should arrive today. I'll report later if any improvements but I doubt there are environment changes.

frank777777 · 2024-01-05T09:28:35Z

SAme issues here . I bought a 2m cable ( from 1m ) .. let' see arrive tomorrow

marc4s · 2024-01-05T09:45:29Z

downgrading to last working 2023.12.4 "fixed" it for me

frank777777 · 2024-01-05T09:49:36Z

can you confirm , is not delays all zigbees devices right? .. only smartplug for me

a-d-r-i-a-n-d · 2024-01-05T10:08:06Z

downgrading to last working 2023.12.4 "fixed" it for me

  OS Version:               Home Assistant OS 11.3
  Home Assistant Core:      2024.1.0

  Home Assistant URL:       http://homeassistant.local:8123
  Observer URL:             http://homeassistant.local:4357
➜  ~ ha core update --version=2023.12.4
Processing... Done.

Command completed successfully.

This downgrade using the command ha core update --version=2023.12.4 seems to have fix it for me also. To mention that in the first 3 minutes after any reboot, the delay is still there, but after that, every command is executed instantly, as it should.

marmolak · 2024-01-05T13:39:48Z

Hi. Interesting.
My zigbee network is totally down after upgrade to 2024.1.0.

I opened discussion here:
https://community.home-assistant.io/t/after-upgrade-to-2024-1-0-zigbee-is-gone-with-failed-to-send-request-failed-to-enqueue-message-after-3-attempts-emberstatus-no-buffers-24/666757/

tanerpaca · 2024-01-05T13:42:47Z

I have had issues with ZHA after the upgrade to 2024.1.0 as well. In my case it wasn't just a delay but commands were timing out and I was not able to control the lights.
~~Downgrading to 2023.12.4 solved the issue.~~

Edit: I was too quick to confirm 2023.12.4 was the solution. I have downgraded to 2023.12.3 and after almost a day, no issues. So this seems to be the good version. I have seen in the release notes of 2023.12.4 a version bump update of ZHA, that may be the culprit.

This seems to be the latest ZHA change until today: #106147

marmolak · 2024-01-05T13:46:22Z

Naive bug against zigpy is here:
zigpy/zigpy#1315

frank777777 · 2024-01-05T16:32:01Z

update : Downgrading to 2023.12.4 solved the issue. IS NOT solving the issue ( on me ) . worked perfect for couple of minutes , and 7/9 interaction , then delay are back again .
:(

frank777777 · 2024-01-05T17:26:28Z

update : Downgrading to 2023.12.3 solved the issue.

marmolak · 2024-01-05T18:59:57Z

Update to 2024.1.1 doesn't help :(.

merdok · 2024-01-05T20:38:34Z

Also having quite some issues with Zigbee devices since 2023.12.4. Last stable working is 2023.12.3, so i guess it must have been a change introduced in between that.

christabone · 2024-01-06T01:23:26Z

Same here. Issues with Zigbee since 2024.1.0. I went quickly from 2023.12.4 to 2024.1.0 so I'm not sure whether 2023.12.4 had issues as well. Identical symptoms to other people who've posted here.

wouterjdb · 2024-03-31T07:41:20Z

So has has this work-around been working for you so far with two separate Zigbee networks?

frank777777 · 2024-03-31T08:06:40Z

Hi, my experience: works with two networks. (ZMA; Z2M) .
Btw . I can see. Radar network is jammed . And DB too .

frank777777 · 2024-03-31T08:21:41Z

BTW. I wonder if someone can help :
Id like to disable/deactivate via an automation the radar sensor. So to have radar sensors only on night time .. (there is no this status: on tuya sensors .. i tried deactivate , disable , switch off .. nothing works ) .. any guess ?

tabrisnet · 2024-03-31T21:22:02Z

So has has this work-around been working for you so far with two separate Zigbee networks?

seems to be stable for the last week. was just about to upgrade HA Core to 2024.3.

Prior to this, every device would drop out for a few seconds to a minute regularly; in addition it would periodically just hang completely, needing a restart of the coordinator and reload.
I'm not convinced the second problem is gone, it wasn't regular at all.
But the problem from this bug? I think it's fixed for me.

ftr, zigbee IDs of what I moved. Not clear that all of them had to be moved, but all but one were in the master bedroom.

mmWave sensors

_TZE204_ztc6ggyl - this needed a custom quirk
_TZE200_v6ossqfy - this did as well
aqara FP1 - lumi.motion.ac01

Not mmWave

_TZ3210_onejz0gt - an LED strip controller
_TZ3000_nzkqcvvs - a smart plug w/o power monitoring
_TZE200_yojqa8xn - a combustible gas sensor - this was in the basement, and it never worked with ZHA

disruptivepatternmaterial · 2024-04-01T01:49:21Z

Oh I didnt realize there was a question of it 2 zigbee nets would work...that is what I did. I have one one a rasp pi running HA from back in December for all the Tuya devices and the main zigbee net on my normal HA server and they are connected with HA remote. It works perfectly. I guess it can just stay that way indefinitely. That is until I replace all the tuya stuff...which I am slowly doing, but they are so thin and compact it is really a shame.

wouterjdb · 2024-04-04T16:37:57Z

So has has this work-around been working for you so far with two separate Zigbee networks?

seems to be stable for the last week. was just about to upgrade HA Core to 2024.3.

Prior to this, every device would drop out for a few seconds to a minute regularly; in addition it would periodically just hang completely, needing a restart of the coordinator and reload. I'm not convinced the second problem is gone, it wasn't regular at all. But the problem from this bug? I think it's fixed for me.

ftr, zigbee IDs of what I moved. Not clear that all of them had to be moved, but all but one were in the master bedroom.

mmWave sensors

_TZE204_ztc6ggyl - this needed a custom quirk

_TZE200_v6ossqfy - this did as well

aqara FP1 - lumi.motion.ac01

Not mmWave

_TZ3210_onejz0gt - an LED strip controller

_TZ3000_nzkqcvvs - a smart plug w/o power monitoring

_TZE200_yojqa8xn - a combustible gas sensor - this was in the basement, and it never worked with ZHA

Good to see that that work-around is plausible. Though, I do still cross my fingers that an easier solution could be created. Just sorted the open issues on the number of comments and this one is rather "popular". (+1 now 👍 )

tabrisnet · 2024-04-04T16:45:55Z

Oh I didnt realize there was a question of it 2 zigbee nets would work...that is what I did. I have one one a rasp pi running HA from back in December for all the Tuya devices and the main zigbee net on my normal HA server and they are connected with HA remote. It works perfectly. I guess it can just stay that way indefinitely. That is until I replace all the tuya stuff...which I am slowly doing, but they are so thin and compact it is really a shame.

I think the question re feasibility was how does Z2M avoid the same overload? Does it have the same bug ZHA used to have? Or does it behave better and that better behaviour could be brought to ZHA.

pgroene · 2024-04-04T18:10:03Z

I do not think a work around is having to ZigBee networks. If that is the case, I would move away from ZHA and make one new MQTT network. I have to many devices to replace them. In the end MQTT zigbee should have the same issue and a bug that does not send the acknowledgements. Or there is a perf issue that is blocking how fast the messages can be processed in ZHA itself.

tabrisnet · 2024-04-04T19:11:43Z

I clearly have not migrated my entire zigbee network. and the fact that I chose a different channel may also be enough of a difference as to not be comparing apples & potatoes.
I'm also under the impression that there is no good way to migrate cleanly, short of a lot of manual effort.

As to perf issue, that was halfway what I was aiming for in my previous comment... except that I wouldn't call it a perf issue as such. Rather, I was hoping there was a better protocol behaviour.
If it were a perf issue, then it might be [partly] tied to the platform that users are using.

wouterjdb · 2024-04-23T07:54:33Z

Has anyone tested a recent version of HA? Has the behavior changed or is it still there?

frank777777 · 2024-04-23T09:51:31Z

@wouterjdb still there dear friend. Installed the tuya radar on the Z2M, and in the log i can see a choc-a-block

marc4s · 2024-04-23T09:56:11Z

currently started a test with 2024.4.3
finger crossed - no delay yet after 20minutes. need to have an eye on the next days.

not sure if this belongs to, but a lot of devices(plugs) seems to switch on/off but the UI is not showing up and getting a device not respond error.
and maybe the other way too, some just really do not respond. but I am not at home, need to check this today evening

2024-04-23 11:51:28.921 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140355173055168] Failed to send request: device did not respond
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/zigpy/device.py", line 342, in request
    return await req.result
           ^^^^^^^^^^^^^^^^
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 64, in wrap_zigpy_exceptions
    yield
  File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 84, in wrapper
    return await RETRYABLE_REQUEST_DECORATOR(func)(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/util.py", line 131, in retry
    return await func()
           ^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/quirks/__init__.py", line 228, in command
    return await self.request(
           ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/zcl/__init__.py", line 377, in request
    return await self._endpoint.request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/endpoint.py", line 253, in request
    return await self.device.request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/device.py", line 341, in request
    async with asyncio_timeout(timeout):
  File "/usr/local/lib/python3.12/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 239, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2543, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2580, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 971, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1043, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/switch.py", line 99, in async_turn_off
    await self._on_off_cluster_handler.turn_off()
  File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/general.py", line 453, in turn_off
    result = await self.off()
             ^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 83, in wrapper
    with wrap_zigpy_exceptions():
  File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__
    self.gen.throw(value)
  File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 66, in wrap_zigpy_exceptions
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Failed to send request: device did not respond
2024-04-23 11:51:31.022 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [1403551730551

wouterjdb · 2024-04-23T11:08:05Z

Thanks @frank777777 and @marc4s for the quick reply.

pgroene · 2024-04-29T05:48:53Z

I have setup zigbee2mqtt for the MMWave and Tuya plugs and update to the latest HA. Looks like it is working fine that way with ha 2024.4.4

marc4s · 2024-04-29T07:31:02Z

an I am fine with zha and 2024.4.4 - it is wrking since I started the test last week.
no delay anymore

the not responding devices can be fixed by a full reboot of HAOS. two times a device got unavailable and I needed to repair it.
but no delays. thanks

pgroene · 2024-04-29T17:37:50Z

Was there anything done to fix the issue, or did it just go away because something else was update?

@marc4s where the non responding devices, devices that where spamming the network?

wouterjdb · 2024-05-01T13:04:14Z

I also updated now, and it seems to be working stable (>24hrs)!

marmolak · 2024-05-03T09:50:19Z

I upgraded to 2024.5.0 and ZHA not working.

Now with:

Failed to call service switch/turn_on. Failed to send request: Failed to enqueue message after 3 attempts: <EmberStatus.NO_BUFFERS: 24>

wouterjdb · 2024-05-08T03:16:12Z

I also updated now, and it seems to be working stable (>24hrs)!

Unfortuonately, back to endless stability issues in the meanwhile.

marc4s · 2024-05-08T05:46:36Z

with 2024.5 I also have more often the behaviour that (sometimes all, sometimes only specific plugs does not respond) and I need to reboot HAOS. but delays not anymore. which kind of stability issues do you have?

wouterjdb · 2024-05-09T19:20:53Z

No delays that I noticed. But all Zigbee devices stopped working randomly again.

wouterjdb · 2024-07-03T20:03:45Z

OK - so latest update from here: I removed two electricity metering plugs from the network (you know - the ones that measure power, voltage, current) and that brought stability back. Updated to the latest and greatest version of HA: no more issues.

I'll try and test them individually later when I get back the will to do so ;-) For now my home runs smooth again!

issue-triage-workflows · 2024-10-01T20:06:58Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

tabrisnet · 2024-10-03T16:35:23Z

@wouterjdb those plugs, were they the type that need polling, or did they send triggered updates?

issue-triage-workflows · 2025-01-01T18:07:39Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

tabrisnet · 2025-01-01T19:27:29Z

adding some butter to the stale bread

home-assistant bot added the integration: zha label Jan 4, 2024

home-assistant bot assigned dmulcahey, Adminiuga and puddly Jan 4, 2024

issue-triage-workflows bot added the stale label Oct 1, 2024

issue-triage-workflows bot removed the stale label Oct 3, 2024

issue-triage-workflows bot added the stale label Jan 1, 2025

github-actions bot removed the stale label Jan 1, 2025

ZHA delays with Tuya mmWave sensors #107200

ZHA delays with Tuya mmWave sensors #107200

Comments

a-d-r-i-a-n-d commented Jan 4, 2024 • edited Loading

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

System Information

home-assistant bot commented Jan 4, 2024

puddly commented Jan 4, 2024

a-d-r-i-a-n-d commented Jan 5, 2024

puddly commented Jan 5, 2024

a-d-r-i-a-n-d commented Jan 5, 2024

a-d-r-i-a-n-d commented Jan 5, 2024

puddly commented Jan 5, 2024

a-d-r-i-a-n-d commented Jan 5, 2024

a-d-r-i-a-n-d commented Jan 5, 2024

a-d-r-i-a-n-d commented Jan 5, 2024

a-d-r-i-a-n-d commented Jan 5, 2024

ChristophCaina commented Jan 5, 2024

marc4s commented Jan 5, 2024 • edited Loading

a-d-r-i-a-n-d commented Jan 5, 2024

frank777777 commented Jan 5, 2024

marc4s commented Jan 5, 2024

frank777777 commented Jan 5, 2024

a-d-r-i-a-n-d commented Jan 5, 2024 • edited Loading

marmolak commented Jan 5, 2024 • edited Loading

tanerpaca commented Jan 5, 2024 • edited Loading

marmolak commented Jan 5, 2024

frank777777 commented Jan 5, 2024

frank777777 commented Jan 5, 2024

marmolak commented Jan 5, 2024

merdok commented Jan 5, 2024

christabone commented Jan 6, 2024

wouterjdb commented Mar 31, 2024

frank777777 commented Mar 31, 2024

frank777777 commented Mar 31, 2024

tabrisnet commented Mar 31, 2024 • edited Loading

disruptivepatternmaterial commented Apr 1, 2024

wouterjdb commented Apr 4, 2024

tabrisnet commented Apr 4, 2024

pgroene commented Apr 4, 2024

tabrisnet commented Apr 4, 2024

wouterjdb commented Apr 23, 2024

frank777777 commented Apr 23, 2024

marc4s commented Apr 23, 2024 • edited Loading

wouterjdb commented Apr 23, 2024

pgroene commented Apr 29, 2024

marc4s commented Apr 29, 2024

pgroene commented Apr 29, 2024 • edited Loading

wouterjdb commented May 1, 2024

marmolak commented May 3, 2024

wouterjdb commented May 8, 2024 • edited Loading

marc4s commented May 8, 2024

wouterjdb commented May 9, 2024

wouterjdb commented Jul 3, 2024

issue-triage-workflows bot commented Oct 1, 2024

tabrisnet commented Oct 3, 2024

issue-triage-workflows bot commented Jan 1, 2025

tabrisnet commented Jan 1, 2025

a-d-r-i-a-n-d commented Jan 4, 2024 •

edited

Loading

marc4s commented Jan 5, 2024 •

edited

Loading

a-d-r-i-a-n-d commented Jan 5, 2024 •

edited

Loading

marmolak commented Jan 5, 2024 •

edited

Loading

tanerpaca commented Jan 5, 2024 •

edited

Loading

tabrisnet commented Mar 31, 2024 •

edited

Loading

marc4s commented Apr 23, 2024 •

edited

Loading

pgroene commented Apr 29, 2024 •

edited

Loading

wouterjdb commented May 8, 2024 •

edited

Loading