Zigbee v3.1.5 plötzlich keine Verbindung mehr
-
@Asgothian
Ne nicht nach dem UpdateAber es läuft wieder, ich glaube unter Bindings war ein Button zum Koppeln, seitdem läuft es.
@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
@Asgothian
Ne nicht nach dem UpdateAber es läuft wieder, ich glaube unter Bindings war ein Button zum Koppeln, seitdem läuft es.
Muss entweder nach update, oder es hat jemand gespielt. (Backup zurück gespielt oder ähnliches).
Der Haken ist mit dem Update 2.x auf 3.x dazu gekommen. Vielleicht hast du nach dem update einmal 'manuell' start gedrückt. Den Haken kann man nicht via Script / Binding / Sonstiges setzen / löschen. Der verschwindet also nicht 'von alleine'. Und auch nicht ohne das der Adapter neu gestartet wird, von demjenigen der den Haken entfernt.
A.
-
@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
@Asgothian
Ne nicht nach dem UpdateAber es läuft wieder, ich glaube unter Bindings war ein Button zum Koppeln, seitdem läuft es.
Muss entweder nach update, oder es hat jemand gespielt. (Backup zurück gespielt oder ähnliches).
Der Haken ist mit dem Update 2.x auf 3.x dazu gekommen. Vielleicht hast du nach dem update einmal 'manuell' start gedrückt. Den Haken kann man nicht via Script / Binding / Sonstiges setzen / löschen. Der verschwindet also nicht 'von alleine'. Und auch nicht ohne das der Adapter neu gestartet wird, von demjenigen der den Haken entfernt.
A.
-
@Asgothian das wird es gewesen sein.
Kann mir noch jemand sagen, warum mir noch nodejs 18.20.8 als empfohlene Version angezeigt wird?
@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
warum mir noch nodejs 18.20.8 als empfohlene Version angezeigt wird?
wo und wie?
bitte zeigen. -
@Thomas-Braun ```
========== Start marking the full check here ===========Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Ubuntu 22.04.5 LTS Static hostname: iobroker-ubuntu-22-04 Icon name: computer-vm Chassis: vm Virtualization: kvm Kernel: Linux 5.15.0-164-generic Architecture: x86-64 Hardware Vendor: QEMU Hardware Model: Standard PC _i440FX + PIIX, 1996_ OS is similar to: debian model name : Common KVM processor Docker : false Virtualization : kvm Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 09:44:40 up 1 day, 19:47, 2 users, load average: 1.10, 0.91, 0.79 CPU threads: 8 *** LIFE CYCLE STATUS *** Operating System codenamed 'jammy' is an aging Ubuntu release! Please upgrade to the latest LTS release 'noble' in due time! *** TIME AND TIMEZONES *** Local time: Mon 2026-01-26 09:44:40 CET Universal time: Mon 2026-01-26 08:44:40 UTC RTC time: Mon 2026-01-26 08:44:40 Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': user HOME=/home/user GROUPS=user adm cdrom sudo dip plugdev lxd iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty System is booting into 'graphical.target'. Usually a server is running in 'multi -user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix ' *** MEMORY *** total used free shared buff/cache available Mem: 1.8G 1.4G 251M 0.0K 208M 222M Swap: 3.0G 1.7G 1.3G Total: 4.8G 3.0G 1.5G Active iob-Instances: 26 1811 M total memory 1351 M used memory 506 M active memory 790 M inactive memory 251 M free memory 41 M buffer memory 166 M swap cache 2952 M total swap 1670 M used swap 1282 M free swap *** top - Table Of Processes *** top - 09:44:41 up 1 day, 19:47, 2 users, load average: 1.10, 0.91, 0.79 Tasks: 160 total, 3 running, 157 sleeping, 0 stopped, 0 zombie %Cpu(s): 25.3 us, 24.0 sy, 0.0 ni, 38.7 id, 0.0 wa, 0.0 hi, 1.3 si, 10.7 st MiB Mem : 1811.3 total, 250.5 free, 1351.6 used, 209.1 buff/cache MiB Swap: 2953.0 total, 1282.6 free, 1670.4 used. 221.8 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on tmpfs tmpfs 632M 1.1M 631M 1% /run /dev/mapper/ubuntu--vg-ubuntu--lv ext4 30G 16G 13G 56% / tmpfs tmpfs 3.1G 0 3.1G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock /dev/sda2 ext4 2.0G 254M 1.6G 14% /boot tmpfs tmpfs 642M 4.0K 642M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Jan 24 13:57:41 2026] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [Sat Jan 24 13:57:43 2026] EXT4-fs (dm-0): re-mounted. Opts: (null). Quota mode: none. [Sat Jan 24 13:57:45 2026] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/ubuntu--vg-ubuntu--lv ext4 rw,relatime |-/snap/core20/2682 /dev/loop0 squashfs ro,nodev,relatime ,errors=continue |-/snap/core20/2686 /dev/loop1 squashfs ro,nodev,relatime ,errors=continue |-/snap/lxd/36558 /dev/loop2 squashfs ro,nodev,relatime ,errors=continue |-/snap/lxd/36918 /dev/loop3 squashfs ro,nodev,relatime ,errors=continue |-/snap/snapd/25577 /dev/loop4 squashfs ro,nodev,relatime ,errors=continue |-/snap/snapd/25935 /dev/loop5 squashfs ro,nodev,relatime ,errors=continue `-/boot /dev/sda2 ext4 rw,relatime Files in neuralgic directories: /var: 2.5G /var/ 1.7G /var/lib 970M /var/lib/snapd 780M /var/lib/snapd/cache 589M /var/log Archived and active journals take up 557.5M in the file system. /opt/iobroker/backups: 6.6M /opt/iobroker/backups/ 4.0K /opt/iobroker/backups/redistmp /opt/iobroker/iobroker-data: 606M /opt/iobroker/iobroker-data/ 425M /opt/iobroker/iobroker-data/files 108M /opt/iobroker/iobroker-data/backup-objects 67M /opt/iobroker/iobroker-data/files/echarts.admin 61M /opt/iobroker/iobroker-data/files/echarts The five largest files in iobroker-data are: 53M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map 26M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41c ee985.js.map 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.j s.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please alw ays prefer the links 'by-id': /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DA P_L43002RW-if03 /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DA P_L43002RW-if00 *** ZigBee Settings *** HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: /dev/ttyACM0 Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.22.0 /usr/bin/node v22.22.0 /usr/bin/npm 10.9.4 /usr/bin/npx 10.9.4 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.22.0-1nodesource1 Candidate: 22.22.0-1nodesource1 Version table: *** 22.22.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 12.22.9~dfsg-1ubuntu3.6 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Pac kages 500 http://de.archive.ubuntu.com/ubuntu jammy-security/universe amd64 Pa ckages 12.22.9~dfsg-1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: iobroker slave iobroker slave (version: 7.0.7, hostname: iobroker slave, alive, uptime: 157613) iobroker-ubuntu-22-04 iobroker-ubuntu-22-04 (version: 7.0.7, hostname: iobroker-ubuntu-22-04, alive, uptime: 157640) Core adapters versions js-controller: 7.0.7 admin: 7.7.22 javascript: 9.0.11 nodejs modules from github: 1 | +-- samsungtv@0.0.0 (git+https://git@github.com/luca-saggese/samsungtv.git#7fc20107455414e2afb94022682e0787e8635550) Adapter State + system.adapter.admin.1 : admin : iobroker-ubuntu-22-04 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : iobroker-ubuntu-22-04 - enabled system.adapter.backitup.0 : backitup : iobroker-ubuntu-22-04 - disabled system.adapter.bring.0 : bring : iobroker-ubuntu-22-04 - disabled + system.adapter.discovery.0 : discovery : iobroker-ubuntu-22-04 - enabled system.adapter.dwd.0 : dwd : iobroker-ubuntu-22-04 - enabled system.adapter.echarts.0 : echarts : iobroker-ubuntu-22-04 - disabled system.adapter.ecovacs-deebot.0 : ecovacs-deebot : iobroker-ubuntu-22-04 - disabled system.adapter.flot.0 : flot : iobroker-ubuntu-22-04 - disabled + system.adapter.hass.0 : hass : iobroker-ubuntu-22-04 - enabled, port: 8123 system.adapter.ical.0 : ical : iobroker-ubuntu-22-04 - enabled system.adapter.icons-mfd-png.0 : icons-mfd-png : iobroker-ubuntu-22-04 - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : iobroker-ubuntu-22-04 - enabled + system.adapter.info.0 : info : iobroker-ubuntu-22-04 - enabled + system.adapter.iot.0 : iot : iobroker-ubuntu-22-04 - enabled + system.adapter.javascript.0 : javascript : iobroker-ubuntu-22-04 - enabled system.adapter.kecontact.0 : kecontact : iobroker-ubuntu-22-04 - disabled + system.adapter.midea.0 : midea : iobroker-ubuntu-22-04 - enabled system.adapter.mihome-lamp.0 : mihome-lamp : iobroker-ubuntu-22-04 - disabled, port: 54321 + system.adapter.modbus.0 : modbus : iobroker-ubuntu-22-04 - enabled + system.adapter.modbus.1 : modbus : iobroker-ubuntu-22-04 - enabled system.adapter.modbus.2 : modbus : iobroker-ubuntu-22-04 - disabled + system.adapter.modbus.3 : modbus : iobroker-ubuntu-22-04 - enabled + system.adapter.mqtt.0 : mqtt : iobroker-ubuntu-22-04 - enabled, port: 1883, bind: 0.0.0.0 system.adapter.mqtt.1 : mqtt : iobroker-ubuntu-22-04 - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker-ubuntu-22-04 - enabled, port: 1880, bind: 0.0.0.0 system.adapter.octoprint.0 : octoprint : iobroker-ubuntu-22-04 - disabled system.adapter.openweathermap.0 : openweathermap : iobroker-ubuntu-22-04 - enabled system.adapter.parser.0 : parser : iobroker-ubuntu-22-04 - disabled system.adapter.pvforecast.0 : pvforecast : iobroker-ubuntu-22-04 - disabled system.adapter.sayit.0 : sayit : iobroker-ubuntu-22-04 - disabled + system.adapter.shelly.0 : shelly : iobroker-ubuntu-22-04 - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : iobroker-ubuntu-22-04 - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : iobroker-ubuntu-22-04 - enabled, port: 8087, bind: 0.0.0.0, run as: admin system.adapter.sonoff.0 : sonoff : iobroker-ubuntu-22-04 - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.sonos.0 : sonos : iobroker-ubuntu-22-04 - enabled system.adapter.sprinklecontrol.0 : sprinklecontrol : iobroker-ubuntu-22-04 - disabled + system.adapter.sql.0 : sql : iobroker-ubuntu-22-04 - enabled, port: 3306 system.adapter.sun2000.0 : sun2000 : iobroker-ubuntu-22-04 - disabled, port: 502 + system.adapter.tankerkoenig.0 : tankerkoenig : iobroker slave - enabled + system.adapter.telegram.0 : telegram : iobroker-ubuntu-22-04 - enabled, port: 8443, bind: 0.0.0.0 system.adapter.tr-064.0 : tr-064 : iobroker-ubuntu-22-04 - disabled + system.adapter.trashschedule.0 : trashschedule : iobroker-ubuntu-22-04 - enabled system.adapter.tuya.0 : tuya : iobroker-ubuntu-22-04 - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : iobroker-ubuntu-22-04 - disabled + system.adapter.vis-inventwo.0 : vis-inventwo : iobroker-ubuntu-22-04 - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : iobroker-ubuntu-22-04 - disabled system.adapter.vis-material-advanced.0 : vis-material-advanced : iobroker-ubuntu-22-04 - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : iobroker-ubuntu-22-04 - enabled system.adapter.vis.0 : vis : iobroker-ubuntu-22-04 - enabled + system.adapter.web.0 : web : iobroker-ubuntu-22-04 - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.wled.0 : wled : iobroker-ubuntu-22-04 - disabled + system.adapter.yahka.0 : yahka : iobroker-ubuntu-22-04 - enabled + system.adapter.zigbee.0 : zigbee : iobroker-ubuntu-22-04 - enabled, port: /dev/ttyACM0 + instance is alive Enabled adapters with bindings + system.adapter.admin.1 : admin : iobroker-ubuntu-22-04 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hass.0 : hass : iobroker-ubuntu-22-04 - enabled, port: 8123 + system.adapter.mqtt.0 : mqtt : iobroker-ubuntu-22-04 - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker-ubuntu-22-04 - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : iobroker-ubuntu-22-04 - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : iobroker-ubuntu-22-04 - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : iobroker-ubuntu-22-04 - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.sql.0 : sql : iobroker-ubuntu-22-04 - enabled, port: 3306 + system.adapter.telegram.0 : telegram : iobroker-ubuntu-22-04 - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker-ubuntu-22-04 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : iobroker-ubuntu-22-04 - enabled, port: /dev/ttyACM0 ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Adapters Used repository: stable Adapter "admin" : 7.7.22 , installed 7.7.22 Adapter "alexa2" : 3.27.4 , installed 3.27.4 Adapter "backitup" : 3.3.13 , installed 3.3.13 Adapter "bring" : 1.8.4 , installed 1.8.4 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "echarts" : 1.9.2 , installed 1.9.2 Adapter "ecovacs-deebot": 1.4.15 , installed 1.4.15 Adapter "firetv" : 2.1.0 , installed 2.1.0 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "haassohn" : 1.0.9 , installed 1.0.9 Adapter "hass" : 1.4.0 , installed 1.4.0 Adapter "ical" : 1.18.1 , installed 1.18.1 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "iot" : 5.0.7 , installed 5.0.7 Adapter "javascript" : 9.0.11 , installed 9.0.11 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "kecontact" : 3.4.0 , installed 3.4.0 Adapter "midea" : 0.0.7 , installed 0.0.7 Adapter "modbus" : 6.3.2 , installed 6.3.2 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "node-red" : 5.2.1 , installed 5.2.1 Adapter "octoprint" : 5.1.0 , installed 5.1.0 Adapter "openweathermap": 1.1.2 , installed 1.1.2 Adapter "parser" : 2.2.4 , installed 2.2.4 Adapter "pvforecast" : 5.0.0 , installed 5.0.0 Adapter "samsung" : 0.6.1 , installed 0.6.1 Adapter "sayit" : 5.0.0 , installed 5.0.0 Adapter "shelly" : 10.5.2 , installed 10.5.2 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.2.1 , installed 3.2.1 Adapter "sonos" : 3.0.0 , installed 3.0.0 Adapter "sprinklecontrol": 0.2.19 , installed 0.2.19 Adapter "sql" : 3.0.1 , installed 3.0.1 Adapter "sun2000" : 2.3.5 , installed 2.3.5 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "trashschedule": 3.3.0 , installed 3.3.0 Adapter "tuya" : 3.16.0 , installed 3.16.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-hqwidgets": 1.5.1 , installed 1.5.1 Adapter "vis-inventwo" : 3.3.5 , installed 3.3.5 Adapter "vis-jqui-mfd" : 1.1.1 , installed 1.1.1 Adapter "vis-material-advanced": 1.7.4, installed 1.7.4 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "wled" : 0.7.2 , installed 0.7.2 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "yahka" : 1.1.5 , installed 1.1.5 Adapter "zigbee" : 3.1.5 , installed 3.1.5 Objects and States Please stand by - This may take a while Objects: 19511 States: 13675 *** OS-Repositories and Updates *** [AHit:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:5 http://de.archive.ubuntu.com/ubuntu jammy-security InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 1001 806 658/iobroker.js-con tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 1001 21342 658/iobroker.js-con tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 18706 1/init tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 23414 723/sshd: /usr/sbin tcp 0 0 127.0.0.1:39345 0.0.0.0:* LISTEN 1001 5420566 1191/io.yahka.0 tcp 0 0 0.0.0.0:33060 0.0.0.0:* LISTEN 115 22187 773/mysqld tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 1001 25660 1033/node-red tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 5550982 3870554/io.mqtt.0 tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 26638 1219/io.shelly.1 tcp 0 0 0.0.0.0:1884 0.0.0.0:* LISTEN 1001 5550983 3870554/io.mqtt.0 tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 102 491 638/systemd-resolve tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 115 23543 773/mysqld tcp6 0 0 :::111 :::* LISTEN 0 18707 1/init tcp6 0 0 :::22 :::* LISTEN 0 23425 723/sshd: /usr/sbin tcp6 0 0 :::45471 :::* LISTEN 1001 24749 1191/io.yahka.0 tcp6 0 0 :::8081 :::* LISTEN 1001 21417 947/io.admin.1 tcp6 0 0 :::8082 :::* LISTEN 1001 26414 1917/io.web.0 tcp6 0 0 :::8087 :::* LISTEN 1001 25078 1391/io.simple-api. tcp6 0 0 :::3500 :::* LISTEN 1001 24730 1172/io.sonos.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 22509 1191/io.yahka.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 22508 1191/io.yahka.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 24709 1157/io.shelly.0 udp 0 0 127.0.0.53:53 0.0.0.0:* 102 490 638/systemd-resolve udp 0 0 0.0.0.0:111 0.0.0.0:* 0 164 1/init udp6 0 0 fe80::3cf8:f2ff:fe8:546 :::* 101 496 636/systemd-network udp6 0 0 :::111 :::* 0 165 1/init *** Log File - Last 25 Lines *** 2026-01-26 09:46:26.843 - info: hass.0 (19952) State changed for unknown object entities.sensor.keba_p30_max_current.device_class. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.984 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_phase_a_apparent_power.state. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.985 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_phase_a_apparent_power.state_class. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.985 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_phase_a_apparent_power.device_class. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.985 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_phase_b_apparent_power.state. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.985 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_phase_b_apparent_power.state_class. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.985 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_phase_b_apparent_power.device_class. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.986 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_phase_c_apparent_power.state. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.986 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_phase_c_apparent_power.state_class. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.986 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_phase_c_apparent_power.device_class. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.988 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_total_apparent_power.state. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.988 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_total_apparent_power.state_class. Please restart the adapter to resync the objects. 2026-01-26 09:46:26.988 - info: hass.0 (19952) State changed for unknown object entities.sensor.shellypro3em_34987a44206c_total_apparent_power.device_class. Please restart the adapter to resync the objects. 2026-01-26 09:46:28.180 - info: hass.0 (19952) State changed for unknown object entities.image.fritz_box_7490_fritz_box_gastzugang.state. Please restart the adapter to resync the objects. 2026-01-26 09:46:28.181 - info: hass.0 (19952) State changed for unknown object entities.image.fritz_box_7490_fritz_box_gastzugang.access_token. Please restart the adapter to resync the objects. 2026-01-26 09:46:28.181 - info: hass.0 (19952) State changed for unknown object entities.image.fritz_box_7490_fritz_box_gastzugang.entity_picture. Please restart the adapter to resync the objects. 2026-01-26 09:46:29.500 - info: hass.0 (19952) State changed for unknown object entities.sensor.grid_l1.state. Please restart the adapter to resync the objects. 2026-01-26 09:46:29.506 - info: hass.0 (19952) State changed for unknown object entities.sensor.grid_l2.state. Please restart the adapter to resync the objects. 2026-01-26 09:46:29.568 - info: hass.0 (19952) State changed for unknown object entities.sensor.grid_l3.state. Please restart the adapter to resync the objects. 2026-01-26 09:46:32.147 - info: hass.0 (19952) State changed for unknown object entities.sensor.keba_p30_max_current.state. Please restart the adapter to resync the objects. 2026-01-26 09:46:32.148 - info: hass.0 (19952) State changed for unknown object entities.sensor.keba_p30_max_current.max_current_hardware. Please restart the adapter to resync the objects. 2026-01-26 09:46:32.148 - info: hass.0 (19952) State changed for unknown object entities.sensor.keba_p30_max_current.device_class. Please restart the adapter to resync the objects. 2026-01-26 09:46:32.249 - info: hass.0 (19952) State changed for unknown object entities.sensor.keba_p30_max_current.state. Please restart the adapter to resync the objects. 2026-01-26 09:46:32.249 - info: hass.0 (19952) State changed for unknown object entities.sensor.keba_p30_max_current.max_current_hardware. Please restart the adapter to resync the objects. 2026-01-26 09:46:32.250 - info: hass.0 (19952) State changed for unknown object entities.sensor.keba_p30_max_current.device_class. Please restart the adapter to resync the objects.============ Mark until here for C&P =============
iob diag has finished.
@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
Operating System codenamed 'jammy' is an aging Ubuntu release!
im ernst
-
Da ist mit Sicherheit der Rest auch komplett veraltet.
-
Ok installiere gerade eine neue Version Ubuntu Server 24.04.3 LTS.
Kann ich ein komplettes Backup von Iobroker machen und in das neue System einspielen?@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
Kann ich ein komplettes Backup von Iobroker machen und in das neue System einspielen?
Klar. Dazu verwendet man am besten den Backitup-Adapter.
Es empfiehlt sich allerdings mit einem 'ioBroker auf aktuellem Stand' umzuziehen.
Abgesoffene Versionsstände bekommst du nämlich nur mit Schwierigkeiten wieder eingespielt.Und statt Schnubbibuntu würde ich da auch das aktuelle Debian empfehlen.
-
Umzug geht weiter, leider bekomme ich zum Zigbee keine Verbindung.
zigbee.0 2026-02-07 11:19:02.483 error Failed to start Zigbee: no message given zigbee.0 2026-02-07 11:19:02.482 error Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) zigbee.0 2026-02-07 11:19:02.253 info Unable to obtain herdsman settings zigbee.0 2026-02-07 11:18:41.290 debug getDevices called from system.adapter.admin.1 with command "getDevices" without ID zigbee.0 2026-02-07 11:18:41.280 debug getCoordinatorInfo result: {"installSource":"iobroker.zigbee@3.1.5","channel":"26","port":"/dev/ttyACM0","installedVersion":"3.1.5","type":"zstack","revision":"not connected","version":"not connected","herdsman":"6.4.2","converters":"25.31.0","autostart":true} zigbee.0 2026-02-07 11:18:41.227 debug get groupes called with {"command":"getGroups","message":{},"from":"system.adapter.admin.1","callback":{"message":{},"id":41,"ack":false,"time":1770459521168},"_id":64084252} disconnected zigbee.0 2026-02-07 11:18:41.179 debug get groupes called with {"command":"getGroups","message":{},"from":"system.adapter.admin.1","callback":{"message":{},"id":41,"ack":false,"time":1770459521168},"_id":64084252} zigbee.0 2026-02-07 11:18:41.178 debug Commands: Command getGroups is unknown zigbee.0 2026-02-07 11:18:41.176 debug readNvBackup returns {"channel":26,"precfgkey":"01030507090b0d0f00020406080a0c0d","extPanID":"d9dddddddcddddcd","panID":6728} zigbee.0 2026-02-07 11:18:41.173 debug readNvBackup called zigbee.0 2026-02-07 11:18:35.581 debug Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2026_02_07-11_18_35.tar.gz success zigbee.0 2026-02-07 11:18:35.542 info Starting Zigbee-Herdsman zigbee.0 2026-02-07 11:18:35.541 info configured transmit power : high zigbee.0 2026-02-07 11:18:35.538 info Installed Version: iobroker.zigbee@3.1.5 (Converters 25.31.0 Herdsman 6.4.2) zigbee.0 2026-02-07 11:18:35.511 info Starting Adapter npm ... zigbee.0 2026-02-07 11:18:35.510 info Autostart Zigbee subsystem zigbee.0 2026-02-07 11:18:35.509 info --- creating device debug --- zigbee.0 2026-02-07 11:18:35.334 info init localConfig zigbee.0 2026-02-07 11:18:35.329 info Adapter ready - starting subsystems. Adapter is running in silly mode. zigbee.0 2026-02-07 11:18:35.249 info starting. Version 3.1.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.22.0, js-controller: 7.0.7 zigbee.0 2026-02-07 11:18:34.653 debug Plugin sentry Initialize Plugin (enabled=true) zigbee.0 2026-02-07 11:18:34.559 debug States connected to redis: 0.0.0.0:9000 zigbee.0 2026-02-07 11:18:34.425 debug States create User PubSub Client zigbee.0 2026-02-07 11:18:34.424 debug States create System PubSub Client zigbee.0 2026-02-07 11:18:34.379 debug Redis States: Use Redis connection: 0.0.0.0:9000 zigbee.0 2026-02-07 11:18:34.279 debug Objects connected to redis: 0.0.0.0:9001 zigbee.0 2026-02-07 11:18:34.267 debug Objects client initialize lua scripts zigbee.0 2026-02-07 11:18:34.111 debug Objects create User PubSub Client zigbee.0 2026-02-07 11:18:34.109 debug Objects create System PubSub Client zigbee.0 2026-02-07 11:18:34.106 debug Objects client ready ... initialize now zigbee.0 2026-02-07 11:18:34.028 debug Redis Objects: Use Redis connection: 0.0.0.0:9001 -
Umzug geht weiter, leider bekomme ich zum Zigbee keine Verbindung.
zigbee.0 2026-02-07 11:19:02.483 error Failed to start Zigbee: no message given zigbee.0 2026-02-07 11:19:02.482 error Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) zigbee.0 2026-02-07 11:19:02.253 info Unable to obtain herdsman settings zigbee.0 2026-02-07 11:18:41.290 debug getDevices called from system.adapter.admin.1 with command "getDevices" without ID zigbee.0 2026-02-07 11:18:41.280 debug getCoordinatorInfo result: {"installSource":"iobroker.zigbee@3.1.5","channel":"26","port":"/dev/ttyACM0","installedVersion":"3.1.5","type":"zstack","revision":"not connected","version":"not connected","herdsman":"6.4.2","converters":"25.31.0","autostart":true} zigbee.0 2026-02-07 11:18:41.227 debug get groupes called with {"command":"getGroups","message":{},"from":"system.adapter.admin.1","callback":{"message":{},"id":41,"ack":false,"time":1770459521168},"_id":64084252} disconnected zigbee.0 2026-02-07 11:18:41.179 debug get groupes called with {"command":"getGroups","message":{},"from":"system.adapter.admin.1","callback":{"message":{},"id":41,"ack":false,"time":1770459521168},"_id":64084252} zigbee.0 2026-02-07 11:18:41.178 debug Commands: Command getGroups is unknown zigbee.0 2026-02-07 11:18:41.176 debug readNvBackup returns {"channel":26,"precfgkey":"01030507090b0d0f00020406080a0c0d","extPanID":"d9dddddddcddddcd","panID":6728} zigbee.0 2026-02-07 11:18:41.173 debug readNvBackup called zigbee.0 2026-02-07 11:18:35.581 debug Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2026_02_07-11_18_35.tar.gz success zigbee.0 2026-02-07 11:18:35.542 info Starting Zigbee-Herdsman zigbee.0 2026-02-07 11:18:35.541 info configured transmit power : high zigbee.0 2026-02-07 11:18:35.538 info Installed Version: iobroker.zigbee@3.1.5 (Converters 25.31.0 Herdsman 6.4.2) zigbee.0 2026-02-07 11:18:35.511 info Starting Adapter npm ... zigbee.0 2026-02-07 11:18:35.510 info Autostart Zigbee subsystem zigbee.0 2026-02-07 11:18:35.509 info --- creating device debug --- zigbee.0 2026-02-07 11:18:35.334 info init localConfig zigbee.0 2026-02-07 11:18:35.329 info Adapter ready - starting subsystems. Adapter is running in silly mode. zigbee.0 2026-02-07 11:18:35.249 info starting. Version 3.1.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.22.0, js-controller: 7.0.7 zigbee.0 2026-02-07 11:18:34.653 debug Plugin sentry Initialize Plugin (enabled=true) zigbee.0 2026-02-07 11:18:34.559 debug States connected to redis: 0.0.0.0:9000 zigbee.0 2026-02-07 11:18:34.425 debug States create User PubSub Client zigbee.0 2026-02-07 11:18:34.424 debug States create System PubSub Client zigbee.0 2026-02-07 11:18:34.379 debug Redis States: Use Redis connection: 0.0.0.0:9000 zigbee.0 2026-02-07 11:18:34.279 debug Objects connected to redis: 0.0.0.0:9001 zigbee.0 2026-02-07 11:18:34.267 debug Objects client initialize lua scripts zigbee.0 2026-02-07 11:18:34.111 debug Objects create User PubSub Client zigbee.0 2026-02-07 11:18:34.109 debug Objects create System PubSub Client zigbee.0 2026-02-07 11:18:34.106 debug Objects client ready ... initialize now zigbee.0 2026-02-07 11:18:34.028 debug Redis Objects: Use Redis connection: 0.0.0.0:9001@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
leider bekomme ich zum Zigbee keine Verbindung.
Verwende einen Link 'by-id' zu dem USB-Stick und zieh den danach raus, 1 Minute warten, wieder einstecken.
-
@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
leider bekomme ich zum Zigbee keine Verbindung.
Verwende einen Link 'by-id' zu dem USB-Stick und zieh den danach raus, 1 Minute warten, wieder einstecken.
-
@Thomas-Braun weiß nicht genau was du damit meinst, aber wenn ich
ls -la /dev/serial/by-id
eingebe, erscheint folgendes, was auch beim Zigbee unter Hardware eingetragen ist.
Du sollst da aber NICHT /dev/ttyACM0 eintragen sondern den Link 'by-id'.
(Denn ich wegen sinnfreier Screenshots von Konsolentext nicht kopieren kann. Sowas NIE als Screenshot, IMMER als Text in CodeTags hier rein) -
Du sollst da aber NICHT /dev/ttyACM0 eintragen sondern den Link 'by-id'.
(Denn ich wegen sinnfreier Screenshots von Konsolentext nicht kopieren kann. Sowas NIE als Screenshot, IMMER als Text in CodeTags hier rein)@Thomas-Braun stehe gerade auf dem Schlauch. So?
/dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00Das merkwürdige ist, ohne das ich was geändert habe, hat er plötzlich eine Verbindung?!
total 0 drwxr-xr-x 2 root root 80 Feb 7 11:11 . drwxr-xr-x 4 root root 80 Feb 7 11:11 .. lrwxrwxrwx 1 root root 13 Feb 7 11:11 usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 -> ../../ttyACM0 lrwxrwxrwx 1 root root 13 Feb 7 11:11 usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if03 -> ../../ttyACM1 superpoli@iobroker:~$ -
@Thomas-Braun stehe gerade auf dem Schlauch. So?
/dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00Das merkwürdige ist, ohne das ich was geändert habe, hat er plötzlich eine Verbindung?!
total 0 drwxr-xr-x 2 root root 80 Feb 7 11:11 . drwxr-xr-x 4 root root 80 Feb 7 11:11 .. lrwxrwxrwx 1 root root 13 Feb 7 11:11 usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 -> ../../ttyACM0 lrwxrwxrwx 1 root root 13 Feb 7 11:11 usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if03 -> ../../ttyACM1 superpoli@iobroker:~$@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
stehe gerade auf dem Schlauch. So?
Ja.
Die Links stehen übrigens u. a. auch in der Ausgabe voniob diagdrin. Fertig zum herauskopieren.
-
Umzug geht weiter, leider bekomme ich zum Zigbee keine Verbindung.
zigbee.0 2026-02-07 11:19:02.483 error Failed to start Zigbee: no message given zigbee.0 2026-02-07 11:19:02.482 error Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) zigbee.0 2026-02-07 11:19:02.253 info Unable to obtain herdsman settings zigbee.0 2026-02-07 11:18:41.290 debug getDevices called from system.adapter.admin.1 with command "getDevices" without ID zigbee.0 2026-02-07 11:18:41.280 debug getCoordinatorInfo result: {"installSource":"iobroker.zigbee@3.1.5","channel":"26","port":"/dev/ttyACM0","installedVersion":"3.1.5","type":"zstack","revision":"not connected","version":"not connected","herdsman":"6.4.2","converters":"25.31.0","autostart":true} zigbee.0 2026-02-07 11:18:41.227 debug get groupes called with {"command":"getGroups","message":{},"from":"system.adapter.admin.1","callback":{"message":{},"id":41,"ack":false,"time":1770459521168},"_id":64084252} disconnected zigbee.0 2026-02-07 11:18:41.179 debug get groupes called with {"command":"getGroups","message":{},"from":"system.adapter.admin.1","callback":{"message":{},"id":41,"ack":false,"time":1770459521168},"_id":64084252} zigbee.0 2026-02-07 11:18:41.178 debug Commands: Command getGroups is unknown zigbee.0 2026-02-07 11:18:41.176 debug readNvBackup returns {"channel":26,"precfgkey":"01030507090b0d0f00020406080a0c0d","extPanID":"d9dddddddcddddcd","panID":6728} zigbee.0 2026-02-07 11:18:41.173 debug readNvBackup called zigbee.0 2026-02-07 11:18:35.581 debug Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2026_02_07-11_18_35.tar.gz success zigbee.0 2026-02-07 11:18:35.542 info Starting Zigbee-Herdsman zigbee.0 2026-02-07 11:18:35.541 info configured transmit power : high zigbee.0 2026-02-07 11:18:35.538 info Installed Version: iobroker.zigbee@3.1.5 (Converters 25.31.0 Herdsman 6.4.2) zigbee.0 2026-02-07 11:18:35.511 info Starting Adapter npm ... zigbee.0 2026-02-07 11:18:35.510 info Autostart Zigbee subsystem zigbee.0 2026-02-07 11:18:35.509 info --- creating device debug --- zigbee.0 2026-02-07 11:18:35.334 info init localConfig zigbee.0 2026-02-07 11:18:35.329 info Adapter ready - starting subsystems. Adapter is running in silly mode. zigbee.0 2026-02-07 11:18:35.249 info starting. Version 3.1.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.22.0, js-controller: 7.0.7 zigbee.0 2026-02-07 11:18:34.653 debug Plugin sentry Initialize Plugin (enabled=true) zigbee.0 2026-02-07 11:18:34.559 debug States connected to redis: 0.0.0.0:9000 zigbee.0 2026-02-07 11:18:34.425 debug States create User PubSub Client zigbee.0 2026-02-07 11:18:34.424 debug States create System PubSub Client zigbee.0 2026-02-07 11:18:34.379 debug Redis States: Use Redis connection: 0.0.0.0:9000 zigbee.0 2026-02-07 11:18:34.279 debug Objects connected to redis: 0.0.0.0:9001 zigbee.0 2026-02-07 11:18:34.267 debug Objects client initialize lua scripts zigbee.0 2026-02-07 11:18:34.111 debug Objects create User PubSub Client zigbee.0 2026-02-07 11:18:34.109 debug Objects create System PubSub Client zigbee.0 2026-02-07 11:18:34.106 debug Objects client ready ... initialize now zigbee.0 2026-02-07 11:18:34.028 debug Redis Objects: Use Redis connection: 0.0.0.0:9001 -
Jetzt habe ich noch Proble mit SQL.
sql.0 2026-02-09 09:19:25.586 error Error: connect ECONNREFUSED 127.0.0.1:3306 sql.0 2026-02-09 09:19:25.574 debug Borrow connection from pool: 1 nowObwohl Backup gemacht und wieder eingespielt:
Last login: Sat Feb 7 11:42:41 2026 from 192.168.115.26 superpoli@iobroker:~$ systemctl status mysql.service Unit mysql.service could not be found. -
Jetzt habe ich noch Proble mit SQL.
sql.0 2026-02-09 09:19:25.586 error Error: connect ECONNREFUSED 127.0.0.1:3306 sql.0 2026-02-09 09:19:25.574 debug Borrow connection from pool: 1 nowObwohl Backup gemacht und wieder eingespielt:
Last login: Sat Feb 7 11:42:41 2026 from 192.168.115.26 superpoli@iobroker:~$ systemctl status mysql.service Unit mysql.service could not be found.@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
Jetzt habe ich noch Proble mit SQL.
Bitte einen neuen Thread für ein neues Problem.
-
@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
Jetzt habe ich noch Proble mit SQL.
Bitte einen neuen Thread für ein neues Problem.
Nach dem Update des Zigbee Adapters von 3.1.5 auf 3.3.5 bekomme ich wieder keine Verbindung.
Auch das Ändern des Pfades bring keine Abhilfe.
/dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if002026-02-11 10:25:41.607 - [34mdebug[39m: zigbee.0 (1869) Test connection for /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 2026-02-11 10:25:41.609 - [34mdebug[39m: zigbee.0 (1869) reading access rights for /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 2026-02-11 10:25:41.610 - [34mdebug[39m: zigbee.0 (1869) read and write access available for /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 2026-02-11 10:25:41.611 - [32minfo[39m: zigbee.0 (1869) Try to reconnect. 1 attempts left 2026-02-11 10:25:41.612 - [32minfo[39m: zigbee.0 (1869) Starting Adapter npm ... 2026-02-11 10:25:41.617 - [32minfo[39m: zigbee.0 (1869) Installed Version: iobroker.zigbee@3.3.5 (Converters 25.112.0 Herdsman 8.1.0) 2026-02-11 10:25:41.618 - [32minfo[39m: zigbee.0 (1869) configured transmit power : high 2026-02-11 10:25:41.619 - [32minfo[39m: zigbee.0 (1869) Starting Zigbee-Herdsman 2026-02-11 10:25:41.688 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Starting zigbee-herdsman...","ack":true,"ts":1770801941684,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801941684} 2026-02-11 10:25:42.092 - [32minfo[39m: zigbee.0 (1869) Unable to obtain herdsman settings 2026-02-11 10:25:42.123 - [31merror[39m: zigbee.0 (1869) Starting zigbee-herdsman problem : Error Resource temporarily unavailable Cannot lock port 2026-02-11 10:25:42.125 - [31merror[39m: zigbee.0 (1869) Failed to start Zigbee: no message given 2026-02-11 10:25:42.147 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Unable to obtain herdsman settings","ack":true,"ts":1770801942143,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801942143} 2026-02-11 10:25:42.148 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Starting zigbee-herdsman problem : Error Resource temporarily unavailable Cannot lock port","ack":true,"ts":1770801942143,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801942143} 2026-02-11 10:25:42.154 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.connection:{"val":false,"ack":true,"ts":1770801942149,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770724947942} 2026-02-11 10:25:42.228 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Failed to start Zigbee: no message given","ack":true,"ts":1770801942224,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801942224} -
Nach dem Update des Zigbee Adapters von 3.1.5 auf 3.3.5 bekomme ich wieder keine Verbindung.
Auch das Ändern des Pfades bring keine Abhilfe.
/dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if002026-02-11 10:25:41.607 - [34mdebug[39m: zigbee.0 (1869) Test connection for /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 2026-02-11 10:25:41.609 - [34mdebug[39m: zigbee.0 (1869) reading access rights for /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 2026-02-11 10:25:41.610 - [34mdebug[39m: zigbee.0 (1869) read and write access available for /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 2026-02-11 10:25:41.611 - [32minfo[39m: zigbee.0 (1869) Try to reconnect. 1 attempts left 2026-02-11 10:25:41.612 - [32minfo[39m: zigbee.0 (1869) Starting Adapter npm ... 2026-02-11 10:25:41.617 - [32minfo[39m: zigbee.0 (1869) Installed Version: iobroker.zigbee@3.3.5 (Converters 25.112.0 Herdsman 8.1.0) 2026-02-11 10:25:41.618 - [32minfo[39m: zigbee.0 (1869) configured transmit power : high 2026-02-11 10:25:41.619 - [32minfo[39m: zigbee.0 (1869) Starting Zigbee-Herdsman 2026-02-11 10:25:41.688 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Starting zigbee-herdsman...","ack":true,"ts":1770801941684,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801941684} 2026-02-11 10:25:42.092 - [32minfo[39m: zigbee.0 (1869) Unable to obtain herdsman settings 2026-02-11 10:25:42.123 - [31merror[39m: zigbee.0 (1869) Starting zigbee-herdsman problem : Error Resource temporarily unavailable Cannot lock port 2026-02-11 10:25:42.125 - [31merror[39m: zigbee.0 (1869) Failed to start Zigbee: no message given 2026-02-11 10:25:42.147 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Unable to obtain herdsman settings","ack":true,"ts":1770801942143,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801942143} 2026-02-11 10:25:42.148 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Starting zigbee-herdsman problem : Error Resource temporarily unavailable Cannot lock port","ack":true,"ts":1770801942143,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801942143} 2026-02-11 10:25:42.154 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.connection:{"val":false,"ack":true,"ts":1770801942149,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770724947942} 2026-02-11 10:25:42.228 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Failed to start Zigbee: no message given","ack":true,"ts":1770801942224,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801942224}@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
Error Resource temporarily unavailable Cannot lock port
Irgendwas / irgendwer greift auf das Gerät schon zu.
Stehst du da (vielleicht in der Konsole) selber drauf?
Versuch mal einen Neustart, das ist am saubersten und wirft ziemlich sicher die bestehenden locks raus. -
Nach dem Update des Zigbee Adapters von 3.1.5 auf 3.3.5 bekomme ich wieder keine Verbindung.
Auch das Ändern des Pfades bring keine Abhilfe.
/dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if002026-02-11 10:25:41.607 - [34mdebug[39m: zigbee.0 (1869) Test connection for /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 2026-02-11 10:25:41.609 - [34mdebug[39m: zigbee.0 (1869) reading access rights for /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 2026-02-11 10:25:41.610 - [34mdebug[39m: zigbee.0 (1869) read and write access available for /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L43002RW-if00 2026-02-11 10:25:41.611 - [32minfo[39m: zigbee.0 (1869) Try to reconnect. 1 attempts left 2026-02-11 10:25:41.612 - [32minfo[39m: zigbee.0 (1869) Starting Adapter npm ... 2026-02-11 10:25:41.617 - [32minfo[39m: zigbee.0 (1869) Installed Version: iobroker.zigbee@3.3.5 (Converters 25.112.0 Herdsman 8.1.0) 2026-02-11 10:25:41.618 - [32minfo[39m: zigbee.0 (1869) configured transmit power : high 2026-02-11 10:25:41.619 - [32minfo[39m: zigbee.0 (1869) Starting Zigbee-Herdsman 2026-02-11 10:25:41.688 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Starting zigbee-herdsman...","ack":true,"ts":1770801941684,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801941684} 2026-02-11 10:25:42.092 - [32minfo[39m: zigbee.0 (1869) Unable to obtain herdsman settings 2026-02-11 10:25:42.123 - [31merror[39m: zigbee.0 (1869) Starting zigbee-herdsman problem : Error Resource temporarily unavailable Cannot lock port 2026-02-11 10:25:42.125 - [31merror[39m: zigbee.0 (1869) Failed to start Zigbee: no message given 2026-02-11 10:25:42.147 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Unable to obtain herdsman settings","ack":true,"ts":1770801942143,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801942143} 2026-02-11 10:25:42.148 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Starting zigbee-herdsman problem : Error Resource temporarily unavailable Cannot lock port","ack":true,"ts":1770801942143,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801942143} 2026-02-11 10:25:42.154 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.connection:{"val":false,"ack":true,"ts":1770801942149,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770724947942} 2026-02-11 10:25:42.228 - [35msilly[39m: zigbee.0 (1869) States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Failed to start Zigbee: no message given","ack":true,"ts":1770801942224,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1770801942224}@tilly sagte in Zigbee v3.1.5 plötzlich keine Verbindung mehr:
Nach dem Update des Zigbee Adapters von 3.1.5 auf 3.3.5 bekomme ich wieder keine Verbindung.
Bitte genau folgendes machen:
- Adapter auf info stellen. Das umstellen auf debug oder silly bringt nicht mehr infos, es flutet Dein log nur mit Rauschen.
- Adapter anhalten (falls er aktiv ist)
- 60 s warten (wichtig)
- Konfigurationsinterface des Adapters öffnen (während der Adapter nicht läuft)
- Auf das 'Hardware' Tab gehen
- Adapter starten (geht aus der Titelzeile :
- 60 sekunden abwarten - schauen ob der Adapter durch startet. Im Log-Fenster unten im Hardware Tab sollten meldungen stehen.
Diese Meldungen hier posten. (als Text)
- Sollte das ZIgbee Netz nicht starten und keine meldungen erscheinen über den Start/Stop button weiter unten versuchen das Netz zu starten
A.
Support us
561
Online32.7k
Benutzer82.5k
Themen1.3m
Beiträge