search

Koenkk / zigbee2mqtt

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

Zigbee2MQTT losing network connection consistently after recent updates (Hassio) #19177

Open allgrinder opened 1 year ago

allgrinder commented 1 year ago

What happened?

Hey,

I've been using Zigbee2MQTT via HomeAssistant for over 2 years, and for a little over a year with the Sonoff Zigbee 3.0 stick.

So far, everything has been running very smoothly and reliably. However, since the last update, and also with the current one, I've been constantly facing issues:

Zigbee2MQTT loses connection to the entire network. No device responds, and the error message is:

Failed to ping "Kitchen" (attempt 1/2, Read 0xd*****/1 genBasic(["zclVersion])... Timeout /... dataRequest)

Once the error occurs, the only solution is to restart. After that, all devices reconnect as usual.

What did you expect to happen?

I have no idea. The regular log just indicates that no device can be pinged. I have now activated Zigbee-herdsman.

How to reproduce it (minimal and precise)

The issue is not reproducible. It occurs intermittently, sometimes after hours, and sometimes only after a day.

Zigbee2MQTT version

1.33 1-1

Adapter firmware version

20210708

Adapter

Sonoff Zigbee 3.0 stick

Debug log

No response

DorjeDorf commented 1 year ago

I am seeing the same thing on Slaesh's stick with the newes firmware. After a couple hours, all communication stops and all I see in logs is the same as OP reported.

CzPeti commented 1 year ago

same error with conbee 2 Error 2023-10-06 15:51:07Publish 'set' 'state' to 'Medence konnektor' failed: 'Error: Command 0xa4c138dbabdd4b01/1 genOnOff.on({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (140))'

rdl987 commented 1 year ago

A solution could be downgrade zigbee2mqtt version?

I have the same problem

allgrinder commented 1 year ago

I understand it not. Since my post, everything ran stable, and today 3 crashes... I changed nothing. Also, the log is somehow not informative....

mjaensch commented 12 months ago

I have the same problem. Lost connections to half of my zigbee devices over night. I will try to downgrade zigbee2mqtt since pairing all these devices again and changing all related home assistant things is a really big pain.

N3rdix commented 12 months ago

pairing all these devices again and changing all related home assistant things is a really big pain.

This is usually not a problem if you just pair them again in Z2M. First thing I would try is putting them in pairing mode without deleting the device, only if this does not help delete it in Z2M. All entities in HA should be kept/recreated as before, I did that a lot of times without any hassle in HA

mjaensch commented 12 months ago

pairing all these devices again and changing all related home assistant things is a really big pain.

This is usually not a problem if you just pair them again in Z2M. First thing I would try is putting them in pairing mode without deleting the device, only if this does not help delete it in Z2M. All entities in HA should be kept/recreated as before, I did that a lot of times without any hassle in HA

Thank you! I managed to re-pair all devices without deleting them first. I downgraded to version 1.33.0 and I hope that it will be a bit more stable now.

aambroze commented 10 months ago

Version 1.34, drops started happening recently once or twice a day. I’ve confirmed that restarting the addon helps. Before that I have these issues reported IMG_9964

If restart helps does it mean it is indeed a software problem ?

tclemos commented 10 months ago

I'm also facing a similar issue. I'm running it as a home assistant add-on and at some point some devices simply stop responding. If I click on a button, the entity state is toggled but the physical switch doesn't toggle the state. Generally a restart to the add-on fixes the problem. Also I have some scene buttons that struggle to communicate, not sure if it is related, I'll try to downgrade it to the previous version and check if it is more stable

Ricconnect commented 8 months ago

Anyone has an update on this issue? I'm experiencing the same problem since more frequently updating the docker instance of Z2M. It works after a restart, but only for some time (minutes or hours) and then all my devices stop responding for some reason

timwar commented 8 months ago

Same issue here :(. @mjaensch Did a downgrade the magic(did it help?)

dodo124 commented 8 months ago

Same problem here. Sonoff Zigbee 3.0 and Zigbee2MQTT. This is happening since I switched from IO Broker to HomeAssistant in Dezember. One more thing though: Some devices not only loose connection but HA tells me that the whole entitie is gone. So far this problem mainly occurs when the Zigbee3 device is completely turned off, e.g. there is a switch to turn it off completely (for the case that HA is not working). And additionaly I do have a Tuya light which randomly looses connection and starts pairing mode. A few more things: a) I recognized that the problem occours when I interact with HA (especially Zigbee2MQTT) especially when using "adopt new devices" b) I have the fealing that the connection is not meshed logically to the nearest Zigbee router but alwyays to the coordinator.(despite the fact that it shows different in the connection mesh overwiew). This is so because of my uniquige room-layout which needs to route via a special zigbee router in order to work properly ( this worked fine in IO broker this way). c) I just found out that the the "adopt new devices" function was changed in some update, because now the "pick unique router to join" function works as intended and does not kick all existing connections. d) When I use "adopt new devices" and I do not specify a unique device it takes ages... and most likely won´t work, this is new to the latest update.

Greetings Dom

JSkier21 commented 6 months ago

Also seeing this, but seemingly limited to Peanut Securifi plugs (other plugs seem okay). I have some over on HA that do not have any connectivity issues. I tried repairing the Peanut devices on zigbee2mqtt, and it seemed okay for a bit, but back to a lot of unavailable / available toggling several times within an hour. Also going through the main coordinator.

Furthermore, I am running Docker 5.0.1, about info before on the docker app instance. 

Zigbee2MQTT version
    [1.36.1](https://github.com/Koenkk/zigbee2mqtt/releases/tag/1.36.1) commit: [ffc2ff1](https://github.com/Koenkk/zigbee2mqtt/commit/ffc2ff1)

Coordinator type
    zStack3x0

Coordinator revision
    20230507
cracyfloyd commented 6 months ago

Same here with Conbee III. For me are only some bulbs from Ikea,Philips and Osram with this problem With my xiaomi sensors not. it is with the latest release version and with the latest beta too. all devices works furthermore. Zigbee2MQTT-Version 1.36.1-dev commit: 245afb1 Coordinator-Typ ConBee3 Coordinator-Version 0x26510900

JSkier21 commented 6 months ago

1.37.0 seems to have fixed connectivity issues with the Peanut plugs I have. It's been two days and no connectivity issues so far 🤞

github-actions[bot] commented 6 days 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