MQTT to BACnet gateway

Need to connect MQTT and BACnet? The Weble WBox routes MQTT → 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 holds everything about a building, but BACnet does not travel well over the internet. To feed a cloud analytics platform, an energy-management service or a portfolio dashboard, the WBox streams selected BACnet objects to an MQTT broker and accepts setpoints and acknowledgements back. You get remote monitoring, fault detection and benchmarking across many sites, while the BMS keeps running exactly as before on site.

How the WBox bridges MQTT and BACnet

Activate the BACnet and MQTT drivers. BACnet objects (Analog Input/Value, Binary) map to MQTT topics carrying JSON payloads; COV subscriptions publish only on change, so bandwidth and broker load stay low. Values received from MQTT are written to the BACnet present-value. A JavaScript step can batch several objects into one message, add metadata, or apply hysteresis before publishing — keeping the cloud feed clean and the gateway in full control of what leaves the site.

← All routes