Catch water leaks in hours, not weeks
A leak on a shared well or in an apartment block can run for weeks before anyone notices — and the first sign is usually an unexpectedly high bill. As the installer, you are the one who gets the call. Datakubo lets you catch those leaks early by surfacing the alarms your LoRaWAN water meters already generate on their own — nothing to configure.
Leak detection here is not a separate product — it is an alarm the meter hardware ships with, pre-armed from the factory. The platform watches every uplink and surfaces the alarm in a portal under your brand the moment the meter reports it. There are no rules to define and no thresholds to tune; the meter already knows when to raise the alarm.
Alarms the meter already raises — nothing to configure
Leak / continuous flow
The moment the meter senses water flowing without stopping — the classic signature of a burst pipe or a running cistern — it raises its own leak alarm. There is no threshold to set: the alarm arrives pre-triggered straight from the device firmware.
Burst
Compatible meters detect an internal flow spike consistent with a burst pipe and report a burst alarm on the same uplink. Datakubo just surfaces it in the portal — the detection itself already happens in hardware.
Reverse flow
If water starts flowing backwards — a common sign of a bad repair or a misinstalled valve — the meter flags a reverse-flow alarm automatically, with no setup on your side.
Overflow
When flow exceeds the range the meter can measure accurately, the device raises an overflow alarm on its own. It is a factory-set signal, not a rule you need to tune.
Wrong installation
The meter checks its own orientation and installation and flags it when something is mounted incorrectly — useful for catching installation mistakes before they turn into a support call.
Low battery
The meter reports its own battery state on every reading. Once it drops below a safe level, the low-battery alarm fires on its own — no threshold for you to define.
Offline / no data
Datakubo also watches for meters that stop reporting altogether — flat battery, network gap, or tampering — and flags them automatically. Nothing to configure here either.
What your client actually sees
Alerts are written for the person reading them, not for an engineer. A community manager sees something like: "Meter 14 (Building B) has reported a leak alarm. This often means a burst pipe or a fixture that will not stop running. We recommend checking the property." No raw payloads, no thresholds, no jargon — just a plain-language heads-up under your brand, with the meter, the location and a suggested next step.
How AquaLinks uses leak alerts
AquaLinks, an independent LoRaWAN installer in Spain, runs Datakubo across private shared-well communities. Their B Meters devices raised a leak alarm on their own for a meter that had been quietly driving consumption up, and Datakubo surfaced it in the portal the moment it arrived — cutting water waste by 75% in the first year. Leaks that once ran for weeks are now caught within hours.
How to set it up
Connect your meters
Point a TTN or ChirpStack webhook at Datakubo. Each LoRaWAN meter auto-registers on its first uplink — no manual entry per device.
That is it — alarms surface automatically
There are no thresholds to set. The meter firmware already knows when to raise a leak, burst, reverse-flow, overflow, wrong-installation or low-battery alarm, and Datakubo picks it up the moment it arrives on the next uplink.
Let your clients see the alerts
Invite the community manager and residents to your branded portal. From then on, alerts surface automatically — and each resident sees only their own meter.
Works with the meters you already install
- B Meters (GSD8-RFM, GMDX-RFM, and other LoRaWAN models)
- Milesight water meters
- Dragino LoRaWAN water sensors
- Any pulse-counter LoRaWAN meter (generic payload support)