Conbee II does not connect

bokkie · August 30, 2023, 8:50pm

I just got a new Raspberry pi 4B and switched from my old 4 to this one. Did a clean new install on a SSD, and when I try to connect the Conbee2 stick it does not react. For example manual firmware update fails.
lsusb shows the stick connected, I’ve got an official 5V Raspi power supply. When I try the stick again on the old Raspi 4 it isn’t working there anymore… Tried with stick on USB2.0 and with usb extension cable.

This is my log:

22:17:52:753 auto connect com /dev/ttyS0
22:17:56:929 GW update firmware not found:
22:17:57:199 Announced to internet https://phoscon.de/discover
22:17:57:199 discovery server date: Wed, 30 Aug 2023 20:17:57 GMT
22:17:57:199     local time seems to be ok
22:17:57:199 discovery reply doesn't contain valid version info
22:18:00:076 DEV Tick.Init: booted after 8000 seconds
22:18:02:084 Daylight now: nauticalDusk, status: 220, daylight: 0, dark: 1
22:18:05:988 device disconnected reason: 1, device index: 0
22:18:06:584 wait reconnect 15 seconds
22:18:06:627 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:18:06:627 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:18:06:627 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:18:06:627 dev /dev/ttyS0 (/dev/ttyS0)
22:18:07:126 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:18:07:127 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:18:07:127 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:18:07:127 dev /dev/ttyS0 (/dev/ttyS0)
22:18:07:127 GW firmware update select /dev/ttyS0 device
22:18:07:127 GW update firmware not found:
22:18:07:584 wait reconnect 14 seconds
22:18:08:584 wait reconnect 13 seconds
22:18:09:584 wait reconnect 12 seconds
22:18:10:584 wait reconnect 11 seconds
22:18:11:584 wait reconnect 10 seconds
22:18:12:084 Daylight now: nauticalDusk, status: 220, daylight: 0, dark: 1
22:18:12:584 networkState: CC_ReconnectNetwork
22:18:12:584 start reconnect to network
22:18:12:584 wait reconnect 9 seconds
22:18:13:584 wait reconnect 8 seconds
22:18:14:584 wait reconnect 7 seconds
22:18:15:584 wait reconnect 6 seconds
22:18:16:584 wait reconnect 5 seconds
22:18:17:126 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:18:17:127 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:18:17:127 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:18:17:127 dev /dev/ttyS0 (/dev/ttyS0)
22:18:17:127 GW firmware update select /dev/ttyS0 device
22:18:17:127 GW update firmware not found:
22:18:17:584 wait reconnect 4 seconds
22:18:17:834 failed to reconnect to network try=1
22:18:18:584 wait reconnect 3 seconds
22:18:19:584 wait reconnect 2 seconds
22:18:20:584 wait reconnect 1 seconds
22:18:20:627 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:18:20:627 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:18:20:627 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:18:20:627 dev /dev/ttyS0 (/dev/ttyS0)
22:18:20:628 auto connect com /dev/ttyS0
22:18:22:084 Daylight now: nauticalDusk, status: 220, daylight: 0, dark: 1
22:18:23:084 try to reconnect to network try=2
22:18:27:084 GW update firmware not found:
22:18:28:084 try to reconnect to network try=3
22:18:31:588 device disconnected reason: 1, device index: 0
22:18:32:084 Daylight now: nauticalDusk, status: 220, daylight: 0, dark: 1
22:18:32:584 wait reconnect 15 seconds
22:18:32:627 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:18:32:627 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:18:32:627 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:18:32:627 dev /dev/ttyS0 (/dev/ttyS0)
22:18:33:084 failed to reconnect to network try=4
22:18:33:584 wait reconnect 14 seconds
22:18:34:584 wait reconnect 13 seconds
22:18:35:584 wait reconnect 12 seconds
22:18:36:584 wait reconnect 11 seconds
22:18:37:126 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:18:37:126 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:18:37:127 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:18:37:127 dev /dev/ttyS0 (/dev/ttyS0)
22:18:37:127 GW firmware update select /dev/ttyS0 device
22:18:37:127 GW update firmware not found:
22:18:37:584 wait reconnect 10 seconds
22:18:38:084 failed to reconnect to network try=5
22:18:43:584 wait reconnect 4 seconds
22:18:44:584 wait reconnect 3 seconds
22:18:45:584 wait reconnect 2 seconds
22:18:46:584 wait reconnect 1 seconds
22:18:46:626 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:18:46:627 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:18:46:627 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:18:46:627 dev /dev/ttyS0 (/dev/ttyS0)
22:18:46:627 auto connect com /dev/ttyS0
22:18:47:129 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:18:47:129 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:18:47:129 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:18:47:129 dev /dev/ttyS0 (/dev/ttyS0)
22:18:47:129 GW firmware update select /dev/ttyS0 device
22:18:47:140 GW update firmware not found:
22:18:48:084 failed to reconnect to network try=7
22:18:52:084 DB save zll database items 0x00000084
22:18:52:084 DB sql exec REPLACE INTO auth (apikey, devicetype, createdate, lastusedate, useragent) VALUES ('CA0ABC837F', 'Phoscon>
22:18:52:085 DB sql exec REPLACE INTO sensors (sid, name, type, modelid, manufacturername, uniqueid, swversion, state, config, fin>
22:18:52:092 DB saved in 8 ms
22:18:52:093 Daylight now: nauticalDusk, status: 220, daylight: 0, dark: 1
22:18:53:084 try to reconnect to network try=8
22:18:57:084 GW update firmware not found:
22:18:58:084 try to reconnect to network try=9
22:18:58:586 device disconnected reason: 1, device index: 0
22:18:59:584 wait reconnect 15 seconds
22:18:59:629 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:18:59:629 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:18:59:629 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:18:59:629 dev /dev/ttyS0 (/dev/ttyS0)
22:19:00:584 wait reconnect 14 seconds
22:19:01:584 wait reconnect 13 seconds
22:19:02:084 Daylight now: nauticalDusk, status: 220, daylight: 0, dark: 1
22:19:02:584 wait reconnect 12 seconds
22:19:03:084 failed to reconnect to network try=10
22:19:03:584 wait reconnect 11 seconds
22:19:04:584 wait reconnect 10 seconds
22:19:05:584 wait reconnect 9 seconds
22:19:06:584 wait reconnect 8 seconds

22:20:56:584 wait reconnect 1 seconds
22:20:56:627 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:20:56:627 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:20:56:627 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:20:56:627 dev /dev/ttyS0 (/dev/ttyS0)
22:20:56:628 auto connect com /dev/ttyS0
22:20:57:126 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:20:57:126 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:20:57:126 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:20:57:126 dev /dev/ttyS0 (/dev/ttyS0)
22:20:57:126 GW firmware update select /dev/ttyS0 device
22:20:57:135 GW update firmware not found:
22:21:00:084 reconnect network failed, try later
22:21:00:584 networkState: CC_ReconnectNetwork
22:21:00:584 start reconnect to network
22:21:02:084 Daylight now: nauticalDusk, status: 220, daylight: 0, dark: 1
22:21:05:835 try to reconnect to network try=1
22:21:07:084 GW update firmware not found:
22:21:08:488 device disconnected reason: 1, device index: 0
22:21:08:584 wait reconnect 15 seconds
22:21:08:627 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:21:08:627 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:21:08:627 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:21:08:627 dev /dev/ttyS0 (/dev/ttyS0)
22:21:09:584 wait reconnect 14 seconds
22:21:10:584 wait reconnect 13 seconds
22:21:11:083 failed to reconnect to network try=2
22:21:11:584 wait reconnect 12 seconds
22:21:12:084 Daylight now: nauticalDusk, status: 220, daylight: 0, dark: 1
22:21:12:584 wait reconnect 11 seconds
22:21:13:584 wait reconnect 10 seconds
22:21:14:584 wait reconnect 9 seconds
22:21:15:584 wait reconnect 8 seconds
22:21:16:084 failed to reconnect to network try=3
22:21:16:584 wait reconnect 7 seconds
22:21:17:127 COM: /dev/ttyACM0 :  (0x1106/0x3483)
22:21:17:127 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
22:21:17:127 COM: /dev/ttyS0 :  (0x0000/0x0000)
22:21:17:127 dev /dev/ttyS0 (/dev/ttyS0)
22:21:17:127 GW firmware update select /dev/ttyS0 device
22:21:17:127 GW update firmware

Mimiix · August 31, 2023, 6:35am

Hi, This level indicates the stick is removed. We often see that if the power is not sufficient. Additionally, this could also be in play: After a sudo apt update && sudo apt full-upgrade and a reboot deconz no longer connects to the conbee 2 · Issue #6937 · dresden-elektronik/deconz-rest-plugin · GitHub

bokkie · August 31, 2023, 7:02am

Thnx @Mimiix ! This sollution worked perfect for me:
deCONZ --dev=/dev/ttyACM0

bokkie · August 31, 2023, 7:46am

if the power is not sufficient, what adapter would you recommend

Mimiix · August 31, 2023, 7:52am

Are you still having issues?

Can you share logs after you changed the Path?

Is the SSD connected to it>?

bokkie · August 31, 2023, 8:04am

yep unfortunately…

my log:
edit: very short log, see below

Mimiix · August 31, 2023, 8:05am

Can you share some more? This is hardly the startup.

bokkie · August 31, 2023, 8:20am

true, here I have a new log: Debian Pastezone

Mimiix · August 31, 2023, 8:27am

It looks like the device switched again from location. You might want to look deeper in the git issue i mentioned before.

bokkie · August 31, 2023, 10:11am

I don’t get what you mean by that sorry
I did not change anything physically or in the software btw

Mimiix · August 31, 2023, 10:11am

After a sudo apt update && sudo apt full-upgrade and a reboot deconz no longer connects to the conbee 2 · Issue #6937 · dresden-elektronik/deconz-rest-plugin · GitHub This issue.

bokkie · August 31, 2023, 10:31am

I think the sollution might lie in this answer (https://github.com/dresden-elektronik/deconz-rest-plugin/issues/6937#issuecomment-1529697409) but no idea how to apply that upgrade

Mimiix · August 31, 2023, 10:41am

github.com/dresden-elektronik/deconz-rest-plugin

After a sudo apt update && sudo apt full-upgrade and a reboot deconz no longer connects to the conbee 2

opened 04:39AM - 01 May 23 UTC

closed 10:32AM - 12 May 23 UTC

Nastras

Bug report

## Describe the bug After a sudo apt update && sudo apt full-upgrade and a re…boot deconz no longer connects to the conbee 2. The problem exists has occurred on three different Raspberry Pi with deconz. The deconz window cannot be closed via the gui. There is a prompt to end the process. If this is confirmed with yes, the deconz window returns that the process is not responding. The window freezes. Raspberry Pi 4 Model B Rev 1.1 Debian GNU/Linux 11 (bullseye) Linux 6.1.21-v8+ deconz 2.21.02 ConBeeII_0x26780700.bin.GCF The following packages were installed: ![IMG_4413](https://user-images.githubusercontent.com/27686185/235407451-055acfe2-1fc8-4181-8d1d-2e37c3312a72.jpeg) ![IMG_4415](https://user-images.githubusercontent.com/27686185/235407613-b83e893b-d99e-4f81-b7de-0993a5426050.jpeg) ![IMG_4414](https://user-images.githubusercontent.com/27686185/235407616-9009bd13-8b8c-4281-9b42-9ac2c81d5458.jpeg)

This should give pointers.

bokkie · September 7, 2023, 8:32am

In the end, what worked for me (after hours of trying) was this:

cd /usr/lib/udev/rules.d/
mv 60-serial.rules 60-serial.rules.backup
sudo nano 60-serial.rules
copy + paste code beneath into new file,
then sudo reboot.
After the reboot the ‘serial/by-id’ was finally visible.

# do not edit this file, it will be overwritten on update

ACTION=="remove", GOTO="serial_end"
SUBSYSTEM!="tty", GOTO="serial_end"

SUBSYSTEMS=="usb", IMPORT{builtin}="usb_id", IMPORT{builtin}="hwdb --subsystem=usb"
SUBSYSTEMS=="pci", ENV{ID_BUS}=="", ENV{ID_BUS}="pci", \
  ENV{ID_VENDOR_ID}="$attr{vendor}", ENV{ID_MODEL_ID}="$attr{device}", \
  IMPORT{builtin}="hwdb --subsystem=pci"

# /dev/serial/by-path/, /dev/serial/by-id/ for USB devices
KERNEL!="ttyUSB[0-9]*|ttyACM[0-9]*", GOTO="serial_end"

SUBSYSTEMS=="usb-serial", ENV{.ID_PORT}="$attr{port_number}"

IMPORT{builtin}="path_id"
ENV{ID_PATH}=="?*",                   ENV{.ID_PORT}=="",   SYMLINK+="serial/by-path/$env{ID_PATH}"
ENV{ID_PATH_WITH_USB_REVISION}=="?*", ENV{.ID_PORT}=="",   SYMLINK+="serial/by-path/$env{ID_PATH_WITH_USB_REVISION}"
ENV{ID_PATH}=="?*",                   ENV{.ID_PORT}=="?*", SYMLINK+="serial/by-path/$env{ID_PATH}-port$env{.ID_PORT}"
ENV{ID_PATH_WITH_USB_REVISION}=="?*", ENV{.ID_PORT}=="?*", SYMLINK+="serial/by-path/$env{ID_PATH_WITH_USB_REVISION}-port$env{.ID_PORT}"

ENV{ID_BUS}=="", GOTO="serial_end"
ENV{ID_SERIAL}=="", GOTO="serial_end"
ENV{ID_USB_INTERFACE_NUM}=="", GOTO="serial_end"
ENV{.ID_PORT}=="", SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-if$env{ID_USB_INTERFACE_NUM}"
ENV{.ID_PORT}=="?*", SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-if$env{ID_USB_INTERFACE_NUM}-port$env{.ID_PORT}"

LABEL="serial_end"

OMR · October 14, 2023, 4:34pm

Thank you! Lifesaver
Happened on 32 bit bullseye after update/upgrade …