Solutions — Heat
Heat metering, from the meter to the data
EnerSync receives the M-Bus telegrams of heat meters over LoRaWAN and turns them into readable energy, volume, flow and temperatures, with the right units and the meter alarms in plain sight.
01 — What it solves
Clean metrology, no estimates
Cumulative meters, derived consumption
The meter transmits absolute totalisers; consumption per period is computed at read time. No stored deltas to fix afterwards.
Decoded alarms, not raw bits
M-Bus status bits become readable alarms, on a standard table extensible per model: you know what the meter is reporting, not just that it is.
Units resolved from the VIF
The same quantity can arrive at different scales: values stay as decoded and units and labels are resolved from the device VIF history.
02 — How it works
How the data arrives
01
Heat meters with a LoRa module
Elvaco CMi series meters (CMi4110, CMi4111, CMi4140, CMi4160e) sending the standard M-Bus telegram every 30–60 minutes.
02
LoRaWAN network
ChirpStack as network server, directly through the HTTP integration or through a queue (Azure Service Bus) with dead-letter recovery.
03
Decoding and identity
The message type is in the payload, not the port: the platform recognises it and binds the data to the meter + module identity, so a board swap does not create a new meter.
04
Dashboard and API
Readings, events and radio telemetry in the dashboard; the same data through the API with a daily partition computed at read time.
03 — Specifications
Under the hood
- Devices
- Elvaco CMi4110 / CMi4111 / CMi4140 / CMi4160e (M-Bus over LoRaWAN)
- Telegrams
- Standard 0x15, Compact 0x16, JSON 0x17; quantities scaled from the VIF
- Data
- Energy, volume, power, flow, flow and return temperatures, info bits, RSSI/SNR/battery
- Integration
- REST API /v1/heat: devices, readings per period, events, telemetry
04 — Regulation and obligations
Remote reading is a legal obligation
Directive (EU) 2018/2002 and (EU) 2023/1791 — EED
Heat meters and allocators installed since 25 October 2020 must be remotely readable; all of them by 1 January 2027. With remotely readable devices consumption information must be provided at least monthly.
Italian D.Lgs. 102/2014, art. 9, as amended by D.Lgs. 73/2020
Italian transposition: individual metering in multi-apartment and multi-purpose buildings, remote reading and billing information based on actual consumption.
UNI 10200
Allocation of heating and domestic hot water costs: it requires reliable, time-aligned readings for every unit, not estimates from a sample.
EN 1434 and MID annex MI-004
Heat meter requirements: the platform keeps totalisers as transmitted by the meter and resolves their units from the VIF, without reprocessing the legal measurement.
Indicative references, current at publication date: they do not replace a regulatory check for your case.
05 — Frequently asked questions
Frequently asked questions on heat metering
Can I connect the heat meters I already have?
If they carry an Elvaco CMi module with LoRaWAN output, yes. The decoder follows the standard M-Bus telegram, so the underlying meter model is not a constraint.
How often do readings arrive?
The cadence is configured on the module, typically every 30 or 60 minutes. The platform exposes the intraday data and a daily view computed at read time.
Do you handle cooling too?
The data model includes cooling energy and hot/cold volumes, but the fleet in the field today is heating only: the fields fill in when a combined meter arrives.
How do I get the data into my cost-allocation system?
Through the REST API with per-tenant tokens: readings come with units already resolved, so shares are computed on correct data.
06 — News
From the blog, on this vertical
Enersync 4: the new generation of the platform
Introducing Enersync 4, our cloud platform for meter reading, redesigned from the ground up — under your own brand, every metering network in one console, and data you can trust.