M-Bus to BACnet gateway

Need to connect M-Bus and BACnet? The Weble WBox routes M-Bus → 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 BACnet BMS needs the meter data sitting on an M-Bus loop — district heating, cold and hot water, electricity sub-meters. Instead of a separate metering concentrator and a manual export, the WBox exposes each M-Bus meter as BACnet objects the BMS reads directly. This is the standard path for tenant billing, ESG and consumption reporting in commercial and multi-tenant buildings, with every reading time-stamped and trended in the same system.

How the WBox bridges M-Bus and BACnet

Activate the BACnet and M-Bus drivers. The WBox polls the M-Bus meters on a schedule, reads the records you select (energy, volume, power, flow and return temperatures) and maps each to a BACnet Analog Input with the correct unit and COV increment. The BMS then polls them like any native point. A JavaScript step can derive values — for example turning a kWh index into instantaneous power — before they appear on BACnet.

Example mapping

← All routes