Divako Divako
SolutionsUtilities & municipalities Housing & sub-metering Industry & buildings Streetlights & smart city Water networks & overflow Leak & anomaly detection Cost settlement & billing Billing & ERP exports Resident portal & apps Drive-By collection Topics
PlatformHardware Network Data Analyze Integrations Security & data protection API & docs Platform status
Customers Resources About Log in Book a demo

Technology

NB-IoT platform, no gateways.

NB-IoT puts a SIM in the meter and lets the mobile operator carry the coverage. Nothing to build, excellent reach into basements and pits, and a rollout that can start the day the meters arrive. Divako receives the data and treats it exactly like everything else on the platform.

Book a demo Compare with LoRaWAN

5,000+ water meters on wM-Bus + NB-IoT, Oslo
10+ years vendor-rated battery life, stationary NB-IoT
2 networks side by side – LoRaWAN and NB-IoT

What is NB-IoT?

NB-IoT is a cellular network technology built for exactly one job: stationary, battery-powered devices sending small messages for a decade. It runs on the mobile operator’s licensed spectrum, so every meter carries a SIM or eSIM and there is nothing for you to build. Its deep-indoor propagation is its strongest feature, which matters because that is where metering is hardest – basements, pits and concrete chambers.

What you gain in convenience you give up in control. The radio plan belongs to the operator, so a chamber with no signal is not something you fix with a ladder and an antenna: you route around it, or you wait for a rollout you have no say in. Billing has the same shape – a monthly fee per device that runs for as long as the meter does. Across fifty scattered meters that is the cheapest thing on the table. Across fifty thousand it becomes a permanent line in the operating budget.

How it works on Divako

  1. Device. The meter arrives with a SIM or eSIM and a device profile. Divako holds the profile, the payload parser and the alarm definitions, so a batch imports by IMSI, CSV or API rather than one device at a time.
  2. Network. The device attaches to the operator’s network and sends its reading – over UDP, CoAP or MQTT, and LwM2M where the device speaks it. There is no gateway, no frame counter and no coverage map of your own to maintain.
  3. Platform. The payload is decoded against the profile and normalised into the same measurements as everything else: unit, timestamp, quality and metadata. Last-seen time, signal level and failed sessions are kept per device.
  4. Analysis. Leak, burst, backflow and drift rules run per device type, and alarms route to email, webhook, MQTT or your incident system. An NB-IoT meter and a LoRaWAN meter follow the same rules.
  5. Integration. Readings leave over REST, MQTT, webhooks or SFTP, and through native connectors to billing, SCADA and ERP.

What to watch out for

  • The SIM and the APN are part of the meter. A private APN, a wrong IP allocation or an unactivated SIM looks exactly like a dead meter from the dashboard. Agree the APN, the addressing and who can reactivate a SIM before the first installation day, not after fifty meters are in the ground.
  • Operator coverage is measured, not promised. A coverage map is drawn for phones at street level, not for a meter under a cast-iron lid. Measure signal in the worst chambers on the list before committing the whole fleet, and keep a fallback for the sites that fail.
  • A weak link costs battery, quietly. A device at the edge of coverage retransmits and raises transmit power to get its message through. Ten-year battery figures assume a decent link; watch the devices whose signal has drifted down before you watch the ones that went silent.
  • An operator’s roadmap is part of what you buy. The 2G and 3G sunsets are a reminder that the technology under a fleet of meters is someone else’s decision. Ask about the commitment period, and keep the platform able to carry a second technology.

What you get

  • NB-IoT meters and sensors with no network of your own to build
  • Deep-indoor reach for basements, pits and meter chambers
  • Vendor-neutral device library with versioned payload parsers
  • UDP, CoAP and MQTT ingestion, plus LwM2M where the device speaks it
  • Connectivity health per device – last seen, signal, failed sessions
  • NB-IoT next to LoRaWAN, wM-Bus and drive-by in one account
  • Leak, burst, backflow and drift alarms on the same rules
  • REST, MQTT, webhooks and SFTP exports from one data model

In production

Unibet ArenaTallinn, Estonia
15 min

water + electricity · one in-building wM-Bus network

Estonia's largest arena reads 20+ Apator Ultrimis NEO water meters and OMS electricity meters over a single wM-Bus network, collected by two NB-IoT Lobaro gateways. Potential leaks surfaced within two weeks – and per-event consumption is the goal.

  • wM-Bus
  • OMS
  • NB-IoT
  • Venues

Read the arena story →

Oslo VAVNorway
5,000+

water meters · wM-Bus + NB-IoT + Sensus RF

From manual drive-by collection to continuous remote reading across central Oslo. New Apator Ultrimis and legacy Sensus iPerl meters on one pipeline. The billing team works from daily data, not quarterly spreadsheets.

  • wM-Bus
  • NB-IoT
  • Water

Read the Oslo story →

Questions

Frequently asked

What is NB-IoT?

A mobile-network standard, carried on the operator's licensed frequencies and trimmed down for devices that sit still and say very little. The meter takes a SIM or eSIM and attaches the way a phone would, which is why there is nothing to mount on a mast and no radio survey to commission.

When is NB-IoT the better choice than LoRaWAN?

When the meters are scattered rather than clustered, when a site sits in a basement or pit where propagation is hardest, or when a rollout has to start before any network could be built. Once a district holds enough meters to keep several gateways busy, LoRaWAN usually wins on cost, because the per-SIM fee never stops arriving.

How long do NB-IoT meter batteries last?

Ten years and more for stationary meters reporting on a normal schedule. The figure depends on reporting interval and signal conditions: a device at the edge of coverage spends far more energy getting each message through than one with a clean link.

Can we mix NB-IoT and LoRaWAN in one system?

Yes, and most municipalities do. Oslo VAV runs more than 5,000 water meters across wM-Bus, NB-IoT and Sensus RF in one pipeline. The network is an engineering choice per area; the data model, dashboards and billing export stay the same.

Your rollout

Let's find your NB-IoT meters.

Tell us where your meters scatter and where they cluster. We'll sketch which sites belong on NB-IoT, which on LoRaWAN, and what it costs either way – in about 30 minutes.