Skip to content
Elausys

Your KNX installation. More possibilities.

The KNX bridge.
To Modbus TCP and more.

Map equipment controls and measurements to KNX group addresses. The Universal KNX Bridge runs on HyperVisu and acts as a universal bidirectional gateway between KNX and building functions from Modbus TCP, MQTT, HTTP, Home Assistant and other protocols.

A core feature of the HyperVisu server.

One address. A new connection.EXAMPLE MAPPING
KNX

KNX wall switch

Play / pause command

HYPERVISUUniversal KNX Bridge
Group address1/0/1
Playback control
CONNECTED AUDIO

Sonos speaker

Playback state

Start the music from a KNX switch. Map the supported playback controls and feedback through HyperVisu.

CONNECT THROUGHKNXModbus TCPMQTTHome AssistantNode-REDHTTP APIs

From device to group address

Make the connection.
Keep working in KNX.

The bridge brings device capabilities into the group-address structure of your project.

01 / CONNECT

Bring in the device.

Connect a supported device or service to HyperVisu, using Modbus TCP, Home Assistant, Node-RED or an HTTP API.

02 / MAP

Assign the group address.

Map a control, status or measured value to a standard KNX group address. Give the KNX installation access to that function.

03 / USE

Control. Read. Automate.

Use the mapped function from KNX switches, displays and logic. Commands and feedback travel through the bridge where the device supports them.

Beyond the bus

Different technologies.
One KNX project.

Bring the useful controls, events and measurements into the installation, wherever they originate.

Modbus TCP

Energy & equipment

Bring meter readings or supported equipment values onto KNX displays and into building logic.

Home Assistant

Connected devices

Use supported device capabilities from your Home Assistant integrations within the KNX project.

Node-RED

Custom automation

Trigger KNX actions from your flows and bring KNX into automation across systems.

HTTP APIs

IP devices & services

Map functions exposed by a supported API to KNX group addresses.

Connected audio

Control from the wall

Use KNX switches for supported audio functions, such as playback and volume.

Available controls and feedback depend on the connected device and its integration.

Built into HyperVisu

The bridge runs
on your server.

The Universal KNX Bridge works alongside the visualisation and the other HyperVisu services. Your KNX devices stay on the bus; the server connects through a KNX/IP interface or router on the local network.

Home Assistant and Node-RED can run on the same HyperVisu server.Bring their devices and flows into the same installation.
HVS-KNX HyperVisu server in its DIN-rail enclosure
HVS-KNX · HyperVisu server

For your next installation

A few practical answers.

Support & documentation
How do I connect Modbus TCP equipment to KNX?

Connect supported equipment to HyperVisu and map the required values or commands to KNX group addresses. Check the device's registers, data types and supported operations. For supported solar inverters, a dedicated INV-KNX gateway supplies the register mapping and operates without the HyperVisu server. KNX energy gateways.

Is the KNX Bridge bidirectional?

It can map KNX commands to supported devices and return their states or measurements to KNX. The direction depends on the function: a read-only meter provides measurements, while other equipment may accept commands. Configure and test each direction needed by the project.

Can I keep my KNX switches and displays?

Yes. Map the connected functions to standard group addresses and configure the switches, displays and logic that will use them. Existing hardware can remain in place, but address assignments and supported data-point types still need to match the required behaviour.

Which integrations can the KNX Bridge use?

The bridge is part of the HyperVisu server. It connects supported functions through Modbus TCP, Home Assistant, Node-RED and HTTP APIs. Check the equipment and the intended commands or feedback; protocol support alone does not mean every function can be mapped. Explore HyperVisu.

Does every IP device work automatically with KNX?

No. A device must expose usable functions through a supported protocol or integration. Connect it, select the needed capabilities and map them in the project. Proprietary or cloud-only equipment requires a compatible integration, and its own network or cloud dependencies remain.

Can KNX use readings from meters and heat pumps?

Yes, where the equipment exposes supported measurements through Modbus TCP or another supported integration. Map those readings for displays and logic. SG-Ready contacts are a separate control method requiring an appropriate actuator or interface; they are not a Modbus connection.

Connect the next part of your building.

Talk to us about the devices and systems in your project.

Discuss your integration