<![CDATA[[Gelöst] IO Broker auf neuer Hardware]]>Hallo,

nachdem mein Raspberry 3B langsam in die Knie gegangen ist, habe ich mir einen 5er mit 8GB gegönnt.

Aufsetzen lief alles prächtig. IO Broker lässt sich aufrufen und ich habe auch das Backup der 3er zurückgespielt.
IP Adresse habe ich auf die des alten PI's gestellt und der alte PI ist vom Netz.

Problem: Wenn ich Node-RED aufrufe startet der Balken "Lade Nodes", läuft max. 1 Sekunde und bleibt dann für immer stehen.

]]>https://forum.iobroker.net/topic/85209/gelöst-io-broker-auf-neuer-hardwareRSS for NodeTue, 25 Aug 2026 04:24:33 GMTThu, 20 Aug 2026 18:39:08 GMT60<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Mon, 24 Aug 2026 08:08:38 GMT]]>

@MiFuFli sagte:

Der neue PI5 läuft zwar immer noch icht, da ich noch ein paar andere Problemchen bei dem Aufsetzen haben,

Grundsetup:

https://forum.iobroker.net/topic/51869/installation-auf-raspi-einfacher-geht-s-nicht

]]>https://forum.iobroker.net/post/1352313https://forum.iobroker.net/post/1352313Mon, 24 Aug 2026 08:08:38 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Mon, 24 Aug 2026 08:05:31 GMT]]>@MiFuFli

Mach mal bitte ein Issue auf GitHub beim Node Red Adapter.
Auch wenn die Zugänge ungültig geworden sind, sollte der Adapter eigentlich starten und nicht abbrechen

]]>https://forum.iobroker.net/post/1352312https://forum.iobroker.net/post/1352312Mon, 24 Aug 2026 08:05:31 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Mon, 24 Aug 2026 08:00:14 GMT]]>Danke an alle für die Hinweis und Tips.
Es hat tatsächlich an den Alexa und GoogleHome Zugriffen gelegen.
Ich habe ein Backup von dem alten System ohne die beiden Zugänge erstellt und diese dann auf den Raspberry 5 geladen und damit ist Node RED gestartet.

Der neue PI5 läuft zwar immer noch icht, da ich noch ein paar andere Problemchen bei dem Aufsetzen haben, aber das ist dann ggf. ein separates Topic.
@thomas-braun - Danke für den Hinweis mit dem user "pi"!

]]>https://forum.iobroker.net/post/1352311https://forum.iobroker.net/post/1352311Mon, 24 Aug 2026 08:00:14 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Fri, 21 Aug 2026 07:16:01 GMT]]>@MiFuFli

Dann leg das LogIn nochmal neu an:

2026-08-20 22:16:09.725 - warn: node-red.0 (1425) Node-RED: 20 Aug 22:16:09 - [warn] [alexa-smart-home-v3-conf:bb58532e7d7403dd] Re-connecting to Alexa/ Google Home Skill MQTT server: mq-red.cb-net.co.uk, account username: mfuss0601
2026-08-20 22:16:09.835 - error: node-red.0 (1425) Node-RED: 20 Aug 22:16:09 - [error] [alexa-smart-home-v3-conf:bb58532e7d7403dd] Error: Connection refused: Not authorized

Da klemmt es für den user mfuss0601 wohl irgendwo.

Apropos username: Du solltest etwas anderes als 'pi' als user auf dem RaspberryOS verwenden. Steht auch ausdrücklich so in der Anleitung drin...

]]>https://forum.iobroker.net/post/1352060https://forum.iobroker.net/post/1352060Fri, 21 Aug 2026 07:16:01 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Fri, 21 Aug 2026 04:18:42 GMT]]>Vielen Dank für die Idee....
Leider der gleiche Effekt. Node RED hängt beim starten auf "Lade Plugins...."

]]>https://forum.iobroker.net/post/1352052https://forum.iobroker.net/post/1352052Fri, 21 Aug 2026 04:18:42 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 20:36:10 GMT]]>ich sehe

@MiFuFli sagte:

2026-08-20 22:16:04.177 - error: node-red.0 (1425) Node-RED: 20 Aug 22:16:04 - [error] [google-home-conf:f760e8cf91b3705e] ErrorWithReasonCode: Connection refused: Not authorized

du hast backup eingespielt?
da waren flows drin?
irgendwas was eine google authentifizierung benötigt?

meinem empfinden nach, sollte das den start von node red eigentlich nicht behindern. ob das korrekt abgefangen wird weiß ich allerdings nicht

ggfs als workaround:
node red adapter löschen
node red neu installieren
einmal clean den adapter starten und aufrufen
dann nochmal node-red backup einspielen

wenn das so funktioniert, dann einen issue auf github bei
iobroker.node-red
anlegen und das so beschreiben

]]>https://forum.iobroker.net/post/1352047https://forum.iobroker.net/post/1352047Thu, 20 Aug 2026 20:36:10 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 20:23:11 GMT]]>Jetzt stoppt der Fortschrittsbalken von Node-RED bei "Lade Plugins"

Das ist iob diag nach der Neuinstallation:

Script v.2026-06-06

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

Model           : Raspberry Pi 5 Model B Rev 1.1

Docker          : false
Virtualization  : none
Unknown

Kernel          : aarch64
Userland        : 64bit

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

Systemuptime and Load:
 22:15:58 up 8 min,  1 user,  load average: 0.37, 0.40, 0.23
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-20 22:15:58 CEST
           Universal time: Thu 2026-08-20 20:15:58 UTC
                 RTC time: Thu 2026-08-20 20:15:58
                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 gpio i2c spi render input lpadmin 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:        Not found
