busware

BREMA for KNX MCP4KNX

Firmware that turns the TUL into an MCP server, so an agent can commission KNX devices without ETS — addresses, tables, parameters. Product data and the project record come from two services in your own network.

 runs on: TUL

Most KNX gateways relay group telegrams: they talk to devices somebody else configured with ETS. This firmware speaks the connection-oriented management services ETS itself uses. It gives a device its individual address, reads and writes memory and properties, drives the Load State Machines, installs address and association tables, restarts the device so the change takes effect, and hands the result to Home Assistant.

The stick answers MCP over plain HTTP on your LAN — no proxy and no cloud account. The tools an agent is offered are generated from the firmware’s own registry, so they cannot drift from what the device can actually do. Two services you run in your own network complete it: knxprod-mcp for the manufacturers’ product data and knxproject-mcp for the installation’s record. The stick finds them by itself and forwards their tools.

It is the KNX incarnation of BREMA (Busware Rule Engine Model Assistant), where what a device means lives as data rather than compiled into the firmware. The project is documented in the open at github.com/tostmann/BREMA — that repository holds the documentation, not the firmware sources.

Do you still need ETS?

In a KNX installation, ETS does four jobs: it holds the manufacturers’ product data, keeps the project, programs the devices and helps diagnose the bus. Here they are spread over the firmware and the two services, and none of them needs ETS:

JobWithout ETS, here
Product dataknxprod-mcp reads the .knxprod files you supply: which product an ApplicationId is, its com objects, its parameters with memory address and value meanings, and what raw memory bytes decode to.
Individual addressThe stick checks that the address is free and that exactly one device is in programming mode, writes the address, verifies it and takes the device out of programming mode.
Group addressesThe address and association tables are built from the links and installed as one operation: load session, chunks verified by read-back, close, restart.
ParametersThe load procedure comes from the device’s product file; the parameter is written inside a load session, verified by read-back, and the device restarted.
Projectknxproject-mcp keeps the installation’s record between conversations: topology, devices, group addresses, links, parameters and the owner’s decisions, each with its source.
DiagnosticsA passive survey of every telegram on the line, an active sweep for the devices on a line, and each device’s identity, properties and memory read back.

The whole chain — address, tables, parameter, restart — is documented end to end on a Merten 649802 blind actuator. A device with another load procedure is a new case: let the agent run it as a dry run first.

Where ETS is still the tool:

Features

Requirements

Getting started

Flash it in the browser at install.busware.de/TUL/mcp/ and provision Wi-Fi in the same USB session over Improv — credentials are never compiled in. The stick then serves its own page at http://busware-knx-<id>.local/, showing its addresses, its hardware identity and the ready-made command:

claude mcp add --transport http busware-knx http://busware-knx-<id>.local/mcp

Point an agent at it and describe what you want commissioned. For product data and the project record, one Compose file starts both services: Running the services.

Documentation

Limits

KNX is the first published backend. Zigbee, EnOcean and HomeMatic run on the same engine but are not released — only what has run on real hardware is offered for download.

The ground-truth service that keeps a model from inventing device facts is in use for the radio backends and is not openly available yet. For KNX, that index is knxprod-mcp: it runs in your own network, over the product files you obtained yourself. A shared catalogue is not offered — the files are the manufacturers’, and some allow them in KNX-recognised tools only. Without the service, the product file stays your input, and the firmware says so rather than inventing the mapping.

KNX and ETS are trademarks of KNX Association cvba.