HMIPServer crashes/hangs during startup after upgrading container from raspberrymatic

[felix-schwarz]

Describe the issue you are experiencing

I switched the image of my Raspberrymatic's docker container from ghcr.io/jens-maus/raspberrymatic:latest to ghcr.io/openccu/openccu:latest, but found that HMIPServer always hangs (or repeatedly crashes with an exception?) then, so the installation can't be used anymore.

Describe the behavior you expected

My expectation was that the change of image would be as smooth as an Raspberrymatic updates, with everything working as before - or even better.

Steps to reproduce the issue

1. Take a working installation based on this docker-compose.yml file:

services:
  raspberrymatic:
    image: ghcr.io/jens-maus/raspberrymatic:latest
    container_name: ccu
    hostname: ccu
    privileged: true
    restart: unless-stopped
    stop_grace_period: 30s
    volumes:
      - ./ccu_data:/usr/local:rw
      - /lib/modules:/lib/modules:ro
      - /run/udev/control:/run/udev/control
    networks:
      ccu:
        ipv4_address: 10.0.8.2
networks:
  ccu:
    name: ccu
    driver: macvlan
    driver_opts:
      parent: eth0
    ipam:
      config:
        - subnet: 10.0.8.0/24
          gateway: 10.0.8.1

2. Change image to ghcr.io/openccu/openccu:latest.
3. Run docker compose pull && docker compose up -d && docker compose logs --follow

What is the version this bug report is based on?

3.85.7.20260131

Which base platform are you running?

rpi3 (RaspberryPi3, ARM64/aarch64)

Which HomeMatic/homematicIP radio module are you using?

RPI-RF-MOD

Anything in the logs that might be useful for us?

The container seems to hang at the step that'd start HMIPServer:

ccu  | Starting udevd: OK
ccu  | Identifying host system: Raspberry Pi 3 Model B Rev 1.2 (oci), OK
ccu  | Initializing RTC Clock: rx8130, OK
ccu  | Running sysctl: OK
ccu  | Checking for UserFS Resize: not required
ccu  | Checking for Factory Reset: not required
ccu  | Checking for Backup Restore: not required
ccu  | Running seedrng: OK
ccu  | Initializing System: OK
ccu  | Setup ca-certificates: OK
ccu  | Starting logging: OK
ccu  | Init onboard LEDs: init, OK
ccu  | Starting network: eth0: link up, fixed, firewall, inet up, 10.0.8.2, OK
ccu  | Identifying Homematic RF-Hardware: ....HmRF: RPI-RF-MOD/GPIO@3f201000.serial, HmIP: RPI-RF-MOD/GPIO@3f201000.serial, OK
ccu  | Updating Homematic RF-Hardware: RPI-RF-MOD: 4.4.22, not necessary, OK
ccu  | Starting hs485dLoader: disabled
ccu  | Starting xinetd: OK
ccu  | Starting eq3configd: OK
ccu  | Starting lighttpd: OK
ccu  | Starting ser2net: disabled
ccu  | Starting ssdpd: OK
ccu  | Starting sshd: OK
ccu  | Starting NUT services: disabled
ccu  | Initializing Third-Party Addons: OK
ccu  | Starting LGWFirmwareUpdate: not required
ccu  | Setting LAN Gateway keys: not required
ccu  | Starting hs485d: disabled
ccu  | Starting multimacd: ...OK
ccu  | Starting rfd: ..OK

Peeking into the container, I find the following error in /var/log/hmserver.log:

2026-02-24 19:00:40,135 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization ERROR [vert.x-eventloop-thread-6] Error 'LOCAL_ADAPTER_NO_SUCH_PORT' while trying to open port '/dev/mmd_hmip': 
de.eq3.cbcs.lib.commdevice.CommDeviceException: Exception while trying to open serial port. Check configured port '/dev/mmd_hmip'
	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

I also tried updating eq3_char_loop to the latest version, rebooting the Raspberry Pi and starting the container then - with the same result.

Switching back to ghcr.io/jens-maus/raspberrymatic:latest immediately solves the issue and the container comes up as usual:

ccu  | Populating /dev using udev: done
ccu  | Identifying host system: Raspberry Pi 3 Model B Rev 1.2 (oci), OK
ccu  | Initializing RTC Clock: rx8130, OK
ccu  | Running sysctl: OK
ccu  | Checking for UserFS Resize: not required
ccu  | Checking for Factory Reset: not required
ccu  | Checking for Backup Restore: not required
ccu  | Running seedrng: OK
ccu  | Initializing System: OK
ccu  | Setup ca-certificates: OK
ccu  | Starting logging: OK
ccu  | Init onboard LEDs: init, OK
ccu  | Starting network: eth0: link up, fixed, firewall, inet up, 10.0.8.2, OK
ccu  | Identifying Homematic RF-Hardware: ....HmRF: RPI-RF-MOD/GPIO@3f201000.serial, HmIP: RPI-RF-MOD/GPIO@3f201000.serial, OK
ccu  | Updating Homematic RF-Hardware: RPI-RF-MOD: 4.4.22, not necessary, OK
ccu  | Starting hs485dLoader: disabled
ccu  | Starting xinetd: OK
ccu  | Starting eq3configd: OK
ccu  | Starting lighttpd: OK
ccu  | Starting ser2net: disabled
ccu  | Starting ssdpd: OK
ccu  | Starting sshd: OK
ccu  | Starting NUT services: disabled
ccu  | Initializing Third-Party Addons: OK
ccu  | Starting LGWFirmwareUpdate: not required
ccu  | Setting LAN Gateway keys: not required
ccu  | Starting hs485d: disabled
ccu  | Starting multimacd: ....OK
ccu  | Starting rfd: ..OK
ccu  | Starting HMIPServer: ......................OK
ccu  | Starting ReGaHss: .OK
ccu  | Starting CloudMatic: disabled
ccu  | Starting Third-Party Addons: OK
ccu  | Starting crond: OK
ccu  | Setup onboard LEDs: booted, OK
ccu  | Finished Boot: 3.83.6.20250824 (raspmatic_oci_arm64)

I also verified that pivccu is indeed version 1.0.85:

$ dkms status
pivccu, 1.0.85, 5.10.0-35-arm64, aarch64: installed
pivccu, 1.0.85, 6.1.21-v8+, aarch64: installed

… and also made double-sure by uninstalling and reinstalling it via:

dkms uninstall pivccu/1.0.85 -k $(uname -r)
dkms install pivccu/1.0.85 -k $(uname -r)

… followed by a reboot. But the result was exactly the same.

Additional information

No response

[jens-maus]

Please make sure to update your pivccu kernel module dependencies to 1.0.88 and this issue should vanish.

See: #3498

[felix-schwarz]

Thanks, updating pivccu-modules-dkms to 1.0.87 solved the issue. I had seen the hint in the release notes and installed updated packages, but missed that the update I had installed was just 1.0.85. 🙈

Thanks for your help and all your work.