Skip to content
RenoktaRenokta

Water consumption monitoring

Monitors water use remotely over LoRaWAN sensors and reports leaks and unusual increases.

Request a demo
Pipes, valves and pressure gauges in a drinking water treatment plant.

Measured point

Main line flow

Renokta IoT Platform · Water monitoring

Live · --:--:--

Sample site › Main line and meters

  • Current flow

    11.9m³/sa

  • Usage today

    228.5m³

  • Night minimum flow

    19L/dk

  • Supply pressure

    3.5bar

Main line flow

TodayYesterday11.9 m³/sa

Flow limit 21

Meter and line status

  • Main meterBuilding inlet · flow meter11.9 m³/sa
  • Supply pressureBoiler room3.5 bar
  • Irrigation lineGarden · flow meter2.4 m³/sa
  • Water tankRoof · level sensor63 %

Event feed

  • 0Critical
  • 1Major
  • 1Minor
  • 2Warning
  • Night minimum flow is nearing the limitOpen
  • Basement leak sensor detected moistureOpen
  • Irrigation meter battery is lowOpen

Sample screen. Values are simulated.

What is water consumption monitoring?

Water consumption monitoring collects data from meters and pressure points wirelessly and shows it in a single view. Meters are read remotely instead of on site, and leaks, night-time flow and unusual increases are detected against thresholds and reported to the right people. It covers most remote water meter reading needs.

How does it work?

A LoRaWAN sensor is connected to the pulse or digital output of your existing meter. The sensor sends data to a gateway, and the gateway forwards it to the platform, which stores the values, draws charts and runs the rules.

  • Sensor: counts meter pulses or reads the meter value.
  • Gateway: carries the LoRaWAN radio signal onto the network.
  • Platform: records consumption, watches thresholds, produces reports and alarms.
  • User: is informed through the dashboard, e-mail or messages.

Which quantities are measured?

  • Total and periodic consumption: for comparison before billing and for zone-level distribution.
  • Instantaneous flow: to see sudden rises and continuous flow.
  • Night-time consumption: flow during hours when nobody uses water is the clearest sign of a leak.
  • Line pressure: to spot pipe and valve problems early.
  • Tank or well level: to watch reserve capacity.

Which meter output or method should you choose?

  • Pulse output: found on most mechanical and ultrasonic meters and simple to install, but the pulse count is held in the sensor and must be kept in step with the meter.
  • M-Bus or a similar digital output: reads the meter value directly and can carry extra data, but interface and model compatibility must be checked first.
  • Meter replacement: a new meter ready for remote reading; it may make sense for old meters but raises cost.
  • Added pressure or level sensor: complements meter data but does not give consumption on its own.

Who is it for?

  • Housing complexes and building management: consumption by flat or block.
  • Factories: separate monitoring of process and facility water.
  • Municipalities and water utilities: district meters and line monitoring.
  • Hotels, hospitals and schools with several buildings.
  • Agricultural irrigation operations: wells and lines.

How do alarms and notifications work?

Thresholds are set on the platform for conditions such as night-time consumption, continuous flow or a sudden increase. When a threshold is crossed, the rule fires and a notification goes to the chosen channels (e-mail, message, dashboard). Acknowledged alarms are logged, and reminders can repeat until the alarm is closed.

If a sensor stops reporting, the platform tracks its last uplink and can flag the device as not responding. Missing data is filled in afterwards as far as the sensor can buffer it, which depends on the device.

Integration with existing systems

Data can be passed through MQTT or an API to building automation, billing software or corporate reporting. Connections to field protocols such as Modbus are adapted to the need. The scope is set during the site survey, based on the software you already use.

Data privacy and security

This solution collects consumption data, not personal data. Flat-level consumption can still reveal usage habits, so who sees what is limited through role-based access. The radio link between sensor and gateway and access to the platform are set up with encryption and authentication. A GDPR or KVKK assessment is done with your own privacy notice and legal adviser.

Installation process and what a quote needs

The process starts with a survey: meter types, outputs and radio coverage are checked on site. A pilot on a few points follows, and once data arrives correctly the rest of the points are rolled out.

For a quote, the following is enough: number of meters, their brands and models or photos, approximate size of the site and the software you use. Send us this information and we will contact you to plan the survey.

Highlights

  • Remote water meter reading

    A sensor on the existing meter output sends consumption to the platform without visiting the meter.

  • Night-time flow and leak alerts

    Continuous flow during idle hours is caught by a threshold and reported to the right person.

  • Zone and flat-level distribution

    Consumption is compared by block, zone and meter, so deviations are visible at a glance.

  • Pressure and level monitoring

    Line pressure and tank or well level are tracked on one dashboard next to consumption.

  • Reports and data export

    Periodic consumption reports are available, and data can pass to other software through an API or MQTT.

From the meter to the alert: water use

Flow meters and sensors send flow, pressure and moisture data. The platform watches night flow, warns when a leak is suspected and prepares the usage report.

Flow meterPressuresensorLeak sensorTank levelsensorLoRaWANgatewayRenokta IoTplatformLeak alertUsagereportMaintenancenotice

Suspected leak in night flow

  1. The flow meter and pressure sensor send readings to the gateway at regular intervals.
  2. When no use is expected at night, the platform sees that flow does not drop to zero and compares the night minimum with its limit.
  3. When flow stays above the limit, the facility manager gets a suspected-leak notification.
  4. The team checks the lines; the event is logged with the flow chart and appears in the report.

The diagram shows the logic; names are examples.

Frequently asked questions

How does remote water meter reading work?
A LoRaWAN sensor connects to the pulse or digital output of the meter and sends the value through a gateway to the platform, where consumption, charts and reports appear.
Which meters and sensors does it work with?
Meters with a pulse output or a digital output such as M-Bus are suitable. The meter model is checked during the survey, and pressure or level sensors are added if needed.
How is a leak detected?
Thresholds are set for flow that continues when nobody uses water, or for a sudden rise in consumption. When one is crossed, a notification is sent and the event is logged.
What determines the cost?
The number of meters and measuring points, sensor type, the gateways needed for radio coverage and the scope of integration determine the cost. Exact details follow the survey.
Do I need to replace my current meters?
In most cases no; a sensor is added to a meter with a pulse or digital output. Old meters without an output are assessed during the survey for replacement or another option.
Who owns the data and who can see it?
Consumption data belongs to the organisation, and access is limited by user roles. A GDPR or KVKK assessment should be made with your own privacy notice and legal adviser.
How long does installation take?
It varies with the number of points and coverage, and becomes clear during the survey. Usually a pilot on a few points comes first, then the remaining points follow.
Can it connect to other software?
Yes; data can go to building automation, billing or reporting software through MQTT or an API. The scope is adapted to your needs.

Our solutions

Let's plan the right solution for you, together.

Request a demo