Probleme mit dem Device-Watcher
ioBroker Allgemein
24
Beiträge
3
Kommentatoren
205
Aufrufe
5
Watching
-
So, jetzt aber los:
Temporär im Device Watcher HS100 und shelly aktiviert. Shelly gibt gerade Ruhe, HS100 hyperaktiv :-)
Log:
026-03-18 17:05:07.765 - info: device-watcher.0 (99890) terminating 2026-03-18 17:05:07.767 - info: device-watcher.0 (99890) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2026-03-18 17:05:07.820 - info: host.iobroker stopInstance system.adapter.device-watcher.0 send kill signal 2026-03-18 17:05:08.269 - info: device-watcher.0 (99890) terminating 2026-03-18 17:05:08.350 - info: host.iobroker instance system.adapter.device-watcher.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2026-03-18 17:05:11.957 - info: host.iobroker instance system.adapter.device-watcher.0 in version "2.15.5" started with pid 117883 2026-03-18 17:05:14.718 - info: device-watcher.0 (117883) starting. Version 2.15.5 in /opt/iobroker/node_modules/iobroker.device-watcher, node: v22.22.1, js-controller: 7.0.7 2026-03-18 17:05:14.748 - info: device-watcher.0 (117883) Number of selected adapters to monitor devices: 7. Loading data from: fritzdectDevices, fullyMQTTDevices, hamDevices, hs100Devices, shellyDevices, sonoffDevices, tapoDevices ... 2026-03-18 17:05:59.484 - info: device-watcher.0 (117883) Das folgende Gerät ist nicht mehr erreichbar: hs100: HS100-1 (2 Minuten) 2026-03-18 17:05:59.553 - info: email.0 (1002) Send email: {"sendTo":"iob@xyz.de","text":"Das folgende Gerät ist nicht mehr erreichbar: \nhs100: HS100-1 (2 Minuten)","subject":"Status Devices","from":"iob@xyz.de","to":"sys@xyz.de"} 2026-03-18 17:05:59.901 - info: email.0 (1002) sent to sys@xyz.de 2026-03-18 17:05:59.924 - info: device-watcher.0 (117883) Das folgende Gerät ist nicht mehr erreichbar: hs100: HS100-2 (2 Minuten) 2026-03-18 17:05:59.985 - info: email.0 (1002) Send email: {"sendTo":"iob@xyz.de","text":"Das folgende Gerät ist nicht mehr erreichbar: \nhs100: HS100-2 (2 Minuten)","subject":"Status Devices","from":"iob@xyz.de","to":"sys@xyz.de"} 2026-03-18 17:06:00.468 - info: email.0 (1002) sent to sys@xyz.de 2026-03-18 17:07:01.866 - info: device-watcher.0 (117883) Das folgende Gerät ist wieder verfügbar: hs100: HS100-1 (0 Minuten) 2026-03-18 17:07:01.960 - info: email.0 (1002) Send email: {"sendTo":"iob@xyz.de","text":"Das folgende Gerät ist wieder verfügbar: \nhs100: HS100-1 (0 Minuten)","subject":"Status Devices","from":"iob@xyz.de","to":"sys@xyz.de"} 2026-03-18 17:07:02.429 - info: email.0 (1002) sent to sys@xyz.de 2026-03-18 17:07:02.444 - info: device-watcher.0 (117883) Das folgende Gerät ist wieder verfügbar: hs100: HS100-2 (0 Minuten) 2026-03-18 17:07:02.496 - info: email.0 (1002) Send email: {"sendTo":"iob@xyz.de","text":"Das folgende Gerät ist wieder verfügbar: \nhs100: HS100-2 (0 Minuten)","subject":"Status Devices","from":"iob@xyz.de","to":"sys@xyz.de"} 2026-03-18 17:07:03.007 - info: email.0 (1002) sent to sys@xyz.de 2026-03-18 17:09:05.549 - info: device-watcher.0 (117883) Das folgende Gerät ist nicht mehr erreichbar: hs100: HS100-1 (2 Minuten) 2026-03-18 17:09:05.599 - info: email.0 (1002) Send email: {"sendTo":"iob@xyz.de","text":"Das folgende Gerät ist nicht mehr erreichbar: \nhs100: HS100-1 (2 Minuten)","subject":"Status Devices","from":"iob@xyz.de","to":"sys@xyz.de"} 2026-03-18 17:09:05.984 - info: email.0 (1002) sent to sys@xyz.de 2026-03-18 17:09:05.999 - info: device-watcher.0 (117883) Das folgende Gerät ist nicht mehr erreichbar: hs100: HS100-2 (2 Minuten) 2026-03-18 17:09:06.051 - info: email.0 (1002) Send email: {"sendTo":"iob@xyz.de","text":"Das folgende Gerät ist nicht mehr erreichbar: \nhs100: HS100-2 (2 Minuten)","subject":"Status Devices","from":"iob@xyz.de","to":"sys@xyz.de"} 2026-03-18 17:09:06.470 - info: email.0 (1002) sent to sys@xyz.de 2026-03-18 17:10:08.767 - info: device-watcher.0 (117883) Das folgende Gerät ist wieder verfügbar: hs100: HS100-1 (0 Minuten) 2026-03-18 17:10:08.819 - info: email.0 (1002) Send email: {"sendTo":"iob@xyz.de","text":"Das folgende Gerät ist wieder verfügbar: \nhs100: HS100-1 (0 Minuten)","subject":"Status Devices","from":"iob@xyz.de","to":"sys@xyz.de"} 2026-03-18 17:10:09.093 - info: email.0 (1002) sent to sys@xyz.de 2026-03-18 17:10:09.108 - info: device-watcher.0 (117883) Das folgende Gerät ist wieder verfügbar: hs100: HS100-2 (0 Minuten) 2026-03-18 17:10:09.160 - info: email.0 (1002) Send email: {"sendTo":"iob@xyz.de","text":"Das folgende Gerät ist wieder verfügbar: \nhs100: HS100-2 (0 Minuten)","subject":"Status Devices","from":"iob@xyz.de","to":"sys@xyz.de"} 2026-03-18 17:10:09.518 - info: email.0 (1002) sent to sys@xyz.de 2026-03-18 17:11:51.632 - info: device-watcher.0 (117883) Das folgende Gerät ist nicht mehr erreichbar: hs100: HS100-1 (2 Minuten) 2026-03-18 17:11:51.687 - info: email.0 (1002) Send email: {"sendTo":"iob@xyz.de","text":"Das folgende Gerät ist nicht mehr erreichbar: \nhs100: HS100-1 (2 Minuten)","subject":"Status Devices","from":"iob@xyz.de","to":"sys@xyz.de"} 2026-03-18 17:11:52.001 - info: email.0 (1002) sent to sys@xyz.de 2026-03-18 17:11:52.032 - info: device-watcher.0 (117883) Das folgende Gerät ist nicht mehr eLetzte größere Änderung:
# 18.03.2026 - OS-Update --------------------------------- - 10 Pakete # 16.03.2026 - Update Adapter + Image ------------------------------------------------ - Update BackItUp von 3.3.13 > 3.3.14 - Update OS (64 Packete) base-files libcap2 libss2 openssh-client bash libcap2-bin libssl3t64 openssh-server busybox libcom-err2 libtalloc2 openssh-sftp-server dirmngr libdpkg-perl libwayland-client0 openssl dpkg libdtovl0 libwayland-cursor0 openssl-provider-legacy dpkg-dev libegl-mesa0 libwayland-egl1 python3-requests e2fsprogs libext2fs2t64 libwayland-server0 raspi-utils gnupg-utils libgbm1 libwbclient0 raspi-utils-core gpg libgl1-mesa-dri linux-base raspi-utils-dt gpg-agent libglx-mesa0 linux-sysctl-defaults raspi-utils-eeprom gpg-wks-client libgpiolib0 logsave raspi-utils-otp gpg-wks-server libmpg123-0t64 mesa-libgallium raspinfo gpgconf libpixman-1-0 mesa-va-drivers ssh gpgsm libpixman-1-dev mesa-vdpau-drivers sudo gpgv libsndfile1 mesa-vulkan-drivers tzdata libcap-dev libsqlite3-0 nodejs wireless-regdb libc-bin libc-dev-bin libc-devtools libc-l10n libc6 libc6-dbg libc6-dev libssl3t64 l ocales openssl openssl-provider-legacy - nodejs v22.22.1 - npm v10.9.4 - Linux 6.12.62 - Update pishrink > v.2026_03_16 # 27.02.2026 - OS - Update, + Image ---------------------------------------- - OS Update (10 Packete) # 17.02.2026 - kleines OS-Update + Image ---------------------------------------------------- - rpi-eeprom - installiert fritzdect 2.6.1 - installiert lovelace 5.0.5 - Image: 2026_0217_ioBroker_Linux 6.12.62 - controller 7.0.7 - admin 7.7.2 - npm 10.9.4 - nodejs 22.22.0diag:
========== Start marking the full check here =========== ```bash Script v.2026-01-31 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: iobroker Icon name: computer Kernel: Linux 6.12.62+rpt-rpi-v8 Architecture: arm64 OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.5 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 17:49:25 up 1 day, 21:34, 1 user, load average: 3.39, 2.11, 1.58 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Wed 2026-03-18 17:49:25 CET Universal time: Wed 2026-03-18 16:49:25 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/home/pi GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 2.9G 633M 13M 4.8G 5.3G Swap: 536M 0B 536M Total: 8.7G 2.9G 1.2G Active iob-Instances: 25 7820 M total memory 2765 M used memory 2738 M active memory 3960 M inactive memory 603 M free memory 467 M buffer memory 4123 M swap cache 511 M total swap 0 M used swap 511 M free swap *** top - Table Of Processes *** top - 17:49:25 up 1 day, 21:34, 1 user, load average: 3.39, 2.11, 1.58 Tasks: 217 total, 2 running, 215 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 2.3 sy, 0.0 ni, 74.4 id, 23.3 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7820.7 total, 603.7 free, 2765.6 used, 4591.2 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 5055.1 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 783M 9.9M 773M 2% /run /dev/mmcblk0p2 ext4 29G 9.9G 18G 37% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock tmpfs tmpfs 3.9G 2.8M 3.9G 1% /tmp tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service /dev/mmcblk0p1 vfat 510M 66M 445M 13% /boot/firmware /dev/sda5 ext4 27G 14G 12G 54% /media/USBintern tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/serial-getty@ttyS0.service tmpfs tmpfs 783M 8.0K 783M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Mon Mar 16 20:14:56 2026] EXT4-fs (mmcblk0p2): mounted filesystem ce208fd3-38a8-424a-87a2-cd44114eb820 ro with ordered data mode. Quota mode: none. [Mon Mar 16 20:14:58 2026] EXT4-fs (mmcblk0p2): re-mounted ce208fd3-38a8-424a-87a2-cd44114eb820 r/w. [Mon Mar 16 20:15:01 2026] EXT4-fs (sda5): mounted filesystem bfb7e6d7-3877-db01-2026-e6d73877db01 r/w with ordered data mode. Quota mode: none. [Mon Mar 16 20:47:36 2026] EXT4-fs (loop0): recovery complete [Mon Mar 16 20:47:36 2026] EXT4-fs (loop0): mounted filesystem ce208fd3-38a8-424a-87a2-cd44114eb820 r/w with ordered data mode. Quota mode: none. [Mon Mar 16 20:47:36 2026] EXT4-fs (loop0): unmounting filesystem ce208fd3-38a8-424a-87a2-cd44114eb820. [Mon Mar 16 20:54:38 2026] EXT4-fs (loop0): mounted filesystem ce208fd3-38a8-424a-87a2-cd44114eb820 r/w with ordered data mode. Quota mode: none. [Mon Mar 16 20:55:36 2026] EXT4-fs (loop0): unmounting filesystem ce208fd3-38a8-424a-87a2-cd44114eb820. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro `-/media/USBintern /dev/sda5 ext4 rw,noatime Files in neuralgic directories: /var: 1.2G /var/ 293M /var/log 292M /var/log/journal/486bb6fc0ef2491bae34baf22dc43901 292M /var/log/journal 205M /var/cache Archived and active journals take up 300.1M in the file system. /opt/iobroker/backups: 76K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 416M /opt/iobroker/iobroker-data/ 282M /opt/iobroker/iobroker-data/files 96M /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: 33M /opt/iobroker/iobroker-data/objects.jsonl 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 24M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.70a15e1f.js.map 18M /opt/iobroker/iobroker-data/files/echarts/preview/static/js/main.5fe9c7da.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' No nvbackup.json found. *** NodeJS-Installation *** /usr/bin/nodejs v22.22.1 /usr/bin/node v22.22.1 /usr/bin/npm 10.9.4 /usr/bin/npx 10.9.4 ✓ Node.js installation is correct nodejs: Installed: 22.22.1-1nodesource1 Candidate: 22.22.1-1nodesource1 Version table: *** 22.22.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.22.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 20.19.2+dfsg-1+deb13u1 500 500 http://deb.debian.org/debian-security trixie-security/main arm64 Packages 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: iobroker iobroker (version: 7.0.7, hostname: iobroker , alive, uptime: 164068) Core adapters versions js-controller: 7.0.7 admin: 7.7.22 javascript: 9.0.18 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : iobroker - enabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.device-watcher.0 : device-watcher : iobroker - enabled + system.adapter.deyeidc.0 : deyeidc : iobroker - enabled, port: 8899 + system.adapter.echarts.0 : echarts : iobroker - enabled + system.adapter.email.0 : email : iobroker - enabled + system.adapter.energiefluss.0 : energiefluss : iobroker - enabled system.adapter.flot.0 : flot : iobroker - enabled + system.adapter.fritzdect.0 : fritzdect : iobroker - enabled + system.adapter.ham.0 : ham : iobroker - enabled + system.adapter.history.0 : history : iobroker - enabled + system.adapter.hs100.0 : hs100 : iobroker - enabled + system.adapter.iot.0 : iot : iobroker - enabled + system.adapter.jarvis.0 : jarvis : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.lovelace.0 : lovelace : iobroker - enabled, port: 8091, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.onvif.0 : onvif : iobroker - enabled, port: 80, 7575, 8000, 8080, 8081, 8899,554,2020 + system.adapter.ping.0 : ping : iobroker - enabled + system.adapter.rpi2.0 : rpi2 : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.statistics.0 : statistics : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.deyeidc.0 : deyeidc : iobroker - enabled, port: 8899 + system.adapter.lovelace.0 : lovelace : iobroker - enabled, port: 8091, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.onvif.0 : onvif : iobroker - enabled, port: 80, 7575, 8000, 8080, 8081, 8899,554,2020 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - 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.22 , installed 7.7.22 Adapter "alexa2" : 3.27.4 , installed 3.27.4 Adapter "backitup" : 3.3.14 , installed 3.3.14 Adapter "device-watcher": 2.15.5 , installed 2.15.5 Adapter "deyeidc" : 0.3.1 , installed 0.3.1 Adapter "echarts" : 1.9.2 , installed 1.9.2 Adapter "email" : 2.0.4 , installed 2.0.4 Adapter "energiefluss" : 3.6.2 , installed 3.6.2 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "fritzdect" : 2.6.2 , installed 2.6.1 [Updatable] Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hs100" : 3.0.5 , installed 3.0.5 Adapter "iot" : 5.0.7 , installed 5.0.7 Adapter "jarvis" : 3.1.8 , installed 3.1.8 Adapter "javascript" : 9.0.18 , installed 9.0.18 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "lovelace" : 5.0.5 , installed 5.0.5 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "onvif" : 1.1.4 , installed 1.1.4 Adapter "ping" : 1.7.9 , installed 1.7.9 Adapter "rpi2" : 2.4.0 , installed 3.0.2 Adapter "shelly" : 10.5.2 , installed 10.5.2 Adapter "socketio" : 6.7.1 , installed 7.0.8 Adapter "sonoff" : 3.2.1 , installed 3.2.1 Adapter "statistics" : 2.4.0 , installed 2.4.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "ws" : 2.6.2 , installed 3.0.19 Objects and States Please stand by - This may take a while Objects: 5987 States: 4919 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://archive.raspberrypi.com/debian trixie InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Done N: Missing Signed-By in the sources.list(5) entry for 'http://archive.raspberrypi.com/debian' Pending systemupdates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 10360 1312/io.sonoff.0 tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1001 10344 1280/io.mqtt.0 tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 7356 700/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 7359 700/iobroker.js-con tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 4963 713/sshd: /usr/sbin tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 8963 1398/io.jarvis.0 tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 5100 969/exim4 tcp6 0 0 ::1:25 :::* LISTEN 0 5101 969/exim4 tcp6 0 0 :::8091 :::* LISTEN 1001 9685 1410/io.lovelace.0 tcp6 0 0 :::8095 :::* LISTEN 1001 8938 1430/io.onvif.0 tcp6 0 0 :::8082 :::* LISTEN 1001 10629 1446/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 7400 990/io.admin.0 tcp6 0 0 :::22 :::* LISTEN 0 4973 713/sshd: /usr/sbin udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 8943 1332/io.ham.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 6607 500/avahi-daemon: r udp 0 0 0.0.0.0:34173 0.0.0.0:* 104 6609 500/avahi-daemon: r udp 0 0 0.0.0.0:58917 0.0.0.0:* 1001 316173 1296/io.shelly.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 8702 1296/io.shelly.0 udp6 0 0 :::5353 :::* 104 6608 500/avahi-daemon: r udp6 0 0 :::45189 :::* 104 6610 500/avahi-daemon: r *** Log File - Last 25 Lines *** 2026-03-18 17:45:00.015 - info: javascript.0 (1074) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-18 17:45:54.474 - info: device-watcher.0 (117883) Das folgende Gerät ist wieder verfügbar: hs100: HS100-1 (0 Minuten) 2026-03-18 17:45:54.522 - info: email.0 (1002) Send email: {"sendTo":"iob@bwlcollection.de","text":"Das folgende Gerät ist wieder verfügbar: \nhs100: HS100-1 (0 Minuten)","subject":"Status Devices","from":"iob@bwlcollection.de","to":"sys@bwlcollection.de"} 2026-03-18 17:45:54.819 - info: email.0 (1002) sent to sys@bwlcollection.de 2026-03-18 17:45:54.834 - info: device-watcher.0 (117883) Das folgende Gerät ist wieder verfügbar: hs100: HS100-2 (0 Minuten) 2026-03-18 17:45:54.886 - info: email.0 (1002) Send email: {"sendTo":"iob@bwlcollection.de","text":"Das folgende Gerät ist wieder verfügbar: \nhs100: HS100-2 (0 Minuten)","subject":"Status Devices","from":"iob@bwlcollection.de","to":"sys@bwlcollection.de"} 2026-03-18 17:45:55.162 - info: email.0 (1002) sent to sys@bwlcollection.de 2026-03-18 17:47:58.316 - info: device-watcher.0 (117883) Das folgende Gerät ist nicht mehr erreichbar: hs100: HS100-1 (2 Minuten) 2026-03-18 17:47:58.367 - info: email.0 (1002) Send email: {"sendTo":"iob@bwlcollection.de","text":"Das folgende Gerät ist nicht mehr erreichbar: \nhs100: HS100-1 (2 Minuten)","subject":"Status Devices","from":"iob@bwlcollection.de","to":"sys@bwlcollection.de"} 2026-03-18 17:47:58.672 - info: email.0 (1002) sent to sys@bwlcollection.de 2026-03-18 17:47:58.694 - info: device-watcher.0 (117883) Das folgende Gerät ist nicht mehr erreichbar: hs100: HS100-2 (2 Minuten) 2026-03-18 17:47:58.743 - info: email.0 (1002) Send email: {"sendTo":"iob@bwlcollection.de","text":"Das folgende Gerät ist nicht mehr erreichbar: \nhs100: HS100-2 (2 Minuten)","subject":"Status Devices","from":"iob@bwlcollection.de","to":"sys@bwlcollection.de"} 2026-03-18 17:47:59.055 - info: email.0 (1002) sent to sys@bwlcollection.de 2026-03-18 17:49:00.584 - info: device-watcher.0 (117883) Das folgende Gerät ist wieder verfügbar: hs100: HS100-1 (0 Minuten) 2026-03-18 17:49:00.635 - info: email.0 (1002) Send email: {"sendTo":"iob@bwlcollection.de","text":"Das folgende Gerät ist wieder verfügbar: \nhs100: HS100-1 (0 Minuten)","subject":"Status Devices","from":"iob@bwlcollection.de","to":"sys@bwlcollection.de"} 2026-03-18 17:49:00.919 - info: email.0 (1002) sent to sys@bwlcollection.de 2026-03-18 17:49:00.934 - info: device-watcher.0 (117883) Das folgende Gerät ist wieder verfügbar: hs100: HS100-2 (0 Minuten) 2026-03-18 17:49:00.986 - info: email.0 (1002) Send email: {"sendTo":"iob@bwlcollection.de","text":"Das folgende Gerät ist wieder verfügbar: \nhs100: HS100-2 (0 Minuten)","subject":"Status Devices","from":"iob@bwlcollection.de","to":"sys@bwlcollection.de"} 2026-03-18 17:49:01.266 - info: email.0 (1002) sent to sys@bwlcollection.de============ Mark until here for C&P =============
iob diag has finished.
Überlegungen:
Dass die HS100 vlt. mal kurz aus dem WLAN ist, weil die Fritzbox via Mesh die Geräte neu zuordnet, ist selten, kann vorkommen. Dass aber beide HS100 ständig "nicht erreichbar" sind ist eher unwahrscheinlich. Beide mit > 15 MBit/s (kleinster Werte) verbunden und erreichbar.
In den Objekten werden die HS100 als verbunden gemeldet:
hs100.0.info.connection trueShelly gibt gerade Ruhe, daher keine aktuellen relevanten Infos.
Aber: Signalstärke geht spontan auf 1 MBit/s zurück, nach ansprechen (AN-Aus) Signalstärke wieder um die 70 MBit/s. Aber auch das folgt keinem erkennbaren System.@Rico-Sander sagte in Probleme mit dem Device-Watcher:
N: Missing Signed-By in the sources.list(5) entry for 'http://archive.raspberrypi.com/debian'
Da stimmt was nicht mit der Quelle.
-
Danke - ist es nun richtig?
*** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending systemupdates: 0 *** Listening Ports *** Active Internet connections (only servers)Wenns nicht geht, wie man will - muss mans tun, wie man kann. -
Danke - ist es nun richtig?
*** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending systemupdates: 0 *** Listening Ports *** Active Internet connections (only servers)Nein, jetzt hast du die ganz deaktiviert...
Auf einem Raspberry sind das die Standard-Repos:
Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://deb.debian.org/debian-security trixie-security InRelease Hit:4 http://archive.raspberrypi.com/debian trixie InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease All packages are up to date.Die sources sieht dann so aus (Schon im neuen Format):
thomas@testpi:~ $ cat /etc/apt/sources.list.d/raspi.sources Types: deb URIs: http://archive.raspberrypi.com/debian/ Suites: trixie Components: main Signed-By: /usr/share/keyrings/raspberrypi-archive-keyring.pgp thomas@testpi:~ $ -
Die cat /etc/apt/sources.list.d/raspi.sources ist bei mir leer.
Die /etc/apt/sources.list.d/nodesource.list sieht dann so aus:
deb [arch=arm64 signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x>Und die /etc/apt/sources.list.d/debian.sources
# Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian-security/ Suites: trixie-security Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie-updates Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpgUnd das hier:
pi@iobroker:/usr/share/keyrings $ ls -a . debian-archive-keyring.pgp .. debian-archive-removed-keys.gpg debian-archive-bookworm-automatic.gpg debian-archive-removed-keys.pgp debian-archive-bookworm-automatic.pgp debian-archive-trixie-automatic.gpg debian-archive-bookworm-security-automatic.gpg debian-archive-trixie-automatic.pgp debian-archive-bookworm-security-automatic.pgp debian-archive-trixie-security-automatic.gpg debian-archive-bookworm-stable.gpg debian-archive-trixie-security-automatic.pgp debian-archive-bookworm-stable.pgp debian-archive-trixie-stable.gpg debian-archive-bullseye-automatic.gpg debian-archive-trixie-stable.pgp debian-archive-bullseye-automatic.pgp nodesource.gpg debian-archive-bullseye-security-automatic.gpg raspberrypi-archive-automatic.gpg debian-archive-bullseye-security-automatic.pgp raspberrypi-archive-automatic.pgp debian-archive-bullseye-stable.gpg raspberrypi-archive-keyring.gpg debian-archive-bullseye-stable.pgp raspberrypi-archive-keyring.pgp debian-archive-keyring.gpg pi@iobroker:/usr/share/keyrings $Wenns nicht geht, wie man will - muss mans tun, wie man kann. -
Die cat /etc/apt/sources.list.d/raspi.sources ist bei mir leer.
Die /etc/apt/sources.list.d/nodesource.list sieht dann so aus:
deb [arch=arm64 signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x>Und die /etc/apt/sources.list.d/debian.sources
# Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian-security/ Suites: trixie-security Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie-updates Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpgUnd das hier:
pi@iobroker:/usr/share/keyrings $ ls -a . debian-archive-keyring.pgp .. debian-archive-removed-keys.gpg debian-archive-bookworm-automatic.gpg debian-archive-removed-keys.pgp debian-archive-bookworm-automatic.pgp debian-archive-trixie-automatic.gpg debian-archive-bookworm-security-automatic.gpg debian-archive-trixie-automatic.pgp debian-archive-bookworm-security-automatic.pgp debian-archive-trixie-security-automatic.gpg debian-archive-bookworm-stable.gpg debian-archive-trixie-security-automatic.pgp debian-archive-bookworm-stable.pgp debian-archive-trixie-stable.gpg debian-archive-bullseye-automatic.gpg debian-archive-trixie-stable.pgp debian-archive-bullseye-automatic.pgp nodesource.gpg debian-archive-bullseye-security-automatic.gpg raspberrypi-archive-automatic.gpg debian-archive-bullseye-security-automatic.pgp raspberrypi-archive-automatic.pgp debian-archive-bullseye-stable.gpg raspberrypi-archive-keyring.gpg debian-archive-bullseye-stable.pgp raspberrypi-archive-keyring.pgp debian-archive-keyring.gpg pi@iobroker:/usr/share/keyrings $@Rico-Sander sagte in Probleme mit dem Device-Watcher:
Die cat /etc/apt/sources.list.d/raspi.sources ist bei mir leer.
Logisch, sonst würde das Repo ja auch gefunden.
Was da rein gehört siehst du oben. -
Na toll, da habe ich nach Deiner Anleitung die Datei befüllt und nun das:
pi@iobroker:~ $ sudo apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Get:4 http://archive.raspberrypi.com/debian trixie InRelease [54.9 kB] Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Err:4 http://archive.raspberrypi.com/debian trixie InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on CF8A1AF502A2AA2D763BAE7E82B129927FA3303E is not bound: No binding signature at time 2026-03-19T09:00:19Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Warning: OpenPGP signature verification failed: http://archive.raspberrypi.com/debian trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on CF8A1AF502A2AA2D763BAE7E82B129927FA3303E is not bound: No binding signature at time 2026-03-19T09:00:19Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Error: The repository 'http://archive.raspberrypi.com/debian trixie InRelease' is not signed. Notice: Updating from such a repository can't be done securely, and is therefore disabled by default. Notice: See apt-secure(8) manpage for repository creation and user configuration details. pi@iobroker:~ $Fragen:
- Woran liegt es?
- Wie bekomme ich den Fehler weg?
- Was ist mit den anderen oben genannten Dateien (z.B. debian.sources)
- Was ist mit den alten keys?
Frage an Mods:
Soll ich den Titel des Themas ändern? Der Hauptinhalt der aktuellen Diskussion hat ja nix mehr mit der eigentlichen Frage zu tun - DankeWenns nicht geht, wie man will - muss mans tun, wie man kann. -
Na toll, da habe ich nach Deiner Anleitung die Datei befüllt und nun das:
pi@iobroker:~ $ sudo apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Get:4 http://archive.raspberrypi.com/debian trixie InRelease [54.9 kB] Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Err:4 http://archive.raspberrypi.com/debian trixie InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on CF8A1AF502A2AA2D763BAE7E82B129927FA3303E is not bound: No binding signature at time 2026-03-19T09:00:19Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Warning: OpenPGP signature verification failed: http://archive.raspberrypi.com/debian trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on CF8A1AF502A2AA2D763BAE7E82B129927FA3303E is not bound: No binding signature at time 2026-03-19T09:00:19Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Error: The repository 'http://archive.raspberrypi.com/debian trixie InRelease' is not signed. Notice: Updating from such a repository can't be done securely, and is therefore disabled by default. Notice: See apt-secure(8) manpage for repository creation and user configuration details. pi@iobroker:~ $Fragen:
- Woran liegt es?
- Wie bekomme ich den Fehler weg?
- Was ist mit den anderen oben genannten Dateien (z.B. debian.sources)
- Was ist mit den alten keys?
Frage an Mods:
Soll ich den Titel des Themas ändern? Der Hauptinhalt der aktuellen Diskussion hat ja nix mehr mit der eigentlichen Frage zu tun - Danke@Rico-Sander sagte in Probleme mit dem Device-Watcher:
Woran liegt es?
An veralteten Schlüsseln.
Hast du das System von einer Vorversion auf Trixie gehoben? -
@Rico-Sander sagte in Probleme mit dem Device-Watcher:
Woran liegt es?
An veralteten Schlüsseln.
Hast du das System von einer Vorversion auf Trixie gehoben?@Thomas-Braun sagte in Probleme mit dem Device-Watcher:
Hast du das System von einer Vorversion auf Trixie gehoben?
Yepp, streng nach Deiner Anleitung abgearbeitet. Dabei wird sicher auch die debian.source entstanden sein?
Wenns nicht geht, wie man will - muss mans tun, wie man kann. -
@Thomas-Braun sagte in Probleme mit dem Device-Watcher:
Hast du das System von einer Vorversion auf Trixie gehoben?
Yepp, streng nach Deiner Anleitung abgearbeitet. Dabei wird sicher auch die debian.source entstanden sein?
@Rico-Sander sagte in Probleme mit dem Device-Watcher:
Dabei wird sicher auch die debian.source entstanden sein?
Nein. Der Part ist optional.
Was liegt denn an Dateien inls -la /etc/apt/sources.list.d/herum?
-
Moin,
pi@iobroker:~ $ ls -la /etc/apt/sources.list.d/ total 24 drwxr-xr-x 2 root root 4096 Mar 19 10:13 . drwxr-xr-x 9 root root 4096 Mar 18 20:12 .. -rw-r--r-- 1 root root 664 Sep 13 2025 debian.sources -rw-r--r-- 1 root root 113 Feb 7 15:23 nodesource.list -rw-r--r-- 1 root root 187 Sep 13 2025 raspi.list.bak -rw-r--r-- 1 root root 151 Mar 19 10:13 raspi.sources pi@iobroker:~ $Wenns nicht geht, wie man will - muss mans tun, wie man kann. -
Moin,
pi@iobroker:~ $ ls -la /etc/apt/sources.list.d/ total 24 drwxr-xr-x 2 root root 4096 Mar 19 10:13 . drwxr-xr-x 9 root root 4096 Mar 18 20:12 .. -rw-r--r-- 1 root root 664 Sep 13 2025 debian.sources -rw-r--r-- 1 root root 113 Feb 7 15:23 nodesource.list -rw-r--r-- 1 root root 187 Sep 13 2025 raspi.list.bak -rw-r--r-- 1 root root 151 Mar 19 10:13 raspi.sources pi@iobroker:~ $apt policy raspberrypi-archive-keyringsagt?
Dirty workaround:sudo rm /etc/apt/sources.list.d/raspi.sources
sudo mv /etc/apt/sources.list.d/raspi.list.bak /etc/apt/sources.list.d/raspi.listDann trag in die raspi.list diese Zeile ein:
deb [trusted=yes] http://archive.raspberrypi.com/debian trixie mainDie bereits vorhandene Zeilen mit # auskommentieren.
Dannsudo apt update sudo apt full-upgradeWenn das durch ist und nach einem Neustart die Änderungen in der raspi.list wieder rückgängig machen.
-
apt policy raspberrypi-archive-keyringsagt?
Dirty workaround:sudo rm /etc/apt/sources.list.d/raspi.sources
sudo mv /etc/apt/sources.list.d/raspi.list.bak /etc/apt/sources.list.d/raspi.listDann trag in die raspi.list diese Zeile ein:
deb [trusted=yes] http://archive.raspberrypi.com/debian trixie mainDie bereits vorhandene Zeilen mit # auskommentieren.
Dannsudo apt update sudo apt full-upgradeWenn das durch ist und nach einem Neustart die Änderungen in der raspi.list wieder rückgängig machen.
@Thomas-Braun sagte in Probleme mit dem Device-Watcher:
apt policy raspberrypi-archive-keyring
pi@iobroker:~ $ apt policy raspberrypi-archive-keyring raspberrypi-archive-keyring: Installed: 2025.1+rpt1 Candidate: 2025.1+rpt1 Version table: *** 2025.1+rpt1 100 100 /var/lib/dpkg/status pi@iobroker:~ $Das andere arbeite ich gleich mal ab - Danke bis dahin..
-
apt policy raspberrypi-archive-keyringsagt?
Dirty workaround:sudo rm /etc/apt/sources.list.d/raspi.sources
sudo mv /etc/apt/sources.list.d/raspi.list.bak /etc/apt/sources.list.d/raspi.listDann trag in die raspi.list diese Zeile ein:
deb [trusted=yes] http://archive.raspberrypi.com/debian trixie mainDie bereits vorhandene Zeilen mit # auskommentieren.
Dannsudo apt update sudo apt full-upgradeWenn das durch ist und nach einem Neustart die Änderungen in der raspi.list wieder rückgängig machen.
Das sollte es dann gewesen sein, oder?
Möchtest Du nochmal diag sehen?pi@iobroker:/ $ sudo apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:5 http://archive.raspberrypi.com/debian trixie InRelease Get:6 http://archive.raspberrypi.com/debian trixie/main Sources [111 kB] Fetched 111 kB in 0s (299 kB/s) All packages are up to date. pi@iobroker:/ $ sudo apt full-upgrade Summary: Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0 pi@iobroker:/ $Wenns nicht geht, wie man will - muss mans tun, wie man kann. -
Das sollte es dann gewesen sein, oder?
Möchtest Du nochmal diag sehen?pi@iobroker:/ $ sudo apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:5 http://archive.raspberrypi.com/debian trixie InRelease Get:6 http://archive.raspberrypi.com/debian trixie/main Sources [111 kB] Fetched 111 kB in 0s (299 kB/s) All packages are up to date. pi@iobroker:/ $ sudo apt full-upgrade Summary: Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0 pi@iobroker:/ $@Rico-Sander sagte in Probleme mit dem Device-Watcher:
Möchtest Du nochmal diag sehen?
Ja. Und den jetzigen Inhalt der /etc/apt/sources.list.d/raspi.list
Und du steht im falschen Verzeichnis, stell dich mit dem user 'pi' in dessen home.
-
/etc/apt/sources.list.d/raspi.list:
#deb [trusted=yes] http://archive.raspberrypi.com/debian trixie main # Uncomment line below then 'apt-get update' to enable 'apt-get source' deb-src http://archive.raspberrypi.com/debian/ trixie main```bash Script v.2026-01-31 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: iobroker Icon name: computer Kernel: Linux 6.12.75+rpt-rpi-v8 Architecture: arm64 OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.5 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 12:16:11 up 1 day, 2:01, 1 user, load average: 1.60, 1.20, 1.01 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Fri 2026-03-20 12:16:11 CET Universal time: Fri 2026-03-20 11:16:11 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/home/pi GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 2.7G 240M 11M 5.4G 5.5G Swap: 536M 0B 536M Total: 8.7G 2.7G 777M Active iob-Instances: 25 7820 M total memory 2579 M used memory 2617 M active memory 4614 M inactive memory 229 M free memory 124 M buffer memory 5012 M swap cache 511 M total swap 0 M used swap 511 M free swap *** top - Table Of Processes *** top - 12:16:12 up 1 day, 2:01, 1 user, load average: 1.79, 1.24, 1.03 Tasks: 219 total, 1 running, 218 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 2.1 sy, 0.0 ni, 95.7 id, 2.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7820.7 total, 228.4 free, 2580.8 used, 5137.6 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 5239.9 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 783M 11M 772M 2% /run /dev/mmcblk0p2 ext4 29G 9.7G 18G 36% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock tmpfs tmpfs 3.9G 424K 3.9G 1% /tmp tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service /dev/mmcblk0p1 vfat 510M 66M 445M 13% /boot/firmware /dev/sda5 ext4 27G 14G 12G 54% /media/USBintern tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/serial-getty@ttyS0.service tmpfs tmpfs 783M 8.0K 783M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Thu Mar 19 10:14:40 2026] EXT4-fs (mmcblk0p2): mounted filesystem ce208fd3-38a8-424a-87a2-cd44114eb820 ro with ordered data mode. Quota mode: none. [Thu Mar 19 10:14:42 2026] EXT4-fs (mmcblk0p2): re-mounted ce208fd3-38a8-424a-87a2-cd44114eb820 r/w. [Thu Mar 19 10:14:45 2026] EXT4-fs (sda5): mounted filesystem bfb7e6d7-3877-db01-2026-e6d73877db01 r/w with ordered data mode. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro `-/media/USBintern /dev/sda5 ext4 rw,noatime Files in neuralgic directories: /var: 1.2G /var/ 293M /var/log 292M /var/log/journal/486bb6fc0ef2491bae34baf22dc43901 292M /var/log/journal 203M /var/cache Archived and active journals take up 300.4M in the file system. /opt/iobroker/backups: 76K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 400M /opt/iobroker/iobroker-data/ 282M /opt/iobroker/iobroker-data/files 96M /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: 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 24M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.70a15e1f.js.map 18M /opt/iobroker/iobroker-data/files/echarts/preview/static/js/main.5fe9c7da.js.map 14M /opt/iobroker/iobroker-data/objects.jsonl USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' No nvbackup.json found. *** NodeJS-Installation *** /usr/bin/nodejs v22.22.1 /usr/bin/node v22.22.1 /usr/bin/npm 10.9.4 /usr/bin/npx 10.9.4 ✓ Node.js installation is correct nodejs: Installed: 22.22.1-1nodesource1 Candidate: 22.22.1-1nodesource1 Version table: *** 22.22.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.22.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 20.19.2+dfsg-1+deb13u1 500 500 http://deb.debian.org/debian-security trixie-security/main arm64 Packages 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: iobroker iobroker (version: 7.0.7, hostname: iobroker , alive, uptime: 93699) Core adapters versions js-controller: 7.0.7 admin: 7.7.22 javascript: 9.0.18 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : iobroker - enabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.device-watcher.0 : device-watcher : iobroker - enabled + system.adapter.deyeidc.0 : deyeidc : iobroker - enabled, port: 8899 + system.adapter.echarts.0 : echarts : iobroker - enabled + system.adapter.email.0 : email : iobroker - enabled + system.adapter.energiefluss.0 : energiefluss : iobroker - enabled system.adapter.flot.0 : flot : iobroker - enabled + system.adapter.fritzdect.0 : fritzdect : iobroker - enabled + system.adapter.ham.0 : ham : iobroker - enabled + system.adapter.history.0 : history : iobroker - enabled + system.adapter.hs100.0 : hs100 : iobroker - enabled + system.adapter.iot.0 : iot : iobroker - enabled + system.adapter.jarvis.0 : jarvis : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.lovelace.0 : lovelace : iobroker - enabled, port: 8091, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.onvif.0 : onvif : iobroker - enabled, port: 80, 7575, 8000, 8080, 8081, 8899,554,2020 + system.adapter.ping.0 : ping : iobroker - enabled + system.adapter.rpi2.0 : rpi2 : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.statistics.0 : statistics : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.deyeidc.0 : deyeidc : iobroker - enabled, port: 8899 + system.adapter.lovelace.0 : lovelace : iobroker - enabled, port: 8091, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.onvif.0 : onvif : iobroker - enabled, port: 80, 7575, 8000, 8080, 8081, 8899,554,2020 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - 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.22 , installed 7.7.22 Adapter "alexa2" : 3.27.4 , installed 3.27.4 Adapter "backitup" : 3.3.14 , installed 3.3.14 Adapter "device-watcher": 2.15.5 , installed 2.15.5 Adapter "deyeidc" : 0.3.1 , installed 0.3.1 Adapter "echarts" : 1.9.2 , installed 1.9.2 Adapter "email" : 2.0.4 , installed 2.0.4 Adapter "energiefluss" : 3.6.2 , installed 3.6.2 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "fritzdect" : 2.6.2 , installed 2.6.1 [Updatable] Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hs100" : 3.0.5 , installed 3.0.5 Adapter "iot" : 5.0.7 , installed 5.0.7 Adapter "jarvis" : 3.1.8 , installed 3.1.8 Adapter "javascript" : 9.0.18 , installed 9.0.18 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "lovelace" : 5.0.5 , installed 5.0.5 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "onvif" : 1.1.4 , installed 1.1.4 Adapter "ping" : 1.7.9 , installed 1.7.9 Adapter "rpi2" : 2.4.0 , installed 3.0.2 Adapter "shelly" : 10.5.2 , installed 10.5.2 Adapter "socketio" : 6.7.1 , installed 7.0.8 Adapter "sonoff" : 3.2.1 , installed 3.2.1 Adapter "statistics" : 2.4.0 , installed 2.4.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "ws" : 2.6.2 , installed 3.0.19 Objects and States Please stand by - This may take a while Objects: 5987 States: 4919 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://archive.raspberrypi.com/debian trixie InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending systemupdates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 8367 990/exim4 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 8380 715/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 5946 715/iobroker.js-con tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 9626 1368/io.sonoff.0 tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1001 6981 1308/io.mqtt.0 tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 9793 1481/io.jarvis.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 7402 728/sshd: /usr/sbin tcp6 0 0 :::8081 :::* LISTEN 1001 7715 1006/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 11457 1565/io.web.0 tcp6 0 0 :::8091 :::* LISTEN 1001 11340 1494/io.lovelace.0 tcp6 0 0 :::8095 :::* LISTEN 1001 9136 1520/io.onvif.0 tcp6 0 0 ::1:25 :::* LISTEN 0 8368 990/exim4 tcp6 0 0 :::22 :::* LISTEN 0 7404 728/sshd: /usr/sbin udp 0 0 0.0.0.0:58240 0.0.0.0:* 104 5728 514/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 8157 1391/io.ham.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 5726 514/avahi-daemon: r udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 9604 1348/io.shelly.0 udp6 0 0 :::40594 :::* 104 5729 514/avahi-daemon: r udp6 0 0 :::5353 :::* 104 5727 514/avahi-daemon: r *** Log File - Last 25 Lines *** 2026-03-20 09:16:04.654 - info: device-watcher.0 (68279) Number of selected adapters to monitor devices: 6. Loading data from: fritzdectDevices, fullyMQTTDevices, hamDevices, shellyDevices, sonoffDevices, tapoDevices ... 2026-03-20 09:17:10.550 - info: lovelace.0 (1494) Unknown request for /lovelace/default_view 2026-03-20 09:18:08.350 - info: web.0 (1565) ==> Connected system.user.admin from ::ffff:192.168.178.2 2026-03-20 09:18:10.901 - info: web.0 (1565) ==> Connected system.user.admin from ::ffff:192.168.178.2 2026-03-20 09:28:32.265 - info: web.0 (1565) <== Disconnect system.user.admin from ::ffff:192.168.178.2 2026-03-20 09:28:32.266 - info: web.0 (1565) <== Disconnect system.user.admin from ::ffff:192.168.178.2 flot 2026-03-20 09:28:41.509 - info: web.0 (1565) ==> Connected system.user.admin from ::ffff:192.168.178.2 2026-03-20 09:28:49.084 - info: web.0 (1565) <== Disconnect system.user.admin from ::ffff:192.168.178.2 energiefluss.0 2026-03-20 09:29:04.616 - info: jarvis.0 (1481) Client with IP 192.168.178.2 connected. 2026-03-20 09:29:05.511 - info: admin.0 (1006) <== Disconnect system.user.admin from ::ffff:192.168.178.2 admin 2026-03-20 09:29:24.116 - info: jarvis.0 (1481) Client with IP 192.168.178.2 disconnected. 2026-03-20 09:30:00.008 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 09:45:00.014 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 10:00:00.011 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 10:15:00.008 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 10:15:05.139 - info: admin.0 (1006) Adapter rating updated 2026-03-20 10:30:00.007 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 10:39:54.750 - warn: hs100.0 (1291) Socket connection Timeout 192_168_178_51 HS100-1 please reconnect the Device 2026-03-20 10:45:00.010 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 11:00:00.009 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 11:15:00.012 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 11:30:00.009 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 11:45:00.009 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 12:00:00.011 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 12:15:00.006 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2Falls noch etwas zu tun ist, erst wieder am Abend...
Und Danke...
Wenns nicht geht, wie man will - muss mans tun, wie man kann. -
/etc/apt/sources.list.d/raspi.list:
#deb [trusted=yes] http://archive.raspberrypi.com/debian trixie main # Uncomment line below then 'apt-get update' to enable 'apt-get source' deb-src http://archive.raspberrypi.com/debian/ trixie main```bash Script v.2026-01-31 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: iobroker Icon name: computer Kernel: Linux 6.12.75+rpt-rpi-v8 Architecture: arm64 OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.5 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 12:16:11 up 1 day, 2:01, 1 user, load average: 1.60, 1.20, 1.01 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Fri 2026-03-20 12:16:11 CET Universal time: Fri 2026-03-20 11:16:11 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/home/pi GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 2.7G 240M 11M 5.4G 5.5G Swap: 536M 0B 536M Total: 8.7G 2.7G 777M Active iob-Instances: 25 7820 M total memory 2579 M used memory 2617 M active memory 4614 M inactive memory 229 M free memory 124 M buffer memory 5012 M swap cache 511 M total swap 0 M used swap 511 M free swap *** top - Table Of Processes *** top - 12:16:12 up 1 day, 2:01, 1 user, load average: 1.79, 1.24, 1.03 Tasks: 219 total, 1 running, 218 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 2.1 sy, 0.0 ni, 95.7 id, 2.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7820.7 total, 228.4 free, 2580.8 used, 5137.6 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 5239.9 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 783M 11M 772M 2% /run /dev/mmcblk0p2 ext4 29G 9.7G 18G 36% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock tmpfs tmpfs 3.9G 424K 3.9G 1% /tmp tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service /dev/mmcblk0p1 vfat 510M 66M 445M 13% /boot/firmware /dev/sda5 ext4 27G 14G 12G 54% /media/USBintern tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/serial-getty@ttyS0.service tmpfs tmpfs 783M 8.0K 783M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Thu Mar 19 10:14:40 2026] EXT4-fs (mmcblk0p2): mounted filesystem ce208fd3-38a8-424a-87a2-cd44114eb820 ro with ordered data mode. Quota mode: none. [Thu Mar 19 10:14:42 2026] EXT4-fs (mmcblk0p2): re-mounted ce208fd3-38a8-424a-87a2-cd44114eb820 r/w. [Thu Mar 19 10:14:45 2026] EXT4-fs (sda5): mounted filesystem bfb7e6d7-3877-db01-2026-e6d73877db01 r/w with ordered data mode. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro `-/media/USBintern /dev/sda5 ext4 rw,noatime Files in neuralgic directories: /var: 1.2G /var/ 293M /var/log 292M /var/log/journal/486bb6fc0ef2491bae34baf22dc43901 292M /var/log/journal 203M /var/cache Archived and active journals take up 300.4M in the file system. /opt/iobroker/backups: 76K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 400M /opt/iobroker/iobroker-data/ 282M /opt/iobroker/iobroker-data/files 96M /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: 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 24M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.70a15e1f.js.map 18M /opt/iobroker/iobroker-data/files/echarts/preview/static/js/main.5fe9c7da.js.map 14M /opt/iobroker/iobroker-data/objects.jsonl USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' No nvbackup.json found. *** NodeJS-Installation *** /usr/bin/nodejs v22.22.1 /usr/bin/node v22.22.1 /usr/bin/npm 10.9.4 /usr/bin/npx 10.9.4 ✓ Node.js installation is correct nodejs: Installed: 22.22.1-1nodesource1 Candidate: 22.22.1-1nodesource1 Version table: *** 22.22.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.22.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 20.19.2+dfsg-1+deb13u1 500 500 http://deb.debian.org/debian-security trixie-security/main arm64 Packages 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: iobroker iobroker (version: 7.0.7, hostname: iobroker , alive, uptime: 93699) Core adapters versions js-controller: 7.0.7 admin: 7.7.22 javascript: 9.0.18 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : iobroker - enabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.device-watcher.0 : device-watcher : iobroker - enabled + system.adapter.deyeidc.0 : deyeidc : iobroker - enabled, port: 8899 + system.adapter.echarts.0 : echarts : iobroker - enabled + system.adapter.email.0 : email : iobroker - enabled + system.adapter.energiefluss.0 : energiefluss : iobroker - enabled system.adapter.flot.0 : flot : iobroker - enabled + system.adapter.fritzdect.0 : fritzdect : iobroker - enabled + system.adapter.ham.0 : ham : iobroker - enabled + system.adapter.history.0 : history : iobroker - enabled + system.adapter.hs100.0 : hs100 : iobroker - enabled + system.adapter.iot.0 : iot : iobroker - enabled + system.adapter.jarvis.0 : jarvis : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.lovelace.0 : lovelace : iobroker - enabled, port: 8091, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.onvif.0 : onvif : iobroker - enabled, port: 80, 7575, 8000, 8080, 8081, 8899,554,2020 + system.adapter.ping.0 : ping : iobroker - enabled + system.adapter.rpi2.0 : rpi2 : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.statistics.0 : statistics : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.deyeidc.0 : deyeidc : iobroker - enabled, port: 8899 + system.adapter.lovelace.0 : lovelace : iobroker - enabled, port: 8091, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.onvif.0 : onvif : iobroker - enabled, port: 80, 7575, 8000, 8080, 8081, 8899,554,2020 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - 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.22 , installed 7.7.22 Adapter "alexa2" : 3.27.4 , installed 3.27.4 Adapter "backitup" : 3.3.14 , installed 3.3.14 Adapter "device-watcher": 2.15.5 , installed 2.15.5 Adapter "deyeidc" : 0.3.1 , installed 0.3.1 Adapter "echarts" : 1.9.2 , installed 1.9.2 Adapter "email" : 2.0.4 , installed 2.0.4 Adapter "energiefluss" : 3.6.2 , installed 3.6.2 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "fritzdect" : 2.6.2 , installed 2.6.1 [Updatable] Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hs100" : 3.0.5 , installed 3.0.5 Adapter "iot" : 5.0.7 , installed 5.0.7 Adapter "jarvis" : 3.1.8 , installed 3.1.8 Adapter "javascript" : 9.0.18 , installed 9.0.18 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "lovelace" : 5.0.5 , installed 5.0.5 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "onvif" : 1.1.4 , installed 1.1.4 Adapter "ping" : 1.7.9 , installed 1.7.9 Adapter "rpi2" : 2.4.0 , installed 3.0.2 Adapter "shelly" : 10.5.2 , installed 10.5.2 Adapter "socketio" : 6.7.1 , installed 7.0.8 Adapter "sonoff" : 3.2.1 , installed 3.2.1 Adapter "statistics" : 2.4.0 , installed 2.4.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "ws" : 2.6.2 , installed 3.0.19 Objects and States Please stand by - This may take a while Objects: 5987 States: 4919 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://archive.raspberrypi.com/debian trixie InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending systemupdates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 8367 990/exim4 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 8380 715/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 5946 715/iobroker.js-con tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 9626 1368/io.sonoff.0 tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1001 6981 1308/io.mqtt.0 tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 9793 1481/io.jarvis.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 7402 728/sshd: /usr/sbin tcp6 0 0 :::8081 :::* LISTEN 1001 7715 1006/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 11457 1565/io.web.0 tcp6 0 0 :::8091 :::* LISTEN 1001 11340 1494/io.lovelace.0 tcp6 0 0 :::8095 :::* LISTEN 1001 9136 1520/io.onvif.0 tcp6 0 0 ::1:25 :::* LISTEN 0 8368 990/exim4 tcp6 0 0 :::22 :::* LISTEN 0 7404 728/sshd: /usr/sbin udp 0 0 0.0.0.0:58240 0.0.0.0:* 104 5728 514/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 8157 1391/io.ham.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 5726 514/avahi-daemon: r udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 9604 1348/io.shelly.0 udp6 0 0 :::40594 :::* 104 5729 514/avahi-daemon: r udp6 0 0 :::5353 :::* 104 5727 514/avahi-daemon: r *** Log File - Last 25 Lines *** 2026-03-20 09:16:04.654 - info: device-watcher.0 (68279) Number of selected adapters to monitor devices: 6. Loading data from: fritzdectDevices, fullyMQTTDevices, hamDevices, shellyDevices, sonoffDevices, tapoDevices ... 2026-03-20 09:17:10.550 - info: lovelace.0 (1494) Unknown request for /lovelace/default_view 2026-03-20 09:18:08.350 - info: web.0 (1565) ==> Connected system.user.admin from ::ffff:192.168.178.2 2026-03-20 09:18:10.901 - info: web.0 (1565) ==> Connected system.user.admin from ::ffff:192.168.178.2 2026-03-20 09:28:32.265 - info: web.0 (1565) <== Disconnect system.user.admin from ::ffff:192.168.178.2 2026-03-20 09:28:32.266 - info: web.0 (1565) <== Disconnect system.user.admin from ::ffff:192.168.178.2 flot 2026-03-20 09:28:41.509 - info: web.0 (1565) ==> Connected system.user.admin from ::ffff:192.168.178.2 2026-03-20 09:28:49.084 - info: web.0 (1565) <== Disconnect system.user.admin from ::ffff:192.168.178.2 energiefluss.0 2026-03-20 09:29:04.616 - info: jarvis.0 (1481) Client with IP 192.168.178.2 connected. 2026-03-20 09:29:05.511 - info: admin.0 (1006) <== Disconnect system.user.admin from ::ffff:192.168.178.2 admin 2026-03-20 09:29:24.116 - info: jarvis.0 (1481) Client with IP 192.168.178.2 disconnected. 2026-03-20 09:30:00.008 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 09:45:00.014 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 10:00:00.011 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 10:15:00.008 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 10:15:05.139 - info: admin.0 (1006) Adapter rating updated 2026-03-20 10:30:00.007 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 10:39:54.750 - warn: hs100.0 (1291) Socket connection Timeout 192_168_178_51 HS100-1 please reconnect the Device 2026-03-20 10:45:00.010 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 11:00:00.009 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 11:15:00.012 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 11:30:00.009 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 11:45:00.009 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 12:00:00.011 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2 2026-03-20 12:15:00.006 - info: javascript.0 (1136) script.js.common.Projekte.Shelly-Script: Shelly Verbrauch: Verbrauchswerte aktualisiert: 3 | Reboots korrigiert: 0 | Unveränderte Werte: 2Falls noch etwas zu tun ist, erst wieder am Abend...
Und Danke...
Die Ausgabe müsste eigentlich anders aussehen.
cat /etc/apt/sources.list.d/raspi.sources cat /etc/apt/sources.list.d/raspi.list -
Nabend Thomas,
Ich habe gerade ein aktuelles raspiOS mittels Rasperry Pi Imager auf SD Card geschrieben und ebenfalls auf Stand gebracht
Dann habe ich mir die von Dir genannten Verzeichnisse und Dateien angeschaut. Darin müssten ja die originalen und richtigen Inhalte zu finden sein.
Ergebnisse:
Aktuellstes System nach update / full-upgraders@raspiOS:~ $ sudo apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://deb.debian.org/debian-security trixie-security InRelease Get:4 http://archive.raspberrypi.com/debian trixie InRelease [54.9 kB] Get:5 http://archive.raspberrypi.com/debian trixie/main arm64 Packages [422 kB] Fetched 477 kB in 2s (272 kB/s) All packages are up to date. rs@raspiOS:~ $rs@raspiOS:/etc/apt/sources.list.d $ ls -la total 16 drwxr-xr-x 2 root root 4096 Dec 4 15:46 . drwxr-xr-x 9 root root 4096 Dec 4 15:41 .. -rw-r--r-- 1 root root 378 Dec 4 15:39 debian.sources -rw-r--r-- 1 root root 151 Dec 4 15:39 raspi.sources rs@raspiOS:/etc/apt/sources.list.d $rs@raspiOS:/etc/apt/sources.list.d $ nano debian.sources Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie trixie-updates Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.pgp Types: deb URIs: http://deb.debian.org/debian-security/ Suites: trixie-security Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.pgprs@raspiOS:/etc/apt/sources.list.d $ nano raspi.sources Types: deb URIs: http://archive.raspberrypi.com/debian/ Suites: trixie Components: main Signed-By: /usr/share/keyrings/raspberrypi-archive-keyring.pgpIm Original raspiOS gibt es keine raspi.list.
Soll ich die relevanten Dateien im ioB-Produktivsystem anpassen?
Schönen Abend derweil...
Wenns nicht geht, wie man will - muss mans tun, wie man kann. -
Nabend Thomas,
Ich habe gerade ein aktuelles raspiOS mittels Rasperry Pi Imager auf SD Card geschrieben und ebenfalls auf Stand gebracht
Dann habe ich mir die von Dir genannten Verzeichnisse und Dateien angeschaut. Darin müssten ja die originalen und richtigen Inhalte zu finden sein.
Ergebnisse:
Aktuellstes System nach update / full-upgraders@raspiOS:~ $ sudo apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://deb.debian.org/debian-security trixie-security InRelease Get:4 http://archive.raspberrypi.com/debian trixie InRelease [54.9 kB] Get:5 http://archive.raspberrypi.com/debian trixie/main arm64 Packages [422 kB] Fetched 477 kB in 2s (272 kB/s) All packages are up to date. rs@raspiOS:~ $rs@raspiOS:/etc/apt/sources.list.d $ ls -la total 16 drwxr-xr-x 2 root root 4096 Dec 4 15:46 . drwxr-xr-x 9 root root 4096 Dec 4 15:41 .. -rw-r--r-- 1 root root 378 Dec 4 15:39 debian.sources -rw-r--r-- 1 root root 151 Dec 4 15:39 raspi.sources rs@raspiOS:/etc/apt/sources.list.d $rs@raspiOS:/etc/apt/sources.list.d $ nano debian.sources Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie trixie-updates Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.pgp Types: deb URIs: http://deb.debian.org/debian-security/ Suites: trixie-security Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.pgprs@raspiOS:/etc/apt/sources.list.d $ nano raspi.sources Types: deb URIs: http://archive.raspberrypi.com/debian/ Suites: trixie Components: main Signed-By: /usr/share/keyrings/raspberrypi-archive-keyring.pgpIm Original raspiOS gibt es keine raspi.list.
Soll ich die relevanten Dateien im ioB-Produktivsystem anpassen?
Schönen Abend derweil...
@Rico-Sander sagte in Probleme mit dem Device-Watcher:
Im Original raspiOS gibt es keine raspi.list.
Möglich. Da werden wohl inzwischen die neueren Repo-Defintionen bevorzugt.
Mach die Dateien in beiden Systemen gleich. -
@Rico-Sander sagte in Probleme mit dem Device-Watcher:
Im Original raspiOS gibt es keine raspi.list.
Möglich. Da werden wohl inzwischen die neueren Repo-Defintionen bevorzugt.
Mach die Dateien in beiden Systemen gleich.@Thomas-Braun sagte in Probleme mit dem Device-Watcher:
Möglich. Da werden wohl inzwischen die neueren Repo-Defintionen bevorzugt.
Mach die Dateien in beiden Systemen gleich.Es gibt auch noch kleinere Unterschiede zwischen einem puren raspiOS von vor einiger Zeit, welches auf Stand gebracht wurde, und dem heutigen ganz aktuellen System.
Ich werde dann mal die Daten auf gleichen Stand bringen. Danke für Unterstützung.
Und ja, da wäre dann ja noch die Ausgangsproblematik :-)
Inzwischen meldet der Device Watcher auch die DECT-Geräte als Offline. Keine Ahnung, was da schief läuft. Vlt. ein lokales Problem. Kann mir eigentlich nicht vorstellen, dass es mit dem OS zusammenhängt. Falls keiner dazu eine Idee hat, werde ich ihn vermutlich rausschmeißen und die entsprechenden DP der wichtigen Geräte überwachen.Schönes Wochenende...
537
Online32.7k
Benutzer82.5k
Themen1.3m
Beiträge