KNX Bridge
The KNX Bridge exposes devices from other protocols — Home Assistant, Modbus TCP, HTTP, MQTT, BACnet/IP, TCP/UDP, Virtual — on the KNX bus, as if they were native KNX devices. A KNX push button can then switch a Home Assistant light; a KNX energy display can show a Modbus inverter's power.
It lives on the Bridge tab, in the Bridge Devices to KNX panel. The bridge sends nothing to the bus while the connection strip shows Disconnected.
Adding a device to the bridge:
-
On the Bridge tab, in Bridge Devices to KNX, click Add Device (on an empty list the button reads Add First Device). In Select Device to Bridge, pick the device: every device that is not a KNX device and is not bridged yet is offered. Its bridge settings open.
-
Check that Enable Bridge is on. For each of the device's group objects you want on the bus:
- choose a Datapoint Type — search or pick from the list;
- under Group Addresses, assign one or more group addresses (type them, e.g.
1/0/1, or pick existing ones). The bridge accepts three-level addresses only; - leave the On Change switch on to send a value only when it changes, or turn it off to send every value, even unchanged.
You do not set a direction: a command object listens on the bus, a feedback object publishes to it.
-
Click Save Configuration. Cancel, or closing the dialog, discards your edits. Once saved, the mapping is active on the bus at once: there is nothing to apply. The footer shows how many objects are bridged.
Per device you can also:
- Enable/disable the device on the bridge without losing its mappings.
- Delete the device from the bridge — this removes its group-address mappings (the device itself is untouched).
📘 Note: Loop prevention is automatic. A value that arrives from the bus is not echoed back to the bus, so bridging a device cannot create a telegram loop.
KNX triggers
A KNX trigger fires a scenario or an automation when a telegram arrives on a group address — the classic "wall push button runs the Leaving scene". Triggers live in the KNX Triggers panel, in the right-hand column of the Bridge tab.
What you need: a connected KNX bus, the group address the switch sends on, and a scenario or automation that already works when run manually. An automation must be switched on to be started by a trigger.
- In KNX Triggers, click Add Trigger.
- In KNX Group Address, select or type the group address to listen on.
- Choose the Condition:
| Condition | Fires when |
|---|---|
| Any Change | Every value written to the address, whether it is 1 or 0 and whether or not it differs from the last one. This is the condition a new trigger starts on. |
| On True (1) | The received value is 1/true. |
| On False (0) | The received value is 0/false. |
| Rising Edge (0 to 1) | The value goes from 0 to 1. |
| Falling Edge (1 to 0) | The value goes from 1 to 0. |
- Under Target Type, choose Scenario or Automation, then select the target in Target Scenario or Target Automation.
- Click Save. The button stays disabled until an address and a target are set. The new trigger appears in the list, switched on.
- Press the real switch and check the result.
📘 Note: With Any Change, a push button that sends
1on press and0on release runs the target twice. Use On True (1) to run it on each received1, or Rising Edge (0 to 1) when you need a transition from0to1.
⚠️ Warning: A trigger that targets an automation runs its actions and skips its conditions, like Trigger in the app's automation editor. Do not rely on the automation's conditions to block a press of the switch.
📘 Note: Only a telegram written by another KNX device fires a trigger. A command sent from the app or from a scenario to the same address does not.
Each trigger can be switched on or off with its switch in the list, and deleted there. A trigger that is switched off is kept.
