Der neue Monatsrückblick für Mai und Juni 2026 ist online!

[Shadowhunter23]

Telegram ist das so eingestellt:

Die Meldung bekommst du weg wenn du den Text in den Einstellungen löscht:

[arnold]

ich dachte der IObroker wird neu gestartet.
das heißt aber 5:04 wird nur der Telegram Adapter gestartet .
und wiso um ca 23 uhr bekomme ich im telegram :
Restarting... (22:56) - hier ändert sich die Zeit
Started! (22:58)
Bitte wähle ein Button

in der log ist um 22:07 was wird da mit host. gestartet
2026-08-05 23:07:23.808 - info: host.RPI4 iobroker.js-controller version 7.2.2 js-controller starting
2026-08-05 23:07:23.815 - info: host.RPI4 Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker
2026-08-05 23:07:23.816 - info: host.RPI4 hostname: RPI4, node: v22.23.1
2026-08-05 23:07:23.817 - info: host.RPI4 ip addresses: 192.168.178.80 fd42:3a51:367:0:dea6:32ff:fe40:6d8a 2003:cc:b73e:9400:dea6:32ff:fe40:6d8a fe80::dea6:32ff:fe40:6d8a
2026-08-05 23:07:27.134 - info: host.RPI4 connected to Objects and States
2026-08-05 23:07:27.187 - info: host.RPI4 added notifications configuration of host
2026-08-05 23:07:35.130 - info: host.RPI4 39 instances found
2026-08-05 23:07:35.267 - info: host.RPI4 starting 36 instances
2026-08-05 23:07:35.965 - info: host.RPI4 Delete state "system.host.RPI4.versions.nodeCurrent"
2026-08-05 23:07:36.431 - info: host.RPI4 Delete state "system.host.RPI4.versions.nodeNewest"
2026-08-05 23:07:36.644 - info: host.RPI4 Delete state "system.host.RPI4.versions.nodeNewestNext"
2026-08-05 23:07:36.656 - info: host.RPI4 Delete state "system.host.RPI4.versions.npmCurrent"
2026-08-05 23:07:36.665 - info: host.RPI4 Delete state "system.host.RPI4.versions.npmNewest"
2026-08-05 23:07:36.688 - info: host.RPI4 instance system.adapter.admin.0 in version "7.8.23" started with pid 1323
2026-08-05 23:07:36.695 - info: host.RPI4 Delete state "system.host.RPI4.versions.npmNewestNext"
2026-08-05 23:07:36.747 - info: host.RPI4 Some obsolete host states deleted.

iobroker.2026-08-05.log.gz

[Meister Mopper]

@arnold sagte:

ich dachte der IObroker wird neu gestartet.

Schau mal nach, ob da ein crontab eingerichtet ist.

crontab -l
sudo crontab -l

[arnold]

[MartinP]

Bei einem Rsapberry Pi würde ich auch nach der Spannungsversorgung schauen - ist ggfs. der Pi selber neu gestartet?

Bei der Hitze könnten es auch Kühlungsprobleme der CPU sein...

[arnold]

aber es ist immer um 23Uhr

[Michael Schmitt]

Für die Helfer=
das scheint der normal restart von Telegram zu sein

2026-08-05 05:03:50.143  - info: tr-064.0 (129874) forEachConfiguredDevice: in GetSpecificHostEntry 20(MI8-sonoffDiy/D8:CE:3A:91:82:1B) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
2026-08-05 05:03:50.159  - warn: wled.0 (130368) Unable to initialise 192.168.178.88 will retry in scheduled interval !
2026-08-05 05:03:56.962  - debug: iot.0 (130102) [AlexaV3::DeviceManager]: ignoring state change event for sonoff.1.DVES_8D856C.POWER1 due to the same value [false]
2026-08-05 05:03:59.133  - warn: mihome-vacuum.0 (129645) State value to set for "mihome-vacuum.0.control.fan_power" has value "90" less than min "101"
2026-08-05 05:04:00.038  - info: telegram.0 (129368) Scheduled restart.
2026-08-05 05:04:00.562  - info: telegram.0 (129368) terminating
2026-08-05 05:04:00.568  - info: tr-064.0 (129874) forEachConfiguredDevice: in GetSpecificHostEntry 4(PC-Markus/2C:41:38:A9:DC:8E) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
2026-08-05 05:04:00.564  - info: telegram.0 (129368) terminating
2026-08-05 05:04:00.566  - info: telegram.0 (129368) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2026-08-05 05:04:00.688  - info: tr-064.0 (129874) forEachConfiguredDevice: in GetSpecificHostEntry 8(android-49158e2b037caa4b/A8:7C:01:A2:77:37) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
2026-08-05 05:04:00.719  - info: tr-064.0 (129874) forEachConfiguredDevice: in GetSpecificHostEntry 9(dlanwireless/F4:06:8D:22:EA:27) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
2026-08-05 05:04:00.962  - info: tr-064.0 (129874) forEachConfiguredDevice: in GetSpecificHostEntry 15(sonoff-1-5837/68:C6:3A:A3:36:CD) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
2026-08-05 05:04:01.056  - info: tr-064.0 (129874) forEachConfiguredDevice: in GetSpecificHostEntry 17(dlanwireless/BC:F2:AF:D2:50:77) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
2026-08-05 05:04:01.149  - info: tr-064.0 (129874) forEachConfiguredDevice: in GetSpecificHostEntry 20(MI8-sonoffDiy/D8:CE:3A:91:82:1B) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
2026-08-05 05:04:01.344  - info: host.RPI4 instance system.adapter.telegram.0 scheduled normal terminated and will be restarted on schedule.
2026-08-05 05:04:01.345  - info: host.RPI4 Restart adapter system.adapter.telegram.0 because enabled
2026-08-05 05:04:03.765  - info: host.RPI4 instance system.adapter.telegram.0 in version "4.1.0" started with pid 161193
2026-08-05 05:04:03.864  - debug: iot.0 (130102) [AlexaV3::DeviceManager]: ignoring state change event for sonoff.1.DVES_DD84B5.POWER1 due to the same value [false]
2026-08-05 05:04:03.867  - debug: iot.0 (130102) [AlexaV3::DeviceManager]: ignoring state change event for sonoff.1.DVES_DD84B5.POWER2 due to the same value [false]
2026-08-05 05:04:05.014  - debug: iot.0 (130102) [AlexaV3::DeviceManager]: ignoring state change event for sonoff.1.DVES_9E3476.POWER due to the same value [false]
2026-08-05 05:04:10.811  - info: telegram.0 (161193) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v22.23.1, js-controller: 7.2.2

