Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie'
-
Hi,
hat hier zufällig noch jemand ein Problem mit dem "Linux-Control" Adapter nach update vom IOB Host auf Trixie?
Linux Control sagt mir alle Devices wären offline obwohl ich diese vom IOB aus erreichen kann.
EDIT: es hat sich etwas mit den User rechten zum Ausführen von "ping" geändert. Nach dieser Anpassung geht es bei mir wieder:
In Debian Trixie, the ping command, provided by the iputils-ping package, no longer executes with elevated privileges by default. Instead, it uses ICMP_PROTO datagram sockets, with access controlled by the net.ipv4.ping_group_range sysctl. This change affects how users can utilize ping, particularly for network troubleshooting. Key Changes and Implications: No more CAP_NET_RAW: The ping command no longer requires the CAP_NET_RAW capability, which is typically associated with elevated privileges. ICMP_PROTO sockets: ping now utilizes ICMP_PROTO datagram sockets for communication. Sysctl control: The net.ipv4.ping_group_range sysctl determines which user groups have permission to use ping. Potential Upgrade Issues: In some upgrade scenarios from previous Debian versions, the linux-sysctl-defaults package might not be installed, potentially affecting ping usage by unprivileged users. Checking and Adjusting the Sysctl: It's recommended to verify the net.ipv4.ping_group_range value and ensure it's set appropriately to allow the desired user group to use ping. How to verify and potentially adjust the net.ipv4.ping_group_range setting: Check the current value: Code sysctl net.ipv4.ping_group_range If the value is restrictive, adjust it: Code sudo sysctl -w net.ipv4.ping_group_range="1 1000" # Example: Allow groups 1-1000 Make the change permanent: Add the following line to /etc/sysctl.conf (or a file in /etc/sysctl.d/): Code net.ipv4.ping_group_range=1 1000 And then apply the changes with: Code sudo sysctl -p In summary, the change in ping's execution in Debian Trixie requires attention to the net.ipv4.ping_group_range sysctl to ensure proper functionality for users needing to use ping for network diagnostics, particularly in scenarios where the linux-sysctl-defaults package is not installed.EDIT2: muss man wohl tiefer einsteigen. Obwohl ich eine sysctl.conf Datei unter /etc mit dem Eintrag angelegt habe funktioniert es nach einem reboot nicht.
Erst nach ausführen von
sudo sysctl -pund anschließendem Neustart der Instanz funktioniert es wieder.
-
Guten morgen @thomas-braun vielen Dank hat sehr gut geklappt.
Herzliche Grüße
Fabio -
@trixie-tester said in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
Hallo, habe das Update nach dieser Anleitung erfolgreich durchlaufen lassen.
Trixie ist drauf und lief. Nachdem ich diese Befehle zum Aufräumen per SSH gesendet habe:apt list '~o'
sudo apt purge '~o'
sudo apt --purge autoremove
sudo apt autocleanist leider die Verbindung zu meinem Raspi 4 abgebrochen und er erhält keine LAN Verbindungs IP mehr? Wlan hatte ich zuvor mal über rfkill deaktiviert. Habt Ihr einen Tipp für mich, wie ich die LAN Verbindung wieder an bekomme.
Vielen Dank.Hallo, da ich bisher nicht weitergekommen bin und keiner hier bisher einen Tipp für mich hatte, habe ich weiter nachgeforscht und festgestellt, wenn ich den Raspi über HDMI anschliesse, das er bootet und "Firmware not found" anzeigt nach dem Trixie Update. Eine SD Karte ist nicht installiert, sondern eine SSD in einem Argon-Forty Gehäuse. Vor dem Update lief es einwandfrei und jetzt bekommt er keine LAN Verbindung mehr, somit ist auch kein SSH Zugriff möglich.
Ist das zu reparieren? -
@trixie-tester sagte in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
Eine SD Karte ist nicht installiert, sondern eine SSD in einem Argon-Forty Gehäuse.
Das hab ich auch, das ist kein Grund.
Was allerdings ein Grund sein könnte: Die Kiste wurde schon mal von Raspberry 11 auf 12 gehoben. An der Stelle wurde nämlich etwas geändert und die Firmware liegt nicht mehr dort.Installier es neu.
-
@thomas-braun sagte in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
@trixie-tester sagte in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
Eine SD Karte ist nicht installiert, sondern eine SSD in einem Argon-Forty Gehäuse.
Das hab ich auch, das ist kein Grund.
Was allerdings ein Grund sein könnte: Die Kiste wurde schon mal von Raspberry 11 auf 12 gehoben. An der Stelle wurde nämlich etwas geändert und die Firmware liegt nicht mehr dort.Installier es neu.
Okay , die Vermutung der vorherigen Anhebung der Installation von 11 auf 12 ist glaube ich richtig, hatte jetzt testweise nach dem Crash eine Neuinstallation gemacht und es lief wieder.
Habe das mit dem Backitup Adapter aus dem Backup wieder hergestellt. Probleme machen mir jedoch die Wiederherstellung meiner Influx.db und von Grafana. Die Wiederherstellung der beiden mit dem Backitup Adapter funktioniert nicht (habe das vorher noch nie gemacht), daher die Frage wegen der Reparatur des Vorsystems? -
@thomas-braun said in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
Upgrades sind nur von der direkten Vorversion und nur von der gleichen CPU-Architektur aus möglich.
Also Debian 12 'Bookworm' und z.B. arch64. CrossUpgrades von 32Bit 'armhf' auf 'arm64' sind nicht möglich (nur für echte Pinguine!) und bedingen eine Neuinstallation.Hallo, den oben stehenden Satz verstehe ich nicht ganz. Ist ein Trixie Upgrade mit einem 32bit Bookworm auf einem Rasp. Pi4 möglich?
*** BASE SYSTEM *** Operating System: Debian GNU/Linux 12 (bookworm) Static hostname: raspberrypi4-iobroker Icon name: computer Kernel: Linux 6.12.34+rpt-rpi-v7l Architecture: arm OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.2 Docker : false Virtualization : none Kernel : armv7l Userland : 32 bit -
@supernils sagte in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
Ist ein Trixie Upgrade mit einem 32bit Bookworm auf einem Rasp. Pi4 möglich?
Installier auf einem Pi4 ein 64Bit-System NEU.
Da ist nix mit 'upgraden' oder '32Bit reichen mir'. Die 32Bit-Plattform stirbt. -
Update auf Debian Trixie single Host erfolgreich, danke für die genaue Beschreibung.
-
@thomas-braun
Vielen Dank für tolle Beschreibung.
Ich habe jetzt mein System aktualisiert.
iob diag sieht so aus:========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: DebianIO Icon name: computer-container Chassis: container ☐ Virtualization: lxc Kernel: Linux 6.14.8-2-pve Architecture: x86-64 OS is similar to: model name : Intel(R) Pentium(R) Silver J5040 CPU @ 2.00GHz Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 16:40:11 up 10 min, 0 users, load average: 0.87, 0.91, 1.05 CPU threads: 2 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Fri 2025-08-15 16:40:12 CEST Universal time: Fri 2025-08-15 14:40:12 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': edi77 HOME=/home/edi77 GROUPS=edi77 sudo users iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/home/edi77 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: 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: 8.6G 2.1G 5.5G 118K 907M 6.5G Swap: 1.1G 0B 1.1G Total: 9.7G 2.1G 6.6G Active iob-Instances: 33 8192 M total memory 2035 M used memory 2089 M active memory 640 M inactive memory 5290 M free memory 0 M buffer memory 865 M swap cache 1024 M total swap 0 M used swap 1024 M free swap *** top - Table Of Processes *** top - 16:40:12 up 10 min, 0 users, load average: 0.87, 0.91, 1.05 Tasks: 58 total, 1 running, 57 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 8192.0 total, 5289.1 free, 2037.2 used, 865.6 buff/cache MiB Swap: 1024.0 total, 1024.0 free, 0.0 used. 6154.8 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System * sys-kernel-config.mount loaded failed failed Kernel Configuration File System Legend: LOAD -> Reflects whether the unit definition was properly loaded. ACTIVE -> The high-level unit activation state, i.e. generalization of SUB. SUB -> The low-level unit activation state, values depend on unit type. 2 loaded units listed. *** DMESG CRITICAL ERRORS *** dmesg: read kernel buffer failed: Operation not permitted No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--104--disk--0 ext4 40G 19G 19G 51% / none tmpfs 492K 4.0K 488K 1% /dev udev devtmpfs 7.6G 0 7.6G 0% /dev/tty tmpfs tmpfs 7.7G 0 7.7G 0% /dev/shm tmpfs tmpfs 3.1G 112K 3.1G 1% /run tmpfs tmpfs 7.7G 0 7.7G 0% /tmp tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--104--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: 950M /var/ 495M /var/log 494M /var/log/journal/07999bdde13e4bb78b0c943aad8ee95b 494M /var/log/journal 292M /var/cache Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 97.1M in the file system. /opt/iobroker/backups: 3.8G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 6.9G /opt/iobroker/iobroker-data/ 5.9G /opt/iobroker/iobroker-data/history 860M /opt/iobroker/iobroker-data/files 228M /opt/iobroker/iobroker-data/files/vis-2 129M /opt/iobroker/iobroker-data/files/vis The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 31M /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 USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp 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 v20.19.4 /usr/bin/node v20.19.4 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.32.0 nodejs: Installed: 20.19.4-1nodesource1 Candidate: 20.19.4-1nodesource1 Version table: *** 20.19.4-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 20.19.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main amd64 Packages 20.19.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main 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: DebianIO DebianIO (version: 7.0.6, hostname: DebianIO , alive, uptime: 620) Core adapters versions js-controller: 7.0.6 admin: 7.6.17 javascript: 8.9.2 nodejs modules from github: 1 +-- iobroker.zigbee@3.0.1 (git+ssh://git@github.com/ioBroker/ioBroker.zigbee.git#ae472aefab7fbb3c70b56d3c477662e265e52f03) Adapter State + system.adapter.admin.0 : admin : DebianIO - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : DebianIO - enabled + system.adapter.backitup.1 : backitup : DebianIO - enabled + system.adapter.cloud.0 : cloud : DebianIO - enabled + system.adapter.device-watcher.0 : device-watcher : DebianIO - enabled system.adapter.devices.0 : devices : DebianIO - enabled + system.adapter.deyeidc.0 : deyeidc : DebianIO - enabled, port: 8899 system.adapter.discovery.0 : discovery : DebianIO - disabled + system.adapter.echarts.0 : echarts : DebianIO - enabled + system.adapter.fritzdect.0 : fritzdect : DebianIO - enabled + system.adapter.history.0 : history : DebianIO - enabled + system.adapter.hmip.0 : hmip : DebianIO - enabled system.adapter.icons-mfd-png.0 : icons-mfd-png : DebianIO - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : DebianIO - disabled + system.adapter.iot.0 : iot : DebianIO - enabled + system.adapter.javascript.0 : javascript : DebianIO - enabled + system.adapter.mihome-vacuum.0 : mihome-vacuum : DebianIO - enabled, port: 54321 + system.adapter.mihome-vacuum.1 : mihome-vacuum : DebianIO - enabled, port: 54321 + system.adapter.onvif.0 : onvif : DebianIO - enabled, port: 8000 + system.adapter.ping.0 : ping : DebianIO - enabled + system.adapter.proxmox.0 : proxmox : DebianIO - enabled, port: 8006 + system.adapter.reolink.0 : reolink : DebianIO - enabled system.adapter.scenes.0 : scenes : DebianIO - disabled + system.adapter.shelly.0 : shelly : DebianIO - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : DebianIO - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.snmp.0 : snmp : DebianIO - enabled system.adapter.socketio.0 : socketio : DebianIO - disabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : DebianIO - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.sourceanalytix.0 : sourceanalytix : DebianIO - enabled + system.adapter.tankerkoenig.0 : tankerkoenig : DebianIO - enabled + system.adapter.telegram.0 : telegram : DebianIO - enabled, port: 8443, bind: 0.0.0.0 system.adapter.text2command.0 : text2command : DebianIO - disabled + system.adapter.tr-064.0 : tr-064 : DebianIO - enabled + system.adapter.tuya.0 : tuya : DebianIO - enabled system.adapter.vis-2-widgets-collection.0: vis-2-widgets-collection: DebianIO - enabled system.adapter.vis-2-widgets-energy.0 : vis-2-widgets-energy : DebianIO - enabled system.adapter.vis-2-widgets-gauges.0 : vis-2-widgets-gauges : DebianIO - enabled system.adapter.vis-2-widgets-inventwo.0 : vis-2-widgets-inventwo: DebianIO - enabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: DebianIO - enabled + system.adapter.vis-2.0 : vis-2 : DebianIO - enabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : DebianIO - disabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : DebianIO - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : DebianIO - disabled + system.adapter.vis-inventwo.0 : vis-inventwo : DebianIO - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : DebianIO - disabled system.adapter.vis-material-advanced.0 : vis-material-advanced : DebianIO - disabled system.adapter.vis-metro.0 : vis-metro : DebianIO - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : DebianIO - disabled system.adapter.vis.0 : vis : DebianIO - enabled + system.adapter.web.0 : web : DebianIO - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.web.1 : web : DebianIO - enabled, port: 8083, bind: 0.0.0.0, run as: admin + system.adapter.ws.0 : ws : DebianIO - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : DebianIO - enabled, port: tcp://192.168.178.12:6638 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : DebianIO - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.deyeidc.0 : deyeidc : DebianIO - enabled, port: 8899 + system.adapter.mihome-vacuum.0 : mihome-vacuum : DebianIO - enabled, port: 54321 + system.adapter.mihome-vacuum.1 : mihome-vacuum : DebianIO - enabled, port: 54321 + system.adapter.onvif.0 : onvif : DebianIO - enabled, port: 8000 + system.adapter.proxmox.0 : proxmox : DebianIO - enabled, port: 8006 + system.adapter.shelly.0 : shelly : DebianIO - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : DebianIO - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : DebianIO - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : DebianIO - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : DebianIO - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.web.1 : web : DebianIO - enabled, port: 8083, bind: 0.0.0.0, run as: admin + system.adapter.ws.0 : ws : DebianIO - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : DebianIO - enabled, port: tcp://192.168.178.12:6638 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.6.17 , installed 7.6.17 Adapter "alias-manager": 2.0.0 , installed 2.0.0 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "device-watcher": 2.12.1 , installed 2.12.1 Adapter "devices" : 1.1.5 , installed 1.1.5 Adapter "deyeidc" : 0.2.0 , installed 0.2.0 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "echarts" : 1.9.2 , installed 1.9.2 Adapter "fritzdect" : 2.6.2 , installed 2.6.2 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hmip" : 1.27.0 , installed 1.27.0 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "iot" : 3.3.0 , installed 3.3.0 Adapter "javascript" : 8.9.2 , installed 8.9.2 Controller "js-controller": 7.0.6 , installed 7.0.6 Adapter "mihome-vacuum": 5.2.0 , installed 5.2.0 Adapter "onvif" : 1.1.4 , installed 1.1.4 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "proxmox" : 2.4.0 , installed 2.4.0 Adapter "reolink" : 1.2.3 , installed 1.2.3 Adapter "scenes" : 3.2.3 , installed 3.2.3 Adapter "shelly" : 10.1.0 , installed 10.1.0 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "snmp" : 3.2.0 , installed 3.2.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.1.2 , installed 3.1.2 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "tuya" : 3.16.0 , installed 3.16.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.9.64 , installed 2.9.64 Adapter "vis-2-widgets-collection": 1.8.1, installed 1.8.1 Adapter "vis-2-widgets-energy": 1.0.2, installed 1.0.2 Adapter "vis-2-widgets-gauges": 1.1.0, installed 1.1.0 Adapter "vis-2-widgets-inventwo": 0.2.2, installed 0.2.2 Adapter "vis-2-widgets-material": 1.4.10, installed 1.4.10 Adapter "vis-canvas-gauges": 1.0.1, installed 1.0.1 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 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-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "zigbee" : 2.0.5 , installed 3.0.1 Objects and States Please stand by - This may take a while Objects: 10632 States: 9133 *** OS-Repositories and Updates *** W: https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... W: https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details 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 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 3843699 174/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 3844511 174/iobroker.js-con tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 3844328 323/master tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 3838891 1/init tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 3845540 565/io.sonoff.0 tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 3845693 610/io.shelly.0 tcp6 0 0 :::22 :::* LISTEN 0 3840845 1/init tcp6 0 0 :::111 :::* LISTEN 0 3838893 1/init tcp6 0 0 :::8095 :::* LISTEN 1001 3854689 898/io.onvif.0 tcp6 0 0 :::8087 :::* LISTEN 1001 3848811 736/io.simple-api.0 tcp6 0 0 :::8084 :::* LISTEN 1001 3849058 787/io.ws.0 tcp6 0 0 :::8083 :::* LISTEN 1001 3849216 832/io.web.1 tcp6 0 0 :::8082 :::* LISTEN 1001 3845929 691/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 3844625 336/io.admin.0 tcp6 0 0 ::1:25 :::* LISTEN 0 3844329 323/master udp 0 0 0.0.0.0:53421 0.0.0.0:* 1001 3848400 625/io.mihome-vacuu udp 0 0 0.0.0.0:37750 0.0.0.0:* 1001 3845073 550/io.snmp.0 udp 0 0 192.168.178.5:5353 0.0.0.0:* 1001 3845643 595/io.tr-064.0 udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 3845595 580/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 3845596 580/io.tuya.0 udp 0 0 0.0.0.0:7885 0.0.0.0:* 1001 3845381 520/io.mihome-vacuu udp 0 0 0.0.0.0:111 0.0.0.0:* 0 3838892 1/init udp6 0 0 :::111 :::* 0 3838894 1/init *** Log File - Last 25 Lines *** <soap:Envelope > <soap:Header> <wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action> <wsa:MessageID>urn:uuid:e1da5585-4fa1-4a38-91e6-f77b38e0d9bd</wsa:MessageID> <wsa:RelatesTo>urn:uuid:ef96d4fd-5ccf-0624-fd92-b1d24ad84bb4</wsa:RelatesTo> <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To> <wsd:AppSequence InstanceId="2614047292" MessageNumber="1"/> </soap:Header> <soap:Body> <wsd:ProbeMatches/> </soap:Body> </soap:Envelope> 2025-08-15 16:32:11.175 - error: onvif.0 (898) undefined 2025-08-15 16:32:15.851 - error: onvif.0 (898) Error during discovery: TypeError: Cannot read properties of undefined (reading 'endpointReference'),TypeError: Cannot read properties of undefined (reading 'endpointReference') 2025-08-15 16:32:15.851 - info: onvif.0 (898) Finished onvif discovery 2025-08-15 16:32:15.852 - info: onvif.0 (898) Starting snapshot server 2025-08-15 16:32:32.676 - info: tuya.0 (580) bf8736ec46b647a352ueah: Error on Reconnect (7): connect EHOSTUNREACH 192.168.178.174:6668 2025-08-15 16:32:34.721 - info: sonoff.0 (565) Client [Stromzaehler] connected with secret 1755268354720_9744 2025-08-15 16:32:34.881 - info: sonoff.0 (565) Client [Nous-3] connected with secret 1755268354880_1452 2025-08-15 16:32:35.239 - info: sonoff.0 (565) Client [Nous-2] connected with secret 1755268355239_5967 2025-08-15 16:32:35.374 - info: sonoff.0 (565) Client [Nous-1_Gefrierschrank] connected with secret 1755268355373_6833 2025-08-15 16:32:59.748 - info: tuya.0 (580) bf4401a6fe27d67a7e1uuq: Error on Reconnect (7): connect EHOSTUNREACH 192.168.178.163:6668 2025-08-15 16:33:01.924 - info: tuya.0 (580) bfb7a39438c5cbac04novg: Error on Reconnect (7): connect EHOSTUNREACH 192.168.178.161:6668 2025-08-15 16:33:03.012 - info: tuya.0 (580) bf302f3b8d8e768522cdj2: Error on Reconnect (7): connect EHOSTUNREACH 192.168.178.167:6668 ============ Mark until here for C&P ============= iob diag has finished.Da wird ein Fehler angezeigt und ich habe keine Ahnung was ich da machen soll.
*** DMESG CRITICAL ERRORS *** dmesg: read kernel buffer failed: Operation not permitted No critical errors detecteddanke nochmal für die Hilfe
-
@eduard77 sagte in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
Da wird ein Fehler angezeigt und ich habe keine Ahnung was ich da machen soll.
Da darf der user nicht die Kernelringpuffer-Meldungen des Hosts sehen. Ist bei LXCs erstmal halt so.
-
@thomas-braun
Okay alles klar. Danke. -
Die anderen Dinge (adm-Gruppe, graphical target, nodejs usw) kannst du aber angehen.
-
@thomas-braun
das Nodejs update möchte ich noch wegen Echarts Adapter nicht machen.Bei Graphical Target habe ich aus deinem Werkzeugkasten folgendes ausgeführt.
edi77@DebianIO:~$ systemctl get-default multi-user.target edi77@DebianIO:~$ sudo systemctl set-default multi-user.target edi77@DebianIO:~$iob diag liefert jetzt das hier:
*** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: ttyWas soll ich machen?
-
@eduard77 sagte in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
Was soll ich machen?
Nix! Ist doch alles tacko.
-
@codierknecht
Ich habe jetzt festgestellt dass Ping Adapter bei mir nicht mehr funktioniert.
Deinstallation und neu Installation hat nichts gebracht.
Hat jemand das auch?
Mein Debug Log.ping.0 2025-08-15 20:44:34.149 debug Ping result for 192.168.178.15: false in -ms (Tried 0/1 times) ping.0 2025-08-15 20:44:34.147 debug STDERR: /bin/ping: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:34.144 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.15 ping.0 2025-08-15 20:44:34.144 debug Pinging offline 192.168.178.15 ping.0 2025-08-15 20:44:34.093 debug Ping result for 192.168.178.14: false in -ms (Tried 1/1 times) ping.0 2025-08-15 20:44:34.092 debug STDERR: /bin/ping: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:34.088 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.14 ping.0 2025-08-15 20:44:34.087 debug Ping result for 192.168.178.14: false in -ms (Tried 0/1 times) ping.0 2025-08-15 20:44:34.086 debug STDERR: /bin/ping: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:34.081 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.14 ping.0 2025-08-15 20:44:34.081 debug Pinging offline 192.168.178.14 ping.0 2025-08-15 20:44:34.028 debug Ping result for 192.168.178.24: false in -ms (Tried 1/1 times) ping.0 2025-08-15 20:44:34.027 debug STDERR: /bin/ping: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:34.024 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.24 ping.0 2025-08-15 20:44:34.023 debug Ping result for 192.168.178.24: false in -ms (Tried 0/1 times) ping.0 2025-08-15 20:44:34.021 debug STDERR: /bin/ping: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:34.018 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.24 ping.0 2025-08-15 20:44:34.017 debug Pinging offline 192.168.178.24 ping.0 2025-08-15 20:44:03.965 debug Ping result for 192.168.178.15: false in -ms (Tried 1/1 times) ping.0 2025-08-15 20:44:03.964 debug STDERR: /bin/ping: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:03.961 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.15 ping.0 2025-08-15 20:44:03.960 debug Ping result for 192.168.178.15: false in -ms (Tried 0/1 times) ping.0 2025-08-15 20:44:03.959 debug STDERR: /bin/ping: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:03.955 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.15 ping.0 2025-08-15 20:44:03.954 debug Pinging offline 192.168.178.15 ping.0 2025-08-15 20:44:03.903 debug Ping result for 192.168.178.14: false in -ms (Tried 1/1 times) ping.0 2025-08-15 20:44:03.902 debug STDERR: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:03.901 debug STDERR: /bin/ping: ping.0 2025-08-15 20:44:03.896 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.14 ping.0 2025-08-15 20:44:03.895 debug Ping result for 192.168.178.14: false in -ms (Tried 0/1 times) ping.0 2025-08-15 20:44:03.894 debug STDERR: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:03.893 debug STDERR: /bin/ping: ping.0 2025-08-15 20:44:03.888 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.14 ping.0 2025-08-15 20:44:03.887 debug Pinging offline 192.168.178.14 ping.0 2025-08-15 20:44:03.830 debug Ping result for 192.168.178.24: false in -ms (Tried 1/1 times) ping.0 2025-08-15 20:44:03.829 debug STDERR: /bin/ping: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:03.822 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.24 ping.0 2025-08-15 20:44:03.822 debug Ping result for 192.168.178.24: false in -ms (Tried 0/1 times) ping.0 2025-08-15 20:44:03.820 debug STDERR: socktype: SOCK_RAW/bin/ping: socket: Operation not permitted/bin/ping: => missing cap_net_raw+p capability or setuid? ping.0 2025-08-15 20:44:03.819 debug STDERR: /bin/ping: ping.0 2025-08-15 20:44:03.813 debug System command: /bin/ping -n -w 2 -c 1 192.168.178.24 ping.0 2025-08-15 20:44:03.812 debug Pinging offline 192.168.178.24 ping.0 2025-08-15 20:44:03.811 debug Start tasks of objects update ping.0 2025-08-15 20:44:03.809 debug Prepare tasks of objects update ping.0 2025-08-15 20:44:03.687 debug Get existing objects ping.0 2025-08-15 20:44:03.686 debug Host=DebianIO ping.0 2025-08-15 20:44:03.685 debug Prepare objects ping.0 2025-08-15 20:44:03.669 info starting. Version 1.6.2 in /opt/iobroker/node_modules/iobroker.ping, node: v20.19.4, js-controller: 7.0.6 ping.0 2025-08-15 20:44:03.220 debug Plugin sentry Initialize Plugin (enabled=true) ping.0 2025-08-15 20:44:03.161 debug States connected to redis: 127.0.0.1:9000 ping.0 2025-08-15 20:44:03.099 debug States create User PubSub Client ping.0 2025-08-15 20:44:03.098 debug States create System PubSub ClientKann es was mit admin rechten liegen?
-
An der Stelle wurde etwas umgestellt, die Rechte an ping werden mit Debian 13 anders vergeben.
Steht aber in der Readme drin. Hab ich glaube ich oben verlinkt.Edith: Kann auch sein, dass da beim Adapter etwas angepasst werden muss. Mach am besten ein Issue dort auf.
-
@thomas-braun
Hab ich gemacht, aber ich bin mir nicht sicher ob alles richtig gemacht. Ist meine erste Issue gewesen. -
@eduard77 also ich hab die tage auch auf Trixie umgestellt und ebenfalls das Nodejs update gemacht und der Ping Adapter funktioniert
========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: Raspberrypi5 Icon name: computer Kernel: Linux 6.12.34+rpt-rpi-2712 Architecture: arm64 OS is similar to: Model : Raspberry Pi 5 Model B Rev 1.0 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 21:52:35 up 3 days, 7:32, 1 user, load average: 0.32, 0.47, 0.44 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: Fri 2025-08-15 21:52:35 CEST Universal time: Fri 2025-08-15 19:52:35 UTC RTC time: Fri 2025-08-15 19:52:35 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': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/home/pi GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty *** MEMORY *** total used free shared buff/cache available Mem: 8.5G 4.7G 1.5G 25M 2.4G 3.7G Swap: 209M 201M 7.8M Total: 8.7G 4.9G 1.5G Active iob-Instances: 33 8063 M total memory 4515 M used memory 4012 M active memory 2075 M inactive memory 1397 M free memory 124 M buffer memory 2136 M swap cache 199 M total swap 192 M used swap 7 M free swap *** top - Table Of Processes *** top - 21:52:35 up 3 days, 7:32, 1 user, load average: 0.38, 0.48, 0.45 Tasks: 242 total, 1 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 50.0 us, 4.3 sy, 0.0 ni, 45.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 8063.1 total, 1406.3 free, 4506.7 used, 2261.5 buff/cache MiB Swap: 200.0 total, 7.5 free, 192.5 used. 3556.4 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 24M 1.6G 2% /run /dev/sda2 ext4 59G 20G 36G 37% / tmpfs tmpfs 4.0G 0 4.0G 0% /dev/shm tmpfs tmpfs 5.0M 48K 5.0M 1% /run/lock tmpfs tmpfs 4.0G 11M 4.0G 1% /tmp tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service /dev/sda1 vfat 510M 73M 438M 15% /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 ext4 filesystem in dmesg: [Tue Aug 12 14:20:16 2025] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 numa=fake=8 system_heap.max_order=0 smsc95xx.macaddr=D8:3A:DD:A3:25:8A vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=beeda195-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE [Tue Aug 12 14:20:21 2025] EXT4-fs (sda2): mounted filesystem 6835594d-a5f3-459f-a244-318060e7e0ab ro with ordered data mode. Quota mode: none. [Tue Aug 12 14:20:22 2025] EXT4-fs (sda2): re-mounted 6835594d-a5f3-459f-a244-318060e7e0ab r/w. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime `-/boot/firmware /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 3.1G /var/ 1.4G /var/lib 1.3G /var/log/journal/02a43974e4004c17afbe02a71ed8236e 1.3G /var/log/journal 1.3G /var/log Archived and active journals take up 1.2G in the file system. /opt/iobroker/backups: 1.9G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 529M /opt/iobroker/iobroker-data/ 160M /opt/iobroker/iobroker-data/files 122M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/node-red 71M /opt/iobroker/iobroker-data/node-red/node_modules The five largest files in iobroker-data are: 42M /opt/iobroker/iobroker-data/objects.jsonl 26M /opt/iobroker/iobroker-data/states.jsonl 8.8M /opt/iobroker/iobroker-data/files/matter.admin/assets/index-CjzUbllv.js 8.6M /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BBu8-Y_o.js 6.2M /opt/iobroker/iobroker-data/jarvis/0/jarvis.0.devices.json USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** 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' *** NodeJS-Installation *** /usr/bin/nodejs v22.18.0 /usr/bin/node v22.18.0 /usr/bin/npm 10.9.3 /usr/bin/npx 10.9.3 /usr/bin/corepack 0.33.0 nodejs: Installed: 22.18.0-1nodesource1 Candidate: 22.18.0-1nodesource1 Version table: *** 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 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 500 500 http://deb.debian.org/debian trixie/main arm64 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: Raspberrypi5 Raspberrypi5 (version: 7.0.7, hostname: Raspberrypi5 , alive, uptime: 286333) Core adapters versions js-controller: 7.0.7 admin: 7.7.2 javascript: 9.0.11 nodejs modules from github: 4 +-- iobroker.influxdb@4.0.3 (git+ssh://git@github.com/ioBroker/ioBroker.influxdb.git#234de8d73a8e1b48aabce21d9133eb8a13af2956) +-- iobroker.jarvis@3.2.0-rc.17 (git+ssh://git@github.com/Zefau/ioBroker.jarvis.git#65370bd2ad4617722447bcff04ba4dc6429bed9b) +-- iobroker.nspanel-lovelace-ui@0.2.4 (git+ssh://git@github.com/ticaki/ioBroker.nspanel-lovelace-ui.git#0a997895460f24da9797ea6d3a74bfdeba28f75a) +-- iobroker.syrconnectapp@1.0.3 (git+ssh://git@github.com/TA2k/ioBroker.syrconnectapp.git#188d6182f6a83ba14edf51d368e01b44b94dc0c2) Adapter State system.adapter.accuweather.0 : accuweather : Raspberrypi5 - disabled + system.adapter.admin.0 : admin : Raspberrypi5 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : Raspberrypi5 - enabled system.adapter.alias-manager.0 : alias-manager : Raspberrypi5 - enabled + system.adapter.alpha-ess.0 : alpha-ess : Raspberrypi5 - enabled + system.adapter.backitup.0 : backitup : Raspberrypi5 - enabled + system.adapter.cloud.0 : cloud : Raspberrypi5 - enabled system.adapter.devices.0 : devices : Raspberrypi5 - enabled + system.adapter.discovery.0 : discovery : Raspberrypi5 - enabled + system.adapter.energiefluss-erweitert.0 : energiefluss-erweitert: Raspberrypi5 - enabled system.adapter.energiefluss-erweitert.1 : energiefluss-erweitert: Raspberrypi5 - disabled + system.adapter.energiefluss-erweitert.2 : energiefluss-erweitert: Raspberrypi5 - enabled system.adapter.energiefluss-erweitert.3 : energiefluss-erweitert: Raspberrypi5 - disabled + system.adapter.fritzdect.0 : fritzdect : Raspberrypi5 - enabled + system.adapter.hm-rega.0 : hm-rega : Raspberrypi5 - enabled + system.adapter.hm-rpc.0 : hm-rpc : Raspberrypi5 - enabled, port: 18701 + system.adapter.hm-rpc.1 : hm-rpc : Raspberrypi5 - enabled, port: 18701 system.adapter.hm-rpc.2 : hm-rpc : Raspberrypi5 - disabled, port: 12001 + system.adapter.homeconnect.0 : homeconnect : Raspberrypi5 - enabled + system.adapter.hue.0 : hue : Raspberrypi5 - enabled, port: 80 system.adapter.ical.0 : ical : Raspberrypi5 - enabled system.adapter.ical.1 : ical : Raspberrypi5 - enabled + system.adapter.influxdb.0 : influxdb : Raspberrypi5 - enabled, port: 8086 + system.adapter.iot.0 : iot : Raspberrypi5 - enabled + system.adapter.jarvis.0 : jarvis : Raspberrypi5 - enabled + system.adapter.javascript.0 : javascript : Raspberrypi5 - enabled + system.adapter.matter.0 : matter : Raspberrypi5 - enabled + system.adapter.modbus.0 : modbus : Raspberrypi5 - enabled + system.adapter.mqtt.0 : mqtt : Raspberrypi5 - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.net-tools.0 : net-tools : Raspberrypi5 - enabled + system.adapter.nspanel-lovelace-ui.0 : nspanel-lovelace-ui : Raspberrypi5 - enabled + system.adapter.nuki.0 : nuki : Raspberrypi5 - enabled system.adapter.openweathermap.0 : openweathermap : Raspberrypi5 - enabled + system.adapter.ping.0 : ping : Raspberrypi5 - enabled + system.adapter.rpi2.0 : rpi2 : Raspberrypi5 - enabled + system.adapter.simple-api.0 : simple-api : Raspberrypi5 - enabled, port: 8087, bind: 192.168.178.82, run as: admin + system.adapter.socketio.0 : socketio : Raspberrypi5 - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : Raspberrypi5 - enabled, port: 1886, bind: 0.0.0.0 system.adapter.syrconnectapp.0 : syrconnectapp : Raspberrypi5 - disabled + system.adapter.telegram.0 : telegram : Raspberrypi5 - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tr-064.0 : tr-064 : Raspberrypi5 - enabled + system.adapter.web.0 : web : Raspberrypi5 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : Raspberrypi5 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : Raspberrypi5 - enabled, port: 18701 + system.adapter.hm-rpc.1 : hm-rpc : Raspberrypi5 - enabled, port: 18701 + system.adapter.hue.0 : hue : Raspberrypi5 - enabled, port: 80 + system.adapter.influxdb.0 : influxdb : Raspberrypi5 - enabled, port: 8086 + system.adapter.mqtt.0 : mqtt : Raspberrypi5 - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : Raspberrypi5 - enabled, port: 8087, bind: 192.168.178.82, run as: admin + system.adapter.socketio.0 : socketio : Raspberrypi5 - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : Raspberrypi5 - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : Raspberrypi5 - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : Raspberrypi5 - enabled, port: 8082, bind: 0.0.0.0, run as: admin 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): beta Upgrade policy: none Installed ioBroker-Adapters Used repository: beta Adapter "accuweather" : 2.1.0 , installed 2.1.0 Adapter "admin" : 7.7.2 , installed 7.7.2 Adapter "alexa2" : 3.27.3 , installed 3.27.3 Adapter "alias-manager": 2.0.0 , installed 2.0.0 Adapter "alpha-ess" : 3.0.1 , installed 3.0.1 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "devices" : 1.2.8 , installed 1.2.8 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "energiefluss-erweitert": 0.7.8, installed 0.7.8 Adapter "fritzdect" : 2.6.2 , installed 2.6.2 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "homeconnect" : 1.4.3 , installed 1.4.3 Adapter "hue" : 3.16.2 , installed 3.16.2 Adapter "ical" : 1.16.2 , installed 1.16.2 Adapter "influxdb" : 4.0.2 , installed 4.0.3 Adapter "iot" : 3.6.0 , installed 3.6.0 Adapter "jarvis" : 3.2.0-rc.5, installed 3.2.0-rc.17 Adapter "javascript" : 9.0.11 , installed 9.0.11 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "matter" : 0.5.2 , installed 0.5.2 Adapter "modbus" : 6.4.0 , installed 6.4.0 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "net-tools" : 1.2.0 , installed 1.2.0 Adapter "nuki" : 2.0.0 , installed 2.0.0 Adapter "openweathermap": 1.4.0 , installed 1.4.0 Adapter "ping" : 1.7.9 , installed 1.7.9 Adapter "rpi2" : 2.4.0 , installed 2.4.0 Adapter "simple-api" : 3.0.7 , installed 3.0.7 Adapter "socketio" : 7.0.8 , installed 7.0.8 Adapter "sonoff" : 3.2.1 , installed 3.2.1 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "web" : 7.0.9 , installed 7.0.9 Adapter "ws" : 3.0.19 , installed 3.0.19 Objects and States Please stand by - This may take a while Objects: 14957 States: 14940 *** OS-Repositories and Updates *** W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://archive.raspberrypi.com/debian trixie InRelease Hit:3 http://deb.debian.org/debian-security trixie-security InRelease Hit:4 https://apt.grafana.com stable InRelease Hit:5 http://deb.debian.org/debian trixie-updates InRelease Hit:6 https://repos.influxdata.com/debian stable InRelease Hit:7 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details 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 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 9586 1197/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 9591 1197/iobroker.js-co tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 9496 1161/exim4 tcp 0 0 192.168.178.82:18701 0.0.0.0:* LISTEN 1001 9140 1474/io.hm-rpc.0 tcp 0 0 192.168.178.82:18702 0.0.0.0:* LISTEN 1001 12692 1766/io.hm-rpc.1 tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1001 11866 1705/io.sonoff.0 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 106 5821 882/mosquitto tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 8475 847/sshd: /usr/sbin tcp 0 0 192.168.178.82:8087 0.0.0.0:* LISTEN 1001 14378 1939/io.simple-api. tcp6 0 0 :::8086 :::* LISTEN 999 7926 878/influxd tcp6 0 0 :::8084 :::* LISTEN 1001 11068 1958/io.socketio.0 tcp6 0 0 :::8082 :::* LISTEN 1001 13092 1994/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 7992 1242/io.admin.0 tcp6 0 0 :::3000 :::* LISTEN 107 3469336 236768/grafana tcp6 0 0 ::1:25 :::* LISTEN 0 9497 1161/exim4 tcp6 0 0 :::1883 :::* LISTEN 106 5822 882/mosquitto tcp6 0 0 :::22 :::* LISTEN 0 8477 847/sshd: /usr/sbin tcp6 0 0 :::8400 :::* LISTEN 1001 12278 1917/io.jarvis.0 udp 0 0 0.0.0.0:41857 0.0.0.0:* 104 7557 662/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 7633901 2095/io.matter.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 7633885 2095/io.matter.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 13930 2095/io.matter.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 13922 2095/io.matter.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 7555 662/avahi-daemon: r udp 0 0 0.0.0.0:5541 0.0.0.0:* 1001 13939 2095/io.matter.0 udp 0 0 0.0.0.0:51454 0.0.0.0:* 1001 15376 2095/io.matter.0 udp6 0 0 fe80::f05b:9255:16f:546 :::* 0 7907 743/NetworkManager udp6 0 0 fe80::38be:beb2:fe6:546 :::* 0 6783 743/NetworkManager udp6 0 0 :::5353 :::* 1001 7633902 2095/io.matter.0 udp6 0 0 :::5353 :::* 1001 7633886 2095/io.matter.0 udp6 0 0 :::5353 :::* 1001 13933 2095/io.matter.0 udp6 0 0 :::5353 :::* 1001 13925 2095/io.matter.0 udp6 0 0 :::5353 :::* 104 7556 662/avahi-daemon: r udp6 0 0 :::5541 :::* 1001 13938 2095/io.matter.0 udp6 0 0 :::46829 :::* 104 7558 662/avahi-daemon: r udp6 0 0 :::51454 :::* 1001 15375 2095/io.matter.0 *** Log File - Last 25 Lines *** 2025-08-15 21:52:55.037 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-ssh1106-21.cmnd.DisplayText[Displays/Tasmota-ssh1106-21/cmnd/DisplayText] 2025-08-15 21:52:57.005 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_9BE738.cmnd.CustomSend[SmartHome/NSPanel_9BE738/cmnd/CustomSend] 2025-08-15 21:52:57.047 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_9BE738.cmnd.CustomSend[SmartHome/NSPanel_9BE738/cmnd/CustomSend] 2025-08-15 21:52:57.048 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_9BE738.cmnd.CustomSend[SmartHome/NSPanel_9BE738/cmnd/CustomSend] 2025-08-15 21:53:00.010 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_C60BC4.cmnd.CustomSend[SmartHome/NSPanel_C60BC4/cmnd/CustomSend] 2025-08-15 21:53:00.011 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_C60BC4.cmnd.CustomSend[SmartHome/NSPanel_C60BC4/cmnd/CustomSend] 2025-08-15 21:53:00.014 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_C60BC4.cmnd.CustomSend[SmartHome/NSPanel_C60BC4/cmnd/CustomSend] 2025-08-15 21:53:00.018 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_C60BC4.cmnd.CustomSend[SmartHome/NSPanel_C60BC4/cmnd/CustomSend] 2025-08-15 21:53:00.018 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_9BE738.cmnd.CustomSend[SmartHome/NSPanel_9BE738/cmnd/CustomSend] 2025-08-15 21:53:00.019 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_9BE738.cmnd.CustomSend[SmartHome/NSPanel_9BE738/cmnd/CustomSend] 2025-08-15 21:53:00.020 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_9BE738.cmnd.CustomSend[SmartHome/NSPanel_9BE738/cmnd/CustomSend] 2025-08-15 21:53:00.022 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_9BE738.cmnd.CustomSend[SmartHome/NSPanel_9BE738/cmnd/CustomSend] 2025-08-15 21:53:00.037 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-ssh1106-21.cmnd.DisplayText[Displays/Tasmota-ssh1106-21/cmnd/DisplayText] 2025-08-15 21:53:00.040 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-ssd1309-176.cmnd.DisplayText[Displays/Tasmota-ssd1309-176/cmnd/DisplayText] 2025-08-15 21:53:00.049 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-4x20-59.cmnd.DisplayText[Displays/Tasmota-4x20-59/cmnd/DisplayText] 2025-08-15 21:53:00.052 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-ssd1309-186.cmnd.DisplayText[Displays/Tasmota-ssd1309-186/cmnd/DisplayText] 2025-08-15 21:53:00.103 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_C60BC4.cmnd.CustomSend[SmartHome/NSPanel_C60BC4/cmnd/CustomSend] 2025-08-15 21:53:00.105 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_C60BC4.cmnd.CustomSend[SmartHome/NSPanel_C60BC4/cmnd/CustomSend] 2025-08-15 21:53:00.107 - info: mqtt.0 (73128) send2Server mqtt.0.SmartHome.NSPanel_C60BC4.cmnd.CustomSend[SmartHome/NSPanel_C60BC4/cmnd/CustomSend] 2025-08-15 21:53:05.005 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-ssd1309-176.cmnd.DisplayText[Displays/Tasmota-ssd1309-176/cmnd/DisplayText] 2025-08-15 21:53:05.010 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-ssh1106-21.cmnd.DisplayText[Displays/Tasmota-ssh1106-21/cmnd/DisplayText] 2025-08-15 21:53:10.013 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-ssh1106-21.cmnd.DisplayText[Displays/Tasmota-ssh1106-21/cmnd/DisplayText] 2025-08-15 21:53:10.016 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-ssd1309-176.cmnd.DisplayText[Displays/Tasmota-ssd1309-176/cmnd/DisplayText] 2025-08-15 21:53:10.058 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-ssd1309-186.cmnd.DisplayText[Displays/Tasmota-ssd1309-186/cmnd/DisplayText] 2025-08-15 21:53:10.062 - info: mqtt.0 (73128) send2Server mqtt.0.Displays.Tasmota-4x20-59.cmnd.DisplayText[Displays/Tasmota-4x20-59/cmnd/DisplayText] ============ Mark until here for C&P ============= iob diag has finished. -
@teletapi sagte: auf Trixie umgestellt und ebenfalls das Nodejs update gemacht und der Ping Adapter funktioniert
Bei mir auch.
-
