HmIP-HAP2-A cannot be learned/connected correctly in OpenCCU Home Assistant add-on although ports are mapped and device is reachable

[Tommy785]

Describe the issue you are experiencing

Describe the issue

I am trying to use an HmIP-HAP2-A as a Homematic IP LAN router with OpenCCU running as a Home Assistant OS add-on.

The same HmIP-HAP2-A works correctly on a CCU3/Charly OpenCCU setup on Raspberry Pi 3:

• it is found during Homematic IP device learning
• it can be learned successfully
• the HAP2 LED stays permanently lit

On the Home Assistant OS OpenCCU add-on setup, the HAP2 is reachable in the LAN, the OpenCCU container can ping it, and the relevant add-on ports are now mapped correctly. However, the HAP2 is not found during learning / does not connect correctly and keeps blinking.

This looks like a Home Assistant add-on / container networking issue with HmIP-HAP2-A discovery or connection handling.

Expected behavior

The HmIP-HAP2-A should be found via:

Geräte anlernen → Homematic IP Gerät anlernen

and should connect as a Homematic IP LAN router, just like it does on the CCU3/Charly OpenCCU setup.

Actual behavior

The HmIP-HAP2-A is not found during learning in the Home Assistant OS OpenCCU add-on setup.

When restored from a working Charly/OpenCCU backup, the HAP2 appears as a device / LAN router, but the LED keeps blinking and it does not seem to connect properly.

Environment

• OpenCCU add-on version: 3.87.6.20260509
• OpenCCU firmware shown in WebUI: 3.87.6.20260509
• Home Assistant OS: 17.3
• Home Assistant Core: 2026.5.2
• Hardware: Raspberry Pi 5
• RF module: HmIP-RFUSB
• HAP2 model: HmIP-HAP2-A
• HAP2 firmware: 1.0.4
• HAP2 IP: 192.168.1.76
• HAP2 MAC: 00:1a:22:26:70:c7
• Home Assistant host IP: 192.168.1.27
• OpenCCU container/internal IP from log: 172.30.33.1
• Network: same LAN/subnet, no VLAN between HA and HAP2

OpenCCU add-on info shows:

host_network: false


ha apps info de838cd8_openccu
9292/tcp: 9292
9293/tcp: 9293
9294/tcp: 9294
43438/udp: 43438
43439/udp: 43439
1900/udp: 1900
host_network: false

Porttest from iMac
nc -vz -w 3 192.168.1.27 9292 → succeeded
nc -vz -w 3 192.168.1.27 9294 → succeeded
nc -vzu -w 3 192.168.1.27 43439 → succeeded
nc -vzu -w 3 192.168.1.27 1900 → succeeded