und hier scheint die raspi neu zu starten

2026-08-05 23:07:23.808  - info: host.RPI4 iobroker.js-controller version 7.2.2 js-controller starting
2026-08-05 23:07:23.815  - info: host.RPI4 Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker
2026-08-05 23:07:23.816  - info: host.RPI4 hostname: RPI4, node: v22.23.1
2026-08-05 23:07:23.817  - info: host.RPI4 ip addresses: 192.168.178.80 fd42:3a51:367:0:dea6:32ff:fe40:6d8a 2003:cc:b73e:9400:dea6:32ff:fe40:6d8a fe80::dea6:32ff:fe40:6d8a
2026-08-05 23:07:27.134  - info: host.RPI4 connected to Objects and States
2026-08-05 23:07:27.187  - info: host.RPI4 added notifications configuration of host
2026-08-05 23:07:35.130  - info: host.RPI4 39 instances found
2026-08-05 23:07:35.267  - info: host.RPI4 starting 36 instances
2026-08-05 23:07:35.965  - info: host.RPI4 Delete state "system.host.RPI4.versions.nodeCurrent"
2026-08-05 23:07:36.431  - info: host.RPI4 Delete state "system.host.RPI4.versions.nodeNewest"
2026-08-05 23:07:36.644  - info: host.RPI4 Delete state "system.host.RPI4.versions.nodeNewestNext"
2026-08-05 23:07:36.656  - info: host.RPI4 Delete state "system.host.RPI4.versions.npmCurrent"
2026-08-05 23:07:36.665  - info: host.RPI4 Delete state "system.host.RPI4.versions.npmNewest"
2026-08-05 23:07:36.688  - info: host.RPI4 instance system.adapter.admin.0 in version "7.8.23" started with pid 1323
2026-08-05 23:07:36.695  - info: host.RPI4 Delete state "system.host.RPI4.versions.npmNewestNext"
2026-08-05 23:07:36.747  - info: host.RPI4 Some obsolete host states deleted.
2026-08-05 23:11:00.192  - info: host.RPI4 instance system.adapter.influxdb.0 in version "4.0.2" started with pid 1331
2026-08-05 23:11:01.867  - error: admin.0 (1323) admin.0 already running
2026-08-05 23:11:01.872  - warn: admin.0 (1323) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-05 23:11:02.773  - error: host.RPI4 instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-05 23:11:02.774  - info: host.RPI4 Restart adapter system.adapter.admin.0 because enabled
2026-08-05 23:11:04.227  - info: host.RPI4 instance system.adapter.javascript.0 in version "9.0.18" started with pid 1351
2026-08-05 23:11:04.440  - error: influxdb.0 (1331) influxdb.0 already running
2026-08-05 23:11:04.445  - warn: influxdb.0 (1331) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-05 23:11:05.199  - error: host.RPI4 instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-05 23:11:05.200  - info: host.RPI4 Restart adapter system.adapter.influxdb.0 because enabled
2026-08-05 23:11:08.299  - info: host.RPI4 instance system.adapter.scenes.0 in version "4.0.4" started with pid 1363
2026-08-05 23:11:08.518  - error: javascript.0 (1351) javascript.0 already running
2026-08-05 23:11:08.524  - warn: javascript.0 (1351) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-05 23:11:09.302  - error: host.RPI4 instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-05 23:11:09.302  - info: host.RPI4 Restart adapter system.adapter.javascript.0 because enabled
2026-08-05 23:11:10.658  - error: scenes.0 (1363) scenes.0 already running
2026-08-05 23:11:10.662  - warn: scenes.0 (1363) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-05 23:11:12.226  - error: host.RPI4 instance system.adapter.scenes.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-05 23:11:12.227  - info: host.RPI4 Restart adapter system.adapter.scenes.0 because enabled
2026-08-05 23:11:12.300  - info: host.RPI4 instance system.adapter.telegram.0 in version "4.1.0" started with pid 1375
2026-08-05 23:11:16.346  - info: host.RPI4 instance system.adapter.alexa2.0 in version "3.28.3" started with pid 1387
2026-08-05 23:11:16.555  - error: telegram.0 (1375) telegram.0 already running
2026-08-05 23:11:16.561  - warn: telegram.0 (1375) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-05 23:11:17.320  - error: host.RPI4 instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-05 23:11:17.321  - info: host.RPI4 Restart adapter system.adapter.telegram.0 because enabled
2026-08-05 23:11:20.957  - info: host.RPI4 instance system.adapter.telegram.0 in version "4.1.0" started with pid 1399
2026-08-05 23:11:20.985  - info: host.RPI4 instance system.adapter.backitup.0 in version "3.3.17" started with pid 1405
2026-08-05 23:11:21.130  - error: alexa2.0 (1387) alexa2.0 already running
2026-08-05 23:11:21.136  - warn: alexa2.0 (1387) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-05 23:11:21.942  - error: host.RPI4 instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-05 23:11:21.943  - info: host.RPI4 Restart adapter system.adapter.alexa2.0 because enabled
2026-08-05 23:11:24.740  - info: host.RPI4 instance system.adapter.cloud.0 in version "6.0.1" started with pid 1423
2026-08-05 23:11:24.950  - error: backitup.0 (1405) backitup.0 already running
2026-08-05 23:11:24.957  - warn: backitup.0 (1405) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-05 23:11:25.756  - error: host.RPI4 instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-05 23:11:25.757  - info: host.RPI4 Restart adapter system.adapter.backitup.0 because enabled
2026-08-05 23:11:28.424  - info: host.RPI4 instance scheduled system.adapter.ical.0 0,30 * * * *
2026-08-05 23:11:28.440  - info: host.RPI4 instance system.adapter.ical.0 in version "1.20.1" started with pid 1435
2026-08-05 23:11:28.676  - error: cloud.0 (1423) cloud.0 already running
2026-08-05 23:11:28.681  - warn: cloud.0 (1423) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-05 23:11:29.205  - info: telegram.0 (1399) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v22.23.1, js-controller: 7.2.2
2026-08-05 23:11:29.470  - error: host.RPI4 instance system.adapter.cloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-05 23:11:29.471  - info: host.RPI4 Restart adapter system.adapter.cloud.0 because enabled

