Conbee II "no firmware version" after updating Raspi from Bullseye to Bookwork

newbiech · July 18, 2025, 10:49am

I just updated from a working Bullseye environment to Bookworm with the existing Deconz/Phoscon/Homebridge installation on my Raspi 4. Everything went well so far and all KNX-devices are functional within Homebridge. However, it looks like my Raspi lost the connection to the attached Conbee II.

pi@homebridge:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@homebridge:~ $ usb-devices 

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 1
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=05.10
S:  Manufacturer=Linux 5.10.103-v8+ xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:01:00.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 4
D:  Ver= 2.10 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=2109 ProdID=3431 Rev=04.21
S:  Product=USB2.0 Hub
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms

T:  Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#=  4 Spd=12  MxCh= 0
D:  Ver= 2.01 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1cf1 ProdID=0030 Rev=01.00
S:  Manufacturer=dresden elektronik ingenieurtechnik GmbH
S:  Product=ConBee II
S:  SerialNumber=DE2434785
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=(none)
E:  Ad=83(I) Atr=03(Int.) MxPS=  64 Ivl=16ms
I:  If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=(none)
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 4
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev=05.10
S:  Manufacturer=Linux 5.10.103-v8+ xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:01:00.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=12ms

pi@homebridge:~ $ ls -l /dev/ttyA*
crw-rw---- 1 root dialout 204, 64 Jul 18 12:45 /dev/ttyAMA0

pi@homebridge:~ $ sudo GCFFlasher_internal -l
no devices found

pi@homebridge:~ $ ls -la /dev/serial/by-id/
ls: cannot access '/dev/serial/by-id/': No such file or directory

I have backup files, of course, what enables me to revert to Bullseye but I would rather make it work on Bookworm.

Anyone who can give a helping hand?

Smanar · July 18, 2025, 1:43pm

Strange GCFFlasher_internal see nothing, you have tried tu unplug/replug the gateway ?

newbiech · July 18, 2025, 2:28pm

Just did that (again):

pi@homebridge:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 014: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@homebridge:~ $ ls -l /dev/ttyA*
crw-rw---- 1 root dialout 204, 64 Jul 18 16:22 /dev/ttyAMA0
pi@homebridge:~ $ sudo GCFFlasher_internal -l
no devices found
Path              | Serial      | Type
------------------+-------------+---------------
pi@homebridge:~ $

What I do not understand is why “lsusb” says the Conbee is present and registered as “ttyAMA0” while GCFFlasher_internal seems to recognize any device at all.

Maybe any issue with the USB port settings within Bookworm? How can I verify?

Is there any way to verify whether ttyAMA0 is the Conbee II at all?

Smanar · July 18, 2025, 3:12pm

Are you in the dialout group ?

pi@raspberrypi:~ $ id $user
uid=1000(pi) gid=1000(pi) groupes=1000(pi),4(adm),20(dialout),24(cdrom),27(sudo),29(audio),44(video),46(plugdev),60(games),100(users),105(input),109(netdev),117(lpadmin),997(gpio),998(i2c),999(spi)

newbiech · July 18, 2025, 3:33pm

looks like:

pi@homebridge:~ $ id $user
uid=1000(pi) gid=1000(pi) groups=1000(pi),4(adm),20(dialout),24(cdrom),27(sudo),29(audio),44(video),46(plugdev),60(games),100(users),105(input),109(netdev),112(bluetooth),997(gpio),998(i2c),999(spi)

newbiech · July 18, 2025, 6:46pm

I googled too much on possible root causes and got totally lost meanwhile. Maybe something is wrong with udev?

pi@homebridge:~ $ apt policy udev
udev:
  Installed: 252.38-1~deb12u1
  Candidate: 252.38-1~deb12u1
  Version table:
 *** 252.38-1~deb12u1 500
        500 http://security.debian.org/debian-security bookworm-security/main armhf Packages
        100 /var/lib/dpkg/status
     252.36-1~deb12u1 500
        500 http://deb.debian.org/debian bookworm/main armhf Packages
pi@homebridge:~ $

manup · July 18, 2025, 8:05pm

I wonder if some other service does access the device

Can you try:

GCFFlasher_internal -d /dev/ttyACM0 -c -x 3

(deCONZ must be closed before)

If that connects there should be some logged messages every ~10 seconds.

manup · July 18, 2025, 8:07pm

And to get more info about the device you can use following command:

udevadm info /dev/ttyACM0

newbiech · July 18, 2025, 8:37pm

ttyACM0 appears to be not present. See above. Looks like the Conbee is device ttyAMA0.

pi@homebridge:~ $ udevadm info /dev/ttyACM0
Unknown device "/dev/ttyACM0": No such device
pi@homebridge:~ $ udevadm info /dev/ttyAMA0
P: /devices/platform/soc/fe201000.serial/tty/ttyAMA0
M: ttyAMA0
R: 0
U: tty
D: c 204:64
N: ttyAMA0
L: 0
S: serial1
E: DEVPATH=/devices/platform/soc/fe201000.serial/tty/ttyAMA0
E: DEVNAME=/dev/ttyAMA0
E: MAJOR=204
E: MINOR=64
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=2968693
E: ID_MM_CANDIDATE=1
E: DEVLINKS=/dev/serial1
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

pi@homebridge:~ $

pi@homebridge:~ $ ls -l /dev/serial1 
lrwxrwxrwx 1 root root 7 Jul 18 12:05 /dev/serial1 -> ttyAMA0

manup · July 19, 2025, 12:50am

Ah I see, the /dev/ttyAMA0 is not the ConBee but the Raspberry Pi UART / serial lines.
So the question is why the system doesn’t create the /dev/ttyACM* device names.

Strange is that the USB device is seen by the os seems to be found as can be seen in lsusb.

Bus 001 Device 014: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]

newbiech · July 19, 2025, 3:38pm

Any idea what to do? It appears to be somewhat of a Debian/Bookworm issue. But I have no clue at all how to solve this.