RaspberryMatic RPI-RF-MOD with RPI5

[RacingHell]

Hi,

after upgrading my hardware from rpi3 to rpi5 + USB3 SSD, I finally managed to get running everything fine again, except the rf module HAT. Does anyone know, if RPI-RF-MOD should work with recent build OS 11.4?

The necessary lines to change in config.txt seem to be slightly different compared to the latest documentation. I needed to add one or two missing lines. If the cfg is of interest, I can post it later.

As far I can see, RaspberryMatic Addon (and current Snapshots) can’t find my module. It still works on my old setup, which I counter checked.

Mounting /data as /usr/local (Home Assistant Add-On): OK
Starting watchdog...
Identifying host system: Raspberry Pi 5 Model B Rev 1.0 (oci), OK
Initializing RTC Clock: onboard, OK
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.1, OK
Identifying Homematic RF-Hardware: HmRF: n/a, HmIP: n/a, OK
Updating Homematic RF-Hardware: no GPIO/USB connected RF-hardware found
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: ...OK
Starting ReGaHss: .OK
Starting CloudMatic: disabled
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: 3.73.9.20231130 (raspmatic_oci_arm64)

[jens-maus]

It seems there is actually a bug in the current config.txt of the RaspberryPi5 version of HomeAssistantOS. In addition to the usual dtoverlay block to enable support for the RPI-RF-MOD in the /mnt/boot/config.txt file:

# 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

Please also add the following line which seems to be necessary at the moment:

overlay_prefix=slot-A/overlays/

Then the RaspberryPi bootloader should be hopefully able to correctly load all necessary device tree overlays for the RPI-RF-MOD

[RacingHell]

Works like a charm!

Vielen Dank Jens! 💪

[Jack-Dapid]

Thanks @jens-maus It did not work for with a 8GB RaspberryPi5 and RaspberryMatic 3.77.6.20240720 and HM-MOD-RPI-PCB
(https://de.elv.com/p/elv-bausatz-homematic-ip-funkmodul-fuer-raspberry-pi-hm-mod-rpi-pcb-P142141/?itemId=142141)
Any idea? thanks

with:

# add device tree overlay for RPI-RF-MOD
dtoverlay=rpi-rf-mod
overlay_prefix=slot-A/overlays/

and the log:

fsck 1.47.0 (5-Feb-2023)
userfs: clean, 5931/891184 files, 112875/3563516 blocks
Starting watchdog...
Identifying host system: [E] Failed to initialize VCHI (ret=-1)
[E] Failed to initialize VCHI (ret=-1)
[E] Failed to initialize VCHI (ret=-1)
VCHI initialization failed
Raspberry Pi 5 Model B Rev 1.0 (rpi5), OK
Initializing ZRAM Swap: OK
Initializing RTC Clock: onboard, OK
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
Starting ArgonONE/FAN daemon: no hardware found
Starting PiDesktop daemon: no hardware found
Populating /dev using udev: done
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting system message bus: done
Starting iptables: OK
Starting bluetoothd: disabled
Starting network: eth0:... link up, dhcp, firewall, inet up, 192.168.89.3, wlan0: disabled, OK
Starting Network Interface Plugging Daemon: eth0 wlan0.
Starting chrony: OK
Identifying Homematic RF-Hardware: HmRF: n/a, HmIP: n/a, OK
Updating Homematic RF-Hardware: no GPIO/USB connected RF-hardware found
Starting hs485dLoader: OK
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting sshd: OK
Starting NUT services: disabled
Starting PIco UPS daemon: no hardware found
Starting PiUSV+ daemon: no hardware found
Starting StromPi2 UPS daemon: disabled
Starting S.USV daemon: no hardware found
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: .cryptEnabled true.cryptEnabled true.cryptEnabled trueOK
Setting LAN Gateway keys: OK
Starting hs485d: OK
Starting multimacd: not required
Starting rfd: ...OK
Starting HMIPServer: ....OK
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.77.6.20240720 (raspmatic_rpi5)

[estegewr]

I migrated from a working RPi4 setup (with HM-MOD-RPI-PCB) to RPi5 and run into the same problem: The RF hardware is not discovered during booting as shown on your log. I tried to fix this with the recommendation from @jens-maus in different locations, like in this HA form or RM's GitHub repository.

I added this lines to /boot/config.txt which is now transferred to /boot/firmware/config.txt:

enable_uart=1
dtparam=i2c_arm=on
dtoverlay=miniuart-bt
dtoverlay=rpi-rf-mod
overlay_prefix=slot-A/overlays/

rpi-rf-mod.dtbo was not in in directory /boot/firmware/overlays, so I copied it from a RaspbeerMatic image.
Unfortunately, no success.

Any help is highly appreciated.