An IoT energy meter measures electricity at a device, circuit or building and sends the readings over a network to software that turns them into usage charts, alerts or bills. This guide covers how the meter works inside, which protocols and networks carry the data, the accuracy rules for billing and where a ledger helps.
Some systems also meter gas, water or heat with the same network and software. A project makes four decisions: the accuracy the use case needs, the protocols the meters support, the network that carries the readings, and whether the data will set anyone's bill. If it does, legal metrology rules apply.
How an IoT energy meter works
A smart energy meter for IoT use has four main parts:
- Current and voltage sensing. A current transformer (CT) clamp or a shunt resistor senses current, and a voltage divider or transformer senses voltage.
- Metering chip. A dedicated chip samples both signals many times per cycle and calculates voltage, current, active power, reactive power and accumulated energy. Common chips include the ADE7953, ATM90E32, BL0942 and CSE7766.
- Microcontroller and radio. A microcontroller reads the chip's registers and sends the values over Wi-Fi, cellular, LoRaWAN or a wired bus.
- Software. A gateway or cloud service stores the readings, checks them and shows the results.
Many smart plugs use exactly this design. Hobby and building projects often pair an ESP32 board with a ready-made module such as the Peacefair PZEM-004T. Open-source firmware such as ESPHome supports these chips and modules directly.
Types of energy metering
| Type | Who installs it | Typical use | Key constraint |
|---|---|---|---|
| Utility smart meters (AMI) | The utility or a meter operator | Billing, time-of-use tariffs and grid operations | Regulated. Data access goes through the utility or a national data hub. |
| Billing-grade submeters | Landlords, campuses and EV charging operators | Billing tenants or charging sessions | Must be certified for billing, such as under MID in the EU |
| Monitoring meters and CT clamps | Facility managers, homeowners and industrial sites | Finding waste, load profiles and alerts | Accurate enough for analysis but not for legal billing |
| Smart plugs | Consumers | Appliance use and on/off control | Low accuracy, tied to a consumer app or platform |
How the data flows
Meter interfaces
Utility meters usually use DLMS/COSEM, the IEC 62056 family of standards, which defines a data model for registers, load profiles and events. Commercial submeters often offer Modbus RTU over RS-485 or Modbus TCP, and some offer M-Bus. Many meters also have pulse outputs or optical ports for simple connections.
In some markets, homes can read near-real-time data from the utility meter through a local interface. In Great Britain, for example, a consumer access device connects to the smart meter's home area network.
Connectivity
| Network | Fits |
|---|---|
| LTE-M or NB-IoT cellular | Scattered sites with no local network |
| LoRaWAN or Wireless M-Bus | Many meters in one area that send small amounts of data |
| RF mesh | Utility networks with dense meter populations |
| Ethernet or Wi-Fi | Meters inside buildings with an existing network |
A gateway often reads several meters over RS-485 and forwards the readings over MQTT or HTTPS.
Head-end and meter data management
A head-end system manages communication with the meters. A meter data management (MDM) system checks readings, estimates missing values, handles meter replacements and produces billing-ready interval data. The checking rules matter as much as data collection. Typical rules catch spikes, missing intervals and reverse flow, and bills built from unchecked data lead to disputes.
Accuracy and legal metrology
If readings decide what someone pays, the meter usually needs approval for billing. In the EU, active electrical energy meters for billing must comply with the Measuring Instruments Directive (2014/32/EU), and the UK has an equivalent set of rules. Other regions have their own approval systems.
Monitoring-grade CT clamps give useful insight, but their readings generally cannot be the basis of a tenant invoice. Check the local rules before the product offers billing features.
What to build on top
- load profiles and baselines that show when and where energy is used
- alerts for unusual use, loads that run after hours and power-quality problems
- tenant and EV charging bills based on certified meters
- demand response and load shifting linked to tariffs or grid signals
- solar and battery monitoring, including energy exported to the grid
These features overlap with building and industrial systems. The guides to industrial IoT solutions and smart home solutions cover those architectures, and the page on smart poles covers energy metering at street level.
Where blockchain helps with energy data
In energy, several independent parties often pay each other based on shared data, so people often suggest ledgers for energy data. Three cases are common:
- Energy attribute certificates: renewable energy certificates and guarantees of origin show that a megawatt-hour came from a specific generator. Official registries already track them. Tokenized certificates can make hourly matching and transfers easier, but the tokens must stay linked to the official registry so that no certificate is counted twice. The guide to tokenization platforms covers the general mechanics.
- Peer-to-peer trading pilots: several countries have run pilots where neighbors trade rooftop solar power. Most markets license retail energy supply, and the grid operator runs settlement, so P2P trading tends to become a pricing layer on top of normal settlement.
- EV charging roaming: several charging operators and payment providers must reconcile each session. Roaming protocols such as OCPI usually handle this reconciliation without a ledger.
For one building, campus or utility, a time-series database with signed readings and access control works better than a ledger. A ledger proves that records were not changed later. It cannot prove that the meter measured correctly, and meter certification exists for that purpose. The guide to blockchain IoT development covers the wider trade-offs.
Implementation checklist
- Decide whether the data will be used for billing, because billing sets the meter certification needs.
- Survey the sites for meter types, protocols, wiring and network coverage.
- Choose gateways and a data model, store timestamps in UTC and record the unit of each value.
- Write the rules for checking, estimating and editing readings before building dashboards.
- Secure devices and data with unique credentials, encrypted transport, role-based access and retention rules for personal data.
Frequently asked questions
What is an IoT energy meter?
An IoT energy meter measures electricity use and sends the readings over a network, such as Wi-Fi, cellular or LoRaWAN. Software then shows the data, raises alerts or produces bills.
Can I bill tenants using CT clamp readings?
Generally not in markets with legal metrology rules, where billing usually requires a certified, type-approved meter. CT clamps suit monitoring and cost allocation analysis.
What reading interval should I use?
Fifteen-minute or thirty-minute intervals match many tariffs and grid settlement periods. One-minute or faster data helps fault finding but needs more storage and bandwidth.
Is blockchain needed for peer-to-peer energy trading?
No. P2P trading can run on normal platforms, with the grid operator handling settlement. A ledger may help when many independent parties need a shared record without a central operator, but regulation usually still requires a licensed supplier.
Which protocol do commercial meters use?
Most commercial submeters use Modbus over RS-485 or TCP, and utility meters usually use DLMS/COSEM. Each meter model's documentation lists its register map.