M-Bus to BMS Integration: Gateways to Modbus & BACnet
Bring M-Bus and wireless M-Bus meter data into your building management system without polling every meter directly. A gateway converts readings into Modbus registers or BACnet objects that your BMS or KNX system can read natively.
Commissioning the integration
Verify meters respond
Before wiring the gateway, confirm every meter answers on its primary address (1-250) or secondary address (8-digit ID). A meter that doesn't respond on the bus won't appear through the gateway either.
Configure point mapping
Map each meter reading to a Modbus register or BACnet object in the gateway's configuration -- this is where the M-Bus data model meets the BMS protocol your building system expects.
Document the mapping
Record which meter, which M-Bus address, and which Modbus register or BACnet object correspond to each other. This mapping is what the building operator and future maintainers rely on.
Test end-to-end
Confirm the BMS actually displays correct, live readings for every mapped point before sign-off -- not just that the gateway is powered and connected.
What the integration pattern covers
Wireless M-Bus in the EU
wM-Bus (EN 13757-4) operates in the 868 MHz band, with S, T and C communication modes covering everything from bidirectional stationary readers to long-battery-life transmit-only meters -- all of it can feed the same gateway as wired M-Bus.
Gateway as protocol bridge
A gateway reads M-Bus or wireless M-Bus meters and republishes their data as Modbus or BACnet points, so a BMS or KNX system never has to speak M-Bus directly.
Two addressing modes to check
Primary addressing uses a number from 1-250 per device on the bus; secondary addressing uses an 8-digit ID (manufacturer code, serial number, version, medium type) that lets you address a specific meter without prior assignment -- useful for large installations and meter swaps.
Not the same protocol as Modbus
M-Bus (EN 13757) was built specifically for utility metering; Modbus is a general industrial fieldbus used far beyond meters. A gateway converts between them -- they don't interoperate without one.
Wired and wireless on one integration
Wired M-Bus runs on a simple two-wire, polarity-free bus powered by the master; wireless M-Bus (EN 13757-4) covers meters that can't be wired. Both feed into the same gateway-to-BMS pattern.
Typical metering scope
Heat cost allocators, water meters, heat meters, gas meters and electricity meters are the devices most commonly brought into a BMS this way, usually alongside centralized reading software at building level.
Integration support
Independent engineering help to get M-Bus metering data reliably into your BMS.
- Review of your meter inventory and addressing (primary/secondary)
- Guidance on gateway selection for your target protocol (Modbus or BACnet)
- Point mapping documentation for handover
- Commissioning support through end-to-end testing
- Independent advice -- we don't push a single gateway brand
Frequently asked questions
Is M-Bus the same as Modbus?
No. M-Bus (EN 13757) is a European standard built specifically for utility meter reading; Modbus is a general industrial fieldbus used in drives, PLCs and inverters, among other things. Some meters offer both outputs, and gateways can convert between them, but they are not interchangeable without one.
What's the difference between primary and secondary addressing?
Primary addressing assigns each device a number from 1-250 on the bus. Secondary addressing uses an 8-digit unique ID (manufacturer code, serial number, version, medium type) and lets you reach a specific meter without a prior primary assignment -- handy for large sites or meter replacements.
Can wireless M-Bus meters go through the same gateway as wired ones?
Many gateways handle both, since wireless M-Bus (EN 13757-4) is the same application layer over a radio link in the 868 MHz band with S, T or C modes, rather than a different data model.
What does the gateway actually do?
It reads meter values over M-Bus or wireless M-Bus and republishes them as Modbus registers or BACnet objects, so the BMS reads points in its own protocol instead of polling every meter over M-Bus.
What should be checked before commissioning starts?
Confirm every meter responds on its bus address, check your segment isn't overloaded by unit-load budgeting on the master or repeaters, and have a clear point-mapping list ready before configuring the gateway.
Planning an M-Bus to BMS integration?
Talk to our engineers about your meter inventory, gateway options and commissioning plan before you wire anything.