deCONZ/Phoscon reports Firmware - Not connected

Hi! I have Hassio v0.97.2 installed on a PC with the deCONZ plugin v3.1 and a Conbee 2 USB stick. Problem is the Phoscon app reports “Firmware Not connected” in the settings, and I cannot add lights, sensors etc. The stick works fine under the deCONZ app on a win10 computer, and reports correct firmware version. The hardware report in Hassio reports /dev/ttyACM0, and the config is:
“device”: “/dev/ttyACM0”,
“vnc_password”: “”

I had to set the deCONZ API backend network to port 80 to be able to access the Phoscon app. The addon log is enclosed below. Any ideas on what to do next? Thanks!

[16:24:01] INFO: Starting VNC server…
[16:24:05] INFO: Starting the deCONZ gateway…
[16:24:05] INFO: Running the deCONZ OTA updater…
[16:24:05] INFO: Running the IKEA OTA updater…
[16:24:05] INFO: Running discovery task…
[16:24:05] INFO: Success send discovery information to Home Assistant
[16:24:05] INFO: deCONZ is set up and running!
libpng warning: iCCP: known incorrect sRGB profile
16:24:05:790 HTTP Server listen on address, port: 80, root: /usr/share/deCONZ/webapp/
16:24:05:867 CTRL. 3.22.016:24:05:902 COM: /dev/ttyACM0 / serialno:
16:24:05:902 COM: --dev: /dev/ttyACM0 (ConBee II)
16:24:05:902 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
16:24:05:965 parent process bash
16:24:05:966 gw run mode: docker/hassio
16:24:05:966 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
16:24:05:967 DB sqlite version 3.22.0
16:24:05:967 DB PRAGMA page_count: 30
16:24:05:967 DB PRAGMA page_size: 4096
16:24:05:967 DB PRAGMA freelist_count: 0
16:24:05:967 DB file size 122880 bytes, free pages 0
16:24:05:967 DB PRAGMA user_version: 6
16:24:05:967 DB cleanup
16:24:05:969 DB create temporary views
16:24:05:973 don’t close database yet, keep open for 900 seconds
16:24:05:975 started websocket server at port 40860
16:24:05:976 discovery updated announce interval to 10 minutes
16:24:05:977 found node plugin: - REST API Plugin
16:24:05:979 found node plugin: - Signal Monitor Plugin
16:24:06:379 found node plugin: - STD OTAU Plugin
16:24:06:396 COM: /dev/ttyACM0 / serialno:
16:24:06:396 COM: --dev: /dev/ttyACM0 (ConBee II)
16:24:06:686 Device firmware version 0x264A0700
16:24:06:692 unlocked max nodes: 200
16:24:06:806 Device protocol version: 0x010B
16:24:06:814 new node - ext: 0x00212effff04884c, nwk: 0x0000
16:24:06:888 Current channel 11
16:24:06:914 CTRL ANT_CTRL 0x03
16:24:10:832 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26490700.bin.GCF
16:24:10:832 GW firmware version: 0x264a0700
16:24:10:832 GW firmware version is up to date: 0x264a0700
16:24:11:150 Announced to internet
16:24:11:824 don’t close database yet, keep open for 900 seconds
16:24:35:613 created username: 7BA154375B, devicetype: Phoscon#B1600x758
16:24:40:826 don’t close database yet, keep open for 900 seconds
16:24:44:615 scan finished
16:28:10:831 GW firmware version: 0x264a0700
16:28:10:831 GW firmware version is up to date: 0x264a0700
16:32:10:831 GW firmware version: 0x264a0700
16:32:10:831 GW firmware version is up to date: 0x264a0700
16:34:06:173 Announced to internet

Conbee2 is on ACM1

It doesnt look like the serial number is reported 16:24:06:396 COM: /dev/ttyACM0 / serialno:

Thanks! I don’t have /dev/ttyACM1. It could seems like the Conbee is mapped to /dev/ttyACM0 though? When I run ‘udevadm info -q property --export -p /sys/bus/usb/devices/usb1/1-1/1-1:1.0/tty/ttyACM0’, I do get:

DEVLINKS=’/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1997237-if00 /dev/serial/by-path/pci-0000:00:01.2-usb-0:1:1.0’
ID_VENDOR_FROM_DATABASE=‘Dresden Elektronik’

Is it a problem that it maps to ACM0?

I have no idea. Since you can map it which ever way you want I guess not

Thanks any way. I did connect a serial terminal to /dev/ttyACM0, only getting rubbish in return. But, for some magic reason it could seems to have brouht the stick to life. It seems sluggish, but at least Im able to connect and could add one sensor.

Try putting it on a usb extension cord

Helped a lot :slight_smile: