LoRaWAN Compatible Smart Water Meters: Technologies, Benefits, and Selection Criteria

LoRaWAN compatible smart water meters combine water measurement with long-range, low-power communication, enabling remote collection of consumption data and meter alerts. For utilities, submetering providers, and property managers, the important question is not only whether a meter supports LoRaWAN. It is how the meter is built, how the network will be deployed, and whether the complete system fits billing, maintenance, and data requirements.

This guide explains the main meter configurations, the specifications worth checking before procurement, and where LoRaWAN is a practical choice compared with cellular alternatives.

Key Takeaways

• LoRaWAN can support private, public, or hybrid smart metering networks, but gateway placement and building conditions directly affect coverage and deployment costs.
• Integrated radio meters reduce the number of separate devices installed at each measurement point, while external modules can be useful when existing meters need to remain in service.
• Meter selection should consider starting flow, battery assumptions, alert functions, installation requirements, legal metrology, gateway needs, and compatibility with the data platform.
• Starting flow and billing accuracy are separate specifications. A meter can register a flow that falls outside its stated accuracy range, so check both figures on the datasheet.
• Decide early whether you will own and operate the LoRaWAN network or buy it as a managed service, because that choice determines gateway responsibility, backhaul and operating costs.
• LoRaWAN is often well suited to concentrated meter populations such as apartment buildings, campuses, manufactured housing communities, and other properties where gateway locations can be planned.
• No communication technology is the best choice for every project. Cellular technologies such as NB IoT may be more practical when endpoints are geographically dispersed or gateway infrastructure cannot be controlled.

LoRaWAN water meters at a glance

Selection area	What to check	Why it matters
Meter architecture	Integrated LoRaWAN radio module	No need for external radio transmitter
Measurement method	Ultrasonic or mechanical	Influences low flow sensitivity, wear, and installation requirements
Starting flow	Lowest flow the meter can register	Helps reveal small continuous consumption that higher thresholds may miss
Battery specification	Expected life and communication assumptions	Reporting frequency and radio settings affect real operating life
Alert functions	Leakage, burst, backflow, empty pipe, temperature, and device alerts	Determines what events can be identified without relying only on manual analysis
Network design	Gateway quantity, location, power, and backhaul	Coverage depends on the property, not meter count alone
Legal metrology	Approvals required for the specific billing jurisdiction	Technical compatibility does not automatically mean a meter can be used for commercial billing
Data platform	Meter, protocol, API, billing, and analytics compatibility	Reduces the risk of creating a closed system that is difficult to expand

What is a LoRaWAN water meter?

A LoRaWAN water meter sends consumption and device information over LoRaWAN, a low power wide area communication technology designed for small data transmissions over long distances. LoRaWAN operates on unlicensed radio frequencies and can be deployed as a private, public, or hybrid network. The specification is maintained by the LoRa Alliance, which also certifies compliant devices.

For smart water metering, a private LoRaWAN network can collect readings from every endpoint without a cellular subscription, although managed LoRaWAN services may still include connectivity charges. We compare LoRaWAN, NB-IoT, LTE-M, and other smart meter communication technologies in greater detail.

Which water meter configurations work with LoRaWAN?

There are two common ways to connect water meters to a LoRaWAN network.

Integrated LoRaWAN meters

The communication radio is built into the meter. This reduces the number of separate components at the measurement point, simplifying installation and maintenance.

Mainlink uses the QALCOSONIC W1 ultrasonic smart water meter for this type of deployment. The United States version supports integrated LoRaWAN communication in the 902 to 928 MHz band, has no moving measuring parts, offers IP68 protection, installs in various positions without straight pipe sections, and has a starting flow rate as low as 0.01 GPM. Battery life is specified at up to 16 years depending on communication settings.

External and retrofit communication modules

A conventional meter can send pulses or other outputs to a separate LoRaWAN communication device, and in some cases, an existing meter can stay in place while a compatible converter adds remote communication. Both approaches serve the same purpose: bringing installed hardware onto the network without replacing it.

This can reduce initial replacement work during a gradual transition from manual reading or AMR to AMI. The tradeoff is additional hardware at each point, with its own installation, battery, and maintenance requirements.

What should you check on a LoRaWAN water meter datasheet?

1. How low is the starting flow?

Starting flow shows the lowest flow at which the meter begins to register consumption. A lower threshold can improve visibility into small, continuous water use that may otherwise be missed.

It should not be confused with leak detection. Identifying a leak also depends on the meter or platform’s alert logic, the flow duration, and the thresholds configured for the project.

2. Battery life and communication settings

Battery claims should always be read together with the communication profile. A specification based on infrequent transmissions is not directly comparable with one based on more frequent reporting.

For the QALCOSONIC W1, Axioma specifies up to 16 years of battery life depending on communication settings. That should be treated as a product specification, not a guaranteed replacement interval for every deployment.

