Device library
Any meter, one platform.
Divako is vendor-neutral by design. The device library decodes meters, sensors and gateways from more than thirty manufacturers, over wM-Bus, LoRaWAN, NB-IoT, M-Bus and DLMS, and treats every reading the same way once it arrives. This page lists what is in production today, by device type.
One device library, every manufacturer
Every meter and sensor on this page is decoded by the same device library. A telegram arrives from a Lobaro gateway, a LoRaWAN network server, a Kamstrup READy collector or a DLMS reader, the library identifies the manufacturer and model, decrypts with the stored key, decodes the fields and writes a reading in the platform’s own data model. From there on, an Apator water meter, a Kamstrup heat meter and a VEGA level sensor are the same kind of thing: a series of validated values with alarms, exports and a place on the map.
That is what makes the list below possible. Adding a manufacturer means adding a parser, not a new integration, and a customer can change supplier between procurement rounds without moving anything else. The list is grouped by what the device measures, because that is how the platform treats it; the radio it uses is shown on each card.
In production
Manufacturers by device type
Models are examples of what is running on the platform today, not an exhaustive list. A manufacturer that appears under several headings has products in each of them.
Water meters
14 Residential, bulk and industrial water meters, cold and hot.Heat, cooling and energy meters
9 District heating, building heat, cooling and thermal energy.Electricity meters
4 Main and sub-meters over DLMS, M-Bus, Modbus and LoRaWAN.Heat cost allocators
6 Radiator allocators for per-apartment heating cost split.Level and overflow sensors
6 Radar and ultrasonic level for tanks, wells, basins and overflows.Gateways, collectors and bridges
8 What carries the telegrams from the meter to the platform.Indoor climate and environment
8 Temperature, humidity, CO₂ and air quality in buildings.Street lighting
1 Lighting control and energy metering per luminaire or cabinet.Zone metering, leak and network tools
4 District meters, leak noise loggers and coverage testers.Manufacturer and product names belong to their owners and are listed to describe what the device library decodes. Divako is not affiliated with the manufacturers on this page unless a partnership is stated elsewhere on the site.
Your device is not on the list?
The list is what runs in production. Adding a device is routine work, not a project.
- Any wM-Bus meter that follows OMS is decoded on arrival; only the AES key is needed
- LoRaWAN devices with a documented payload get a versioned parser, usually within two weeks
- DLMS/COSEM meters are onboarded with their OBIS map
- Parsers are tested with the Divako Parser tool before the first device is installed
- Pulse, M-Bus and Modbus devices reach the platform through a supported gateway
- Custom parsers are part of the subscription, not a professional-services line
Questions
Frequently asked
Is Divako tied to any meter manufacturer?
No. Divako reads the meter the customer chose, and most customers run several manufacturers side by side. Asker reads more than 20,000 meters from Kamstrup, Axioma and Apator on one account; Oslo reads Sensus, Kamstrup and Apator meters across wM-Bus, NB-IoT and Sensus RF. A manufacturer change in the next procurement round does not change the platform.
What do you need to add a meter that is not listed?
For a wM-Bus meter, the AES key and one telegram; if it follows OMS it usually decodes without any work. For a LoRaWAN device, the payload documentation and a device to test with. For a DLMS meter, the OBIS list. We write and version the parser, test it with the Divako Parser tool and only then register the devices.
Do you sell the meters?
Divako sells the platform. Meters and gateways come from the manufacturer or a distributor of your choice; in Norway many customers buy through Øwre-Johnsen, which stocks Apator, Honeywell/Elster and Engelmann. We help with the specification so the meter, the radio and the key handover are right before the order goes out.
Can one installation mix wM-Bus, LoRaWAN and NB-IoT?
Yes, and most municipal rollouts do. Each meter uses the radio it was bought with, the platform collects over all of them, and the readings land in the same account with the same alarms and the same billing export.
Your meters
Send us your meter list.
A CSV with manufacturer, model and radio is enough. We check every line against the device library and tell you what is decoded today, what needs a key and what we would add.