[arnold]

also die 5 Uhr von Telegram ist mir egal ,kommt schon seit jahren .
aber die ca.23 Uhr nervt
die befehle
crontab -l
sudo crontab -l
zeigen no Crontab

[Meister Mopper]

@Michael-Schmitt

Ich würde den telegram-Neustart ausschalten und hier das Ergebnis von iob diag in </> codetags einstellen.

[Michael Schmitt]

@Meister-Mopper sagte:

@Michael-Schmitt

Ich würde den telegram-Neustart ausschalten und hier das Ergebnis von iob diag in </> codetags einstellen.

ist sicher an @arnold gerichtet ;)

[OliverIO]

@arnold

was mir am log auffällt ist, das sich die log uhrzeit ändert, also zurückspringt

erst
23:06
23:07
23.08
dann wieder
23:07
23:11
23:12

genau mit dem zeitlichen rücksprung startet iobroker neu
weiß nicht ob da iobroker reagiert oder irgendein systemdienst

ein rücksprung um 25 sekunden ist viel.
wie oft wird die systemzeit aktualisiert?

man müsste mal die betriebssystemlogs prüfen.

[arnold]

```bash
Script v.2026-06-06

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 13 (trixie)
 Static hostname: RPI4
       Icon name: computer
          Kernel: Linux 6.18.34+rpt-rpi-v8
    Architecture: arm64
OS is similar to:

Model           : Raspberry Pi 4 Model B Rev 1.1

Docker          : false
Virtualization  : none
Unknown

Kernel          : aarch64
Userland        : 64bit

System was installed 49 days ago (on 2026-06-18).

Systemuptime and Load:
 23:09:36 up 23:59,  2 users,  load average: 0.28, 0.38, 0.36
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: Thu 2026-08-06 23:09:36 CEST
           Universal time: Thu 2026-08-06 21:09:36 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
pi
HOME=/home/pi
GROUPS=pi adm dialout cdrom sudo audio video plugdev games users netdev lpadmin gpio i2c spi render input iobroker

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c

*** DISPLAY-SERVER SETUP ***
Display-Server:         Unknown
Display-Manager:        * lightdm.service - Light Display Manager
Desktop:
Session:                tty
Boot Target:            multi-user.target

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            4.0G        3.6G        172M        3.4M        326M        413M
Swap:           2.1G        1.4G        734M
Total:          6.1G        5.0G        907M

Active iob-Instances:   33

         3795 M total memory
         3401 M used memory
         1968 M active memory
         1059 M inactive memory
          164 M free memory
           39 M buffer memory
          271 M swap cache
         2047 M total swap
         1347 M used swap
          700 M free swap

*** top - Table Of Processes  ***
top - 23:09:37 up 23:59,  2 users,  load average: 0.28, 0.38, 0.36
Tasks: 217 total,   1 running, 216 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.1 us,  2.1 sy,  0.0 ni, 95.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   3795.8 total,    163.9 free,   3401.2 used,    312.4 buff/cache
MiB Swap:   2048.0 total,    700.6 free,   1347.4 used.    394.6 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  1.6G     0  1.6G   0% /dev
tmpfs          tmpfs     760M   15M  745M   2% /run
/dev/mmcblk0p2 ext4       29G   12G   16G  42% /
tmpfs          tmpfs     1.9G  8.0K  1.9G   1% /dev/shm
tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs          tmpfs     1.9G  756K  1.9G   1% /tmp
/dev/mmcblk0p1 vfat      505M   87M  418M  18% /boot/firmware
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs          tmpfs     380M   60K  380M   1% /run/user/1000

Messages concerning filesystems in dmesg:
[Wed Aug  5 23:10:23 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
[Wed Aug  5 23:10:23 2026] EXT4-fs (mmcblk0p2): mounted filesystem 8abab6b9-ef90-4fee-ae3d-91079bfae7c1 ro with ordered data mode. Quota mode: none.
[Wed Aug  5 23:10:26 2026] EXT4-fs (mmcblk0p2): re-mounted 8abab6b9-ef90-4fee-ae3d-91079bfae7c1 r/w.

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

Files in neuralgic directories:
/var:
2.8G    /var/
541M    /var/cache
536M    /var/cache/apt
405M    /var/cache/apt/archives
260M    /var/lib
Archived and active journals take up 13.8M in the file system.

/opt/iobroker/backups:
83M     /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
474M    /opt/iobroker/iobroker-data/
283M    /opt/iobroker/iobroker-data/files
149M    /opt/iobroker/iobroker-data/backup-objects
47M     /opt/iobroker/iobroker-data/files/admin.admin
46M     /opt/iobroker/iobroker-data/files/admin.admin/custom/assets

The five largest files in iobroker-data are:
32M     /opt/iobroker/iobroker-data/objects.jsonl
27M     /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map
16M     /opt/iobroker/iobroker-data/files/matter.admin/assets/index-EdnNzxJx.js
11M     /opt/iobroker/iobroker-data/states.jsonl
9.2M    /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js

USB-Devices by-id:
USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups,
please always prefer the links 'by-id':

/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_96afdeed50c8eb118ac2c4c3de5b81b4-if00-port0

*** ZigBee Settings ***

✓ Your zigbee.0 COM-Port is matching 'by-id'. Very good!

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'

=== ZigBee Port Overview ===
Instance        Configured Port                     Available by-id Port                Status
--------        ----------------                    ----------------------------        ------
zigbee.0        ...c2c4c3de5b81b4-if00-port0        ...c2c4c3de5b81b4-if00-port0        ✓ Matching

*** NodeJS-Installation ***

/usr/bin/nodejs         v22.23.1
/usr/bin/node           v22.23.1
/usr/bin/npm            10.9.8
/usr/bin/npx            10.9.8

✓ Node.js installation is correct

nodejs:
  Installed: 22.23.1-1nodesource1
  Candidate: 22.23.1-1nodesource1
  Version table:
 *** 22.23.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
        100 /var/lib/dpkg/status
     22.23.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.22.3-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.22.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.22.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     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+deb13u2 500
        500 http://deb.debian.org/debian trixie/main arm64 Packages
        500 http://deb.debian.org/debian-security trixie-security/main arm64 Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

Checking for nodejs vulnerability:
No known Vulnerabilities detected!


*** ioBroker-Installation ***
ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
RPI4                RPI4 (version: 7.2.2, hostname: RPI4          , alive, uptime: 86371)

Core adapters versions
js-controller:  7.2.2
admin:          7.8.23
javascript:     9.0.18

nodejs modules from github:     0


Adapter State
+ system.adapter.admin.0                  : admin                 : RPI4                                     -  enabled, port: 6030, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.alexa2.0                 : alexa2                : RPI4                                     -  enabled
+ system.adapter.backitup.0               : backitup              : RPI4                                     -  enabled
+ system.adapter.ble.0                    : ble                   : RPI4                                     -  enabled
+ system.adapter.cloud.0                  : cloud                 : RPI4                                     -  enabled
+ system.adapter.daswetter.0              : daswetter             : RPI4                                     -  enabled
+ system.adapter.discovery.0              : discovery             : RPI4                                     -  enabled
  system.adapter.dwd.0                    : dwd                   : RPI4                                     -  enabled
  system.adapter.flot.0                   : flot                  : RPI4                                     -  enabled
  system.adapter.ical.0                   : ical                  : RPI4                                     -  enabled
  system.adapter.icons-addictive-flavour-png.0: icons-addictive-flavour-png: RPI4                                     -  enabled
+ system.adapter.influxdb.0               : influxdb              : RPI4                                     -  enabled, port: 8086
+ system.adapter.iot.0                    : iot                   : RPI4                                     -  enabled
+ system.adapter.iqontrol.0               : iqontrol              : RPI4                                     -  enabled
+ system.adapter.javascript.0             : javascript            : RPI4                                     -  enabled
+ system.adapter.matter.0                 : matter                : RPI4                                     -  enabled
+ system.adapter.mihome-vacuum.0          : mihome-vacuum         : RPI4                                     -  enabled, port: 54321
+ system.adapter.mqtt.0                   : mqtt                  : RPI4                                     -  enabled, port: 1885, bind: 0.0.0.0
  system.adapter.openweathermap.0         : openweathermap        : RPI4                                     -  enabled
+ system.adapter.parcel.0                 : parcel                : RPI4                                     -  enabled
+ system.adapter.ping.0                   : ping                  : RPI4                                     -  enabled
+ system.adapter.rpi2.1                   : rpi2                  : RPI4                                     -  enabled
+ system.adapter.scenes.0                 : scenes                : RPI4                                     -  enabled
+ system.adapter.simple-api.0             : simple-api            : RPI4                                     -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.sonoff.1                 : sonoff                : RPI4                                     -  enabled, port: 1884, bind: 0.0.0.0
+ system.adapter.sourceanalytix.0         : sourceanalytix        : RPI4                                     -  enabled
+ system.adapter.sourceanalytix.1         : sourceanalytix        : RPI4                                     -  enabled
+ system.adapter.tankerkoenig.0           : tankerkoenig          : RPI4                                     -  enabled
+ system.adapter.telegram.0               : telegram              : RPI4                                     -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.text2command.0           : text2command          : RPI4                                     -  enabled
+ system.adapter.tr-064.0                 : tr-064                : RPI4                                     -  enabled
+ system.adapter.trashschedule.0          : trashschedule         : RPI4                                     -  enabled
  system.adapter.vis.0                    : vis                   : RPI4                                     -  enabled
+ system.adapter.volumio.0                : volumio               : RPI4                                     -  enabled
+ system.adapter.web.0                    : web                   : RPI4                                     -  enabled, port: 6032, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.wled.0                   : wled                  : RPI4                                     -  enabled
+ system.adapter.worx.0                   : worx                  : RPI4                                     -  enabled
+ system.adapter.zigbee.0                 : zigbee                : RPI4                                     -  enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_96afdeed50c8eb118ac2c4c3de5b81b4-if00-port0
  system.adapter.zigbee2mqtt.0            : zigbee2mqtt           : RPI4                                     - disabled

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : RPI4                                     -  enabled, port: 6030, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.influxdb.0               : influxdb              : RPI4                                     -  enabled, port: 8086
+ system.adapter.mihome-vacuum.0          : mihome-vacuum         : RPI4                                     -  enabled, port: 54321
+ system.adapter.mqtt.0                   : mqtt                  : RPI4                                     -  enabled, port: 1885, bind: 0.0.0.0
+ system.adapter.simple-api.0             : simple-api            : RPI4                                     -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.sonoff.1                 : sonoff                : RPI4                                     -  enabled, port: 1884, bind: 0.0.0.0
+ system.adapter.telegram.0               : telegram              : RPI4                                     -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.web.0                    : web                   : RPI4                                     -  enabled, port: 6032, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.zigbee.0                 : zigbee                : RPI4                                     -  enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_96afdeed50c8eb118ac2c4c3de5b81b4-if00-port0


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
┌─────────┬──────────────────────────────────────────────┬───────────────────────────────┬──────────┬────────────────┐
│ (index) │ id                                           │ name                          │ version  │ upgrade policy │
├─────────┼──────────────────────────────────────────────┼───────────────────────────────┼──────────┼────────────────┤
│ 0       │ 'system.adapter.admin'                       │ 'admin'                       │ '7.8.23' │ 'none'         │
│ 1       │ 'system.adapter.alexa2'                      │ 'alexa2'                      │ '3.28.3' │ 'none'         │
│ 2       │ 'system.adapter.backitup'                    │ 'backitup'                    │ '3.3.17' │ 'none'         │
│ 3       │ 'system.adapter.ble'                         │ 'ble'                         │ '0.14.1' │ 'none'         │
│ 4       │ 'system.adapter.cloud'                       │ 'cloud'                       │ '6.0.1'  │ 'none'         │
│ 5       │ 'system.adapter.daswetter'                   │ 'daswetter'                   │ '4.5.3'  │ 'none'         │
│ 6       │ 'system.adapter.discovery'                   │ 'discovery'                   │ '5.0.0'  │ 'none'         │
│ 7       │ 'system.adapter.dwd'                         │ 'dwd'                         │ '2.8.5'  │ 'none'         │
│ 8       │ 'system.adapter.flot'                        │ 'flot'                        │ '1.12.0' │ 'none'         │
│ 9       │ 'system.adapter.ical'                        │ 'ical'                        │ '1.20.1' │ 'none'         │
│ 10      │ 'system.adapter.icons-addictive-flavour-png' │ 'icons-addictive-flavour-png' │ '0.1.0'  │ 'none'         │
│ 11      │ 'system.adapter.influxdb'                    │ 'influxdb'                    │ '4.0.2'  │ 'none'         │
│ 12      │ 'system.adapter.iot'                         │ 'iot'                         │ '6.0.3'  │ 'none'         │
│ 13      │ 'system.adapter.iqontrol'                    │ 'iqontrol'                    │ '3.0.0'  │ 'none'         │
│ 14      │ 'system.adapter.javascript'                  │ 'javascript'                  │ '9.0.18' │ 'none'         │
│ 15      │ 'system.adapter.matter'                      │ 'matter'                      │ '1.3.1'  │ 'none'         │
│ 16      │ 'system.adapter.mihome-vacuum'               │ 'mihome-vacuum'               │ '5.2.0'  │ 'none'         │
│ 17      │ 'system.adapter.mqtt'                        │ 'mqtt'                        │ '6.1.4'  │ 'none'         │
│ 18      │ 'system.adapter.openweathermap'              │ 'openweathermap'              │ '1.4.0'  │ 'none'         │
│ 19      │ 'system.adapter.parcel'                      │ 'parcel'                      │ '0.3.2'  │ 'none'         │
│ 20      │ 'system.adapter.ping'                        │ 'ping'                        │ '1.7.9'  │ 'none'         │
│ 21      │ 'system.adapter.rpi2'                        │ 'rpi2'                        │ '3.0.2'  │ 'none'         │
│ 22      │ 'system.adapter.scenes'                      │ 'scenes'                      │ '4.0.4'  │ 'none'         │
│ 23      │ 'system.adapter.simple-api'                  │ 'simple-api'                  │ '2.8.0'  │ 'none'         │
│ 24      │ 'system.adapter.socketio'                    │ 'socketio'                    │ '7.1.3'  │ 'none'         │
│ 25      │ 'system.adapter.sonoff'                      │ 'sonoff'                      │ '3.3.0'  │ 'none'         │
│ 26      │ 'system.adapter.sourceanalytix'              │ 'sourceanalytix'              │ '0.4.14' │ 'none'         │
│ 27      │ 'system.adapter.tankerkoenig'                │ 'tankerkoenig'                │ '3.4.0'  │ 'none'         │
│ 28      │ 'system.adapter.telegram'                    │ 'telegram'                    │ '4.1.0'  │ 'none'         │
│ 29      │ 'system.adapter.text2command'                │ 'text2command'                │ '4.0.0'  │ 'none'         │
│ 30      │ 'system.adapter.tr-064'                      │ 'tr-064'                      │ '4.3.0'  │ 'none'         │
│ 31      │ 'system.adapter.trashschedule'               │ 'trashschedule'               │ '5.3.0'  │ 'none'         │
│ 32      │ 'system.adapter.vis'                         │ 'vis'                         │ '1.5.6'  │ 'none'         │
│ 33      │ 'system.adapter.volumio'                     │ 'volumio'                     │ '0.9.0'  │ 'none'         │
│ 34      │ 'system.adapter.web'                         │ 'web'                         │ '8.0.0'  │ 'none'         │
│ 35      │ 'system.adapter.wled'                        │ 'wled'                        │ '0.7.3'  │ 'none'         │
│ 36      │ 'system.adapter.worx'                        │ 'worx'                        │ '3.3.0'  │ 'none'         │
│ 37      │ 'system.adapter.ws'                          │ 'ws'                          │ '4.1.0'  │ 'none'         │
│ 38      │ 'system.adapter.zigbee'                      │ 'zigbee'                      │ '3.3.5'  │ 'none'         │
│ 39      │ 'system.adapter.zigbee2mqtt'                 │ 'zigbee2mqtt'                 │ '3.2.2'  │ 'none'         │
└─────────┴──────────────────────────────────────────────┴───────────────────────────────┴──────────┴────────────────┘


ioBroker-Adapter Versions and update status
Used repository: stable
 Objects database error: read ECONNRESET
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
```bash
Script v.2026-06-06

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 13 (trixie)
 Static hostname: RPI4
       Icon name: computer
          Kernel: Linux 6.18.34+rpt-rpi-v8
    Architecture: arm64
