BACnet, Modbus, M-Bus and KNX: open protocols, plainly explained

Every building management system is really a conversation between devices — controllers asking sensors what they see, telling valves what to do, asking meters what's been used. Protocols are the languages that conversation happens in, and whether they're open or proprietary shapes everything about who can work on your building and what it costs. Here are the four you'll meet most, without the marketing gloss.

BACnet — the native tongue of buildings

BACnet was designed specifically for building automation, and it shows. Devices describe themselves as standard objects — an analogue input, a schedule, an alarm — with standard properties, which means a supervisor can discover a compliant device and largely understand it without a translation exercise. It runs over ordinary IP networks (BACnet/IP) for the backbone and over simple twisted-pair (MS/TP) for field devices. If you're specifying anything new today, BACnet/IP should be the default answer unless there's a good reason otherwise.

Modbus — simple, everywhere, slightly stubborn

Modbus is far older and far simpler: a device is just a list of numbered registers holding values. That simplicity is why it's everywhere — chillers, boilers, inverters, power meters, packaged plant of every kind. The catch is that the registers mean nothing by themselves; you need the manufacturer's register map, and the integration is only as good as the engineer's care in mapping it. Done properly it's rock solid. Done lazily it's a screen full of numbers nobody trusts.

M-Bus — built for meters

M-Bus (Meter-Bus) exists for one job: reading utility meters — heat, water, electricity, gas — cheaply and reliably over long two-wire runs. If your energy strategy involves submetering (and it should), M-Bus is usually how those readings get into the system.

KNX — the room-level specialist

KNX lives at the room end of the building: lighting, blinds, room panels, small fan coils. It's decentralised — devices talk directly to each other — and mature. In practice you'll often see KNX handling rooms with BACnet handling plant, bridged so the supervisor sees both. DALI plays a similar role specifically for lighting control and fits the same pattern.

What to take from this

Openness is a procurement decision as much as a technical one. Specify open protocols, yes — but also insist on open engineering: documentation, register maps, backups and credentials handed over as deliverables. That combination is what keeps you free to choose who works on your building next year, and the year after that.