In this piece
How can a water utility field-test a LoRaWAN meter reading and leak alarm?
A technician at the meter can read out the figure an operator should see at the next scheduled update on screen. A leak alarm takes more work to verify. What makes this model declare a leak, when does it report one, and can the person on duty identify the meter? Before ordering a batch, I would ask the supplier to demonstrate both the reading and the alarm on the same sample meter.
What did the Innsbruck field trial involve?
Innsbruck’s municipal utility, IKB, was already leading the project when we joined. A meter reading could still mean a trip, even where staff could collect it from a passing vehicle. The utility wanted its citywide LoRaWAN network to spare those trips and give staff more recent readings. In an interview published by IKB, a member of its telecommunications team describes responding earlier to leaks that customers had yet to notice.
We tested water meters in an ordinary installation location and in a spot where we expected weaker reception. Cargo-bike trackers were among the other devices we worked with. We developed dashboards with IKB to help staff see where something might be wrong.
Some messages arrived on a schedule. Others appeared only when an event occurred. The datasheet often matched what the device sent. With some devices, we only discovered a difference when we could compare it with a real packet. We kept real packets so we could replay them offline. Our IKB case study describes the fieldwork.
What should the supplier demonstrate before a volume order?
For an acceptance test, I would ask operations to choose a typical installation and a representative location with difficult reception. Use the intended meter settings at both. Ask the supplier for the reporting interval, the condition that triggers a leak alarm and the point at which the meter transmits it. Have the utility agree how old a reading can be and how long the duty team can wait for an alarm.
| Test | What to do | What to keep |
|---|---|---|
| Meter reading | Read the register at a known measurement time and find the corresponding reading on screen. Repeat over the agreed reporting intervals at both sites. | Meter ID, value and unit at both ends, measurement time and time received. Record missed reports separately. |
| Leak alarm | Use the manufacturer’s documented procedure on the test meter or test rig. Have the duty team watch the agreed alarm channel. | Trigger time, arrival time, meter ID and displayed alarm state. Record whether the operator could identify the installation to attend. |
| Return to service | End the test and follow the meter’s documented procedure for clearing the alarm. | Time and final state on screen. Record who will follow up if the alarm remains open. |
A test mode may let the meter send an alarm without exercising the sensor’s detection logic. That demonstration covers the reporting path from the meter onward. Ask the manufacturer what bench test would also establish detection.
Where do you look when the dashboard stays quiet?
First check when the report was due. A meter may carry an alarm flag in its next routine transmission. Once the expected time is clear, check whether the application received any packet from that meter around then. IKB’s account of its LoRaWAN network describes the part that sensors and gateways play in delivery.
If a packet arrived, compare the relevant field in the datasheet, the state you observed at the meter and the value your decoder produced. The Things Stack documentation on payload formatters explains how transmitted bytes become readable fields. Our LoRaWAN payload codec tester lets you run the same recorded packet through a decoder again. You can check a correction without waiting for the device to report another leak. Return to the installation to verify reception there.
Which results justify placing the order?
For each location, the buyer should be able to see how many readings were due, how many arrived and whether the duty team could identify the alarm within the agreed time. If readings arrive from both locations but the alarm arrives from only one, keep the second location open for a repeat test.
A proposal to add a gateway needs two checks before the buyer accepts the quote. Can the operator secure permission to install it and get access later for maintenance?
For teams still choosing a radio technology, our pilot cost comparison covers that decision. Once the network is chosen, the guide to scoping a pilot can help you agree on the evidence you need before placing the order. To arrange a field test with our municipal IoT team, bring a sample meter, its datasheet and two candidate sites.