I’m using a ConBee II dongle on a raspi 4, raspian bullseye, all updates. My setup worked fine for a month until I updated today raspian by “sudo apt update” and “sudo apt upgrade”.
Now I have Phoscon 2.17.01 and deCONZ 2.17.1. The Conbee 2 firmware is 26780700.
So I think everything is up to date!
Phoscon is working fine and shows the gateway and sensors and so on, but deCONZ is always hanging in the startup phase while connecting to the device. The drop-down box under the field “connect to device” looks fine and shows my ConBee II dongle.
So deCONZ does not really hang but the dongle doesn’t get connected and I can’t do anything meaningful with deCONZ. Maybe the log will help? These lines are repeating every few seconds.
I checked the device names and they are OK.
Any ideas how to proceed?
Thanks and bye,
22:48:25:479 wait reconnect 4 seconds
22:48:26:479 wait reconnect 3 seconds
22:48:27:479 wait reconnect 2 seconds
22:48:27:979 Daylight now: dusk, status: 210, daylight: 0, dark: 1
22:48:28:479 wait reconnect 1 seconds
22:48:28:586 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
22:48:28:587 COM: /dev/ttyAMA0 : (0x0000/0x0000)
22:48:28:588 dev /dev/ttyAMA0 (/dev/ttyAMA0)
22:48:28:589 COM: /dev/ttyUSB0 : USB Serial (0x1A86/0x7523)
22:48:28:591 failed open com status: (-3), path: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2497667-if00
22:48:29:480 wait reconnect 5 seconds
22:48:29:567 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
22:48:29:568 COM: /dev/ttyAMA0 : (0x0000/0x0000)
22:48:29:569 dev /dev/ttyAMA0 (/dev/ttyAMA0)
22:48:29:569 COM: /dev/ttyUSB0 : USB Serial (0x1A86/0x7523)
22:48:29:979 failed to reconnect to network try=3
It’s strange Phoscon is working and not deconz.
Can you check if you have a firmware number displayed on phoscon/gateway.
Can you check too if you haven’t 2 deconz instances ? the headless and the desktop one for exemple ?
ps ax | grep deCONZ
Phoscon looks quite normal:
pi@raspiwetter:~ $ ps ax | grep deCONZ
413 ? Ss 1:52 /bin/bash /usr/bin/deCONZ-update2.sh
415 ? Ss 5:16 /bin/bash /usr/bin/deCONZ-WIFI2.sh
418 ? Ssl 10:53 /usr/bin/deCONZ -platform minimal --http-port=80
31559 pts/0 S+ 0:00 grep --color=auto deCONZ
But I found a workaround: When deCONZ trys to connect to the ConBee II dongle you have to plug it on and off a few times. It redetects the dongle then and after 1-3 trys it will connect. Strange…
After that deCONZ works as expected, but if you restart deCONZ the problem reappears.
When you say deconz, you mean the GUI application ? if yes, its because you already have the headless version running
/usr/bin/deCONZ -platform minimal --http-port=80
You can’t have the headless and the desktop version in same time.
OK, I think I understand now. Phoscon is the headless version, running on port 80 and deCONZ is the GUI version. But for me these two programs are completely different and so I mixed the terms “headless” and “gui”. This is a little bit misleading as there’s not such thing like a headless deCONZ version, right?
So if I’m stopping the deconz service (which presents the Phoscon app), then the deCONZ version is running without a problem.
Thanks and bye,
No. deCONZ is the program (that runs as a service) that does all the magic. Phoscon is the web application that is provided by deCONZ. Once you stop deCONZ, Phoscon is offline as well.
deCONZ can be run in two modes:
You should never runs deCONZ in both modes in parallel, that is asking for trouble.
The recommendation is to run deCONZ in normal mode, i.e. not headless, even if your raspberry pi is not connected to a monitor. You can still access the deCONZ GUI using tools like VNC viewer. Only the deCONZ GUI will allow you to perform firmware updates, or show you the network layout of your ZigBee network.