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.
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
Conbee II : problem devices connection after latest upgrade 26660700 firmware #3570
Comments
Hi! Can you try going to version 26650700 ? If that works, you have the same issue as #3387 |
Thanks for the suggestion. I am downgraded the firmware and now the conbee working properly. |
@baldus88 I suggest re-opening this one. |
Can you provide logs? |
Can you try with a extension cable? It can't join the network. |
@Mimiix Raspbee, so that will be difficult... Except for there is any external device attached. |
That must be the case then. |
Before the upgrade the conbee work good without a problem. Only difference are upgrade deconz and upgrade firmware. |
@SwoopX Can it be that network key thing you had earlier? |
I am also experiencing similar issues using a ConBee2 with a Raspberry Pi 3 B+ and an extension cable:
The weird thing is that the Zigbee connection to my devices still seems to work, but every now and then my lights disappear and the deCONZ web UI shows the firmware as "Not connected", after which I need to disconnect the ConBee 2 for 10 seconds, reconnect it and restart Home Assistant in order to make everything visible again. I also had an issue where my Trådfri remotes stopped working for a day or two until they started working again by themselves, but that might be an unrelated problem. I was initially using the 26660700 firmware and downgraded to 26650700, but the same issue persists. |
@vsaarinen Can you open a seperate issue with your own details? Also: In the addon make sure to use the full device serial and not the dev/ttyAMA0. |
In my deCONZ Home Assistant add-on, my configuration is:
But sure, I'll open a new issue when I have time to dig into this further. |
Hi @vsaarinen. I have the same situation. I have tested the same things in addition have a problem with light from osram. |
Sorry to continue using this issue, but just in case it's relevant: could these error logs be due to pi@raspberrypi:~ $ ps ax | grep deCONZ
325 ? Ss 14:00 /bin/bash /usr/bin/deCONZ-WIFI2.sh
329 ? Ss 5:08 /bin/bash /usr/bin/deCONZ-update2.sh
7423 ? Ssl 78:59 /usr/bin/deCONZ -platform minimal --http-port=80
22737 ? Ssl 47:28 deCONZ -platform xcb --auto-connect=1 --dbg-info=1 --dbg-aps=0 --dbg-otau=0 --dbg-zcl=0 --dbg-zdp=0 --upnp=0 --http-port=40850 --ws-port=8081 --dev=/dev/ttyACM1
22806 ? S 0:00 /bin/sh /usr/bin/deCONZ-otau-dl.sh
23420 ? Sl 0:24 /usr/bin/Xtigervnc :0 -desktop Home Assistant - deCONZ -auth /data/.Xauthority -geometry 1920x1080 -depth 16 -rfbwait 30000 -rfbport 5900 -pn -localhost -SecurityTypes None
23422 ? S 0:00 /usr/bin/perl /usr/bin/tigervncserver -name Home Assistant - deCONZ -geometry 1920x1080 -depth 16 -localhost yes -SecurityTypes None --I-KNOW-THIS-IS-INSECURE :0
30454 pts/0 S+ 0:00 grep --color=auto deCONZ |
What is it now actually? Above in the screenshot it shows Raspbee, the log files say Conbee II |
Erm, good question. 26390500 is for Raspbee I, 26660700 for Conbee II (and Raspbee II as I recall). |
Yep, is not normal the conbee II signal the upgrade for firmware raspbee :( |
As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
As there hasn't been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it isn't solved, request to get this opened again. |
@Mimiix I propose to reopen the issue. I upgraded Conbee II to the newest firmware and it doesn't work after that. It appears in the system as USB device for very short time (1-2 seconds) and than disappear again. In Phoscon I see product/firmware info for this short time and than "Not connected". I tried to connect it in Windows/Debian - the same thing. It looks like infinite boot loop. Is any chance to re-flash it manually including option with solder? |
same behaviour after latest update over here. short appearance and again, and again after latest update |
Sorry, missed this email of this message. All be it a bad late: Just retry manually updating the firmware , even while bootlooping it should catch on. Same goes for @foscoj . |
Just did that within windows a few minutes ago and it's alive again, thanks! |
Describe the bug
Hi.
I have the Conbee II plugged to my raspberry (with raspbian os) and home assistant software for home automation.
Before this double upgrade (firmware & deconz) the integration of my zigbee devices is ok.
First I have installed the firmware (26660700) via this guide:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually#update-in-windows
After I have installed the latest version of deconz 2.05.86.
The old firmware and not update needed.
After I tried to plug the conbee ii on my laptopt and I am successfully update the conbee to the last firmware.
When try to connect the new device (ex. osram light) the phosocon app found and connect the device. But I am trying to integrate this in home assistant o restart the device the phosocon app have more different behaviors.
Firmware: Not connected
Or Firmware: 000000
Firmware Not Connected & Product blank & Vendor unknown
If i try to reconnect the light the conbee not found nothing.
Probably the deconz software is corrupted? Or other reasons?
I am already removed the software (via "sudo apt remove deconz") and reinstalled but the problem remain the same.
Thanks for the support
Steps to reproduce the behavior
Expected behavior
The regular connected of my zigbee devices
Screenshots
If I will try to update firmware via raspbian in phoscon app view this:
Firmware not connected:
Product blank:
Environment
deCONZ Logs
Additional context
The text was updated successfully, but these errors were encountered: