An IoT energy meter solution measures electricity (and sometimes gas, water or heat) at a device, circuit or building, sends readings over a network, and turns them into usage analytics, alerts or bills. The engineering choices are about measurement accuracy, which protocols the meters speak, how readings travel, and whether the data will be used for billing, which brings legal metrology rules into play.
Types of metering
| Type | Who installs it | Typical use | Key constraint |
|---|---|---|---|
| Utility smart meters (AMI) | Utility or meter operator | Billing, time-of-use tariffs, grid operations | Regulated; access to data via utility or data hubs |
| Billing-grade submeters | Landlords, campuses, EV charging operators | Recharging tenants or charging sessions | Must be certified for billing (e.g. MID in the EU) |
| Monitoring meters and CT clamps | Facilities, homeowners, industrial sites | Finding waste, load profiling, alerts | Accuracy adequate for analysis, not legal billing |
| Device-level smart plugs | Consumers | Appliance usage and control | Low accuracy, consumer ecosystems |
How the data flows
Meter interfaces
Utility meters generally speak DLMS/COSEM (the IEC 62056 family), which defines a data model for registers, load profiles and events. Commercial submeters often expose Modbus RTU over RS-485 or Modbus TCP, and some offer M-Bus. Many meters also have pulse outputs or optical ports for simple integration. In homes, some markets give consumers access to near-real-time data through a local interface on the utility meter.
Connectivity
Options depend on density and location: cellular LTE-M or NB-IoT for scattered sites, LoRaWAN or Wireless M-Bus for dense, low-data deployments, RF mesh in utility networks, and Ethernet or Wi-Fi inside buildings. A gateway often polls several meters over RS-485 and forwards readings over MQTT or HTTPS.
Head-end and meter data management
A head-end system manages communication with meters; a meter data management (MDM) system validates readings, estimates gaps, handles meter replacements and produces billing-ready intervals. Validation rules (spike detection, missing intervals, reverse flow) matter as much as collection. Bills built from unvalidated data generate disputes.
Accuracy and legal metrology
If readings determine what someone pays, the meter usually has to be type-approved for billing. In the EU and UK, that means compliance with the Measuring Instruments Directive (MID) for active energy meters; other regions have equivalent regimes. Monitoring-grade CT clamps are fine for insight but generally cannot be the basis of a tenant invoice. Check local rules before you promise billing features.
What to build on top
- Load profiles and baselines that show when and where energy is used.
- Alerts for abnormal consumption, after-hours loads and power-quality issues.
- Tenant and EV charging billing using certified meters.
- Demand response and load shifting tied to tariffs or grid signals.
- Solar and battery monitoring, including export.
These features overlap with building and industrial systems; see industrial IoT solutions and smart home solutions for adjacent architectures, and smart poles for street-level energy metering.
Where blockchain is genuinely useful
Energy is one of the few IoT domains where several independent parties settle money based on shared data, so ledger ideas come up often. An honest assessment:
- Energy attribute certificates: renewable energy certificates and guarantees of origin track that a megawatt-hour came from a specific generator. Registries already exist; tokenized certificates can make granular, hourly matching and transfer easier, but they must stay linked to the official registry to avoid double counting. The general mechanics are covered under tokenization platforms.
- Peer-to-peer trading pilots: neighbors trading rooftop solar has been piloted in several countries. In most markets, retail energy supply is licensed and settlement runs through the grid operator, so P2P trading tends to become a pricing layer on top of conventional settlement.
- EV charging roaming and settlement: multiple operators and payment providers reconcile sessions; established roaming protocols such as OCPI usually solve this without a ledger.
For an individual building, campus or utility, a time-series database with signed readings and proper access control does the job better. The ledger proves records were not altered later; it cannot prove the meter measured correctly, which is what certification is for. The general trade-offs are discussed under blockchain IoT development.
Implementation checklist
- Decide whether data will be used for billing, which sets meter certification requirements.
- Survey sites: meter types, protocols, wiring, and connectivity coverage.
- Choose gateways and a data model, including timestamps in UTC and units.
- Build validation, estimation and editing rules before dashboards.
- Secure devices and data: unique credentials, encrypted transport, role-based access, retention policies for personal data.
Frequently asked questions
Can I bill tenants using CT clamp readings?
Generally not in markets with legal metrology rules. Billing usually requires a certified, type-approved meter. CT clamps are suitable for monitoring and allocation analysis.
What reading interval should I use?
Fifteen-minute or thirty-minute intervals align with many tariffs and grid settlement periods. One-minute or faster data helps diagnostics but increases storage and bandwidth.
Is blockchain needed for peer-to-peer energy trading?
No. P2P trading can run on conventional 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 requires a licensed party anyway.
Which protocol do commercial meters use?
Modbus over RS-485 or TCP is the most common for commercial submeters. Utility meters typically use DLMS/COSEM. Check each model's documentation for register maps.