Installing instructions DeConz -> apt key depreciated

deCONZ General Support
1

Nuc7 running Debian Bullseye KVM HomeAssistant

Ubuntu and raspbian are forks so Deconz should… run.

Used Phoscon Webpage CLI sequence conbee2/install#ubuntu

Result…

> aum@Nuc-7:~$ wget -O - xxxx://phoscon.de/apt/deconz.pub.key |            sudo apt-key add -
> --2023-05-19 17:17:18--  xxxx://phoscon.de/apt/deconz.pub.key
> Resolving phoscon.de (xxxx)... 144.76.96.194
> Connecting to phoscon.de (xxxx)|144.76.96.194|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 1692 (1.7K) [application/octet-stream]
> Saving to: ‘STDOUT’
> 
> -                   100%[===================>]   1.65K  --.-KB/s    in 0s      
> 
> 2023-05-19 17:17:18 (225 MB/s) - written to stdout [1692/1692]
> 
> Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
> OK

(OK… the xxxx’s are to bypass the 2 link limit in a posting …)

Appears to me that Phoscon will need to update their installation CLI’s because of a change in APT KEY behavior ???

I managed to get Deconz running, but it does NOT detect the ConBee2 stick. Probably because of this key problem?

Also the ConBee2 stick appears not to mount properly.

aum@Nuc-7:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 001 Device 005: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 

aum@Nuc-7:~$ ls -l /dev/ttyACM*
crw-rw---- 1 root dialout 166, 0 May 19 17:29 /dev/ttyACM0

aum@Nuc-7:~$ ls /dev/serial/*
pci-0000:00:15.0-usb-0:3:1.0

It appears to me that somehow its not added to /dev/serial ?

I would like to connect the ConBee 2 in a Virtual KVM to Homeassistant too. I have tried several solutions in this and the Homeassistant forum. Occasionally it does show up in Homeassistant but when installing it fails, it cant find the ConBee2. Some of these postings mention a link to /dev/serial… but in my case no entry is detected.

ConBee2 confirmed working and has been updated to latest firmware on WIN10 machine.

I got the feeling the two problems are related that is why I post them together.

Could somebody shed a light on this perhaps. I’m really looking fwd to use DeConz and the ConBee2 in my network because of the mapping feature. Thank you.

2

Don’t know for apt key, but for /dev/serial it’s certainly related to 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

1 Like
3

@BabelsYou,

:pray: :pray: :pray:

Your published link made the difference. Near the end of this posting Kenneth Lavrsen writes an “ear-smoking” :face_with_hand_over_mouth: posting about Debian having messed up the update of the /usr/lib/udev/rules.d directory 60-serial.rules file very unfortunately, causing a lot of HAVOC… . Probably not only at Dresden Electronics…

I backed up the old 60-serial.rules file and replaced it with his posting (and made a copy of that one too just in case it gets written over with update with the wrong one…). Rebooted and :yum:

aum@Nuc-7:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 001 Device 002: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
aum@Nuc-7:~$ ls -l /dev/ttyACM*
crw-rw---- 1 root dialout 166, 0 May 20 14:12 /dev/ttyACM0
aum@Nuc-7:~$ ls /dev/serial/*
/dev/serial/by-id:
usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxxxxx-if00

/dev/serial/by-path:
pci-0000:00:15.0-usb-0:3:1.0

The ConBee2 showed up properly and was immediately recognized and running by Deconz.

Adjusted the serial xml in KVM to:

<serial type="dev">
  <source path="/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxxxxx-if00"/>
  <target type="usb-serial" port="1">
    <model name="usb-serial"/>
  </target>
  <alias name="serial0"/>
  <address type="usb" bus="0" port="4"/>
</serial>

Shutdown and restarted KVM (important) than VM’ed HAOS and Homeassistant. In HA uninstalled DeConz first and reinstalled with

/dev/serial/by-id/usb-QEMU_QEMU_USB_SERIAL_1-0000:00:03.7-4-if00-port0

as the ConBee2 source.

All up and running now :yum: :pray:

2 Likes
4

Related to the message from apt…
I had already suggested in February to the support to adjust the text for the installation, because I also got the message - permanently at each apt update…

APT-Repository für deCONZ konfigurieren:

Auflösen des Hostnamens phoscon .de (phoscon .de) … Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).

Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
W: http://phoscon.de/apt/deconz/dists/jammy/InRelease: Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/trusted.gpg), siehe den Abschnitt MISSBILLIGUNG in apt-key(8) für Details.

Diese Warnung kommt nun immer bei jedem “apt update”!

5

Hier muss es heißen "sudo curl http://phoscon.de/apt/deconz.pub.key | sudo -H gpg --dearmor -o /etc/apt/trusted.gpg.d/deconz.pub.key.gpg

" statt “apt-key add”

6

Can you translate to English?