Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Conbee: Firmware update 1.35.2 breaks link with zigbee devices #21162

Closed
Malvadis opened this issue Feb 2, 2024 · 203 comments · Fixed by Koenkk/zigbee-herdsman#913
Closed

Conbee: Firmware update 1.35.2 breaks link with zigbee devices #21162

Malvadis opened this issue Feb 2, 2024 · 203 comments · Fixed by Koenkk/zigbee-herdsman#913
Labels
problem Something isn't working

Comments

@Malvadis
Copy link

Malvadis commented Feb 2, 2024

What happened?

Update 1.35.2 was applied by auto update last night, I was previously running on version 1.35.1.
After the update the link to all devices was lost.

What did you expect to happen?

I expected the update to apply and all device joins to be working

How to reproduce it (minimal and precise)

Update to version 1.35.2 from 1.35.1, I use the Conbee 2 dongel.
HomeAssistant is running on a promox VM, the conbee stick is directly passed to the VM using USB redirection.

Zigbee2MQTT version

1.35.2

Adapter firmware version

Unsure

Adapter

Conbee 2

Setup

Addon on home assistant OS, running Home assistant OS on a virtual machine, Proxmox hypervisor, conbee stick directly given to the OS.

Debug log

log (1).txt
@Malvadis Malvadis added the problem Something isn't working label Feb 2, 2024
@Andrewletsdig18
Copy link

hi i also have same problem

@donagrejja
Copy link

Many reports of similar issues all over the place. I also have the same issue so I had to roll back.

@lion06
Copy link

lion06 commented Feb 2, 2024

same issue

@janwing
Copy link

janwing commented Feb 2, 2024

Same setup, same problem, rollback to 1.35.1 fixed it.

@solarssk
Copy link

solarssk commented Feb 2, 2024

The same situation.

Hardware: Synology DS920+
Home Assistant version: 2024.1.5
Zigbee2MQTT version: worked on 1.35.1
Adapter: Conbee2
How HA is working: VM

@Gazoonky
Copy link

Gazoonky commented Feb 2, 2024

Same issue here.

@petterw33
Copy link

Same issue for me as well

@ExMacro
Copy link

ExMacro commented Feb 2, 2024

Same thing with Conbee II and latest HA version. Restore from backup to 1.35.1 returned all the lights.

@tduong-cloud
Copy link

Same here with HA on docker, and skyconnect. I had to roll back to 1.35.1 as well.

@treb33
Copy link

treb33 commented Feb 2, 2024

Same here!

@Rempert
Copy link

Rempert commented Feb 2, 2024

No problems here with 1.35.2. Using Z2M and UZG-01.

@linloen
Copy link

linloen commented Feb 2, 2024 •
edited
Loading

+1 Zigbee2mqtt broken after latest update. Conbee2 not supported.
Conbee 2 does not communicate with devices.

@BarryH1972
Copy link

No problems, sonoff stick, HA running direct on a thinclient

@aceindy
Copy link

aceindy commented Feb 2, 2024

Here too issues with ConBee-II

@ahaverty ahaverty mentioned this issue Feb 2, 2024
Closed
@JulianLundh
Copy link

Im using a sonzoff and my aqura devices working great but my Tuya Model TS0042 Singel button stopped working. Solved by downgrading

@z-master42
Copy link

Same problem here, with ConBee 2 on a Home Assistant Yellow. Connection is established for approx. 15 minutes, after which all devices are no longer available. The same after an add-on restart.

@BurningTheSky
Copy link

Similar issue here. Conbee 2 on Unraid via docker. Works for a while then starts erroring talking to any device. Works for a time when container is restarted but then stops again.

@pbathuk
Copy link

pbathuk commented Feb 3, 2024

I'm on HASS OS with conbee 2 and upgraded last night (via add-on), v1.35.2 is working for me today. I did downgrade the conbee stick a while ago to the firmware mentioned on the zigbee2mqtt website to ensure other bugs did not happen (I forget the version).
Just wanted to add this, as can see it appears to all be conbee 2 sticks only affected from the thread.

@Koenkk
Copy link
Owner

Koenkk commented Feb 3, 2024

Is anyone running a bare metal setup here (without docker)?

@leopoldwang
Copy link

Also affecting conbee 1.

@Koenkk
Copy link
Owner

Koenkk commented Feb 3, 2024

Can someone provide the herdsman debug log of this?

See this on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files.

@Koenkk Koenkk changed the title Firmware update 1.35.2 breaks link with zigbee devices Conbee: Firmware update 1.35.2 breaks link with zigbee devices Feb 3, 2024
@fraban
Copy link

fraban commented Feb 3, 2024 •
edited
Loading

Same here - auto update witch Conbee1 and Conbee 2 ( I run severals HA-Systems) all breaking the connection to all Aqara temp sensors ...

