How to Choose the Right IoT Connectivity: LoRa vs NB-IoT vs WiFi vs Cellular

Why This Decision Can Make or Break Your IoT Project

If you are planning an IoT deployment anywhere in India, whether it is a smart city initiative in Pune, a precision agriculture rollout across farms in Telangana, or a smart building retrofit in a Gurugram IT park, the single most important technical decision you will make is choosing the right wireless connectivity technology. Get it right, and your project scales smoothly from pilot to production. Get it wrong, and you will face premature battery failures, spiralling SIM card bills, embarrassing coverage gaps, or worse, a complete re-architecture six months after launch.

At IoTMATE, we have deployed thousands of IoT nodes across India, from humid coastal warehouses in Kochi to dusty industrial zones in Jamshedpur. We have seen every mistake in the book, and we have learned what works. This guide distils that experience into a practical, India-specific framework for choosing between LoRa/LoRaWAN, NB-IoT, WiFi, and 4G/5G cellular connectivity.

By the end of this article, you will know exactly which technology fits your use case, what it will cost over five years in INR, and how to avoid the most common pitfalls that derail Indian IoT projects.

The Four Main Contenders: A Quick Overview

Before diving into the details, let us set the stage. There are four primary wireless technologies used in IoT deployments across India today:

LoRa/LoRaWAN is a Low Power Wide Area Network (LPWAN) technology that operates in the unlicensed ISM band (865-867 MHz in India, as per WPC regulations). You deploy your own gateways, own your network, and pay zero recurring connectivity fees. It excels at sending small data packets over long distances with exceptional battery life.

NB-IoT (Narrowband IoT) rides on existing cellular infrastructure from operators like Jio, Airtel, and Vi. You get nationwide coverage without deploying any infrastructure yourself, but you pay a monthly SIM fee for every device.

WiFi is the familiar technology you use every day. It offers high bandwidth and leverages existing access points in offices, factories, and homes. However, it is power-hungry and range-limited.

4G/5G Cellular provides the highest bandwidth and mobility support. It is ideal for applications like fleet tracking and video surveillance, but the combination of high power consumption and recurring data costs makes it impractical for large-scale sensor deployments.

Detailed Technology Deep Dive

LoRa/LoRaWAN: The Workhorse for Indian IoT

LoRaWAN has emerged as the dominant LPWAN technology for IoT in India, and for good reason. India's diverse geography, from dense urban centres to vast rural landscapes, plays directly to LoRa's strengths.

How It Works in the Indian Context

In India, LoRa operates on the 865-867 MHz ISM band, which is license-free under the Wireless Planning and Coordination (WPC) Wing regulations. The maximum allowed transmit power is 1 Watt (30 dBm) EIRP, which is generous compared to Europe's 25 mW limitation. This means LoRa deployments in India can achieve significantly better range than their European counterparts.

A typical deployment involves placing LoRa gateways at elevated positions (rooftops, telecom towers, water tanks) and distributing battery-powered sensor nodes across the coverage area. Each gateway can handle 1,000 to 10,000 devices depending on the data transmission frequency.

Range Performance Across Indian Terrains

Cost Breakdown (INR)

When to Choose LoRa

Choose LoRa when you need to deploy hundreds or thousands of sensors, battery life of 5-10+ years matters, and you want to avoid the death-by-a-thousand-SIMs problem. It is ideal for smart agriculture, campus-wide monitoring, industrial estates, smart city sensor networks, and any scenario where you control the deployment area.

When to Avoid LoRa

Avoid LoRa for real-time video or audio (the bandwidth is simply insufficient at 0.3-50 kbps), mobile assets that roam across cities (no seamless handoff between gateways), and indoor-only deployments in buildings with heavy reinforced concrete where a single gateway cannot penetrate multiple floors.

NB-IoT: Leveraging India's Cellular Giants

NB-IoT is the telecom industry's answer to LPWAN. In India, Reliance Jio launched NB-IoT services in 2019, followed by Airtel and Vi in select circles. The technology piggybacks on existing 4G LTE infrastructure, which means you get coverage wherever there is a cell tower.

Coverage Reality in India (2026)

As of early 2026, NB-IoT coverage in India is largely concentrated in urban and semi-urban areas. Jio offers the widest NB-IoT footprint covering approximately 85% of India's population, though geographic coverage (by area) is significantly lower due to sparse rural tower density.

Key Advantages in India

The biggest advantage of NB-IoT is zero infrastructure deployment. You do not need to install gateways, manage backhaul, or worry about tower siting permissions. This is particularly valuable for deployments spread across an entire city or state where installing LoRa gateways at every location would be impractical.

