@Thomas-Braun Bei mir tritt leider das selbe Problem auf.
Ich habe am Wochenende auf meinem PI ein apt update-upgrade durchgeführt und nach einem reboot bekommt der Zigbee-Adapter keine Verbindung mehr zum Conbee II-Stick.
Beim einem Neustart vom Zigbee-Adapter bekomme ich folgende Logeinträge.
zigbee.0 2023-05-02 21:10:07.494 error Error herdsman start
zigbee.0 2023-05-02 21:10:07.493 error Failed to start Zigbee
zigbee.0 2023-05-02 21:10:07.492 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2255878-if00'"
zigbee.0 2023-05-02 21:10:07.244 info Installed Version: iobroker.zigbee@1.8.10
zigbee.0 2023-05-02 21:10:07.196 debug Starting zigbee-herdsman...
zigbee.0 2023-05-02 21:10:07.195 info Starting Zigbee npm ...
zigbee.0 2023-05-02 21:10:07.193 info Try to reconnect. 1 attempts left
zigbee.0 2023-05-02 21:09:57.211 debug Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2023_05_02-21_09_56.tar.gz success
zigbee.0 2023-05-02 21:09:57.194 info Installed Version: iobroker.zigbee@1.8.10
zigbee.0 2023-05-02 21:09:57.189 error Error herdsman start
zigbee.0 2023-05-02 21:09:57.188 error Failed to start Zigbee
zigbee.0 2023-05-02 21:09:57.187 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2255878-if00'"
zigbee.0 2023-05-02 21:09:56.316 debug Starting zigbee-herdsman...
zigbee.0 2023-05-02 21:09:56.313 info Starting Zigbee npm ...
zigbee.0 2023-05-02 21:09:56.310 info delete old Backup files. keep only last 10
zigbee.0 2023-05-02 21:09:56.206 debug Using zigbee-herdsman with settings: {"network":{"panID":6574,"extendedPanID":[175,221,221,221,221,221,221,221],"channelList":[11],"networkKey":[1,3,5,7,9,7,159,175,0,194,4,6,8,10,12,154]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2255878-if00","adapter":"deconz"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}}
zigbee.0 2023-05-02 21:09:56.153 info starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.16.0, js-controller: 4.0.24
zigbee.0 2023-05-02 21:09:55.534 debug Plugin sentry Initialize Plugin (enabled=true)
zigbee.0 2023-05-02 21:09:47.429 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
zigbee.0 2023-05-02 21:09:47.428 debug Plugin sentry destroyed
zigbee.0 2023-05-02 21:09:47.427 info terminating
zigbee.0 2023-05-02 21:09:47.389 info Zigbee: disabling joining new devices.
zigbee.0 2023-05-02 21:09:47.361 debug DeviceAvailability:Publish LQ for 0x54ef4410003e3f2e = 0
zigbee.0 2023-05-02 21:09:47.341 debug DeviceAvailability:Publish available for 0x54ef4410003e3f2e = false
zigbee.0 2023-05-02 21:09:47.296 debug DeviceAvailability:Publish LQ for 0x54ef4410003e431c = 0
zigbee.0 2023-05-02 21:09:47.285 debug DeviceAvailability:Publish available for 0x54ef4410003e431c = false
zigbee.0 2023-05-02 21:09:47.276 info cleaned everything up...
zigbee.0 2023-05-02 21:09:47.273 info Got terminate signal TERMINATE_YOURSELF
Zu meinem System:
======================= SUMMARY =======================
v.2023-04-16
Operatingsystem: Debian GNU/Linux 11 (bullseye)
Kernel: 6.1.21-v8+
Installation: Native
Timezone: Europe/Berlin (CEST, +0200)
User-ID: 1000
X-Server: false
Boot Target: graphical.target
Pending OS-Updates: 0
Pending iob updates: 0
Nodejs-Installation: /usr/bin/nodejs v18.16.0
/usr/bin/node v18.16.0
/usr/bin/npm 9.5.1
/usr/bin/npx 9.5.1
Recommended versions are nodejs 18.x.y and npm 9.x.y
Your nodejs installation is correct
MEMORY:
total used free shared buff/cache available
Mem: 3.8G 2.0G 119M 2.0M 1.7G 1.8G
Swap: 99M 29M 70M
Total: 3.9G 2.0G 190M
Active iob-Instances: 25
Active repo(s): stable
ioBroker Core: js-controller 4.0.24
admin 6.3.5
ioBroker Status: iobroker is running on this host.
Objects type: jsonl
States type: jsonl
Status admin and web instance:
+ system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin
Objects: 16038
States: 14916
Size of iob-Database:
15M /opt/iobroker/iobroker-data/objects.jsonl
26M /opt/iobroker/iobroker-data/states.jsonl
=================== END OF SUMMARY ====================
apt policy usb.ids und udev habe ich auch ausgeführt:
MaB@iobroker:~ $ apt policy usb.ids
usb.ids:
Installiert: (keine)
Installationskandidat: 2023.01.16-0+deb11u1
Versionstabelle:
2023.01.16-0+deb11u1 500
500 http://deb.debian.org/debian bullseye/main arm64 Packages
500 http://deb.debian.org/debian bullseye/main armhf Packages
MaB@iobroker:~ $ apt policy udev
udev:
Installiert: 247.3-7+deb11u2
Installationskandidat: 247.3-7+deb11u2
Versionstabelle:
*** 247.3-7+deb11u2 500
500 http://deb.debian.org/debian bullseye/main arm64 Packages
100 /var/lib/dpkg/status
MaB@iobroker:~ $ ls -la /dev/serial/by-id
ls: Zugriff auf '/dev/serial/by-id' nicht möglich: Datei oder Verzeichnis nicht gefunden
MaB@iobroker:~ $
Auch habe ich mir den Bugreport den @Marc-Berg gepostet hat angesehen. Nur fehlen mir dazu die notwendigen Linux-Kenntnisse um eine mögliche Lösung zu finden. Das einzige was ich gefunden habe ist, dass bei mir die in einem Link erwähnte Datei "60-serial.rules" leer ist.
Ich wäre dankbar wenn ihr mir weiterhelfen könnt.
Gruß Michael