Conbee USB stick connection issues Topic is solved

[mknops]

Hi,

I have Domoticz 2021.1 running on a Pi Model 3b (running buster) and recently attached a Conbee 2 Zigbee USB-stick to it. However:
- Phoscon app tells me "firmware is disconnected" and
- Domoticz (on port 80) is telling me every 10th second: Error: ConbeeStick: (ConbeeStick) Startup failed. retrying....

Where am I and what did I do so far:
- I did follow these instructions to install the stick and connect to Domoticz: https://www.robbshop.nl/blog/conbee-usb ... nstalleren.
- I do see the Conbee listed under hardware in Domoticz.
- I can access the Phoscon app (on port 8080; version 2.13.01/6-10-2021) on my (the same) pi, but it complains about firmware not connected
- I already follow these instructions here: https://phoscon.de/en/support#conbee2-connection-issues .....however.......

...my ConBee-stick is *not* listed as a registered device under lsusb...the FAQ page only describes what to do next when using Docker or a virtual machine. I'm using neither one of them.

Dmesg is telling me lots of these:
[ 90.564016] usb 1-1.5: new full-speed USB device number 14 using dwc_otg
[ 90.708483] usb 1-1.5: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[ 90.708539] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 90.708556] usb 1-1.5: Product: ConBee II
[ 90.708571] usb 1-1.5: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[ 90.708586] usb 1-1.5: SerialNumber: DE2458103
[ 90.710048] cdc_acm 1-1.5:1.0: ttyACM1: USB ACM device
[ 94.078361] usb 1-1.5: USB disconnect, device number 14
[ 102.563858] usb 1-1.5: new full-speed USB device number 15 using dwc_otg
[ 102.718604] usb 1-1.5: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[ 102.718632] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 102.718648] usb 1-1.5: Product: ConBee II
[ 102.718663] usb 1-1.5: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[ 102.718678] usb 1-1.5: SerialNumber: DE2458103
[ 102.721278] cdc_acm 1-1.5:1.0: ttyACM1: USB ACM device
[ 106.369318] usb 1-1.5: USB disconnect, device number 15

First thing I note, I have a ttyACM0 device (the default) in /dev. The device ttyACM1 does not exist in /dev.

I have searched GitHub, the Discord channel and many places more, but...I'm lost on what to do.

ANY help would be much appreciated.

Thanks in advance and kind regards,

Michel.

[Dave21w]

My first question would be apart from Phoscon can you confirm you have deconz running, unless you are running your Pi in headless mode you should be able to login and see the deconz app, when it starts up it will ask you to connect to the type of device you are using, either a raspee or conbee, until you have confirmed the type and clicked connect phsocon will not be able to talk to the device.

[mknops]

Hi,

Thanks so much for your reply.

I'm running headless indeed. Deconz service is enabled and running. No error message in (sys)logs other than the one dmesg shows.

Michel.

[Dave21w]

I did have issues with headless mode but it was so long ago I really can't remember what it was, I did however end up not using headless mode anymore and just allowing my Pi to auto boot to the GUI and I use VNC to access it, maybe you could try it this way, obviously you need to switch deconz out of headless mode too and start it either with a script or manually, it is quite useful being able to see its GUI as there is a lot of information in there.

Dave

[Thorgal789]

Your issue seem a firmware issue, it s a new device ? It s common on new device or updated with a virtual machine.
To be sure make a try on windows, you will listen the "usb disconnect sound" every 10s (good method to be sure, it s the only issue you can have on windows, no power issue, no OS issue, ...)
Try to update manualy the conbee, you have the long story here https://github.com/dresden-elektronik/d ... Z-manually

Just some comment :
- Never use virtual machine, docker or VM to update the firwmare
- you can use the firwmare you already have if you like it
- The command have special setting to increase the timeout and the number of retry, so It can take some time.
- If you don't use Virtual machine, the next time, you will be able to update the firmware using Phoscon, so you can take an older firmware if you don't have issue with it.

If it realy don't work I will give you another procedure (increase the timeout, and unplug/replug the device), but updating the firmware with the official method is enought.

And BTW you haven't found help on their discord channel https://discord.gg/QFhTxqN ? I m on it too, name Smanar

[mknops]

Dear Thorgal789/Smanar,

I do recognize Smanar indeed from the many places I have visited during my quest for a solution

Your answer was the silver bullet. I had already tried flashing the stick through my RPI but that did not work (also bit strange). On Windows 11 it worked like a charm, the stick is now correctly registered on the RPI as well and Domoticz has finally integrated!!

Thank you very very much for your crucial help!

Regards,

Michel.

[Thorgal789]

Np, perhaps you haven't used exactly the same command, there is a "lighter" one, this one is specially for the issue, the firmware was badly copied on the device, lot of users have returned the conbee because of that.
And it don't work always at first try, this one have a longer timeout to work even with the USB disconnection, but the disconnection can stay 1s or 10 s ...
The good news, it s don't happen on RPI, so I hope it s the last time you need to do that

But don't hesitate to ask on the discord if you have problem, it s easier than create an issue on the github, and you will find at least someone to guid you on the good direction.
It s forbidden hightlight someone, but can PM me too.

[jamessw]

Hi! I have the same issue right now. I hope to find the solution in this thread...

[mknops]

Hi,

Well, if your issues is truely identical do not hesitate to follow Thorgal789's post/instruction. It worked flawlessly in my case.

Regards,

Michel