[Gelöst] NodeRed Deploy plötzlich unendlich langsam
-
Hallo,
nach dem Umstieg auf UI 2.0 habe ich versucht unbenutzte Konfigurations-Nodes zu löschen und plötzlich dauert das Deployen "unendlich" (>10min) lange, was vorher in Sekunden ging.
Wenn ich den Raspberry neu starte, was gefühlt auch länger dauert, funktioniert alles scheinbar ordentlich, aber wehe ich deploye die Flows in der NodeRed Instanz, dann hängt sich das Teil komplett weg.Ich habe das Gefühl das es an der "node-red-contrib-ads-client"-Palette hängt, welche ich zum testen installiert habe um die "node-red-contrib-ads" abzulösen. Diese wird wohl zukünftig nicht weiterentwickelt.
Ich habe leider keine Ahnung wie ich an ein .log komme und vor allem was ich daraus lesen könnte :-(
HW: Raspberry 5 mit 8GB
wenn der iobroker sonst läuft und du nur probleme mit nodered hast,
könntest du mal in den instanz einstellungen den log level von info auf debug stellen.
dann nodered öffnen.
dann im admin auf den reiter log oder protokolle gehen und oben im filter auf nodered filternich weiß allerdings nicht was da alle ausgegeben wird und ob die nodered fehler auch alle ins iobroker log umgeleitet werden
-
-
Der Hauptfehler, der sich durch das log zieht, ist
2026-09-20 20:12:52.682 - error: node-red.0 (2300) Node-RED: 20 Sep 20:12:52 - [error] Unable to listen on http://127.0.0.1:1880/ 2026-09-20 20:12:52.683 - error: node-red.0 (2300) Node-RED: 20 Sep 20:12:52 - [error] Error: port in useD.h. der Port über den der Adapter mit nodered kommuniziert ist bereits in Nutzung.
Hast du zwei Instanzen nodered installiert?
Ansonsten musst du mal auf dem Rechner schauen, ob es noch einen anderen Server gibt, der auf dem Port 1880 horcht. -
Ich habe mal versucht alles upzudaten und nochmal eine Diagnose gestartet:
========== Start marking the full check here ===========
Script v.2026-08-30 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: raspberry5 Icon name: computer Kernel: Linux 6.18.50+rpt-rpi-2712 Architecture: arm64 OS is similar to: Model : Raspberry Pi 5 Model B Rev 1.1 Docker : false Virtualization : none Unknown Kernel : aarch64 Userland : 64bit System was installed 94 days ago (on 2026-06-18). Systemuptime and Load: 20:45:25 up 1:01, 1 user, load average: 1.57, 1.51, 1.22 CPU threads : 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Sun 2026-09-20 20:45:25 CEST Universal time: Sun 2026-09-20 18:45:25 UTC RTC time: Sun 2026-09-20 18:45:25 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': mf HOME=/home/mf GROUPS=mf adm dialout cdrom sudo audio video plugdev games users netdev gpio i2c spi render input lpadmin iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: Unknown Display-Manager: Not found Desktop: Session: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 8.5G 2.3G 5.3G 23M 1.0G 6.2G Swap: 2.1G 0B 2.1G Total: 10G 2.3G 7.4G Active iob-Instances: 12 8062 M total memory 2162 M used memory 1874 M active memory 667 M inactive memory 5010 M free memory 126 M buffer memory 872 M swap cache 2047 M total swap 0 M used swap 2047 M free swap *** top - Table Of Processes *** top - 20:45:26 up 1:01, 1 user, load average: 1.57, 1.51, 1.22 Tasks: 172 total, 2 running, 170 sleeping, 0 stopped, 0 zombie %Cpu(s): 32.7 us, 3.6 sy, 0.0 ni, 58.2 id, 5.5 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 8062.3 total, 5001.3 free, 2171.0 used, 1000.3 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 5891.3 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 udev devtmpfs 3.9G 0 3.9G 0% /dev tmpfs tmpfs 1.6G 13M 1.6G 1% /run /dev/mmcblk0p2 ext4 58G 6.7G 49G 13% / tmpfs tmpfs 4.0G 0 4.0G 0% /dev/shm tmpfs tmpfs 5.0M 48K 5.0M 1% /run/lock tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service tmpfs tmpfs 4.0G 11M 4.0G 1% /tmp /dev/mmcblk0p1 vfat 505M 67M 438M 14% /boot/firmware tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/serial-getty@ttyAMA10.service tmpfs tmpfs 807M 32K 807M 1% /run/user/1000 Messages concerning filesystems in dmesg (Last 15 lines only): [Sun Sep 20 19:44:01 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs [Sun Sep 20 19:44:01 2026] EXT4-fs (mmcblk0p2): mounted filesystem 15f4c6be-1102-4331-9904-f78e78afd1fd ro with ordered data mode. Quota mode: none. [Sun Sep 20 19:44:04 2026] EXT4-fs (mmcblk0p2): re-mounted 15f4c6be-1102-4331-9904-f78e78afd1fd r/w. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime,commit=600 `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 2.5G /var/ 270M /var/cache 264M /var/cache/apt 185M /var/lib 148M /var/lib/apt/lists Archived and active journals take up 8M in the file system. /opt/iobroker/backups: 31M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 363M /opt/iobroker/iobroker-data/ 236M /opt/iobroker/iobroker-data/node-red 234M /opt/iobroker/iobroker-data/node-red/node_modules 72M /opt/iobroker/iobroker-data/backup-objects 62M /opt/iobroker/iobroker-data/node-red/node_modules/echarts The five largest files in iobroker-data are: 10M /opt/iobroker/iobroker-data/objects.jsonl 7.8M /opt/iobroker/iobroker-data/node-red/node_modules/echarts/dist/echarts.js.map 7.8M /opt/iobroker/iobroker-data/node-red/node_modules/echarts/dist/echarts.esm.mjs.map 7.8M /opt/iobroker/iobroker-data/node-red/node_modules/echarts/dist/echarts.esm.js.map 6.8M /opt/iobroker/iobroker-data/files/backitup.admin/custom/assets/_virtual_mf___mfe_internal__ConfigCustomBackItUpSet__mf_owner__1__loadShare___mf_0_iobroker_mf_1_gui_mf_2_components__loadShare__.js-Bs-T0f9g.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_AVDMb135B02-if00-port0 /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 /dev/serial/by-id/usb-SHK_NANO_CUL_868-if00-port0 *** ZigBee Settings *** 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' === ZigBee Port Overview === Instance Configured Port Available by-id Port Status -------- ---------------- ---------------------------- ------ zigbee.0 tcp://192.168.178.203:7638 - tcp *** NodeJS-Installation *** /usr/bin/nodejs v22.23.2 /usr/bin/node v22.23.2 /usr/bin/npm 10.9.8 /usr/bin/npx 10.9.8 ✓ Node.js installation is correct nodejs: Installed: 22.23.2-1nodesource1 Candidate: 22.23.2-1nodesource1 Version table: *** 22.23.2-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.23.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.23.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.3-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.2-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 20.19.2+dfsg-1+deb13u2 500 500 http://deb.debian.org/debian trixie/main arm64 Packages 500 http://deb.debian.org/debian-security trixie-security/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: No known Vulnerabilities detected! *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: raspberry5 raspberry5 (version: 7.2.2, hostname: raspberry5 , alive, uptime: 1186) Core adapters versions js-controller: 7.2.2 admin: 8.0.11 javascript: "javascript" not found nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberry5 - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : raspberry5 - disabled + system.adapter.backitup.0 : backitup : raspberry5 - enabled + system.adapter.discovery.0 : discovery : raspberry5 - enabled + system.adapter.mbus.0 : mbus : raspberry5 - enabled, port: 3493 + system.adapter.node-red.0 : node-red : raspberry5 - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.reolink.0 : reolink : raspberry5 - enabled + system.adapter.smartmeter.0 : smartmeter : raspberry5 - enabled + system.adapter.systeminfo.0 : systeminfo : raspberry5 - enabled + system.adapter.web.0 : web : raspberry5 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wireless-mbus.0 : wireless-mbus : raspberry5 - enabled + system.adapter.zigbee.0 : zigbee : raspberry5 - enabled, port: tcp://192.168.178.203:7638 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberry5 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.mbus.0 : mbus : raspberry5 - enabled, port: 3493 + system.adapter.node-red.0 : node-red : raspberry5 - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberry5 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberry5 - enabled, port: tcp://192.168.178.203:7638 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 ┌─────────┬────────────────────────────────┬─────────────────┬──────────┬────────────────┐ │ (index) │ id │ name │ version │ upgrade policy │ ├─────────┼────────────────────────────────┼─────────────────┼──────────┼────────────────┤ │ 0 │ 'system.adapter.admin' │ 'admin' │ '8.0.11' │ 'none' │ │ 1 │ 'system.adapter.alias-manager' │ 'alias-manager' │ '2.1.0' │ 'none' │ │ 2 │ 'system.adapter.backitup' │ 'backitup' │ '4.0.3' │ 'none' │ │ 3 │ 'system.adapter.discovery' │ 'discovery' │ '5.0.0' │ 'none' │ │ 4 │ 'system.adapter.influxdb' │ 'influxdb' │ '4.0.2' │ 'none' │ │ 5 │ 'system.adapter.mbus' │ 'mbus' │ '2.7.0' │ 'none' │ │ 6 │ 'system.adapter.node-red' │ 'node-red' │ '6.0.7' │ 'none' │ │ 7 │ 'system.adapter.reolink' │ 'reolink' │ '1.4.2' │ 'none' │ │ 8 │ 'system.adapter.smartmeter' │ 'smartmeter' │ '3.4.0' │ 'none' │ │ 9 │ 'system.adapter.socketio' │ 'socketio' │ '7.1.3' │ 'none' │ │ 10 │ 'system.adapter.systeminfo' │ 'systeminfo' │ '1.3.0' │ 'none' │ │ 11 │ 'system.adapter.web' │ 'web' │ '8.0.0' │ 'none' │ │ 12 │ 'system.adapter.wireless-mbus' │ 'wireless-mbus' │ '0.10.2' │ 'none' │ │ 13 │ 'system.adapter.ws' │ 'ws' │ '4.1.0' │ 'none' │ │ 14 │ 'system.adapter.zigbee' │ 'zigbee' │ '3.5.5' │ 'none' │ └─────────┴────────────────────────────────┴─────────────────┴──────────┴────────────────┘ ioBroker-Adapter Versions and update status Used repository: stable Adapter "admin" : 8.0.11 , installed 8.0.11 Adapter "alias-manager": 2.1.0 , installed 2.1.0 Adapter "backitup" : 4.0.3 , installed 4.0.3 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Controller "js-controller": 7.2.2 , installed 7.2.2 Adapter "mbus" : 2.7.0 , installed 2.7.0 Adapter "node-red" : 6.0.7 , installed 6.0.7 Adapter "reolink" : 1.4.2 , installed 1.4.2 Adapter "smartmeter" : 3.4.0 , installed 3.4.0 Adapter "socketio" : 7.1.3 , installed 7.1.3 Adapter "systeminfo" : 1.3.0 , installed 1.3.0 Adapter "web" : 8.0.0 , installed 8.0.0 Adapter "wireless-mbus": 0.10.2 , installed 0.10.2 Adapter "ws" : 4.1.0 , installed 4.1.0 Adapter "zigbee" : 3.5.5 , installed 3.5.5 Objects and States Please stand by - This may take a while Objects: 777 States: 613 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://deb.debian.org/debian-security trixie-security InRelease Hit:4 http://archive.raspberrypi.com/debian trixie InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Get:6 https://repos.influxdata.com/debian stable InRelease [6922 B] Fetched 6922 B in 0s (23.3 kB/s) Reading package lists... Pending systemupdates: 0 *** Listening Ports *** Netid State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess udp UNCONN 0 0 0.0.0.0:sunrpc 0.0.0.0:* users:(("rpcbind",pid=663,fd=5),("systemd",pid=1,fd=150)) udp UNCONN 0 0 0.0.0.0:mdns 0.0.0.0:* users:(("avahi-daemon",pid=687,fd=12)) udp UNCONN 0 0 0.0.0.0:52092 0.0.0.0:* users:(("avahi-daemon",pid=687,fd=14)) udp UNCONN 0 0 *:sunrpc *:* users:(("rpcbind",pid=663,fd=7),("systemd",pid=1,fd=152)) udp UNCONN 0 0 [fe80::8aa2:9eff:fef2:8ad1]:dhcpv6-client *:* users:(("NetworkManager",pid=746,fd=24)) udp UNCONN 0 0 *:mdns *:* users:(("avahi-daemon",pid=687,fd=13)) udp UNCONN 0 0 *:56789 *:* users:(("avahi-daemon",pid=687,fd=15)) tcp LISTEN 0 511 127.0.0.1:9000 0.0.0.0:* users:(("iobroker.js-con",pid=3830,fd=29)) tcp LISTEN 0 511 127.0.0.1:9001 0.0.0.0:* users:(("iobroker.js-con",pid=3830,fd=23)) tcp LISTEN 0 4096 0.0.0.0:sunrpc 0.0.0.0:* users:(("rpcbind",pid=663,fd=4),("systemd",pid=1,fd=149)) tcp LISTEN 0 128 0.0.0.0:ssh 0.0.0.0:* users:(("sshd",pid=1176,fd=6)) tcp LISTEN 2 511 0.0.0.0:1880 0.0.0.0:* users:(("node-red",pid=3914,fd=24)) tcp LISTEN 0 511 *:8082 *:* users:(("io.web.0",pid=4303,fd=35)) tcp LISTEN 0 511 *:tproxy *:* users:(("io.admin.0",pid=3850,fd=39)) tcp LISTEN 0 4096 [::]:sunrpc [::]:* users:(("rpcbind",pid=663,fd=6),("systemd",pid=1,fd=151)) tcp LISTEN 0 128 [::]:ssh [::]:* users:(("sshd",pid=1176,fd=7)) tcp LISTEN 0 511 *:10001 *:* users:(("node-red",pid=3914,fd=60)) *** Log File - Last 25 Lines *** 2026-09-20 20:37:39.073 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:38:10.073 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:38:41.063 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:39:12.061 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:39:43.064 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:40:14.056 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:40:17.328 - debug: node-red.0 (3898) Node-RED: 20 Sep 20:40:17 - [info] [ui-scheduler:Hochbeet] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application 2026-09-20 20:40:17.373 - debug: node-red.0 (3898) Node-RED: 20 Sep 20:40:17 - [info] [ui-scheduler:scheduler] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application 2026-09-20 20:40:17.389 - error: node-red.0 (3898) Node-RED: 20 Sep 20:40:17 - [error] [google-home-conf:f3d8c7527a11ea59] Error: connack timeout at Timeout._onTimeout (/opt/iobroker/iobroker-data/node-red/node_modules/mqtt/build/lib/client.js:363:32) at listOnTimeout (node:internal/timers:585:17) at process.processTimers (node:internal/timers:521:7) 2026-09-20 20:40:45.058 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:41:13.738 - warn: zigbee.0 (4196) DeviceAvailability:ELEVATED: Non-pingable device 'Temperatur_Aussen (0xf044d3fffebd4a7c)' was last seen '1285.136' seconds ago. 2026-09-20 20:41:13.740 - warn: zigbee.0 (4196) DeviceAvailability:ELEVATED: Non-pingable device 'Kontakt_Tuer_Wohnzimmer (0x00158d008c835388)' was last seen '421.475' seconds ago. 2026-09-20 20:41:16.051 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:41:47.050 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:42:18.048 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:42:49.049 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:43:20.042 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:43:51.042 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:44:22.039 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:44:53.046 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:45:24.042 - info: smartmeter.0 (4235) Received 5 values, 2 updated 2026-09-20 20:45:55.553 - info: smartmeter.0 (4235) Received 5 values, 2 updated============= Mark until here for C&P =============
-
Der Hauptfehler, der sich durch das log zieht, ist
2026-09-20 20:12:52.682 - error: node-red.0 (2300) Node-RED: 20 Sep 20:12:52 - [error] Unable to listen on http://127.0.0.1:1880/ 2026-09-20 20:12:52.683 - error: node-red.0 (2300) Node-RED: 20 Sep 20:12:52 - [error] Error: port in useD.h. der Port über den der Adapter mit nodered kommuniziert ist bereits in Nutzung.
Hast du zwei Instanzen nodered installiert?
Ansonsten musst du mal auf dem Rechner schauen, ob es noch einen anderen Server gibt, der auf dem Port 1880 horcht. -
-
-
Bitte keine Screenshots
Wenn der erste Befehl nicht funktioniert hat woher hast du dann den pid 24?Ah weiter oben.
Ich sagte pid und nicht fd
Aber man sieht schon es läuft nodered
Wahrscheinlich noch ein Zombie ProzessAls erstes Iobroker neu starten und wenn dann immer noch dann Rechner neu starten
-
Hallo,
danke für den Hinweis bezüglich des Screenshots. Für mich als Newbie war das die einfachste Möglichkeit, zu beschreiben, welches Ergebnis die vorgeschlagene Befehlseingabe geliefert hat.
Was hätte ich stattdessen (ps -fp 24) eingeben sollen? Wo finde ich die PID?
Den Raspberry habe ich bereits mehrfach neu gestartet. Wenn ich die Node-RED-Instanz anschließend im abgesicherten Modus starte (entsprechendes Häkchen in der ioBroker-Instanz gesetzt), funktioniert das erste deployen problemlos. Danach wird das System jedoch wieder sehr langsam. Das Dashboard ist nicht mehr erreichbar, und ein weiteres deployen ist ebenfalls nicht mehr möglich bzw. dauert unendlich.
-
Hallo,
danke für den Hinweis bezüglich des Screenshots. Für mich als Newbie war das die einfachste Möglichkeit, zu beschreiben, welches Ergebnis die vorgeschlagene Befehlseingabe geliefert hat.
Was hätte ich stattdessen (ps -fp 24) eingeben sollen? Wo finde ich die PID?
Den Raspberry habe ich bereits mehrfach neu gestartet. Wenn ich die Node-RED-Instanz anschließend im abgesicherten Modus starte (entsprechendes Häkchen in der ioBroker-Instanz gesetzt), funktioniert das erste deployen problemlos. Danach wird das System jedoch wieder sehr langsam. Das Dashboard ist nicht mehr erreichbar, und ein weiteres deployen ist ebenfalls nicht mehr möglich bzw. dauert unendlich.
Was hätte ich stattdessen (ps -fp 24) eingeben sollen? Wo finde ich die PID?
richtiges und genaues lesen (wie in der schule früher aus einem + ein - machen war auch fatal)
in der ausgabe in deinem screenshot steht pid=246,fd=24
pid ist leider durch einen zeilenumbruch getrennt.
du hast aber halt die zahl von fd genommen, was aber eine komplett andere kennziffer ist.da aber der prozessname da ebenfalls steht, konnte man sich den ps befehl (sowas wie der process explorer von windows, dann schon sparen)
dann mache mal bitte noch mal die iobroker diagnose,
aber diesmal mit laufendem iobroker. du hast die diagnose das letzte mal gemacht, da lief der iobroker nicht. da sieht man dann auch nicht so viel. -
Hallo,
danke für den Hinweis bezüglich des Screenshots. Für mich als Newbie war das die einfachste Möglichkeit, zu beschreiben, welches Ergebnis die vorgeschlagene Befehlseingabe geliefert hat.
Was hätte ich stattdessen (ps -fp 24) eingeben sollen? Wo finde ich die PID?
Den Raspberry habe ich bereits mehrfach neu gestartet. Wenn ich die Node-RED-Instanz anschließend im abgesicherten Modus starte (entsprechendes Häkchen in der ioBroker-Instanz gesetzt), funktioniert das erste deployen problemlos. Danach wird das System jedoch wieder sehr langsam. Das Dashboard ist nicht mehr erreichbar, und ein weiteres deployen ist ebenfalls nicht mehr möglich bzw. dauert unendlich.
danke für den Hinweis bezüglich des Screenshots. Für mich als Newbie war das die einfachste Möglichkeit, zu beschreiben, welches Ergebnis die vorgeschlagene Befehlseingabe geliefert hat.
Dann koper den TEXT aus dem Termina hier rein. CodeTags drumherum und dann kann das
a) viel besser gelesen werden
b) findet das auch die Suchfunktion
c) ist ein langer Text dann auch eher vollständig und
d) ist Text wesentlich kleiner als ein Bildchen.Und Helfer können den Text auch für Ihre eigene Recherche verwenden. Geht mit Bildchens auch nicht.
-
Hallo,
danke für den Hinweis bezüglich des Screenshots. Für mich als Newbie war das die einfachste Möglichkeit, zu beschreiben, welches Ergebnis die vorgeschlagene Befehlseingabe geliefert hat.
Was hätte ich stattdessen (ps -fp 24) eingeben sollen? Wo finde ich die PID?
Den Raspberry habe ich bereits mehrfach neu gestartet. Wenn ich die Node-RED-Instanz anschließend im abgesicherten Modus starte (entsprechendes Häkchen in der ioBroker-Instanz gesetzt), funktioniert das erste deployen problemlos. Danach wird das System jedoch wieder sehr langsam. Das Dashboard ist nicht mehr erreichbar, und ein weiteres deployen ist ebenfalls nicht mehr möglich bzw. dauert unendlich.
in ergänzung zu thomas:
- genau so wie du iob diag kopiert hast und hier eingefügt hast
- ein tipp zum lernen: unter linux lassen sich alle ausgaben eines befehls auch in eine datei umleiten in dem man "> /tmp/ausgabe.txt" anhängt.
also bspw
sudo ss -ltnp | grep ':1880' > /tmp/ausgabe.txtdann landet die ausgabe in der datei im /tmp ordner.
der pfad kann natürlich entsprechend den berechtigungen frei gewählt werden. /tmp ist aber immer ein guter ort -
@thomas-braun Vielen Dank für die ausführliche Erklärung. Jetzt ist mir auch klar warum man keine Screenshots einstellen soll.
Vielen für die Geduld die Ihr mit mir habt......
So, hier die iob diag bei laufendem iobroker:
========== Start marking the full check here ===========Script v.2026-08-30 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: raspberry5 Icon name: computer Kernel: Linux 6.18.50+rpt-rpi-2712 Architecture: arm64 OS is similar to: Model : Raspberry Pi 5 Model B Rev 1.1 Docker : false Virtualization : none Unknown Kernel : aarch64 Userland : 64bit System was installed 95 days ago (on 2026-06-18). Systemuptime and Load: 20:00:56 up 22:26, 1 user, load average: 0.19, 0.10, 0.03 CPU threads : 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Mon 2026-09-21 20:00:56 CEST Universal time: Mon 2026-09-21 18:00:56 UTC RTC time: Mon 2026-09-21 18:00:56 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': mf HOME=/home/mf GROUPS=mf adm dialout cdrom sudo audio video plugdev games users netdev gpio i2c spi render input lpadmin iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: Unknown Display-Manager: Not found Desktop: Session: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 8.5G 2.0G 5.8G 21M 773M 6.4G Swap: 2.1G 0B 2.1G Total: 10G 2.0G 7.9G Active iob-Instances: 12 8062 M total memory 1947 M used memory 1789 M active memory 427 M inactive memory 5485 M free memory 112 M buffer memory 625 M swap cache 2047 M total swap 0 M used swap 2047 M free swap *** top - Table Of Processes *** top - 20:00:57 up 22:26, 1 user, load average: 0.19, 0.10, 0.03 Tasks: 171 total, 1 running, 170 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.9 us, 0.0 sy, 0.0 ni, 92.6 id, 5.6 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 8062.3 total, 5482.9 free, 1948.7 used, 738.7 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 6113.7 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 udev devtmpfs 3.9G 0 3.9G 0% /dev tmpfs tmpfs 1.6G 13M 1.6G 1% /run /dev/mmcblk0p2 ext4 58G 6.7G 49G 13% / tmpfs tmpfs 4.0G 0 4.0G 0% /dev/shm tmpfs tmpfs 5.0M 48K 5.0M 1% /run/lock tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service tmpfs tmpfs 4.0G 7.9M 4.0G 1% /tmp /dev/mmcblk0p1 vfat 505M 67M 438M 14% /boot/firmware tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/serial-getty@ttyAMA10.service tmpfs tmpfs 807M 32K 807M 1% /run/user/1000 Messages concerning filesystems in dmesg (Last 15 lines only): [Sun Sep 20 21:34:34 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs [Sun Sep 20 21:34:34 2026] EXT4-fs (mmcblk0p2): mounted filesystem 15f4c6be-1102-4331-9904-f78e78afd1fd ro with ordered data mode. Quota mode: none. [Sun Sep 20 21:34:37 2026] EXT4-fs (mmcblk0p2): re-mounted 15f4c6be-1102-4331-9904-f78e78afd1fd r/w. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime,commit=600 `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 2.5G /var/ 270M /var/cache 264M /var/cache/apt 185M /var/lib 148M /var/lib/apt/lists Archived and active journals take up 8M in the file system. /opt/iobroker/backups: 31M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 378M /opt/iobroker/iobroker-data/ 236M /opt/iobroker/iobroker-data/node-red 234M /opt/iobroker/iobroker-data/node-red/node_modules 72M /opt/iobroker/iobroker-data/backup-objects 62M /opt/iobroker/iobroker-data/node-red/node_modules/echarts The five largest files in iobroker-data are: 21M /opt/iobroker/iobroker-data/objects.jsonl 7.8M /opt/iobroker/iobroker-data/node-red/node_modules/echarts/dist/echarts.js.map 7.8M /opt/iobroker/iobroker-data/node-red/node_modules/echarts/dist/echarts.esm.mjs.map 7.8M /opt/iobroker/iobroker-data/node-red/node_modules/echarts/dist/echarts.esm.js.map 6.8M /opt/iobroker/iobroker-data/files/backitup.admin/custom/assets/_virtual_mf___mfe_internal__ConfigCustomBackItUpSet__mf_owner__1__loadShare___mf_0_iobroker_mf_1_gui_mf_2_components__loadShare__.js-Bs-T0f9g.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-SHK_NANO_CUL_868-if00-port0 /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_AVDMb135B02-if00-port0 *** ZigBee Settings *** 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' === ZigBee Port Overview === Instance Configured Port Available by-id Port Status -------- ---------------- ---------------------------- ------ zigbee.0 tcp://192.168.178.203:7638 - tcp *** NodeJS-Installation *** /usr/bin/nodejs v22.23.2 /usr/bin/node v22.23.2 /usr/bin/npm 10.9.8 /usr/bin/npx 10.9.8 ✓ Node.js installation is correct nodejs: Installed: 22.23.2-1nodesource1 Candidate: 22.23.2-1nodesource1 Version table: *** 22.23.2-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.23.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.23.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.3-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.2-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 20.19.2+dfsg-1+deb13u2 500 500 http://deb.debian.org/debian trixie/main arm64 Packages 500 http://deb.debian.org/debian-security trixie-security/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: No known Vulnerabilities detected! *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: raspberry5 raspberry5 (version: 7.2.2, hostname: raspberry5 , alive, uptime: 80781) Core adapters versions js-controller: 7.2.2 admin: 8.0.11 javascript: "javascript" not found nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberry5 - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : raspberry5 - disabled + system.adapter.backitup.0 : backitup : raspberry5 - enabled + system.adapter.discovery.0 : discovery : raspberry5 - enabled + system.adapter.mbus.0 : mbus : raspberry5 - enabled, port: 3493 + system.adapter.node-red.0 : node-red : raspberry5 - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.reolink.0 : reolink : raspberry5 - enabled + system.adapter.smartmeter.0 : smartmeter : raspberry5 - enabled + system.adapter.systeminfo.0 : systeminfo : raspberry5 - enabled + system.adapter.web.0 : web : raspberry5 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wireless-mbus.0 : wireless-mbus : raspberry5 - enabled + system.adapter.zigbee.0 : zigbee : raspberry5 - enabled, port: tcp://192.168.178.203:7638 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberry5 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.mbus.0 : mbus : raspberry5 - enabled, port: 3493 + system.adapter.node-red.0 : node-red : raspberry5 - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberry5 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberry5 - enabled, port: tcp://192.168.178.203:7638 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 ┌─────────┬────────────────────────────────┬─────────────────┬──────────┬────────────────┐ │ (index) │ id │ name │ version │ upgrade policy │ ├─────────┼────────────────────────────────┼─────────────────┼──────────┼────────────────┤ │ 0 │ 'system.adapter.admin' │ 'admin' │ '8.0.11' │ 'none' │ │ 1 │ 'system.adapter.alias-manager' │ 'alias-manager' │ '2.1.0' │ 'none' │ │ 2 │ 'system.adapter.backitup' │ 'backitup' │ '4.0.3' │ 'none' │ │ 3 │ 'system.adapter.discovery' │ 'discovery' │ '5.0.0' │ 'none' │ │ 4 │ 'system.adapter.influxdb' │ 'influxdb' │ '4.0.2' │ 'none' │ │ 5 │ 'system.adapter.mbus' │ 'mbus' │ '2.7.0' │ 'none' │ │ 6 │ 'system.adapter.node-red' │ 'node-red' │ '6.0.7' │ 'none' │ │ 7 │ 'system.adapter.reolink' │ 'reolink' │ '1.4.2' │ 'none' │ │ 8 │ 'system.adapter.smartmeter' │ 'smartmeter' │ '3.4.0' │ 'none' │ │ 9 │ 'system.adapter.socketio' │ 'socketio' │ '7.1.3' │ 'none' │ │ 10 │ 'system.adapter.systeminfo' │ 'systeminfo' │ '1.3.0' │ 'none' │ │ 11 │ 'system.adapter.web' │ 'web' │ '8.0.0' │ 'none' │ │ 12 │ 'system.adapter.wireless-mbus' │ 'wireless-mbus' │ '0.10.2' │ 'none' │ │ 13 │ 'system.adapter.ws' │ 'ws' │ '4.1.0' │ 'none' │ │ 14 │ 'system.adapter.zigbee' │ 'zigbee' │ '3.5.5' │ 'none' │ └─────────┴────────────────────────────────┴─────────────────┴──────────┴────────────────┘ ioBroker-Adapter Versions and update status Used repository: stable Adapter "admin" : 8.0.11 , installed 8.0.11 Adapter "alias-manager": 2.1.0 , installed 2.1.0 Adapter "backitup" : 4.0.3 , installed 4.0.3 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Controller "js-controller": 7.2.2 , installed 7.2.2 Adapter "mbus" : 2.7.0 , installed 2.7.0 Adapter "node-red" : 6.0.7 , installed 6.0.7 Adapter "reolink" : 1.4.2 , installed 1.4.2 Adapter "smartmeter" : 3.4.0 , installed 3.4.0 Adapter "socketio" : 7.1.3 , installed 7.1.3 Adapter "systeminfo" : 1.3.0 , installed 1.3.0 Adapter "web" : 8.0.0 , installed 8.0.0 Adapter "wireless-mbus": 0.10.2 , installed 0.10.2 Adapter "ws" : 4.1.0 , installed 4.1.0 Adapter "zigbee" : 3.5.5 , installed 3.5.5 Objects and States Please stand by - This may take a while Objects: 777 States: 613 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://deb.debian.org/debian-security trixie-security InRelease Hit:4 http://archive.raspberrypi.com/debian trixie InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Get:6 https://repos.influxdata.com/debian stable InRelease [6922 B] Fetched 6922 B in 0s (34.4 kB/s) Reading package lists... Pending systemupdates: 1 *** Listening Ports *** Netid State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess udp UNCONN 0 0 0.0.0.0:sunrpc 0.0.0.0:* users:(("rpcbind",pid=653,fd=5),("systemd",pid=1,fd=117)) udp UNCONN 0 0 0.0.0.0:33590 0.0.0.0:* users:(("avahi-daemon",pid=677,fd=14)) udp UNCONN 0 0 0.0.0.0:mdns 0.0.0.0:* users:(("avahi-daemon",pid=677,fd=12)) udp UNCONN 0 0 *:40278 *:* users:(("avahi-daemon",pid=677,fd=15)) udp UNCONN 0 0 *:sunrpc *:* users:(("rpcbind",pid=653,fd=7),("systemd",pid=1,fd=119)) udp UNCONN 0 0 [fe80::8aa2:9eff:fef2:8ad1]:dhcpv6-client *:* users:(("NetworkManager",pid=738,fd=24)) udp UNCONN 0 0 *:mdns *:* users:(("avahi-daemon",pid=677,fd=13)) tcp LISTEN 0 4096 0.0.0.0:sunrpc 0.0.0.0:* users:(("rpcbind",pid=653,fd=4),("systemd",pid=1,fd=116)) tcp LISTEN 0 128 0.0.0.0:ssh 0.0.0.0:* users:(("sshd",pid=1167,fd=6)) tcp LISTEN 0 511 127.0.0.1:9001 0.0.0.0:* users:(("iobroker.js-con",pid=1154,fd=23)) tcp LISTEN 0 511 127.0.0.1:9000 0.0.0.0:* users:(("iobroker.js-con",pid=1154,fd=29)) tcp LISTEN 0 511 0.0.0.0:1880 0.0.0.0:* users:(("node-red",pid=1246,fd=24)) tcp LISTEN 0 511 *:8082 *:* users:(("io.web.0",pid=1674,fd=35)) tcp LISTEN 0 511 *:tproxy *:* users:(("io.admin.0",pid=1204,fd=39)) tcp LISTEN 0 4096 [::]:sunrpc [::]:* users:(("rpcbind",pid=653,fd=6),("systemd",pid=1,fd=118)) tcp LISTEN 0 128 [::]:ssh [::]:* users:(("sshd",pid=1167,fd=7)) tcp LISTEN 0 511 *:10001 *:* users:(("node-red",pid=1246,fd=59)) *** Log File - Last 25 Lines *** 2026-09-21 19:57:25.728 - warn: node-red.0 (1225) Node-RED: 21 Sep 19:57:25 - [warn] [shelly-gen1:f1125e919646b337] Error in executeCommand1: /color/0?turn=off&brightness=0 --> Error: connect EHOSTUNREACH 192.168.178.46:80 2026-09-21 19:57:25.729 - warn: node-red.0 (1225) Node-RED: 21 Sep 19:57:25 - [warn] [shelly-gen2:bbafaff93d9d0b07] connect EHOSTUNREACH 192.168.178.43:80 2026-09-21 19:57:25.730 - warn: node-red.0 (1225) Node-RED: 21 Sep 19:57:25 - [warn] [shelly-gen2:d7320743653ee5c1] connect EHOSTUNREACH 192.168.178.39:80 2026-09-21 19:57:29.004 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 19:58:00.007 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 19:58:31.000 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 19:59:01.998 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 19:59:16.006 - info: admin.0 (1204) ==> Connected system.user.admin from ::ffff:192.168.178.2 2026-09-21 19:59:32.995 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 20:00:03.992 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 20:00:11.733 - warn: zigbee.0 (1564) DeviceAvailability:ELEVATED: Non-pingable device 'Temperatur_Aussen (0xf044d3fffebd4a7c)' was last seen '269.363' seconds ago. 2026-09-21 20:00:11.736 - warn: zigbee.0 (1564) DeviceAvailability:ELEVATED: Non-pingable device 'Kontakt_Tuer_Wohnzimmer (0x00158d008c835388)' was last seen '1584.402' seconds ago. 2026-09-21 20:00:34.991 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 20:01:00.012 - warn: systeminfo.0 (1342) State "systeminfo.0.NAS.Space_?" has no existing object, this might lead to an error in future versions 2026-09-21 20:01:05.988 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 20:01:23.876 - warn: zigbee.0 (1564) ELEVATED:I01 (38a4) Zigbee Event of Type attributeReport from device 'Temperatur_Aussen (0xf044d3fffebd4a7c)', incoming event: {"type":"attributeReport","data":{"measuredValue":6880},"linkquality":0,"groupID":0,"cluster":"msRelativeHumidity","meta":{"rawData":{"type":"Buffer","data":[8,11,10,0,0,33,224,26]},"zclTransactionSequenceNumber":11,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1} 2026-09-21 20:01:23.877 - warn: zigbee.0 (1564) ELEVATED:I03 (38a5) message received '{"available":true}' from device 'Temperatur_Aussen (f044d3fffebd4a7c)' type 'SNZB-02P' 2026-09-21 20:01:23.877 - warn: zigbee.0 (1564) ELEVATED:I04 (38a5) value generated 'true' from device 'Temperatur_Aussen (f044d3fffebd4a7c)' for 'Available' 2026-09-21 20:01:23.878 - warn: zigbee.0 (1564) ELEVATED:I02 (38a4) 1 converter available for 'SNZB-02P' 'Temperatur_Aussen (f044d3fffebd4a7c)' with cluster 'msRelativeHumidity' and type 'attributeReport' 2026-09-21 20:01:23.878 - warn: zigbee.0 (1564) ELEVATED:I02.1a (38a4) converter 1 : Cluster msRelativeHumidity 2026-09-21 20:01:23.878 - warn: zigbee.0 (1564) ELEVATED:I02.0b (38a4) data: {"measuredValue":6880} options: {} meta:{"deviceIEEE":"0xf044d3fffebd4a7c","logger":"StatesController","state":{"state":""}} result:{"humidity":68.8} 2026-09-21 20:01:23.878 - warn: zigbee.0 (1564) ELEVATED:I02.1c (38a4) candidates: [{"humidity":68.8}] => payload {"humidity":68.8} 2026-09-21 20:01:23.879 - warn: zigbee.0 (1564) ELEVATED:I03 (38a4) message received '{"humidity":68.8}' from device 'Temperatur_Aussen (f044d3fffebd4a7c)' type 'SNZB-02P' 2026-09-21 20:01:23.879 - warn: zigbee.0 (1564) ELEVATED:I04 (38a4) value generated '68.8' from device 'Temperatur_Aussen (f044d3fffebd4a7c)' for 'Measured relative humidity' 2026-09-21 20:01:36.986 - info: smartmeter.0 (1590) Received 5 values, 2 updated============= Mark until here for C&P =============
Und nochmal die vorgeschlagene Befehlsfolge:
mf@raspberry5:~ $ mf@raspberry5:~ $ sudo ss -ltnp | grep ':1880' LISTEN 0 511 0.0.0.0:1880 0.0.0.0:* users:(("node-red",pi d=1246,fd=24)) mf@raspberry5:~ $ ps -fp 1246 UID PID PPID C STIME TTY TIME CMD iobroker 1246 1225 2 Sep20 ? 00:32:47 node-red mf@raspberry5:~ $ -
@thomas-braun Vielen Dank für die ausführliche Erklärung. Jetzt ist mir auch klar warum man keine Screenshots einstellen soll.
Vielen für die Geduld die Ihr mit mir habt......
So, hier die iob diag bei laufendem iobroker:
========== Start marking the full check here ===========Script v.2026-08-30 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: raspberry5 Icon name: computer Kernel: Linux 6.18.50+rpt-rpi-2712 Architecture: arm64 OS is similar to: Model : Raspberry Pi 5 Model B Rev 1.1 Docker : false Virtualization : none Unknown Kernel : aarch64 Userland : 64bit System was installed 95 days ago (on 2026-06-18). Systemuptime and Load: 20:00:56 up 22:26, 1 user, load average: 0.19, 0.10, 0.03 CPU threads : 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Mon 2026-09-21 20:00:56 CEST Universal time: Mon 2026-09-21 18:00:56 UTC RTC time: Mon 2026-09-21 18:00:56 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': mf HOME=/home/mf GROUPS=mf adm dialout cdrom sudo audio video plugdev games users netdev gpio i2c spi render input lpadmin iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: Unknown Display-Manager: Not found Desktop: Session: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 8.5G 2.0G 5.8G 21M 773M 6.4G Swap: 2.1G 0B 2.1G Total: 10G 2.0G 7.9G Active iob-Instances: 12 8062 M total memory 1947 M used memory 1789 M active memory 427 M inactive memory 5485 M free memory 112 M buffer memory 625 M swap cache 2047 M total swap 0 M used swap 2047 M free swap *** top - Table Of Processes *** top - 20:00:57 up 22:26, 1 user, load average: 0.19, 0.10, 0.03 Tasks: 171 total, 1 running, 170 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.9 us, 0.0 sy, 0.0 ni, 92.6 id, 5.6 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 8062.3 total, 5482.9 free, 1948.7 used, 738.7 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 6113.7 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 udev devtmpfs 3.9G 0 3.9G 0% /dev tmpfs tmpfs 1.6G 13M 1.6G 1% /run /dev/mmcblk0p2 ext4 58G 6.7G 49G 13% / tmpfs tmpfs 4.0G 0 4.0G 0% /dev/shm tmpfs tmpfs 5.0M 48K 5.0M 1% /run/lock tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service tmpfs tmpfs 4.0G 7.9M 4.0G 1% /tmp /dev/mmcblk0p1 vfat 505M 67M 438M 14% /boot/firmware tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/serial-getty@ttyAMA10.service tmpfs tmpfs 807M 32K 807M 1% /run/user/1000 Messages concerning filesystems in dmesg (Last 15 lines only): [Sun Sep 20 21:34:34 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs [Sun Sep 20 21:34:34 2026] EXT4-fs (mmcblk0p2): mounted filesystem 15f4c6be-1102-4331-9904-f78e78afd1fd ro with ordered data mode. Quota mode: none. [Sun Sep 20 21:34:37 2026] EXT4-fs (mmcblk0p2): re-mounted 15f4c6be-1102-4331-9904-f78e78afd1fd r/w. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime,commit=600 `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 2.5G /var/ 270M /var/cache 264M /var/cache/apt 185M /var/lib 148M /var/lib/apt/lists Archived and active journals take up 8M in the file system. /opt/iobroker/backups: 31M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 378M /opt/iobroker/iobroker-data/ 236M /opt/iobroker/iobroker-data/node-red 234M /opt/iobroker/iobroker-data/node-red/node_modules 72M /opt/iobroker/iobroker-data/backup-objects 62M /opt/iobroker/iobroker-data/node-red/node_modules/echarts The five largest files in iobroker-data are: 21M /opt/iobroker/iobroker-data/objects.jsonl 7.8M /opt/iobroker/iobroker-data/node-red/node_modules/echarts/dist/echarts.js.map 7.8M /opt/iobroker/iobroker-data/node-red/node_modules/echarts/dist/echarts.esm.mjs.map 7.8M /opt/iobroker/iobroker-data/node-red/node_modules/echarts/dist/echarts.esm.js.map 6.8M /opt/iobroker/iobroker-data/files/backitup.admin/custom/assets/_virtual_mf___mfe_internal__ConfigCustomBackItUpSet__mf_owner__1__loadShare___mf_0_iobroker_mf_1_gui_mf_2_components__loadShare__.js-Bs-T0f9g.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-SHK_NANO_CUL_868-if00-port0 /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_AVDMb135B02-if00-port0 *** ZigBee Settings *** 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' === ZigBee Port Overview === Instance Configured Port Available by-id Port Status -------- ---------------- ---------------------------- ------ zigbee.0 tcp://192.168.178.203:7638 - tcp *** NodeJS-Installation *** /usr/bin/nodejs v22.23.2 /usr/bin/node v22.23.2 /usr/bin/npm 10.9.8 /usr/bin/npx 10.9.8 ✓ Node.js installation is correct nodejs: Installed: 22.23.2-1nodesource1 Candidate: 22.23.2-1nodesource1 Version table: *** 22.23.2-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.23.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.23.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.3-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.2-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.22.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 20.19.2+dfsg-1+deb13u2 500 500 http://deb.debian.org/debian trixie/main arm64 Packages 500 http://deb.debian.org/debian-security trixie-security/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: No known Vulnerabilities detected! *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: raspberry5 raspberry5 (version: 7.2.2, hostname: raspberry5 , alive, uptime: 80781) Core adapters versions js-controller: 7.2.2 admin: 8.0.11 javascript: "javascript" not found nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberry5 - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : raspberry5 - disabled + system.adapter.backitup.0 : backitup : raspberry5 - enabled + system.adapter.discovery.0 : discovery : raspberry5 - enabled + system.adapter.mbus.0 : mbus : raspberry5 - enabled, port: 3493 + system.adapter.node-red.0 : node-red : raspberry5 - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.reolink.0 : reolink : raspberry5 - enabled + system.adapter.smartmeter.0 : smartmeter : raspberry5 - enabled + system.adapter.systeminfo.0 : systeminfo : raspberry5 - enabled + system.adapter.web.0 : web : raspberry5 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wireless-mbus.0 : wireless-mbus : raspberry5 - enabled + system.adapter.zigbee.0 : zigbee : raspberry5 - enabled, port: tcp://192.168.178.203:7638 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberry5 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.mbus.0 : mbus : raspberry5 - enabled, port: 3493 + system.adapter.node-red.0 : node-red : raspberry5 - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberry5 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberry5 - enabled, port: tcp://192.168.178.203:7638 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 ┌─────────┬────────────────────────────────┬─────────────────┬──────────┬────────────────┐ │ (index) │ id │ name │ version │ upgrade policy │ ├─────────┼────────────────────────────────┼─────────────────┼──────────┼────────────────┤ │ 0 │ 'system.adapter.admin' │ 'admin' │ '8.0.11' │ 'none' │ │ 1 │ 'system.adapter.alias-manager' │ 'alias-manager' │ '2.1.0' │ 'none' │ │ 2 │ 'system.adapter.backitup' │ 'backitup' │ '4.0.3' │ 'none' │ │ 3 │ 'system.adapter.discovery' │ 'discovery' │ '5.0.0' │ 'none' │ │ 4 │ 'system.adapter.influxdb' │ 'influxdb' │ '4.0.2' │ 'none' │ │ 5 │ 'system.adapter.mbus' │ 'mbus' │ '2.7.0' │ 'none' │ │ 6 │ 'system.adapter.node-red' │ 'node-red' │ '6.0.7' │ 'none' │ │ 7 │ 'system.adapter.reolink' │ 'reolink' │ '1.4.2' │ 'none' │ │ 8 │ 'system.adapter.smartmeter' │ 'smartmeter' │ '3.4.0' │ 'none' │ │ 9 │ 'system.adapter.socketio' │ 'socketio' │ '7.1.3' │ 'none' │ │ 10 │ 'system.adapter.systeminfo' │ 'systeminfo' │ '1.3.0' │ 'none' │ │ 11 │ 'system.adapter.web' │ 'web' │ '8.0.0' │ 'none' │ │ 12 │ 'system.adapter.wireless-mbus' │ 'wireless-mbus' │ '0.10.2' │ 'none' │ │ 13 │ 'system.adapter.ws' │ 'ws' │ '4.1.0' │ 'none' │ │ 14 │ 'system.adapter.zigbee' │ 'zigbee' │ '3.5.5' │ 'none' │ └─────────┴────────────────────────────────┴─────────────────┴──────────┴────────────────┘ ioBroker-Adapter Versions and update status Used repository: stable Adapter "admin" : 8.0.11 , installed 8.0.11 Adapter "alias-manager": 2.1.0 , installed 2.1.0 Adapter "backitup" : 4.0.3 , installed 4.0.3 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Controller "js-controller": 7.2.2 , installed 7.2.2 Adapter "mbus" : 2.7.0 , installed 2.7.0 Adapter "node-red" : 6.0.7 , installed 6.0.7 Adapter "reolink" : 1.4.2 , installed 1.4.2 Adapter "smartmeter" : 3.4.0 , installed 3.4.0 Adapter "socketio" : 7.1.3 , installed 7.1.3 Adapter "systeminfo" : 1.3.0 , installed 1.3.0 Adapter "web" : 8.0.0 , installed 8.0.0 Adapter "wireless-mbus": 0.10.2 , installed 0.10.2 Adapter "ws" : 4.1.0 , installed 4.1.0 Adapter "zigbee" : 3.5.5 , installed 3.5.5 Objects and States Please stand by - This may take a while Objects: 777 States: 613 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://deb.debian.org/debian-security trixie-security InRelease Hit:4 http://archive.raspberrypi.com/debian trixie InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Get:6 https://repos.influxdata.com/debian stable InRelease [6922 B] Fetched 6922 B in 0s (34.4 kB/s) Reading package lists... Pending systemupdates: 1 *** Listening Ports *** Netid State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess udp UNCONN 0 0 0.0.0.0:sunrpc 0.0.0.0:* users:(("rpcbind",pid=653,fd=5),("systemd",pid=1,fd=117)) udp UNCONN 0 0 0.0.0.0:33590 0.0.0.0:* users:(("avahi-daemon",pid=677,fd=14)) udp UNCONN 0 0 0.0.0.0:mdns 0.0.0.0:* users:(("avahi-daemon",pid=677,fd=12)) udp UNCONN 0 0 *:40278 *:* users:(("avahi-daemon",pid=677,fd=15)) udp UNCONN 0 0 *:sunrpc *:* users:(("rpcbind",pid=653,fd=7),("systemd",pid=1,fd=119)) udp UNCONN 0 0 [fe80::8aa2:9eff:fef2:8ad1]:dhcpv6-client *:* users:(("NetworkManager",pid=738,fd=24)) udp UNCONN 0 0 *:mdns *:* users:(("avahi-daemon",pid=677,fd=13)) tcp LISTEN 0 4096 0.0.0.0:sunrpc 0.0.0.0:* users:(("rpcbind",pid=653,fd=4),("systemd",pid=1,fd=116)) tcp LISTEN 0 128 0.0.0.0:ssh 0.0.0.0:* users:(("sshd",pid=1167,fd=6)) tcp LISTEN 0 511 127.0.0.1:9001 0.0.0.0:* users:(("iobroker.js-con",pid=1154,fd=23)) tcp LISTEN 0 511 127.0.0.1:9000 0.0.0.0:* users:(("iobroker.js-con",pid=1154,fd=29)) tcp LISTEN 0 511 0.0.0.0:1880 0.0.0.0:* users:(("node-red",pid=1246,fd=24)) tcp LISTEN 0 511 *:8082 *:* users:(("io.web.0",pid=1674,fd=35)) tcp LISTEN 0 511 *:tproxy *:* users:(("io.admin.0",pid=1204,fd=39)) tcp LISTEN 0 4096 [::]:sunrpc [::]:* users:(("rpcbind",pid=653,fd=6),("systemd",pid=1,fd=118)) tcp LISTEN 0 128 [::]:ssh [::]:* users:(("sshd",pid=1167,fd=7)) tcp LISTEN 0 511 *:10001 *:* users:(("node-red",pid=1246,fd=59)) *** Log File - Last 25 Lines *** 2026-09-21 19:57:25.728 - warn: node-red.0 (1225) Node-RED: 21 Sep 19:57:25 - [warn] [shelly-gen1:f1125e919646b337] Error in executeCommand1: /color/0?turn=off&brightness=0 --> Error: connect EHOSTUNREACH 192.168.178.46:80 2026-09-21 19:57:25.729 - warn: node-red.0 (1225) Node-RED: 21 Sep 19:57:25 - [warn] [shelly-gen2:bbafaff93d9d0b07] connect EHOSTUNREACH 192.168.178.43:80 2026-09-21 19:57:25.730 - warn: node-red.0 (1225) Node-RED: 21 Sep 19:57:25 - [warn] [shelly-gen2:d7320743653ee5c1] connect EHOSTUNREACH 192.168.178.39:80 2026-09-21 19:57:29.004 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 19:58:00.007 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 19:58:31.000 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 19:59:01.998 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 19:59:16.006 - info: admin.0 (1204) ==> Connected system.user.admin from ::ffff:192.168.178.2 2026-09-21 19:59:32.995 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 20:00:03.992 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 20:00:11.733 - warn: zigbee.0 (1564) DeviceAvailability:ELEVATED: Non-pingable device 'Temperatur_Aussen (0xf044d3fffebd4a7c)' was last seen '269.363' seconds ago. 2026-09-21 20:00:11.736 - warn: zigbee.0 (1564) DeviceAvailability:ELEVATED: Non-pingable device 'Kontakt_Tuer_Wohnzimmer (0x00158d008c835388)' was last seen '1584.402' seconds ago. 2026-09-21 20:00:34.991 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 20:01:00.012 - warn: systeminfo.0 (1342) State "systeminfo.0.NAS.Space_?" has no existing object, this might lead to an error in future versions 2026-09-21 20:01:05.988 - info: smartmeter.0 (1590) Received 5 values, 2 updated 2026-09-21 20:01:23.876 - warn: zigbee.0 (1564) ELEVATED:I01 (38a4) Zigbee Event of Type attributeReport from device 'Temperatur_Aussen (0xf044d3fffebd4a7c)', incoming event: {"type":"attributeReport","data":{"measuredValue":6880},"linkquality":0,"groupID":0,"cluster":"msRelativeHumidity","meta":{"rawData":{"type":"Buffer","data":[8,11,10,0,0,33,224,26]},"zclTransactionSequenceNumber":11,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1} 2026-09-21 20:01:23.877 - warn: zigbee.0 (1564) ELEVATED:I03 (38a5) message received '{"available":true}' from device 'Temperatur_Aussen (f044d3fffebd4a7c)' type 'SNZB-02P' 2026-09-21 20:01:23.877 - warn: zigbee.0 (1564) ELEVATED:I04 (38a5) value generated 'true' from device 'Temperatur_Aussen (f044d3fffebd4a7c)' for 'Available' 2026-09-21 20:01:23.878 - warn: zigbee.0 (1564) ELEVATED:I02 (38a4) 1 converter available for 'SNZB-02P' 'Temperatur_Aussen (f044d3fffebd4a7c)' with cluster 'msRelativeHumidity' and type 'attributeReport' 2026-09-21 20:01:23.878 - warn: zigbee.0 (1564) ELEVATED:I02.1a (38a4) converter 1 : Cluster msRelativeHumidity 2026-09-21 20:01:23.878 - warn: zigbee.0 (1564) ELEVATED:I02.0b (38a4) data: {"measuredValue":6880} options: {} meta:{"deviceIEEE":"0xf044d3fffebd4a7c","logger":"StatesController","state":{"state":""}} result:{"humidity":68.8} 2026-09-21 20:01:23.878 - warn: zigbee.0 (1564) ELEVATED:I02.1c (38a4) candidates: [{"humidity":68.8}] => payload {"humidity":68.8} 2026-09-21 20:01:23.879 - warn: zigbee.0 (1564) ELEVATED:I03 (38a4) message received '{"humidity":68.8}' from device 'Temperatur_Aussen (f044d3fffebd4a7c)' type 'SNZB-02P' 2026-09-21 20:01:23.879 - warn: zigbee.0 (1564) ELEVATED:I04 (38a4) value generated '68.8' from device 'Temperatur_Aussen (f044d3fffebd4a7c)' for 'Measured relative humidity' 2026-09-21 20:01:36.986 - info: smartmeter.0 (1590) Received 5 values, 2 updated============= Mark until here for C&P =============
Und nochmal die vorgeschlagene Befehlsfolge:
mf@raspberry5:~ $ mf@raspberry5:~ $ sudo ss -ltnp | grep ':1880' LISTEN 0 511 0.0.0.0:1880 0.0.0.0:* users:(("node-red",pi d=1246,fd=24)) mf@raspberry5:~ $ ps -fp 1246 UID PID PPID C STIME TTY TIME CMD iobroker 1246 1225 2 Sep20 ? 00:32:47 node-red mf@raspberry5:~ $Also in irgendwelchen nodes hast du schon mal Fehler
2026-09-21 19:57:25.728 - warn: node-red.0 (1225) Node-RED: 21 Sep 19:57:25 - [warn] [shelly-gen1:f1125e919646b337] Error in executeCommand1: /color/0?turn=off&brightness=0 --> Error: connect EHOSTUNREACH 192.168.178.46:80 2026-09-21 19:57:25.729 - warn: node-red.0 (1225) Node-RED: 21 Sep 19:57:25 - [warn] [shelly-gen2:bbafaff93d9d0b07] connect EHOSTUNREACH 192.168.178.43:80 2026-09-21 19:57:25.730 - warn: node-red.0 (1225) Node-RED: 21 Sep 19:57:25 - [warn] [shelly-gen2:d7320743653ee5c1] connect EHOSTUNREACH 192.168.178.39:80Dürfte zwar nicht der Auslöser sein, aber schon mal korrigieren.
Das Gerät ist unter der angegebenen ip nicht erreichbarDann nochmal
Nodered aufrufen und prüfen ob die Probleme wieder auftauchen.
Wenn ja nochmal das log schicken, aber evtl wirklich nur auf pihole gefiltert. Das letzte Mal war es alles.Also so wie in Post #4
-
Sorry, dass ich mich erst jetzt zurückmelde, ich war unterwegs.
Scheinbar lag es tatsächlich an Netzwerkproblemen. Meine Erklärung wäre folgende, auch wenn ich nicht sagen kann, ob sie zu 100 % stimmt:
Ein Problem mit dem Router hat vermutlich dazu geführt, dass die über Node-RED verbundenen Shelly-Geräte ungewöhnlich viel Traffic erzeugt haben. Dadurch wurde Node-RED offenbar so stark belastet, dass es zu den beobachteten Problemen kam. Ein Neustart des Routers hat leider nichts gebracht. Nachdem ich den Router jedoch ausgetauscht habe, war das Problem sofort verschwunden.
Vielen Dank nochmal für die Unterstützung und die hilfreichen Hinweise!
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
521
Online33.1k
Benutzer84.2k
Themen1.4m
Beiträge