OS is similar to:

Model           : Raspberry Pi 4 Model B Rev 1.1

Docker          : false
Virtualization  : none
Unknown

Kernel          : aarch64
Userland        : 64bit

System was installed 49 days ago (on 2026-06-18).

Systemuptime and Load:
 23:09:36 up 23:59,  2 users,  load average: 0.28, 0.38, 0.36
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: Thu 2026-08-06 23:09:36 CEST
           Universal time: Thu 2026-08-06 21:09:36 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
pi
HOME=/home/pi
GROUPS=pi adm dialout cdrom sudo audio video plugdev games users netdev lpadmin gpio i2c spi render input iobroker

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c

*** DISPLAY-SERVER SETUP ***
Display-Server:         Unknown
Display-Manager:        * lightdm.service - Light Display Manager
Desktop:
Session:                tty
Boot Target:            multi-user.target

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            4.0G        3.6G        172M        3.4M        326M        413M
Swap:           2.1G        1.4G        734M
Total:          6.1G        5.0G        907M

Active iob-Instances:   33

         3795 M total memory
         3401 M used memory
         1968 M active memory
         1059 M inactive memory
          164 M free memory
           39 M buffer memory
          271 M swap cache
         2047 M total swap
         1347 M used swap
          700 M free swap

*** top - Table Of Processes  ***
top - 23:09:37 up 23:59,  2 users,  load average: 0.28, 0.38, 0.36
Tasks: 217 total,   1 running, 216 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.1 us,  2.1 sy,  0.0 ni, 95.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   3795.8 total,    163.9 free,   3401.2 used,    312.4 buff/cache
MiB Swap:   2048.0 total,    700.6 free,   1347.4 used.    394.6 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  1.6G     0  1.6G   0% /dev
tmpfs          tmpfs     760M   15M  745M   2% /run
/dev/mmcblk0p2 ext4       29G   12G   16G  42% /
tmpfs          tmpfs     1.9G  8.0K  1.9G   1% /dev/shm
tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs          tmpfs     1.9G  756K  1.9G   1% /tmp
/dev/mmcblk0p1 vfat      505M   87M  418M  18% /boot/firmware
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs          tmpfs     380M   60K  380M   1% /run/user/1000

