Zum Hauptinhalt springen

Live KNX bus telemetry

The Live Bus tab on a project streams the installation's KNX telegrams into the browser in real time, so you can watch what the bus is actually doing — which group addresses are switching, what values sensors report — without ETS or a laptop on site. It is monitoring-only: it never writes to or commissions the bus.

The bridge​

Telemetry flows through a bridge — a small agent the customer runs on-site, one per project. It's a Docker container on any Linux host on the same LAN as the KNXnet/IP gateway (a Raspberry Pi 4, a NUC, a NAS), started with host networking. It watches the gateway and forwards telegrams to KNX Clarity; it is configured entirely through environment variables (KNX_GATEWAY_HOST, KNX_GATEWAY_PORT, INGEST_URL, BRIDGE_TOKEN).

Adding a bridge​

On the Live Bus tab, under KNX-Brücken, click Neue Brücke and give it a name (and optionally a note like 192.168.1.50:3671 / Gira X1). On success the app shows two secrets exactly once:

  • the bridge token (kxb_…) — the container's BRIDGE_TOKEN, and
  • a command signing key — the container's BRIDGE_COMMAND_SIGNING_KEY.

Copy both immediately; only a hash of the token is stored, so neither can be shown again. Paste them into the bridge's configuration and start the container.

To retire a bridge, click Widerrufen — it's rejected on its next call. Rotating the token is just revoke + add a new one and swap BRIDGE_TOKEN.

What you see​

  • A bridge card listing every registered bridge with its token prefix, active/revoked state, telegram count, and last-seen time.
  • A live feed — a rolling table of the most recent telegrams, newest first, refreshed every few seconds: Zeit (time), GA (group address), Quelle (source device), APCI (e.g. GroupValue_Write), Wert (the decoded value, e.g. 21.5 °C), and Roh (the raw hex).
  • An "Anlage scannen" panel to discover devices on the bus (a simulated demo in the current build) and promote them into the project.

Telemetry is off by default and must be switched on per project with the Telemetrie toggle. KNX telegrams reveal presence, temperature, and security-relevant data, so the app keeps a standing reminder to only enable it with the building owner's explicit consent. Consent is re-checked on every ingest, and you can't turn telemetry off while bridges are still active — revoke them first.

Pro plan required

Live-bus telemetry is a Pro (and above) feature — see Plans & billing. Beta and Starter orgs don't have it. Pro includes up to 5 bridges and a monthly budget of 10 million telegrams; Enterprise raises both. Stored telegrams are retained for 7 days on Pro (30 on Enterprise); the per-group-address last value is always kept live.

When the monthly budget runs out​

Each stored telegram counts against your monthly budget. When it's exhausted, an amber banner appears with a link to your plan, and the system stops archiving new telegrams — but the live values keep updating (the last-seen value per group address is always folded in), so the feed doesn't freeze. Archiving resumes next month, or sooner on a higher plan.