Remote Water Meter Reading with Dragino LoRaWAN and ProSense Flow Meters
A water meter that only gets checked once a month can hide a leak for weeks. On a farm, at an irrigation pump, or beside a remote storage tank, that delay can mean lost water, wasted power, and a bill that makes no sense when it finally arrives.
Pulse-output water and flow meters solve the measurement side of the problem. Dragino LoRaWAN hardware solves the distance problem. Put them together and a mechanical or electronic meter can send usage data from a paddock, bore line, factory inlet, wash-down area, tank fill point, or remote pump station without running data cables back to site.
The basic idea is simple. A ProSense flow meter produces a pulse each time a known volume of water passes through it. A Dragino LoRaWAN pulse counter or I/O node counts those pulses, converts them to litres or cubic metres, and sends readings over a LoRaWAN network at set intervals.
How a pulse-output water meter works with LoRaWAN
Most pulse-output meters use a simple contact, reed switch, open collector, Hall effect sensor, or similar output. The meter does not need to send a complex data packet. It only needs to close a contact or change state each time a set amount of water passes through.
For example, a meter may be configured so that:
1 pulse equals 1 litre
1 pulse equals 10 litres
1 pulse equals 100 litres
1 pulse equals 1 cubic metre
The Dragino device monitors the pulse input and keeps a count. The LoRaWAN network does the communication. A gateway receives the radio message and forwards it to a network server, then the data can be shown in a dashboard, sent to a SCADA system, stored in a database, or passed to an alerting platform.
This makes Remote Water Meter Reading with Dragino LoRaWAN and ProSense Flow Meters a good fit where mains power, Ethernet, Wi-Fi, or cellular equipment would be too costly or too hard to maintain.
A typical chain looks like this:
ProSense pulse-output flow meter
Measures water flow and creates one pulse per configured volume.
Dragino LoRaWAN pulse counter or I/O node
Counts pulses, stores totals, and sends data on a schedule.
LoRaWAN gateway
Receives radio packets from field devices.
Network server and application
Converts the raw payload into litres, cubic metres, flow rate, totals, and alerts.
The hardware is not trying to replace the meter. It extends it. The meter remains the trusted measurement point, while the Dragino device adds long-range wireless reporting.
Choosing the right Dragino hardware for pulse counting
The best Dragino device depends on the output type from the meter, the installation environment, and how the data will be used.
For a single pulse-output water meter in a remote location, a battery-powered LoRaWAN pulse counter is often the simplest option. For several meters in one cabinet, a LoRaWAN I/O controller with multiple digital inputs may be a better fit. For sites with power available, a mains-powered or externally powered unit can report more often without worrying about battery life.
Look for these features when matching hardware:
Requirement | Why it matters |
Pulse or digital input support | The Dragino unit must be able to detect the meter output cleanly. |
Input type compatibility | Reed switch, dry contact, open collector, NPN, PNP, and powered pulse outputs need the right wiring method. |
Pulse count storage | The node should keep a running count, including between transmissions. |
Debounce filtering | Mechanical reed switches can bounce, so filtering helps prevent false counts. |
Weather protection | Outdoor sites need a suitable enclosure and cable glands. |
External antenna option | Useful near tanks, metal cabinets, pump sheds, and low signal areas. |
Battery or solar support | Remote sites often need long unattended operation. |
Some Dragino nodes are better suited to simple field sensing. Others are designed as industrial I/O devices with more inputs and power options. The meter output, expected pulse rate, and reporting plan should drive the selection.
The safest approach is to confirm three things before installation:
What type of pulse output the ProSense meter provides
The maximum pulse frequency at peak flow
The input specification of the Dragino device
If the meter sends pulses faster than the LoRaWAN node can count, the total will fall behind. That risk increases when litres-per-pulse is set very low on a high-flow pipe.
Setting litres per pulse correctly
The litres-per-pulse value is the link between the physical meter and the digital reading. If that value is wrong, every reported total will be wrong.
A pulse is only a count. The application needs to know what each count means.
Use this basic formula:
`Volume = Pulse count × Litres per pulse`
If a meter sends 1 pulse per 10 litres and the Dragino device records 4,500 pulses, the total volume is:
`4,500 × 10 = 45,000 litres`
That can also be displayed as:
`45 cubic metres`
Where possible, set the litres-per-pulse value from the meter documentation, meter label, dial marking, or pulse module specification. Do not guess based on pipe size alone. Two meters of the same diameter can have different pulse scales depending on the pulse module fitted.
Common configuration choices include:
Meter pulse scale | Best used for | Trade-off |
1 litre per pulse | Low flows where fine detail matters | More pulses to count and send |
10 litres per pulse | General water monitoring | Good balance for many sites |
100 litres per pulse | Larger irrigation and industrial lines | Less detail at very low flows |
1,000 litres per pulse | Bulk water and large transfer lines | Coarser data, but lower pulse rate |
A small dosing line may need high resolution. A centre pivot irrigation supply or bulk tank fill line may not. The goal is to capture useful data without creating an unnecessary pulse burden for the input device.
Totalisation and flow rate are not the same thing
Remote meter reading is usually built around totalisation. The system counts every pulse and builds a running total.
That running total answers questions such as:
How much water has passed through this meter today?
How much did this paddock use overnight?
Did the wash-down area use more water this week than last week?
Has a remote tank filled to the expected volume?
Is there unexplained use when the site should be idle?
Flow rate is different. Flow rate estimates how quickly water is moving at a point in time. A system can calculate flow rate by comparing pulse counts across a time period.
For example:
The previous report showed 10,000 litres total.
The current report shows 13,000 litres total.
The reports are 30 minutes apart.
The flow across that interval was 3,000 litres per 30 minutes, or 100 litres per minute on average.
This is useful, but it is still an average across the reporting interval. If the flow stopped and started several times between reports, the system may not show each short event unless the reporting interval is short enough or the field device supports event-based reporting.
For water accounting, billing support, compliance logs, and usage trends, totalisation is the foundation. For pump protection, burst detection, or process control, near-real-time flow rate may also be needed.
Choosing reporting intervals that match the job
LoRaWAN is designed for small packets of data sent at sensible intervals. It is not intended to stream live process data every second. That is one reason it works well on batteries and over long distances.
A water meter installation might report:
Every 5 to 15 minutes for irrigation scheduling, leak checks, or active operations
Every 30 to 60 minutes for general usage tracking
A few times per day for remote infrastructure where only a daily total matters
On a pulse threshold, if the hardware and application support event-based reporting
Shorter intervals give fresher data, but they use more battery and more network airtime. Longer intervals save power, but they delay visibility.
A good reporting plan balances four needs:
How quickly a problem must be seen
A leak on a high-pressure main may need alerts within minutes. A storage tank make-up line may not.
How much detail the application needs
Irrigation blocks benefit from hourly or sub-hourly usage data. Monthly meter replacements do not.
How much power is available
Battery-only devices should avoid needless transmissions.
What the LoRaWAN network can support
Gateway coverage, payload size, spreading factor, and local duty cycle rules all affect good network design.
For many remote water sites, a 15, 30, or 60 minute interval is a practical starting point. The interval can then be adjusted after the first few weeks of data show how the site behaves.
Battery and solar considerations for remote meters
Battery life is one of the main reasons to use LoRaWAN for water metering. A pulse counter can sleep most of the time, wake to count events or send scheduled reports, then return to low-power mode.
Actual battery life depends on several factors:
Reporting interval
LoRaWAN signal strength
Spreading factor and transmit power
Pulse input activity
Temperature
Battery size and chemistry
Sensor wiring and any external power draw
Whether acknowledgements are used for every message
A device at the edge of coverage usually uses more power than one close to a gateway. Poor antenna placement can reduce battery life as well as reliability.
For battery-only installations, keep the design simple:
Place the antenna where it has the clearest practical path to the gateway.
Use a reporting interval that matches the real need.
Avoid confirmed uplinks unless the application truly needs them.
Check that the pulse input does not require the node to power an external circuit.
Protect cables from water, UV exposure, rodents, and machinery.
Solar is useful where reports need to be frequent, where the site is hard to visit, or where the LoRaWAN node also powers another sensor. A small solar system should include a suitable charge controller, battery storage for cloudy days, and an enclosure that can handle heat, dust, moisture, and insects.
Solar does not fix poor design. If the antenna is inside a steel cabinet or the device is sending far more often than needed, power problems may continue. Start with a low-power communication plan, then use solar where it adds real value.
Where ProSense flow meters fit
ProSense flow meters are a strong pairing for Dragino equipment because they give the field measurement point that the LoRaWAN device needs. The meter provides the pulse. The Dragino device provides wireless collection.
This pairing works well when the project needs a clear division of roles:
ProSense flow meter | Dragino LoRaWAN hardware |
Measures water movement in the pipe | Counts pulses from the meter |
Provides a known pulse output | Sends readings over long-range radio |
Suits the pipe size and flow range | Suits the network, power, and input needs |
Stays installed as the primary meter | Connects the meter to remote software |
When specifying the meter, match it to the real hydraulic conditions. Pipe diameter matters, but so do expected minimum flow, maximum flow, pressure, water quality, installation orientation, straight pipe runs, and whether the meter will see clean water, bore water, recycled water, or process water.
A good meter choice reduces false confidence. If the meter is oversized, low flows may not register well. If it is undersized, pressure loss and wear can become problems. If the pulse output is not suited to the input device, the data chain becomes harder than it needs to be.
For simple remote readings, a pulse-output ProSense meter and a Dragino counter can be enough. For harsher industrial water or higher-value process monitoring, the application may also need isolation, surge protection, shielded cable, local display, or a nearby control panel.
Applications across farms, irrigation, industry, and remote infrastructure
Remote water data is useful anywhere the meter is far from the person who needs the reading.
Farms and stock water
On farms, pulse meters can track water pumped from bores, dams, tanks, and reticulation mains. A single dashboard can show which lines used water overnight and whether a trough network is drawing when it should not.
Common farm uses include:
Bore output logging
Tank fill monitoring
Stock water usage
Leak alerts on long rural pipelines
Water allocation tracking between paddocks or blocks
Irrigation systems
Irrigation systems often need both totals and timing. A grower may want to know how much water each block received, whether a valve opened as expected, and whether pump output changed during a run.
Dragino LoRaWAN nodes can be placed near meters on pump outlets, filter stations, submains, or block feeds. ProSense flow meters provide the pulse data that makes each irrigation event measurable.
Industrial water
Industrial sites use water for cooling, wash-down, batching, rinsing, boiler make-up, and process supply. Many of these points have meters, but the readings stay local unless someone walks the site.
Remote pulse counting helps turn those meters into usable records. Teams can compare shifts, track abnormal use, and feed water data into maintenance or environmental reporting systems.
Remote infrastructure
Councils, utilities, contractors, and asset owners often manage water points far from staffed locations. Examples include remote buildings, depot tanks, pump stations, standpipes, public amenities, and temporary works.
LoRaWAN works well in these settings because one gateway can often serve many low-power devices across a wide area, depending on terrain, antenna height, and local radio conditions.
Practical installation checks before commissioning
Before the system goes live, verify the full chain from pipe to dashboard.
Start with the meter. Confirm the flow direction, installation orientation, straight pipe requirements, pulse output type, and pulse value. Record the starting mechanical meter reading if the meter has a register. That value can be used to align the remote total.
Next, test the pulse input. If possible, run a known volume through the meter and compare the physical register with the Dragino count. Even a small bucket test can expose a wiring or scaling error on small meters. Larger systems may need a controlled run or comparison against the installed meter register.
Then check the LoRaWAN side. Confirm that payloads arrive, the decoder interprets the count correctly, and the application applies the right multiplier. Make sure resets, battery changes, or communication gaps do not create false usage spikes.
A practical commissioning list includes:
Meter pulse value confirmed from documentation or label
Dragino input type matched to the meter output
Cable polarity checked where required
Debounce or input filtering set where needed
Pulse count tested against a known flow event
Litres-per-pulse multiplier entered in the application
Starting total recorded
Reporting interval set for the use case
LoRaWAN signal checked at installation height
Enclosures sealed and cables strain-relieved
Alerts tested for high use, no flow, or unexpected flow
Good commissioning prevents the most common problem in remote metering, which is beautiful data based on the wrong multiplier.
A simple pairing with a lot of value
Pulse-output water meters are proven, simple, and easy to understand. Dragino LoRaWAN hardware gives them a practical path to remote reporting. Together, they help turn scattered meter points into useful water data without trenching cable or relying on local Wi-Fi.
For many sites, the best setup is direct: choose the right ProSense flow meter for the pipe and flow range, connect its pulse output to a suitable Dragino LoRaWAN pulse counter or I/O device, set the litres-per-pulse value correctly, then report totals at an interval that matches the job.
That combination can reveal leaks sooner, reduce manual meter runs, support irrigation records, and give remote infrastructure owners a clearer view of water use. The technology is simple. The value comes from getting the meter, pulse scale, power plan, and reporting interval right from the start.
Comments