Your energy meters speak wired or wireless M-Bus, sometimes Modbus. But their readings stay locked on the local bus: you cannot use them for billing, sub-metering or centralised consumption tracking without a dedicated metering infrastructure. M-Bus does not natively talk to the cloud.
M-Bus metering to the cloud
Push your M-Bus (and Modbus) meters to an MQTT broker or smart-me, as ready-to-use values.
The problem
How the WBox does it
The WBox gateway reads M-Bus meters (wired master, or wireless M-Bus via a USB adapter) and Modbus, normalises the readings and applies an optional unit conversion (Wh → kWh, scaling) in Blockly or JavaScript.
The values are then published over MQTT — as lightweight JSON messages — to the broker of your choice (private or public cloud), and/or pushed to smart-me. Publication frequency, a hysteresis and a consistency check keep the network and the platform from being flooded. You get centralised metering for a whole building, with no proprietary concentrator.
What you need
- a WBox gateway (S103, S485, G110…);
- the M-Bus driver (wired and wireless M-Bus);
- the MQTT driver and/or the smart-me driver;
- for wireless: a wireless M-Bus adapter.
The same principle applies: Modbus meters are read the same way, and the upload can target Azure, AWS or Google Cloud instead of a generic MQTT broker.
© 2026 Weble GmbH. All rights reserved. Conditions générales