HMIPServer no longer starts after upgrading to 3.85.7.20260124

[agross]

Describe the issue you are experiencing

I upgraded from 3.85.7.20251129 to 3.85.7.20260124. With the new version starting HMIPServer times out. Downgrading works.

Describe the behavior you expected

Normal start behavior:

Jan 25 00:22:44 nest docker[2180901]: ccu-1  | Starting udevd: OK
Jan 25 00:22:45 nest docker[2180901]: ccu-1  | Identifying host system: QEMU Standard PC (Q35 + ICH9, 2009) (oci), OK
Jan 25 00:22:45 nest docker[2180901]: ccu-1  | Initializing RTC Clock: rtc_cmos 00:02, OK
Jan 25 00:22:45 nest docker[2180901]: ccu-1  | Running sysctl: OK
Jan 25 00:22:45 nest docker[2180901]: ccu-1  | Checking for UserFS Resize: not required
Jan 25 00:22:45 nest docker[2180901]: ccu-1  | Checking for Factory Reset: not required
Jan 25 00:22:45 nest docker[2180901]: ccu-1  | Checking for Backup Restore: not required
Jan 25 00:22:45 nest docker[2180901]: ccu-1  | Running seedrng: OK
Jan 25 00:22:45 nest docker[2180901]: ccu-1  | Initializing System: OK
Jan 25 00:22:48 nest docker[2180901]: ccu-1  | Setup ca-certificates: OK
Jan 25 00:22:48 nest docker[2180901]: ccu-1  | Starting logging: OK
Jan 25 00:22:48 nest docker[2180901]: ccu-1  | Init onboard LEDs: init, OK
Jan 25 00:22:48 nest docker[2180901]: ccu-1  | Starting network: eth0: link up, fixed, firewall, inet up, 172.18.0.2, OK
Jan 25 00:22:53 nest docker[2180901]: ccu-1  | Identifying Homematic RF-Hardware: ..../etc/init.d/S47InitRFHardware: line 304: can't create /sys/bus/platform/drivers/leds-gpio/unbind: nonexistent directory
Jan 25 00:22:53 nest docker[2180901]: ccu-1  | /etc/init.d/S47InitRFHardware: line 315: can't create /sys/bus/platform/drivers/leds-gpio/bind: nonexistent directory
Jan 25 00:22:55 nest docker[2180901]: ccu-1  | HmRF: RPI-RF-MOD/HB-RF-USB-2@usb-0000:07:1b.0-1, HmIP: RPI-RF-MOD/HB-RF-USB-2@usb-0000:07:1b.0-1, OK
Jan 25 00:22:55 nest docker[2180901]: ccu-1  | Updating Homematic RF-Hardware: RPI-RF-MOD: 4.4.22, not necessary, OK
Jan 25 00:22:55 nest docker[2180901]: ccu-1  | Starting hs485dLoader: disabled
Jan 25 00:22:55 nest docker[2180901]: ccu-1  | Starting xinetd: OK
Jan 25 00:22:55 nest docker[2180901]: ccu-1  | Starting eq3configd: OK
Jan 25 00:22:56 nest docker[2180901]: ccu-1  | Starting lighttpd: OK
Jan 25 00:22:56 nest docker[2180901]: ccu-1  | Starting ser2net: disabled
Jan 25 00:22:56 nest docker[2180901]: ccu-1  | Starting ssdpd: OK
Jan 25 00:22:56 nest docker[2180901]: ccu-1  | Starting NUT services: disabled
Jan 25 00:22:56 nest docker[2180901]: ccu-1  | Initializing Third-Party Addons: OK
Jan 25 00:22:56 nest docker[2180901]: ccu-1  | Starting LGWFirmwareUpdate: not required
Jan 25 00:22:56 nest docker[2180901]: ccu-1  | Setting LAN Gateway keys: not required
Jan 25 00:22:56 nest docker[2180901]: ccu-1  | Starting hs485d: disabled
Jan 25 00:23:00 nest docker[2180901]: ccu-1  | Starting multimacd: ...OK
Jan 25 00:23:02 nest docker[2180901]: ccu-1  | Starting rfd: .OK
Jan 25 00:23:18 nest docker[2180901]: ccu-1  | Starting HMIPServer: .........OK
Jan 25 00:23:20 nest docker[2180901]: ccu-1  | Starting ReGaHss: .OK
Jan 25 00:23:20 nest docker[2180901]: ccu-1  | Starting CloudMatic: disabled
Jan 25 00:23:20 nest docker[2180901]: ccu-1  | Starting Third-Party Addons: OK
Jan 25 00:23:20 nest docker[2180901]: ccu-1  | Starting crond: OK
Jan 25 00:23:20 nest docker[2180901]: ccu-1  | Setup onboard LEDs: booted, OK
Jan 25 00:23:20 nest docker[2180901]: ccu-1  | Finished Boot: 3.85.7.20251129 (oci_amd64)

