Homematic IP Local (HCU)
Ediminator/homematicip-hcu · v2.6.1
This is a custom integration for Home Assistant that connects directly to your Homematic IP Home Control Unit (HCU) over your local network. It allows you to control and monitor your Homematic IP devices without relying on the cloud.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
light | Light | |
switch | Switch or outlet | |
cover | Blind, garage door, window or door | |
climate | Thermostat | |
lock | Lock | Needs its own HomeKit Bridge in accessory mode |
alarm_control_panel | Security system | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
valve | Valve | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
2 reports below say how a device from this integration behaves in the Home app.
What people report
Local Homematic IP HCU integration finds more devices than the cloud one and gets quick fixes for new hardware. Door locks and garage modules needed HomeKit workarounds or added entities.
- Works4
- Partly works3
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Homematic IP alarm system (HCU firmware 1.79) | Works Local | Arm/disarm fixed after PRESENCE/ABSENCE zone renameSaved copyDescription HmIP's 1.79 HCU firmware update introduced a new alarm system that renamed the security zone groups used by `setExtendedZonesActivation`: `INTERNAL`/`EXTERNAL` became `PRESENCE`/`ABSENCE`. Arm/disarm requests built with the old names now fail with `HTTP 400 UNKNOWN_GROUP`. This PR: - Detects which zone names the HCU currently reports in `securityZones` (`INTERNAL`/`EXTERNAL` on older firmware, `PRESENCE`/`ABSENCE` on 1.79+) and uses those for both reading and setting the alarm state, so the integration keeps working across the firmware rollout. - On 1.79+ firmware, … Excerpt saved from GitHub on 2026-10-23. | PR #418 · 2026-07 | |
| Homematic IP door lock HmIP-DLD | Works Local | Partly in Home Apple Home lacks an Open Latch function; separate button works around it | Dedicated unlatch button added to bypass Apple's missing Open Latch supportSaved copyCloses #30. Apple HomeKit Door Unlatch Bypass Added a dedicated \HcuDoorUnlatchButton\ for HmIP-DLD door locks to bypass Apple Homekit refusing to support an Open Latch function for locks. Enhanced Authentication Diagnostics Catches \CLIENT_INVALID_AUTHORIZATION\ errors for the plugin user and prints a clear troubleshooting guide for HCU FW 1.6.16. Excerpt saved from GitHub on 2026-10-23. | PR #308 · 2026-03 |
| Homematic IP HCU1 with 74 devices | Works Local | Local setup easy; found 74 devices versus 64 via cloudSaved copyHatte jetzt endlich mal Zeit meine HCU1 im Home Assistant mit der lokalen Anbindung zu übertragen. Das ging alles sehr einfach. Kleiner Tipp...deaktiviert vorher die Cloud Anbindung, dann findert ihr die Entitäten dann wieder leichter, da diese dann grau hinterlegt sind und die anderen zur lokalen Anbindung gehören. Ich habe insgesamt 64 Geräte bei der Cloud Anbindung und siehe da, bei der lokalen dann 74 Geräte. Endlich wird hier auch der wired co2 Sensor SCTHD angezeigt (das ging bei der Cloud nicht). Bei der lokalen Anbindung sind schon sehr viele Geräte dabei, allerdings sind mir einige … Excerpt saved from GitHub on 2026-10-23. | Issue #94 · 2025-11 | |
| Homematic IP HmIP-FDC door communication module | Works Local | Access authorization and per-device PIN supportedSaved copySummary This PR adds full support for the HmIP-FDC (Door Communication Module) including its access-authorization model, per-device PIN management, and improved error reporting via HA Repairs. --- ## What's new ### HmIP-FDC: Access Authorization Channel The FDC uses a dedicated `ACCESS_AUTHORIZATION_CHANNEL` instead of the `DOOR_SWITCH_CHANNEL` to trigger the pull latch. The integration now: - Finds the correct `ACCESS_AUTHORIZATION_CHANNEL` that belongs to the same switch group as the door button. - Verifies that the integration's `clientId` is listed in an `ACCESS_AUTHORIZATION_PROFILE` … Excerpt saved from GitHub on 2026-10-23. | PR #350 · 2026-05 | |
| Homematic IP HCU top-light | Partly works Local | Switch, dim, color work in beta; off reported unsupported by one userSaved copyDescribe the bug When I try to switch on my HCUs Top-Light, I receive this error message: [code] To Reproduce Steps to reproduce the behavior: Try to switch on the light in HCUs device settings Expected behavior Light on Screenshots Versions *Home Assistant* - Installationsmethode: Home Assistant OS - Core: 2025.11.2 - Supervisor: 2025.11.2 - Operating System: 16.3 - Frontend: 20251105.0 - Companion-App: 2025.11.1-full (18678) - HCU-Addon: 1.17.2 *HCU* - HCU: 1.5.16 Excerpt saved from GitHub on 2026-10-23. | Issue #154 · 2025-11 | |
| Homematic IP wired 32-channel input module | Partly works Local | Events only evaluated on some channelsSaved copyHallo Ediminator, beim Punkt 4. Wired 32-fach Eingangsmodul funktionieren nicht alle Eingänge. Sprich die Ereignisse werden im HA nur bei einigen Kanälen ausgewertet…ich habe dein letztes Update 1.17.2 installiert. Habe meine ganzen wired Geräte inkl. wired AP neu gestartet. Habe auch die HCU und den HA neu gestartet. Außerdem habe ich die neueste Core Update vom HA gemacht und alle Geräte in der HCU local Integration neu geladen bzw. auch versucht das wired 32-Eingangsmodul kurz zu deaktivieren und dann wieder aktiviert. Die folgenden Eingänge werden im HA ausgewertet und beim drücken der … Excerpt saved from GitHub on 2026-10-23. | Issue #94 · 2025-11 | |
| Novoferm Homematic IP Funk-Modul (HmIP-MOD-TM) | Partly works Local | Partly in Home Users wanted it in HomeKit; light function missing | Open/close visible after HmIP-MOD-HO support; light and opener missingSaved copyFirst of all, thank you very much for the great work you’re doing here! 🙏 Now to the actual topic: Attached are the diagnostic files from my HCU with the “Novoferm Homematic IP Funk-Modul”. I’ve mapped the device locally as follow: [code] With that, it basically works. However, the option to control the light on the module is still missing. In addition, the name is currently displayed as “Domain plus self._attr_unique_id”. I have several devices with names like that, especially HmIP-FROLL and HmIP-PSM-2. I’ll open a separate issue for that. … Excerpt saved from GitHub on 2026-10-23. | Issue #25 · 2025-10 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Found automatically over
- Bonjour (zeroconf)
Details
| Installs (analytics) | 349 (0.05%) |
|---|---|
| GitHub stars | 74 |
| Latest version | 2.6.1 (2026-10-22) |
| Set up in the UI | Yes |
| Maintainers | @Ediminator |
| License | MIT |
Limitations from the README
- This integration is an independent community project. It is not affiliated with, endorsed by, or supported by eQ-3 AG. Homematic IP is a registered trademark of eQ-3 AG. Use this integration at your own risk. The authors are not responsible for any malfunctions, data loss, or unintended device switching. ---
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/Ediminator/homematicip-hcu
- Source code: https://github.com/Ediminator/homematicip-hcu
- Issues: https://github.com/Ediminator/homematicip-hcu/issues
- HACS: https://hacs.xyz