search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.79k stars 1.64k forks source link

Timeout issues - no response received (206) #21792

Open shalak opened 6 months ago

shalak commented 6 months ago

What happened?

I've been experiencing frequent timeout issues with Zigbee2MQTT in Home Assistant since yesterday - for the majority of my devices. Most frequently it looks like the first request to a device, for example, toggling the left button, works fine. However, subsequent requests, like attempting to toggle the right button immediately after, result in a timeout. After couple of minutes the request goes through.

Although, this behavior is not consistent - sometimes I can get 10 consecutive requests working on, while then the 11th times out...

Here's a snippet of the log indicating the problem:

Publish 'set' 'state' to 'VR Room' failed: 'Error: Command 0x00124b002226f636/2 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (206))'

Devices affected:

However, the issues does not happen at all for those:

HA Core: 2024.3.0 HA Supervisor: 2024.03.0 Z2M Add-On: 1.36.0-1 ConBee2/RaspBee2 version 0x26780700

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.36.0-1

Adapter firmware version

0x26780700

Adapter

ConBee2/RaspBee2

Setup

HA x86, as add-on

Debug log

No response

shalak commented 6 months ago

I tried rebooting, restoring whole Hassio from backup, toggling the "Availability" setting (based on this issue) - nothing helped.

So just now, I figured that maybe those timing-out devices were all using the same router and that router device just malfunctioned, so I triggered the Map scan to see the exact connections between devices.

...even before the scan finished everything started to work OK!

What's going on? How can I avoid this in future?

kremik commented 6 months ago

Having the same issue also with other devices

github-actions[bot] commented 1 week ago

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days