Water networks
Water level monitoring remotely.
Level sensors on LoRaWAN or NB-IoT report to the same platform as your water meters. Divako turns the readings into calibrated levels, four-tier alarms and overflow events – so the network is watched around the clock without anyone driving out to look.
What is water level monitoring?
Water level monitoring is the continuous, remote measurement of the water level in wells, tanks, reservoirs, pump-station sumps and open channels, with alarms when a level goes outside its normal band. A sensor at the site reports over a low-power radio network; a platform stores the readings, shows the trend and raises the alarm. It replaces the site visit, the float switch nobody trusts and the phone call from a neighbour.
How it works on Divako
- Sensor. A pressure, ultrasonic or radar level sensor is installed in the well or tank. Battery-powered LoRaWAN or NB-IoT sensors run for years; pump-station controllers can also feed levels over Modbus or OPC UA.
- Network. The sensor sends a small message every few minutes. On LoRaWAN it reaches your own gateways; on NB-IoT it rides the mobile operator’s network. Both can run side by side in one Divako account.
- Platform. Divako decodes the payload, applies the per-device calibration (sensor offset, tank geometry) and stores the level. Each device gets four thresholds: HH, H, L and LL.
- Alarms and events. Crossing a threshold raises an alarm to email, webhook, MQTT or your existing incident system. Overflow events are recorded with start, end, duration and peak, so you have a log rather than a memory.
- Integration. Levels are available through the same REST and MQTT interfaces as your meter readings, for SCADA, GIS or reporting.
What to watch out for
- Calibration drifts with the installation, not the sensor. A pressure sensor reads height of water above itself. Move it ten centimetres during maintenance and every level shifts. Divako keeps calibration per device so a correction is one field, not a firmware job.
- Radio range in wells is not radio range on a map. A concrete well with a steel lid is a Faraday cage. Antenna placement decides whether a site works, and LoRaWAN link budget matters more than the sensor’s datasheet range. Plan gateways for the wells, not the town centre.
- Alarm fatigue kills the system. One threshold that flaps at every rain shower trains people to ignore alarms. Use the H tier for information and reserve HH for the level that means action; add hysteresis where the platform supports it.
- Battery life is a function of reporting interval. Five-minute reporting is fine on mains-fed sites and a poor idea on a ten-year battery. Divako lets you set the interval per device and change it remotely when the season changes.
What you get
- Continuous level monitoring with per-device sensor calibration
- Four-tier alarm thresholds (HH / H / L / LL) per device or group
- Overflow event detection: start, end, duration, peak above threshold
- Map view with live status; sparkline trend per device
- Alarm routing to email, webhook, MQTT or your incident system
- Same dashboards, users and API as your consumption metering
- LoRaWAN, NB-IoT and Modbus level sensors on one platform
Questions
Frequently asked
How does remote water level monitoring work?
A pressure, ultrasonic or radar sensor in the well or tank measures the level and sends it over LoRaWAN or NB-IoT every few minutes. Divako receives the message, applies the sensor's calibration, stores the level, and compares it with the HH/H/L/LL thresholds you set. When a threshold is crossed the platform raises an alarm and records an event.
Which sensors and networks are supported?
Any LoRaWAN or NB-IoT level sensor with a documented payload, plus Modbus and OPC UA sources from pump-station controllers. Divako decodes the payload and normalises it, so different sensor brands appear the same way in the dashboard.
What are HH, H, L and LL alarms?
Two high and two low thresholds per device. H and L warn that a level is drifting; HH and LL mean it has reached a critical point – an imminent overflow or a dry well. Each tier can notify different people through different channels.
Can level monitoring run on the same platform as our water meters?
Yes. Level sensors, overflow detection and consumption metering share one Divako account, one map, one user list and one API. Municipalities such as Asker and Oslo run tens of thousands of meters on the same platform.
Your network
Let's look at your wells and tanks.
Tell us how many sites you have and which networks already exist. We'll suggest sensors, connectivity and a rollout order in about 30 minutes.