Key takeaways
- Connectivity is a power-and-payload trade-off first, a coverage one second.
- LoRaWAN = years on a battery, but you own/share the gateways.
- LTE-M / cellular = reuse carrier coverage, pay per-device airtime.
- Mesh (Wi-SUN/Wirepas/DigiMesh) = best for dense, bounded deployments.
- Plan for a mix, and unify it behind one fleet-management platform.
Start from the physics, not the brochure
The fastest way to a wrong radio is to choose by buzzword. Choose by three questions instead: How big is each message? How often does it send? What is the power budget? A soil-moisture sensor reporting a few bytes every hour and a 1080p camera streaming continuously are not on the same network — and no single radio serves both well.
The decision matrix
| Technology | Best for | Range | Power | Payload | Cost model |
|---|---|---|---|---|---|
| LoRaWAN | Metering, parking, agriculture, environment | Km-scale | Very low (years on battery) | Small | You own/share gateways |
| LTE-M | Mobile or firmware-updatable assets | Carrier | Low–moderate | Moderate | Per-device airtime |
| Cellular (LTE Cat-1/4, 5G) | Gateways, video, high-throughput nodes | Carrier | Higher | Large | Per-device airtime |
| Wi-SUN / Wirepas / DigiMesh | Dense utility, lighting, campus meshes | Mesh-extended | Low–moderate | Small–moderate | You own the mesh |
How to read the matrix
Choose LoRaWAN when…
…your devices are fixed, send small payloads infrequently, and must live for years on a battery. The trade-off is that you provide or share the gateway coverage. It is the workhorse of low-power wide-area sensing.
Choose LTE-M when…
…devices move, need reliable firmware updates, or you don’t want to deploy any gateways. You reuse carrier infrastructure and pay per-device airtime. It sits neatly between LoRaWAN’s frugality and full cellular’s throughput.
Choose full cellular when…
…you have gateways, cameras, or nodes that push real bandwidth. Power and airtime cost go up, but so does capability.
Choose a mesh (Wi-SUN, Wirepas, DigiMesh) when…
…you have many devices in a bounded area — utility metering, street lighting, a large campus — and want resilient, self-healing coverage without per-node carrier cost.
Plan for a mix
Most production deployments are not single-radio. A typical pattern: LoRaWAN sensors feeding a cellular gateway, or a Wi-SUN lighting mesh alongside cellular cameras. The discipline that keeps this manageable is to unify every device behind one platform — one place for identity, updates and audit — so three radios don’t become three operational silos.
Where Fundamentum fits
Whatever radio mix you land on, you still manage one fleet. Fundamentum, our Canadian IoT platform, gives you device identity, governed OTA and an audit trail across cellular, LoRaWAN and mesh devices alike — inside a SOC 2 Type II perimeter — so connectivity choices don’t fragment your operations. See the platform →
Frequently asked questions
Is LoRaWAN better than cellular for battery devices?
For low-data, long-life sensors, usually yes — LoRaWAN can run years on a battery where cellular drains faster. But LoRaWAN needs gateway coverage you provide or share, while cellular reuses carrier infrastructure. The trade is infrastructure-you-own (LoRaWAN) vs per-device airtime (cellular).
When should I choose LTE-M over LoRaWAN?
Choose LTE-M when devices move, need carrier-grade coverage without deploying gateways, send moderate payloads, or must receive firmware updates reliably. LoRaWAN wins on cost-per-node and battery life for fixed, low-data sensing.
What about Wi-SUN, Wirepas or DigiMesh?
These mesh technologies shine in dense deployments — utility metering, street lighting, large campuses — where nodes can relay for each other and extend coverage without per-node carrier cost. Consider them when you have many devices in a bounded area and want resilient, self-healing coverage.
Can I mix several radios in one product line?
Yes, and most real deployments do — for example LoRaWAN sensors feeding a cellular gateway. The key is to unify them behind one platform so you manage a single fleet, not three. That is exactly what a platform layer is for.
Related reading
Talk to an IoT engineer — free
Book a FREE 30-minute consultation with our team. No slides, no obligation — a working session on your connectivity, platform or compliance questions.
