OpenCCU-Loom¶
A standalone Go daemon that bridges Homematic and HomematicIP CCUs to MQTT, a REST + WebSocket API, a web Config UI, and Matter.
OpenCCU-Loom talks to Homematic / HomematicIP CCUs (CCU2, CCU3, OpenCCU) over XML-RPC, BIN-RPC, and JSON-RPC — and to openccu-lite boxes over occulited's HTTP API and event stream — and exposes them on the north side to standard protocols, so you can use your devices from MQTT, REST/WebSocket clients, a browser, or a Matter controller without running Home Assistant.
OpenCCU-Loom began as a Go port of aiohomematic and now develops on its own. The two projects coexist: aiohomematic powers the Home Assistant integration Homematic(IP) Local; OpenCCU-Loom serves users who want MQTT / REST / UI / Matter access without it. It is open source under the Apache License 2.0.
What it gives you¶
- MQTT — Home Assistant Discovery and a raw topic plane, in parallel.
- REST + WebSocket API — full device/parameter control and a live event stream.
- Config UI — a Svelte SPA for setup, device configuration, and diagnostics.
- Matter — a pure-Go Matter bridge (opt-in, built on go-fabric) so your CCU devices appear in Apple Home, Google Home, and Alexa.
- Alarm system and Security & Safety — zones, arming, codes and a fault overview across your sensors, on MQTT, REST and the web UI.
- History, webhooks and MCP — measurement history, outbound and inbound webhooks, and an MCP server so an AI assistant can drive the daemon.
- Multi-CCU — one daemon, many centrals, first-class from day one — full CCUs and openccu-lite boxes side by side.
Single static binary¶
OpenCCU-Loom ships as a single static binary (CGO_ENABLED=0) and as multi-arch Docker images (amd64, arm64, armv7). Persistence is pure-Go SQLite plus the filesystem — no external database, no CGo.
Where to next¶
The navigation follows three tracks — pick the one that matches what you want to do.
-
Use
Get a CCU bridged and use your devices from the web UI, MQTT, or a Matter controller.
Concepts · Web UI · Matter · Alarm
Running Home Assistant? Start with choosing your integration path.
-
Operate & integrate
Install, configure, secure and run the daemon; connect MQTT, REST, WebSocket and MCP clients.
-
Develop & architecture
How the daemon is built and why: architecture, the Matter boundary, wiring, testing, releases and the decision records.
Project links¶
- Source: github.com/SukramJ/openccu-loom
- Matter stack: go-fabric
- Sibling project (Home Assistant integration): aiohomematic
- Upstream OS: OpenCCU · openccu.de
Documentation language
The documentation is built to be multilingual. For now it is published in English only; German pages will be added over time.