With 3.85.7.20260124:

Jan 24 22:27:17 nest docker[2001348]: ccu-1  | Starting udevd: OK
Jan 24 22:27:18 nest docker[2001348]: ccu-1  | Identifying host system: QEMU Standard PC (Q35 + ICH9, 2009) (oci), OK
Jan 24 22:27:18 nest docker[2001348]: ccu-1  | Initializing RTC Clock: rtc_cmos 00:02, OK
Jan 24 22:27:18 nest docker[2001348]: ccu-1  | Running sysctl: OK
Jan 24 22:27:18 nest docker[2001348]: ccu-1  | Checking for UserFS Resize: not required
Jan 24 22:27:18 nest docker[2001348]: ccu-1  | Checking for Factory Reset: not required
Jan 24 22:27:18 nest docker[2001348]: ccu-1  | Checking for Backup Restore: not required
Jan 24 22:27:18 nest docker[2001348]: ccu-1  | Running seedrng: OK
Jan 24 22:27:19 nest docker[2001348]: ccu-1  | Initializing System: OK
Jan 24 22:27:19 nest docker[2001348]: ccu-1  | Setup ca-certificates: OK
Jan 24 22:27:19 nest docker[2001348]: ccu-1  | Starting logging: OK
Jan 24 22:27:19 nest docker[2001348]: ccu-1  | Init onboard LEDs: init, OK
Jan 24 22:27:19 nest docker[2001348]: ccu-1  | Starting network: eth0: link up, fixed, firewall, inet up, 172.18.0.2, OK
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Identifying Homematic RF-Hardware: ....HmRF: RPI-RF-MOD/HB-RF-USB-2@usb-0000:07:1b.0-1, HmIP: RPI-RF-MOD/HB-RF-USB-2@usb-0000:07:1b.0-1, OK
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Updating Homematic RF-Hardware: RPI-RF-MOD: 4.4.22, not necessary, OK
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Starting hs485dLoader: disabled
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Starting xinetd: OK
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Starting eq3configd: OK
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Starting lighttpd: OK
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Starting ser2net: disabled
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Starting ssdpd: OK
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Starting NUT services: disabled
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Initializing Third-Party Addons: OK
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Starting LGWFirmwareUpdate: not required
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Setting LAN Gateway keys: not required
Jan 24 22:27:26 nest docker[2001348]: ccu-1  | Starting hs485d: disabled
Jan 24 22:27:30 nest docker[2001348]: ccu-1  | Starting multimacd: ....OK
Jan 24 22:27:32 nest docker[2001348]: ccu-1  | Starting rfd: .OK
Jan 24 22:32:32 nest docker[2001348]: ccu-1  | Starting HMIPServer: .......................................................................................................................................................ERROR
Jan 24 22:32:34 nest docker[2001348]: ccu-1  | Starting ReGaHss: .OK
Jan 24 22:32:34 nest docker[2001348]: ccu-1  | Starting CloudMatic: disabled
Jan 24 22:32:34 nest docker[2001348]: ccu-1  | Starting Third-Party Addons: OK
Jan 24 22:32:34 nest docker[2001348]: ccu-1  | Starting crond: OK
Jan 24 22:32:34 nest docker[2001348]: ccu-1  | Setup onboard LEDs: booted, OK
Jan 24 22:32:34 nest docker[2001348]: ccu-1  | Finished Boot: 3.85.7.20260124 (oci_amd64)

