Skip to content

Using the Web UI

OpenCCU-Loom ships a browser-based Config UI for inspecting your CCUs, browsing devices, changing values, and configuring devices — no command line needed. This page is a tour of what you can do there.

Who this page is for

End users who want to manage their Homematic devices from a browser. No Go knowledge or API experience required.

Opening the UI

By default the web UI listens on port 8081. In a browser on the same network, open:

http://<host-running-openccu-loom>:8081/

First run

The very first time you open the UI, there is no account yet. You are sent to the first-run setup page at /setup, where you create the initial administrator account.

http://<host>:8081/setup

After that, future visits go through the login page at /login.

Logging in

OpenCCU-Loom supports several sign-in methods (local accounts, sessions, and optionally OIDC single sign-on). Which ones are available depends on how the daemon was configured. For the details of accounts, roles, and OIDC, see Authentication.

Tip

If the page does not load at all, the rich Svelte app may not be built into your binary. A minimal fallback page is served instead and points you back to the same address. In that case check your install per Getting started.

What the UI lets you do

The app is organised into views. The main ones, and the everyday tasks they cover:

View What you do there
Devices Browse all devices across your CCUs, drill into channels and parameters.
Device detail Inspect one device, read and change its data points, and configure it.
Un-ignore Reveal hidden / expert parameters so they appear and publish north-bound.
Matter Enable exposure of devices to Apple Home / Google Home / Alexa and pair.
Diagnostics Check health and troubleshooting information.
Backups Manage configuration backups.
Firmware View device firmware status.
Inbox / Messages See pending notices from your CCUs.
Programs / System variables Browse CCU programs and system variables.
Audit log Review what changes were made and by whom.
Settings Adjust daemon and UI settings.

The sections below cover the tasks most users do.

Browsing devices, channels, and parameters

Open the Devices view to see every device OpenCCU-Loom has discovered across all configured CCUs. If you run more than one CCU, devices are grouped by their CCU name (the central_name).

Selecting a device opens its detail view, where you can:

  1. See the device's channels.
  2. Open a channel to list its data points (parameters such as STATE, LEVEL, TEMPERATURE).
  3. Read the current value of each data point.

If you are unsure what "device", "channel", and "data point" mean, read Core concepts first.

Changing a value

For writable parameters, the UI gives you a control (a toggle, a slider, an input field) to set a new value. When you confirm, OpenCCU-Loom sends the change to the CCU and the device reacts.

Behind the scenes this is a single write to the parameter (PUT /api/v1/devices/{address}/channels/{channel}/data-points/{parameter}/value); you do not need to call it yourself — the control does it for you.

Warning

Writing a value actuates a real device. Make sure you are changing the device you intend to before you confirm.

Configuring a device (paramsets)

Beyond live values, many devices have configuration parameters (the device's settings, as opposed to its current state). The UI presents these as editable forms per channel, with sensible grouping and labels.

You can also export a channel's configuration and import it again, which is handy for copying settings between similar devices. These map to the channel config export/import endpoints (GET .../config/export and POST .../config/import).

Showing hidden parameters (un-ignore)

Some parameters are hidden by default to keep views clean — see parameter visibility. The Un-ignore view lists the parameters currently available to un-ignore, and lets you mark the ones you want.

  1. Open the Un-ignore view.
  2. Find the parameter you need (the view can suggest candidates).
  3. Mark it to un-ignore.

Once un-ignored, the parameter shows up in the device's data-point list and is published to MQTT, REST, and the other north-bound bridges like any other data point.

Health and diagnostics

The Diagnostics view shows the daemon's overall health and connection status to each CCU and interface — useful when a device seems unresponsive or a CCU dropped offline. There is also a server-rendered /health page if you only need a quick up/down check.

For deeper operational topics (log levels, captures, metrics), see Observability.

Where to go next