NB-IoT also offers exceptional indoor penetration, around 20 dB better than standard LTE. This makes it excellent for smart meters installed in basements, underground car parks, or inside metal enclosures.

The Hidden Cost Problem

Here is where many Indian IoT projects get burned. The per-SIM cost looks small (Rs 50-200 per month), but it compounds viciously at scale:

At 500+ devices, NB-IoT's recurring costs typically exceed the total cost of deploying and maintaining a private LoRa network. This is the crossover point where most Indian projects should seriously consider LoRa instead.

When to Choose NB-IoT

Choose NB-IoT for geographically distributed deployments (smart meters across a city), mobile assets with SIM-based authentication requirements, deep indoor applications (basement parking sensors, underground utility meters), and rapid pilots where you need to go live in weeks rather than months.

When to Avoid NB-IoT

Avoid NB-IoT for large-scale sensor deployments (500+ devices), rural areas without cellular coverage (tribal belts, remote forests, hill stations), and projects requiring 10+ year battery life (NB-IoT's power consumption is 10-20x higher than LoRa per transmission).

WiFi: The Familiar but Misunderstood Option

WiFi is everywhere in India. Every office, mall, and increasingly every factory floor has WiFi coverage. So the temptation to "just use WiFi" for IoT is strong. Sometimes that temptation is justified; often it is not.

Where WiFi Shines in Indian IoT

WiFi is the right choice for powered indoor devices that need high bandwidth or low latency. Think occupancy sensors in a smart building in BKC Mumbai, environmental monitoring in a Hyderabad data centre, or digital signage in a Chennai shopping mall.

Modern WiFi 6 (802.11ax) with Target Wake Time (TWT) has significantly improved power efficiency, making WiFi viable for some battery-powered applications, though it still cannot compete with LoRa's multi-year battery life.

Cost Structure

The Power Problem

WiFi's Achilles heel for IoT is power consumption. A WiFi radio draws 120-300 mA during active transmission and 10-15 mA even in idle mode. Compare this to LoRa's 14 mA transmit current and 1.5 microamp sleep current. For a battery-powered device transmitting every 15 minutes:

• LoRa: 5-10 year battery life on a 2400 mAh cell
• WiFi: 2-7 days on the same battery

This is why you never see battery-powered WiFi sensors in professional IoT deployments. If your device has a power outlet nearby, WiFi is great. If it runs on batteries, look elsewhere.

When to Choose WiFi

Choose WiFi for powered indoor IoT devices, high-bandwidth applications (video analytics, rich dashboards), real-time control systems requiring sub-100ms latency, and environments where WiFi infrastructure already exists and devices can be plugged into power.

When to Avoid WiFi

Avoid WiFi for battery-powered deployments, outdoor sensors more than 50 metres from an access point, environments with heavy WiFi congestion (dense office floors with 50+ APs from neighbouring tenants), and rugged industrial environments where enterprise APs cannot survive.

4G/5G Cellular: High Power, High Cost, High Capability

4G LTE and 5G are the premium tier of IoT connectivity. You get massive bandwidth (10-100+ Mbps), nationwide mobility, low latency, and carrier-grade reliability. But you pay for it in both power and money.

India's 5G Landscape (2026)

India's 5G rollout has covered most major cities by early 2026. Jio and Airtel offer 5G in over 700 cities and towns. However, 5G IoT-specific features like RedCap (Reduced Capability) and NR-IoT are still in early deployment, meaning most IoT devices still fall back to 4G for connectivity.

Cost Structure

When to Choose Cellular

Choose 4G/5G for mobile assets (fleet management across Indian highways), high-bandwidth applications (CCTV, video analytics), mission-critical systems requiring carrier-grade SLAs, and applications where devices have reliable power supply and the budget supports recurring costs.

The Comprehensive Comparison Matrix

Here is a side-by-side comparison of all four technologies across the parameters that matter most for Indian IoT deployments:

5-Year Total Cost of Ownership: The Numbers That Matter

Let us put real INR numbers behind these technologies. We will analyse three deployment scales that are common in Indian IoT projects.

Scenario 1: Small Pilot (50 Devices)

At 50 devices, WiFi wins if the deployment is indoors and devices are powered. NB-IoT is competitive for outdoor/remote deployments where building WiFi infrastructure is not feasible.

Scenario 2: Medium Deployment (500 Devices)

At 500 devices, the NB-IoT SIM costs have ballooned to Rs 30 lakhs over five years. LoRa is now nearly half the cost of NB-IoT. WiFi remains cheapest but is only viable if all 500 devices are in powered, indoor locations with existing WiFi coverage.

Scenario 3: Large Scale (5,000 Devices)

At 5,000 devices, LoRa costs less than half of NB-IoT. The Rs 3 crore SIM bill alone exceeds the entire LoRa deployment cost. This is why nearly every large-scale IoT project in India, from smart agriculture to smart city deployments, gravitates toward LoRa.

Real-World Decision Case Studies from India

Case Study 1: Smart Irrigation in Nashik Grape Vineyards

Project: 800 soil moisture sensors across 300 hectares of grape vineyards in Nashik district, Maharashtra

Requirements: 15-minute soil moisture readings, 7+ year battery life, coverage across hilly terrain with minimal cellular connectivity, integration with automated drip irrigation valves

Decision: LoRa

The team deployed 6 outdoor LoRa gateways on existing water tank towers (15-20 metre elevation). Each gateway covers a 3-5 km radius across the undulating vineyard terrain. Sensor nodes with capacitive soil moisture probes were buried at vine root level with only the antenna protruding above ground.

Why not NB-IoT: Cellular coverage in the vineyard areas was patchy (only 2 out of 3 operators had coverage, and signal strength dropped below -120 dBm in valleys). Additionally, 800 SIMs at Rs 100/month would cost Rs 9.6 lakhs per year, which is more than the entire LoRa infrastructure cost.

5-Year Cost: Rs 35 lakhs (LoRa) vs Rs 83 lakhs (NB-IoT estimate)

Result: 22% water savings in the first year, translating to Rs 18 lakhs in reduced electricity and water costs. The system paid for itself in under two years. Read more about our LoRa-based smart agriculture deployments.

Case Study 2: Smart Water Meters in Indore Municipal Corporation

Project: 12,000 ultrasonic water meters across Indore city for automated billing and leakage detection

Requirements: Once-daily meter readings, 15-year meter lifespan, meters installed in underground pits and basement meter rooms, city-wide deployment across 30+ wards

Decision: NB-IoT

Indore has excellent Jio NB-IoT coverage (the city was among the first Smart City Mission cities to receive NB-IoT infrastructure). The meters are installed in pits and basements where NB-IoT's superior indoor penetration (164 dB link budget) is critical. Deploying LoRa gateways across 30+ wards would require 50-80 gateway sites, negotiations with building owners, and ongoing maintenance, a logistical nightmare for a municipal corporation.

Why not LoRa: The geographic spread across an entire city, the need for deep indoor penetration in meter pits, and the municipal corporation's preference for a managed connectivity solution (no infrastructure to maintain) all favoured NB-IoT. At the negotiated bulk SIM rate of Rs 35/month from Jio, the economics were acceptable.

5-Year Cost: Rs 4.2 crores (NB-IoT, including SIM costs) vs Rs 3.1 crores (LoRa estimate, but with significant gateway deployment and maintenance overhead)

Result: Non-Revenue Water reduced from 38% to 24% within 18 months, saving the corporation Rs 12 crores annually in recovered water revenue.

Case Study 3: Smart Building Retrofit in Bengaluru Tech Park

Project: 350 sensors across a 2,00,000 sq ft IT campus in Whitefield, Bengaluru, covering occupancy detection, HVAC optimisation, indoor air quality, and energy monitoring

Requirements: Real-time occupancy data (sub-second updates for lighting automation), integration with existing BMS, deployment within existing office infrastructure

Decision: WiFi (Primary) + LoRa (Secondary)

The campus already had enterprise WiFi with 150+ access points. Occupancy sensors, indoor air quality monitors, and energy meters were deployed on WiFi since they all had access to power outlets and needed real-time data feeds. LoRa was used for outdoor parking lot sensors (battery-powered, weatherproof) and rooftop solar monitoring equipment where running power cables was impractical.

Why not all-WiFi: The outdoor parking sensors needed 5+ year battery life, which WiFi simply cannot deliver. A single LoRa gateway on the building rooftop covered the entire parking area and rooftop solar installation.

Result: 31% reduction in HVAC energy costs (Rs 45 lakhs annual savings), 100% parking occupancy visibility, and tenant satisfaction scores improved by 28%. Learn more about our smart building solutions.

Case Study 4: Cold Chain Fleet Monitoring Across India

Project: Temperature and GPS monitoring for 75 refrigerated trucks operated by a Kolkata-based pharmaceutical distributor, covering routes across East and Northeast India

Requirements: Continuous GPS tracking, temperature readings every 5 minutes, real-time alerts for temperature excursions, door open/close detection, coverage on National Highways and state roads

Decision: 4G Cellular

Trucks are constantly moving across state borders, highways, and urban areas. They have 12V/24V power from the vehicle battery. The high mobility requirement and need for real-time GPS tracking made 4G the only viable option.

Why not LoRa: No LoRa infrastructure along highways. You would need thousands of gateways along every route the trucks travel, which is obviously impractical. NB-IoT was considered but its higher latency (1-10 seconds) and lower bandwidth made real-time tracking less reliable, and coverage gaps in Northeast India were a concern.

5-Year Cost: Rs 52 lakhs (including Rs 36 lakhs in SIM and data costs)

Result: Zero temperature excursion losses in the first year (previously Rs 40 lakhs/year in spoiled pharmaceutical products). Insurance premium reduced by 12%.

Hybrid Architectures: The Smart Approach

In our experience, the most successful Indian IoT deployments use a hybrid approach, matching the right technology to each specific use case within the project. Here are two architecture patterns we frequently implement:

Hybrid Pattern 1: Smart City Infrastructure

For smart city projects like those under the Smart Cities Mission, we typically recommend:

Hybrid Pattern 2: Smart Industrial Estate

For industrial complexes and manufacturing zones:

Indian Regulatory Considerations

WPC Regulations for LoRa (865-867 MHz ISM Band)

India's Wireless Planning and Coordination Wing regulates the ISM band usage. Key points for LoRa deployments:

• Frequency: 865-867 MHz (3 channels available)
• Maximum transmit power: 1 Watt (30 dBm) EIRP
• Duty cycle: No explicit duty cycle restriction in India (unlike Europe's 1% limit), but responsible usage is recommended
• License: Not required for devices conforming to WPC standards
• Import: LoRa modules must have WPC ETA (Equipment Type Approval) certification

This regulatory environment is actually quite favourable for LoRa in India compared to Europe, where the 1% duty cycle severely limits transmission frequency.

Telecom Regulatory Authority of India (TRAI) for NB-IoT/Cellular

• NB-IoT and 4G/5G operate on licensed spectrum allocated by DoT
• M2M SIM cards have specific regulatory guidelines (TRAI M2M regulations)
• Bulk SIM procurement requires KYC compliance and may need a UL(VNO) license for large deployments
• Cross-border roaming for IoT SIMs is subject to DoT guidelines

Bureau of Indian Standards (BIS)

• IoT devices sold in India must comply with BIS safety standards
• Mandatory BIS certification for electronics (CRS registration)
• Relevant standards: IS 13252 (Safety), IS 616 (EMC)

Troubleshooting Common Connectivity Issues

Problem: LoRa Range Is Much Less Than Expected

Symptoms: Sensor nodes losing connectivity at 500 metres instead of the expected 3-5 km in urban areas.

Common Causes and Fixes:

1. Antenna orientation: Ensure the gateway antenna is vertical and has clear line of sight. A gateway mounted inside a room behind a glass window loses 6-10 dB compared to outdoor mounting.
2. Fresnel zone obstruction: Even if you can see the sensor from the gateway, buildings/trees in the path between them can significantly attenuate the signal. Raise the gateway to at least 10 metres above surrounding obstacles.
3. Incorrect frequency configuration: Verify that both gateway and nodes are configured for the 865-867 MHz Indian ISM band. Devices shipped with EU (868 MHz) or US (915 MHz) default settings will not work correctly in India.
4. Spreading factor mismatch: If nodes are configured for SF7 (fastest, shortest range), switch to SF10 or SF12 for longer range at the cost of lower data rate and higher battery consumption.

Problem: NB-IoT Devices Fail to Connect

Symptoms: SIM is activated, device powers on, but cannot attach to the network.

Common Causes and Fixes:

1. Operator NB-IoT band not supported: Jio uses Band 5 (850 MHz) for NB-IoT. Airtel uses Band 3 (1800 MHz). Ensure your module supports the correct band for your chosen operator.
2. APN configuration: NB-IoT requires a specific APN (Access Point Name) different from regular mobile data. Contact your operator for the correct M2M APN.
3. Coverage gap: Use the operator's coverage checker tool or test with a signal strength meter on-site before bulk deployment.
4. Power saving mode: If the device enters PSM (Power Saving Mode) too aggressively, it may miss downstream commands. Adjust the T3412 and T3324 timer values.

Problem: WiFi IoT Devices Keep Disconnecting

Symptoms: Sensors connect initially but drop off randomly, especially during business hours.

Common Causes and Fixes:

1. DHCP lease exhaustion: Enterprise networks may limit DHCP leases. Request a dedicated IP range for IoT devices from your IT team.
2. Band steering: Enterprise APs may aggressively steer devices to 5 GHz, but many IoT modules only support 2.4 GHz. Disable band steering for the IoT SSID.
3. Client isolation: Some APs enable client isolation for security, which prevents IoT devices from communicating with local gateways. Create a dedicated IoT VLAN.
4. Channel congestion: In dense office buildings, 2.4 GHz channels 1, 6, and 11 may be saturated. Consider WiFi 6 (802.11ax) APs with OFDMA for better multi-device handling.

Future-Proofing Your Connectivity Choice

Technologies to Watch in India (2026-2028)

5G RedCap (Reduced Capability): Expected to bridge the gap between NB-IoT and full 5G, offering moderate bandwidth (150 Mbps) with better power efficiency. Jio and Airtel are expected to roll out RedCap modules by late 2026 or early 2027. Device costs should be in the Rs 4,000-8,000 range.

WiFi HaLow (802.11ah): This sub-GHz WiFi standard promises 1 km range with low power consumption. However, it operates at 900 MHz which overlaps with the Indian ISM band and regulatory approval is still pending from WPC. Real deployments in India are unlikely before 2027.

LoRa 2.4 GHz: A higher-frequency variant of LoRa that offers more bandwidth (up to 253 kbps) at shorter range. Useful for global products that need a single frequency plan across countries. Available in India today but rarely used since the sub-GHz 865 MHz band offers far superior range.

Satellite IoT (ISRO/OneWeb/Starlink): For truly remote locations like forest reserves, offshore platforms, or high-altitude monitoring stations. ISRO's NavIC-based IoT communication is in development. Commercial satellite IoT services are available but expensive (Rs 500-2,000 per device per month).

Private 5G Networks: TRAI guidelines now allow enterprises to set up captive private 5G networks. Large manufacturing plants and logistics hubs are evaluating this option for ultra-low-latency applications. Costs are still prohibitive for most (Rs 1-5 crores for setup), but will decrease.

Decision Framework: A Step-by-Step Process

Use this framework to make your connectivity decision systematically:

Step 1: Define Your Requirements

• How many devices? (10s, 100s, 1000s, 10000s)
• Are they battery-powered or plugged in?
• How much data per device per day? (bytes, kilobytes, megabytes)
• How often do you need updates? (seconds, minutes, hours, daily)
• Where are the devices? (indoor, outdoor, underground, mobile)
• What is the deployment area? (single building, campus, city, nationwide)

Step 2: Eliminate Non-Starters

• Battery-powered + high bandwidth = NOT WiFi, NOT 4G
• Mobile across cities = NOT LoRa, NOT WiFi
• Underground/basement = NOT WiFi (usually), consider NB-IoT
• 10,000+ devices with tight budget = NOT NB-IoT, NOT 4G (SIM costs)

Step 3: Compare Remaining Options on TCO

• Calculate 5-year total cost using the tables in this article
• Include hidden costs: SIM management, battery replacements, gateway maintenance

Step 4: Conduct a Site Survey

• Test actual signal strength at your deployment locations
• Rent test equipment or request trial kits from vendors
• Verify that the chosen technology meets range and penetration requirements in your specific environment

Step 5: Run a Pilot

• Deploy 10-20 devices for 30-60 days
• Measure actual battery life, data reliability, and coverage
• Validate TCO assumptions with real data before committing to full deployment

Conclusion: There Is No Universal Best, But There Is a Best for You

The right IoT connectivity technology for your project depends on a unique combination of range, power, bandwidth, cost, and scale requirements. In the Indian context, we see the following patterns consistently:

• LoRa dominates for large-scale outdoor sensor networks: agriculture, smart cities, industrial estates, campus monitoring. If you are deploying 200+ battery-powered sensors and can install a few gateways, LoRa almost always wins on TCO. Explore our LoRa portfolio for real deployment examples.

• NB-IoT wins for city-wide distributed deployments where installing gateway infrastructure is impractical: smart metering, asset tracking across a metro area, and deep indoor applications.

• WiFi is ideal for powered indoor IoT within smart buildings: occupancy detection, HVAC control, energy monitoring, indoor air quality.

• 4G/5G is necessary for mobile assets and high-bandwidth applications: fleet tracking, video surveillance, connected vehicles.

• Hybrid architectures are the most successful: use the right technology for each use case within your project.

Need help deciding? IoTMATE offers free connectivity assessments for IoT projects across India. We will analyse your requirements, conduct site surveys, build a 5-year TCO model, and recommend the optimal connectivity architecture, whether that is LoRa, NB-IoT, WiFi, cellular, or a hybrid of multiple technologies. Contact us for a technical consultation and pilot equipment rental.