Sourcer63
(Johannes)
March 19, 2025, 4:15pm
1
Hello community,
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:
Identifying Homematic RF-Hardware: HmRF: n/a, HmIP: n/a, OK
Updating Homematic RF-Hardware: HMIP-RFUSB: =>4.4.18, ERROR ( != 4.4.18)
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.
Any hints how to cure this?
Thx Johannes
Hello Johannes ,
I think that is where you have to ask or look.
Not a lot that Home Assistant can help with here.
Sourcer63
(Johannes)
March 19, 2025, 4:48pm
3
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.
WallyR
(Wally)
March 19, 2025, 5:13pm
4
I had the same issue once with Debmatic, which is similar to RaspberryMatic.
I had to run a reconfigure of the pvccu, I think.
Here is the thread.
opened 12:22AM - 06 Jun 23 UTC
closed 09:23PM - 07 Jun 23 UTC
I updated my Debmatic to newest version and then lost access to the USB stick.
… I could not find any errors and then tried to install RaspberryMatic instead to see if that worked.
It did not, but in the logs this line occurred.
Updating Homematic RF-Hardware: HMIP-RFUSB: =>4.4.18, ERROR ( != 4.4.18)
I then found a thread on the RaspberryMatic GitHub page about a similar issue.
https://github.com/jens-maus/RaspberryMatic/issues/1516
Is this the same issue with a new version and what info can I give you to help in debugging?
```
root@ha:/# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 1b1f:c020 eQ-3 Entwicklung GmbH HmIP-RFUSB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
```
My stick is bought directly from ELV, so it is not a Telekom stick and Debmatic have been running for nearly 2 years with that stick and Debmatic.
Sourcer63
(Johannes)
March 21, 2025, 7:10pm
8
Deleted - opened a new thread
WallyR
(Wally)
March 21, 2025, 11:31pm
9
tom_I has a mishap and corrected it when it was pointed out to him.
Could you do the reconfigure mentioned in the end of my link?
Sourcer63
(Johannes)
March 22, 2025, 4:02am
10
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.
WallyR
(Wally)
March 22, 2025, 5:33am
11
I am pretty sure it backup addons too.
Try opening the CCU webpage to see more.
Sourcer63
(Johannes)
March 22, 2025, 7:40am
12
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.
Sourcer63
(Johannes)
March 24, 2025, 10:40am
13
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.
floslight
(Torsten Otto)
August 15, 2025, 8:28am
14
I got the same error message on a Home Assistant Yellow Appliance after the last OS Upgrade.
Anyone having the same challenge?
Updating Homematic RF-Hardware: HMIP-RFUSB: =>4.4.18, ERROR ( != 4.4.18)
floslight
(Torsten Otto)
August 15, 2025, 8:42am
15
There is a fix for those running Home Assistant Yellow: ha os update --version 16.2.dev20250814
opened 06:49AM - 14 Aug 25 UTC
board/yellow
### Describe the issue you are experiencing
Homematic / Homatic IP devices conn… ected/controlled via Homematic Integration - RaspberryMatic addon - HmIP-RFUSB stopped working after update.
HmIP-RFUSB not visible in RaspberryMatic Addon.
update to HA 2025.8 no problem
update to HA 2025.q no problem
update to HA OS 16.1 HmIP-RFUSB not available
### What operating system image do you use?
yellow (Home Assistant Yellow)
### What version of Home Assistant Operating System is installed?
HA OS 16.1
### Did the problem occur after upgrading the Operating System?
Yes
### Hardware details
Home assistant Yellow - HmIP-RFUSB directly connected
LANGW (addional interface for RaspberryMatic/Homematic devises connected via (working)
3 ESPHome devices
5 Zigbee devices (Zigbee HA integration)
### Steps to reproduce the issue
1. reboot of HA Yellow - no change
2. install backup for RaspberryMatic CCU 3.81.5.20250326 on HA OS 16.1 - no improvement
3. rolling back to HA OS 16.0 -> everything works fine again2. update to RaspberryMatic CCU 3.81.2025 20250705 on HA OS 16.0 - works fine
3.
...
### Anything in the Supervisor logs that might be useful for us?
```txt
sorry to many restarts/reboots
```
### Anything in the Host logs that might be useful for us?
```txt
sorry to many restarts
```
### System information
## System Information
version | core-2025.8.1
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
container_arch | aarch64
user | root
virtualenv | false
python_version | 3.13.3
os_name | Linux
os_version | 6.12.25-haos-raspi
arch | aarch64
timezone | Europe/Vienna
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
HACS Data | ok
GitHub API Calls Remaining | 5000
Installed Version | 2.0.5
Stage | running
Available Repositories | 2214
Downloaded Repositories | 10
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 16.0
-- | --
update_channel | stable
supervisor_version | supervisor-2025.08.1
agent_version | 1.7.2
docker_version | 28.3.0
disk_total | 916.9 GB
disk_used | 18.0 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization |
board | yellow
supervisor_api | ok
version_api | ok
installed_addons | Advanced SSH & Web Terminal (21.0.2), RaspberryMatic CCU (3.83.6.20250705), Studio Code Server (5.19.3), ESPHome Device Builder (2025.7.5), File editor (5.8.0), Samba share (12.5.2), NGINX Home Assistant SSL proxy (3.13.0), Mosquitto broker (6.5.1), Silicon Labs Flasher (0.3.3), AdGuard Home (5.3.1), Matter Server (8.0.0)
</details>
<details><summary>Dashboards</summary>
dashboards | 4
-- | --
resources | 7
views | 11
mode | storage
</details>
<details><summary>Network Configuration</summary>
adapters | lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth10dd4ab (disabled), vethb5775fc (disabled), vethf7e4e41 (disabled), vethed57d8d (disabled), veth53082d7 (disabled), vethd5fcd8f (disabled), vethae11ba9 (disabled), vetha53f127 (disabled), veth9200ac2 (disabled)
-- | --
ipv4_addresses | lo (127.0.0.1/8), end0 (192.168.9.97/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth10dd4ab (), vethb5775fc (), vethf7e4e41 (), vethed57d8d (), veth53082d7 (), vethd5fcd8f (), vethae11ba9 (), vetha53f127 (), veth9200ac2 ()
ipv6_addresses | lo (::1/128), end0 (fe80::4e0b:4037:7f2:b9c5/64), hassio (fe80::7496:76ff:fe2b:c7b8/64), docker0 (fe80::f08e:e8ff:fe1d:28a0/64), veth10dd4ab (fe80::3862:63ff:fe87:b5e7/64), vethb5775fc (fe80::54e0:f9ff:fefd:cc07/64), vethf7e4e41 (fe80::9ce2:6aff:fee8:47e/64), vethed57d8d (fe80::8c78:86ff:fe2e:a85/64), veth53082d7 (fe80::d82f:46ff:feac:4eeb/64), vethd5fcd8f (fe80::103a:24ff:feb9:b937/64), vethae11ba9 (fe80::54c6:9eff:feab:6c4b/64), vetha53f127 (fe80::20cb:a4ff:fe15:30a9/64), veth9200ac2 (fe80::6810:3eff:fef4:e6b2/64)
announce_addresses | 192.168.9.97, fe80::4e0b:4037:7f2:b9c5
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | July 28, 2025 at 20:22
-- | --
current_recorder_run | August 14, 2025 at 06:45
estimated_db_size | 479.08 MiB
database_engine | sqlite
database_version | 3.48.0
### Additional information
_No response_
Big thank you to the contributors!
1 Like