NEWS
Test Adapter Linux Control v1.x.x
Tester
714
Beiträge
73
Kommentatoren
180.4k
Aufrufe
67
Watching
-
@Thomas-Braun sagte in Test Adapter Linux Control v1.x.x:
Mal bestätigt?
Aber natürlich ^^
(ich weiss die Frage musste gestellt werden aber brachte mich trotzdem kurz zum schmunzeln)@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
(ich weiss die Frage musste gestellt werden aber brachte mich trotzdem kurz zum schmunzeln)
Was ich hier schon alles gesehen habe...
Was kommt denn bei dir dabei herum?
cd /home/iobroker || exit sudo -H -u iobroker npm i is-my-node-vulnerable sudo -H -u iobroker npx is-my-node-vulnerable -
Hier die Ausgabe, nur das /home/iobroker bei mir /opt/iobroker sein muss.
cd /opt/iobroker || exit sudo -H -u iobroker npm i is-my-node-vulnerable sudo -H -u iobroker npx is-my-node-vulnerable added 8 packages in 2s 164 packages are looking for funding run `npm fund` for details █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██Ich bin wie ich bin, was anderes bekommt man nicht !!
-
Hier die Ausgabe, nur das /home/iobroker bei mir /opt/iobroker sein muss.
cd /opt/iobroker || exit sudo -H -u iobroker npm i is-my-node-vulnerable sudo -H -u iobroker npx is-my-node-vulnerable added 8 packages in 2s 164 packages are looking for funding run `npm fund` for details █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
das /home/iobroker bei mir /opt/iobroker sein muss.
Warum? Der user iobroker hat eigentlich auch ein home. Das Modul wird bewusst nicht in /opt/iobroker installiert sondern außerhalb des Installationsverzeichnisses.
-
@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
das /home/iobroker bei mir /opt/iobroker sein muss.
Warum? Der user iobroker hat eigentlich auch ein home. Das Modul wird bewusst nicht in /opt/iobroker installiert sondern außerhalb des Installationsverzeichnisses.
@Thomas-Braun sagte in Test Adapter Linux Control v1.x.x:
Warum? Der user iobroker hat eigentlich auch ein home. Das Modul wird bewusst nicht in /opt/iobroker installiert sondern außerhalb des Installationsverzeichnisses.
Ok dann hier im Original ohne Anpassung:
cd /home/iobroker || exit sudo -H -u iobroker npm i is-my-node-vulnerable sudo -H -u iobroker npx is-my-node-vulnerable npm error code EACCES npm error syscall mkdir npm error path /home/iobroker/node_modules npm error errno -13 npm error Error: EACCES: permission denied, mkdir '/home/iobroker/node_modules' npm error at async mkdir (node:internal/fs/promises:860:10) npm error at async /usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:624:20 npm error at async Promise.allSettled (index 0) npm error at async [reifyPackages] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:325:11) npm error at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:142:5) npm error at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:150:5) npm error at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:207:9) npm error at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:74:5) { npm error errno: -13, npm error code: 'EACCES', npm error syscall: 'mkdir', npm error path: '/home/iobroker/node_modules' npm error } npm error npm error The operation was rejected by your operating system. npm error It is likely you do not have the permissions to access this file as the current user npm error npm error If you believe this might be a permissions issue, please double-check the npm error permissions of the file and its containing directories, or try running npm error the command again as root/Administrator. npm error A complete log of this run can be found in: /opt/iobroker/.npm/_logs/2026-01-13T10_24_12_176Z-debug-0.log █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██Ich bin wie ich bin, was anderes bekommt man nicht !!
-
@Thomas-Braun sagte in Test Adapter Linux Control v1.x.x:
Warum? Der user iobroker hat eigentlich auch ein home. Das Modul wird bewusst nicht in /opt/iobroker installiert sondern außerhalb des Installationsverzeichnisses.
Ok dann hier im Original ohne Anpassung:
cd /home/iobroker || exit sudo -H -u iobroker npm i is-my-node-vulnerable sudo -H -u iobroker npx is-my-node-vulnerable npm error code EACCES npm error syscall mkdir npm error path /home/iobroker/node_modules npm error errno -13 npm error Error: EACCES: permission denied, mkdir '/home/iobroker/node_modules' npm error at async mkdir (node:internal/fs/promises:860:10) npm error at async /usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:624:20 npm error at async Promise.allSettled (index 0) npm error at async [reifyPackages] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:325:11) npm error at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:142:5) npm error at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:150:5) npm error at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:207:9) npm error at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:74:5) { npm error errno: -13, npm error code: 'EACCES', npm error syscall: 'mkdir', npm error path: '/home/iobroker/node_modules' npm error } npm error npm error The operation was rejected by your operating system. npm error It is likely you do not have the permissions to access this file as the current user npm error npm error If you believe this might be a permissions issue, please double-check the npm error permissions of the file and its containing directories, or try running npm error the command again as root/Administrator. npm error A complete log of this run can be found in: /opt/iobroker/.npm/_logs/2026-01-13T10_24_12_176Z-debug-0.log █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
npm error code EACCES
dann stimmt bei dir was mit dem user nicht.
Wir hatten gerade einen anderen Fall mit Docker, da lief das Script problemlos durch
kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
npm error code EACCES
dann stimmt bei dir was mit dem user nicht.
Wir hatten gerade einen anderen Fall mit Docker, da lief das Script problemlos durch
@Homoran sagte in Test Adapter Linux Control v1.x.x:
dann stimmt bei dir was mit dem user nicht.
Wir hatten gerade einen anderen Fall mit Docker, da lief das Script problemlos durchDas kann sein aber ich nutze ausschließlich den Docker Container von Buanet.
Änderungen meinerseits hab ich nicht gemacht, ich verlasse mich da ganz auf den Ersteller des Containers und der läuft ja. Ausser der Adapter um den es hier geht, wobei der ja auch läuft nur das er bei einem Neustart den Fehler ins Log schreibt.Ich bin wie ich bin, was anderes bekommt man nicht !!
-
@Homoran sagte in Test Adapter Linux Control v1.x.x:
dann stimmt bei dir was mit dem user nicht.
Wir hatten gerade einen anderen Fall mit Docker, da lief das Script problemlos durchDas kann sein aber ich nutze ausschließlich den Docker Container von Buanet.
Änderungen meinerseits hab ich nicht gemacht, ich verlasse mich da ganz auf den Ersteller des Containers und der läuft ja. Ausser der Adapter um den es hier geht, wobei der ja auch läuft nur das er bei einem Neustart den Fehler ins Log schreibt.@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
ich nutze ausschließlich den Docker Container von Buanet.
das ist bei allen Dockern usern so (fast ausschließlich zumindest)
-
@Thomas-Braun sagte in Test Adapter Linux Control v1.x.x:
Warum? Der user iobroker hat eigentlich auch ein home. Das Modul wird bewusst nicht in /opt/iobroker installiert sondern außerhalb des Installationsverzeichnisses.
Ok dann hier im Original ohne Anpassung:
cd /home/iobroker || exit sudo -H -u iobroker npm i is-my-node-vulnerable sudo -H -u iobroker npx is-my-node-vulnerable npm error code EACCES npm error syscall mkdir npm error path /home/iobroker/node_modules npm error errno -13 npm error Error: EACCES: permission denied, mkdir '/home/iobroker/node_modules' npm error at async mkdir (node:internal/fs/promises:860:10) npm error at async /usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:624:20 npm error at async Promise.allSettled (index 0) npm error at async [reifyPackages] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:325:11) npm error at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:142:5) npm error at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:150:5) npm error at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:207:9) npm error at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:74:5) { npm error errno: -13, npm error code: 'EACCES', npm error syscall: 'mkdir', npm error path: '/home/iobroker/node_modules' npm error } npm error npm error The operation was rejected by your operating system. npm error It is likely you do not have the permissions to access this file as the current user npm error npm error If you believe this might be a permissions issue, please double-check the npm error permissions of the file and its containing directories, or try running npm error the command again as root/Administrator. npm error A complete log of this run can be found in: /opt/iobroker/.npm/_logs/2026-01-13T10_24_12_176Z-debug-0.log █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██Welcher user macht den Aufruf?
Und in welchen Gruppen ist dieser user enthalten?
Wie sehen die Rechte anls -lAh /home/aus?
Keine Ahnung, ob der Docker-Container an der Stelle anders aufgesetzt wurde, grundsätzlich funktioniert 'iob diag' aber in einem üblichen Docker-Setup. -
Der Aufruf erfolgt über: docker exec -it iobroker bash was dann so aussieht:
root@Odin:/opt/iobroker#Dann der Befehl und das Ergebniss:
root@Odin:/opt/iobroker# ls -lAh /home/ total 0 drwxr-xr-x 1 1000 1000 70 Jan 12 20:54 iobroker root@Odin:/opt/iobroker#Wie gesagt zu dem Aufbau des Docker-Containers kann ich nichts sagen, ist der schon genannte.
Ich bin wie ich bin, was anderes bekommt man nicht !!
-
Der Aufruf erfolgt über: docker exec -it iobroker bash was dann so aussieht:
root@Odin:/opt/iobroker#Dann der Befehl und das Ergebniss:
root@Odin:/opt/iobroker# ls -lAh /home/ total 0 drwxr-xr-x 1 1000 1000 70 Jan 12 20:54 iobroker root@Odin:/opt/iobroker#Wie gesagt zu dem Aufbau des Docker-Containers kann ich nichts sagen, ist der schon genannte.
Da ist doch das home des 'iobroker'.
Keine Ahnung warum das bei dir nicht so funktioniert wie in den anderen Dockern. -
@thomas-braun
ich habe mal das Script aus deiner Signatur ausprobiert (curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh) und das Ergebniss sieht man hier:========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Hardware Vendor : Micro-Star International Co., Ltd Kernel : x86_64 Userland : 64 bit Docker : v11.0.0 Virtualization : docker Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 12:40:13 up 8 days, 17:44, 0 user, load average: 1.26, 1.38, 1.34 CPU threads: 12 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** TIME AND TIMEZONES *** Tue Jan 13 11:40:13 UTC 2026 Tue Jan 13 12:40:13 CET 2026 CET +0100 Etc/UTC *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker HOME=/opt/iobroker GROUPS=users tty dialout audio video plugdev *** DISPLAY-SERVER SETUP *** Display-Server: false System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down Display-Manager: Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 29G 15G 416M 2.3G 15G 13G Swap: 0B 0B 0B Total: 29G 15G 416M Active iob-Instances: 23 27968 M total memory 14802 M used memory 15167 M active memory 10392 M inactive memory 397 M free memory 0 M buffer memory 15219 M swap cache 0 M total swap 0 M used swap 0 M free swap *** top - Table Of Processes *** top - 12:40:13 up 8 days, 17:45, 0 user, load average: 1.26, 1.38, 1.34 Tasks: 29 total, 1 running, 28 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 27968.4 total, 397.1 free, 14802.3 used, 15219.9 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 13166.1 avail Mem *** DMESG CRITICAL ERRORS *** dmesg: read kernel buffer failed: Operation not permitted No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p1 btrfs 932G 351G 567G 39% / tmpfs tmpfs 64M 0 64M 0% /dev shm tmpfs 64M 0 64M 0% /dev/shm /dev/nvme0n1p1 btrfs 932G 351G 567G 39% /opt/iobroker /dev/md3p1 xfs 2.8T 1.1T 1.8T 37% /opt/iobroker/backups tmpfs tmpfs 14G 0 14G 0% /proc/acpi tmpfs tmpfs 14G 0 14G 0% /sys/firmware tmpfs tmpfs 14G 0 14G 0% /sys/devices/virtual/powercap Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/nvme0n1p1[/appdata/docker/docker/btrfs/subvolumes/0ac7ae18a35cd26f43a67b63e17fd433dd434f4edfc9ecc1fee56aa6a727b86b] btrfs rw,noat |-/opt/userscripts | /dev/nvme0n1p1[/appdata/iobroker/scripts] btrfs rw,noat |-/opt/iobroker | /dev/nvme0n1p1[/appdata/iobroker/data] btrfs rw,noat | `-/opt/iobroker/backups | /dev/md3p1[/Server-Backup/iobroker] xfs rw,noat |-/etc/resolv.conf | /dev/nvme0n1p1[/appdata/docker/docker/containers/43a4efcdf9735a215297032e411bba77a9cb460b0d487fc6db042afb3d9c716a/resolv.conf] | btrfs rw,noat |-/etc/hostname | /dev/nvme0n1p1[/appdata/docker/docker/containers/43a4efcdf9735a215297032e411bba77a9cb460b0d487fc6db042afb3d9c716a/hostname] | btrfs rw,noat `-/etc/hosts /dev/nvme0n1p1[/appdata/docker/docker/containers/43a4efcdf9735a215297032e411bba77a9cb460b0d487fc6db042afb3d9c716a/hosts] btrfs rw,noat Files in neuralgic directories: /var: 35M /var/ 33M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 14M /var/lib/dpkg /opt/iobroker/backups: 5.5G /opt/iobroker/backups/ 3.3G /opt/iobroker/backups/2025-Backups 1.5G /opt/iobroker/backups/2026-Januar 4.0K /opt/iobroker/backups/.stfolder /opt/iobroker/iobroker-data: 4.2G /opt/iobroker/iobroker-data/ 3.4G /opt/iobroker/iobroker-data/history 640M /opt/iobroker/iobroker-data/backup-objects 122M /opt/iobroker/iobroker-data/files 47M /opt/iobroker/iobroker-data/files/admin.admin The five largest files in iobroker-data are: 48M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/backup-objects/2026-01-13_12-14_objects.jsonl.gz 27M /opt/iobroker/iobroker-data/backup-objects/2026-01-13_10-14_objects.jsonl.gz 27M /opt/iobroker/iobroker-data/backup-objects/2026-01-13_08-14_objects.jsonl.gz 27M /opt/iobroker/iobroker-data/backup-objects/2026-01-13_04-13_objects.jsonl.gz 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.21.0 /usr/bin/node v22.21.0 /usr/bin/npm 10.9.4 /usr/bin/npx 10.9.4 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.21.0-1nodesource1 Candidate: 22.21.0-1nodesource1 Version table: *** 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: Odin Odin (version: 7.0.7, hostname: Odin , alive, uptime: 23131) Core adapters versions js-controller: 7.0.7 admin: 7.7.19 javascript: 9.0.11 nodejs modules from github: 2 +-- iobroker.nebenkosten-monitor@1.3.5 (git+ssh://git@github.com/fischi87/ioBroker.nebenkosten-monitor.git#6d2aa917c772506c0ce5be8fb1d2dce3d59254c2) +-- iobroker.sourceanalytix@0.4.15-alpha.1 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.sourceanalytix.git#fd3b7f9f362a348741cbe18d70a130d2bfee6727) Adapter State + system.adapter.admin.0 : admin : Odin - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : Odin - enabled + system.adapter.backitup.0 : backitup : Odin - enabled system.adapter.device-reminder.0 : device-reminder : Odin - disabled + system.adapter.discovery.0 : discovery : Odin - enabled + system.adapter.history.0 : history : Odin - enabled + system.adapter.influxdb.0 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.1 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.2 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.3 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.4 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.5 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.6 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.7 : influxdb : Odin - enabled, port: 8086 + system.adapter.javascript.0 : javascript : Odin - enabled + system.adapter.linux-control.0 : linux-control : Odin - enabled + system.adapter.nebenkosten-monitor.0 : nebenkosten-monitor : Odin - enabled + system.adapter.pirate-weather.0 : pirate-weather : Odin - enabled + system.adapter.shelly.0 : shelly : Odin - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : Odin - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : Odin - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.sourceanalytix.0 : sourceanalytix : Odin - enabled system.adapter.telegram.0 : telegram : Odin - disabled, port: 8443, bind: 0.0.0.0 system.adapter.web.0 : web : Odin - disabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.whatsapp-cmb.0 : whatsapp-cmb : Odin - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : Odin - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.1 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.2 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.3 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.4 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.5 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.6 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.7 : influxdb : Odin - enabled, port: 8086 + system.adapter.shelly.0 : shelly : Odin - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : Odin - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : Odin - enabled, port: 1883, bind: 0.0.0.0 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.7.19 , installed 7.7.19 Adapter "alexa2" : 3.27.4 , installed 3.27.4 Adapter "backitup" : 3.3.13 , installed 3.3.13 Adapter "device-reminder": 3.1.2 , installed 3.1.2 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "javascript" : 9.0.11 , installed 9.0.11 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "linux-control": 1.1.5 , installed 1.1.5 Adapter "pirate-weather": 0.8.0 , installed 0.8.0 Adapter "shelly" : 10.4.1 , installed 10.4.1 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.2.1 , installed 3.2.1 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "whatsapp-cmb" : 0.3.0 , installed 0.3.0 Adapter "ws" : 2.6.2 , installed 2.6.2 Objects and States Please stand by - This may take a while Objects: 6579 States: 6176 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 https://repos.influxdata.com/debian stable InRelease Hit:4 http://deb.debian.org/debian-security bookworm-security InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Done Pending Updates: 41 *** 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:3000 0.0.0.0:* LISTEN 0 1901499105 - tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 0 1901512963 - tcp 0 0 0.0.0.0:3333 0.0.0.0:* LISTEN 0 1901428797 - tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 0 1901893145 - tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 0 1901893144 - tcp 0 0 0.0.0.0:20211 0.0.0.0:* LISTEN 20211 90440 - tcp 0 0 0.0.0.0:20212 0.0.0.0:* LISTEN 20211 119413 - tcp 0 0 0.0.0.0:4040 0.0.0.0:* LISTEN 0 80056 - tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 41297 - tcp 0 0 0.0.0.0:49517 0.0.0.0:* LISTEN 32 33308 - tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 0 80114 - tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 99 1901945074 - tcp 0 0 0.0.0.0:1888 0.0.0.0:* LISTEN 99 1901933537 - tcp 0 0 0.0.0.0:7634 0.0.0.0:* LISTEN 0 1901887528 - tcp 0 0 127.0.0.1:443 0.0.0.0:* LISTEN 0 23972 - tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 0 4519 - tcp 0 0 0.0.0.0:7878 0.0.0.0:* LISTEN 0 1901311380 - tcp 0 0 127.0.0.1:16509 0.0.0.0:* LISTEN 0 84317 - tcp 0 0 127.0.0.1:80 0.0.0.0:* LISTEN 0 23970 - tcp 0 0 0.0.0.0:8088 0.0.0.0:* LISTEN 0 1901810497 - tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN 0 1901816074 - tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 0 1901892215 - tcp 0 0 0.0.0.0:8086 0.0.0.0:* LISTEN 0 1901810494 - tcp 0 0 0.0.0.0:8074 0.0.0.0:* LISTEN 0 1901879426 - tcp 0 0 0.0.0.0:8073 0.0.0.0:* LISTEN 0 1901873765 - tcp 0 0 0.0.0.0:8072 0.0.0.0:* LISTEN 0 1901877377 - tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 0 4520 - tcp 0 0 0.0.0.0:8191 0.0.0.0:* LISTEN 0 1901299071 - tcp 0 0 0.0.0.0:37361 0.0.0.0:* LISTEN 0 123277 - tcp 0 0 0.0.0.0:5055 0.0.0.0:* LISTEN 0 1901385399 - tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 0 1901893151 - tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 0 1901893150 - tcp 0 0 0.0.0.0:5432 0.0.0.0:* LISTEN 0 1901423247 - tcp 0 0 0.0.0.0:5800 0.0.0.0:* LISTEN 99 1901879756 - tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 99 1901874471 - tcp 0 0 127.0.0.1:2049 0.0.0.0:* LISTEN 0 126346 - tcp 0 0 0.0.0.0:43363 0.0.0.0:* LISTEN 0 123309 - tcp 0 0 0.0.0.0:44835 0.0.0.0:* LISTEN 0 123204 - tcp 0 0 0.0.0.0:8192 0.0.0.0:* LISTEN 0 1901296062 - tcp 0 0 0.0.0.0:8666 0.0.0.0:* LISTEN 0 1901809079 - tcp 0 0 0.0.0.0:8686 0.0.0.0:* LISTEN 0 1901297198 - tcp 0 0 0.0.0.0:8765 0.0.0.0:* LISTEN 0 1901878464 - tcp 0 0 0.0.0.0:8989 0.0.0.0:* LISTEN 0 1901294199 - tcp 0 0 0.0.0.0:9090 0.0.0.0:* LISTEN 0 1901885772 - tcp 0 0 0.0.0.0:42283 0.0.0.0:* LISTEN 0 123293 - tcp 0 0 0.0.0.0:9705 0.0.0.0:* LISTEN 0 1901356900 - tcp 0 0 0.0.0.0:9696 0.0.0.0:* LISTEN 0 1901356111 - tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 99 1901886699 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 99 1901886694 - tcp 0 0 192.168.0.60:22 0.0.0.0:* LISTEN 0 259 - tcp 0 0 192.168.0.60:80 0.0.0.0:* LISTEN 0 23971 - tcp 0 0 192.168.0.60:139 0.0.0.0:* LISTEN 0 4522 - tcp 0 0 192.168.0.60:443 0.0.0.0:* LISTEN 0 23973 - tcp 0 0 192.168.0.60:445 0.0.0.0:* LISTEN 0 4521 - tcp 0 0 192.168.0.60:2049 0.0.0.0:* LISTEN 0 126331 - tcp6 0 0 :::3000 :::* LISTEN 0 1901505032 - tcp6 0 0 :::3306 :::* LISTEN 0 1901490001 - tcp6 0 0 :::3333 :::* LISTEN 0 1901421084 - tcp6 0 0 :::4040 :::* LISTEN 0 62252 - tcp6 0 0 :::111 :::* LISTEN 0 41301 - tcp6 0 0 :::33163 :::* LISTEN 32 33314 - tcp6 0 0 :::33953 :::* LISTEN 0 123206 - tcp6 0 0 :::7878 :::* LISTEN 0 1901344007 - tcp6 0 0 :::8088 :::* LISTEN 0 1901817072 - tcp6 0 0 :::8083 :::* LISTEN 0 1901816079 - tcp6 0 0 :::8081 :::* LISTEN 99 1901890266 - tcp6 0 0 :::8080 :::* LISTEN 0 1901880195 - tcp6 0 0 :::8086 :::* LISTEN 0 1901816082 - tcp6 0 0 :::8074 :::* LISTEN 0 1901880383 - tcp6 0 0 :::8073 :::* LISTEN 0 1901865752 - tcp6 0 0 :::8072 :::* LISTEN 0 1901873756 - tcp6 0 0 :::8096 :::* LISTEN 2 1901505881 - tcp6 0 0 :::8191 :::* LISTEN 0 1901303139 - tcp6 0 0 :::5055 :::* LISTEN 0 1901421869 - tcp6 0 0 :::5432 :::* LISTEN 0 1901423252 - tcp6 0 0 :::38271 :::* LISTEN 0 123317 - tcp6 0 0 ::1:9666 :::* LISTEN 99 1901883564 - tcp6 0 0 :::5800 :::* LISTEN 99 1901879757 - tcp6 0 0 :::5900 :::* LISTEN 99 1901874472 - tcp6 0 0 :::8192 :::* LISTEN 0 1901300620 - tcp6 0 0 :::8666 :::* LISTEN 0 1901763435 - tcp6 0 0 :::8686 :::* LISTEN 0 1901292370 - tcp6 0 0 :::8765 :::* LISTEN 0 1901876568 - tcp6 0 0 :::8989 :::* LISTEN 0 1901335552 - tcp6 0 0 :::9100 :::* LISTEN 0 28877 - tcp6 0 0 :::9090 :::* LISTEN 0 1901888603 - tcp6 0 0 :::9705 :::* LISTEN 0 1901353537 - tcp6 0 0 :::9696 :::* LISTEN 0 1901350776 - tcp6 0 0 127.0.0.1:9666 :::* LISTEN 99 1901883563 - tcp6 0 0 127.0.0.1:9665 :::* LISTEN 99 1901878132 - tcp6 0 0 :::47875 :::* LISTEN 0 123285 - tcp6 0 0 :::45245 :::* LISTEN 0 123301 - udp 0 0 0.0.0.0:64470 0.0.0.0:* 0 41295 - udp 0 0 192.168.122.1:53 0.0.0.0:* 0 80113 - udp 0 0 0.0.0.0:67 0.0.0.0:* 0 80110 - udp 0 0 192.168.0.60:111 0.0.0.0:* 0 41294 - udp 0 0 127.0.0.1:111 0.0.0.0:* 0 41293 - udp 0 0 192.168.0.60:123 0.0.0.0:* 44 64291 - udp 0 0 127.0.0.1:123 0.0.0.0:* 0 6358 - udp 0 0 192.168.0.60:137 0.0.0.0:* 0 9540 - udp 0 0 0.0.0.0:137 0.0.0.0:* 0 9528 - udp 0 0 192.168.0.60:138 0.0.0.0:* 0 9541 - udp 0 0 0.0.0.0:138 0.0.0.0:* 0 9529 - udp 0 0 0.0.0.0:161 0.0.0.0:* 0 29054 - udp 0 0 127.0.0.1:768 0.0.0.0:* 0 33300 - udp 0 0 0.0.0.0:50739 0.0.0.0:* 0 123203 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 2 1901511752 - udp 0 0 127.0.0.1:2049 0.0.0.0:* 0 126347 - udp 0 0 192.168.0.60:2049 0.0.0.0:* 0 126345 - udp 0 0 0.0.0.0:3702 0.0.0.0:* 0 1901893143 - udp 0 0 0.0.0.0:3702 0.0.0.0:* 0 1901893141 - udp 0 0 0.0.0.0:53703 0.0.0.0:* 0 123273 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 61 4507 - udp 0 0 0.0.0.0:5355 0.0.0.0:* 0 1901893149 - udp 0 0 0.0.0.0:5355 0.0.0.0:* 0 1901893147 - udp 0 0 0.0.0.0:5683 0.0.0.0:* 99 1901943017 - udp 0 0 0.0.0.0:55039 0.0.0.0:* 0 123289 - udp 0 0 0.0.0.0:38712 0.0.0.0:* 2 1901511753 - udp 0 0 0.0.0.0:39495 0.0.0.0:* 32 33305 - udp 0 0 0.0.0.0:57063 0.0.0.0:* 0 66665 - udp 0 0 0.0.0.0:57934 0.0.0.0:* 0 123305 - udp 0 0 0.0.0.0:59085 0.0.0.0:* 61 4508 - udp 0 0 192.168.0.60:43253 0.0.0.0:* 2 1901511754 - udp 0 0 127.0.0.1:60511 0.0.0.0:* 2 1901511755 - udp 0 0 192.168.0.60:45542 0.0.0.0:* 0 24034 - udp6 0 0 :::63538 :::* 0 41300 - udp6 0 0 ::1:111 :::* 0 41298 - udp6 0 0 :::52657 :::* 0 123297 - udp6 0 0 :::36464 :::* 0 123281 - udp6 0 0 :::53036 :::* 0 123205 - udp6 0 0 :::55493 :::* 0 123313 - udp6 0 0 :::56257 :::* 32 33311 - udp6 0 0 :::7359 :::* 2 1901503302 - *** Log File - Last 25 Lines *** 2026-01-13 12:30:00.002 - info: javascript.0 (307) script.js.common.Shelly_COAP: Shelly Verbrauch: Verbrauchswerte aktualisiert: 2 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-01-13 12:30:00.004 - info: javascript.0 (307) script.js.common.Tasmo_Sono_Kosten: Sonoff/Tasmota Kosten: Verwende Strompreis von 0.3159 €/kWh für diese Berechnung. 2026-01-13 12:30:00.005 - info: javascript.0 (307) script.js.common.Tasmo_Sono_Kosten: Sonoff/Tasmota Kosten: Update abgeschlossen. Geräte mit Verbrauch: 3 | Reboots erkannt: 0 | Fehler: 0 2026-01-13 12:30:00.010 - info: javascript.0 (307) script.js.common.Shelly_MQTT: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-01-13 12:30:57.312 - info: linux-control.0 (693) successful received data from RPi-HA (192.168.0.11:22) 2026-01-13 12:31:13.962 - info: linux-control.0 (693) getting data from Pihole2 (192.168.0.6:22) 2026-01-13 12:31:23.817 - info: linux-control.0 (693) getting data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:31:35.373 - info: linux-control.0 (693) successful received data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:31:40.379 - info: linux-control.0 (693) successful received data from Pihole2 (192.168.0.6:22) 2026-01-13 12:32:34.402 - info: linux-control.0 (693) getting data from Pihole1 (192.168.0.3:22) 2026-01-13 12:32:44.027 - info: linux-control.0 (693) successful received data from Pihole1 (192.168.0.3:22) 2026-01-13 12:34:35.374 - info: linux-control.0 (693) getting data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:34:45.048 - info: linux-control.0 (693) successful received data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:35:57.313 - info: linux-control.0 (693) getting data from RPi-HA (192.168.0.11:22) 2026-01-13 12:36:02.319 - error: linux-control.0 (693) [getConnection] Could not establish a connection to 'RPi-HA' (192.168.0.11:22)! 2026-01-13 12:36:02.319 - error: linux-control.0 (693) [getConnection] error: Timed out while waiting for handshake, stack: Error: Timed out while waiting for handshake at Timeout._onTimeout (/opt/iobroker/node_modules/ssh2/lib/client.js:1114:23) at listOnTimeout (node:internal/timers:588:17) at process.processTimers (node:internal/timers:523:7) 2026-01-13 12:36:40.380 - info: linux-control.0 (693) getting data from Pihole2 (192.168.0.6:22) 2026-01-13 12:37:07.329 - info: linux-control.0 (693) successful received data from Pihole2 (192.168.0.6:22) 2026-01-13 12:37:44.028 - info: linux-control.0 (693) getting data from Pihole1 (192.168.0.3:22) 2026-01-13 12:37:45.047 - info: linux-control.0 (693) getting data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:37:53.486 - info: linux-control.0 (693) successful received data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:37:53.687 - info: linux-control.0 (693) successful received data from Pihole1 (192.168.0.3:22) ============ Mark until here for C&P ============= iob diag has finished.Vielleicht hilft das ja weiter.
Ich bin wie ich bin, was anderes bekommt man nicht !!
-
@thomas-braun
ich habe mal das Script aus deiner Signatur ausprobiert (curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh) und das Ergebniss sieht man hier:========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Hardware Vendor : Micro-Star International Co., Ltd Kernel : x86_64 Userland : 64 bit Docker : v11.0.0 Virtualization : docker Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 12:40:13 up 8 days, 17:44, 0 user, load average: 1.26, 1.38, 1.34 CPU threads: 12 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** TIME AND TIMEZONES *** Tue Jan 13 11:40:13 UTC 2026 Tue Jan 13 12:40:13 CET 2026 CET +0100 Etc/UTC *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker HOME=/opt/iobroker GROUPS=users tty dialout audio video plugdev *** DISPLAY-SERVER SETUP *** Display-Server: false System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down Display-Manager: Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 29G 15G 416M 2.3G 15G 13G Swap: 0B 0B 0B Total: 29G 15G 416M Active iob-Instances: 23 27968 M total memory 14802 M used memory 15167 M active memory 10392 M inactive memory 397 M free memory 0 M buffer memory 15219 M swap cache 0 M total swap 0 M used swap 0 M free swap *** top - Table Of Processes *** top - 12:40:13 up 8 days, 17:45, 0 user, load average: 1.26, 1.38, 1.34 Tasks: 29 total, 1 running, 28 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 27968.4 total, 397.1 free, 14802.3 used, 15219.9 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 13166.1 avail Mem *** DMESG CRITICAL ERRORS *** dmesg: read kernel buffer failed: Operation not permitted No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p1 btrfs 932G 351G 567G 39% / tmpfs tmpfs 64M 0 64M 0% /dev shm tmpfs 64M 0 64M 0% /dev/shm /dev/nvme0n1p1 btrfs 932G 351G 567G 39% /opt/iobroker /dev/md3p1 xfs 2.8T 1.1T 1.8T 37% /opt/iobroker/backups tmpfs tmpfs 14G 0 14G 0% /proc/acpi tmpfs tmpfs 14G 0 14G 0% /sys/firmware tmpfs tmpfs 14G 0 14G 0% /sys/devices/virtual/powercap Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/nvme0n1p1[/appdata/docker/docker/btrfs/subvolumes/0ac7ae18a35cd26f43a67b63e17fd433dd434f4edfc9ecc1fee56aa6a727b86b] btrfs rw,noat |-/opt/userscripts | /dev/nvme0n1p1[/appdata/iobroker/scripts] btrfs rw,noat |-/opt/iobroker | /dev/nvme0n1p1[/appdata/iobroker/data] btrfs rw,noat | `-/opt/iobroker/backups | /dev/md3p1[/Server-Backup/iobroker] xfs rw,noat |-/etc/resolv.conf | /dev/nvme0n1p1[/appdata/docker/docker/containers/43a4efcdf9735a215297032e411bba77a9cb460b0d487fc6db042afb3d9c716a/resolv.conf] | btrfs rw,noat |-/etc/hostname | /dev/nvme0n1p1[/appdata/docker/docker/containers/43a4efcdf9735a215297032e411bba77a9cb460b0d487fc6db042afb3d9c716a/hostname] | btrfs rw,noat `-/etc/hosts /dev/nvme0n1p1[/appdata/docker/docker/containers/43a4efcdf9735a215297032e411bba77a9cb460b0d487fc6db042afb3d9c716a/hosts] btrfs rw,noat Files in neuralgic directories: /var: 35M /var/ 33M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 14M /var/lib/dpkg /opt/iobroker/backups: 5.5G /opt/iobroker/backups/ 3.3G /opt/iobroker/backups/2025-Backups 1.5G /opt/iobroker/backups/2026-Januar 4.0K /opt/iobroker/backups/.stfolder /opt/iobroker/iobroker-data: 4.2G /opt/iobroker/iobroker-data/ 3.4G /opt/iobroker/iobroker-data/history 640M /opt/iobroker/iobroker-data/backup-objects 122M /opt/iobroker/iobroker-data/files 47M /opt/iobroker/iobroker-data/files/admin.admin The five largest files in iobroker-data are: 48M /opt/iobroker/iobroker-data/objects.jsonl 27M /opt/iobroker/iobroker-data/backup-objects/2026-01-13_12-14_objects.jsonl.gz 27M /opt/iobroker/iobroker-data/backup-objects/2026-01-13_10-14_objects.jsonl.gz 27M /opt/iobroker/iobroker-data/backup-objects/2026-01-13_08-14_objects.jsonl.gz 27M /opt/iobroker/iobroker-data/backup-objects/2026-01-13_04-13_objects.jsonl.gz 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.21.0 /usr/bin/node v22.21.0 /usr/bin/npm 10.9.4 /usr/bin/npx 10.9.4 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.21.0-1nodesource1 Candidate: 22.21.0-1nodesource1 Version table: *** 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: Odin Odin (version: 7.0.7, hostname: Odin , alive, uptime: 23131) Core adapters versions js-controller: 7.0.7 admin: 7.7.19 javascript: 9.0.11 nodejs modules from github: 2 +-- iobroker.nebenkosten-monitor@1.3.5 (git+ssh://git@github.com/fischi87/ioBroker.nebenkosten-monitor.git#6d2aa917c772506c0ce5be8fb1d2dce3d59254c2) +-- iobroker.sourceanalytix@0.4.15-alpha.1 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.sourceanalytix.git#fd3b7f9f362a348741cbe18d70a130d2bfee6727) Adapter State + system.adapter.admin.0 : admin : Odin - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : Odin - enabled + system.adapter.backitup.0 : backitup : Odin - enabled system.adapter.device-reminder.0 : device-reminder : Odin - disabled + system.adapter.discovery.0 : discovery : Odin - enabled + system.adapter.history.0 : history : Odin - enabled + system.adapter.influxdb.0 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.1 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.2 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.3 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.4 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.5 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.6 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.7 : influxdb : Odin - enabled, port: 8086 + system.adapter.javascript.0 : javascript : Odin - enabled + system.adapter.linux-control.0 : linux-control : Odin - enabled + system.adapter.nebenkosten-monitor.0 : nebenkosten-monitor : Odin - enabled + system.adapter.pirate-weather.0 : pirate-weather : Odin - enabled + system.adapter.shelly.0 : shelly : Odin - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : Odin - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : Odin - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.sourceanalytix.0 : sourceanalytix : Odin - enabled system.adapter.telegram.0 : telegram : Odin - disabled, port: 8443, bind: 0.0.0.0 system.adapter.web.0 : web : Odin - disabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.whatsapp-cmb.0 : whatsapp-cmb : Odin - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : Odin - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.1 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.2 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.3 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.4 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.5 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.6 : influxdb : Odin - enabled, port: 8086 + system.adapter.influxdb.7 : influxdb : Odin - enabled, port: 8086 + system.adapter.shelly.0 : shelly : Odin - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : Odin - enabled, port: 1888, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : Odin - enabled, port: 1883, bind: 0.0.0.0 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.7.19 , installed 7.7.19 Adapter "alexa2" : 3.27.4 , installed 3.27.4 Adapter "backitup" : 3.3.13 , installed 3.3.13 Adapter "device-reminder": 3.1.2 , installed 3.1.2 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "javascript" : 9.0.11 , installed 9.0.11 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "linux-control": 1.1.5 , installed 1.1.5 Adapter "pirate-weather": 0.8.0 , installed 0.8.0 Adapter "shelly" : 10.4.1 , installed 10.4.1 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.2.1 , installed 3.2.1 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "whatsapp-cmb" : 0.3.0 , installed 0.3.0 Adapter "ws" : 2.6.2 , installed 2.6.2 Objects and States Please stand by - This may take a while Objects: 6579 States: 6176 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 https://repos.influxdata.com/debian stable InRelease Hit:4 http://deb.debian.org/debian-security bookworm-security InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Done Pending Updates: 41 *** 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:3000 0.0.0.0:* LISTEN 0 1901499105 - tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 0 1901512963 - tcp 0 0 0.0.0.0:3333 0.0.0.0:* LISTEN 0 1901428797 - tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 0 1901893145 - tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 0 1901893144 - tcp 0 0 0.0.0.0:20211 0.0.0.0:* LISTEN 20211 90440 - tcp 0 0 0.0.0.0:20212 0.0.0.0:* LISTEN 20211 119413 - tcp 0 0 0.0.0.0:4040 0.0.0.0:* LISTEN 0 80056 - tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 41297 - tcp 0 0 0.0.0.0:49517 0.0.0.0:* LISTEN 32 33308 - tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 0 80114 - tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 99 1901945074 - tcp 0 0 0.0.0.0:1888 0.0.0.0:* LISTEN 99 1901933537 - tcp 0 0 0.0.0.0:7634 0.0.0.0:* LISTEN 0 1901887528 - tcp 0 0 127.0.0.1:443 0.0.0.0:* LISTEN 0 23972 - tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 0 4519 - tcp 0 0 0.0.0.0:7878 0.0.0.0:* LISTEN 0 1901311380 - tcp 0 0 127.0.0.1:16509 0.0.0.0:* LISTEN 0 84317 - tcp 0 0 127.0.0.1:80 0.0.0.0:* LISTEN 0 23970 - tcp 0 0 0.0.0.0:8088 0.0.0.0:* LISTEN 0 1901810497 - tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN 0 1901816074 - tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 0 1901892215 - tcp 0 0 0.0.0.0:8086 0.0.0.0:* LISTEN 0 1901810494 - tcp 0 0 0.0.0.0:8074 0.0.0.0:* LISTEN 0 1901879426 - tcp 0 0 0.0.0.0:8073 0.0.0.0:* LISTEN 0 1901873765 - tcp 0 0 0.0.0.0:8072 0.0.0.0:* LISTEN 0 1901877377 - tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 0 4520 - tcp 0 0 0.0.0.0:8191 0.0.0.0:* LISTEN 0 1901299071 - tcp 0 0 0.0.0.0:37361 0.0.0.0:* LISTEN 0 123277 - tcp 0 0 0.0.0.0:5055 0.0.0.0:* LISTEN 0 1901385399 - tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 0 1901893151 - tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 0 1901893150 - tcp 0 0 0.0.0.0:5432 0.0.0.0:* LISTEN 0 1901423247 - tcp 0 0 0.0.0.0:5800 0.0.0.0:* LISTEN 99 1901879756 - tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 99 1901874471 - tcp 0 0 127.0.0.1:2049 0.0.0.0:* LISTEN 0 126346 - tcp 0 0 0.0.0.0:43363 0.0.0.0:* LISTEN 0 123309 - tcp 0 0 0.0.0.0:44835 0.0.0.0:* LISTEN 0 123204 - tcp 0 0 0.0.0.0:8192 0.0.0.0:* LISTEN 0 1901296062 - tcp 0 0 0.0.0.0:8666 0.0.0.0:* LISTEN 0 1901809079 - tcp 0 0 0.0.0.0:8686 0.0.0.0:* LISTEN 0 1901297198 - tcp 0 0 0.0.0.0:8765 0.0.0.0:* LISTEN 0 1901878464 - tcp 0 0 0.0.0.0:8989 0.0.0.0:* LISTEN 0 1901294199 - tcp 0 0 0.0.0.0:9090 0.0.0.0:* LISTEN 0 1901885772 - tcp 0 0 0.0.0.0:42283 0.0.0.0:* LISTEN 0 123293 - tcp 0 0 0.0.0.0:9705 0.0.0.0:* LISTEN 0 1901356900 - tcp 0 0 0.0.0.0:9696 0.0.0.0:* LISTEN 0 1901356111 - tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 99 1901886699 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 99 1901886694 - tcp 0 0 192.168.0.60:22 0.0.0.0:* LISTEN 0 259 - tcp 0 0 192.168.0.60:80 0.0.0.0:* LISTEN 0 23971 - tcp 0 0 192.168.0.60:139 0.0.0.0:* LISTEN 0 4522 - tcp 0 0 192.168.0.60:443 0.0.0.0:* LISTEN 0 23973 - tcp 0 0 192.168.0.60:445 0.0.0.0:* LISTEN 0 4521 - tcp 0 0 192.168.0.60:2049 0.0.0.0:* LISTEN 0 126331 - tcp6 0 0 :::3000 :::* LISTEN 0 1901505032 - tcp6 0 0 :::3306 :::* LISTEN 0 1901490001 - tcp6 0 0 :::3333 :::* LISTEN 0 1901421084 - tcp6 0 0 :::4040 :::* LISTEN 0 62252 - tcp6 0 0 :::111 :::* LISTEN 0 41301 - tcp6 0 0 :::33163 :::* LISTEN 32 33314 - tcp6 0 0 :::33953 :::* LISTEN 0 123206 - tcp6 0 0 :::7878 :::* LISTEN 0 1901344007 - tcp6 0 0 :::8088 :::* LISTEN 0 1901817072 - tcp6 0 0 :::8083 :::* LISTEN 0 1901816079 - tcp6 0 0 :::8081 :::* LISTEN 99 1901890266 - tcp6 0 0 :::8080 :::* LISTEN 0 1901880195 - tcp6 0 0 :::8086 :::* LISTEN 0 1901816082 - tcp6 0 0 :::8074 :::* LISTEN 0 1901880383 - tcp6 0 0 :::8073 :::* LISTEN 0 1901865752 - tcp6 0 0 :::8072 :::* LISTEN 0 1901873756 - tcp6 0 0 :::8096 :::* LISTEN 2 1901505881 - tcp6 0 0 :::8191 :::* LISTEN 0 1901303139 - tcp6 0 0 :::5055 :::* LISTEN 0 1901421869 - tcp6 0 0 :::5432 :::* LISTEN 0 1901423252 - tcp6 0 0 :::38271 :::* LISTEN 0 123317 - tcp6 0 0 ::1:9666 :::* LISTEN 99 1901883564 - tcp6 0 0 :::5800 :::* LISTEN 99 1901879757 - tcp6 0 0 :::5900 :::* LISTEN 99 1901874472 - tcp6 0 0 :::8192 :::* LISTEN 0 1901300620 - tcp6 0 0 :::8666 :::* LISTEN 0 1901763435 - tcp6 0 0 :::8686 :::* LISTEN 0 1901292370 - tcp6 0 0 :::8765 :::* LISTEN 0 1901876568 - tcp6 0 0 :::8989 :::* LISTEN 0 1901335552 - tcp6 0 0 :::9100 :::* LISTEN 0 28877 - tcp6 0 0 :::9090 :::* LISTEN 0 1901888603 - tcp6 0 0 :::9705 :::* LISTEN 0 1901353537 - tcp6 0 0 :::9696 :::* LISTEN 0 1901350776 - tcp6 0 0 127.0.0.1:9666 :::* LISTEN 99 1901883563 - tcp6 0 0 127.0.0.1:9665 :::* LISTEN 99 1901878132 - tcp6 0 0 :::47875 :::* LISTEN 0 123285 - tcp6 0 0 :::45245 :::* LISTEN 0 123301 - udp 0 0 0.0.0.0:64470 0.0.0.0:* 0 41295 - udp 0 0 192.168.122.1:53 0.0.0.0:* 0 80113 - udp 0 0 0.0.0.0:67 0.0.0.0:* 0 80110 - udp 0 0 192.168.0.60:111 0.0.0.0:* 0 41294 - udp 0 0 127.0.0.1:111 0.0.0.0:* 0 41293 - udp 0 0 192.168.0.60:123 0.0.0.0:* 44 64291 - udp 0 0 127.0.0.1:123 0.0.0.0:* 0 6358 - udp 0 0 192.168.0.60:137 0.0.0.0:* 0 9540 - udp 0 0 0.0.0.0:137 0.0.0.0:* 0 9528 - udp 0 0 192.168.0.60:138 0.0.0.0:* 0 9541 - udp 0 0 0.0.0.0:138 0.0.0.0:* 0 9529 - udp 0 0 0.0.0.0:161 0.0.0.0:* 0 29054 - udp 0 0 127.0.0.1:768 0.0.0.0:* 0 33300 - udp 0 0 0.0.0.0:50739 0.0.0.0:* 0 123203 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 2 1901511752 - udp 0 0 127.0.0.1:2049 0.0.0.0:* 0 126347 - udp 0 0 192.168.0.60:2049 0.0.0.0:* 0 126345 - udp 0 0 0.0.0.0:3702 0.0.0.0:* 0 1901893143 - udp 0 0 0.0.0.0:3702 0.0.0.0:* 0 1901893141 - udp 0 0 0.0.0.0:53703 0.0.0.0:* 0 123273 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 61 4507 - udp 0 0 0.0.0.0:5355 0.0.0.0:* 0 1901893149 - udp 0 0 0.0.0.0:5355 0.0.0.0:* 0 1901893147 - udp 0 0 0.0.0.0:5683 0.0.0.0:* 99 1901943017 - udp 0 0 0.0.0.0:55039 0.0.0.0:* 0 123289 - udp 0 0 0.0.0.0:38712 0.0.0.0:* 2 1901511753 - udp 0 0 0.0.0.0:39495 0.0.0.0:* 32 33305 - udp 0 0 0.0.0.0:57063 0.0.0.0:* 0 66665 - udp 0 0 0.0.0.0:57934 0.0.0.0:* 0 123305 - udp 0 0 0.0.0.0:59085 0.0.0.0:* 61 4508 - udp 0 0 192.168.0.60:43253 0.0.0.0:* 2 1901511754 - udp 0 0 127.0.0.1:60511 0.0.0.0:* 2 1901511755 - udp 0 0 192.168.0.60:45542 0.0.0.0:* 0 24034 - udp6 0 0 :::63538 :::* 0 41300 - udp6 0 0 ::1:111 :::* 0 41298 - udp6 0 0 :::52657 :::* 0 123297 - udp6 0 0 :::36464 :::* 0 123281 - udp6 0 0 :::53036 :::* 0 123205 - udp6 0 0 :::55493 :::* 0 123313 - udp6 0 0 :::56257 :::* 32 33311 - udp6 0 0 :::7359 :::* 2 1901503302 - *** Log File - Last 25 Lines *** 2026-01-13 12:30:00.002 - info: javascript.0 (307) script.js.common.Shelly_COAP: Shelly Verbrauch: Verbrauchswerte aktualisiert: 2 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-01-13 12:30:00.004 - info: javascript.0 (307) script.js.common.Tasmo_Sono_Kosten: Sonoff/Tasmota Kosten: Verwende Strompreis von 0.3159 €/kWh für diese Berechnung. 2026-01-13 12:30:00.005 - info: javascript.0 (307) script.js.common.Tasmo_Sono_Kosten: Sonoff/Tasmota Kosten: Update abgeschlossen. Geräte mit Verbrauch: 3 | Reboots erkannt: 0 | Fehler: 0 2026-01-13 12:30:00.010 - info: javascript.0 (307) script.js.common.Shelly_MQTT: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-01-13 12:30:57.312 - info: linux-control.0 (693) successful received data from RPi-HA (192.168.0.11:22) 2026-01-13 12:31:13.962 - info: linux-control.0 (693) getting data from Pihole2 (192.168.0.6:22) 2026-01-13 12:31:23.817 - info: linux-control.0 (693) getting data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:31:35.373 - info: linux-control.0 (693) successful received data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:31:40.379 - info: linux-control.0 (693) successful received data from Pihole2 (192.168.0.6:22) 2026-01-13 12:32:34.402 - info: linux-control.0 (693) getting data from Pihole1 (192.168.0.3:22) 2026-01-13 12:32:44.027 - info: linux-control.0 (693) successful received data from Pihole1 (192.168.0.3:22) 2026-01-13 12:34:35.374 - info: linux-control.0 (693) getting data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:34:45.048 - info: linux-control.0 (693) successful received data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:35:57.313 - info: linux-control.0 (693) getting data from RPi-HA (192.168.0.11:22) 2026-01-13 12:36:02.319 - error: linux-control.0 (693) [getConnection] Could not establish a connection to 'RPi-HA' (192.168.0.11:22)! 2026-01-13 12:36:02.319 - error: linux-control.0 (693) [getConnection] error: Timed out while waiting for handshake, stack: Error: Timed out while waiting for handshake at Timeout._onTimeout (/opt/iobroker/node_modules/ssh2/lib/client.js:1114:23) at listOnTimeout (node:internal/timers:588:17) at process.processTimers (node:internal/timers:523:7) 2026-01-13 12:36:40.380 - info: linux-control.0 (693) getting data from Pihole2 (192.168.0.6:22) 2026-01-13 12:37:07.329 - info: linux-control.0 (693) successful received data from Pihole2 (192.168.0.6:22) 2026-01-13 12:37:44.028 - info: linux-control.0 (693) getting data from Pihole1 (192.168.0.3:22) 2026-01-13 12:37:45.047 - info: linux-control.0 (693) getting data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:37:53.486 - info: linux-control.0 (693) successful received data from RPi-KUE (192.168.0.10:22) 2026-01-13 12:37:53.687 - info: linux-control.0 (693) successful received data from Pihole1 (192.168.0.3:22) ============ Mark until here for C&P ============= iob diag has finished.Vielleicht hilft das ja weiter.
@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
Vielleicht hilft das ja weiter.
dein Problem müsste hier zu suchen sein
@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
2026-01-13 12:36:02.319 - error: linux-control.0 (693) [getConnection] Could not establish a connection to 'RPi-HA' (192.168.0.11:22)!
2026-01-13 12:36kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
Vielleicht hilft das ja weiter.
dein Problem müsste hier zu suchen sein
@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
2026-01-13 12:36:02.319 - error: linux-control.0 (693) [getConnection] Could not establish a connection to 'RPi-HA' (192.168.0.11:22)!
2026-01-13 12:36@Homoran sagte in Test Adapter Linux Control v1.x.x:
dein Problem müsste hier zu suchen sein
error: linux-control.0 (693) [getConnection] Could not establish a connection to 'RPi->HA' (192.168.0.11:22)!
2026-01-13 12:36Das kam daher das ich gleichzeitig den RPi, der da auftaucht, geupdatet sowie ein Reboot gemacht habe (was ich immer mache nach Updates) und er deshalb nicht erreichbar war. Kann mir also nicht Vorstellen das es daran liegen sollte.
Ich bin wie ich bin, was anderes bekommt man nicht !!
-
@Homoran sagte in Test Adapter Linux Control v1.x.x:
dein Problem müsste hier zu suchen sein
error: linux-control.0 (693) [getConnection] Could not establish a connection to 'RPi->HA' (192.168.0.11:22)!
2026-01-13 12:36Das kam daher das ich gleichzeitig den RPi, der da auftaucht, geupdatet sowie ein Reboot gemacht habe (was ich immer mache nach Updates) und er deshalb nicht erreichbar war. Kann mir also nicht Vorstellen das es daran liegen sollte.
@RoddiEF und was läuft jetzt nicht?
Alle anderen Einträge im log sehen doch gut aus.kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@Homoran sagte in Test Adapter Linux Control v1.x.x:
@RoddiEF und was läuft jetzt nicht?
Alle anderen Einträge im log sehen doch gut aus.Im Kern des ganzen ging es darum das der Adapter einen Fehler ins Log schreibt wenn er gestartet wird.
Daten liefert er ja, aber jeden Morgen (nach dem Backup vom ioBroker) bringt er den Fehler und das macht mich kirre im Kopf.Edit: bild hinzugefügt
Ich bin wie ich bin, was anderes bekommt man nicht !!
-
@Homoran sagte in Test Adapter Linux Control v1.x.x:
@RoddiEF und was läuft jetzt nicht?
Alle anderen Einträge im log sehen doch gut aus.Im Kern des ganzen ging es darum das der Adapter einen Fehler ins Log schreibt wenn er gestartet wird.
Daten liefert er ja, aber jeden Morgen (nach dem Backup vom ioBroker) bringt er den Fehler und das macht mich kirre im Kopf.Edit: bild hinzugefügt
@RoddiEF sagte in Test Adapter Linux Control v1.x.x:
das der Adapter einen Fehler ins Log schreibt wenn er gestartet wird.
wenn das alles ist, kannst du das ignorieren
-
Hat zu meinem Problem niemand eine Idee? 😕
https://forum.iobroker.net/post/1316457
sagte in Test Adapter Linux Control v1.x.x:
Ich hab da auch mal ne Frage. Ich hab jetzt einen Raspi3 eingebunden, auf welchem 2 Kameras (Garten u. Hof) auf einem USB-Stick Bilder ablegen. Beide Ordner enthalten aktuell jeweils >20GB Daten. Wieso wird das nicht korrekt dargestellt? Hat da jemand eine Idee? Die Anzahl der Dateien hingegen stimmt.
-
Hat zu meinem Problem niemand eine Idee? 😕
https://forum.iobroker.net/post/1316457
sagte in Test Adapter Linux Control v1.x.x:
Ich hab da auch mal ne Frage. Ich hab jetzt einen Raspi3 eingebunden, auf welchem 2 Kameras (Garten u. Hof) auf einem USB-Stick Bilder ablegen. Beide Ordner enthalten aktuell jeweils >20GB Daten. Wieso wird das nicht korrekt dargestellt? Hat da jemand eine Idee? Die Anzahl der Dateien hingegen stimmt.
@1Topf sagte in Test Adapter Linux Control v1.x.x:
auf einem USB-Stick Bilder ablegen. Beide Ordner enthalten aktuell jeweils >20GB Daten
und wie sind die jeweils ins System eingebunden?
umgestiegen von Proxmox auf Unraid
-
@1Topf sagte in Test Adapter Linux Control v1.x.x:
auf einem USB-Stick Bilder ablegen. Beide Ordner enthalten aktuell jeweils >20GB Daten
und wie sind die jeweils ins System eingebunden?
@crunchip sagte in Test Adapter Linux Control v1.x.x:
und wie sind die jeweils ins System eingebunden?
Tja, mal kurz überlegen (is schon ne Weile her ...).
Auf dem Raspi3 läuftDebian GNU/Linux 12 (bookworm), raspios ohne GUI. Die Bilder werden von den Kameras per FTP auf den Raspi geschickt.
Der Stick ist normal 🤷♂️ eingebunden:Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/sda1 __ 58G __ 50G _ 8,3G _ 86% _ /media/usbstickDie beiden Ordner liegen unter /media/usbstick/Garten bzw. .../Hof.
Oder welche Info genau hättest Du gern?
-
@D3ltoroxp die Frage ist eher, was da genau läuft auf deinen Systemen. Hat ja nichts mit den Befehlen zu tun.
@crunchip sagte in Test Adapter Linux Control v1.x.x:
@D3ltoroxp die Frage ist eher, was da genau läuft auf deinen Systemen. Hat ja nichts mit den Befehlen zu tun.
Also das ist einmal nen LXC mit Mainsail / Klipper drauf und einmal ein PVE Host. Die beiden habe ich angelegt. Daraus erstellt er dann die DP's. Das ding lief auch schon mal. Ich befürchte seit irgendeinem Update läuft das bei mir nicht mehr richtig.
Wenn ich ihn starte dreht die Log komplett durch.
host.iobroker 2026-01-13 21:50:47.913 error instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:105:5) host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[9]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27) host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[9]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[9]: Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[9]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[8]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[8]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[8]: ReplyError: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[7]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[6]: at processTicksAndRejections (node:internal/process/task_queues:105:5) host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[6]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27) host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[6]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[6]: Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern host.iobroker 2026-01-13 21:50:47.913 error Caught by controller[5]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[4]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[4]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[4]: ReplyError: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:105:5) host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[2]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27) host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[2]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[2]: Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[1]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[1]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[1]: ReplyError: Error The pattern "linux-control.0.Mainsail.services.●.restart" is not a valid ID pattern host.iobroker 2026-01-13 21:50:47.912 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: linux-control.0 2026-01-13 21:50:47.810 info terminating linux-control.0 2026-01-13 21:50:47.810 info terminating linux-control.0 2026-01-13 21:50:47.782 warn Used invalid characters: linux-control.0.Mainsail.services.●.stop changed to linux-control.0.Mainsail.services._.stop linux-control.0 2026-01-13 21:50:47.781 error Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27) at processTicksAndRejections (node:internal/process/task_queues:105:5) linux-control.0 2026-01-13 21:50:47.780 error unhandled promise rejection: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern linux-control.0 2026-01-13 21:50:47.780 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). linux-control.0 2026-01-13 21:50:47.779 warn Used invalid characters: linux-control.0.Mainsail.services.●.start changed to linux-control.0.Mainsail.services._.start linux-control.0 2026-01-13 21:50:47.778 warn Used invalid characters: linux-control.0.Mainsail.services.●.restart changed to linux-control.0.Mainsail.services._.restart linux-control.0 2026-01-13 21:50:47.736 warn State "linux-control.0.Mainsail.services.●.description" has no existing object, this might lead to an error in future versions linux-control.0 2026-01-13 21:50:47.734 warn Used invalid characters: linux-control.0.Mainsail.services.●.description changed to linux-control.0.Mainsail.services._.description linux-control.0 2026-01-13 21:50:47.687 warn State "linux-control.0.Mainsail.services.●.running" has no existing object, this might lead to an error in future versions linux-control.0 2026-01-13 21:50:47.686 warn Used invalid characters: linux-control.0.Mainsail.services.●.running changed to linux-control.0.Mainsail.services._.running linux-control.0 2026-01-13 21:50:47.642 warn State "linux-control.0.Mainsail.services.●.active" has no existing object, this might lead to an error in future versions linux-control.0 2026-01-13 21:50:47.638 warn Used invalid characters: linux-control.0.Mainsail.services.●.active changed to linux-control.0.Mainsail.services._.active linux-control.0 2026-01-13 21:50:47.593 warn State "linux-control.0.Mainsail.services.●.load" has no existing object, this might lead to an error in future versions linux-control.0 2026-01-13 21:50:47.591 warn Used invalid characters: linux-control.0.Mainsail.services.●.load changed to linux-control.0.Mainsail.services._.load linux-control.0 2026-01-13 21:50:47.589 error ReplyError: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) linux-control.0 2026-01-13 21:50:47.589 error unhandled promise rejection: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern linux-control.0 2026-01-13 21:50:47.589 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). host.iobroker 2026-01-13 21:50:47.588 warn host.iobroker-Server States 127.0.0.1:44596 Error from InMemDB: Error: The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:323:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:240:14) at RedisHandler.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:380:26) at RedisHandler.emit (node:events:519:28) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:485:21) at process.callbackTrampoline (node:internal/async_hooks:130:17) linux-control.0 2026-01-13 21:50:47.587 warn Used invalid characters: linux-control.0.Mainsail.services.●.stop changed to linux-control.0.Mainsail.services._.stop linux-control.0 2026-01-13 21:50:47.585 error Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27) at processTicksAndRejections (node:internal/process/task_queues:105:5) linux-control.0 2026-01-13 21:50:47.584 error unhandled promise rejection: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern linux-control.0 2026-01-13 21:50:47.584 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). linux-control.0 2026-01-13 21:50:47.583 warn Used invalid characters: linux-control.0.Mainsail.services.●.start changed to linux-control.0.Mainsail.services._.start linux-control.0 2026-01-13 21:50:47.582 warn Used invalid characters: linux-control.0.Mainsail.services.●.restart changed to linux-control.0.Mainsail.services._.restart linux-control.0 2026-01-13 21:50:47.539 warn State "linux-control.0.Mainsail.services.●.description" has no existing object, this might lead to an error in future versions linux-control.0 2026-01-13 21:50:47.538 warn Used invalid characters: linux-control.0.Mainsail.services.●.description changed to linux-control.0.Mainsail.services._.description linux-control.0 2026-01-13 21:50:47.492 warn State "linux-control.0.Mainsail.services.●.running" has no existing object, this might lead to an error in future versions linux-control.0 2026-01-13 21:50:47.490 warn Used invalid characters: linux-control.0.Mainsail.services.●.running changed to linux-control.0.Mainsail.services._.running linux-control.0 2026-01-13 21:50:47.443 warn State "linux-control.0.Mainsail.services.●.active" has no existing object, this might lead to an error in future versions linux-control.0 2026-01-13 21:50:47.442 warn Used invalid characters: linux-control.0.Mainsail.services.●.active changed to linux-control.0.Mainsail.services._.active linux-control.0 2026-01-13 21:50:47.399 warn State "linux-control.0.Mainsail.services.●.load" has no existing object, this might lead to an error in future versions linux-control.0 2026-01-13 21:50:47.398 warn Used invalid characters: linux-control.0.Mainsail.services.●.load changed to linux-control.0.Mainsail.services._.load linux-control.0 2026-01-13 21:50:47.396 error ReplyError: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) linux-control.0 2026-01-13 21:50:47.396 error unhandled promise rejection: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern linux-control.0 2026-01-13 21:50:47.395 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). host.iobroker 2026-01-13 21:50:47.395 warn host.iobroker-Server States 127.0.0.1:44596 Error from InMemDB: Error: The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:323:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:240:14) at RedisHandler.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:380:26) at RedisHandler.emit (node:events:519:28) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:485:21) at process.callbackTrampoline (node:internal/async_hooks:130:17) linux-control.0 2026-01-13 21:50:47.390 warn Used invalid characters: linux-control.0.Mainsail.services.●.stop changed to linux-control.0.Mainsail.services._.stop linux-control.0 2026-01-13 21:50:47.389 error Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27) at processTicksAndRejections (node:internal/process/task_queues:105:5) linux-control.0 2026-01-13 21:50:47.338 error unhandled promise rejection: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern linux-control.0 2026-01-13 21:50:47.338 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). linux-control.0 2026-01-13 21:50:47.310 warn Used invalid characters: linux-control.0.Mainsail.services.●.start changed to linux-control.0.Mainsail.services._.start linux-control.0 2026-01-13 21:50:47.309 warn Terminated (UNCAUGHT_EXCEPTION): Without reasonDas ist aktiv.
Support us
400
Online32.6k
Benutzer82.0k
Themen1.3m
Beiträge