NEWS
Wir empfehlen: Node.js 22.x
-
Hallo zusammen,
mein IOB System ist auf aktuellem Stand auf Debian 12, allerdings noch auf nodeJS v20.19.5.
Wenn ich jetzt mittels "iob nodejs-update 22" ein Update auf die 22.19.0 mache, dann klappt das, aber der iob startet nicht mehr. Mache ich ein downgrade (iob nodejs-update 20), ist wieder alles OK.Die Fehlermeldung bei mir ist:
Sep 16 14:51:49 iobroker01 bash[197699]: at Module._compile (node:internal/modules/cjs/loader:1706:14) Sep 16 14:51:49 iobroker01 bash[197699]: at Object.<anonymous> (/opt/iobroker/node_modules/unix-dgram/lib/unix_dgram.js:4:34) Sep 16 14:51:49 iobroker01 bash[197699]: at bindings (/opt/iobroker/node_modules/bindings/bindings.js:112:48) Sep 16 14:51:49 iobroker01 bash[197699]: at require (node:internal/modules/helpers:147:16) Sep 16 14:51:49 iobroker01 bash[197699]: at Module.require (node:internal/modules/cjs/loader:1463:12) Sep 16 14:51:49 iobroker01 bash[197699]: at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) Sep 16 14:51:49 iobroker01 bash[197699]: at TracingChannel.traceSync (node:diagnostics_channel:322:14) Sep 16 14:51:49 iobroker01 bash[197699]: at Function._load (node:internal/modules/cjs/loader:1263:12) Sep 16 14:51:49 iobroker01 bash[197699]: at Module.load (node:internal/modules/cjs/loader:1441:32) Sep 16 14:51:49 iobroker01 bash[197699]: at Object..node (node:internal/modules/cjs/loader:1865:18) Sep 16 14:51:49 iobroker01 bash[197699]: the module (for instance, using `npm rebuild` or `npm install`). Sep 16 14:51:49 iobroker01 bash[197699]: NODE_MODULE_VERSION 127. Please try re-compiling or re-installing Sep 16 14:51:49 iobroker01 bash[197699]: NODE_MODULE_VERSION 115. This version of Node.js requires Sep 16 14:51:49 iobroker01 bash[197699]: was compiled against a different Node.js version using Sep 16 14:51:49 iobroker01 bash[197699]: Uncaught Rejection: Error: The module '/opt/iobroker/node_modules/unix-dgram/build/Release/unix_dgram.node'Wenn ich nach dem Update nochmal "iob fix", "iob update", "iob upgrade", "apt update" (als root) oder "apt upgrade" (also root) ausführe, findet er nichts neues.
Ist das ein bekannter Fehler? Wie bekomme ich den am saubersten weg?
Besten Dank,
KoMa@koma666 sagte in Wir empfehlen: Node.js 22.x:
Ist das ein bekannter Fehler? Wie bekomme ich den am saubersten weg?
Dazu müsstest du schauen, wo genau der Rebuild scheitert. Dein Log hat ja nur Fragmente. (Und ist auch chronologisch falsch herum...)
So wird was sinnvolleres draus:Sep 16 14:51:49 iobroker01 bash[197699]: Uncaught Rejection: Error: The module '/opt/iobroker/node_modules/unix-dgram/build/Release/unix_dgram.node' Sep 16 14:51:49 iobroker01 bash[197699]: was compiled against a different Node.js version using Sep 16 14:51:49 iobroker01 bash[197699]: NODE_MODULE_VERSION 115. This version of Node.js requires Sep 16 14:51:49 iobroker01 bash[197699]: NODE_MODULE_VERSION 127. Please try re-compiling or re-installing Sep 16 14:51:49 iobroker01 bash[197699]: the module (for instance, using `npm rebuild` or `npm install`).Du musst also schauen, wo
unix-dgramverwendet wird und den Adapter neubauen oder neuinstallieren.cd /opt/iobroker && npm ls unix-dgramanschauen.
-
@koma666 sagte in Wir empfehlen: Node.js 22.x:
Ist das ein bekannter Fehler? Wie bekomme ich den am saubersten weg?
Dazu müsstest du schauen, wo genau der Rebuild scheitert. Dein Log hat ja nur Fragmente. (Und ist auch chronologisch falsch herum...)
So wird was sinnvolleres draus:Sep 16 14:51:49 iobroker01 bash[197699]: Uncaught Rejection: Error: The module '/opt/iobroker/node_modules/unix-dgram/build/Release/unix_dgram.node' Sep 16 14:51:49 iobroker01 bash[197699]: was compiled against a different Node.js version using Sep 16 14:51:49 iobroker01 bash[197699]: NODE_MODULE_VERSION 115. This version of Node.js requires Sep 16 14:51:49 iobroker01 bash[197699]: NODE_MODULE_VERSION 127. Please try re-compiling or re-installing Sep 16 14:51:49 iobroker01 bash[197699]: the module (for instance, using `npm rebuild` or `npm install`).Du musst also schauen, wo
unix-dgramverwendet wird und den Adapter neubauen oder neuinstallieren.cd /opt/iobroker && npm ls unix-dgramanschauen.
@thomas-braun said in Wir empfehlen: Node.js 22.x:
Ja, das lag an "journalctl -r", aber ich denke die Fehler wurden ersichtlich ;-)Mit nodejs 20 sieht es so aus:
iobroker.inst@3.0.0 /opt/iobroker └─┬ iobroker.js-controller@7.0.7 └─┬ @iobroker/js-controller-common-db@7.0.7 └─┬ winston-syslog@2.7.1 └── unix-dgram@2.0.6Dann habe ich ein Update von nodeJS gemacht:
iob stop iob fix iob nodejs-update 22 iob fixDanach sieht es (genau)so aus:
iobroker.inst@3.0.0 /opt/iobroker └─┬ iobroker.js-controller@7.0.7 └─┬ @iobroker/js-controller-common-db@7.0.7 └─┬ winston-syslog@2.7.1 └── unix-dgram@2.0.6 -
@thomas-braun said in Wir empfehlen: Node.js 22.x:
Ja, das lag an "journalctl -r", aber ich denke die Fehler wurden ersichtlich ;-)Mit nodejs 20 sieht es so aus:
iobroker.inst@3.0.0 /opt/iobroker └─┬ iobroker.js-controller@7.0.7 └─┬ @iobroker/js-controller-common-db@7.0.7 └─┬ winston-syslog@2.7.1 └── unix-dgram@2.0.6Dann habe ich ein Update von nodeJS gemacht:
iob stop iob fix iob nodejs-update 22 iob fixDanach sieht es (genau)so aus:
iobroker.inst@3.0.0 /opt/iobroker └─┬ iobroker.js-controller@7.0.7 └─┬ @iobroker/js-controller-common-db@7.0.7 └─┬ winston-syslog@2.7.1 └── unix-dgram@2.0.6@thomas-braun said in Wir empfehlen: Node.js 22.x:
Ich habe jetzt mal testweise " npm install unix-dgram" in /opt/iobroker gemacht und nun startet iob wieder, aber es sieht so aus:iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.js-controller@7.0.7 │ └─┬ @iobroker/js-controller-common-db@7.0.7 │ └─┬ winston-syslog@2.7.1 │ └── unix-dgram@2.0.6 └── unix-dgram@2.0.7Ich vermute mal das löst zwar mein Problem, ist aber unsauber, da unix-dgram@207 ja vermutlich besser unterhalb von winston-syslog sein sollte, oder?
-
@thomas-braun said in Wir empfehlen: Node.js 22.x:
Ich habe jetzt mal testweise " npm install unix-dgram" in /opt/iobroker gemacht und nun startet iob wieder, aber es sieht so aus:iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.js-controller@7.0.7 │ └─┬ @iobroker/js-controller-common-db@7.0.7 │ └─┬ winston-syslog@2.7.1 │ └── unix-dgram@2.0.6 └── unix-dgram@2.0.7Ich vermute mal das löst zwar mein Problem, ist aber unsauber, da unix-dgram@207 ja vermutlich besser unterhalb von winston-syslog sein sollte, oder?
@koma666 sagte in Wir empfehlen: Node.js 22.x:
da unix-dgram@207 ja vermutlich besser unterhalb von winston-syslog sein sollte, oder?
Ja, richtig. Auf meinem System ist das auch so.
-
@thomas-braun said in Wir empfehlen: Node.js 22.x:
Ich habe jetzt mal testweise " npm install unix-dgram" in /opt/iobroker gemacht und nun startet iob wieder, aber es sieht so aus:iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.js-controller@7.0.7 │ └─┬ @iobroker/js-controller-common-db@7.0.7 │ └─┬ winston-syslog@2.7.1 │ └── unix-dgram@2.0.6 └── unix-dgram@2.0.7Ich vermute mal das löst zwar mein Problem, ist aber unsauber, da unix-dgram@207 ja vermutlich besser unterhalb von winston-syslog sein sollte, oder?
@thomas-braun said in Wir empfehlen: Node.js 22.x:
Nächstes Update ... js-controller auf 7.0.6 mittels "npm install iobroker.js-controller@7.0.6" downgegraded und der ioBroker startet auch mit nodeJS 22:
iobroker.inst@3.0.0 /opt/iobroker └─┬ iobroker.js-controller@7.0.6 └─┬ @iobroker/js-controller-common-db@7.0.6 └─┬ winston-syslog@2.7.1 └── unix-dgram@2.0.6Danach wieder upgedated mit "iob upgrade self" und "iob fix" und es sieht wieder so aus:
iobroker.inst@3.0.0 /opt/iobroker └─┬ iobroker.js-controller@7.0.7 └─┬ @iobroker/js-controller-common-db@7.0.7 └─┬ winston-syslog@2.7.1 └── unix-dgram@2.0.6Und der IOB läuft!
Jetzt ist mein System auf nodeJS 22.19.0, NPM 10.9.3 und js-controller 7.0.7.
Das Problem scheint also zu bestehen, wenn der js-controller schon vor dem nodeJS Update auf 7.0.7 ist. Ist er noch auf 7.0.6 und wird erst danach aktualisiert sieht alles gut aus.
Auf jeden Fall vielen Dank! Deine Tips mit dem "npm ls unix-dgram" haben mich auf jeden Fall in die richtige Richtung geschubst ...
-
Hallo ich habe auf meiner Synologie den Docker und darin den iobroker aber wie bekomme ich den jetzt aktualisiert?
Roll da den aktuellen Docker drüber. Ist soweit ich weiß v11 mittlerweile.
-
Ich brauche bitte ebenfalls eure Hilfe. Mir wird seit Wochen angezeigt, dass es ein Nodejs Update gibt, leider wird es aber nicht aktualisiert. Was mache ich falsch, wenn iob diag, iob fix und iob nodejs-update nichts bringen?
iob nodejs-update
ioBroker nodejs fixer 2025-08-09 Recommended nodejs-version is: 22.20.0 Checking your installation now. Please be patient! Your current setup is: /usr/bin/nodejs v22.15.0 /usr/bin/node v22.15.0 /usr/bin/npm 10.9.2 /usr/bin/npx 10.9.2 /usr/bin/corepack 0.32.0 We found these nodejs versions available for installation: 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 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main armhf Packages Nothing to do - Your installation is using the correct paths. You are running nodejs v22.15.0. Do you want to install recommended version 22.20.0? Press <y> to continue or any other key to quitiob diag gibt aus:
========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: raspberrypi Icon name: computer Kernel: Linux 6.1.21-v8+ Architecture: arm64 OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : aarch64 Userland : 32 bit Systemuptime and Load: 20:26:47 up 5:03, 1 user, load average: 1.47, 1.38, 1.21 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Fri 2025-10-03 20:26:47 CEST Universal time: Fri 2025-10-03 18:26:47 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': iobroker HOME=/home/iobroker SUDO_HOME=/home/pi GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 2.8G 3.9G 14M 1.7G 5.4G Swap: 209M 0B 209M Total: 8.4G 2.8G 4.1G Active iob-Instances: 37 7812 M total memory 2636 M used memory 2538 M active memory 1185 M inactive memory 3728 M free memory 477 M buffer memory 1104 M swap cache 199 M total swap 0 M used swap 199 M free swap *** top - Table Of Processes *** top - 20:26:48 up 5:03, 1 user, load average: 1.47, 1.38, 1.21 Tasks: 201 total, 3 running, 198 sleeping, 0 stopped, 0 zombie %Cpu(s): 27.1 us, 12.5 sy, 0.0 ni, 58.3 id, 0.0 wa, 0.0 hi, 2.1 si, 0.0 st MiB Mem : 7812.3 total, 3727.7 free, 2637.6 used, 1582.4 buff/cache MiB Swap: 200.0 total, 200.0 free, 0.0 used. 5174.7 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** 23 CRITICAL ERRORS DETECTED! Check 'sudo dmesg --level=emerg,alert,crit -T' for details *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 117G 25G 88G 22% / devtmpfs devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 11M 1.6G 1% /run tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock tmpfs tmpfs 3.9G 3.0M 3.9G 1% /tmp /dev/mmcblk0p1 vfat 253M 51M 202M 20% /boot /dev/sda1 vfat 233G 31G 203G 14% /media/usb tmpfs tmpfs 782M 12K 782M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Fri Oct 3 15:22:56 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:D9:04:68 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 #console=ttyS0,115200 console=tty1 root=PARTUUID=cdb3ca5a-02 rootfstype=ext4 fsck.repair=yes rootwait [Fri Oct 3 15:22:57 2025] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Fri Oct 3 15:22:57 2025] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Fri Oct 3 15:23:02 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,flush,errors=remount-ro `-/media/usb /dev/sda1 vfat rw,nosuid,nodev,noexec,relatime,sync,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 7.9G /var/ 4.0G /var/log 3.7G /var/log/journal/3e23e34d17484a28b9473f69f7d9d21c 3.7G /var/log/journal 3.5G /var/cache/apt Archived and active journals take up 3.6G in the file system. /opt/iobroker/backups: 2.6G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 844M /opt/iobroker/iobroker-data/ 519M /opt/iobroker/iobroker-data/files 246M /opt/iobroker/iobroker-data/backup-objects 67M /opt/iobroker/iobroker-data/files/echarts.admin 61M /opt/iobroker/iobroker-data/files/echarts The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 31M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map 26M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.15.0 /usr/bin/node v22.15.0 /usr/bin/npm 10.9.2 /usr/bin/npx 10.9.2 /usr/bin/corepack 0.32.0 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 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/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 = *** 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: 13555) Core adapters versions js-controller: 7.0.7 admin: 7.7.2 javascript: 8.9.2 nodejs modules from github: 12 +-- iobroker.ble@0.14.1 (git+ssh://git@github.com/AlCalzone/ioBroker.ble.git#f0dd1214a8482b2d60cbf48f642e2add12ece177) +-- iobroker.esphome@0.5.0-beta.10 (git+ssh://git@github.com/DrozmotiX/ioBroker.esphome.git#6b97f67d1d1ce6af3a0e598ba77eec8f570a0854) +-- iobroker.ical@1.17.0 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.ical.git#cec92fab5a12b1a00723f397b6f72eba1fa0ab00) +-- iobroker.jarvis@3.2.0-rc.17 (git+ssh://git@github.com/Zefau/ioBroker.jarvis.git#65370bd2ad4617722447bcff04ba4dc6429bed9b) +-- iobroker.keyble@0.1.1 (git+ssh://git@github.com/oyooyo/ioBroker.keyble.git#1a0292db0cc4402582885d6414a5a1bd2af804a3) +-- iobroker.nut@1.7.0 (git+ssh://git@github.com/Apollon77/ioBroker.nut.git#65bbeeb4f8b12938eb4e77af9ee7ef1ecc2cfd39) +-- iobroker.paw@0.3.2 (git+ssh://git@github.com/bondrogeen/ioBroker.paw.git#66372ac89942184fb4022e6838b2d36940ed7711) +-- iobroker.sonoff@3.3.0 (git+ssh://git@github.com/ioBroker/ioBroker.sonoff.git#fa775b5d1170181d1c2055c8537ef5b9103a4f24) +-- iobroker.trashschedule@4.0.1 (git+ssh://git@github.com/klein0r/ioBroker.trashschedule.git#0048391f4ff95ea965c6dede4ca84d53b5462b20) +-- iobroker.tuya@3.17.0 (git+ssh://git@github.com/Apollon77/ioBroker.tuya.git#640df7360a877f37764a31d628e4d6de3ed1f6e3) +-- iobroker.viessmannapi@2.4.3 (git+ssh://git@github.com/TA2k/ioBroker.viessmannapi.git#a45b02bd2888bdc40c7bca9be886c88c95e2e40e) +-- iobroker.vw-connect@0.6.0 (git+ssh://git@github.com/ta2k/ioBroker.vw-connect.git#1bea7002b834d672f998717c2232223d4d1d13af) Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.ble.1 : ble : raspberrypi - enabled + system.adapter.bring.0 : bring : raspberrypi - enabled system.adapter.daswetter.0 : daswetter : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.dwd.0 : dwd : raspberrypi - enabled + system.adapter.echarts.0 : echarts : raspberrypi - enabled system.adapter.feiertage.0 : feiertage : raspberrypi - enabled + system.adapter.fritzdect.0 : fritzdect : raspberrypi - enabled + system.adapter.fullybrowser.0 : fullybrowser : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.homeconnect.0 : homeconnect : raspberrypi - enabled system.adapter.ical.0 : ical : raspberrypi - enabled + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.jarvis.0 : jarvis : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.meross.0 : meross : raspberrypi - enabled + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1883, bind: 192.168.178.76 + system.adapter.nut.0 : nut : raspberrypi - enabled + system.adapter.parser.0 : parser : raspberrypi - enabled + system.adapter.pollenflug.0 : pollenflug : raspberrypi - enabled + system.adapter.pvforecast.0 : pvforecast : raspberrypi - enabled + system.adapter.rpi2.0 : rpi2 : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : raspberrypi - enabled, port: 8087, bind: 0.0.0.0, run as: admin system.adapter.smoothed.0 : smoothed : raspberrypi - disabled + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.sourceanalytix.0 : sourceanalytix : raspberrypi - enabled + system.adapter.tado.0 : tado : raspberrypi - enabled + system.adapter.tankerkoenig.1 : tankerkoenig : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tr-064.0 : tr-064 : raspberrypi - enabled + system.adapter.trashschedule.0 : trashschedule : raspberrypi - enabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled + system.adapter.upnp.0 : upnp : raspberrypi - enabled + system.adapter.viessmannapi.0 : viessmannapi : raspberrypi - enabled system.adapter.vw-connect.0 : vw-connect : raspberrypi - disabled + system.adapter.weatherunderground.0 : weatherunderground : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wled.0 : wled : 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.mqtt.0 : mqtt : raspberrypi - enabled, port: 1883, bind: 192.168.178.76 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : raspberrypi - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1885, 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 (default)' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'Beta (latest)' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴────────────────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): Stable (default) Upgrade policy: none Installed ioBroker-Adapters Used repository: Stable (default) Adapter "admin" : 7.7.2 , installed 7.7.2 Adapter "alexa2" : 3.27.3 , installed 3.27.3 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "ble" : 0.14.0 , installed 0.14.1 Adapter "bring" : 1.8.4 , installed 1.8.4 Adapter "chromecast" : 4.0.0 , installed 4.0.0 Adapter "daswetter" : 3.2.3 , installed 3.2.3 Adapter "deconz" : 1.6.4 , installed 1.6.4 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "echarts" : 1.9.2 , installed 1.9.2 Adapter "energiefluss-erweitert": 0.7.7, installed 0.7.7 Adapter "fb-checkpresence": 1.4.0 , installed 1.4.0 Adapter "feiertage" : 1.2.1 , installed 1.2.1 Adapter "firetv" : 2.1.0 , installed 2.1.0 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "fritzdect" : 2.6.2 , installed 2.6.2 Adapter "fullybrowser" : 3.1.2 , installed 3.1.2 Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "homeconnect" : 1.4.3 , installed 1.4.3 Adapter "ical" : 1.16.2 , installed 1.17.0 Adapter "iot" : 3.3.0 , installed 3.3.0 Adapter "jarvis" : 3.1.8 , installed 3.2.0-rc.17 Adapter "javascript" : 8.9.2 , installed 8.9.2 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "meross" : 1.17.0 , installed 1.17.0 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "net-tools" : 1.1.2 , installed 1.1.2 Adapter "nut" : 1.6.0 , installed 1.7.0 Adapter "octoprint" : 5.1.0 , installed 5.1.0 Adapter "parser" : 2.2.4 , installed 2.2.4 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "pollenflug" : 2.0.0 , installed 2.0.0 Adapter "pvforecast" : 5.0.0 , installed 5.0.0 Adapter "rpi2" : 2.4.0 , installed 2.4.0 Adapter "rssfeed" : 3.5.2 , installed 3.5.2 Adapter "shelly" : 10.2.0 , installed 10.2.0 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "smoothed" : 1.4.0 , installed 1.4.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.2.1 , installed 3.3.0 Adapter "tado" : 0.7.10 , installed 0.7.10 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "trashschedule": 3.3.0 , installed 4.0.1 Adapter "tuya" : 3.16.0 , installed 3.17.0 Adapter "tvprogram" : 4.0.0 , installed 4.0.0 Adapter "tvspielfilm" : 2.1.0 , installed 2.1.0 Adapter "upnp" : 1.1.0 , installed 1.1.0 Adapter "viessmannapi" : 2.3.0 , installed 2.4.3 Adapter "virtualpowermeter": 1.5.0, installed 1.5.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "weatherunderground": 3.7.0, installed 3.7.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "whatsapp-cmb" : 0.3.0 , installed 0.3.0 Adapter "wled" : 0.7.2 , installed 0.7.2 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "yahoo-stock-market": 0.0.7, installed 0.0.7 Adapter "zigbee2mqtt" : 3.0.9 , installed 3.0.9 Objects and States Please stand by - This may take a while Objects: 35415 States: 28739 *** OS-Repositories and Updates *** E: The repository 'http://phoscon.de/apt/deconz trixie Release' does not have a Release file. W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details W: http://archive.raspberrypi.org/debian/dists/trixie/InRelease: Policy will reject signature within a year, see --audit for details Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 91258 17755/io.sonoff.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 19573 891/sshd: /usr/sbin tcp 0 0 192.168.178.76:1883 0.0.0.0:* LISTEN 1001 87822 17663/io.mqtt.0 tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 1001 87024 17371/iobroker.js-c tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 1001 88453 17371/iobroker.js-c tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 19949 1352/exim4 tcp6 0 0 :::1984 :::* LISTEN 1000 13187 504/go2rtc_linux_ar tcp6 0 0 :::1886 :::* LISTEN 1001 89807 17633/io.fullybrows tcp6 0 0 :::8400 :::* LISTEN 1001 92482 18141/io.jarvis.0 tcp6 0 0 ::1:25 :::* LISTEN 0 19950 1352/exim4 tcp6 0 0 :::22 :::* LISTEN 0 18521 891/sshd: /usr/sbin tcp6 0 0 :::8555 :::* LISTEN 1000 16273 504/go2rtc_linux_ar tcp6 0 0 :::8554 :::* LISTEN 1000 16269 504/go2rtc_linux_ar tcp6 0 0 :::8087 :::* LISTEN 1001 91021 17904/io.simple-api tcp6 0 0 :::8082 :::* LISTEN 1001 90017 17822/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 88563 17390/io.admin.0 udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 89802 17557/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 89803 17557/io.tuya.0 udp 0 0 0.0.0.0:48504 0.0.0.0:* 108 13132 499/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 16217 631/dhcpcd: [networ udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 90983 18013/io.wled.0 udp 0 0 192.168.178.76:5353 0.0.0.0:* 1001 87603 17487/io.tr-064.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 13130 499/avahi-daemon: r udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 88828 17501/io.shelly.0 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 92353 17866/io.upnp.0 udp 0 0 0.0.0.0:34716 0.0.0.0:* 1001 92187 17866/io.upnp.0 udp6 0 0 :::546 :::* 0 16219 631/dhcpcd: [networ udp6 0 0 :::5353 :::* 108 13131 499/avahi-daemon: r udp6 0 0 :::46913 :::* 108 13133 499/avahi-daemon: r *** Log File - Last 25 Lines *** Aufgabe:working 2025-10-03 20:00:23.965 - warn: javascript.0 (17439) script.js.common.Eqiva.Haustür_abschließen: Steckdose ausgeschalten. Script fertig. 2025-10-03 20:03:33.852 - error: nut.0 (17811) Error happened: Error: connect ECONNREFUSED 192.168.178.76:3493 2025-10-03 20:03:33.856 - error: nut.0 (17811) USV not available - Delay initialization 2025-10-03 20:08:33.857 - error: nut.0 (17811) Error happened: Error: connect ECONNREFUSED 192.168.178.76:3493 2025-10-03 20:08:33.861 - error: nut.0 (17811) USV not available - Delay initialization 2025-10-03 20:13:33.864 - error: nut.0 (17811) Error happened: Error: connect ECONNREFUSED 192.168.178.76:3493 2025-10-03 20:13:33.869 - error: nut.0 (17811) USV not available - Delay initialization 2025-10-03 20:18:33.870 - error: nut.0 (17811) Error happened: Error: connect ECONNREFUSED 192.168.178.76:3493 2025-10-03 20:18:33.927 - error: nut.0 (17811) USV not available - Delay initialization 2025-10-03 20:23:33.928 - error: nut.0 (17811) Error happened: Error: connect ECONNREFUSED 192.168.178.76:3493 2025-10-03 20:23:33.932 - error: nut.0 (17811) USV not available - Delay initialization 2025-10-03 20:25:00.211 - error: tado.0 (30571) AxiosError: Request failed with status code 429 2025-10-03 20:25:00.223 - error: tado.0 (30571) Issue at apiCall for 'get /api/v2/homes/940259/zones/7/state': AxiosError: axiosInstance(getZoneState) failed: Request failed with status code 429 2025-10-03 20:25:00.225 - error: tado.0 (30571) Error in data refresh at step DoZones: AxiosError: axiosInstance(getZoneState) failed: Request failed with status code 429 2025-10-03 20:25:00.254 - error: tado.0 (30571) Disconnected from Tado cloud service ..., retry in 60 seconds ! 2025-10-03 20:26:00.430 - error: tado.0 (30571) AxiosError: Request failed with status code 429 2025-10-03 20:26:00.432 - error: tado.0 (30571) Issue at apiCall for 'get /api/v2/homes/940259/mobileDevices': AxiosError: axiosInstance(getMobileDevices) failed: Request failed with status code 429 2025-10-03 20:26:00.433 - error: tado.0 (30571) Error in data refresh at step DoMobileDevices: AxiosError: axiosInstance(getMobileDevices) failed: Request failed with status code 429 2025-10-03 20:26:00.443 - error: tado.0 (30571) Disconnected from Tado cloud service ..., retry in 120 seconds ! 2025-10-03 20:28:01.487 - error: tado.0 (30571) AxiosError: Request failed with status code 429 2025-10-03 20:28:01.489 - error: tado.0 (30571) Issue at apiCall for 'get /api/v2/homes/940259/mobileDevices': AxiosError: axiosInstance(getMobileDevices) failed: Request failed with status code 429 2025-10-03 20:28:01.490 - error: tado.0 (30571) Error in data refresh at step DoMobileDevices: AxiosError: axiosInstance(getMobileDevices) failed: Request failed with status code 429 2025-10-03 20:28:01.492 - error: tado.0 (30571) Disconnected from Tado cloud service ..., retry in 180 seconds !============ Mark until here for C&P =============
-
Ich brauche bitte ebenfalls eure Hilfe. Mir wird seit Wochen angezeigt, dass es ein Nodejs Update gibt, leider wird es aber nicht aktualisiert. Was mache ich falsch, wenn iob diag, iob fix und iob nodejs-update nichts bringen?
iob nodejs-update
ioBroker nodejs fixer 2025-08-09 Recommended nodejs-version is: 22.20.0 Checking your installation now. Please be patient! Your current setup is: /usr/bin/nodejs v22.15.0 /usr/bin/node v22.15.0 /usr/bin/npm 10.9.2 /usr/bin/npx 10.9.2 /usr/bin/corepack 0.32.0 We found these nodejs versions available for installation: 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 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main armhf Packages Nothing to do - Your installation is using the correct paths. You are running nodejs v22.15.0. Do you want to install recommended version 22.20.0? Press <y> to continue or any other key to quitiob diag gibt aus:
========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: raspberrypi Icon name: computer Kernel: Linux 6.1.21-v8+ Architecture: arm64 OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : aarch64 Userland : 32 bit Systemuptime and Load: 20:26:47 up 5:03, 1 user, load average: 1.47, 1.38, 1.21 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Fri 2025-10-03 20:26:47 CEST Universal time: Fri 2025-10-03 18:26:47 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': iobroker HOME=/home/iobroker SUDO_HOME=/home/pi GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 2.8G 3.9G 14M 1.7G 5.4G Swap: 209M 0B 209M Total: 8.4G 2.8G 4.1G Active iob-Instances: 37 7812 M total memory 2636 M used memory 2538 M active memory 1185 M inactive memory 3728 M free memory 477 M buffer memory 1104 M swap cache 199 M total swap 0 M used swap 199 M free swap *** top - Table Of Processes *** top - 20:26:48 up 5:03, 1 user, load average: 1.47, 1.38, 1.21 Tasks: 201 total, 3 running, 198 sleeping, 0 stopped, 0 zombie %Cpu(s): 27.1 us, 12.5 sy, 0.0 ni, 58.3 id, 0.0 wa, 0.0 hi, 2.1 si, 0.0 st MiB Mem : 7812.3 total, 3727.7 free, 2637.6 used, 1582.4 buff/cache MiB Swap: 200.0 total, 200.0 free, 0.0 used. 5174.7 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** 23 CRITICAL ERRORS DETECTED! Check 'sudo dmesg --level=emerg,alert,crit -T' for details *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 117G 25G 88G 22% / devtmpfs devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 11M 1.6G 1% /run tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock tmpfs tmpfs 3.9G 3.0M 3.9G 1% /tmp /dev/mmcblk0p1 vfat 253M 51M 202M 20% /boot /dev/sda1 vfat 233G 31G 203G 14% /media/usb tmpfs tmpfs 782M 12K 782M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Fri Oct 3 15:22:56 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:D9:04:68 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 #console=ttyS0,115200 console=tty1 root=PARTUUID=cdb3ca5a-02 rootfstype=ext4 fsck.repair=yes rootwait [Fri Oct 3 15:22:57 2025] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Fri Oct 3 15:22:57 2025] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Fri Oct 3 15:23:02 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,flush,errors=remount-ro `-/media/usb /dev/sda1 vfat rw,nosuid,nodev,noexec,relatime,sync,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 7.9G /var/ 4.0G /var/log 3.7G /var/log/journal/3e23e34d17484a28b9473f69f7d9d21c 3.7G /var/log/journal 3.5G /var/cache/apt Archived and active journals take up 3.6G in the file system. /opt/iobroker/backups: 2.6G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 844M /opt/iobroker/iobroker-data/ 519M /opt/iobroker/iobroker-data/files 246M /opt/iobroker/iobroker-data/backup-objects 67M /opt/iobroker/iobroker-data/files/echarts.admin 61M /opt/iobroker/iobroker-data/files/echarts The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 31M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map 26M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.15.0 /usr/bin/node v22.15.0 /usr/bin/npm 10.9.2 /usr/bin/npx 10.9.2 /usr/bin/corepack 0.32.0 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 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/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 = *** 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: 13555) Core adapters versions js-controller: 7.0.7 admin: 7.7.2 javascript: 8.9.2 nodejs modules from github: 12 +-- iobroker.ble@0.14.1 (git+ssh://git@github.com/AlCalzone/ioBroker.ble.git#f0dd1214a8482b2d60cbf48f642e2add12ece177) +-- iobroker.esphome@0.5.0-beta.10 (git+ssh://git@github.com/DrozmotiX/ioBroker.esphome.git#6b97f67d1d1ce6af3a0e598ba77eec8f570a0854) +-- iobroker.ical@1.17.0 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.ical.git#cec92fab5a12b1a00723f397b6f72eba1fa0ab00) +-- iobroker.jarvis@3.2.0-rc.17 (git+ssh://git@github.com/Zefau/ioBroker.jarvis.git#65370bd2ad4617722447bcff04ba4dc6429bed9b) +-- iobroker.keyble@0.1.1 (git+ssh://git@github.com/oyooyo/ioBroker.keyble.git#1a0292db0cc4402582885d6414a5a1bd2af804a3) +-- iobroker.nut@1.7.0 (git+ssh://git@github.com/Apollon77/ioBroker.nut.git#65bbeeb4f8b12938eb4e77af9ee7ef1ecc2cfd39) +-- iobroker.paw@0.3.2 (git+ssh://git@github.com/bondrogeen/ioBroker.paw.git#66372ac89942184fb4022e6838b2d36940ed7711) +-- iobroker.sonoff@3.3.0 (git+ssh://git@github.com/ioBroker/ioBroker.sonoff.git#fa775b5d1170181d1c2055c8537ef5b9103a4f24) +-- iobroker.trashschedule@4.0.1 (git+ssh://git@github.com/klein0r/ioBroker.trashschedule.git#0048391f4ff95ea965c6dede4ca84d53b5462b20) +-- iobroker.tuya@3.17.0 (git+ssh://git@github.com/Apollon77/ioBroker.tuya.git#640df7360a877f37764a31d628e4d6de3ed1f6e3) +-- iobroker.viessmannapi@2.4.3 (git+ssh://git@github.com/TA2k/ioBroker.viessmannapi.git#a45b02bd2888bdc40c7bca9be886c88c95e2e40e) +-- iobroker.vw-connect@0.6.0 (git+ssh://git@github.com/ta2k/ioBroker.vw-connect.git#1bea7002b834d672f998717c2232223d4d1d13af) Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.ble.1 : ble : raspberrypi - enabled + system.adapter.bring.0 : bring : raspberrypi - enabled system.adapter.daswetter.0 : daswetter : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.dwd.0 : dwd : raspberrypi - enabled + system.adapter.echarts.0 : echarts : raspberrypi - enabled system.adapter.feiertage.0 : feiertage : raspberrypi - enabled + system.adapter.fritzdect.0 : fritzdect : raspberrypi - enabled + system.adapter.fullybrowser.0 : fullybrowser : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.homeconnect.0 : homeconnect : raspberrypi - enabled system.adapter.ical.0 : ical : raspberrypi - enabled + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.jarvis.0 : jarvis : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.meross.0 : meross : raspberrypi - enabled + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1883, bind: 192.168.178.76 + system.adapter.nut.0 : nut : raspberrypi - enabled + system.adapter.parser.0 : parser : raspberrypi - enabled + system.adapter.pollenflug.0 : pollenflug : raspberrypi - enabled + system.adapter.pvforecast.0 : pvforecast : raspberrypi - enabled + system.adapter.rpi2.0 : rpi2 : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : raspberrypi - enabled, port: 8087, bind: 0.0.0.0, run as: admin system.adapter.smoothed.0 : smoothed : raspberrypi - disabled + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.sourceanalytix.0 : sourceanalytix : raspberrypi - enabled + system.adapter.tado.0 : tado : raspberrypi - enabled + system.adapter.tankerkoenig.1 : tankerkoenig : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tr-064.0 : tr-064 : raspberrypi - enabled + system.adapter.trashschedule.0 : trashschedule : raspberrypi - enabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled + system.adapter.upnp.0 : upnp : raspberrypi - enabled + system.adapter.viessmannapi.0 : viessmannapi : raspberrypi - enabled system.adapter.vw-connect.0 : vw-connect : raspberrypi - disabled + system.adapter.weatherunderground.0 : weatherunderground : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wled.0 : wled : 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.mqtt.0 : mqtt : raspberrypi - enabled, port: 1883, bind: 192.168.178.76 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : raspberrypi - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1885, 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 (default)' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'Beta (latest)' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴────────────────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): Stable (default) Upgrade policy: none Installed ioBroker-Adapters Used repository: Stable (default) Adapter "admin" : 7.7.2 , installed 7.7.2 Adapter "alexa2" : 3.27.3 , installed 3.27.3 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "ble" : 0.14.0 , installed 0.14.1 Adapter "bring" : 1.8.4 , installed 1.8.4 Adapter "chromecast" : 4.0.0 , installed 4.0.0 Adapter "daswetter" : 3.2.3 , installed 3.2.3 Adapter "deconz" : 1.6.4 , installed 1.6.4 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "echarts" : 1.9.2 , installed 1.9.2 Adapter "energiefluss-erweitert": 0.7.7, installed 0.7.7 Adapter "fb-checkpresence": 1.4.0 , installed 1.4.0 Adapter "feiertage" : 1.2.1 , installed 1.2.1 Adapter "firetv" : 2.1.0 , installed 2.1.0 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "fritzdect" : 2.6.2 , installed 2.6.2 Adapter "fullybrowser" : 3.1.2 , installed 3.1.2 Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "homeconnect" : 1.4.3 , installed 1.4.3 Adapter "ical" : 1.16.2 , installed 1.17.0 Adapter "iot" : 3.3.0 , installed 3.3.0 Adapter "jarvis" : 3.1.8 , installed 3.2.0-rc.17 Adapter "javascript" : 8.9.2 , installed 8.9.2 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "meross" : 1.17.0 , installed 1.17.0 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "net-tools" : 1.1.2 , installed 1.1.2 Adapter "nut" : 1.6.0 , installed 1.7.0 Adapter "octoprint" : 5.1.0 , installed 5.1.0 Adapter "parser" : 2.2.4 , installed 2.2.4 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "pollenflug" : 2.0.0 , installed 2.0.0 Adapter "pvforecast" : 5.0.0 , installed 5.0.0 Adapter "rpi2" : 2.4.0 , installed 2.4.0 Adapter "rssfeed" : 3.5.2 , installed 3.5.2 Adapter "shelly" : 10.2.0 , installed 10.2.0 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "smoothed" : 1.4.0 , installed 1.4.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.2.1 , installed 3.3.0 Adapter "tado" : 0.7.10 , installed 0.7.10 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "trashschedule": 3.3.0 , installed 4.0.1 Adapter "tuya" : 3.16.0 , installed 3.17.0 Adapter "tvprogram" : 4.0.0 , installed 4.0.0 Adapter "tvspielfilm" : 2.1.0 , installed 2.1.0 Adapter "upnp" : 1.1.0 , installed 1.1.0 Adapter "viessmannapi" : 2.3.0 , installed 2.4.3 Adapter "virtualpowermeter": 1.5.0, installed 1.5.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "weatherunderground": 3.7.0, installed 3.7.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "whatsapp-cmb" : 0.3.0 , installed 0.3.0 Adapter "wled" : 0.7.2 , installed 0.7.2 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "yahoo-stock-market": 0.0.7, installed 0.0.7 Adapter "zigbee2mqtt" : 3.0.9 , installed 3.0.9 Objects and States Please stand by - This may take a while Objects: 35415 States: 28739 *** OS-Repositories and Updates *** E: The repository 'http://phoscon.de/apt/deconz trixie Release' does not have a Release file. W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details W: http://archive.raspberrypi.org/debian/dists/trixie/InRelease: Policy will reject signature within a year, see --audit for details Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 91258 17755/io.sonoff.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 19573 891/sshd: /usr/sbin tcp 0 0 192.168.178.76:1883 0.0.0.0:* LISTEN 1001 87822 17663/io.mqtt.0 tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 1001 87024 17371/iobroker.js-c tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 1001 88453 17371/iobroker.js-c tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 19949 1352/exim4 tcp6 0 0 :::1984 :::* LISTEN 1000 13187 504/go2rtc_linux_ar tcp6 0 0 :::1886 :::* LISTEN 1001 89807 17633/io.fullybrows tcp6 0 0 :::8400 :::* LISTEN 1001 92482 18141/io.jarvis.0 tcp6 0 0 ::1:25 :::* LISTEN 0 19950 1352/exim4 tcp6 0 0 :::22 :::* LISTEN 0 18521 891/sshd: /usr/sbin tcp6 0 0 :::8555 :::* LISTEN 1000 16273 504/go2rtc_linux_ar tcp6 0 0 :::8554 :::* LISTEN 1000 16269 504/go2rtc_linux_ar tcp6 0 0 :::8087 :::* LISTEN 1001 91021 17904/io.simple-api tcp6 0 0 :::8082 :::* LISTEN 1001 90017 17822/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 88563 17390/io.admin.0 udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 89802 17557/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 89803 17557/io.tuya.0 udp 0 0 0.0.0.0:48504 0.0.0.0:* 108 13132 499/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 16217 631/dhcpcd: [networ udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 90983 18013/io.wled.0 udp 0 0 192.168.178.76:5353 0.0.0.0:* 1001 87603 17487/io.tr-064.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 13130 499/avahi-daemon: r udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 88828 17501/io.shelly.0 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 92353 17866/io.upnp.0 udp 0 0 0.0.0.0:34716 0.0.0.0:* 1001 92187 17866/io.upnp.0 udp6 0 0 :::546 :::* 0 16219 631/dhcpcd: [networ udp6 0 0 :::5353 :::* 108 13131 499/avahi-daemon: r udp6 0 0 :::46913 :::* 108 13133 499/avahi-daemon: r *** Log File - Last 25 Lines *** Aufgabe:working 2025-10-03 20:00:23.965 - warn: javascript.0 (17439) script.js.common.Eqiva.Haustür_abschließen: Steckdose ausgeschalten. Script fertig. 2025-10-03 20:03:33.852 - error: nut.0 (17811) Error happened: Error: connect ECONNREFUSED 192.168.178.76:3493 2025-10-03 20:03:33.856 - error: nut.0 (17811) USV not available - Delay initialization 2025-10-03 20:08:33.857 - error: nut.0 (17811) Error happened: Error: connect ECONNREFUSED 192.168.178.76:3493 2025-10-03 20:08:33.861 - error: nut.0 (17811) USV not available - Delay initialization 2025-10-03 20:13:33.864 - error: nut.0 (17811) Error happened: Error: connect ECONNREFUSED 192.168.178.76:3493 2025-10-03 20:13:33.869 - error: nut.0 (17811) USV not available - Delay initialization 2025-10-03 20:18:33.870 - error: nut.0 (17811) Error happened: Error: connect ECONNREFUSED 192.168.178.76:3493 2025-10-03 20:18:33.927 - error: nut.0 (17811) USV not available - Delay initialization 2025-10-03 20:23:33.928 - error: nut.0 (17811) Error happened: Error: connect ECONNREFUSED 192.168.178.76:3493 2025-10-03 20:23:33.932 - error: nut.0 (17811) USV not available - Delay initialization 2025-10-03 20:25:00.211 - error: tado.0 (30571) AxiosError: Request failed with status code 429 2025-10-03 20:25:00.223 - error: tado.0 (30571) Issue at apiCall for 'get /api/v2/homes/940259/zones/7/state': AxiosError: axiosInstance(getZoneState) failed: Request failed with status code 429 2025-10-03 20:25:00.225 - error: tado.0 (30571) Error in data refresh at step DoZones: AxiosError: axiosInstance(getZoneState) failed: Request failed with status code 429 2025-10-03 20:25:00.254 - error: tado.0 (30571) Disconnected from Tado cloud service ..., retry in 60 seconds ! 2025-10-03 20:26:00.430 - error: tado.0 (30571) AxiosError: Request failed with status code 429 2025-10-03 20:26:00.432 - error: tado.0 (30571) Issue at apiCall for 'get /api/v2/homes/940259/mobileDevices': AxiosError: axiosInstance(getMobileDevices) failed: Request failed with status code 429 2025-10-03 20:26:00.433 - error: tado.0 (30571) Error in data refresh at step DoMobileDevices: AxiosError: axiosInstance(getMobileDevices) failed: Request failed with status code 429 2025-10-03 20:26:00.443 - error: tado.0 (30571) Disconnected from Tado cloud service ..., retry in 120 seconds ! 2025-10-03 20:28:01.487 - error: tado.0 (30571) AxiosError: Request failed with status code 429 2025-10-03 20:28:01.489 - error: tado.0 (30571) Issue at apiCall for 'get /api/v2/homes/940259/mobileDevices': AxiosError: axiosInstance(getMobileDevices) failed: Request failed with status code 429 2025-10-03 20:28:01.490 - error: tado.0 (30571) Error in data refresh at step DoMobileDevices: AxiosError: axiosInstance(getMobileDevices) failed: Request failed with status code 429 2025-10-03 20:28:01.492 - error: tado.0 (30571) Disconnected from Tado cloud service ..., retry in 180 seconds !============ Mark until here for C&P =============
Dein Betriebssystem ist falsch installiert.
Installier es komplett neu. -
Dein Betriebssystem ist falsch installiert.
Installier es komplett neu. -
@thomas-braun oh, danke. Das ist ja blöd. Es läuft auf dem RPI schon viele Jahre und bisher konnte ich auch alles ohne Probleme updaten. Gibts da noch eine Lösung?
@marc_el_k sagte in Wir empfehlen: Node.js 22.x:
Gibts da noch eine Lösung?
Ja, eine NEUinstallation.
Und das du das seit Jahren mitschleppst sieht man am jetzigen Zustand. Das war mal ein RaspberrOS 10 oder 11 und ist immer auf das nächste Release gehoben worden. Nur funktioniert das nicht in jedem Fall.
In deinem z. B. nicht. -
@marc_el_k sagte in Wir empfehlen: Node.js 22.x:
Gibts da noch eine Lösung?
Ja, eine NEUinstallation.
Und das du das seit Jahren mitschleppst sieht man am jetzigen Zustand. Das war mal ein RaspberrOS 10 oder 11 und ist immer auf das nächste Release gehoben worden. Nur funktioniert das nicht in jedem Fall.
In deinem z. B. nicht.Ich habe gestern Node.js 22 installiert doch leider lief mein Ziggbee2mqtt Adapter der mit einem SLZB-06 über POE angeschlossen ist danach
unzuverlässig und mit ständiger Warnmeldung. Ich musste wieder auf Node.js 20.19 zurück. Danach lief alles wieder wie gehabt. Schade :angry: -
Ich habe gestern Node.js 22 installiert doch leider lief mein Ziggbee2mqtt Adapter der mit einem SLZB-06 über POE angeschlossen ist danach
unzuverlässig und mit ständiger Warnmeldung. Ich musste wieder auf Node.js 20.19 zurück. Danach lief alles wieder wie gehabt. Schade :angry:Leider sagts du nicht was du unter 'lief unzuverlässig' verstehts. Keine Fehlermeldungen oder ähnliches.
Es ist auch nicht wirklich klar ob nun der ioBroker Adapter oder die externe zigbee2mqtt Software Probleme machte.
Nicht böse sein, aber mit den Infos wird niemand eine Fehlereingrenzung oder eine Verbesserung vornehmen können.
-
Leider sagts du nicht was du unter 'lief unzuverlässig' verstehts. Keine Fehlermeldungen oder ähnliches.
Es ist auch nicht wirklich klar ob nun der ioBroker Adapter oder die externe zigbee2mqtt Software Probleme machte.
Nicht böse sein, aber mit den Infos wird niemand eine Fehlereingrenzung oder eine Verbesserung vornehmen können.
@mcm1957 said in Wir empfehlen: Node.js 22.x:
Leider sagts du nicht was du unter 'lief unzuverlässig' verstehts. Keine Fehlermeldungen oder ähnliches.
Es ist auch nicht wirklich klar ob nun der ioBroker Adapter oder die externe zigbee2mqtt Software Probleme machte.
Nicht böse sein, aber mit den Infos wird niemand eine Fehlereingrenzung oder eine Verbesserung vornehmen können.
08:53:38.761 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee2mqtt.0 2025-10-11 08:53:38.761 info terminating zigbee2mqtt.0 2025-10-11 08:53:38.358 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2025-10-11 08:53:38.358 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2025-10-11 08:53:38.323 warn Start try again in 1 seconds... zigbee2mqtt.0 2025-10-11 08:53:38.319 info Got terminate signal TERMINATE_YOURSELF zigbee2mqtt.0 2025-10-11 08:53:16.777 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.456 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.456 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.455 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:13.789 info Connect to Zigbee2MQTT over websocket connection. zigbee2mqtt.0 2025-10-11 08:53:12.786 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.typeIch habe das kopiert deswegen ist das etwas komisch so
-
@mcm1957 said in Wir empfehlen: Node.js 22.x:
Leider sagts du nicht was du unter 'lief unzuverlässig' verstehts. Keine Fehlermeldungen oder ähnliches.
Es ist auch nicht wirklich klar ob nun der ioBroker Adapter oder die externe zigbee2mqtt Software Probleme machte.
Nicht böse sein, aber mit den Infos wird niemand eine Fehlereingrenzung oder eine Verbesserung vornehmen können.
08:53:38.761 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee2mqtt.0 2025-10-11 08:53:38.761 info terminating zigbee2mqtt.0 2025-10-11 08:53:38.358 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2025-10-11 08:53:38.358 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2025-10-11 08:53:38.323 warn Start try again in 1 seconds... zigbee2mqtt.0 2025-10-11 08:53:38.319 info Got terminate signal TERMINATE_YOURSELF zigbee2mqtt.0 2025-10-11 08:53:16.777 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.456 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.456 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.455 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:13.789 info Connect to Zigbee2MQTT over websocket connection. zigbee2mqtt.0 2025-10-11 08:53:12.786 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.typeIch habe das kopiert deswegen ist das etwas komisch so
@biker1602
Danke f.d. Info.Würde das aber eher als Problem des Adapters als als generelles node.js22 Problem sehen.
Bitte mach ein Issue beim Adapter auf oder ein getrenntes Topic und gib dort auch die für eine Analyse notwenigen Infos (z.B. Version des Adapters) an.
@Asgothian FYI falls du mit den derzeitigen Infos schon was anfangen kannst.Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
Support Repositoryverwaltung.Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker
-
@biker1602
Danke f.d. Info.Würde das aber eher als Problem des Adapters als als generelles node.js22 Problem sehen.
Bitte mach ein Issue beim Adapter auf oder ein getrenntes Topic und gib dort auch die für eine Analyse notwenigen Infos (z.B. Version des Adapters) an.
@Asgothian FYI falls du mit den derzeitigen Infos schon was anfangen kannst.@mcm1957 sagte in Wir empfehlen: Node.js 22.x:
Bitte mach ein Issue beim Adapter auf oder ein getrenntes Topic und gib dort auch die für eine Analyse notwenigen Infos (z.B. Version des Adapters) an.
@Asgothian FYI falls du mit den derzeitigen Infos schon was anfangen kannst.Das ist eher @arteck 's Baustelle, sorry. Sieht aber wirklich komisch aus. Hier mal in Lesbar:
08:53:38.761 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee2mqtt.0 2025-10-11 08:53:38.761 info terminating zigbee2mqtt.0 2025-10-11 08:53:38.358 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2025-10-11 08:53:38.358 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2025-10-11 08:53:38.323 warn Start try again in 1 seconds... zigbee2mqtt.0 2025-10-11 08:53:38.319 info Got terminate signal TERMINATE_YOURSELF zigbee2mqtt.0 2025-10-11 08:53:16.777 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.456 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.456 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.455 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:13.789 info Connect to Zigbee2MQTT over websocket connection. zigbee2mqtt.0 2025-10-11 08:53:12.786 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type -
@mcm1957 sagte in Wir empfehlen: Node.js 22.x:
Bitte mach ein Issue beim Adapter auf oder ein getrenntes Topic und gib dort auch die für eine Analyse notwenigen Infos (z.B. Version des Adapters) an.
@Asgothian FYI falls du mit den derzeitigen Infos schon was anfangen kannst.Das ist eher @arteck 's Baustelle, sorry. Sieht aber wirklich komisch aus. Hier mal in Lesbar:
08:53:38.761 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee2mqtt.0 2025-10-11 08:53:38.761 info terminating zigbee2mqtt.0 2025-10-11 08:53:38.358 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2025-10-11 08:53:38.358 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2025-10-11 08:53:38.323 warn Start try again in 1 seconds... zigbee2mqtt.0 2025-10-11 08:53:38.319 info Got terminate signal TERMINATE_YOURSELF zigbee2mqtt.0 2025-10-11 08:53:16.777 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.456 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.456 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.455 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:13.789 info Connect to Zigbee2MQTT over websocket connection. zigbee2mqtt.0 2025-10-11 08:53:12.786 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type@asgothian said in Wir empfehlen: Node.js 22.x:
@mcm1957 sagte in Wir empfehlen: Node.js 22.x:
Bitte mach ein Issue beim Adapter auf oder ein getrenntes Topic und gib dort auch die für eine Analyse notwenigen Infos (z.B. Version des Adapters) an.
@Asgothian FYI falls du mit den derzeitigen Infos schon was anfangen kannst.Das ist eher @arteck 's Baustelle, sorry. Sieht aber wirklich komisch aus. Hier mal in Lesbar:
08:53:38.761 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee2mqtt.0 2025-10-11 08:53:38.761 info terminating zigbee2mqtt.0 2025-10-11 08:53:38.358 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2025-10-11 08:53:38.358 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2025-10-11 08:53:38.323 warn Start try again in 1 seconds... zigbee2mqtt.0 2025-10-11 08:53:38.319 info Got terminate signal TERMINATE_YOURSELF zigbee2mqtt.0 2025-10-11 08:53:16.777 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:16.768 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.456 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.456 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:15.455 debug Device: bridge/definitions not found, queue state in incStatsQueue! zigbee2mqtt.0 2025-10-11 08:53:13.789 info Connect to Zigbee2MQTT over websocket connection. zigbee2mqtt.0 2025-10-11 08:53:12.786 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.typeDas komische war, halt auch das alle Geräte plötzlich für kurze Zeit keine Verbindung mehr hatten und dann wieder ja und das im Wechsel.
-
Hallo zusammen ,
Probiere node js updaten. kommt aber immer folgender fehler.
Was mache ich falsch ?
Danke für die Hilfe
ioBroker nodejs fixer 2025-08-09 You requested to install latest version from nodejs v22 tree. Your current setup is: /usr/bin/nodejs v22.20.0 /usr/local/bin/node v20.16.0 /usr/local/bin/npm 10.8.1 /usr/local/bin/npx 10.8.1 /usr/local/bin/corepack 0.28.2 *** nodejs is NOT correctly installed *** We found these nodejs versions available for installation: nodejs: Installed: 22.20.0-1nodesource1 Candidate: 22.21.0-1nodesource1 Version table: 22.21.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages *** 22.20.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.19.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.18.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.16.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 500 http://deb.debian.org/debian-security bookworm-security/main arm64 P ackages Your nodejs-Installation seems to be faulty. Shall we try to fix it? Press <y> to continue or any other key to quit You are running nodejs v20.16.0. Do you want to install latest version from node js v.22 tree? Press <y> to continue or any other key to quit Not fixing your installation. Exiting. -
Hallo zusammen ,
Probiere node js updaten. kommt aber immer folgender fehler.
Was mache ich falsch ?
Danke für die Hilfe
ioBroker nodejs fixer 2025-08-09 You requested to install latest version from nodejs v22 tree. Your current setup is: /usr/bin/nodejs v22.20.0 /usr/local/bin/node v20.16.0 /usr/local/bin/npm 10.8.1 /usr/local/bin/npx 10.8.1 /usr/local/bin/corepack 0.28.2 *** nodejs is NOT correctly installed *** We found these nodejs versions available for installation: nodejs: Installed: 22.20.0-1nodesource1 Candidate: 22.21.0-1nodesource1 Version table: 22.21.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages *** 22.20.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.19.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.18.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.16.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 500 http://deb.debian.org/debian-security bookworm-security/main arm64 P ackages Your nodejs-Installation seems to be faulty. Shall we try to fix it? Press <y> to continue or any other key to quit You are running nodejs v20.16.0. Do you want to install latest version from node js v.22 tree? Press <y> to continue or any other key to quit Not fixing your installation. Exiting.@schererv sagte in Wir empfehlen: Node.js 22.x:
Was mache ich falsch ?
was machst du überhaupt?
anscheinend verbietest du dem Fixer die fehlerhafte Installation zu fixen.
824
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge