=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2026.06.02 18:20:38 =~=~=~=~=~=~=~=~=~=~=~= login as: dieter dieter@10.0.0.20's password: Linux smarthome 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Tue Jun 2 18:03:35 2026 from 10.0.0.148 Wi-Fi is currently blocked by rfkill. Use raspi-config to set the country before use. [?2004h]0;dieter@smarthome: ~dieter@smarthome:~ $ exitPress any key to continue ************************************************************************** ]0;dieter@smarthome: ~dieter@smarthome:~ $  Some output is masked. For full results please use 'iob diag --unmask' * ]0;dieter@smarthome: ~dieter@smarthome:~ $ ************************************************************************* ]0;dieter@smarthome: ~dieter@smarthome:~ $ It helps us to help you!  Just copy and paste the Summary Page, including the ``` characters at start and end.https://forum.iobroker.net  The following checks may give hints to potential malconfigurations or errors, please post them in our forum: Please stretch the window of your terminal programm (puTTY) s wide as possible or switch to full screen *** ioBroker Diagnosis ***  iob diag --unmask > iob_diag.txt [?2004l *** iob diag is starting up, please wait *** iob diag needs to be updated. Please execute 'iobroker fix' first. npm error code ELSPROBLEMS npm error missing: homebridge-ewelink@^10.4.0, required by iobroker.ham@5.3.1 npm error A complete log of this run can be found in: /home/dieter/.npm/_logs/2026-06-02T16_21_14_899Z-debug-0.log  *** ioBroker Diagnosis *** Please stretch the window of your terminal programm (puTTY) as wide as possible or switch to full screen The following checks may give hints to potential malconfigurations or errors, please post them in our forum: https://forum.iobroker.net Just copy and paste the Summary Page, including the ``` characters at start and end. It helps us to help you! Press any key to continue  ========== Start marking the full check here =========== ```bash Script v.2026-01-31 *** BASE SYSTEM *** Operating System: Raspbian GNU/Linux 11 (bullseye) Static hostname: smarthome Icon name: computer Kernel: Linux 6.1.21-v8+ Architecture: arm64 OS is similar to: debian Model : Raspberry Pi 4 Model B Rev 1.5 Docker : false Virtualization : none Kernel : aarch64 Userland : 32 bit Outdated 32Bit architecture detected. Only a pure 64Bit-System will be supported in the future. You will have to reinstall your operating system with full 64Bit support or upgrade to more modern hardware soon. Systemuptime and Load: 18:21:23 up 507 days, 22:24, 4 users, load average: 1.71, 1.24, 1.11 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian Release codenamed 'bullseye' reached its END OF LIFE and needs to be updated to the latest stable release 'trixie' NOW! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Tue 2026-06-02 18:21:23 CEST Universal time: Tue 2026-06-02 16:21:23 UTC RTC time: n/a Time zone: Europe/Vienna (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': dieter HOME=/home/dieter GROUPS=dieter adm dialout cdrom sudo audio www-data video plugdev games users input render netdev lpadmin gpio i2c spi 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: true Display-Manager: * lightdm.service - Light Display Manager Desktop: Session: tty System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix' *** MEMORY *** total used free shared buff/cache available Mem: 3.8G 1.8G 575M 33M 1.4G 1.8G Swap: 99M 81M 18M Total: 3.9G 1.9G 594M Active iob-Instances: 21 3794 M total memory 1841 M used memory 1896 M active memory 887 M inactive memory 575 M free memory 168 M buffer memory 1208 M swap cache 99 M total swap 81 M used swap 18 M free swap *** top - Table Of Processes *** top - 18:21:23 up 507 days, 22:24, 4 users, load average: 1.71, 1.24, 1.11 Tasks: 222 total, 1 running, 221 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.4 us, 2.8 sy, 0.0 ni, 95.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3794.3 total, 575.9 free, 1842.0 used, 1376.5 buff/cache MiB Swap: 100.0 total, 18.5 free, 81.5 used. 1843.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 /dev/root ext4 29G 15G 13G 55% / devtmpfs devtmpfs 1.7G 0 1.7G 0% /dev tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 759M 1.2M 758M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 51M 205M 20% /boot tmpfs tmpfs 380M 20K 380M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Fri Jan 10 18:57:10 2025] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Fri Jan 10 18:57:10 2025] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Fri Jan 10 18:57:13 2025] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime,commit=600 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 4.2G /var/ 2.9G /var/log/journal/f3018591bcda4d7887bfb99ad9079e36 2.9G /var/log/journal 2.9G /var/log 1.1G /var/lib Archived and active journals take up 2.8G in the file system. /opt/iobroker/backups: 2.3G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 461M /opt/iobroker/iobroker-data/ 331M /opt/iobroker/iobroker-data/files 103M /opt/iobroker/iobroker-data/backup-objects 78M /opt/iobroker/iobroker-data/files/icons-open-icon-library-png 55M /opt/iobroker/iobroker-data/files/vis The five largest files in iobroker-data are: 20M /opt/iobroker/iobroker-data/objects.jsonl 9.8M /opt/iobroker/iobroker-data/files/vis-2/material-icons/knx-uf.json 8.2M /opt/iobroker/iobroker-data/files/modbus.admin/assets/index-6vd4TbNS.js 8.2M /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BDfRPp5J.js 7.2M /opt/iobroker/iobroker-data/files/ham.admin/static/js/main.8080bc0b.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' No nvbackup.json found. *** NodeJS-Installation *** /usr/bin/nodejs v22.15.0 /usr/bin/node v22.15.0 /usr/bin/npm 10.9.2 /usr/bin/npx 10.9.2 ✓ Node.js installation is correct nodejs: Installed: 22.15.0-1nodesource1 Candidate: 22.15.0-1nodesource1 Version table: *** 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 100 /var/lib/dpkg/status 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages 12.22.12~dfsg-1~deb11u7 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: ██████ █████ ███ ██ ██████ ███████ ███████ ██ ██ ██ ██ ████ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ██ ███ █████ ███████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██████ ██ ██ ██ ████ ██████ ███████ ██ ██ The current Node.js version (v22.15.0) is vulnerable to the following CVEs: CVE-2025-23166(high): The C++ method SignTraits::DeriveBits() may incorrectly call ThrowException() based on user-supplied inputs when executing in a background thread, crashing the Node.js process. Such cryptographic operations are commonly applied to untrusted inputs. Thus, this mechanism potentially allows an adversary to remotely crash a Node.js runtime. Patched versions: ^20.19.2 || ^22.15.1 || ^23.11.1 || ^24.0.2 = CVE-2025-55130(high): A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25. Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0 = CVE-2025-55131(high): A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module with the timeout option. Under specific timing conditions, buffers allocated with `Buffer.alloc` and other `TypedArray` instances like `Uint8Array` may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact. Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0 = CVE-2025-55132(low): A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via `futimes()` even when the process has only read permissions. Unlike `utimes()`, `futimes()` does not apply the expected write-permission checks, which means file metadata can be modified in read-only directories. This behavior could be used to alter timestamps in ways that obscure activity, reducing the reliability of logs. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25. Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0 = CVE-2025-59464(medium): A memory leak in Node.js’s OpenSSL integration occurs when converting `X.509` certificate fields to UTF-8 without freeing the allocated buffer. When applications call `socket.getPeerCertificate(true)`, each certificate field leaks memory, allowing remote clients to trigger steady memory growth through repeated TLS connections. Over time this can lead to resource exhaustion and denial of service. Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 = CVE-2025-59465(high): A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` error `ECONNRESET`. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example: ``` server.on('secureConnection', socket => { socket.on('error', err => { console.log(err) }) }) ``` Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0 = CVE-2025-59466(medium): We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.createHook()` is enabled. Instead of reaching `process.on('uncaughtException')`, the process terminates, making the crash unrecoverable. Applications that rely on `AsyncLocalStorage` (v22, v20) or `async_hooks.createHook()` (v24, v22, v20) become vulnerable to denial-of-service crashes triggered by deep recursion under specific conditions. Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0 = CVE-2026-21637(high): A flaw in Node.js TLS error handling leaves `SNICallback` invocations unprotected against synchronous exceptions, while the equivalent ALPN and PSK callbacks were already addressed in CVE-2026-21637. This represents an incomplete fix of that prior vulnerability. When an `SNICallback` throws synchronously on unexpected input the exception bypasses TLS error handlers and propagates as an uncaught exception, crashing the Node.js process. * This vulnerability affects all Node.js versions that received the CVE-2026-21637 fix, including **20.x, 22.x, 24.x, and 25.x**, on any TLS server where `SNICallback` may throw on unexpected `servername` input. Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2 = CVE-2026-21710(high): A flaw in Node.js HTTP request handling causes an uncaught `TypeError` when a request is received with a header named `__proto__` and the application accesses `req.headersDistinct`. When this occurs, `dest["__proto__"]` resolves to `Object.prototype` rather than `undefined`, causing `.push()` to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by `error` event listeners, meaning it cannot be handled without wrapping every `req.headersDistinct` access in a `try/catch`. * This vulnerability affects all Node.js HTTP servers on **20.x, 22.x, 24.x, and v25.x** Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2 = CVE-2026-21713(medium): A flaw in Node.js HMAC verification uses a non-constant-time comparison when validating user-provided signatures, potentially leaking timing information proportional to the number of matching bytes. Under certain threat models where high-resolution timing measurements are possible, this behavior could be exploited as a timing oracle to infer HMAC values. Node.js already provides timing-safe comparison primitives used elsewhere in the codebase, indicating this is an oversight rather than an intentional design decision. This vulnerability affects **20.x, 22.x, 24.x, and 25.x**. Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2 = CVE-2026-21714(medium): A memory leak occurs in Node.js HTTP/2 servers when a client sends WINDOW_UPDATE frames on stream 0 (connection-level) that cause the flow control window to exceed the maximum value of 2³¹-1. The server correctly sends a GOAWAY frame, but the Http2Session object is never cleaned up. This vulnerability affects HTTP2 users on Node.js 20, 22, 24 and 25. Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2 = CVE-2026-21715(low): A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync.native()` without the required read permission checks, while all comparable filesystem functions correctly enforce them. As a result, code running under `--permission` with restricted `--allow-fs-read` can still use `fs.realpathSync.native()` to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories. This vulnerability affects **20.x, 22.x, 24.x, and 25.x** processes using the Permission Model where `--allow-fs-read` is intentionally restricted. Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2 = CVE-2026-21716(low): An incomplete fix for CVE-2024-36137 leaves `FileHandle.chmod()` and `FileHandle.chown()` in the promises API without the required permission checks, while their callback-based equivalents (`fs.fchmod()`, `fs.fchown()`) were correctly patched. As a result, code running under `--permission` with restricted `--allow-fs-write` can still use promise-based `FileHandle` methods to modify file permissions and ownership on already-open file descriptors, bypassing the intended write restrictions. This vulnerability affects **20.x, 22.x, 24.x, and 25.x** processes using the Permission Model where `--allow-fs-write` is intentionally restricted. Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2 = CVE-2026-21717(medium): A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable. By crafting a request that causes many such collisions in V8's internal string table, an attacker can significantly degrade performance of the Node.js process. The most common trigger is any endpoint that calls `JSON.parse()` on attacker-controlled input, as JSON parsing automatically internalizes short strings into the affected hash table. This vulnerability affects **20.x, 22.x, 24.x, and 25.x**. Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2 = Outdated 32Bit architecture detected. Only a pure 64Bit-System will be supported in the future. You will have to reinstall your operating system with full 64Bit support or upgrade to more modern hardware soon. *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: smarthome smarthome (version: 7.0.7, hostname: smarthome , alive, uptime: 29726) Core adapters versions js-controller: 7.0.7 admin: 7.8.23 javascript: 9.0.18 nodejs modules from github: 1 +-- iobroker.icons-open-icon-library-png@0.1.3 (git+ssh://git@github.com/ioBroker/ioBroker.icons-open-icon-library-png.git#0847a79d713ee6725ccb6ccfb044c025b73ec946) Adapter State + system.adapter.admin.0 : admin : smarthome - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.admin.1 : admin : smarthome - enabled, port: 8085, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : smarthome - enabled system.adapter.alias-manager.0 : alias-manager : smarthome - disabled + system.adapter.backitup.0 : backitup : smarthome - enabled + system.adapter.cloud.0 : cloud : smarthome - enabled + system.adapter.daikin-cloud.0 : daikin-cloud : smarthome - enabled + system.adapter.discovery.0 : discovery : smarthome - enabled + system.adapter.echarts.0 : echarts : smarthome - enabled system.adapter.flot.0 : flot : smarthome - disabled + system.adapter.ham.0 : ham : smarthome - enabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : smarthome - disabled + system.adapter.javascript.0 : javascript : smarthome - enabled + system.adapter.modbus.0 : modbus : smarthome - enabled + system.adapter.mqtt.0 : mqtt : smarthome - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.pvforecast.1 : pvforecast : smarthome - enabled + system.adapter.rpi2.0 : rpi2 : smarthome - enabled + system.adapter.schedule-switcher.0 : schedule-switcher : smarthome - enabled + system.adapter.shelly.1 : shelly : smarthome - enabled, port: 1882, bind: 0.0.0.0 system.adapter.solarmanpv.0 : solarmanpv : smarthome - enabled + system.adapter.sonoff.0 : sonoff : smarthome - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.sql.0 : sql : smarthome - enabled + system.adapter.tuya.0 : tuya : smarthome - enabled system.adapter.vis-2.0 : vis-2 : smarthome - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : smarthome - disabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : smarthome - disabled system.adapter.vis-material-advanced.0 : vis-material-advanced : smarthome - disabled system.adapter.vis-materialdesign.0 : vis-materialdesign : smarthome - enabled system.adapter.vis.0 : vis : smarthome - enabled + system.adapter.web.0 : web : smarthome - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : smarthome - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.admin.1 : admin : smarthome - enabled, port: 8085, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : smarthome - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : smarthome - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : smarthome - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.web.0 : web : smarthome - 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): stable Upgrade policy: none Installed ioBroker-Adapters Used repository: stable Adapter "admin" : 7.8.23 , installed 7.8.23 Adapter "alexa2" : 3.27.4 , installed 3.27.4 Adapter "alias-manager": 2.1.0 , installed 2.1.0 Adapter "backitup" : 3.3.14 , installed 3.3.14 Adapter "cloud" : 6.0.1 , installed 6.0.1 Adapter "daikin-cloud" : 0.4.12 , installed 0.4.12 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "echarts" : 3.1.0 , installed 3.1.0 Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "icons-open-icon-library-png": 0.1.2, installed 0.1.3 Adapter "javascript" : 9.0.18 , installed 9.0.18 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "modbus" : 8.0.3 , installed 8.0.3 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "pvforecast" : 6.1.0 , installed 6.1.0 Adapter "rpi2" : 3.0.2 , installed 2.4.0 [Updatable] Adapter "schedule-switcher": 0.0.12, installed 0.0.12 Adapter "shelly" : 10.6.1 , installed 10.6.1 Adapter "simple-api" : 3.0.7 , installed 2.8.0 [Updatable] Adapter "socketio" : 7.1.3 , installed 7.1.3 Adapter "solarmanpv" : 0.7.3 , installed 0.7.3 Adapter "sonoff" : 3.3.0 , installed 3.3.0 Adapter "sql" : 3.0.1 , installed 3.0.1 Adapter "tuya" : 3.17.0 , installed 3.17.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.13.8 , installed 2.13.8 Adapter "vis-hqwidgets": 1.6.1 , installed 1.6.0 [Updatable] Adapter "vis-jqui-mfd" : 1.1.3 , installed 1.1.3 Adapter "vis-material-advanced": 1.7.4, installed 1.7.4 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "web" : 8.0.0 , installed 8.0.0 Adapter "ws" : 4.0.0 , installed 4.0.0 Objects and States Please stand by - This may take a while Objects: 4370 States: 3603 *** OS-Repositories and Updates *** E: The repository 'http://debian.org bullseye-backports Release' does not have a Release file. Pending systemupdates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 340509466 25011/sshd: /usr/sb tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 116 99987240 32663/mariadbd tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 340537364 433/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 340537359 433/iobroker.js-con tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 340537785 720/io.mqtt.0 tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 340537809 801/io.shelly.1 tcp 0 0 0.0.0.0:1884 0.0.0.0:* LISTEN 1001 340537855 829/io.sonoff.0 tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 340266060 18226/cupsd tcp6 0 0 ::1:631 :::* LISTEN 0 340266059 18226/cupsd tcp6 0 0 :::22 :::* LISTEN 0 340509468 25011/sshd: /usr/sb tcp6 0 0 :::80 :::* LISTEN 0 340509597 25126/apache2 tcp6 0 0 :::8081 :::* LISTEN 1001 340537414 451/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 340540748 1179/io.web.0 tcp6 0 0 :::8085 :::* LISTEN 1001 340536599 462/io.admin.1 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 12239 528/dhcpcd udp 0 0 0.0.0.0:57590 0.0.0.0:* 108 13158 385/avahi-daemon: r udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 340539543 603/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 340539544 603/io.tuya.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 340538773 673/io.ham.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 13156 385/avahi-daemon: r udp6 0 0 :::546 :::* 0 64942180 528/dhcpcd udp6 0 0 :::5353 :::* 108 13157 385/avahi-daemon: r udp6 0 0 :::56886 :::* 108 13159 385/avahi-daemon: r *** Log File - Last 25 Lines *** 2026-06-02 18:00:00.661 - info: host.smarthome Restart adapter system.adapter.cloud.0 because enabled 2026-06-02 18:00:05.939 - info: host.smarthome instance system.adapter.cloud.0 in version "6.0.1" started with pid 25488 2026-06-02 18:00:25.016 - info: host.smarthome instance system.adapter.solarmanpv.0 in version "0.7.3" started with pid 25522 2026-06-02 18:00:32.804 - info: host.smarthome instance system.adapter.solarmanpv.0 having pid 25522 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2026-06-02 18:02:35.545 - info: sql.0 (534) Do not store value "NULL" for modbus.0.inputRegisters.13024_Battery_Temperature because no number 2026-06-02 18:06:25.028 - info: host.smarthome instance system.adapter.solarmanpv.0 in version "0.7.3" started with pid 26540 2026-06-02 18:06:39.930 - info: host.smarthome instance system.adapter.solarmanpv.0 having pid 26540 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2026-06-02 18:12:25.026 - info: host.smarthome instance system.adapter.solarmanpv.0 in version "0.7.3" started with pid 28877 2026-06-02 18:12:30.052 - warn: solarmanpv.0 (28877) [getDeviceData] remote rpc exception ID: 216253446 2026-06-02 18:12:31.957 - info: host.smarthome instance system.adapter.solarmanpv.0 having pid 28877 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2026-06-02 18:12:35.546 - info: sql.0 (534) Do not store value "NULL" for modbus.0.inputRegisters.13024_Battery_Temperature because no number 2026-06-02 18:17:23.150 - warn: modbus.0 (808) Error: undefined 2026-06-02 18:17:23.151 - warn: modbus.0 (808) [DevID_1/inputRegs] Block 5002-5017: {} 2026-06-02 18:17:24.152 - info: modbus.0 (808) Disconnected from slave 10.0.0.128 2026-06-02 18:17:38.995 - info: mqtt.0 (720) Client [SHRDZM-98F4ABB1344A] connection closed: timeout 2026-06-02 18:17:50.509 - info: mqtt.0 (720) Client [SHRDZM-98F4ABB1344A] connected with secret 1780417070508_1097 2026-06-02 18:17:50.570 - info: mqtt.0 (720) Client [SHRDZM-98F4ABB1344A] subscribes on "mqtt.0.SHRDZM.98F4ABB1344A.set" 2026-06-02 18:17:50.718 - info: mqtt.0 (720) Client [SHRDZM-98F4ABB1344A] subscribes on "mqtt.0.SHRDZM.98F4ABB1344A.config.set" 2026-06-02 18:17:50.770 - info: mqtt.0 (720) Client [SHRDZM-98F4ABB1344A] publishOnSubscribe 2026-06-02 18:17:50.918 - info: mqtt.0 (720) Client [SHRDZM-98F4ABB1344A] publishOnSubscribe 2026-06-02 18:17:52.792 - info: shelly.1 (801) [MQTT] Device with client id "shellyplusi4-Heizung" connected from 10.0.0.131! 2026-06-02 18:17:55.502 - info: shelly.1 (801) [MQTT] Device with client id "shellyplusi4-Heizung" initialized. 2026-06-02 18:17:57.629 - info: modbus.0 (808) Connected to slave 10.0.0.128 2026-06-02 18:18:25.215 - info: host.smarthome instance system.adapter.solarmanpv.0 in version "0.7.3" started with pid 29583 2026-06-02 18:18:34.160 - info: host.smarthome instance system.adapter.solarmanpv.0 having pid 29583 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) ``` ============ Mark until here for C&P ============= iob diag has finished. [?2004h]0;dieter@smarthome: ~dieter@smarthome:~ $ exit [?2004l logout