[de838cd8_openccu_2026-05-18T10-15-11.240Z.log](https://github.com/user-attachments/files/27954672/de838cd8_openccu_2026-05-18T10-15-11.240Z.log)

<img width="1910" height="1256" alt="Image" src="https://github.com/user-attachments/assets/5d098fdc-9fe1-468a-bb48-ef742f42d618" />

### Describe the behavior you expected

Want to use the HmIP-HAP2-A as a LAN-Gateway to have access to the basement of our building.

### Steps to reproduce the issue

1.Run Home Assistant OS on Raspberry Pi 5.
2. Install OpenCCU as Home Assistant add-on.
3. Use HmIP-RFUSB as RF module.
4.Make sure the relevant OpenCCU add-on network ports are mapped.
5.Factory reset HmIP-HAP2-A.
6.Start OpenCCU WebUI.
7. Go to Geräte anlernen → Homematic IP Gerät anlernen.
8.Press the HAP2 system button / put it into learning mode.
9. HAP2 is not found / does not connect correctly and keeps blinking.2.


### What is the version this bug report is based on?

3.87.6.20260509

### Which base platform are you running?

ha-addon (HomeAssistant Add-on)

### Which HomeMatic/homematicIP radio module are you using?

HmIP-RFUSB

### Anything in the logs that might be useful for us?

```txt
ha apps info de838cd8_openccu shows:
9292/tcp: 9292
9293/tcp: 9293
9294/tcp: 9294
43438/udp: 43438
43439/udp: 43439
1900/udp: 1900

After this change, the relevant ports are reachable from another LAN client:
nc -vz -w 3 192.168.1.27 9292
# succeeded

nc -vz -w 3 192.168.1.27 9294
# succeeded

nc -vzu -w 3 192.168.1.27 43439
# succeeded

nc -vzu -w 3 192.168.1.27 1900
# succeeded

The OpenCCU container can also reach the HAP2:
docker exec -it addon_de838cd8_openccu ping -c 4 192.168.1.76
# 4 packets transmitted, 4 received, 0% packet loss

docker exec -it addon_de838cd8_openccu nc -vzu -w 3 192.168.1.76 43439
# UDP packet sent successfully

tcpdump findings

During HAP2 reset / boot / learning attempt, tcpdump on the Home Assistant host only shows ARP traffic related to the HAP2, but no meaningful IP traffic from/to the HAP2 and the Home Assistant/OpenCCU host IP.

Example:
ARP, Request who-has 192.168.1.76 tell 0.0.0.0
ARP, Request who-has 192.168.1.76 tell 192.168.1.76
ARP, Request who-has 192.168.1.76 tell 192.168.1.1

What I would have expected to see, but do not see:
192.168.1.76 -> 192.168.1.27:9292/9294/43439
192.168.1.27 -> 192.168.1.76

There is internal traffic between Home Assistant/Supervisor and the OpenCCU container, for example:
172.30.32.1 -> 172.30.33.1:9292
172.30.33.1:9292 -> 172.30.32.1
But I do not see comparable HAP2 traffic from 192.168.1.76 to 192.168.1.27.

Comparison test

The same HmIP-HAP2-A works correctly with an OpenCCU/CCU3 Charly setup on Raspberry Pi 3:

HAP2 is found during Homematic IP device learning
HAP2 can be learned successfully
HAP2 LED stays permanently lit

This suggests that:

the HAP2 itself is not defective
the LAN/UniFi network is probably not the root cause
the problem seems specific to OpenCCU running as Home Assistant OS add-on / container
OpenCCU log

OpenCCU itself starts without obvious errors:
Starting eq3configd: OK
Starting multimacd: OK
Starting HMIPServer: OK
Starting ReGaHss: OK
Finished Boot: 3.87.6.20260509
During learning attempts, I do not see useful HAP2-related log entries.

Additional notes

The OpenCCU WebUI firewall is set to:
Firewall-Richtlinie: Ports offen
Homematic XML-RPC API: Vollzugriff
Remote Homematic-Script API: Vollzugriff
Mediola-Zugriff: Vollzugriff

The HAP2 was also tested after factory reset and direct learning attempt on the HA OpenCCU add-on after the ports had been mapped correctly.

Additional information

de838cd8-openccu-2026-05-18.log

de838cd8_openccu_2026-05-18T10-15-11.240Z.log

[jens-maus]

This is not a bug in OpenCCU but a technical limitation of the used docker environment within HomeAssistant. Therefore you currently have to use a cumbersome workaround script to setup the correct macvlan environment to get a HmIP-HAP or HmIPW-DRAP connected/working when you run your OpenCCU within HomeAssistant. See here:

https://github.com/OpenCCU/OpenCCU/wiki/Installation-HomeAssistant#hmiphaphmipwdrap-support-patch

Even thought I am currently working on getting this a bit easier implemented, avoiding application of that script on every reboot of the OpenCCU Addon or HA, that's why it is usually a good idea to avoid running OpenCCU as a HomeAssistant App/Add-on an better use a dedicated VM only for OpenCCU alongside a VM for HomeAssistant (if you use a virtualization environment like ProxmoxVE) or keep OpenCCU running on a dedicated Hardware. As said, all this is due to technical restrictions in the docker environment routing multicast UDP traffic which is required for communication with a HmIP-HAP or HmIPW-DRAP.