Was zeigt dieses Log? Welches Fehler? Kann jemand bitet helfen.

[wled-faq]

What this log means? What is wrong? Can anyone help please:
RaspberryMatic via Home Assistant AddOn; HW: Raspberry Pi; OS: debian 12; HMIP-RFUSB
It was working until I've updated Home Assistant and RaspberryMatic Addon today.

mounting /data as /usr/local (Home Assistant Add-On): OK
Starting watchdog...
Identifying host system: n/a (oci), OK
Initializing RTC Clock: /etc/init.d/S02InitRTC: line 95: can't create /sys/class/i2c-dev/i2c-1/device/new_device: nonexistent directory
/etc/init.d/S02InitRTC: line 97: can't create /sys/class/i2c-dev/i2c-1/device/delete_device: nonexistent directory
sh: write error: Device or resource busy
/etc/init.d/S02InitRTC: line 112: can't create /sys/class/i2c-dev/i2c-1/device/delete_device: nonexistent directory
sh: write error: Device or resource busy
/etc/init.d/S02InitRTC: line 121: can't create /sys/class/i2c-dev/i2c-1/device/delete_device: nonexistent directory
sh: write error: Device or resource busy
/etc/init.d/S02InitRTC: line 134: can't create /sys/class/i2c-dev/i2c-1/device/delete_device: nonexistent directory
no hardware found
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Running seedrng: OK
Initializing System: OK
Setup ca-certificates: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.2, OK
Identifying Homematic RF-Hardware: .../bin/detect_radio_module: error while loading shared libraries: /usr/lib64/libstdc++.so.6: file too short
HmRF: n/a, HmIP: n/a, OK
Updating Homematic RF-Hardware: HMIP-RFUSB: =>4.4.18, /bin/detect_radio_module: error while loading shared libraries: /usr/lib64/libstdc++.so.6: file too short
ERROR ( != 4.4.18)
Identifying Homematic RF-Hardware: .../bin/detect_radio_module: error while loading shared libraries: /usr/lib64/libstdc++.so.6: file too short
HmRF: n/a, HmIP: n/a, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: not required
Starting rfd: no BidCos-RF hardware found
Starting HMIPServer: .......................................................................................................................................................ERROR
Starting ReGaHss: ....................ERROR
Starting CloudMatic: OK
Starting NeoServer: disabled
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: start-stop-daemon: warning: killing process 328: No such process
booted, OK
Finished Boot: 3.73.9.20240130 (raspmatic_oci_arm64)

[jens-maus]

Well, you are obviously using a HomeAssistant Supervised installation. These kind of HA installation are always criticial, especially when it comes to interoperatibility. Thus, please have a look for the Important note block at the very top of the documentation:

https://github.com/jens-maus/RaspberryMatic/wiki/Installation-HomeAssistant#using-homeassistant-supervised

Thus, please consider using HomeAssistantOS instead of running HA within a standard debian environment, which in fact could be easily the reason why the Addon fails now....