Remote water meter reading no drive-by.

What is remote water meter reading?

Remote reading is the meter reporting its own register value over a network, on a schedule, instead of someone driving a route or a customer posting a card. The reading arrives, gets validated and is stored – and the annual reading round, with its missed appointments, transcription errors and estimated invoices, stops existing. No separate remote reader is needed at each meter: the radio sits in the meter itself or in a module fitted to it, and the network or a passing drive-by receiver does the reading.

The practical difference is not the effort saved on reading day. It is that the utility now has a complete, dated series per connection. Billing runs from measured figures, customer service can answer a disputed invoice with a curve, and a leak on the customer’s side is visible while it is still small.

Drive-by, walk-by or a fixed network?

Remote reading comes in two forms, usually called AMR (automatic meter reading) and AMI (advanced metering infrastructure).

• Walk-by and drive-by (AMR). The meter broadcasts its reading over wM-Bus, and a handheld receiver or a receiver in a vehicle picks it up in passing. Nobody needs access to the property, but someone still has to go out, and the utility gets a reading only when the round is done – often monthly or once a year.
• Fixed network (AMI). The meter sends its reading over LoRaWAN, NB-IoT or a wM-Bus gateway every day, and nobody goes out. The utility gets a daily series per meter, which is what leak alarms, monthly billing and water-loss analysis need.

Most utilities use both: a fixed network where it pays, and a planned walk-by or drive-by round for the addresses where it does not. On Divako both kinds of reading go into the same meter register and the same billing export.

Adding a remote reader to an existing meter

A meter without its own radio does not always have to be replaced. Depending on the model, there are three common ways to read it remotely:

• A radio module fitted to the meter’s register – for example Zenner’s EDC modules for mechanical meters – which then transmits the reading like a meter with a built-in radio.
• A pulse reader connected to a meter with a pulse output. It counts the pulses and reports the total over LoRaWAN or M-Bus.
• A wM-Bus to LoRaWAN bridge that receives the readings of existing wM-Bus meters in a building and forwards them over a fixed network, so walk-by meters can move to daily reading without a visit to each meter.

Whether a retrofit pays depends on the meter’s age. A meter that is due for replacement within a few years is usually better replaced with one that has the radio built in. The supported devices list shows which modules and readers run on Divako today.

How it works on Divako

1. Meter. Each meter is registered with its serial, its address and a device profile that knows its payload and its register format. The field installation flow records position and photo at mounting, so the register is right from day one.
2. Network. LoRaWAN, NB-IoT and wM-Bus carry the readings; drive-by and walk-by collection covers the rest and syncs when the collector comes back online. Oslo VAV reads more than 5,000 meters this way, across three technologies at once.
3. Platform. Every reading is decoded, normalised and checked: gaps, duplicates, implausible steps, and meters whose consumption has stopped changing. Read status per meter – last seen, missing reads, signal, battery – is visible as a list you can work through.
4. Analysis. Continuous flow, reverse flow, tamper and frost flags are evaluated as the readings arrive, so the meter fleet doubles as a leak-detection network.
5. Integration. A scheduled export or a native connector hands billing a complete, validated set – Komtek and Gemini are in production – and REST, MQTT, webhooks and SFTP serve everything else.

What to watch out for

• Legacy meters do not disappear on cutover day. A fleet is mixed for years, and the awkward part is the old protocol nobody wants to own. Decide early which platform is responsible for reading the old meters, or you will run two processes and reconcile them by hand.
• A missing read is not a missing meter. Radio has bad days, and a meter with a cumulative register can catch up on the next successful message. Write the gap-filling policy down before the first billing run, and make the export show which figures were measured and which were derived.
• Keep drive-by as a tool, not as an admission of failure. Every network has addresses where fixed collection is not economic. Planning a small drive-by round on purpose is cheaper than chasing full coverage into the last few percent.
• Reading time and billing period have to line up. If the export takes each meter’s latest reading whenever it happens to arrive, the invoice period differs per customer. Read to a fixed timestamp and check meter clock offset, or the first disputed invoice will find it for you.