-- I downgraded from the backup we have here... now working again ...
We downgraded to 1.35.0

@BurningTheSky
Copy link

Can someone provide the herdsman debug log of this?

See this on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files.

Not sure if this is what you're looking for?

error 2024-02-03 08:43:08 Publish 'set' 'state' to 'Toilet and Under Stairs Lights' failed: 'Error: Command 0x54ef44100076d47e/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 (73))'
debug 2024-02-03 08:43:08 Error: Command 0x54ef44100076d47e/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 (73)) at DeconzAdapter.sendZclFrameToEndpoint (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:666:23) at Request.send (/app/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20) at Endpoint.command (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:746:28) at Object.convertSet (/app/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:46:17) at Publish.onMQTTMessage (/app/lib/extension/publish.ts:249:36) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17)
info 2024-02-03 08:43:08 MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'state' to 'Toilet and Under Stairs Lights' failed: 'Error: Command 0x54ef44100076d47e/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 (73))'","meta":{"friendly_name":"Toilet and Under Stairs Lights"},"type":"zigbee_publish_error"}'

@janfuhlrott
Copy link

Same here with Conbee II.

@Koenkk
Copy link
Owner

Koenkk commented Feb 3, 2024

Please share more about the setup, HA addon, z2m docker image or bare metal. Otherwise I cannot help

@BurningTheSky
Copy link

I'm running z2m as a docker container through Unraid with the ConBee 2 mapped to the container

@vsatmydynipnet
Copy link

Everything was not working here after this auto-update to 1.35-2:
HA latest

Core 2024.1.6
Supervisor 2023.12.1
Operating System 11.4
Frontend 20240104.0

Current version: 1.35.2-1

Conbee II

IKEA Sensors

Power Switches, Motion Sensor and temperature Sensors failed. After 2 reboots th epower switches works again, motion sensor too, but temperature sensors do not work. they have a old value, but do not update. I think i will roll back the VM to 1.35.1 and block auto update

@gilrim
Copy link

gilrim commented Mar 6, 2024

Just here to "third" the comment about this keeping me from upgrading and checking back to this thread fairly frequently in the homes that there's some change or update that actually resolves the issue. The install I'm using the conbee at is far away from home, so I need to be fairly certain that if I'm going to be doing a upgrade, then it's going to work...

@z-master42
Copy link

z-master42 commented Mar 6, 2024 •
edited
Loading

The following configuration runs flawlessly with Home Assistant OS on a Home Assistant Yellow. The development version of 1.35.x already ran flawlessly for me. After the update, I restarted the entire system (host), not just Home Assistant (core).

Zigbee2MQTT-Version 1.36.0 commit: unknown
Coordinator-Typ ConBee2/RaspBee2
Coordinator-Version 0x26720700
Frontend-Version 0.6.159
zigbee_herdsman_converters_version 18.42.0
zigbee_herdsman_version 0.35.1

@stomko11
Copy link

stomko11 commented Mar 6, 2024 •
edited
Loading

Updated to 1.36.0-1 and no issues. Previous versions were not working for me. I am on Conbee II (ver. 0x26700700), did not upgrade firmware nor rebooted host. It has been 6 hours now.

@s3frank
Copy link

s3frank commented Mar 6, 2024 via email

@Llenas09
Copy link

Llenas09 commented Mar 6, 2024

Hi... bad news for me. I need to recover backup to 1.35.1.

5.-
Conbee II with firmware 0x26580700.bin
Home Assistant addon Zigbee2MQTT: 1.36.0
Status: After 72 hours multiple sensors end up disconnected, rebooting the system everything works again until it fails again.

What coordinator do you recoomend to buy for substitute the conbeeII? Anyone knows what coordinator uses Koenkk in his house? i think that this is the most guaranteed coordinator...

@Prokopchini
Copy link

Conbee III + RPi5 + Homebridge - everything works stably!

@OlafKocanda
Copy link

Maybe a solution for you guys: Disable availability in the settings. Worked for me!
This thread brought me to the solution:
#21495 (comment)

@majkers
Copy link

majkers commented Mar 12, 2024 •
edited
Loading

All right guys. Since Koenkk did not reply to my last message, it seems to me that we are left alone with that problem. Me personally I won't update above last working version of z2m because changing a dongle is not an option for me.

Is there anyone else beside @Llenas09 that still has problems? Maybe it is better to open new issue?

@DavyRoswinkel
Copy link

All right guys. Since Koenkk did not reply to my last message, it seems to me that we are left alone with that problem. Me personally I won't update above last working version of z2m because changing a dongle is not an option for me.

Is there anyone else beside @Llenas09 that still has problems? Maybe it is better to open new issue?

I do still have the problem, but on the other hand, it works great if downgrading to the former version..so...it's not really a problem

Solving the issue would be nice, but ignoring the update is a possibility, as long as that works.

@sstarcher
Copy link

