Draft
Getting started
From first start to KNX devices in a home app.
Requirements
KMBridge is a single, fully static executable that runs directly on ARMv5 and ARM64 Linux without external system library dependencies. Packages are available on the download page.
Start
knx-matter-bridge --data-path /var/lib/knx-bridge
Configuration and the licence live in the data directory (standalone.db and future.key). The web interface listens on port 8080 by default; use --web-port to change it.
First sign-in
From a computer or phone on the same network, open http://kmbridge.local:8080. With more than one bridge on the network, the sign-in page lists them all; pick one to switch. If it doesn't open, see Set up, or find the bridge's IP in the router's device list and open http://<bridge-address>:8080.
If the bridge is in another subnet: bridges on the same switch but in a different subnet appear in the list directly, with the subnet to add to the computer; open bridges behind a router or in another VLAN by IP, or have the network forward UDP 5620 (the bridge's discovery messages) multicast or broadcast so they are listed too.
On first visit, initialise the administrator account (password of at least 8 characters) and accept the Terms of Use.
Internet access (optional)
The "Allow internet access" master switch under System → Network ships turned off by default. While it is off, KNX, Matter, HomeKit and the local web interface operate entirely within your local network. Online activation, update checks, remote access and AI require this switch enabled; the Privacy Policy lists what each one sends.
Activate a licence (optional)
Without activation KMBridge runs as Community edition: up to 40 devices, without ecosystem native bridges, AI assistant, ETS project import, advanced automation or remote maintenance.
- Online: enter the activation code received at purchase under System → License.
- Offline: if the device cannot connect to the internet, choose "No internet access? Activate offline" to generate an offline request package, submit it to support for a licence code; the device never connects to the internet.
Connect to KNX
On the KNX page, under Connection, choose the connection type (UDP tunnelling, TCP tunnelling or multicast routing) and enter the KNX IP interface's address. Native direct link needs dedicated hardware.
Add devices
Any of these works:
- import an ETS project on the Devices page (requires a licence);
- add devices manually;
- scan the bus first under KNX → Survey, then add devices based on discovered topologies.
To evaluate features first, import preconfigured demo devices on the Devices page.
Add to your home app
- Matter: open the pairing window on the Matter page, then in Apple Home, Google Home or another Matter-compatible app add a Matter device and scan the QR code or enter the setup code.
- HomeKit: open the Home app on iPhone / iPad, tap "Add Accessory", then scan the QR code or enter the setup code manually. HomeKit requires a Plus or Pro Max licence.
Stay up to date
Check for updates under System → Maintenance → Firmware update, or upload an update package. If a new version fails to start, it rolls back automatically to the previous version.