LoRaWAN Sub-Metering in UAE Buildings: When Wireless Beats Wired Modbus
Sub-metering a building means putting a meter on every tenant, unit or plant item and getting its readings somewhere useful. The meters are the easy part. The cost and the disruption sit in the cabling between them, and that is the problem LoRaWAN removes. It also brings limits of its own, and a specification that ignores them produces a system that reads well on paper and drops readings in the basement.
The Short Answer
- LoRaWAN wins on retrofit in occupied buildings, where running a data cable to every meter is the expensive, disruptive part.
- Wired Modbus or M-Bus wins where cabling is going in anyway (new build), where readings are needed every few seconds, or where the same network must also control equipment.
- In the UAE, specify EU868 devices and gateways and ask for TDRA type approval of the radio equipment.
- The radio does not make a reading billing-grade. The meter's accuracy class and approval do.
- Do a radio survey of meter rooms and basements before fixing the gateway count.
How a LoRaWAN Metering System Fits Together
There are four layers. Meters (electricity kWh, water m³, or BTU/thermal energy meters on chilled water) either have a LoRaWAN radio built in, or have a pulse or RS-485 output connected to a small LoRaWAN transmitter. Gateways on site receive every device in range and forward the messages over Ethernet or cellular. A network server checks, de-duplicates and decrypts them. An application layer (a metering platform, the BMS via a BACnet/IP or API integration, or a billing system) turns the readings into consumption per tenant, alarms and reports.
Each layer is a separate choice, and the integration between the network server and the application is where most projects spend their commissioning time. Our LoRaWAN sub-metering solution covers all four.
Wired Modbus or M-Bus vs LoRaWAN
| Factor | Wired (Modbus RTU / M-Bus) | LoRaWAN |
|---|---|---|
| Cabling | A bus cable to every meter, plus containment and riser penetrations. | No data cable to the meter. Gateways need power and a network connection. |
| Retrofit in an occupied building | Disruptive: ceilings, risers and tenant areas opened for cabling. | Usually far less disruptive, because only gateways are cabled. |
| Reading interval | Can poll every few seconds. | Typically minutes, limited by airtime rules and battery life. |
| Control | Yes, real-time read and write. | Monitoring only for battery (Class A) devices. |
| Coverage risk | None once installed. | Basements, meter rooms and concrete cores need a radio survey and sometimes extra gateways. |
| Power at the meter | Usually powered or bus-powered. | Usually battery, so maintenance is battery replacement on a known cycle. |
The two are not exclusive. A common pattern is wired Modbus in the main plant room, where the BMS already has cabling and needs fast data, and LoRaWAN for the hundreds of apartment or shop meters spread across floors.
The Limits Worth Knowing Before You Specify
Frequency plan. The Things Network's country table lists EU863-870 for the UAE, with EN 302 208 and the national regulator's rules as references. Devices built for another region's plan, such as US915 or AS923, are the wrong product, however cheap.
Airtime. Licence-free bands limit how much each device may transmit; a 1% duty cycle is common in the European plan. Combined with battery life, that is why LoRaWAN meters report every few minutes rather than every few seconds. For consumption and billing that is plenty. For fast plant control it is not.
Downlinks. Battery meters are normally Class A: after each uplink they open two short receive windows, and that is the only time the network can reach them. A command can therefore wait until the meter next reports.
Coverage in concrete. Meter rooms, basements, car parks and service cores are exactly where meters live and where radio struggles. A device far from a gateway falls back to a slower data rate, which uses more airtime per message and more battery. A survey with a test device in the worst rooms, before the gateway count is fixed, avoids discovering this at handover.
Battery claims. A multi-year battery figure is only meaningful with its assumptions: reporting interval, data rate and temperature. Ask for them, and compare products on the same basis.
Billing-Grade Is About the Meter, Not the Radio
LoRaWAN carries a reading; it does not improve or certify it. If the data will be used to bill tenants, the questions are about the meter: its accuracy class, the standard it is approved to (for example OIML R 49 for water meters or EN 1434 for thermal energy meters), how it was installed, and how the platform handles a missing reading.
Billing rules also come from outside the building. In Dubai, district cooling services are regulated under Executive Council Resolution No. (6) of 2021, whose Article 11 sets out that bills show items such as the volume of consumption and the consumption unit rate. Who may bill whom, and on what basis, is a question for the billing provider and the regulator, not for the radio network. Intellicon supplies and integrates the metering network; we do not provide billing software or metrological certification.
Getting the Data Into the BMS
Meter data is most useful next to the plant data it explains: chilled-water energy per tenant beside chiller and pump status, or water use beside leak alarms. The usual route is from the network server to the BMS as BACnet/IP objects, or through an API or MQTT integration into the BMS or an analytics platform. Decide early which system is the master record of consumption, so that the dashboard and the bill never show two different numbers.
Overnight flow on a water meter is one of the cheapest leak alarms a building can have, and it comes free once the meters report. Pair it with point leak detection in plant rooms for the places where minutes matter.
What to Put in the Specification
- Meter schedule: type, size, location and purpose (billing or monitoring) for every meter.
- Accuracy and approval for any meter whose data will be billed.
- Region and approval: EU868 devices and gateways, with UAE (TDRA) type approval documents.
- Reporting interval and the battery-life assumption behind it.
- Radio survey of meter rooms, basements and risers, with the gateway count and locations it supports.
- Network server: who operates it, where it is hosted, and who holds the device keys at handover.
- Integration: BACnet/IP points, API or MQTT, and which system is the master record.
- Data handling: how gaps are flagged, and whether any reading is ever estimated.
Frequently Asked Questions
What is LoRaWAN sub-metering?
It is measuring the electricity, water or chilled-water energy used by individual tenants, units or areas with meters that send their readings over LoRaWAN radio instead of over RS-485 cabling. On-site gateways receive the readings and pass them to a network server, which feeds a dashboard, the BMS or a billing platform.
Which LoRaWAN frequency plan applies in the UAE?
The Things Network’s frequency-plans-by-country table lists EU863-870 (and EU433) for the United Arab Emirates, with EN 302 208 and the national regulator’s rules as the references. In practice that means specifying EU868 devices and gateways, and asking the supplier for UAE (TDRA) type approval for the radio equipment.
Is LoRaWAN accurate enough for tenant billing?
The radio does not decide accuracy; the meter does. LoRaWAN carries whatever reading the meter produces. Whether the data can be used for a bill depends on the meter’s accuracy class and approval, how it is installed, how missing readings are handled, and the rules of the billing provider and regulator. The radio link has to be reliable enough that readings arrive, and the platform has to show which readings are measured and which are estimated.
How long do LoRaWAN meter batteries last?
It depends on how often the device transmits, how far it is from a gateway (which sets the data rate and therefore the airtime per message), and the meter electronics themselves. Multi-year battery figures are quoted at a stated reporting interval and signal condition, so ask for that assumption in writing before comparing products.
Can LoRaWAN be used to control equipment?
Not well. Most battery meters are Class A devices: they can only receive a command in two short windows straight after they send an uplink. That suits reporting a reading every few minutes, not switching a valve on demand. Control belongs on the wired BMS; LoRaWAN is for monitoring.
Is LoRaWAN data secure?
LoRaWAN 1.0 uses 128-bit AES keys: a network session key checks that each message has not been altered, and a separate application session key encrypts the payload. Security in practice also depends on how keys are generated, stored and handed over, and on who operates the network server.
Sources
- The Things Network, Frequency plans by country (UAE: EU863-870, EN 302 208, TRA regulations)
- The Things Network, Duty cycle
- The Things Network, Device classes (Class A receive windows)
- The Things Network, Security (NwkSKey, AppSKey, AES-128)
- Dubai Executive Council Resolution No. (6) of 2021 Regulating the Provision of District Cooling Services (Article 11, metering and billing)
- OIML R 49 (water meters) and EN 1434 (thermal energy meters): the standards to ask a meter supplier about
Checked 2 October 2026. Frequency-plan information is as listed by The Things Network, not read from TDRA documents directly.
Planning Sub-Metering for a Building?
Send us the meter schedule or just the number of units and where the meter rooms are. We will tell you whether LoRaWAN, wired or a mix fits, and what the radio survey needs to cover.
Request a Metering Assessment