I don’t know what drove me, but I thought it is time to do a firmware update (sudo rpi-update) on my RPi5.
All good, except that now all the Homematic devices are no longer connected. Reason seems to be that the RF adapter module is not initialized anymore:
Consequently no RF adapter in Raspberrymatic. Apparently the pi’s firmware update has messed up something in the raspberrymatic docker setup. Sadly, I have no clue how to fix this. Rerunning automatic and/or manual installation as per the Jens Maus Github either throw errors or is not changing anything.
Sure, I just thought that somebody might have had the same issue before.
Anyway, I now managed to kill my RPi completely. It is booting, but doesn’t display its GUI anymore when connecting to it. Looks that I will need to start all over again.
Hi Wally,
I tried to follow the instructions However, somehow I must have damaged my system, because it didn’t boot anymore at some point.
Meanwhile I have done a complete new setup, this time with HA running in a VM on my RPi5, and restored my configuration from a backup. The RFUSB is now loaded by Raspberrymatic, but not used yet. No communication with devices. It is certainly a setup issue, as the IP of the CCU is still the old one.
If I understand the architecture correctly, Raspberrymatic runs as a separate server in a container. I am not sure if the HA backup also saves this container, probably not.
It certainly does, all other add-ons are there and operational. The problem appears to be a wrong server ip for the CCU. The settings still show the address of the old setup. The main difference now is that HA runs as HAOS in a VM.
I’ll be on the road today and will look into it tomorrow.
Meanwhile, after three days of non-functioning, Raspberrymatic appears to have repaired itself. This morning, after an unrelated update of another app, all devices were suddenly communicating again and display signal strengths. All that was left to doy was to redefine the hub in the configuration to activate the entities in HA.
Not that I would understand what happened. I certainly restarted a couple of times in the last days. Anyway, I am glad that it is working again.