- ioBroker Community Home
- Deutsch
- ioBroker Allgemein
- Switchbot Hub Adapter
Switchbot Hub Adapter
Geplant
Angeheftet
Gesperrt
Verschoben
ioBroker Allgemein
13
Beiträge
3
Kommentatoren
280
Aufrufe
6
Beobachtet
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
-
Danke für den Hinweis.
Ich hab den Fehler jetzt gefunden...ein Klassiker, der nicht leicht ersichtlich war.
Habe beim Kopieren des Tokens ein Leerzeichen am Ende mit kopiert
Jetzt funktioniert es.Nodejs auf Stand gebracht?
Wie schaut der Rest des Systems aus? -
Nein hab ich noch nicht gemacht.
Werde ich demnächst mal erledigen...eilt ja nicht.
Was meinst du mit Rest?
NPM: 10.8.2
Admin: 7.8.23eilt ja nicht
Doch, das eilt. Denn dein nodejs?20 ist ABGEKÜNDIGT!
Also JETZT updaten. JETZT wie sofort und unverzüglich!
Mit Rest ist z.B. dein Betriebssystem und die ioBroker-Adaptee gemeint. Was sagt denn ein
iob diagauf der Kiste?
-
Hallo zusammen, ich möchte einen Switchbot Bot in den iobroker integrieren.
Hierfür habe ich den Switchbot Hub Adapter installiert und den Token von der App mit Secret Key eingegeben.
Leider wird der Adapter nicht grün.
Folgendes erscheint im Log:switchbot-hub.0 2026-05-19 21:41:30.208 info starting. Version 0.1.2 (non-npm: arteck/ioBroker.switchbot-hub#375dc3d6d53d8322071e7d172137fef1f5849370) in /opt/iobroker/node_modules/iobroker.switchbot-hub, node: v20.19.1, js-controller: 7.0.7 switchbot-hub.0 2026-05-19 21:41:19.342 info terminating switchbot-hub.0 2026-05-19 21:41:18.839 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason switchbot-hub.0 2026-05-19 21:41:18.837 info terminating switchbot-hub.0 2026-05-19 21:41:18.829 info Got terminate signal TERMINATE_YOURSELFVielleicht kann jemand helfen, oder wie habt ihr das mit Switchbot gemacht?
arteck/ioBroker.switchbot-hub
Du hast offensichtlich irgendeinen fork direkt von Github installiert. Wende dich bei Fragen zu LABOR installationn bitte direkt an den Entwickler mit dem du den Test durchführst. Der Adapter arteck/ioBroker.switchbot-hub ist jedenfalls nicht offiziell in einem Repository gelistet. Du brauchst dich alseo nicht wundern wenn ein PRE-ALPHA Version /Githubonly Version mal nicht geht oder gar dei system ernsthaft stört.
Von direkten Installation von GitHub - insbesondere auf produktiven Systemen - wird explizit abgeraten.
GitHub Versionen können sich jederzeit (auch kurzfristig) ändern und durchaus auch in sich inkonsistent und fehlerhaft sein. Versionsangaben von GitHub Installationen sind Schall und Rauch da die Versionsnummer zumindest bei Verwendung der standardmäßigen Umgebung erst im Zuge der Releaseerstellung geändert wird.
Auf explizite Aufforderung durch den Entwickler kann eine GitHub Installation zur Fehlereingrenzung oder zum Test neuer Funktionalität - unter Inkaufnahme des erhöhten Risikos - natürlich erfolgen.
Adapter die nur via GitHub oder npm (also NICHT aus einem der beiden Repositories) installierbar sind sind mit erhöhter Vorsicht zu betrachten. Hier sollte der Entwickler drum ersucht werden eine Aufnahme in die Repositories zu veranlassen indem z.B. ein Issue im Adapterrepository erstellt wird.
Und falls es irgendwie unklar ist:
ioBroker unterstützt folgende Arten von Installation:
-
aus dem STABLE Repository
Das sind Adapter Releases die keine groben Fehler aufweisen (sollten). Natürlich kann es auch dort Fehler geben, die Behebung davon obliegt dem jeweiligen Dev und kann ggF auch dauern.
-
aus dem LATEST Repository
Das sind Adapter Releases die neu erstellt wurden und nur rudimentär getestet sind - oft auch als BETA Releases bezeichnet. Releases aus dem LATEST sind primär für unsere zahlreichen freiwilligen Tester gedacht. BETA / LATEST Releases können durchaus Fehler aufweisen - auch wenn ich davon ausgehe dass jeder aintainer dies zu vermeiden versucht. Vom Einsatz auf produktiven Systemen wird abgeraten außer man braucht irgenein neues Feature (z.B. neues Gerät) unbedingt. Hier muss dann jeder Entscheiden was ihm wichtig ist.
-
direkt von GITHUB
Von Installationen direkt aus Giuthub wird definitiv abgeraten außer auf Anweisung des Maintainers und für den Fall dass man gemeinsam mit diesem etwas testen will. Details siehe oben.
-
direkt von npm
Diese Installation kann erforderlich sein, wenn man eine bestimmte Version installieren möchte / muss. Im Normalfall sollte man direkte npm Installationen ebenso meiden wie direkte GitHub Installationen - ausgenommen um z.B. zu einer bekannten Version downzugraden - obwohl hier wenigstens ein definierter Stand garantiert ist.
Adapter die NUR via npm und/oder nur via GitHub installierbar sind sollte man meiden - diese wurden nicht mal einem rudimentären Review unterzogen und sollten mit dem Attribut "vollständig auf eigenes Risiko verwenden" installiert werden. Hier empfiehlt es sich den Developer zu ersuchen eine Aufnahme in die Repos zu veranlassen. Wenn dieser darauf nicht reagiert sollte man von einer eher kurzen und unklaren Lebensdauer des Adapters ausgehen. Support meiner-/unsererseits für solche Adapter ist mit Sicherheit minimalistisch.
Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
Support Repositoryverwaltung.Wer 'nen Kaffee spendieren will: https://paypal.me
-
-
@Thomas-Braun sorry für die späte Rückmeldung, jetzt hatte ich mal wieder Zeit.
Node.js ist jetzt auf Version 22.15.0
Soll ich die ganze Diagnose hier reinkopieren?
Sorry hab das noch nie gemacht. -
@Thomas-Braun sorry für die späte Rückmeldung, jetzt hatte ich mal wieder Zeit.
Node.js ist jetzt auf Version 22.15.0
Soll ich die ganze Diagnose hier reinkopieren?
Sorry hab das noch nie gemacht.Soll ich die ganze Diagnose hier reinkopieren?
Ja, denn nodejs 22.15.0 deutet stark darauf hin, dass du da mit einem veralteten 32Bit-System herumkurvst. Muss dann komplett neuinstalliert werden.
Sorry hab das noch nie gemacht.
Einfach nach dem Lauf des diag-Skripts wieder nach oben scrollen und alles zwischen den Kopiermarken hier reinkopieren.
-
Soll ich die ganze Diagnose hier reinkopieren?
Ja, denn nodejs 22.15.0 deutet stark darauf hin, dass du da mit einem veralteten 32Bit-System herumkurvst. Muss dann komplett neuinstalliert werden.
Sorry hab das noch nie gemacht.
Einfach nach dem Lauf des diag-Skripts wieder nach oben scrollen und alles zwischen den Kopiermarken hier reinkopieren.
Ja es läuft auf einem 32Bit-System
========== Start marking the full check here ===========Script v.2026-01-31 *** BASE SYSTEM *** Operating System: Raspbian GNU/Linux 11 (bullseye) Static hostname: raspberrypi Icon name: computer Kernel: Linux 5.10.103-v7l+ Architecture: arm OS is similar to: debian Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : armv7l 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: 13:06:24 up 14 days, 16:24, 1 user, load average: 13.57, 5.53, 2.41 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-05-26 13:06:24 CEST Universal time: Tue 2026-05-26 11:06:24 UTC RTC time: n/a 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 netdev gpio i2c spi iobroker User that is running 'js-controller': /home/iobroker/.diag.sh: line 495: [[: 1106 32632: syntax error in expression (error token is "32632") js-controller is not running *** DISPLAY-SERVER SETUP *** Display-Server: true Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix' *** MEMORY *** total used free shared buff/cache available Mem: 7.9G 2.5G 3.0G 0.0K 2.4G 5.2G Swap: 99M 17M 82M Total: 8.0G 2.5G 3.1G Active iob-Instances: 25 7898 M total memory 2513 M used memory 1173 M active memory 3475 M inactive memory 3016 M free memory 277 M buffer memory 2090 M swap cache 99 M total swap 17 M used swap 82 M free swap *** top - Table Of Processes *** top - 13:06:25 up 14 days, 16:24, 1 user, load average: 13.57, 5.53, 2.41 Tasks: 183 total, 5 running, 178 sleeping, 0 stopped, 0 zombie %Cpu(s): 65.7 us, 15.7 sy, 0.0 ni, 4.3 id, 11.4 wa, 0.0 hi, 2.9 si, 0.0 st MiB Mem : 7898.7 total, 3010.4 free, 2518.5 used, 2369.8 buff/cache MiB Swap: 100.0 total, 82.4 free, 17.6 used. 5206.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 /dev/root ext4 117G 46G 68G 41% / devtmpfs devtmpfs 3.7G 0 3.7G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 720K 1.6G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 253M 49M 204M 20% /boot tmpfs tmpfs 790M 0 790M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Mon May 11 20:41:54 2026] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Mon May 11 20:41:54 2026] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Mon May 11 20:41:57 2026] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 22G /var/ 11G /var/log 11G /var/lib 9.9G /var/lib/influxdb/data 9.9G /var/lib/influxdb Archived and active journals take up 3.6G in the file system. /opt/iobroker/backups: 14G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 2.6G /opt/iobroker/iobroker-data/ 2.0G /opt/iobroker/iobroker-data/history 330M /opt/iobroker/iobroker-data/files 140M /opt/iobroker/iobroker-data/backup-objects 61M /opt/iobroker/iobroker-data/files/vis-2 The five largest files in iobroker-data are: 30M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 18M /opt/iobroker/iobroker-data/states.jsonl 13M /opt/iobroker/iobroker-data/history/20260525/history.0_userdata.0.Heizung.Wärmemengen.Wärmemengen_Berechnung.Spannung_Durchflusssensor.json 12M /opt/iobroker/iobroker-data/history/20260524/history.0_userdata.0.Heizung.Wärmemengen.Wärmemengen_Berechnung.Spannung_Durchflusssensor.json 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-Silicon_Labs_WiMOD_iM871A-usb_02B12B4B-if00-port0 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: raspberrypi raspberrypi (version: 7.0.7, hostname: raspberrypi , alive, uptime: 298) Core adapters versions js-controller: 7.0.7 admin: 7.8.23 javascript: 9.0.18 nodejs modules from github: 2 +-- iobroker.sourceanalytix@0.4.12-1 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.sourceanalytix.git#362346b297c0a21c717ec20bd8d16331bca3b22d) +-- iobroker.switchbot-hub@0.1.2 (git+ssh://git@github.com/DrozmotiX/ioBroker.switchbot-hub.git#7a05fa59dfc5e3ce8d73018badc4e420996452f8) Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.admin.1 : admin : raspberrypi - enabled, port: 8089, bind: 0.0.0.0, run as: admin system.adapter.alexa-shoppinglist.0 : alexa-shoppinglist : raspberrypi - disabled system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled system.adapter.awattar.0 : awattar : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled system.adapter.birthdays.0 : birthdays : raspberrypi - enabled system.adapter.ble.0 : ble : raspberrypi - enabled + system.adapter.cloud.0 : cloud : raspberrypi - enabled system.adapter.device-reminder.0 : device-reminder : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.dwd.0 : dwd : raspberrypi - enabled system.adapter.e3dc-rscp.0 : e3dc-rscp : raspberrypi - disabled system.adapter.ecovacs-deebot.0 : ecovacs-deebot : raspberrypi - enabled system.adapter.followthesun.0 : followthesun : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.homeconnect.0 : homeconnect : raspberrypi - enabled system.adapter.hue.0 : hue : raspberrypi - disabled, port: 443 system.adapter.ical.0 : ical : raspberrypi - enabled system.adapter.ical.1 : ical : raspberrypi - enabled system.adapter.icons-material-png.0 : icons-material-png : raspberrypi - enabled system.adapter.icons-mfd-png.0 : icons-mfd-png : raspberrypi - enabled system.adapter.icons-ultimate-png.0 : icons-ultimate-png : raspberrypi - enabled + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.modbus.0 : modbus : raspberrypi - enabled + system.adapter.modbus.1 : modbus : raspberrypi - enabled system.adapter.mqtt.0 : mqtt : raspberrypi - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : raspberrypi - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.netatmo.0 : netatmo : raspberrypi - enabled system.adapter.parser.0 : parser : raspberrypi - enabled + system.adapter.pegelalarm.0 : pegelalarm : raspberrypi - enabled system.adapter.reolink.0 : reolink : raspberrypi - disabled + system.adapter.rpi2.0 : rpi2 : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.smartgarden.0 : smartgarden : raspberrypi - enabled + system.adapter.sourceanalytix.0 : sourceanalytix : raspberrypi - enabled system.adapter.switchbot-hub.0 : switchbot-hub : raspberrypi - enabled system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tvspielfilm.0 : tvspielfilm : raspberrypi - enabled system.adapter.vis-2.0 : vis-2 : raspberrypi - enabled system.adapter.vis-history.0 : vis-history : raspberrypi - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberrypi - enabled system.adapter.vis-icontwo.0 : vis-icontwo : raspberrypi - enabled + system.adapter.vis-inventwo.0 : vis-inventwo : raspberrypi - enabled system.adapter.vis-justgage.0 : vis-justgage : raspberrypi - enabled system.adapter.vis-map.0 : vis-map : raspberrypi - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : raspberrypi - enabled system.adapter.vis-plumb.0 : vis-plumb : raspberrypi - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wireless-mbus.0 : wireless-mbus : raspberrypi - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.admin.1 : admin : raspberrypi - enabled, port: 8089, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 + system.adapter.mqtt.1 : mqtt : raspberrypi - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - 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 "alexa-shoppinglist": 1.1.3, installed 1.1.3 Adapter "alexa2" : 3.27.4 , installed 3.27.4 Adapter "awattar" : 1.0.6 , installed 1.0.6 Adapter "backitup" : 3.3.14 , installed 3.3.14 Adapter "birthdays" : 5.0.0 , installed 5.0.0 Adapter "ble" : 0.14.0 , installed 0.14.0 Adapter "cloud" : 6.0.1 , installed 6.0.1 Adapter "device-reminder": 3.1.2 , installed 3.1.2 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "e3dc-rscp" : 1.4.4 , installed 1.4.4 Adapter "ecovacs-deebot": 1.4.15 , installed 1.4.15 Adapter "followthesun" : 0.5.2 , installed 0.5.2 Adapter "history" : 4.0.0 , installed 4.0.0 Adapter "homeconnect" : 1.5.2 , installed 1.5.2 Adapter "hue" : 3.16.2 , installed 3.16.2 Adapter "ical" : 1.20.0 , installed 1.20.0 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-ultimate-png": 1.0.1, installed 1.0.1 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "iot" : 5.0.12 , installed 5.0.12 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 "netatmo" : 3.1.0 , installed 3.1.0 Adapter "parser" : 3.1.0 , installed 3.1.0 Adapter "pegelalarm" : 1.3.12 , installed 1.3.12 Adapter "reolink" : 1.4.2 , installed 1.4.2 Adapter "rpi2" : 3.0.2 , installed 2.4.0 [Updatable] Adapter "shelly" : 10.6.1 , installed 10.6.1 Adapter "simple-api" : 3.0.7 , installed 3.0.7 Adapter "smartgarden" : 2.0.1 , installed 2.0.1 Adapter "socketio" : 7.1.3 , installed 7.1.3 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "tvprogram" : 4.0.4 , installed 4.0.4 Adapter "tvspielfilm" : 2.1.0 , installed 2.1.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.13.8 , installed 2.13.8 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.6.1 , installed 1.6.1 Adapter "vis-icontwo" : 2.11.3 , installed 2.11.3 Adapter "vis-inventwo" : 3.3.5 , installed 3.3.5 Adapter "vis-justgage" : 2.1.7 , installed 2.1.7 Adapter "vis-map" : 1.1.2 , installed 1.1.2 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-plumb" : 1.0.2 , installed 1.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 8.0.0 , installed 8.0.0 Adapter "wireless-mbus": 0.10.2 , installed 0.10.2 Adapter "ws" : 4.0.0 , installed 4.0.0 Objects and States Please stand by - This may take a while Objects: 31139 States: 29786 *** OS-Repositories and Updates *** W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B W: Failed to fetch https://repos.influxdata.com/debian/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B W: Some index files failed to download. They have been ignored, or old ones used instead. Hit:1 http://archive.raspberrypi.org/debian buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:3 https://deb.nodesource.com/node_22.x nodistro InRelease Get:4 https://repos.influxdata.com/debian buster InRelease [12.9 kB] Err:4 https://repos.influxdata.com/debian buster InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B Fetched 12.9 kB in 2s (7403 B/s) Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B W: Failed to fetch https://repos.influxdata.com/debian/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B W: Some index files failed to download. They have been ignored, or old ones used instead. 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 32711208 28348/sshd: /usr/sb tcp 0 0 127.0.0.1:8088 0.0.0.0:* LISTEN 999 32684605 25196/influxd tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 32722696 498/io.shelly.1 tcp 0 0 0.0.0.0:1884 0.0.0.0:* LISTEN 1001 32722982 540/io.mqtt.1 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 32716479 32632/iobroker.js-c tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 32716474 32632/iobroker.js-c tcp6 0 0 :::8081 :::* LISTEN 1001 32717318 32653/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 32722516 652/io.web.0 tcp6 0 0 :::22 :::* LISTEN 0 32711210 28348/sshd: /usr/sb tcp6 0 0 :::8086 :::* LISTEN 999 32683786 25196/influxd tcp6 0 0 :::3000 :::* LISTEN 109 11927 639/grafana-server tcp6 0 0 :::8089 :::* LISTEN 1001 32718939 32660/io.admin.1 tcp6 0 0 :::1984 :::* LISTEN 0 13680 380/go2rtc_linux_ar tcp6 0 0 :::8554 :::* LISTEN 0 13684 380/go2rtc_linux_ar tcp6 0 0 :::8555 :::* LISTEN 0 13688 380/go2rtc_linux_ar udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 32724346 480/io.shelly.0 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 12969 638/dhcpcd udp 0 0 0.0.0.0:43686 0.0.0.0:* 108 13561 374/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 13559 374/avahi-daemon: r udp6 0 0 :::44982 :::* 108 13562 374/avahi-daemon: r udp6 0 0 :::5353 :::* 108 13560 374/avahi-daemon: r *** Log File - Last 25 Lines *** 2026-05-26 13:07:25.997 - info: vis.0 (2422) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v22.15.0, js-controller: 7.0.7 2026-05-26 13:07:29.745 - info: javascript.0 (32671) script.js.common.Energie.Überschusssteuerung_Heizstab_Warmwasser: Heizstab Aus 2026-05-26 13:07:30.198 - info: vis.0 (2422) Terminated (NO_ERROR): Without reason 2026-05-26 13:07:35.691 - info: sourceanalytix.0 (827) Initialization of modbus.0.holdingRegisters.40072_Hausverbrauch_Leistung successfully 2026-05-26 13:07:35.693 - info: sourceanalytix.0 (827) Initialising (3 of 43) "mqtt.0.Wasserzaehler.main.value" 2026-05-26 13:07:35.779 - error: sourceanalytix.0 (827) Check settings for mqtt.0.Wasserzaehler.main.value ! Known valueAtDeviceReset : (1485.647) > known cumulative value (0) cannot proceed 2026-05-26 13:07:35.780 - error: sourceanalytix.0 (827) Troubleshoot Data mqtt.0.Wasserzaehler.main.value custom Data : {"common":{"name":"Wasserzaehler/main/value","write":true,"read":true,"role":"variable","desc":"mqtt server variable","unit":"m³","type":"string","custom":{"influxdb.0":{"enabled":true,"storageType":"Number","aliasId":"","changesOnly":true,"debounce":1000,"changesRelogInterval":3600,"changesMinDelta":0},"sourceanalytix.0":{"enabled":true,"selectedUnit":"m³","start_day":2002.6689999999999,"start_week":2002.6689999999999,"start_month":2002.6689999999999,"start_quarter":2002.6689999999999,"start_year":2002.6689999999999,"alias":"Wasserverbrauch","selectedPrice":"Water","costs":true,"consumption":true,"valueAtDeviceReset":1485.647,"valueAtDeviceInit":null,"cumulativeValue":2002.6689999999999}}},"native":{"topic":"Wasserzaehler/main/value"},"type":"state","_id":"mqtt.0.Wasserzaehler.main.value","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"},"from":"system.adapter.sourceanalytix.0","user":"system.user.admin","ts":1735686000625} 2026-05-26 13:07:35.781 - error: sourceanalytix.0 (827) Cannot handle calculations for mqtt.0.Wasserzaehler.main.value, check log messages and adjust settings! 2026-05-26 13:07:35.804 - error: sourceanalytix.0 (827) Initialization of mqtt.0.Wasserzaehler.main.value failed, check warn messages ! 2026-05-26 13:07:35.805 - info: sourceanalytix.0 (827) Initialising (4 of 43) "0_userdata.0.PV-Auswertung.Einspeisung" 2026-05-26 13:07:38.116 - info: shelly.1 (498) [authEnabled] 192.168.2.168 (shellyplusplugs / shellyplusplugs-c82e1808da70 / shellyplusplugs#c82e1808da70#1): This device is not protected via restricted login (see adapter documentation for details) 2026-05-26 13:07:51.431 - info: tankerkoenig.0 (968) Start first request 2026-05-26 13:07:54.469 - info: shelly.1 (498) [authEnabled] 192.168.2.168 (shellyplusplugs / shellyplusplugs-c82e1808da70 / shellyplusplugs#c82e1808da70#1): This device is not protected via restricted login (see adapter documentation for details) 2026-05-26 13:08:00.350 - info: javascript.0 (32671) script.js.common.Energie.Überschusssteuerung_Heizstab_Warmwasser: Heizstab Aus 2026-05-26 13:08:01.416 - info: sourceanalytix.0 (827) Initialization of 0_userdata.0.PV-Auswertung.Einspeisung successfully 2026-05-26 13:08:01.417 - info: sourceanalytix.0 (827) Initialising (5 of 43) "0_userdata.0.PV-Auswertung.Bezug" 2026-05-26 13:08:11.020 - info: shelly.1 (498) [authEnabled] 192.168.2.168 (shellyplusplugs / shellyplusplugs-c82e1808da70 / shellyplusplugs#c82e1808da70#1): This device is not protected via restricted login (see adapter documentation for details) 2026-05-26 13:08:14.755 - info: sourceanalytix.0 (827) Initialization of 0_userdata.0.PV-Auswertung.Bezug successfully 2026-05-26 13:08:14.756 - info: sourceanalytix.0 (827) Initialising (6 of 43) "0_userdata.0.PV-Auswertung.Batterie_Laden" 2026-05-26 13:08:19.757 - info: sourceanalytix.0 (827) Initialization of 0_userdata.0.PV-Auswertung.Batterie_Laden successfully 2026-05-26 13:08:19.758 - info: sourceanalytix.0 (827) Initialising (7 of 43) "0_userdata.0.PV-Auswertung.Batterie_Entladen" 2026-05-26 13:08:22.616 - info: javascript.0 (32671) script.js.common.Heizung.Überschusssteuerung: SG-READY EIN 2026-05-26 13:08:28.216 - info: shelly.1 (498) [authEnabled] 192.168.2.168 (shellyplusplugs / shellyplusplugs-c82e1808da70 / shellyplusplugs#c82e1808da70#1): This device is not protected via restricted login (see adapter documentation for details) 2026-05-26 13:08:29.140 - info: sourceanalytix.0 (827) Initialization of 0_userdata.0.PV-Auswertung.Batterie_Entladen successfully 2026-05-26 13:08:29.141 - info: sourceanalytix.0 (827) Initialising (8 of 43) "0_userdata.0.PV-Auswertung.Eigenverbrauch"============ Mark until here for C&P =============
iob diag has finished.
-
Ja es läuft auf einem 32Bit-System
========== Start marking the full check here ===========Script v.2026-01-31 *** BASE SYSTEM *** Operating System: Raspbian GNU/Linux 11 (bullseye) Static hostname: raspberrypi Icon name: computer Kernel: Linux 5.10.103-v7l+ Architecture: arm OS is similar to: debian Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : armv7l 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: 13:06:24 up 14 days, 16:24, 1 user, load average: 13.57, 5.53, 2.41 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-05-26 13:06:24 CEST Universal time: Tue 2026-05-26 11:06:24 UTC RTC time: n/a 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 netdev gpio i2c spi iobroker User that is running 'js-controller': /home/iobroker/.diag.sh: line 495: [[: 1106 32632: syntax error in expression (error token is "32632") js-controller is not running *** DISPLAY-SERVER SETUP *** Display-Server: true Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix' *** MEMORY *** total used free shared buff/cache available Mem: 7.9G 2.5G 3.0G 0.0K 2.4G 5.2G Swap: 99M 17M 82M Total: 8.0G 2.5G 3.1G Active iob-Instances: 25 7898 M total memory 2513 M used memory 1173 M active memory 3475 M inactive memory 3016 M free memory 277 M buffer memory 2090 M swap cache 99 M total swap 17 M used swap 82 M free swap *** top - Table Of Processes *** top - 13:06:25 up 14 days, 16:24, 1 user, load average: 13.57, 5.53, 2.41 Tasks: 183 total, 5 running, 178 sleeping, 0 stopped, 0 zombie %Cpu(s): 65.7 us, 15.7 sy, 0.0 ni, 4.3 id, 11.4 wa, 0.0 hi, 2.9 si, 0.0 st MiB Mem : 7898.7 total, 3010.4 free, 2518.5 used, 2369.8 buff/cache MiB Swap: 100.0 total, 82.4 free, 17.6 used. 5206.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 /dev/root ext4 117G 46G 68G 41% / devtmpfs devtmpfs 3.7G 0 3.7G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 720K 1.6G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 253M 49M 204M 20% /boot tmpfs tmpfs 790M 0 790M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Mon May 11 20:41:54 2026] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Mon May 11 20:41:54 2026] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Mon May 11 20:41:57 2026] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 22G /var/ 11G /var/log 11G /var/lib 9.9G /var/lib/influxdb/data 9.9G /var/lib/influxdb Archived and active journals take up 3.6G in the file system. /opt/iobroker/backups: 14G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 2.6G /opt/iobroker/iobroker-data/ 2.0G /opt/iobroker/iobroker-data/history 330M /opt/iobroker/iobroker-data/files 140M /opt/iobroker/iobroker-data/backup-objects 61M /opt/iobroker/iobroker-data/files/vis-2 The five largest files in iobroker-data are: 30M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 18M /opt/iobroker/iobroker-data/states.jsonl 13M /opt/iobroker/iobroker-data/history/20260525/history.0_userdata.0.Heizung.Wärmemengen.Wärmemengen_Berechnung.Spannung_Durchflusssensor.json 12M /opt/iobroker/iobroker-data/history/20260524/history.0_userdata.0.Heizung.Wärmemengen.Wärmemengen_Berechnung.Spannung_Durchflusssensor.json 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-Silicon_Labs_WiMOD_iM871A-usb_02B12B4B-if00-port0 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: raspberrypi raspberrypi (version: 7.0.7, hostname: raspberrypi , alive, uptime: 298) Core adapters versions js-controller: 7.0.7 admin: 7.8.23 javascript: 9.0.18 nodejs modules from github: 2 +-- iobroker.sourceanalytix@0.4.12-1 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.sourceanalytix.git#362346b297c0a21c717ec20bd8d16331bca3b22d) +-- iobroker.switchbot-hub@0.1.2 (git+ssh://git@github.com/DrozmotiX/ioBroker.switchbot-hub.git#7a05fa59dfc5e3ce8d73018badc4e420996452f8) Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.admin.1 : admin : raspberrypi - enabled, port: 8089, bind: 0.0.0.0, run as: admin system.adapter.alexa-shoppinglist.0 : alexa-shoppinglist : raspberrypi - disabled system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled system.adapter.awattar.0 : awattar : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled system.adapter.birthdays.0 : birthdays : raspberrypi - enabled system.adapter.ble.0 : ble : raspberrypi - enabled + system.adapter.cloud.0 : cloud : raspberrypi - enabled system.adapter.device-reminder.0 : device-reminder : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.dwd.0 : dwd : raspberrypi - enabled system.adapter.e3dc-rscp.0 : e3dc-rscp : raspberrypi - disabled system.adapter.ecovacs-deebot.0 : ecovacs-deebot : raspberrypi - enabled system.adapter.followthesun.0 : followthesun : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.homeconnect.0 : homeconnect : raspberrypi - enabled system.adapter.hue.0 : hue : raspberrypi - disabled, port: 443 system.adapter.ical.0 : ical : raspberrypi - enabled system.adapter.ical.1 : ical : raspberrypi - enabled system.adapter.icons-material-png.0 : icons-material-png : raspberrypi - enabled system.adapter.icons-mfd-png.0 : icons-mfd-png : raspberrypi - enabled system.adapter.icons-ultimate-png.0 : icons-ultimate-png : raspberrypi - enabled + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.modbus.0 : modbus : raspberrypi - enabled + system.adapter.modbus.1 : modbus : raspberrypi - enabled system.adapter.mqtt.0 : mqtt : raspberrypi - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : raspberrypi - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.netatmo.0 : netatmo : raspberrypi - enabled system.adapter.parser.0 : parser : raspberrypi - enabled + system.adapter.pegelalarm.0 : pegelalarm : raspberrypi - enabled system.adapter.reolink.0 : reolink : raspberrypi - disabled + system.adapter.rpi2.0 : rpi2 : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.smartgarden.0 : smartgarden : raspberrypi - enabled + system.adapter.sourceanalytix.0 : sourceanalytix : raspberrypi - enabled system.adapter.switchbot-hub.0 : switchbot-hub : raspberrypi - enabled system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tvspielfilm.0 : tvspielfilm : raspberrypi - enabled system.adapter.vis-2.0 : vis-2 : raspberrypi - enabled system.adapter.vis-history.0 : vis-history : raspberrypi - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberrypi - enabled system.adapter.vis-icontwo.0 : vis-icontwo : raspberrypi - enabled + system.adapter.vis-inventwo.0 : vis-inventwo : raspberrypi - enabled system.adapter.vis-justgage.0 : vis-justgage : raspberrypi - enabled system.adapter.vis-map.0 : vis-map : raspberrypi - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : raspberrypi - enabled system.adapter.vis-plumb.0 : vis-plumb : raspberrypi - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wireless-mbus.0 : wireless-mbus : raspberrypi - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.admin.1 : admin : raspberrypi - enabled, port: 8089, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 + system.adapter.mqtt.1 : mqtt : raspberrypi - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - 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 "alexa-shoppinglist": 1.1.3, installed 1.1.3 Adapter "alexa2" : 3.27.4 , installed 3.27.4 Adapter "awattar" : 1.0.6 , installed 1.0.6 Adapter "backitup" : 3.3.14 , installed 3.3.14 Adapter "birthdays" : 5.0.0 , installed 5.0.0 Adapter "ble" : 0.14.0 , installed 0.14.0 Adapter "cloud" : 6.0.1 , installed 6.0.1 Adapter "device-reminder": 3.1.2 , installed 3.1.2 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "e3dc-rscp" : 1.4.4 , installed 1.4.4 Adapter "ecovacs-deebot": 1.4.15 , installed 1.4.15 Adapter "followthesun" : 0.5.2 , installed 0.5.2 Adapter "history" : 4.0.0 , installed 4.0.0 Adapter "homeconnect" : 1.5.2 , installed 1.5.2 Adapter "hue" : 3.16.2 , installed 3.16.2 Adapter "ical" : 1.20.0 , installed 1.20.0 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-ultimate-png": 1.0.1, installed 1.0.1 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "iot" : 5.0.12 , installed 5.0.12 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 "netatmo" : 3.1.0 , installed 3.1.0 Adapter "parser" : 3.1.0 , installed 3.1.0 Adapter "pegelalarm" : 1.3.12 , installed 1.3.12 Adapter "reolink" : 1.4.2 , installed 1.4.2 Adapter "rpi2" : 3.0.2 , installed 2.4.0 [Updatable] Adapter "shelly" : 10.6.1 , installed 10.6.1 Adapter "simple-api" : 3.0.7 , installed 3.0.7 Adapter "smartgarden" : 2.0.1 , installed 2.0.1 Adapter "socketio" : 7.1.3 , installed 7.1.3 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "tvprogram" : 4.0.4 , installed 4.0.4 Adapter "tvspielfilm" : 2.1.0 , installed 2.1.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.13.8 , installed 2.13.8 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.6.1 , installed 1.6.1 Adapter "vis-icontwo" : 2.11.3 , installed 2.11.3 Adapter "vis-inventwo" : 3.3.5 , installed 3.3.5 Adapter "vis-justgage" : 2.1.7 , installed 2.1.7 Adapter "vis-map" : 1.1.2 , installed 1.1.2 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-plumb" : 1.0.2 , installed 1.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 8.0.0 , installed 8.0.0 Adapter "wireless-mbus": 0.10.2 , installed 0.10.2 Adapter "ws" : 4.0.0 , installed 4.0.0 Objects and States Please stand by - This may take a while Objects: 31139 States: 29786 *** OS-Repositories and Updates *** W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B W: Failed to fetch https://repos.influxdata.com/debian/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B W: Some index files failed to download. They have been ignored, or old ones used instead. Hit:1 http://archive.raspberrypi.org/debian buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:3 https://deb.nodesource.com/node_22.x nodistro InRelease Get:4 https://repos.influxdata.com/debian buster InRelease [12.9 kB] Err:4 https://repos.influxdata.com/debian buster InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B Fetched 12.9 kB in 2s (7403 B/s) Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B W: Failed to fetch https://repos.influxdata.com/debian/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B W: Some index files failed to download. They have been ignored, or old ones used instead. 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 32711208 28348/sshd: /usr/sb tcp 0 0 127.0.0.1:8088 0.0.0.0:* LISTEN 999 32684605 25196/influxd tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 32722696 498/io.shelly.1 tcp 0 0 0.0.0.0:1884 0.0.0.0:* LISTEN 1001 32722982 540/io.mqtt.1 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 32716479 32632/iobroker.js-c tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 32716474 32632/iobroker.js-c tcp6 0 0 :::8081 :::* LISTEN 1001 32717318 32653/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 32722516 652/io.web.0 tcp6 0 0 :::22 :::* LISTEN 0 32711210 28348/sshd: /usr/sb tcp6 0 0 :::8086 :::* LISTEN 999 32683786 25196/influxd tcp6 0 0 :::3000 :::* LISTEN 109 11927 639/grafana-server tcp6 0 0 :::8089 :::* LISTEN 1001 32718939 32660/io.admin.1 tcp6 0 0 :::1984 :::* LISTEN 0 13680 380/go2rtc_linux_ar tcp6 0 0 :::8554 :::* LISTEN 0 13684 380/go2rtc_linux_ar tcp6 0 0 :::8555 :::* LISTEN 0 13688 380/go2rtc_linux_ar udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 32724346 480/io.shelly.0 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 12969 638/dhcpcd udp 0 0 0.0.0.0:43686 0.0.0.0:* 108 13561 374/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 13559 374/avahi-daemon: r udp6 0 0 :::44982 :::* 108 13562 374/avahi-daemon: r udp6 0 0 :::5353 :::* 108 13560 374/avahi-daemon: r *** Log File - Last 25 Lines *** 2026-05-26 13:07:25.997 - info: vis.0 (2422) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v22.15.0, js-controller: 7.0.7 2026-05-26 13:07:29.745 - info: javascript.0 (32671) script.js.common.Energie.Überschusssteuerung_Heizstab_Warmwasser: Heizstab Aus 2026-05-26 13:07:30.198 - info: vis.0 (2422) Terminated (NO_ERROR): Without reason 2026-05-26 13:07:35.691 - info: sourceanalytix.0 (827) Initialization of modbus.0.holdingRegisters.40072_Hausverbrauch_Leistung successfully 2026-05-26 13:07:35.693 - info: sourceanalytix.0 (827) Initialising (3 of 43) "mqtt.0.Wasserzaehler.main.value" 2026-05-26 13:07:35.779 - error: sourceanalytix.0 (827) Check settings for mqtt.0.Wasserzaehler.main.value ! Known valueAtDeviceReset : (1485.647) > known cumulative value (0) cannot proceed 2026-05-26 13:07:35.780 - error: sourceanalytix.0 (827) Troubleshoot Data mqtt.0.Wasserzaehler.main.value custom Data : {"common":{"name":"Wasserzaehler/main/value","write":true,"read":true,"role":"variable","desc":"mqtt server variable","unit":"m³","type":"string","custom":{"influxdb.0":{"enabled":true,"storageType":"Number","aliasId":"","changesOnly":true,"debounce":1000,"changesRelogInterval":3600,"changesMinDelta":0},"sourceanalytix.0":{"enabled":true,"selectedUnit":"m³","start_day":2002.6689999999999,"start_week":2002.6689999999999,"start_month":2002.6689999999999,"start_quarter":2002.6689999999999,"start_year":2002.6689999999999,"alias":"Wasserverbrauch","selectedPrice":"Water","costs":true,"consumption":true,"valueAtDeviceReset":1485.647,"valueAtDeviceInit":null,"cumulativeValue":2002.6689999999999}}},"native":{"topic":"Wasserzaehler/main/value"},"type":"state","_id":"mqtt.0.Wasserzaehler.main.value","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"},"from":"system.adapter.sourceanalytix.0","user":"system.user.admin","ts":1735686000625} 2026-05-26 13:07:35.781 - error: sourceanalytix.0 (827) Cannot handle calculations for mqtt.0.Wasserzaehler.main.value, check log messages and adjust settings! 2026-05-26 13:07:35.804 - error: sourceanalytix.0 (827) Initialization of mqtt.0.Wasserzaehler.main.value failed, check warn messages ! 2026-05-26 13:07:35.805 - info: sourceanalytix.0 (827) Initialising (4 of 43) "0_userdata.0.PV-Auswertung.Einspeisung" 2026-05-26 13:07:38.116 - info: shelly.1 (498) [authEnabled] 192.168.2.168 (shellyplusplugs / shellyplusplugs-c82e1808da70 / shellyplusplugs#c82e1808da70#1): This device is not protected via restricted login (see adapter documentation for details) 2026-05-26 13:07:51.431 - info: tankerkoenig.0 (968) Start first request 2026-05-26 13:07:54.469 - info: shelly.1 (498) [authEnabled] 192.168.2.168 (shellyplusplugs / shellyplusplugs-c82e1808da70 / shellyplusplugs#c82e1808da70#1): This device is not protected via restricted login (see adapter documentation for details) 2026-05-26 13:08:00.350 - info: javascript.0 (32671) script.js.common.Energie.Überschusssteuerung_Heizstab_Warmwasser: Heizstab Aus 2026-05-26 13:08:01.416 - info: sourceanalytix.0 (827) Initialization of 0_userdata.0.PV-Auswertung.Einspeisung successfully 2026-05-26 13:08:01.417 - info: sourceanalytix.0 (827) Initialising (5 of 43) "0_userdata.0.PV-Auswertung.Bezug" 2026-05-26 13:08:11.020 - info: shelly.1 (498) [authEnabled] 192.168.2.168 (shellyplusplugs / shellyplusplugs-c82e1808da70 / shellyplusplugs#c82e1808da70#1): This device is not protected via restricted login (see adapter documentation for details) 2026-05-26 13:08:14.755 - info: sourceanalytix.0 (827) Initialization of 0_userdata.0.PV-Auswertung.Bezug successfully 2026-05-26 13:08:14.756 - info: sourceanalytix.0 (827) Initialising (6 of 43) "0_userdata.0.PV-Auswertung.Batterie_Laden" 2026-05-26 13:08:19.757 - info: sourceanalytix.0 (827) Initialization of 0_userdata.0.PV-Auswertung.Batterie_Laden successfully 2026-05-26 13:08:19.758 - info: sourceanalytix.0 (827) Initialising (7 of 43) "0_userdata.0.PV-Auswertung.Batterie_Entladen" 2026-05-26 13:08:22.616 - info: javascript.0 (32671) script.js.common.Heizung.Überschusssteuerung: SG-READY EIN 2026-05-26 13:08:28.216 - info: shelly.1 (498) [authEnabled] 192.168.2.168 (shellyplusplugs / shellyplusplugs-c82e1808da70 / shellyplusplugs#c82e1808da70#1): This device is not protected via restricted login (see adapter documentation for details) 2026-05-26 13:08:29.140 - info: sourceanalytix.0 (827) Initialization of 0_userdata.0.PV-Auswertung.Batterie_Entladen successfully 2026-05-26 13:08:29.141 - info: sourceanalytix.0 (827) Initialising (8 of 43) "0_userdata.0.PV-Auswertung.Eigenverbrauch"============ Mark until here for C&P =============
iob diag has finished.
Dann installier da komplett von Grund auf neu die aktuelle 64Bit-Lite-Version von RaspberryOS 13 'Trixie'.
Dein
Raspbian GNU/Linux 11 (bullseye)
ist ja auch schon längst tot.Dann während der Installation einen user anlegen, der nicht 'pi' heißt.
-
Habe tatsächlich schon einen Pi 5 parallel am laufen...den Umzug habe ich bisher noch nicht gewagt. Da muss ich mir mal in Ruhe Zeit nehmen dafür.
Da muss ich mir mal in Ruhe Zeit nehmen dafür.
Aber nicht zu lange, dein derzeitiges Ding ist überfällig.
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 Anmelden619
Online32.9k
Benutzer83.2k
Themen1.3m
Beiträge
ioBroker Community 2014-2026