Desktop:
Session:                tty
Boot Target:            multi-user.target

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            8.5G        1.7G        5.9G         23M        989M        6.7G
Swap:           2.1G          0B        2.1G
Total:           10G        1.7G        8.0G

Active iob-Instances:   10

         8062 M total memory
         1630 M used memory
         1441 M active memory
          680 M inactive memory
         5598 M free memory
          104 M buffer memory
          838 M swap cache
         2047 M total swap
            0 M used swap
         2047 M free swap

*** top - Table Of Processes  ***
top - 22:15:58 up 8 min,  1 user,  load average: 0.37, 0.40, 0.23
Tasks: 177 total,   1 running, 176 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   8062.4 total,   5597.2 free,   1631.6 used,    943.7 buff/cache
MiB Swap:   2048.0 total,   2048.0 free,      0.0 used.   6430.8 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.9G     0  3.9G   0% /dev
tmpfs          tmpfs     1.6G   13M  1.6G   1% /run
/dev/mmcblk0p2 ext4       58G  6.3G   49G  12% /
tmpfs          tmpfs     4.0G     0  4.0G   0% /dev/shm
tmpfs          tmpfs     5.0M   48K  5.0M   1% /run/lock
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs          tmpfs     4.0G   11M  4.0G   1% /tmp
/dev/mmcblk0p1 vfat      505M   66M  439M  14% /boot/firmware
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@ttyAMA10.service
tmpfs          tmpfs     807M   32K  807M   1% /run/user/1000

