Need to connect KNX and Modbus? The Weble WBox routes KNX Modbus natively: one gateway speaks both protocols and maps data points in real time — no PC, no middleware, no cloud dependency.

The protocols

KNX

KNX is the worldwide standard for home and building control, running over twisted-pair, IP or RF.

KNX driver →

Modbus

Modbus (TCP/IP and RTU) connects PLCs, meters, variable-speed drives and countless industrial devices.

Modbus driver →

Typical use case

Room control is KNX, but the energy meters, variable-speed drives, heat pumps and inverters on site are Modbus (RTU or TCP) — two ecosystems that ignore each other. The WBox bridges them: live power, flow and pump status from Modbus equipment appear inside the KNX visualisation, and KNX switch or setpoint objects drive Modbus actuators. Facility teams get one consistent view and one set of controls instead of two parallel systems.

How the WBox bridges KNX and Modbus

Activate the KNX and Modbus drivers and map points in the editor. Modbus holding or input registers (e.g. active power in kW, a pump run state) map to KNX group addresses on DPT 14.x or 1.x; KNX commands map to Modbus coils or registers to start/stop a drive or push a setpoint. Word order, signed values and scaling are set per register, and a Blockly or JavaScript step can rescale or combine values on the way through — all on the gateway.

Example mapping

A worked example, all on one gateway:

  • Modbus holding 40001 active power → KNX 5/1/0 (DPT 14.056, W)
  • KNX 0/1/2 switch (DPT 1.001) → Modbus coil 00010
  • Modbus input 30002 pump running → KNX 5/0/1 (DPT 1.001)

Route KNX Modbus on your project

Find the right WBox gateway for your installation, or get in touch to validate your case.

Configure my gateway

← All routes