KNX integration
The KNX page in the admin panel is the workbench for everything KNX: the bus connection, ETS programming access, the group-address library, the bus monitor, the KNX Bridge and KNX triggers. Open it from the sidebar. The page has three tabs: Bridge, Bus monitor and Group addresses. On the Bridge and Bus monitor tabs, a connection strip shows the Protocol, the Gateway IP and the live status (Connected / Disconnected).
Connection & remote ETS access
What you need: a configured KNX connection (see “Connections”) showing Connected.
The connection strip mirrors the KNX connection you configured on the Connections page. If it shows Disconnected, fix the connection there first — nothing on this page works without the bus.
Programming with ETS on site. HyperVisu keeps its KNX connection while you program with ETS: there is nothing to switch, and widgets stay live. Most KNX/IP interfaces allow only a limited number of tunnels, and HyperVisu holds one of them, so ETS needs another free tunnel on the interface (or its own programming interface).
Remote ETS access. To program the bus with ETS from outside the building, enable Remote ETS access. This opens a secured tunnel through the cloud connection and displays the Server and a Port number.
- On the KNX page (Bridge tab), switch on Remote ETS access. The switch takes a few seconds while the tunnel opens.
- Note the displayed server and port number. The port is assigned anew each time the access is enabled.
- In ETS, configure a KNX/IP tunnelling connection to that server and enter that port.
- Switch Remote ETS access off when you are done.
📘 Note: The remote tunnel closes automatically after 8 hours. Re-enable it if you need more time, and note the new port.
Group addresses
The Group addresses tab holds the server's group-address library — every address known from ETS, browsable as the ETS project tree ("N main groups · M addresses"). This is the same library the Devices workspace offers for drag-and-drop binding.
- Search by address, name or datapoint type using the search field above the tree.
- Import addresses from an ETS group-address XML export if you do not want to import the whole project: click Import Group Addresses in the header of this tab and choose the file ETS produces via Group Addresses → Export.
Select an address in the tree to open its detail panel:
| Field | Meaning |
|---|---|
| Last value | The most recent decoded value seen on the bus. |
| Last seen | When that value arrived. |
| Used by | Every device and automation bound to this address ("Not used by any device or automation" when free). |
| Watch on the bus monitor | Opens the Bus monitor tab with a reminder of the address. The table is not filtered: type the address in Search telegrams... to isolate its telegrams (see “KNX Bus Monitor”). |
💡 Tip: "Used by" is the quickest way to answer "what happens if this address changes?" before you rewire anything.
Binding KNX
In the Devices workspace, the KNX tab of the Communication objects rail shows the ETS project tree — your group addresses, organized as in ETS — whichever device is selected. If the tree is empty, click Import Group Addresses in the rail and choose your ETS group-address export (XML) (see “Group addresses” above).
To bind:
- Expand the device row (Show objects) to show its communication objects.
- Find the address in the tree, or type in Search group addresses....
- Drag the group address onto the matching object row. While you drag, empty rows read Drop here to assign. The address is assigned, and the object takes the address's datapoint type (DPT) from the ETS data, with the matching unit and number of decimals.
- Repeat for each command and feedback object of the device.
- Click Apply changes in the sidebar, then Apply changes in the Apply configuration changes dialog (see “Admin Panel Tour”).
📘 Note: A group address is dropped on one object row at a time. It cannot be dropped on the device as a whole: only a Home Assistant entity fills several objects in one drop (see “Home Assistant Integration”).
When the data type does not match. If the group address's DPT differs from what the object expects, the dialog Data type differs from object type explains the mismatch: the address's real data type will be bound to the object, and a transformation is required to convert between them. Click Cancel and drop the right address, or click Map anyway only when you intend to add the transformation — the object stays flagged on the Health page until you do (see “Value Transformations & Health”).
💡 Tip: Typical case: a status byte (DPT 5.010) feeding a boolean object — map anyway, then add a Bit Check transformation (see “Value Transformations & Health”).