Need to connect M-Bus and KNX? The Weble WBox routes M-Bus KNX natively: one gateway speaks both protocols and maps data points in real time — no PC, no middleware, no cloud dependency.

M-Bus→WBoxgateway→KNXOne WBox gateway · native conversion · no PC

The protocols

M-Bus

M-Bus reads heat, water, gas and electricity meters over a dedicated 2-wire bus.

M-Bus driver →

KNX

KNX is the worldwide standard for home and building control, running over twisted-pair, IP or RF.

KNX driver →

Further reading: Wired vs wireless M-Bus: what is the difference? →

Typical use case

Heat, water, gas and electricity meters are wired in M-Bus (or wireless M-Bus), while the building visualisation and room control run on KNX. The WBox reads the meters and surfaces their consumption inside the KNX system — for tenant displays, load shedding, or simple sub-metering per floor or per zone. No proprietary M-Bus concentrator and no second supervision tool: the meter values live alongside everything else on the KNX visualisation.

Example deployment

Typical scenario Per-apartment meters into KNX In a multi-tenant residential building, heat and water meters sit on M-Bus, one set per apartment, while the building runs on KNX. The WBox reads each meter and publishes consumption to KNX group objects, feeding in-apartment displays and a simple per-zone sub-metering without a proprietary concentrator. Technical documentation →

How the WBox bridges M-Bus and KNX

Activate the KNX and M-Bus drivers. The WBox polls each meter on a configurable cycle and reads the records you need — energy in kWh, volume in m³, power, flow temperature — then maps them to KNX group addresses on DPT 13.x (4-byte counters) or 14.x (floats). A Blockly or JavaScript step handles unit conversion (e.g. Wh to kWh) or turns a rising index into an instantaneous value before it reaches KNX.

Example mapping

M-Bus meters are read-only, so the bridge feeds KNX:

  • M-Bus meter #5 record 0 active energy (kWh) → KNX 5/0/0 (DPT 13.010)
  • M-Bus meter #5 record 2 volume flow (m³/h) → KNX 5/0/2 (DPT 9.025)
  • M-Bus meter #5 record 4 flow temperature (°C) → KNX 5/0/4 (DPT 9.001)

Capacity & limits

  • M-Bus — M-Bus drives up to 190 metering slaves through a Weble level converter (250 per the standard).
  • KNX — KNX exposes the installation's group objects; a TP line carries up to 64 bus devices, extended through lines, areas and KNXnet/IP.

On the WBox, a driver licence enables the whole protocol — there is no artificial per-point tier to unlock. Capacity scales with the gateway model, from the compact S103 to the E413: you are bounded by the field bus, not by your licence.

Frequently asked questions

How do I read M-Bus meters into a KNX system?

A WBox with the M-Bus and KNX drivers reads the heat, water, gas and electricity meters and exposes their consumption as KNX group objects (DPT 13.x counters or 14.x floats) — for tenant displays, load management or sub-metering, with no proprietary concentrator.

Wired M-Bus or wireless M-Bus?

Both. Wired M-Bus via a level converter (RS485toMBus or EthernettoMBus that powers the bus), or Wireless M-Bus via a radio stick.

Is the bridge bidirectional?

Meter reading is read-only by nature: the WBox reads the M-Bus meters and publishes to KNX. On the same gateway it can additionally drive KNX actuators from other sources if the project needs it.

Which WBox model do I need?

Choose the WBox S485 KNX for the KNX TP interface on board, plus the M-Bus driver licence and the matching converter. A Blockly or JavaScript step can convert units (Wh to kWh) before the value reaches KNX.

What you need

One WBox gateway with these two driver licences:

M-Bus M-Bus Driver licence 100.00 CHF KNX KNX Driver licence 100.00 CHF

Route M-Bus KNX on your project

Find the right WBox gateway for your installation, or get in touch to validate your case.

Configure my gateway

Related routes

← All routes