Hallo Jens,
danke für deine Antwort!
Ich habe jetzt das RaspberryMatic Add-on nochmal neuinstalliert, um eventuellen Problemen mit dem eingespielten PiVCCU-Backup aus dem Weg zu gehen.
Die Einträge im
boot.log bleiben die gleichen:
Code: Alles auswählen
***** /var/log/boot.log *****
Mounting /data as /usr/local (Home Assistant Add-On): OK
Starting watchdog...
Identifying host system: Raspberry Pi 4 Model B Rev 1.2 (oci), OK
Initializing RTC Clock: 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 iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.0, OK
Identifying Homematic RF-Hardware: ....HmRF: n/a, HmIP: HM-MOD-RPI-PCB/GPIO@fe201000.serial, OK
Updating Homematic RF-Hardware: HM-MOD-RPI-PCB: 2.8.6, not necessary, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: creating new SSL cert... 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: .OK
Starting CloudMatic: OK
Starting NeoServer: OK
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: 3.75.6.20240316 (raspmatic_oci_arm64)
Die Einträge sind (wie zu erwarten) identisch zum Log des Add-ons in Home Assistant:
Der HMIPServer scheint keine Verbindung zum Funkmodul zu bekommen. In der CCU WebUI findet sich folgender Eintrag in den Alarms:
Weiterhin folgende Warnung:
Daraufhin habe ich (wie von dir vorgeschlagen) die Einträge in de
config.txt erneut geprüft. Hier alle Einträge:
Code: Alles auswählen
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details
# HAOS - don't change it!
disable_splash=1
kernel=u-boot.bin
# uncomment for aarch64 bit support
arm_64bit=1
# uncomment to enable primary UART console
#enable_uart=1
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1
# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4
# uncomment for composite PAL
#sdtv_mode=2
# Uncomment to disable continous SD-card poll (for USB SSD)
#dtparam=sd_poll_once=on
# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi
# Uncomment this to enable GPIO support for RPI-RF-MOD/HM-MOD-RPI-PCB
enable_uart=1
dtparam=i2c_arm=on
dtoverlay=miniuart-bt
dtoverlay=rpi-rf-mod
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
# Enable boost from 1.5Ghz to 1.8Ghz on compatible models
arm_boost=1
[all]
#dtoverlay=vc4-fkms-v3d
#max_framebuffers=2
Die Änderungen an der
config.txt habe ich direkt auf der /boot Partition der SD-Karte vorgenommen, nachdem ich die Karte lokal (unter Fedora Linux) gemountet hatte:
Nachdem ich über eventuelle Probleme mit CR/LF (Windows) und LF (Linux) Line Endings und UTF-8 Character Encoding gelesen hatte, habe ich die
config.txt erneut direkt mit Windows-1252 Encoding (ANSI) und LF Line Endings gespeichert.
Andere Punkte die ich anfassen könnte sehe ich gerade nicht. Was habe ich übersehen?
Viele Grüße
Benjamin