Automatic meter reading allows you to collect water, gas, electricity, heating, and cooling meter readings without having to make on-site visits. With an Eziwan gateway connected via 4G LTE, M-Bus, Modbus, or pulse-type meters are read remotely, logged locally, transmitted via a secure VPN, and integrated into your billing system, ERP, SCADA, or energy platform.
Why Replace Manual Meter-Reading Rounds?
Manual meter reading rounds remain common in the water, energy, industrial, and service sectors, as well as in private networks and multi-site facilities. They work, but they present several limitations: delays in data availability, data entry errors, difficulty accessing meters, travel costs, no alerts between readings, and a lack of visibility into consumption patterns.
With a scattered network of meters, manual meter reading quickly becomes an operational burden:
- Meter readings arrive too late to detect a leak or a deviation;
- Meters located in basements, utility rooms, outdoor meter boxes, or industrial sites require significant logistical effort;
- Reading or data entry errors result in bill corrections;
- Customer disputes are difficult to resolve without accurate historical data;
- Non-communicating meters are not discovered until the next meter-reading round;
- Abnormal nighttime consumption goes unnoticed;
- The time-of-use profiles needed for energy optimization are not available;
- Older 2G or GPRS modems must be migrated to more sustainable technologies;
- Data remains scattered across paper readings, spreadsheets, line-of-business software, and operator portals.
4G LTE remote meter reading transforms the meter into a continuous source of data. It’s not just about faster billing—it also helps detect anomalies, track usage, optimize contracts, and make better use of networks.
The 2G and GPRS Context: Preparing for the Migration
Many legacy remote meter reading systems still use 2G, GPRS, or 3G modems. This installed base is becoming a risk, as carriers are gradually shutting down these networks to reallocate radio spectrum to 4G and 5G.
In France, ARCEP has published a timeline for the shutdown of 2G and 3G networks by operator. Orange began phasing out 2G in 2026 in certain areas, while SFR and Bouygues Telecom have also announced shutdown dates. The exact dates vary by operator, area, and network.
For an operator, the stakes are clear: a remote meter reading modem that still relies on 2G or GPRS could stop working at any moment. Migrating to a 4G LTE gateway—with dual SIM and connectivity monitoring—prevents the failure from going unnoticed until billing time.
Note: Important Consideration Do not simply migrate the SIM card. Also verify the meter protocol, power supply, antenna, local storage, cybersecurity, output API, and the ability to resume data transmission after an outage.
Architecture of a 4G LTE Remote Meter Reading System
The recommended architecture involves placing an Eziwan industrial gateway near the meters. It reads the meters via M-Bus, Modbus RTU, Modbus TCP, or pulse inputs, then transmits the data via 4G LTE to a central platform or directly to the customer’s information system.
This architecture prevents meters from being exposed to the Internet. The gateway initiates a secure outbound connection, stores the data in the event of an outage, and automatically synchronizes the meter readings as soon as the connection is restored.
Supported Counting Protocols
A meter fleet is rarely uniform. Some meters are new and connected, while others are older but have a pulse output. A remote meter reading gateway must therefore support multiple protocols.
| Protocol | Common Uses | Points to Watch For |
|---|---|---|
| Wired M-Bus | water, gas, heating, cooling, electricity | bus length, power supply, primary or secondary addressing |
| Wireless M-Bus | meters that are difficult to wire | radio coverage, transmission frequency, encryption |
| Modbus RTU | industrial RS-485 meters | parity, baud rate, address, wiring quality |
| Modbus TCP | network analyzers, Ethernet meters | IP plan, segmentation, network filtering |
| Pulse inputs | older mechanical meters | pulse weight, debouncing, counting direction |
| Dry contact | fault, status, local alarm | normally open or normally closed logic |
| API or files | third-party platforms | format, frequency, timestamping, error recovery |
The choice of protocol depends on the meters installed, the required level of accuracy, the reading frequency, the existing wiring, and billing requirements.
M-Bus: The Industry Standard for Meters
M-Bus is widely used for reading water, gas, heating, cooling, and energy meters in buildings, private networks, and commercial facilities. It allows multiple meters to be queried over a single bus using a data structure tailored for metering.
The information typically collected includes:
- cumulative reading;
- energy consumed;
- volume;
- instantaneous flow rate;
- power;
- supply and return temperatures;
- serial number;
- internal timestamp;
- meter status;
- manufacturer alarms;
- battery level for certain meters.
An M-Bus master gateway must handle discovery, addressing, polling frequency, detection of missing meters, and communication errors.
Tip: Good Practice Document each meter with its serial number, M-Bus address, medium, unit, location, conversion factor, and billing purpose. This mapping helps prevent many errors during integration.
Modbus for Industrial Meters and Network Analyzers
Modbus remains widely used in industry and technical infrastructure. It is used in electric meters, network analyzers, PLCs, variable-speed drives, inverters, metering stations, and energy equipment.
The main challenge is mapping the registers. Two Modbus devices may expose similar data using different addresses, formats, and conversion factors.
The items to check are:
- slave address;
- register table;
- data type: integer, floating-point, double-word;
- word order;
- unit;
- multiplicative factor;
- read frequency;
- error handling;
- consistency between index and instantaneous power.
Electric meter: LV network analyzer
Protocole : Modbus RTU
Adresse esclave : 12
Speed: 9,600 baud
Parity: even
Active Energy Index: Record 3204
Total active power: register 3054
Voltage L1 L2 L3: Registers 3020 through 3024
Meter reading frequency: 15 minutes
Instantaneous measurement interval: 1 minute
These settings must be verified on site. A transposed word or an incorrect factor can produce values that appear plausible but are actually incorrect, which is more dangerous than a visible error.
Pulse Meters and Old Mechanical Meters
Not all meters have a digital interface. Some older meters emit a pulse for each unit of volume or energy consumed. A gateway can convert these pulses into a cumulative reading or an estimated flow rate.
Examples:
- 1 pulse per 1 liter;
- 1 pulse per 10 liters;
- 1 pulse per 1 kWh;
- dry contact triggered by a passing magnet;
- Wiegand output depending on the meter;
- pulse relay on a gas or water meter.
The critical factors are the impulse weight, anti-rebound, local index persistence, and power outage management. The mechanical meter remains the physical reference: the digital index must be able to be reset during an inspection visit.
Data Collection Frequency: Real-Time or Periodic?
Remote data collection does not necessarily mean real-time data transmission. The appropriate frequency depends on the business use case.
| Use | Recommended Frequency | Objective |
|---|---|---|
| Monthly Billing | 1 day to 1 month | Reliable and traceable data |
| Leak Detection | 15 minutes to 1 hour | Identify continuous consumption |
| Building energy monitoring | 10 to 15 minutes | analyze load profiles |
| Industrial control | 1 to 5 minutes | monitor rapid deviations |
| Electrical grid analysis | 1 minute or less as needed | detect power, imbalance, overload |
| Battery meter | Event-based or low-frequency readings | Preserve battery life |
We need to strike a balance between accuracy, data volume, energy consumption, transmission costs, and operational utility. Collecting data that is of little use too often increases noise without improving decision-making.
Local Storage and Automatic Replay
A reliable remote meter reading system must be able to handle network outages. 4G may be temporarily unavailable, the VPN may go down, an antenna may be moved, or a service provider may be performing local maintenance. Even so, the data must not be lost.
The Eziwan gateway can store readings and measurements locally and then retransmit them when the connection is reestablished. This mechanism is essential for:
- avoid gaps in billing;
- maintain a history of load curves;
- Determine whether a meter was not recording data;
- Investigate a leak after a power outage;
- Synchronize data in chronological order;
- Distinguish between a communication failure and a lack of consumption.
The timestamp is just as important as the value. A reading received today may correspond to a measurement taken yesterday during a power outage.
Consumer Data Security
Access log data may seem less sensitive than access to a PLC, but it reveals usage patterns, schedules, absences, activity levels, and sometimes contractual information. It must therefore be protected.
A secure remote meter reading architecture includes:
- OpenVPN or IPsec VPN tunnel;
- data encryption;
- no public port exposure;
- certificate-based authentication;
- segmentation between the meter network and the office network;
- connection logging;
- API access control;
- key or token rotation;
- secure local storage;
- revocation of service provider access;
- monitoring of tunnel status.
For industrial or multi-site environments, this approach aligns with best practices for industrial connectivity and OT network security.
Integration with Billing, ERP, SCADA, and Energy Platforms
The value of remote meter reading depends on integration. A dashboard alone isn’t enough if teams then have to manually enter the meter readings into the billing software.
Eziwan can transmit data to multiple destinations:
| Destination | Data Sent | Usage |
|---|---|---|
| Billing software | validated meter readings, period, meter, customer | invoices, adjustments, disputes |
| ERP | consumption, sites, costs | internal re-billing, asset management |
| SCADA | real-time measurements, status, faults | technical operations |
| EMS | load curves, IPE | energy management |
| CMMS | non-communicating meters, faults, anomalies | maintenance interventions |
| Data platform | time series | advanced analysis, fraud detection |
| Business APIs | JSON, webhooks, files | custom integration |
Exports can be performed via REST API, webhooks, CSV files, JSON, SFTP, or dedicated connectors, depending on the client’s environment.
Data Quality: Validation Before Billing
A meter reading must be validated before it can be used for billing. Remote meter reading must therefore include consistency checks.
Common validation rules:
- monotonically increasing index for cumulative counters;
- rejection of inconsistent zero values;
- detection of sudden jumps;
- serial number check;
- unit verification;
- comparison with historical data;
- detection of a silent counter;
- timestamp check;
- flagging of an estimated value;
- reconciliation with a manual control reading.
This step prevents wiring, register, or conversion errors from resulting in billing errors.
Detection of Leaks and Abnormal Water Usage
Remote meter reading provides an immediate benefit in detecting anomalies. A water leak or abnormal electricity usage can be identified well before the next bill arrives.
Examples of useful rules:
- Continuous nighttime consumption on the water meter;
- Meter readings increasing outside of operating hours;
- Power usage exceeding the usual pattern;
- Exceeding the contracted power limit;
- Zero consumption even though the site is active;
- Meter that is no longer responding;
- Reversal of meter readings;
- Discrepancy between the main meter and submeters;
- Unusual gas consumption during hot weather;
- Gradual deviation from a baseline.
Analysis Rules must be adapted to the context. Nighttime consumption may be normal at a 24/7 industrial site, but abnormal in a closed commercial building. The usage profile is essential for avoiding false alarms.
Silent Meter Alerts and Fleet Monitoring
A silent meter is an operational issue. It may indicate a meter malfunction, a bus problem, a power outage, an incorrect address, a low battery, or a gateway that is offline.
Alerts must distinguish between several levels:
- Meter not responding;
- M-Bus inaccessible;
- Repeated Modbus error;
- Gateway offline;
- VPN tunnel unavailable;
- SIM card switched over;
- local storage nearly full;
- retransmission pending;
- index inconsistency;
- abnormal consumption.
A fleet dashboard allows you to track collection rates, sites with issues, non-reporting meters, transmitted data volumes, connected gateways, and maintenance activities.
Dual SIM and 4G LTE Availability
Remote data collection must work even when mobile coverage fluctuates. Dual SIM enhances resilience by allowing the gateway to switch between two carriers.
The criteria for switching may include:
- loss of mobile network connection;
- loss of VPN connection;
- excessive latency;
- packet loss;
- inability to send data;
- degraded radio signal;
- repeated synchronization failures.
A switchover must not result in any data loss. Indexes collected during the unstable period remain stored locally and are then retransmitted.
Remote Meter Reading for Water, Gas, and Electricity: Use Cases
| Sector | Affected meters | Primary value |
|---|---|---|
| Water Authority | cold water, zone metering, reservoirs | leak detection and billing |
| Industry | electricity, gas, compressed air, process water | energy monitoring and internal rebilling |
| Commercial | electricity, heat, cooling, water | commercial regulations, sub-metering, tenants |
| Multi-site real estate | master and sub-meters | site consolidation and comparison |
| District heating | heat, flow, temperature | billing and network efficiency |
| Campground or marina | water and electricity per site | individualized billing |
| Local Government | public buildings, schools, gyms | consumption management |
| Logistics | electricity, cooling, EV charging | usage monitoring and alerts |
The same architecture can support multiple fluids and multiple business lines, provided the data is structured correctly from the start.
Example of a Meter Layout
| Meter | Protocol | Unit | Frequency | Usage |
|---|---|---|---|---|
| General water, Building A | M-Bus | m³ | 1 hour | Leaks and billing |
| General electricity | Modbus TCP | kWh | 15 minutes | energy and power |
| Boiler room gas | M-Bus | m³ | 1 hour | heating monitoring |
| District heating | M-Bus | kWh | 15 minutes | rebilling |
| Tenant submeter | M-Bus | kWh | 1 day | monthly billing |
| Old water meter | pulse | liters | 15 minutes | flow estimation |
| Grid analyzer | Modbus RTU | kW | 1 minute | power overload |
This map must be shared among operations, billing, maintenance, and energy. It becomes the project’s reference.
Automatic Reports and Summaries
Remote meter reading makes it possible to automatically generate actionable reports:
- daily consumption;
- weekly consumption;
- monthly consumption;
- comparison with the previous period;
- Comparison between sites;
- Start and end indices;
- Load curve;
- Detected anomalies;
- Inactive meters;
- Estimated or missing data;
- Export for audit or dispute resolution.
Reports must remain easy to read. A good report highlights significant discrepancies, missing data, and recommended actions, rather than overwhelming the user with raw data.
Compliance, Traceability, and Auditing
Remote meter reading can be used for billing, but it must also provide robust traceability.
Important points:
- timestamping of meter readings;
- unique meter identification;
- correction history;
- status of estimated data;
- communication error log;
- configuration version;
- user access log;
- proof of retransmission after an outage;
- retention of export data;
- consistency between the physical meter and the digital reading.
In commercial buildings, meter readings can also contribute to energy monitoring and reporting requirements, particularly for energy performance initiatives. For regulatory or contractual purposes, the measurement method, scope, and data quality must be clearly defined.
Selection of Field Equipment
The success of a remote meter reading project depends heavily on the on-site installation.
Items to check before deployment:
- meter type and available protocol;
- gateway power supply;
- length and quality of the RS-485 or M-Bus;
- number of meters per line;
- location of the 4G antenna;
- radio signal quality of the service providers;
- need for a suitable IP-rated enclosure;
- temperature and humidity of the room;
- electrical protection;
- maintenance access;
- cybersecurity requirements;
- existing documentation.
Common Mistake Installing a 4G antenna inside a metal cabinet significantly degrades connectivity. An actual on-site radio measurement is better than a theoretical coverage estimate.
Typical Deployment with Eziwan
An automatic meter reading project generally takes place in several stages.
1. Meter Inventory
List the meters, utilities, serial numbers, protocols, locations, units, data owners, and billing purposes.
2. Communications Audit
Check M-Bus, Modbus RTU, Modbus TCP, pulses, wiring, addresses, power supply, Ethernet availability, and 4G coverage.
3. Data Mapping
Define the indices, metrics, units, factors, reading frequencies, alert thresholds, and validation rules.
4. Installing the gateway
The Eziwan gateway is connected to the meter bus, the 4G antenna, the power supply, and any pulse inputs.
5. Securing the Connection
The outbound VPN tunnel is enabled, certificates have been provisioned, API access is controlled, and public ports remain closed.
6. Backup Tests
Each meter is tested for: response, unit, index, consistency with the local display, timestamp, retransmission, and error handling.
7. IT Integration
The validated data is sent to the billing system, the ERP, the SCADA system, the CMMS, or the energy platform.
8. Supervision
Alerts, reports, inactive counters, collection rates, and gateway statuses are monitored from the multi-site dashboard.
Common Pitfalls
Several errors slow down or compromise remote meter reading projects.
- migrating connectivity without checking the meters;
- overlooking conversion factors;
- confusing meter readings with consumption over a given period;
- failing to handle network outages;
- collecting data too frequently without a business need;
- failing to validate data before billing;
- ignoring inactive meters;
- using a single SIM card at a remote site;
- exposing a meter interface to the Internet;
- failing to document M-Bus or Modbus addresses;
- forgetting to reconcile with the physical reading;
- creating alerts without a clear recipient.
Reliable remote meter reading is measured as much by its ability to handle exceptions as by its ability to collect meter readings during normal operation.
How Eziwan Fits Into Your Remote Meter Reading System
Eziwan provides the data collection, connectivity, and integration layer between field meters and your business tools. The Eziwan gateway reads M-Bus, Modbus, or pulse-based meters; connectivity solutions secure 4G LTE transmission; and the cloud platform centralizes dashboards, alerts, historical data, and exports.
This approach is suitable for utility companies, manufacturers, multi-site operators, property managers, local governments, private networks, and operators who want to reduce meter-reading rounds while improving data quality.
Conclusion
Automatic meter reading via 4G LTE replaces manual readings with a reliable, time-stamped, and integrated data collection process. Water, gas, electricity, heating, and cooling meters can be accessed remotely via M-Bus, Modbus, or pulse signals, with local storage, retransmission after an outage, alerts for silent meters, and data exports for billing.
With Eziwan, operators gain greater visibility, reduce errors, detect anomalies more quickly, and prepare to migrate legacy 2G or GPRS equipment to a modern, secure architecture that supports billing, energy management, and multi-site monitoring needs.
Further Reading
- Remote Meter Reading — automate the collection of water, gas, and electricity meter readings at your sites
- Wireless M-Bus Remote Meter Reading — wireless M-Bus remote meter reading for smart meters without wiring
- M-Bus Cloud — centralize your M-Bus data in the cloud for automated billing
- Modbus Meters — integrate your Modbus meters into your monitoring system
- Industrial Connectivity — choose the right connectivity for your remote meter reading sites