Steps to reproduce the issue

1. Upgrade to 3.85.7.20260124

What is the version this bug report is based on?

3.85.7.20260124

Which base platform are you running?

generic-x86_64 (Generic UEFI capable system, AMD64/x86_64)

Which HomeMatic/homematicIP radio module are you using?

RPI-RF-MOD

Anything in the logs that might be useful for us?

See logs below

Additional information

broken-3.85.7.20260124.log
working-3.85.7.20251129.log

[nhulsch]

same issue as #3442 - the pivccu-modules-dkms package needs to be updated but hasn't been pushed to stable yet (still on 1.0.86 but 1.0.87 is needed)

[dontobi]

I'm having the same problem right now. Then I'll downgrade first.

[jens-maus]

same issue as #3442 - the pivccu-modules-dkms package needs to be updated but hasn't been pushed to stable yet (still on 1.0.86 but 1.0.87 is needed)

You are correct that this is the root cause here and that the issue will vanish as soon as @alexreinert will move the pivccu-modules-dkms 1.0.87 from testing to stable. So sorry for the inconvenience, I missed to add a breaking change note for docker and lx installations in the release notes (will do so!).

@alexreinert Can you please move that package to stable quickly now that two weeks in testing must have passed? Thanks!

[sander76]

using it inside hass. How do I downgrade ?

[Baxxy13]

Update HA-OS to 17.x or use the (hopefully created) backup to restore the previous version of the add-on.

[alexreinert]

@alexreinert Can you please move that package to stable quickly now that two weeks in testing must have passed? Thanks!

Done

[jens-maus]

@alexreinert Can you please move that package to stable quickly now that two weeks in testing must have passed? Thanks!

Done

Thanks @alexreinert for moving pivccu-modules-dkms 1.0.87 to the stable apt repository part.

So please anyone running in this issue because you have a pure docker or LXC container based OpenCCU installation, make sure to run a apt update && apt upgrade pivccu-modules-dkms first and then reboot your host system before trying to run OpenCCU 3.85.7.20260124. Note, however, that this is NOT required for environments where HomeAssistant OS is used as the operating system! For these installation, just make sure to upgrade to HomeAssistantOS 17.0 or newer, which comes with the necessary changes to successfully run OpenCCU 3.85.7.20260124.

[stohn]

Sorry but it seems not to be limited to docker/LXC only.
I run OpenCCU as AddOn inside of HomeAssistant with OS version 17.0 (Intel NUC) and after upgrade the same problem appeared:

Starting HMIPServer: .......................................................................................................................................................ERROR

I downgraded with a backup to the previous version for now.

[jens-maus]

For further debugging I would require the content of the /var/log/hmipserver.log file from within a running OpenCCU version when the issue appears.

[gschmidl]

Apologies, it will not for the life of me let me copy out of the terminal, so here's a screenshot of my log - same error on a Raspberry Pi CM5 with OS 17.0 and the latest OpenCCU.

[stohn]

I did the following:

1. Full reboot of HA

About page shows:

Installationsmethode Home Assistant OS
Core 2026.1.3
Supervisor 2026.01.1
Operating System 17.0
Frontend 20260107.2

2. I took the "hmipserver.log" from the OLD OpenCCU version which works (attached file "hmipserver-old.log")

3. I installed the OpenCCU AddOn update

same problem as before

4. I took the "hmipserver.log" from the NEW OpenCCU version (attached file "hmipserver-new.log")

