In a building, every trade speaks its own protocol: comfort over KNX (lighting, blinds, HVAC), the BMS over BACnet, energy meters and field equipment over Modbus, utility metering over M-Bus, cloud and industrial systems over MQTT or OPC UA. On their own, these networks don’t talk to each other. Inter-protocol routing is the WBox’s core function: it reads data points from one protocol and exposes them on another, in real time, so systems that were never designed to interoperate exchange their values directly.
Routing runs entirely on the gateway. You enable the source and destination drivers, then map each data point; conversion, scaling and logic are executed on the WBox itself — no PC, no middleware, no cloud dependency. Routes can be one-way or bidirectional, and a single gateway handles many routes at once across all the protocols it supports.
The same engine bridges field buses to each other and to IoT and cloud services alike, from a KNX-to-BACnet conversion to pushing Modbus readings over MQTT. Because everything runs on one open device, you integrate existing installations without proprietary hardware and without locking yourself to a single manufacturer.
The same software also runs off the hardware: the complete stack — every driver, the routing engine, logic and supervision — is available as an installable Windows application, identical to what runs on the WBox. Deploy it on a PC, a server or a virtual machine — a flexibility most building-automation gateways don’t offer.
