LoRaWAN®NB-IoT
Integrations

Integrations: compatible water meters and networks

If your meters already transmit, they connect as they are.

Datakubo receives readings from any source that sends them by webhook. Most often that is LoRaWAN and NB-IoT meters, through your network server (TTN, ChirpStack or an all-in-one gateway) or straight over HTTP. Because it does not talk to the meter directly, the meter brand does not matter.

Documented integrations, on LoRaWAN: B Meters Hydrodigit-S1 and the Axioma Qalcosonic W1 range. Any other meter that arrives by webhook works too, and if it needs a decoder we write it for free within 24 hours.

Last updated:

Compatible meters

Three levels: models with a documented integration, models that work through the standard path with no specific work, and models not supported yet, for which we write the decoder.

Documented integration
Own page, decoder, the manufacturer’s alarms turned into alerts, and a setup guide.
Compatible
Works through the standard path — ChirpStack or TTN JSON — with no model-specific work.
Custom
Not supported yet: we write the decoder for free within 24 hours.
Protocol
Level

6 results

  • B Meters Hydrodigit-S1 water meter with digital display

    B Meters Hydrodigit-S1

    Documented integrationLoRaWANNB-IoT · Custom

    Apartment meter, cold and hot water

    LoRaWAN: TTN, ChirpStack or an all-in-one gateway. NB-IoT: built to order, custom connection.

    LoRaWAN with Datakubo’s own decoder: it is the meter in the AquaLinks case study (66 meters in one community). B Meters builds the NB-IoT version to order and it is not connected yet; we write its decoder for free within 24 hours. The Wireless M-Bus version is not read directly.

    See integration →
  • Axioma Qalcosonic W1 ultrasonic water meter with digital display

    Axioma Qalcosonic W1

    Documented integrationLoRaWANNB-IoT · Custom

    Ultrasonic meter for apartments and bulk lines (risers, irrigation)

    LoRaWAN: TTN, ChirpStack or an all-in-one gateway, with the manufacturer’s decoder. NB-IoT: custom connection.

    The LoRaWAN version also carries Wireless M-Bus and both radios run at the same time; Datakubo reads the LoRaWAN one, with a step-by-step setup guide. The NB-IoT version does not send ChirpStack or TTN JSON: we build its connection for free within 24 hours. As the bulk meter of a zone, it is compared with the sum of the apartments to catch losses.

    See integration →
  • Other LoRaWAN meters

    CompatibleLoRaWAN

    Mixed and other-brand fleets

    Any network server that delivers the decoded uplink

  • Other NB-IoT meters

    CompatibleNB-IoT

    SIM-based meters

    HTTP POST to the ingest endpoint, as ChirpStack or TTN JSON

  • Wired M-Bus meters

    CompatibleM-Bus

    Meter rooms wired for M-Bus

    Through a concentrator that posts the readings over HTTP (ChirpStack or TTN format)

  • Your model, if it is not listed

    CustomLoRaWAN / NB-IoT

    Any meter that already transmits

    Send us the model and a sample uplink; we write the decoder for free within 24 hours

Can’t find your meter? Send us its datasheet and payload decoder, and we’ll add it.

Send the datasheet

By protocol

By manufacturer

  • B Meters: the LoRaWAN meters in the AquaLinks deployment, with the hardware alarms the meter itself reports.
  • Axioma Metering: the Qalcosonic W1 ultrasonic range on LoRaWAN, with a step-by-step setup guide; the NB-IoT version, to order.

Network servers and gateways

On LoRaWAN, the meter talks to a gateway and the gateway to a network server (LNS). Datakubo does not replace your LNS: it receives the already-decoded uplink from any of these.

