KNX to BACnet gateway

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

The protocols

Typical use case

A common commercial-building split: lighting, blinds, presence and room controllers run on KNX, while the central BMS and the chiller/AHU plant speak BACnet/IP. The two worlds normally need a Windows gateway PC and per-project engineering to talk. The WBox replaces that PC — it sits on both networks at once, so the BMS reads and commands KNX rooms (occupancy, temperature setpoints, lighting scenes, blind positions) and KNX feedback flows straight into BMS graphics and trends.

How the WBox bridges KNX and BACnet

Activate the KNX and BACnet drivers, then map points in the visual editor. Each KNX group address becomes a BACnet object: a temperature on DPT 9.001 to an Analog Input, a setpoint to an Analog Value, a switch or fault to a Binary Value/Input. The WBox exposes them as native BACnet objects the BMS discovers on its own — no extra database. Reads and writes propagate both ways; DPT-to-object-type conversion, scaling and any custom logic (Blockly or JavaScript) run on the gateway, no cloud dependency.

Example mapping

← All routes