from inside the file:

de.eq3.cbcs.lib.commdevice.CommDeviceException: Exception while trying to open serial port. Check configured port '/dev/raw-uart'
	at de.eq3.cbcs.lib.nrjavaserialdevice.SerialCommDevice.open(SerialCommDevice.java:124) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.lib.hmiptrxcommadapter.HomeMaticIPTRXCommAdapter.open(HomeMaticIPTRXCommAdapter.java:1042) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.lib.hmiptrxcommadapter.HomeMaticIPTRXCommAdapter.<init>(HomeMaticIPTRXCommAdapter.java:108) ~[HMIPServer.jar:?]
	at
de.eq3.cbcs.server.local.base.internal.ShareableHomeMaticIPTRXCommAdapter.<init>(ShareableHomeMaticIPTRXCommAdapter.java:34) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization.start(LocalServerAdapterInitialization.java:116) ~[HMIPServer.jar:?]
	at io.vertx.core.AbstractVerticle.start(AbstractVerticle.java:106) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$5(DeploymentManager.java:196) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:63) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.EventLoopContext.lambda$runOnContext$0(EventLoopContext.java:38) ~[HMIPServer.jar:?]
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) ~[HMIPServer.jar:?]
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469) ~[HMIPServer.jar:?]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) ~[HMIPServer.jar:?]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) ~[HMIPServer.jar:?]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[HMIPServer.jar:?]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[HMIPServer.jar:?]
	at java.lang.Thread.run(Unknown Source) ~[?:?]
Caused by: gnu.io.NoSuchPortException
	at gnu.io.CommPortIdentifier.getPortIdentifier(CommPortIdentifier.java:274) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.lib.nrjavaserialdevice.SerialCommDevice.open(SerialCommDevice.java:116) ~[HMIPServer.jar:?]
	... 16 more

For your reference i use a HMIP-RFUSB-TK dongle.

Output from OLD (working) OpenCCU AddOn Log:

Identifying host system: Intel Corporation NUC8BEB (oci), OK
Initializing RTC Clock: rtc_cmos rtc_cmos, OK
Running sysctl: OK
Checking for UserFS Resize: not required
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 network: eth0: link up, fixed, firewall, inet up, 172.30.33.2, OK
Identifying Homematic RF-Hardware: ....HmRF: n/a, HmIP: HMIP-RFUSB-TK/eQ-3 HmIP-RFUSB@usb-0000:00:14.0-3, OK
Updating Homematic RF-Hardware: HMIP-RFUSB-TK: 4.2.14, not necessary, 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: not required
Setting LAN Gateway keys: not required
Starting hs485d: disabled
Starting multimacd: not required
Starting rfd: no BidCos-RF hardware found
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.85.7.20251129 (oci_amd64)

hmipserver-new.txt

hmipserver-old.txt

[sander76]

I'm running on hassos 17 now and that fixed the issue.

[jens-maus]

Please note: Apart from the HomeAssistantOS 17.0+ dependency that might be the reason why for some users the HmIPServer might not startup correctly, I just found out that there is currently a bug in OpenCCU 3.85.7.20260124 that prevents the HmIPServer to work correctly with a HmIP-RFUSB-TK. See here:

#3498

So, every user that is seeing HMIPServer startup errors and is using a HmIP-RFUSB-TK (with the -TK at the end) for HomematicIP connectivity is asked to downgrade to 3.85.7.20251129 until the issue is fixed.

[eeeeeeeeven]

i can confirm that it ist the -TK Stick. Have both on hand. Tried with Both.

3.85.7.20260124
RF-USB = starting just like normal
RF-USB-TK = hanging at "starting hmipserver........" until ERROR

with 3.85.7.20260128 (snapshot) the -TK works also just fine.

Running VM on Proxmox

[stohn]

I just want to confirm,

HA OS 17.1 stable came out, I installed it, then installed the latest OpenCCU and everything is working.

Thanks for the great work.