SourceHow it connects
The Things Network (TTN)Public network server (with a free plan), via custom webhook
ChirpStackYour own network server, via HTTP integration
Dragino LPS8N · Milesight UG65/UG67 · Kerlink Wanesy Edge · RAK7268/7240All-in-one gateways with an embedded network server, via their webhook (ChirpStack v4 or TTN v3 format)
    1. MeterThe one you already fitted
    2. LoRaWAN / NB-IoTYour radio or your SIM
    3. TTN / ChirpStack / APIYour network server
    1. DatakuboInbound webhook
    2. Your brandYour logo, your subdomain
    3. Your customerTheir own login

The integration is always the same: a POST with the decoded payload to the ingest endpoint, in ChirpStack or TTN format. With TTN it is a custom webhook; a private gateway with TTN as backup is common, as AquaLinks does. Details in the The Things Network guide and the webhook format.

Datakubo LNS (coming soon): you will be able to point the gateway straight at Datakubo, with no TTN or ChirpStack. Until then, any of the routes above.

How to connect your meters to Datakubo

Six steps, the same ones you will see in the dashboard.

  1. Create your account

    At app.datakubo.com/signup, with a 30-day trial and no card. The setup wizard walks you through the next steps.

  2. Copy your API key

    In the dashboard, Settings → API Key. It is the X-API-Key header that identifies your organisation. It is shown once: keep it safe.

  3. Register the meters on their network

    LoRaWAN: each meter with its DevEUI, AppKey and decoder on TTN, ChirpStack or an all-in-one gateway. NB-IoT: the meter or its platform sends JSON shaped like ChirpStack or TTN.

  4. Point the webhook at Datakubo

    URL https://api.datakubo.com/api/v1/ingest/water-consumption, method POST and the X-API-Key header. On TTN it is a custom webhook; on ChirpStack, an HTTP integration; on an all-in-one gateway, its HTTP forwarding. Fields and examples in the webhook format.

  5. Check the meters in Devices

    Each meter appears on its own with its first uplink, with no registration form. Compare the reading with the meter’s display and give it a name people recognise (flat 3B, riser C).

  6. Assign and invite

    Create the community in Customers, assign each meter to its home in Devices, add your logo and colours in Settings and invite the management and every resident.

Before you connect: check your webhook

If a meter shows up with no readings, it is almost always a decoder field name. Paste a sample webhook into the payload checker and it tells you which field is missing and what it should be called.

Rather do it together? Book 30 minutes and we connect your first installation with you.Full guide

What we do not read: Wireless M-Bus

Datakubo does not read Wireless M-Bus (walk-by or drive-by reading). If your meters carry both radios — like the Axioma Qalcosonic W1 — Datakubo uses the LoRaWAN one and your wM-Bus route can keep running.

Wired M-Bus does work, through a concentrator that posts the readings over HTTP. Mechanical meters with no transmitter do not fit directly: write to us and we look at it case by case.

Integrations and compatibility FAQ

Which water meters work with Datakubo?

Any meter whose readings reach Datakubo by webhook, as ChirpStack or TTN JSON. Most often that is LoRaWAN and NB-IoT meters such as the B Meters Hydrodigit-S1 and the Axioma Qalcosonic W1 range. Wired M-Bus works through a concentrator.

Can I mix brands in the same installation?

Yes. Payloads are normalised on arrival, so meters from different manufacturers show up in one view with the same charts and alert rules.

Which LoRaWAN network server do I need?

None in particular: The Things Network, ChirpStack or an all-in-one gateway with an embedded network server. Datakubo receives the decoded uplink by webhook. Datakubo’s own LNS is coming soon.

What if my meters are NB-IoT?

No gateway or network server is needed: the meter posts over the cellular network to the Datakubo HTTP endpoint, as ChirpStack or TTN JSON.

Does Datakubo read Wireless M-Bus?

No. Datakubo reads LoRaWAN and NB-IoT. If a meter also carries Wireless M-Bus, Datakubo uses its LoRaWAN radio.

What if my model is not supported?

We write the decoder for free within 24 hours. Send us the model and a sample uplink.

Try it with your meters

Open the demo with no signup, or activate your first customer from €49/mo with 20 meters included.