Remote Water Meter Reading in Apartment Buildings: How It Actually Works
Allocating water consumption per apartment is one of the most time-consuming jobs a building manager has. Knocking on doors, returning to units where nobody was home, transcribing handwritten numbers into a spreadsheet — remote reading removes that cycle entirely.
Here are the three approaches, and which building each one actually fits.
What remote reading requires
Remote reading means the meter value reaches a central system without anyone touching it. Three components are needed:
- A readable meter — a smart water meter, or a mechanical meter fitted with a pulse head.
- A transport path — the wireless or wired link that carries the value out of the building.
- A collection and reporting layer — software that stores readings, maps them to units, and turns them into reports.
Failed deployments almost always come from solving the first two and treating the third as an afterthought.
Option 1 — LoRaWAN (wireless, battery powered)
Each meter gets a battery-powered radio module that reports once or a few times a day to a single receiver (gateway) placed anywhere in the building.
Strength: no cabling. In occupied buildings this is decisive — you are not opening walls to run cable through existing risers.
Range: a single gateway typically covers an entire reinforced-concrete block; LoRa passes through floor slabs well. Detached-block sites usually need one to three gateways.
Limit: battery life is a direct function of reporting frequency. A meter rated for 8-10 years at one reading per day will not come close to that if configured hourly — and for billing, daily is already more than enough.
Option 2 — Wired M-Bus
M-Bus (EN 13757) is a two-wire standard designed specifically for meter reading. The bus also powers the meters, so there is no battery to manage.
Strength: no batteries, unlimited read frequency. In new construction the cabling is part of the project anyway, so the marginal cost is low.
Limit: retrofitting an M-Bus wire loop into an occupied building is rarely economical. A collector also supports a limited number of meters before a repeater is required.
Rule of thumb: if the building is still under construction, use M-Bus. If people already live there, use LoRaWAN.
Option 3 — Walk-by / drive-by
Meters broadcast over short-range radio and a technician collects the values while walking or driving past.
It removes the door knocking, but somebody still has to show up. There are no alarms, no leak detection, no daily visibility — you get one snapshot per month. Reasonable as a stopgap for scattered sites; not what we would recommend as a permanent installation.
Comparison
| LoRaWAN | Wired M-Bus | Walk-by | |
|---|---|---|---|
| Fits existing buildings | High | Low | High |
| Cabling required | No | Yes | No |
| Reading frequency | 1-4 per day | Unlimited | Monthly |
| Battery maintenance | Every 8-10 years | None | Every 8-10 years |
| Real-time leak alarm | Yes | Yes | No |
| Site visits | At install | At install | Every reading |
Deployment, step by step
1. Inventory the meters. How many per unit (cold water, hot water, heat), make and model. Without this list you cannot even quote the job properly.
2. Decide: replace or retrofit. If the existing meters accept pulse heads, the cost drops substantially.
3. Run a coverage test. Before committing, place one gateway and a few test devices at the hardest points — basement, furthest block, metal meter cabinets. Adding gateways after the fact is expensive and looks bad.
4. Record the meter-to-unit mapping. This is the subtlest failure mode on site: meters read correctly, data flows, but unit 8 on floor 4 is recorded against unit 8 on floor 3. Photograph each meter's serial number against its unit number during installation.
5. Set a realistic reading interval. Once per day is standard for battery meters. Pushing to hourly drains batteries and adds no value for billing.
6. Double-read the first month. Run remote and manual readings in parallel for one period and compare. Mapping errors surface only this way.
Three common mistakes
Reading too often. It wastes battery, and since "no data received" alarms are derived from the expected interval, a wrong interval produces a stream of false alarms.
Not recording meter replacements. A replacement meter starts from zero. If the system does not know, that unit's consumption goes negative or the period total explodes. The replacement date and the old/new index must be entered.
Treating reporting as optional. Data flowing is not the finish line. If building management does not get a ready per-unit list at month end, the deployment has not done its job.
Where Piklon fits
Piklon is the third component — the collection and reporting layer. It ingests readings over LoRaWAN, M-Bus and Modbus into one panel, builds a block / floor / unit consumption heatmap, computes per-unit period deltas and exports PDF and CSV reports. It is independent of meter brand.
It raises email alerts for continuous flow, missing data and abnormal consumption, and keeps dedicated records for field realities such as meter replacement and temporary offsets.
Frequently Asked Questions
Do existing mechanical meters have to be replaced?
Usually yes. A mechanical meter can only be read remotely if it accepts a pulse head, otherwise it has to be replaced with a smart meter. Some models support retrofit pulse heads; confirm with the manufacturer using the model plate on the meter.
How long do batteries last in wireless meters?
Manufacturers typically claim 8-10 years for LoRaWAN water meters. That figure assumes infrequent reporting. A meter configured to transmit hourly instead of daily will drain noticeably faster, and for billing purposes hourly data adds nothing.
Can the system detect leaks on its own?
It can detect continuous-flow patterns. If a unit's consumption never drops to zero, even overnight, that usually means a running toilet or a dripping tap. The system reports the pattern; locating the leak is still a physical check.
Can the readings be used for billing?
Piklon produces per-unit period deltas and exports them as PDF or CSV, which feeds the building management's own billing process. Using readings for legally binding commercial billing additionally requires the meter itself to be approved and stamped under local metrology regulations.