LoRaWAN sensors for buildings: range, battery life, security and where they fit
Milvian AI teamFacilities and infrastructure intelligence
LoRaWAN sensors for buildings are battery-powered wireless devices that send small readings, such as meter totals, CO2 or temperature, over long distances to a gateway on low power. Aqueduct uses LoRaWAN alongside BACnet, Modbus, MQTT and LTE to connect meters, air quality sensors, leak sensors and relays across a facility without running new cable.
What LoRaWAN is
LoRaWAN is a low-power, wide-area networking protocol maintained by the LoRa Alliance. It runs on the LoRa radio layer, which uses chirp spread spectrum modulation to send small packets over long distances at very low power. The protocol defines how devices join a network, how their messages are secured and how they reach the application that uses the data.
A LoRaWAN network has a simple shape. End devices, such as sensors and meters, send readings by radio. Any gateway in range receives them and forwards them over an IP connection to a network server, which removes duplicates, checks security and passes the data to the application. Devices do not pair with one gateway, so adding a second gateway improves coverage without reconfiguring sensors.
LoRaWAN uses unlicensed sub-gigahertz radio bands, with regional plans such as US915 in the United States, EU868 in Europe and IN865 in India. Sub-gigahertz signals pass through walls, floors and plant rooms better than 2.4 GHz Wi-Fi, which is why LoRaWAN suits buildings full of concrete and steel.
Why LoRaWAN suits facilities
Most facility monitoring does not need much bandwidth. A water meter total, a CO2 reading or a temperature every few minutes is a few bytes. What it needs is coverage in awkward places, such as basements, risers, ceiling voids and rooftops, and devices that run for years without anyone changing a battery. LoRaWAN is designed for exactly that.
Battery-powered LoRaWAN sensors usually send data points at intervals between five and sixty minutes, depending on the device and setting. Because the radio is only on briefly, battery life can stretch to many years. Many devices can also report on events, such as a leak contact sensor sending an alert the moment water bridges its contacts, or an asset tracker reporting when it moves.
The other advantage is installation. LoRaWAN sensors need no data cabling and usually no power, so a meter in a plant room or a sensor in a ceiling can be fitted in minutes. That lowers the cost of covering a building densely enough to make a water balance close or an air quality picture complete.
LoRaWAN compared with other building connectivity
Each option has a place. Most facilities end up using several.
| Connectivity | Best for | Limits |
|---|---|---|
| LoRaWAN | Battery sensors and meters spread across a building or campus | Low bandwidth, not suited to video or fast control loops |
| Wi-Fi | Higher-bandwidth devices where good coverage already exists | Power hungry for batteries, weaker through concrete, tied to the corporate network |
| Ethernet with MQTT | High-bandwidth monitoring and control of equipment | Needs cabling and network ports at each device |
| BACnet and Modbus | BMS controllers, AHUs, RTUs, chillers and power meters | Wired fieldbus or IP networks, often already in place |
| M-Bus | Utility meters, common in water and heat metering | Wired bus, usually bridged to another network |
| LTE cellular | Remote sites and independent backhaul for gateways | Ongoing data plans and higher power use |
What LoRaWAN sensors measure in a building
Nearly every facility capability has a LoRaWAN option. Indoor air quality sensors report temperature, humidity, CO2, VOCs, pressure and particulates, and some add specialized gases or radon. Occupancy sensors use passive infrared. Bathroom monitors combine odor, sound, occupancy and VOCs. Outdoor stations report weather and ambient air quality.
Metering is the other big category. Ultrasonic water meters can send totals directly over LoRaWAN. Existing electricity, gas and water meters with pulse outputs connect through LoRaWAN pulse counters, which send pulse counts that are converted in the cloud to consumption and flow or demand. Modbus and M-Bus meters connect through bridges that convert their data to LoRaWAN messages.
LoRaWAN also carries simple control. Relay switches turn fans, locks and gates on and off, and water valves report open, closed or partially open. Actuators like these usually listen for commands continuously, so many are mains powered. Complex equipment such as AHUs and chillers is better reached over BACnet or Modbus through a field device network controller.
Security on a LoRaWAN network
LoRaWAN security is built into the protocol. Each device has unique keys, and devices joining by over-the-air activation derive fresh session keys when they join. Messages are protected with AES-128 at two layers: a network session key authenticates messages to the network server, and an application session key encrypts the payload so only the application can read it.
Aqueduct adds to that at the gateway and cloud. Its gateways encrypt traffic at the link and network layers and use mutual authentication between communicating endpoints, so data integrity and device identity are protected end to end. Milvian AI holds ISO/IEC 27001 and SOC 2 Type 2.
LoRaWAN also helps with IT concerns in another way. Sensors do not join the corporate network at all. Gateways can backhaul over the building's Ethernet or Wi-Fi, or over an integrated LTE modem that keeps facility data entirely off the customer network, which many IT teams prefer.
Gateways and coverage planning
Coverage depends on the building. Construction materials, floor count, plant rooms and basements all change how far a signal travels, so a gateway that covers one building may need a partner in the next. A wireless survey before installation shows where gateways should go, and Aqueduct's Core includes a wireless survey view for this purpose.
Aqueduct uses two gateway types. A LoRaWAN gateway receives wireless data from LoRaWAN sensors and forwards it to the cloud over Ethernet, Wi-Fi or an integrated LTE modem. An IP gateway receives data from Ethernet and Wi-Fi devices on a local network and forwards it over its own LTE connection. Many sites use both.
Once installed, coverage has to be watched. Aqueduct's device health view reports connection rate and battery voltage for battery devices, or capacitor voltage for wired ones, so the team knows which sensor needs attention before a gap appears in the data. That is what makes readings trustworthy enough to act on.
When LoRaWAN is not the right choice
LoRaWAN is built for small, infrequent messages. It is not the right path for video, for high-frequency power quality data or for control loops that need answers in seconds. Cameras stream over IP, power monitoring at a switchboard often reports over Modbus or MQTT on Ethernet, and AHU and chiller control runs through BACnet or Modbus field devices.
It is also not a reason to replace systems that work. If a BMS already reads a meter, a pulse splitter can share the same pulse output with a LoRaWAN pulse counter, so the existing system keeps its feed and Aqueduct gets the data too. If a building has reliable wired networks to the equipment that matters, use them.
The practical rule is to match the link to the job. LoRaWAN for battery sensors and meters spread across a site, wired protocols for equipment control, IP for high-bandwidth devices, and LTE where a gateway needs its own backhaul. A good facility platform reads all of them into one place.
Where LoRaWAN fits in a facility platform
LoRaWAN is a way to get data, not a platform in itself. Its value depends on what happens next. In Aqueduct, every reading lands in one data layer organized by site, floor, zone and device, alongside BMS points read over BACnet and Modbus and higher-bandwidth devices on MQTT. The digital twins refresh every 60 seconds from that telemetry.
From there, the same flywheel runs as for any other source. Meter readings close the water balance and feed weather-normalized baselines. Air quality readings are overlaid with occupancy. Relays and valves act where control is enabled, with owner approval, and every command is logged. Results are verified at the meter.
Milvian AI is device agnostic and does not sell hardware as its core business. Installation runs through partners, and existing devices connect wherever they emit telemetry. LoRaWAN is often the fastest way to fill the gaps between them.
