Use case

Energy management on live meter data

Main meters, sub-meters, power analysers and BMS controllers publish to ConnectMQ. Your energy management system, dashboards and production tools subscribe, so you see kWh, peak demand, gas and compressed air per site, line and asset — while you can still do something about it.

No card required

Example message

PUBLISH energy/dallas/line-1/main-meter/power

{"ts":"2026-10-22T10:15:00Z","kw":412.6,"kwh_total":1849213.4,"pf":0.94,"v_l1":231.2}

QoS 1 · TLS 8883 · PUBACK

The problem

One utility bill, no idea where it went

Energy cost arrives as one monthly invoice per site. Sub-meters exist, but they are read by different gateways, stored in a BMS or a vendor portal and never put next to production data. Peak-demand charges are discovered after the fact, and energy per part or per square metre remains a guess.

How it works

  1. 1

    Meter the loads

    Power analysers, sub-meters and pulse counters on lines, compressors, HVAC and chillers are read over Modbus, M-Bus or BACnet by a site gateway or the BMS.

  2. 2

    Publish per site and asset

    The gateway publishes kW, kWh, power factor, gas and compressed-air flow to topics per site, building, line or asset over TLS.

  3. 3

    Analyse and correlate

    Your EMS, historian or dashboard subscribes and puts consumption next to production counts or occupancy to calculate energy per part, shift or square metre.

  4. 4

    Act on peaks

    Threshold rules alert when demand approaches the contracted peak, and your control logic can publish a command to shed or shift non-critical loads.

ConnectMQ

What it needs from the broker

Every site, one broker

Factories, stores, offices and warehouses publish to one private broker with a consistent topic tree and separate credentials per site.

Many consumers, one reading

The same reading feeds the EMS, sustainability reporting, the plant dashboard and the 3D Digital Twin without reading the meter twice.

Alerts on demand

Threshold rules on kW or consumption notify facility and plant managers before a peak turns into an invoice line.

Reliable control commands

Load-shedding and setpoint commands use QoS 1 on dedicated command topics, and retained state shows what each load is currently set to.

What you get

  • Consumption visible per site, line and asset, not per invoice
  • Peak-demand events caught while they are happening
  • Energy per unit of output tracked next to production
  • Measured data ready for energy reviews and sustainability reporting
Example topics
energy/dallas/line-1/main-meter/power
energy/dallas/utilities/compressor-02/power
energy/dallas/site/demand              (retained)
energy/dallas/hvac/ahu-03/set

Industries that run this use case

Frequently asked questions

How do I send energy meter data to MQTT?

Many modern meters and power analysers publish MQTT natively. For Modbus, M-Bus or BACnet devices, a gateway — an industrial IoT gateway, a PLC or Node-RED on an edge PC — reads the registers and publishes the values to a topic per meter over TLS.

Can MQTT data be used for ISO 50001 energy management?

MQTT can carry the measured data your energy management system uses for energy reviews, baselines and energy performance indicators. ConnectMQ delivers that data; the analysis, reporting and any certification stay with your EMS and your organisation.

MQTT or BACnet for building energy monitoring?

They solve different problems. BACnet runs the building automation inside a site; MQTT moves data out of many sites to central applications. Most portfolios keep BACnet in the building and publish selected points to an MQTT broker for central energy monitoring.

Build it on ConnectMQ

Start on the Free plan — no card required — connect your first devices today and upgrade when you go live.