The Mistake: Beginners often select LoRaWAN over NB-IoT because “LoRaWAN claims 15 km range vs NB-IoT’s 10 km,” assuming longer range always wins.
Why It’s Wrong: Range specifications are maximum theoretical values under ideal conditions (line-of-sight, rural, no interference). Real-world performance depends on: - Urban vs rural: LoRaWAN’s 15 km becomes 2-5 km in cities; NB-IoT’s 10 km also drops to 3-7 km - Indoor penetration: NB-IoT’s licensed-band link budget tolerates up to 20 dB more coupling loss than LoRaWAN’s unlicensed-band operation — giving NB-IoT superior building and underground penetration in practice - Interference: LoRaWAN in unlicensed ISM bands competes with Wi-Fi, industrial equipment, and other unlicensed users; NB-IoT in licensed LTE bands has carrier-guaranteed quality of service - Link budget: Both technologies degrade range when using higher data rates; LoRaWAN range also decreases at lower spreading factors (SF7 vs SF12)
The Right Approach: Select based on deployment requirements, not maximum range:
| Indoor smart meters |
NB-IoT |
Better building penetration, leverages existing cellular infrastructure |
| Rural farm sensors |
LoRaWAN |
Open terrain favors long range, private gateway gives full network control |
| City parking sensors |
NB-IoT or LoRaWAN |
Both work; decide based on TCO (LoRaWAN) vs carrier SLA (NB-IoT) |
Example: Barcelona smart parking deployment uses NB-IoT despite LoRaWAN having “longer range” because: - Sensors are underground (need NB-IoT’s superior penetration margin) - City wants carrier SLA reliability for payment-integrated system - No gateway deployment needed (leverages existing cell tower infrastructure)
Bottom line: Evaluate technologies on fitness for purpose, not headline specifications. A technology with “worse” range that meets your deployment needs is always preferable to one with “better” range that fails in your environment.