3. Alarm functions

Check which events the meter can identify and which are calculated later by the data platform. Leakage, burst, backflow, low temperature, low battery, and other alerts may be relevant depending on the application.

4. Installation requirements

Meter orientation, available pipe length, environmental protection, accessibility, and pipe size affect installation time and cost.

Ultrasonic meters can be useful in constrained spaces when the selected model supports flexible orientation and does not require straight pipe sections.

5. Legal metrology

A technically suitable LoRaWAN meter is not automatically approved for every billing application. Buyers should confirm the requirements for the specific meter version and installation.

6. Gateway requirements

Ask how many gateways the actual site needs and where they can be installed. Building materials, meter locations, site geometry, interference, power, and backhaul can all affect network design.

A large number of meters does not automatically require a large number of gateways, but one gateway should never be assumed before radio planning or site validation.

7. Data platform compatibility

The meter is only one part of an AMI system. The data platform should be able to collect meter readings, manage devices, process alerts, provide billing data, and integrate with other systems.

Mainlink’s Smart Metering Platform combines meter data management and head end functions and supports multiple meter brands, communication technologies, and device types. This is useful when a portfolio uses LoRaWAN in one property and cellular communication elsewhere. For LoRaWAN specifically, the platform’s network health analysis and data outage detection views matter as much as the consumption dashboards, because they show which devices have stopped reporting before a billing period closes.

How to set up LoRaWAN gateways for the smart metering project?

Setting up LoRaWAN gateways starts before any hardware is installed. Mainlink evaluates each project and conducts a network propagation study based on the site layout, meter locations, building characteristics, and surrounding environment. This helps determine how many gateways are needed and where they should be installed to provide reliable meter communication across the project area.

Once the gateway locations are confirmed, Mainlink preconfigures the gateways and ships them ready for deployment. The client only needs to install each gateway at the specified location and connect it to power. This approach simplifies on-site deployment and reduces the technical work required during installation.

What can a LoRaWAN deployment look like in practice?

A useful example is Mission Terrace in Santa Clara, California, a multifamily property with 202 units where Meternet deployed 404 Axioma ultrasonic meters for hot and cold water.

The project ultrasonic meters with integrated LoRaWAN radio modules and used four indoor Kerlink LoRaWAN gateways. All 404 meters were installed in 30 days, with about 15 minutes required per meter. Six water leaks were detected during the first two months. The case study also reports approximately $8,000 in labor savings and $40,400 in savings from avoiding separate remote meter displays.

These are project specific results, not universal performance expectations. The broader lesson is to evaluate the meter, the network, the gateways, and data access as a single system.

Where does LoRaWAN fit best?

LoRaWAN is often a strong option where many meters are located within a property, campus, neighborhood, or defined service area and the operator can plan gateway coverage.

Typical applications include multifamily properties, manufactured housing communities, RV parks, campuses, submetering portfolios, and dense utility areas. Mainlink’s submetering solutions use LoRaWAN to transmit meter data through gateways to a central platform for monitoring, billing, and alerts, and the same network can carry other building devices, such as leak sensors, when a property wants more than meter readings.

LoRaWAN may be less attractive for very small properties or geographically scattered endpoints where gateway access, power, or backhaul is difficult to secure. In those cases, NB IoT or another cellular option may provide a simpler deployment model.

The choice should consider coverage, infrastructure ownership, battery performance, data requirements, and total lifecycle cost.

Frequently asked questions

Do all smart water meters work with LoRaWAN?

No. Some meters have LoRaWAN communication integrated, while others require an external module. Other smart water meters use NB-IoT, LTE-M, Wireless M-Bus, or other communication technologies.

How many gateways does a LoRaWAN water metering project need?

There is no fixed number based only on meter count. Gateway requirements depend on site size, building materials, meter location, gateway placement, interference, and the required coverage level.

How long do LoRaWAN water meter batteries last?

Battery life depends on the meter, reporting frequency, radio configuration, network conditions, and other operating factors. For example, the QALCOSONIC W1 model is specified for up to 16 years depending on communication settings.

Are LoRaWAN water meters approved for tenant billing in the United States?

LoRaWAN itself does not determine whether a meter is approved for billing. Buyers need to verify the approvals required for the specific meter, application, jurisdiction, and installation.

Choosing the right LoRaWAN water meter

A strong LoRaWAN meter selection starts with more than communication range. Buyers should compare the measurement technology, low flow performance, battery assumptions, alerts, installation conditions, legal metrology, gateway design, network ownership and data platform before committing to hardware.

For concentrated meter populations, LoRaWAN can provide a practical route to automated readings and operational alerts without relying on a cellular subscription for every meter. Where endpoints are dispersed, cellular communication may be the better fit. The right choice is the one that works across the meter, network, platform, and billing environments throughout the deployment’s life.