Messages concerning filesystems in dmesg:
[Thu Aug 20 22:07:14 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
[Thu Aug 20 22:07:14 2026] EXT4-fs (mmcblk0p2): mounted filesystem 15f4c6be-1102-4331-9904-f78e78afd1fd ro with ordered data mode. Quota mode: none.
[Thu Aug 20 22:07:17 2026] EXT4-fs (mmcblk0p2): re-mounted 15f4c6be-1102-4331-9904-f78e78afd1fd r/w.

Show mounted filesystems:
TARGET           SOURCE         FSTYPE OPTIONS
/                /dev/mmcblk0p2 ext4   rw,noatime,commit=600
`-/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.5G    /var/
240M    /var/cache
234M    /var/cache/apt
184M    /var/lib
148M    /var/lib/apt
Archived and active journals take up 8M in the file system.

/opt/iobroker/backups:
2.7M    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
229M    /opt/iobroker/iobroker-data/
113M    /opt/iobroker/iobroker-data/node-red
111M    /opt/iobroker/iobroker-data/node-red/node_modules
87M     /opt/iobroker/iobroker-data/files
47M     /opt/iobroker/iobroker-data/files/admin.admin

The five largest files in iobroker-data are:
30M     /opt/iobroker/iobroker-data/objects.jsonl
7.5M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BeQV_TGa.js
3.7M    /opt/iobroker/iobroker-data/files/backitup.admin/custom/assets/index-Byv11PyV.js
3.7M    /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-ZPb95xPG.js
3.7M    /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-IIKn7Ixx.js

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

No Devices found 'by-id'
*** ZigBee Settings ***

⚠ HINT:
Your zigbee.0 COM-Port is NOT matching 'by-id'.
Please check your setting:
tcp

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        tcp://192.168.178.203:7638          -                                   tcp

*** NodeJS-Installation ***

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

✓ Node.js installation is correct

nodejs:
  Installed: 22.23.2-1nodesource1
  Candidate: 22.23.2-1nodesource1
  Version table:
 *** 22.23.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
        100 /var/lib/dpkg/status
     22.23.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     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:
raspberry5          raspberry5 (version: 7.2.2, hostname: raspberry5    , alive, uptime: 514)

Core adapters versions
js-controller:  7.2.2
admin:          7.8.23
javascript:     "javascript" not found

nodejs modules from github:     0


Adapter State
+ system.adapter.admin.0                  : admin                 : raspberry5                               -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.alias-manager.0          : alias-manager         : raspberry5                               - disabled
+ system.adapter.backitup.0               : backitup              : raspberry5                               -  enabled
+ system.adapter.discovery.0              : discovery             : raspberry5                               -  enabled
  system.adapter.mbus.0                   : mbus                  : raspberry5                               - disabled, port: 3493
+ system.adapter.node-red.0               : node-red              : raspberry5                               -  enabled, port: 1880, bind: 0.0.0.0
+ system.adapter.reolink.0                : reolink               : raspberry5                               -  enabled
  system.adapter.smartmeter.0             : smartmeter            : raspberry5                               - disabled
+ system.adapter.systeminfo.0             : systeminfo            : raspberry5                               -  enabled
+ system.adapter.web.0                    : web                   : raspberry5                               -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
+ system.adapter.wireless-mbus.0          : wireless-mbus         : raspberry5                               -  enabled
+ system.adapter.zigbee.0                 : zigbee                : raspberry5                               -  enabled, port: tcp://192.168.178.203:7638

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : raspberry5                               -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.node-red.0               : node-red              : raspberry5                               -  enabled, port: 1880, bind: 0.0.0.0
+ system.adapter.web.0                    : web                   : raspberry5                               -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
+ system.adapter.zigbee.0                 : zigbee                : raspberry5                               -  enabled, port: tcp://192.168.178.203:7638


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.alias-manager' │ 'alias-manager' │ '2.1.0'  │ 'none'         │
│ 2       │ 'system.adapter.backitup'      │ 'backitup'      │ '3.3.17' │ 'none'         │
│ 3       │ 'system.adapter.discovery'     │ 'discovery'     │ '5.0.0'  │ 'none'         │
│ 4       │ 'system.adapter.mbus'          │ 'mbus'          │ '2.7.0'  │ 'none'         │
│ 5       │ 'system.adapter.node-red'      │ 'node-red'      │ '6.0.7'  │ 'none'         │
│ 6       │ 'system.adapter.reolink'       │ 'reolink'       │ '1.4.2'  │ 'none'         │
│ 7       │ 'system.adapter.smartmeter'    │ 'smartmeter'    │ '3.4.0'  │ 'none'         │
│ 8       │ 'system.adapter.socketio'      │ 'socketio'      │ '7.1.3'  │ 'none'         │
│ 9       │ 'system.adapter.systeminfo'    │ 'systeminfo'    │ '1.3.0'  │ 'none'         │
│ 10      │ 'system.adapter.web'           │ 'web'           │ '8.0.0'  │ 'none'         │
│ 11      │ 'system.adapter.wireless-mbus' │ 'wireless-mbus' │ '0.10.2' │ 'none'         │
│ 12      │ 'system.adapter.ws'            │ 'ws'            │ '4.1.0'  │ 'none'         │
│ 13      │ 'system.adapter.zigbee'        │ 'zigbee'        │ '3.4.5'  │ 'none'         │
└─────────┴────────────────────────────────┴─────────────────┴──────────┴────────────────┘


ioBroker-Adapter Versions and update status
Used repository: stable
Adapter    "admin"        : 7.8.23   , installed 7.8.23
Adapter    "alias-manager": 2.1.0    , installed 2.1.0
Adapter    "backitup"     : 3.3.17   , installed 3.3.17
Adapter    "discovery"    : 5.0.0    , installed 5.0.0
Controller "js-controller": 7.2.2    , installed 7.2.2
Adapter    "mbus"         : 2.7.0    , installed 2.7.0
Adapter    "node-red"     : 6.0.7    , installed 6.0.7
Adapter    "reolink"      : 1.4.2    , installed 1.4.2
Adapter    "smartmeter"   : 3.4.0    , installed 3.4.0
Adapter    "socketio"     : 7.1.3    , installed 7.1.3
Adapter    "systeminfo"   : 1.3.0    , installed 1.3.0
Adapter    "web"          : 8.0.0    , installed 8.0.0
Adapter    "wireless-mbus": 0.10.2   , installed 0.10.2
Adapter    "ws"           : 4.1.0    , installed 4.1.0
Adapter    "zigbee"       : 3.5.5    , installed 3.4.5  [Updatable]


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

Objects:        791
States:         607

*** OS-Repositories and Updates ***

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
Reading package lists...

Pending systemupdates: 0

*** Listening Ports ***
Netid State  Recv-Q Send-Q               Local Address:Port          Peer Address:PortProcess
udp   UNCONN 0      0                          0.0.0.0:mdns               0.0.0.0:*    users:(("avahi-daemon",pid=659,fd=12))
udp   UNCONN 0      0                          0.0.0.0:53170              0.0.0.0:*    users:(("avahi-daemon",pid=659,fd=14))
udp   UNCONN 0      0                          0.0.0.0:sunrpc             0.0.0.0:*    users:(("rpcbind",pid=634,fd=5),("systemd",pid=1,fd=118))
udp   UNCONN 0      0                                *:33767                    *:*    users:(("avahi-daemon",pid=659,fd=15))
udp   UNCONN 0      0                                *:mdns                     *:*    users:(("avahi-daemon",pid=659,fd=13))
udp   UNCONN 0      0                                *:sunrpc                   *:*    users:(("rpcbind",pid=634,fd=7),("systemd",pid=1,fd=120))
udp   UNCONN 0      0      [fe80::8aa2:9eff:fef2:8ad1]:dhcpv6-client            *:*    users:(("NetworkManager",pid=718,fd=31))
tcp   LISTEN 0      4096                       0.0.0.0:sunrpc             0.0.0.0:*    users:(("rpcbind",pid=634,fd=4),("systemd",pid=1,fd=117))
tcp   LISTEN 0      128                        0.0.0.0:ssh                0.0.0.0:*    users:(("sshd",pid=1148,fd=6))
tcp   LISTEN 0      511                      127.0.0.1:9000               0.0.0.0:*    users:(("iobroker.js-con",pid=1134,fd=29))
tcp   LISTEN 0      511                      127.0.0.1:9001               0.0.0.0:*    users:(("iobroker.js-con",pid=1134,fd=23))
tcp   LISTEN 0      511                        0.0.0.0:1880               0.0.0.0:*    users:(("node-red",pid=2728,fd=24))
tcp   LISTEN 0      4096                          [::]:sunrpc                [::]:*    users:(("rpcbind",pid=634,fd=6),("systemd",pid=1,fd=119))
tcp   LISTEN 0      128                           [::]:ssh                   [::]:*    users:(("sshd",pid=1148,fd=7))
tcp   LISTEN 0      511                              *:10001                    *:*    users:(("node-red",pid=2728,fd=48))
tcp   LISTEN 0      511                              *:8082                     *:*    users:(("io.web.0",pid=1519,fd=35))
tcp   LISTEN 0      511                              *:tproxy                   *:*    users:(("io.admin.0",pid=1187,fd=40))


*** Log File - Last 25 Lines ***
    at processTimers (node:internal/timers:521:7)
2026-08-20 22:16:04.177  - error: node-red.0 (1425) Node-RED: 20 Aug 22:16:04 - [error] [google-home-conf:f760e8cf91b3705e] ErrorWithReasonCode: Connection refused: Not authorized
    at handleConnack (/opt/iobroker/iobroker-data/node-red/node_modules/node-red-contrib-googlehome/node_modules/mqtt/src/lib/handlers/connack.ts:47:15)
    at handle (/opt/iobroker/iobroker-data/node-red/node_modules/node-red-contrib-googlehome/node_modules/mqtt/src/lib/handlers/index.ts:49:17)
    at work (/opt/iobroker/iobroker-data/node-red/node_modules/node-red-contrib-googlehome/node_modules/mqtt/src/lib/client.ts:795:17)
    at Writable.writable._write (/opt/iobroker/iobroker-data/node-red/node_modules/node-red-contrib-googlehome/node_modules/mqtt/src/lib/client.ts:819:4)
    at writeOrBuffer (/opt/iobroker/iobroker-data/node-red/node_modules/node-red-contrib-googlehome/node_modules/readable-stream/lib/internal/streams/writable.js:336:12)
    at _write (/opt/iobroker/iobroker-data/node-red/node_modules/node-red-contrib-googlehome/node_modules/readable-stream/lib/internal/streams/writable.js:285:10)
    at Writable.write (/opt/iobroker/iobroker-data/node-red/node_modules/node-red-contrib-googlehome/node_modules/readable-stream/lib/internal/streams/writable.js:288:10)
    at Socket.ondata (node:internal/streams/readable:1009:22)
    at Socket.emit (node:events:519:28)
    at addChunk (node:internal/streams/readable:561:12)
2026-08-20 22:16:09.725  - warn: node-red.0 (1425) Node-RED: 20 Aug 22:16:09 - [warn] [alexa-smart-home-v3-conf:bb58532e7d7403dd] Re-connecting to Alexa/ Google Home Skill MQTT server: mq-red.cb-net.co.uk, account username: mfuss0601
2026-08-20 22:16:09.835  - error: node-red.0 (1425) Node-RED: 20 Aug 22:16:09 - [error] [alexa-smart-home-v3-conf:bb58532e7d7403dd] Error: Connection refused: Not authorized
    at MqttClient._handleConnack (/opt/iobroker/iobroker-data/node-red/node_modules/mqtt/lib/client.js:1388:17)
    at MqttClient._handlePacket (/opt/iobroker/iobroker-data/node-red/node_modules/mqtt/lib/client.js:549:12)
    at work (/opt/iobroker/iobroker-data/node-red/node_modules/mqtt/lib/client.js:438:12)
    at Writable.writable._write (/opt/iobroker/iobroker-data/node-red/node_modules/mqtt/lib/client.js:452:5)
    at doWrite (/opt/iobroker/iobroker-data/node-red/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:409:139)
    at writeOrBuffer (/opt/iobroker/iobroker-data/node-red/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:398:5)
    at Writable.write (/opt/iobroker/iobroker-data/node-red/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:307:11)
    at TLSSocket.ondata (node:internal/streams/readable:1009:22)
    at TLSSocket.emit (node:events:519:28)
    at addChunk (node:internal/streams/readable:561:12)
2026-08-20 22:16:14.844  - warn: node-red.0 (1425) Node-RED: 20 Aug 22:16:14 - [warn] [alexa-smart-home-v3-conf:bb58532e7d7403dd] Re-connecting to Alexa/ Google Home Skill MQTT server: mq-red.cb-net.co.uk, account username: mfuss0601

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

]]>https://forum.iobroker.net/post/1352046https://forum.iobroker.net/post/1352046Thu, 20 Aug 2026 20:23:11 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:54:41 GMT]]>@Homoran

korinthenkackermodusan
Das Boottarget hat aber ja nun nix mit dem gebooteten OS zu tun. ;-)

]]>https://forum.iobroker.net/post/1352045https://forum.iobroker.net/post/1352045Thu, 20 Aug 2026 19:54:41 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:47:39 GMT]]>@thomas-braun

Aber nicht lite

@MiFuFli sagte:

Boot Target: graphical.target

]]>https://forum.iobroker.net/post/1352044https://forum.iobroker.net/post/1352044Thu, 20 Aug 2026 19:47:39 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:37:46 GMT]]>@MiFuFli

Das OS ist schon das richtige:

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 13 (trixie)
 Static hostname: raspberry-5-1
       Icon name: computer
          Kernel: Linux 6.18.34+rpt-rpi-2712
    Architecture: arm64
OS is similar to: 
 
Model           : Raspberry Pi 5 Model B Rev 1.1
]]>https://forum.iobroker.net/post/1352043https://forum.iobroker.net/post/1352043Thu, 20 Aug 2026 19:37:46 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:33:58 GMT]]>Ich habe das falsche Betriebssystem ausgewählt :-(
Sorry....
Bin gerade am neu aufsetzten.

]]>https://forum.iobroker.net/post/1352042https://forum.iobroker.net/post/1352042Thu, 20 Aug 2026 19:33:58 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:32:17 GMT]]>

@MiFuFli sagte:

eigentlich schon genau so.

Mit Sicherheit nicht. Dann würde da kein user 'pi' existiern, kein grapical.traget geladen werden und du hättest keine 164 Updates verschludert.

]]>https://forum.iobroker.net/post/1352041https://forum.iobroker.net/post/1352041Thu, 20 Aug 2026 19:32:17 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:24:23 GMT]]>Mhh.... eigentlich schon genau so. Aber ich kann es auch nochmal machen.

]]>https://forum.iobroker.net/post/1352040https://forum.iobroker.net/post/1352040Thu, 20 Aug 2026 19:24:23 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:24:04 GMT]]>@MiFuFli bitte keine gesamte Datei, lediglich relevante Zeilen.

Dabei private Daten entfernen!

Siehe verlinkten Thread

]]>https://forum.iobroker.net/post/1352039https://forum.iobroker.net/post/1352039Thu, 20 Aug 2026 19:24:04 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:22:46 GMT]]>@MiFuFli

Ich weiß nicht, nach welcher Anleitung du das Ding aufgesetzt hast, bestimmt aber nicht danach:

https://forum.iobroker.net/topic/51869/installation-auf-raspi-einfacher-geht-s-nicht

]]>https://forum.iobroker.net/post/1352038https://forum.iobroker.net/post/1352038Thu, 20 Aug 2026 19:22:46 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:22:15 GMT]]>

@MiFuFli sagte:

Pending systemupdates: 164

So viele sollten es nach Neuinstallation niemals sein!
Zieh mal dein Trixie auf aktuellen Stand

@MiFuFli sagte:

> 2026-08-20 21:04:50.439  - error: node-red.0 (1814) Node-RED: 20 Aug 21:04:50 - [error] [ads-connection:b4573aee.d36498] Error on connect: check target NetId or routing
> 2026-08-20 21:04:50.552  - error: node-red.0 (1814) Node-RED: 20 Aug 21:04:50 - [error] [function:5ed85a4eda4f2d46] TypeError: msg.payload.toFixed is not a function
>     at Function node:5ed85a4eda4f2d46:2:26
>     at Function node:5ed85a4eda4f2d46:5:3
>     at Script.runInContext (node:vm:149:12)
>     at processMessage (/opt/iobroker/node_modules/@node-red/nodes/core/function/10-function.js:430:37)
>     at FunctionNode._inputCallback (/opt/iobroker/node_modules/@node-red/nodes/core/function/10-function.js:348:17)
>     at /opt/iobroker/node_modules/@node-red/runtime/lib/nodes/Node.js:214:26
>     at Object.trigger (/opt/iobroker/node_modules/@node-red/util/lib/hooks.js:166:13)
>     at FunctionNode.Node._emitInput (/opt/iobroker/node_modules/@node-red/runtime/lib/nodes/Node.js:206:11)
>     at FunctionNode.Node.emit (/opt/iobroker/node_modules/@node-red/runtime/lib/nodes/Node.js:190:25)
> 2026-08-20 21:04:55.044  - warn: node-red.0 (1814) Node-RED: 20 Aug 21:04:55 - [warn] [alexa-smart-home-v3-conf:bb58532e7d7403dd] Re-connecting to Alexa/ Google Home Skill MQTT server: .........., account username: xxxxxxx
> 2026

Gibts da noch mehr im log?

]]>https://forum.iobroker.net/post/1352037https://forum.iobroker.net/post/1352037Thu, 20 Aug 2026 19:22:15 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:23:07 GMT]]>Ich habe die Anweisungen wie genannt durchgeführt. Leider immer noch das selbe Ergebnis. Die Log-Daten findet Ihr oben.
Hier noch die Log.-Datei (ich hoffe im richtigen Format)
iobroker.2026-08-20.html

]]>https://forum.iobroker.net/post/1352034https://forum.iobroker.net/post/1352034Thu, 20 Aug 2026 19:23:07 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 19:21:30 GMT]]>========== Start marking the full check here ===========

Script v.2026-06-06

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

Model           : Raspberry Pi 5 Model B Rev 1.1

Docker          : false
Virtualization  : none
Unknown

Kernel          : aarch64
Userland        : 64bit

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

Systemuptime and Load:
 21:04:27 up 1 min,  2 users,  load average: 1.22, 0.58, 0.22
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-20 21:04:27 CEST
           Universal time: Thu 2026-08-20 19:04:27 UTC
                 RTC time: Thu 2026-08-20 19:04:27
                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:
Boot Target:            graphical.target

System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'.
Please set BootTarget to 'multi-user.target' or run 'iobroker fix'

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            8.5G        1.8G        5.6G         38M        1.1G        6.6G
Swap:           2.1G          0B        2.1G
Total:           10G        1.8G        7.7G

Active iob-Instances:   12

         8062 M total memory
         1759 M used memory
         1741 M active memory
          654 M inactive memory
         5332 M free memory
           93 M buffer memory
         1000 M swap cache
         2047 M total swap
            0 M used swap
         2047 M free swap

*** top - Table Of Processes  ***
top - 21:04:27 up 1 min,  2 users,  load average: 1.22, 0.58, 0.22
Tasks: 222 total,   2 running, 220 sleeping,   0 stopped,   0 zombie
%Cpu(s): 26.9 us,  7.7 sy,  0.0 ni, 61.5 id,  3.8 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem :   8062.4 total,   5323.4 free,   1767.8 used,   1094.9 buff/cache     
MiB Swap:   2048.0 total,   2048.0 free,      0.0 used.   6294.5 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.9G     0  3.9G   0% /dev
tmpfs          tmpfs     1.6G   14M  1.6G   1% /run
/dev/mmcblk0p2 ext4       58G  8.8G   47G  16% /
tmpfs          tmpfs     4.0G  400K  4.0G   1% /dev/shm
tmpfs          tmpfs     5.0M   48K  5.0M   1% /run/lock
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs          tmpfs     4.0G  2.6M  4.0G   1% /tmp
/dev/mmcblk0p1 vfat      505M   87M  418M  18% /boot/firmware
tmpfs          tmpfs     807M  256K  806M   1% /run/user/1000
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@ttyAMA10.service

Messages concerning filesystems in dmesg:
[Thu Aug 20 21:02:34 2026] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
[Thu Aug 20 21:02:34 2026] EXT4-fs (mmcblk0p2): mounted filesystem 8abab6b9-ef90-4fee-ae3d-91079bfae7c1 ro with ordered data mode. Quota mode: none.
[Thu Aug 20 21:02:36 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.5G    /var/
216M    /var/lib
215M    /var/cache
211M    /var/cache/apt
150M    /var/lib/apt
Archived and active journals take up 8M in the file system.

/opt/iobroker/backups:
2.8M    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
208M    /opt/iobroker/iobroker-data/
113M    /opt/iobroker/iobroker-data/node-red
111M    /opt/iobroker/iobroker-data/node-red/node_modules
87M     /opt/iobroker/iobroker-data/files
47M     /opt/iobroker/iobroker-data/files/admin.admin

The five largest files in iobroker-data are:
8.3M    /opt/iobroker/iobroker-data/objects.jsonl
7.5M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BeQV_TGa.js
3.7M    /opt/iobroker/iobroker-data/files/backitup.admin/custom/assets/index-Byv11PyV.js
3.7M    /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-ZPb95xPG.js
3.7M    /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-IIKn7Ixx.js

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

No Devices found 'by-id'
*** ZigBee Settings ***

⚠ HINT:
Your zigbee.0 COM-Port is NOT matching 'by-id'.
Please check your setting:
tcp

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        tcp://192.168.178.203:7638          -                                   tcp      

*** NodeJS-Installation ***

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

✓ Node.js installation is correct

nodejs:
  Installed: 22.23.2-1nodesource1
  Candidate: 22.23.2-1nodesource1
  Version table:
 *** 22.23.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
        100 /var/lib/dpkg/status
     22.23.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     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:
raspberry-5-1       raspberry-5-1 (version: 7.2.2, hostname: raspberry-5-1 , alive, uptime: 110)

Core adapters versions
js-controller:  7.2.2
admin:          7.8.23
javascript:     "javascript" not found

nodejs modules from github:     0


Adapter State
+ system.adapter.admin.0                  : admin                 : raspberry-5-1                            -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.alias-manager.0          : alias-manager         : raspberry-5-1                            - disabled
+ system.adapter.backitup.0               : backitup              : raspberry-5-1                            -  enabled
+ system.adapter.discovery.0              : discovery             : raspberry-5-1                            -  enabled
+ system.adapter.mbus.0                   : mbus                  : raspberry-5-1                            -  enabled, port: 3493
+ system.adapter.node-red.0               : node-red              : raspberry-5-1                            -  enabled, port: 1880, bind: 0.0.0.0
+ system.adapter.reolink.0                : reolink               : raspberry-5-1                            -  enabled
+ system.adapter.smartmeter.0             : smartmeter            : raspberry-5-1                            -  enabled
+ system.adapter.systeminfo.0             : systeminfo            : raspberry-5-1                            -  enabled
+ system.adapter.web.0                    : web                   : raspberry-5-1                            -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
+ system.adapter.wireless-mbus.0          : wireless-mbus         : raspberry-5-1                            -  enabled
+ system.adapter.zigbee.0                 : zigbee                : raspberry-5-1                            -  enabled, port: tcp://192.168.178.203:7638

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : raspberry-5-1                            -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.mbus.0                   : mbus                  : raspberry-5-1                            -  enabled, port: 3493
+ system.adapter.node-red.0               : node-red              : raspberry-5-1                            -  enabled, port: 1880, bind: 0.0.0.0
+ system.adapter.web.0                    : web                   : raspberry-5-1                            -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
+ system.adapter.zigbee.0                 : zigbee                : raspberry-5-1                            -  enabled, port: tcp://192.168.178.203:7638


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.alias-manager' │ 'alias-manager' │ '2.1.0'  │ 'none'         │
│ 2       │ 'system.adapter.backitup'      │ 'backitup'      │ '3.3.17' │ 'none'         │
│ 3       │ 'system.adapter.discovery'     │ 'discovery'     │ '5.0.0'  │ 'none'         │
│ 4       │ 'system.adapter.mbus'          │ 'mbus'          │ '2.7.0'  │ 'none'         │
│ 5       │ 'system.adapter.node-red'      │ 'node-red'      │ '6.0.7'  │ 'none'         │
│ 6       │ 'system.adapter.reolink'       │ 'reolink'       │ '1.4.2'  │ 'none'         │
│ 7       │ 'system.adapter.smartmeter'    │ 'smartmeter'    │ '3.4.0'  │ 'none'         │
│ 8       │ 'system.adapter.socketio'      │ 'socketio'      │ '7.1.3'  │ 'none'         │
│ 9       │ 'system.adapter.systeminfo'    │ 'systeminfo'    │ '1.3.0'  │ 'none'         │
│ 10      │ 'system.adapter.web'           │ 'web'           │ '8.0.0'  │ 'none'         │
│ 11      │ 'system.adapter.wireless-mbus' │ 'wireless-mbus' │ '0.10.2' │ 'none'         │
│ 12      │ 'system.adapter.ws'            │ 'ws'            │ '4.1.0'  │ 'none'         │
│ 13      │ 'system.adapter.zigbee'        │ 'zigbee'        │ '3.4.5'  │ 'none'         │
└─────────┴────────────────────────────────┴─────────────────┴──────────┴────────────────┘


ioBroker-Adapter Versions and update status
Used repository: stable
Adapter    "admin"        : 7.8.23   , installed 7.8.23
Adapter    "alias-manager": 2.1.0    , installed 2.1.0
Adapter    "backitup"     : 3.3.17   , installed 3.3.17
Adapter    "discovery"    : 5.0.0    , installed 5.0.0
Controller "js-controller": 7.2.2    , installed 7.2.2
Adapter    "mbus"         : 2.7.0    , installed 2.7.0
Adapter    "node-red"     : 6.0.7    , installed 6.0.7
Adapter    "reolink"      : 1.4.2    , installed 1.4.2
Adapter    "smartmeter"   : 3.4.0    , installed 3.4.0
Adapter    "socketio"     : 7.1.3    , installed 7.1.3
Adapter    "systeminfo"   : 1.3.0    , installed 1.3.0
Adapter    "web"          : 8.0.0    , installed 8.0.0
Adapter    "wireless-mbus": 0.10.2   , installed 0.10.2
Adapter    "ws"           : 4.1.0    , installed 4.1.0
Adapter    "zigbee"       : 3.5.5    , installed 3.4.5  [Updatable]


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

Objects:        772
States:         606

*** OS-Repositories and Updates ***

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
Reading package lists...

Pending systemupdates: 164

*** Listening Ports ***
Netid State  Recv-Q Send-Q                            Local Address:Port          Peer Address:PortProcess                                                  
udp   UNCONN 0      0                                192.168.178.15:54399              0.0.0.0:*    users:(("rpi-connectd",pid=1269,fd=12))                 
udp   UNCONN 0      0                                       0.0.0.0:mdns               0.0.0.0:*    users:(("rpi-connectd",pid=1269,fd=8))                  
udp   UNCONN 0      0                                       0.0.0.0:mdns               0.0.0.0:*    users:(("avahi-daemon",pid=680,fd=12))                  
udp   UNCONN 0      0                                       0.0.0.0:59551              0.0.0.0:*    users:(("avahi-daemon",pid=680,fd=14))                  
udp   UNCONN 0      0                                       0.0.0.0:59769              0.0.0.0:*    users:(("rpi-connectd",pid=1269,fd=16))                 
udp   UNCONN 0      0                                       0.0.0.0:36129              0.0.0.0:*    users:(("rpi-connectd",pid=1269,fd=19))                 
udp   UNCONN 0      0                                       0.0.0.0:36657              0.0.0.0:*    users:(("rpi-connectd",pid=1269,fd=20))                 
udp   UNCONN 0      0                                       0.0.0.0:sunrpc             0.0.0.0:*    users:(("rpcbind",pid=652,fd=5),("systemd",pid=1,fd=83))
udp   UNCONN 0      0                                       0.0.0.0:45189              0.0.0.0:*    users:(("rpi-connectd",pid=1269,fd=10))                 
udp   UNCONN 0      0                                             *:mdns                     *:*    users:(("rpi-connectd",pid=1269,fd=9))                  
udp   UNCONN 0      0                                             *:mdns                     *:*    users:(("avahi-daemon",pid=680,fd=13))                  
udp   UNCONN 0      0                                             *:55432                    *:*    users:(("avahi-daemon",pid=680,fd=15))                  
udp   UNCONN 0      0                                             *:55960                    *:*    users:(("rpi-connectd",pid=1269,fd=14))                 
udp   UNCONN 0      0       [2003:f9:5718:8d00:8aa2:9eff:fef2:8ad1]:40902                    *:*    users:(("rpi-connectd",pid=1269,fd=15))                 
udp   UNCONN 0      0                                             *:53299                    *:*    users:(("rpi-connectd",pid=1269,fd=11))                 
udp   UNCONN 0      0                                             *:sunrpc                   *:*    users:(("rpcbind",pid=652,fd=7),("systemd",pid=1,fd=85))
udp   UNCONN 0      0      [fd67:8f5c:ad89:9f4:8aa2:9eff:fef2:8ad1]:37169                    *:*    users:(("rpi-connectd",pid=1269,fd=17))                 
udp   UNCONN 0      0                   [fe80::8aa2:9eff:fef2:8ad1]:dhcpv6-client            *:*    users:(("NetworkManager",pid=789,fd=24))                
udp   UNCONN 0      0                   [fe80::8aa2:9eff:fef2:8ad1]:49818                    *:*    users:(("rpi-connectd",pid=1269,fd=18))                 
udp   UNCONN 0      0                                             *:58297                    *:*    users:(("rpi-connectd",pid=1269,fd=21))                 
tcp   LISTEN 0      4096                                    0.0.0.0:sunrpc             0.0.0.0:*    users:(("rpcbind",pid=652,fd=4),("systemd",pid=1,fd=82))
tcp   LISTEN 0      511                                     0.0.0.0:1880               0.0.0.0:*    users:(("node-red",pid=2907,fd=24))                     
tcp   LISTEN 0      511                                   127.0.0.1:9000               0.0.0.0:*    users:(("iobroker.js-con",pid=1213,fd=29))              
tcp   LISTEN 0      511                                   127.0.0.1:9001               0.0.0.0:*    users:(("iobroker.js-con",pid=1213,fd=23))              
tcp   LISTEN 0      4096                                       [::]:sunrpc                [::]:*    users:(("rpcbind",pid=652,fd=6),("systemd",pid=1,fd=84))
tcp   LISTEN 0      511                                           *:10001                    *:*    users:(("node-red",pid=2907,fd=47))                     
tcp   LISTEN 0      511                                           *:tproxy                   *:*    users:(("io.admin.0",pid=1775,fd=39))                   
tcp   LISTEN 0      511                                           *:8082                     *:*    users:(("io.web.0",pid=2323,fd=35))                     


*** Log File - Last 25 Lines ***
2026-08-20 21:04:50.148  - info: node-red.0 (2907) 31c1e62c564880b1: Automatic objects creation is not enabled. You can enable it in the node configuration
2026-08-20 21:04:50.169  - info: node-red.0 (2907) 96c3a28711c8f018: "ioBroker in" Cannot set state of non-existing object "mbus.0.EMU-2748.data.3-0-Current".
2026-08-20 21:04:50.169  - info: node-red.0 (2907) 96c3a28711c8f018: Automatic objects creation is not enabled. You can enable it in the node configuration
2026-08-20 21:04:50.275  - info: node-red.0 (2907) d66daa294bed4485: "ioBroker in" Cannot set state of non-existing object "mbus.0.EMU-2768.data.5-0-Current".
2026-08-20 21:04:50.276  - info: node-red.0 (2907) d66daa294bed4485: Automatic objects creation is not enabled. You can enable it in the node configuration
2026-08-20 21:04:50.297  - info: node-red.0 (2907) 8437c76b3a6fcd57: "ioBroker in" Cannot set state of non-existing object "mbus.0.EMU-2768.data.3-0-Current".
2026-08-20 21:04:50.297  - info: node-red.0 (2907) 8437c76b3a6fcd57: Automatic objects creation is not enabled. You can enable it in the node configuration
2026-08-20 21:04:50.439  - error: node-red.0 (1814) Node-RED: 20 Aug 21:04:50 - [error] [ads-connection:b4573aee.d36498] Error on connect: check target NetId or routing
2026-08-20 21:04:50.552  - error: node-red.0 (1814) Node-RED: 20 Aug 21:04:50 - [error] [function:5ed85a4eda4f2d46] TypeError: msg.payload.toFixed is not a function
    at Function node:5ed85a4eda4f2d46:2:26
    at Function node:5ed85a4eda4f2d46:5:3
    at Script.runInContext (node:vm:149:12)
    at processMessage (/opt/iobroker/node_modules/@node-red/nodes/core/function/10-function.js:430:37)
    at FunctionNode._inputCallback (/opt/iobroker/node_modules/@node-red/nodes/core/function/10-function.js:348:17)
    at /opt/iobroker/node_modules/@node-red/runtime/lib/nodes/Node.js:214:26
    at Object.trigger (/opt/iobroker/node_modules/@node-red/util/lib/hooks.js:166:13)
    at FunctionNode.Node._emitInput (/opt/iobroker/node_modules/@node-red/runtime/lib/nodes/Node.js:206:11)
    at FunctionNode.Node.emit (/opt/iobroker/node_modules/@node-red/runtime/lib/nodes/Node.js:190:25)
2026-08-20 21:04:55.044  - warn: node-red.0 (1814) Node-RED: 20 Aug 21:04:55 - [warn] [alexa-smart-home-v3-conf:bb58532e7d7403dd] Re-connecting to **priivate Daten entfernt!**
2026-08-20 21:04:55.522  - info: smartmeter.0 (1949) Error: No or too long answer from Serial Device after last request.
2026-08-20 21:04:55.522  - warn: smartmeter.0 (1949) No or too long answer from Serial Device after last request.
2026-08-20 21:05:01.524  - info: smartmeter.0 (1949) Error: No or too long answer from Serial Device after last request.
2026-08-20 21:05:01.525  - warn: smartmeter.0 (1949) No or too long answer from Serial Device after last request.
2026-08-20 21:05:07.527  - info: smartmeter.0 (1949) Error: No or too long answer from Serial Device after last request.
2026-08-20 21:05:07.527  - warn: smartmeter.0 (1949) No or too long answer from Serial Device after last request.

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

]]>https://forum.iobroker.net/post/1352033https://forum.iobroker.net/post/1352033Thu, 20 Aug 2026 19:21:30 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 18:59:56 GMT]]>

@MiFuFli sagte:

Meinst Du mit log diag das?

Bitte keine Screenshots von Konsolentexten.
Und zuerst mal

iob stop
iob fix 
sudo reboot

durchführen. Danach nochmal

iob diag

Kann aber auch sein, dass nodered dann schon läuft.

]]>https://forum.iobroker.net/post/1352032https://forum.iobroker.net/post/1352032Thu, 20 Aug 2026 18:59:56 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 18:58:46 GMT]]>

@MiFuFli sagte:

Meinst Du mit log diag das?

Jein!
Einmal das log ("Protokolle")
Und zum anderen die Ausgabe von iob diag

Siehe auchbim Link.

]]>https://forum.iobroker.net/post/1352030https://forum.iobroker.net/post/1352030Thu, 20 Aug 2026 18:58:46 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 18:55:15 GMT]]>2026-08-20 20_53_39-raspberry-5-1 remote shell – Raspberry Pi Connect.png
Meinst Du mit log diag das?

]]>https://forum.iobroker.net/post/1352029https://forum.iobroker.net/post/1352029Thu, 20 Aug 2026 18:55:15 GMT<![CDATA[Reply to [Gelöst] IO Broker auf neuer Hardware on Thu, 20 Aug 2026 18:43:01 GMT]]>

@MiFuFli sagte:

läuft max. 1 Sekunde und bleibt dann für immer stehen.

Und im log und ̀iob diag steht nichts?

https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge

]]>https://forum.iobroker.net/post/1352026https://forum.iobroker.net/post/1352026Thu, 20 Aug 2026 18:43:01 GMT