NB-IoT vs LoRaWAN, which has more byte?

Connectivity is one of the most underestimated parts of remote sensing.

Everyone focuses on the sensor.

Is it accurate?
Is it calibrated?
Is the enclosure waterproof?
Is the battery big enough?

All important questions but they do not matter much if the device cannot reliably get data out of the field.

Through our recent NB-IoT deployments, including environmental monitoring systems used in vineyard field trials, we have spent a lot of time thinking about the practical trade-offs between WiFi, LoRaWAN, NB-IoT and satellite backhaul.

There is no universal winner. The right answer depends on the site, the payload, the power budget and the project model.

Power

WiFi is rarely the first choice for remote battery-powered sensing. The modules are cheap and familiar, but the power profile is usually better suited to mains-powered devices, local hubs or sites with existing infrastructure.

LoRaWAN can be excellent for low-power telemetry. For small payloads sent infrequently, it can be extremely efficient.

NB-IoT can also work very well on batteries, but only when it is engineered properly. You cannot just add a modem and hope for the best. Registration time, signal quality, attach retries, PDP activation, transmit current, PSM, eDRX and modem shutdown behaviour all affect the real battery life.

For us, the power work is not theoretical. It means measuring the actual current profile, controlling wake windows, limiting failed attach attempts, and making sure the device gets back to sleep cleanly after a successful or failed transmission.

Bandwidth

Most field sensing applications do not need much data.

A soil moisture reading, light level, temperature, spectral measurement, battery voltage and signal diagnostic payload is tiny compared with normal internet traffic.

That makes WiFi feel excessive at the individual sensor level. They can be useful as site backhaul, especially where a farm, estate, research site or construction site needs broader connectivity, but they are rarely proportionate for every low-power sensor node.

LoRaWAN is well suited to small packets, but payload size, duty cycle, downlink limits and network congestion need to be considered.

NB-IoT gives more flexibility for conventional IP-based workflows such as HTTP, MQTT or CoAP. That is useful when you want the sensor to talk directly to cloud infrastructure without installing and maintaining a local gateway.

Infrastructure

This is one of the core differentiators between the approaches. 

WiFi needs local infrastructure: router, access point, broadband, power and range planning.

LoRaWAN needs a gateway. That gateway needs a good mounting position, power and backhaul. If it is your gateway, it is also your network to maintain.

NB-IoT uses existing cellular infrastructure. For the right site, that is a major advantage: no gateway, no local broadband dependency, and no need for the landowner or project partner to maintain a network.

Project fit

A LoRaWAN gateway may be completely justified if you are deploying many devices across one controlled site but it is still hardware, installation time and maintenance risk.

With NB-IoT, the cost model can be simpler. Low-cost IoT SIMs, including providers such as 1NCE, can often be treated as project consumables and built into the deployment budget from day one.

That makes NB-IoT especially useful for sparse deployments: a few devices across several sites, trial plots, vineyards, farms, reservoirs, woodland areas, buildings or other hard-to-reach environments.

Takeaway

LoRaWAN is excellent when you want very low-power devices and you can control the gateway infrastructure.

WiFi is useful when the infrastructure already exists.

NB-IoT is a strong fit when you need small, battery-powered devices to send data from hard-to-reach places without installing your own network.

At Fyto, this is the kind of engineering we care about: supporting the full journey from funding application and project management through to sensor development, field deployment, data infrastructure and commercialisation. Every decision, from radio technology to power strategy to data architecture, is a fine balance between technical performance, project budget, deployment risk and long-term value.