I also still have this problem. After upgrading to 1.35.2 about 25% of my devices no longer work. I downgraded to 1.35.0 and my devices continue e to not work. If I stop Zigbee2MQTT and unplug my adapter and replug it in they will start working for a bit until they die again.

@sstarcher
Copy link

@OlafKocanda looks like I already have availability not enabled.

@Celedhrim
Copy link

Celedhrim commented Mar 12, 2024 •
edited
Loading

All right guys. Since Koenkk did not reply to my last message, it seems to me that we are left alone with that problem. Me personally I won't update above last working version of z2m because changing a dongle is not an option for me.
Is there anyone else beside @Llenas09 that still has problems? Maybe it is better to open new issue?

I do still have the problem, but on the other hand, it works great if downgrading to the former version..so...it's not really a problem

Solving the issue would be nice, but ignoring the update is a possibility, as long as that works.

This is never a "solution" because :

  • The issue is still there
  • One day you will add a new zigbee devices not supported by your old version
  • possible security issue can expose you
  • One day you will reinstall your os and discover your "good old release" is no more available"

"My old version is fine" is a dangerous logic , you will pay for it one day or another :)

@fraban
Copy link

fraban commented Mar 12, 2024 via email

@Albruaje
Copy link

Still the same for me with Raspbee II, had to return to 1.35.1-1

@majkers
Copy link

majkers commented Mar 13, 2024

IMHO we should open new issue

@pgepl
Copy link

pgepl commented Mar 13, 2024

I'm running the latest Conbee 3 firmware and have multiple "Failed to ping" entries. Mainly Tuya devices. I am following this topic and others in search of a solution. I have version 1.36.0.

@majkers
Copy link

majkers commented Mar 14, 2024

OK so who can open new issue with logs and stuff? I can't since I am still on last working version and afraid to upgrade :(

@fraban
Copy link

fraban commented Mar 14, 2024 via email

@s3frank
Copy link

s3frank commented Mar 14, 2024 via email

@sstarcher
Copy link

So far my devices have been up for 24 hours, but I had to fully remove and reconnect them to the network for each one that was offline. This is with using 1.36.0

@Albruaje
Copy link

Still the same for me with Raspbee II, had to return to 1.35.1-1

Since there seems to be no solution to this, I have chosen to switch to a SONOFF USB dongle. The change has been relatively easy (just re-pair the devices) and everything is working correctly with version 1.36

@BenjiBizz
Copy link

BenjiBizz commented Mar 23, 2024 •
edited
Loading

After reading this: https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html I quote: For USB adapters you can use dmesg command on Linux hosts to find the mounted device. Where possible you should use the /dev/serial/by-id/ path of the stick, instead of /dev/tty*. This is because the /dev/tty* path can change - for example /dev/ttyACM0 may become /dev/ttyACM1 and then later back to /dev/ttyACM0. The /dev/serial/by-id/ path won't change.

That was also the solution for me. It has been running for over a week now and that on the current version ! :)

thanks

i am using deconz conbee 2 Stick

@mcrodriguezb
Copy link

mcrodriguezb commented Mar 23, 2024 •
edited
Loading

After not many people messaging during the last weeks, I decided to give a try to version 1.36.0. This was on March 17th. So far, all running fine.

In my configuration, I have /dev/serial/by-id/ since installation. Failed with 1.35.2, but not with 1.36.0.

HTH

@GD-Dal
Copy link

GD-Dal commented Mar 29, 2024

Seems to still be an issue in 1.36.0. Losing contact with several nodes
I'm running HA OS on bare metal, and the conbee is registered as /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2231282-if00 in Z2M

@z-master42
Copy link

Seems to still be an issue in 1.36.0. Losing contact with several nodes
I'm running HA OS on bare metal, and the conbee is registered as /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2231282-if00 in Z2M

I cannot confirm this. I've been on 1.36 for weeks and have no problems at all. ConBee II as /dev/ttyACM0.

@fraban
Copy link

fraban commented Apr 1, 2024 via email

@chatainsim
Copy link

Since 1.36 no more issue. It's seems even more stable than ever. Thanks

@Koenkk Koenkk unpinned this issue Apr 8, 2024
@majkers
Copy link

majkers commented Apr 12, 2024

Unfortunaly I had the same issue. Upgrated to latest 1.36.1-1 after about 30h of working ok it started to not work with error like this:

Publish 'set' 'state' to 'gniazdko_xiaomi' failed: 'Error: Command 0x00158d0002347282/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (16))'

It seems that it can't set state to my coordinators that are smart plugs like Xiaomi ZNCZ02LM and Tuya TS011F_plug_1. I rolled back to 1.35.2-1 and hope not to have those errors anymore.

@majkers majkers mentioned this issue Apr 13, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
problem Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(master): release 0.33.9 Koenkk/zigbee-herdsman