Matter Bridge to KNX: Integrating Matter Devices into an Existing KNX Installation
A Matter bridge exposes KNX group objects as Matter endpoints, enabling Apple Home, Google Home and Amazon Alexa voice control without replacing the KNX infrastructure. The bridge translates between KNX telegrams and Matter clusters — preserving KNX as the automation backbone while adding consumer ecosystem access.
Why bridge rather than replace
KNX devices are not natively Matter-capable — the KNX association and CSA have no joint roadmap for Matter-on-TP. Replacing a working KNX installation with Matter devices loses deterministic bus communication, certified actuators and the ETS6 commissioning toolchain. The bridge approach preserves the KNX layer completely and adds consumer ecosystem access as an overlay.
Recommended architecture: KNX handles all automation logic (scenes, schedules, sensors, actuators). The Matter bridge adds voice control and remote status only — it does not replace KNX logic. Write commands (voice → light on/off) flow KNX→actuator via bridge. Read commands (app status check) read KNX state via bridge. Complex automation (wind-triggered blinds, occupancy-based HVAC) stays in ETS6 / KNX logic module — not in Apple Home shortcuts.
Matter Bridge options for KNX
Several platforms implement a KNX-to-Matter bridge. The most practical options as of 2025:
| Platform | KNX method | Matter bridge | Notes |
|---|---|---|---|
| Home Assistant | KNX integration (xknx, IP/USB) | HA Matter Server (HACS) | Most flexible; requires HA OS or supervised |
| Homey Pro (2023) | KNX app (KNXnet/IP tunnelling) | Built-in Matter controller | Simpler setup; fewer advanced KNX features |
| Gira X1 HomeServer | Native KNX; Quadclient | No native Matter; use HA as bridge | Combine X1 ↔ HA via REST API |
| Eve Systems Bridge | No KNX support | Matter/Thread bridge only | Not applicable for KNX bridging |
KNX group object → Matter cluster mapping
Matter uses a cluster-based data model. Each KNX group address maps to a Matter attribute within the appropriate cluster. The DPT determines the correct cluster and attribute.
| KNX DPT | KNX use case | Matter cluster | Attribute |
|---|---|---|---|
| DPT 1.001 | Switch (on/off) | On/Off (0x0006) | OnOff |
| DPT 5.001 | Dimming (0–100%) | Level Control (0x0008) | CurrentLevel (0–254) |
| DPT 5.003 | Colour angle (0–360°) | Color Control (0x0300) | CurrentHue |
| DPT 9.001 | Temperature (°C) | Thermostat (0x0201) | LocalTemperature |
| DPT 1.008 | Up/Down shading | Window Covering (0x0102) | TargetPositionLiftPercent100ths |
| DPT 5.001 | Slat angle (0–100%) | Window Covering (0x0102) | TargetPositionTiltPercent100ths |
| DPT 1.001 | Alarm (on/off) | Boolean State (0x0405) | StateValue |
Home Assistant setup: KNX + Matter Server
Home Assistant running on Home Assistant OS (Raspberry Pi 4 or HA Green) is the most capable KNX–Matter bridge. The KNX integration handles group address read/write; the Matter Server add-on exposes HA entities as Matter endpoints to Apple Home, Google Home and Amazon Alexa simultaneously.
Home Assistant configuration.yaml — KNX light example
# KNX integration — group address mapping
knx:
light:
- name: "Living Room Main Light"
address: "1/1/1" # DPT 1.001 — switch GA
brightness_address: "1/1/2" # DPT 5.001 — dim level GA
state_address: "1/1/3" # DPT 1.001 — status feedback GA
brightness_state_address: "1/1/4" # DPT 5.001 — brightness feedback GA
# Matter Server automatically picks up HA light entities
# No extra Matter config needed — HA light → Matter On/Off + Level Control
# Commission in Apple Home: scan QR code from HA Matter Server add-onKNX cover (blinds) → Matter Window Covering
knx:
cover:
- name: "Living Room Blinds"
move_long_address: "2/1/1" # DPT 1.008 up/down
move_short_address: "2/1/2" # DPT 1.007 stop/step
position_address: "2/1/3" # DPT 5.001 target position write
position_state_address: "2/1/4" # DPT 5.001 position feedback
angle_address: "2/1/5" # DPT 5.003 slat angle write
angle_state_address: "2/1/6" # DPT 5.003 slat angle feedback
# HA cover entity → Matter Window Covering cluster
# Apple Home: "Close the blinds 50%" → DPT 5.001 value 50 → KNX actuatorLatency and limitations
Understanding the latency budget through the bridge prevents unrealistic expectations. Voice commands are not suitable for time-critical automation — use KNX logic for that.
| Step | Latency | Notes |
|---|---|---|
| Voice recognition (Siri/Google) | 500–1500 ms | Cloud round-trip for NLU |
| HomeKit/Google Home → HA | 50–200 ms | Local network if Thread/Wi-Fi; cloud adds 200–500 ms |
| HA entity state update | 10–50 ms | Internal HA bus |
| HA KNX integration → IP router | 10–30 ms | KNXnet/IP tunnelling |
| KNX IP router → TP actuator | 5–20 ms | TP bus telegram propagation |
| Total (voice → actuator) | 575–1800 ms | Use KNX buttons for fast response |
Attribute write-back gaps: Not all Matter cluster attributes have a direct KNX DPT equivalent. Colour temperature (DPT 7.600, Mired) maps to Matter ColorTemperatureMired but requires a KNX RGB/RGBW actuator with a colour temperature group address. RGB colour (DPT 232.600) is not natively exposed as a single Matter Hue/Saturation pair — separate HUE and SAT group addresses are needed, introducing a two-telegram update that may cause a brief visible colour step on the actuator.
Multi-admin: Apple Home + Google Home simultaneously
Matter’s multi-admin feature allows the same HA Matter Server to be commissioned into multiple fabrics — Apple Home, Google Home and Amazon Alexa can all control the same KNX devices through the bridge without interfering with each other.
Adding HA Matter Server to multiple fabrics
Step 1: Commission HA Matter Server into Apple Home HA Settings > Integrations > Matter (BETA) > Add device Scan QR code with iPhone (iOS 16+ required) HA appears as Matter bridge in Apple Home All exposed KNX entities appear as accessories Step 2: Add same HA Matter Server to Google Home Google Home app > + > Set up device > Matter > Scan QR code HA generates a new QR code for the second fabric Commissioning with device passcode (same device, new fabric credential) Step 3: Amazon Alexa Alexa app > Devices > + > Add Device > Matter Same procedure — new fabric pairing code from HA Result: one KNX group address, three voice assistants "Hey Siri, turn on living room" → HA KNX → actuator "Hey Google, dim bedroom to 30%" → HA KNX → actuator (all operate independently via separate fabric credentials)
Need Matter and KNX integrated in your project?
We design KNX installations with Matter bridge integration — Apple Home, Google Home and Amazon Alexa voice control over your existing KNX infrastructure, with proper group address mapping and full commissioning documentation.
Request a quote →