Messages concerning filesystems in dmesg:
[Wed Aug  5 23:10:23 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
[Wed Aug  5 23:10:23 2026] EXT4-fs (mmcblk0p2): mounted filesystem 8abab6b9-ef90-4fee-ae3d-91079bfae7c1 ro with ordered data mode. Quota mode: none.
[Wed Aug  5 23:10:26 2026] EXT4-fs (mmcblk0p2): re-mounted 8abab6b9-ef90-4fee-ae3d-91079bfae7c1 r/w.

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

Files in neura Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
 Objects database error: connect ECONNREFUSED 127.0.0.1:9001
 States database error: connect ECONNREFUSED 127.0.0.1:9000
Uncaught Rejection: Error: Connection is closed.
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:160:20)
    at Object.onceWrapper (node:events:634:26)
    at Socket.emit (node:events:519:28)
    at TCP.<anonymous> (node:net:347:12)
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:
Error: Connection is closed.
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:160:20)
    at Object.onceWrapper (node:events:634:26)
    at Socket.emit (node:events:519:28)
    at TCP.<anonymous> (node:net:347:12)


Objects and States
Please stand by - This may take a while

Objects:        1
States:         9932

*** OS-Repositories and Updates ***

```bash
Script v.2026-06-06

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 13 (trixie)
 Static hostname: RPI4
       Icon name: computer
          Kernel: Linux 6.18.34+rpt-rpi-v8
    Architecture: arm64
OS is similar to:

Model           : Raspberry Pi 4 Model B Rev 1.1

Docker          : false
Virtualization  : none
Unknown

Kernel          : aarch64
Userland        : 64bit

System was installed 49 days ago (on 2026-06-18).

Systemuptime and Load:
 23:09:36 up 23:59,  2 users,  load average: 0.28, 0.38, 0.36
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: Thu 2026-08-06 23:09:36 CEST
           Universal time: Thu 2026-08-06 21:09:36 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
pi
HOME=/home/pi
GROUPS=pi adm dialout cdrom sudo audio video plugdev games users netdev lpadmin gpio i2c spi render input iobroker

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c

*** DISPLAY-SERVER SETUP ***
Display-Server:         Unknown
Display-Manager:        * lightdm.service - Light Display Manager
Desktop:
Session:                tty
Boot Target:            multi-user.target

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            4.0G        3.6G        172M        3.4M        326M        413M
Swap:           2.1G        1.4G        734M
Total:          6.1G        5.0G        907M

Active iob-Instances:   33

         3795 M total memory
         3401 M used memory
         1968 M active memory
         1059 M inactive memory
          164 M free memory
           39 M buffer memory
          271 M swap cache
         2047 M total swap
         1347 M used swap
          700 M free swap

*** top - Table Of Processes  ***
top - 23:09:37 up 23:59,  2 users,  load average: 0.28, 0.38, 0.36
Tasks: 217 total,   1 running, 216 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.1 us,  2.1 sy,  0.0 ni, 95.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   3795.8 total,    163.9 free,   3401.2 used,    312.4 buff/cache
MiB Swap:   2048.0 total,    700.6 free,   1347.4 used.    394.6 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  1.6G     0  1.6G   0% /dev
tmpfs          tmpfs     760M   15M  745M   2% /run
/dev/mmcblk0p2 ext4       29G   12G   16G  42% /
tmpfs          tmpfs     1.9G  8.0K  1.9G   1% /dev/shm
tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs          tmpfs     1.9G  756K  1.9G   1% /tmp
/dev/mmcblk0p1 vfat      505M   87M  418M  18% /boot/firmware
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs          tmpfs     380M   60K  380M   1% /run/user/1000

Messages concerning filesystems in dmesg:
[Wed Aug  5 23:10:23 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
[Wed Aug  5 23:10:23 2026] EXT4-fs (mmcblk0p2): mounted filesystem 8abab6b9-ef90-4fee-ae3d-91079bfae7c1 ro with ordered data mode. Quota mode: none.
[Wed Aug  5 23:10:26 2026] EXT4-fs (mmcblk0p2): re-mounted 8abab6b9-ef90-4fee-ae3d-91079bfae7c1 r/w.

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

Files in neuraHit: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
Reading package lists...

Pending systemupdates: 142

*** Listening Ports ***
Netid State  Recv-Q Send-Q Local Address:Port    Peer Address:PortProcess
udp   UNCONN 0      0            0.0.0.0:48540        0.0.0.0:*    users:(("avahi-daemon",pid=648,fd=14))
udp   UNCONN 0      0            0.0.0.0:sunrpc       0.0.0.0:*    users:(("rpcbind",pid=624,fd=5),("systemd",pid=1,fd=117))
udp   UNCONN 0      0            0.0.0.0:mdns         0.0.0.0:*    users:(("avahi-daemon",pid=648,fd=12))
udp   UNCONN 0      0                  *:sunrpc             *:*    users:(("rpcbind",pid=624,fd=7),("systemd",pid=1,fd=120))
udp   UNCONN 0      0                  *:39487              *:*    users:(("avahi-daemon",pid=648,fd=15))
udp   UNCONN 0      0                  *:mdns               *:*    users:(("avahi-daemon",pid=648,fd=13))
tcp   LISTEN 0      511        127.0.0.1:9000         0.0.0.0:*    users:(("iobroker.js-con",pid=129789,fd=29))
tcp   LISTEN 1      511        127.0.0.1:9001         0.0.0.0:*    users:(("iobroker.js-con",pid=129789,fd=23))
tcp   LISTEN 0      4096       127.0.0.1:omniorb      0.0.0.0:*    users:(("influxd",pid=1161,fd=3))
tcp   LISTEN 0      128          0.0.0.0:ssh          0.0.0.0:*    users:(("sshd",pid=1178,fd=6))
tcp   LISTEN 0      4096         0.0.0.0:sunrpc       0.0.0.0:*    users:(("rpcbind",pid=624,fd=4),("systemd",pid=1,fd=116))
tcp   LISTEN 0      4096               *:8086               *:*    users:(("influxd",pid=1161,fd=37))
tcp   LISTEN 0      4096               *:3000               *:*    users:(("grafana",pid=1224,fd=9))
tcp   LISTEN 0      128             [::]:ssh             [::]:*    users:(("sshd",pid=1178,fd=7))
tcp   LISTEN 0      4096            [::]:sunrpc          [::]:*    users:(("rpcbind",pid=624,fd=6),("systemd",pid=1,fd=118))


*** Log File - Last 25 Lines ***
2026-08-06 23:13:25.446  - warn: backitup.0 (129945) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-06 23:13:26.361  - error: host.RPI4 instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-06 23:13:26.362  - info: host.RPI4 Restart adapter system.adapter.backitup.0 because enabled
2026-08-06 23:13:28.207  - info: host.RPI4 instance scheduled system.adapter.ical.0 0,30 * * * *
2026-08-06 23:13:28.228  - info: host.RPI4 instance system.adapter.ical.0 in version "1.20.1" started with pid 130011
2026-08-06 23:13:29.237  - error: cloud.0 (129964) cloud.0 already running
2026-08-06 23:13:29.245  - warn: cloud.0 (129964) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-06 23:13:30.070  - error: host.RPI4 instance system.adapter.cloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-06 23:13:30.073  - info: host.RPI4 Restart adapter system.adapter.cloud.0 because enabled
2026-08-06 23:13:32.599  - info: host.RPI4 instance system.adapter.mihome-vacuum.0 in version "5.2.0" started with pid 130030
2026-08-06 23:13:34.059  - info: telegram.0 (129944) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v22.23.1, js-controller: 7.2.2
2026-08-06 23:13:40.010  - info: host.RPI4 instance system.adapter.mqtt.0 in version "6.1.4" started with pid 130051
2026-08-06 23:13:40.818  - info: host.RPI4 instance system.adapter.admin.0 in version "7.8.23" started with pid 130059
2026-08-06 23:13:42.052  - info: host.RPI4 instance system.adapter.influxdb.0 in version "4.0.2" started with pid 130068
2026-08-06 23:13:43.002  - info: host.RPI4 instance scheduled system.adapter.openweathermap.0 23 * * * *
2026-08-06 23:13:43.029  - info: host.RPI4 instance system.adapter.openweathermap.0 in version "1.4.0" started with pid 130079
2026-08-06 23:13:43.903  - error: mihome-vacuum.0 (130030) mihome-vacuum.0 already running
2026-08-06 23:13:43.919  - warn: mihome-vacuum.0 (130030) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-06 23:13:48.859  - info: host.RPI4 instance system.adapter.javascript.0 in version "9.0.18" started with pid 130100
2026-08-06 23:13:49.206  - error: host.RPI4 instance system.adapter.mihome-vacuum.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2026-08-06 23:13:49.208  - info: host.RPI4 Restart adapter system.adapter.mihome-vacuum.0 because enabled
2026-08-06 23:13:51.974  - info: host.RPI4 instance system.adapter.ping.0 in version "1.7.9" started with pid 130108
2026-08-06 23:13:52.733  - error: mqtt.0 (130051) mqtt.0 already running
2026-08-06 23:13:52.748  - warn: mqtt.0 (130051) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2026-08-06 23:13:52.868  - info: host.RPI4 instance system.adapter.scenes.0 in version "4.0.4" started with pid 130119

============= Mark until here for C&P =============

iob diag has finished.

[MartinP]

Würden gemeldete Spannungszusammenbrüche ("Brown out") im dmesg Log den reboot überstehen?

Passiert um diese Zeit ggfs etwas, was viel Strom zieht, z. B. Aktivieren einer USB Festplatte, für Backup?

https://raspberrypi.stackexchange.com/questions/143143/raspberry-pi-3-brownouts-and-under-voltage-issue-with-good-power-supplies

[skvarel]

Ich würde den Cron bei Telegram lassen und nur die Meldung ausschalten. Mache ich seit Jahren so.