Most farm connectivity problems have the same cause. The places where a farmer most needs data, such as a far pasture, a borehole pump or the end of an irrigation line, are the places carriers serve worst. Cellular maps still show rural gaps, WiFi stops near the farmhouse, and satellite internet is built for bandwidth, not for a sensor that sends 20 bytes a few times an hour.
LoRa (the radio technique) and LoRaWAN (the open network standard built on it) were designed for that gap. In 2026 the question is no longer whether it works. The question is how to design, secure and maintain a network that still works in year five. This guide covers that, and says where LoRaWAN is the wrong tool.
LoRa vs LoRaWAN: A Distinction Worth Knowing Before You Buy
LoRa is the physical-layer modulation. It uses chirp spread spectrum to recover very weak signals, which is why a small battery-powered node can reach a gateway kilometres away. LoRaWAN is the open networking specification, maintained by the LoRa Alliance, that defines how devices join a network, encrypt traffic and roam.
Buy LoRaWAN-compliant hardware, not just “LoRa” hardware. Proprietary LoRa products can lock you into one vendor’s cloud. An open standard lets you change sensor brands or network servers later without replacing the whole farm network.
What Changed by 2026: Verified Developments
- Scale. In September 2026 the LoRa Alliance reported 150 million LoRaWAN devices deployed globally, growing about 25% a year. The figure was 125 million at the end of 2025.
- Ecosystem. The Alliance’s July 2026 agriculture release cites more than 650 certified devices from over 334 member companies. That means you can mix sensor makers instead of depending on one.
- Satellite backhaul and satellite-connected LoRaWAN. Satellite-linked LoRaWAN now extends coverage where terrestrial networks end. The Alliance’s roadmap lists Satellite Discovery Enhancements for 2026, which standardise how commercial off-the-shelf devices find LoRaWAN satellite constellations.
- Mobile gateways. A Walk-By/Drive-By Reading extension, also due in 2026, lets devices connect to base stations carried on vehicles, drones or by hand. A 2026 study in the Asian Journal of Agriculture and Development tested a LoRaWAN gateway on an agricultural drone over an oil palm plantation. It reported a 35% improvement in data recovery at locations where a fixed gateway had lost data.
- Easier onboarding. The roadmap includes device-migration features in 2026 and zero-touch onboarding in 2027. It also plans a standard gateway-to-network-server interface and a gateway certification programme in 2027. The Alliance announced new onboarding specifications in August 2026 as well, so check its technical documents for the current versions before you buy.
The Alliance is promoting its own technology, so treat its market claims as industry-sourced. The deployment examples below are still useful because they include concrete numbers.
Four Real Deployments and What You Can Copy From Them
These come from the LoRa Alliance’s July 2026 smart agriculture release.
| Farm context | What they did | Lesson for your farm |
|---|---|---|
| Banana disease monitoring (Ghana, Brazil) | Satellite-connected sensors track temperature and humidity on about 10 plants per hectare, with soil sensors on a 50 m grid and AI imaging | Sample density can be modest if sensors sit where disease risk is highest |
| Cattle tracking (Australia) | Solar GPS ear tags under 30 g, with solar-powered gateways in the middle of the property | Gateways need no mains power, so put them where coverage is best |
| Durian estate (Malaysia) | Over 20 soil sensors across 6,000 trees on 80+ hectares, replacing about two hours of daily manual checks | Count the labour you save, not just the sensor cost |
| Watermelon and cabbage fields (Bulgaria) | Soil moisture, temperature, humidity and light sensors feeding one phone-accessible platform | A single platform view matters more than extra sensor types |
Where LoRaWAN Fits Among Rural Connectivity Options
No single technology wins every job. An honest comparison:
| Need | Best fit | Why |
|---|---|---|
| Soil, weather, tank, pump and storage sensors | LoRaWAN | Low power, no data plan, long range |
| Moving assets where cellular exists | LTE-M / NB-IoT | Mobility and roaming, but a per-device subscription |
| Cameras, drone video, large files | WiFi, point-to-point links, private LTE/5G | LoRa data rates are far too low |
| Remote assets with no terrestrial coverage | Satellite IoT or satellite-backed LoRaWAN | Coverage where nothing else reaches |
The rule of thumb is simple: if the data fits in a short message sent every few minutes or hours, use LoRaWAN. If it is video or bulk data, use something else.
The Problems LoRaWAN Solves, and the Limits Nobody Mentions
Problem 1: No coverage. One elevated gateway can serve a large area. The Malaysian durian estate cites gateway coverage up to 10 km, but treat that as best case. Real range depends on antenna height, terrain and crop canopy, so plan for a few kilometres and test.
Problem 2: Subscription cost at scale. LoRaWAN uses licence-free spectrum, so there are no SIM plans. Illustrative arithmetic: at an assumed $3 per device per month for a cellular IoT plan, 40 sensors cost about $1,440 a year in connectivity. A private LoRaWAN network replaces that with one-off gateway, mast and backhaul costs plus your time. Use your own local quotes, because prices vary widely.
Problem 3: Power. Nodes sleep almost all the time. Vendors quote battery lives from three to ten years. Treat those as best-case figures, because cold weather, retries at weak signal and heavy sensors all shorten life.
Limits to plan around:
- Small payloads and low data rates. Fine for readings and alarms, unsuitable for images.
- Duty-cycle and airtime rules. In the EU 868 MHz band, ETSI rules limit how much each device can transmit, commonly 1% in main sub-bands. US 902–928 MHz rules differ. Check your national regulator before you design uplink rates.
- Downlink is limited. Commands to valves arrive only at specific moments for Class A devices. Use Class C or scheduled downlinks for actuators.
- The backhaul still depends on someone. The radio is yours, but the gateway’s internet link is not.
Seven Farm Use Cases With Design Notes
1. Soil moisture and temperature
Place sensors by management zone, not on a uniform grid. Use yield maps, soil surveys or elevation to find zones that behave differently, then install two or three sensors per zone at root depth. Keep the antenna above the crop canopy, because wet soil and dense foliage absorb signal. Calibrate against a gravimetric sample in season one. A 30-minute interval suits most irrigation decisions and saves battery.
2. Irrigation control
Put the safety logic on the device or local controller. A valve should have a maximum run time so a lost message never leaves a pump running. Log every command and acknowledgement.
3. Livestock
LoRaWAN suits herd location pings, water-trough levels, gate status and fence-breach alerts. Frequent GPS fixes drain batteries, so design for infrequent fixes. Do not assume a generic LoRa collar can deliver virtual-fence stimuli. Check animal-welfare rules, and test battery life on real animals, because mud, rain and rubbing shorten datasheet figures.
4. Water, tank and pump condition
Tank levels, trough floats and pump current are small signals with high value. Use event-driven alerts for alarms plus a regular heartbeat so you can tell a silent sensor from a failed one.
5. Weather and microclimate
Deploy small stations at low points, on ridges and near windbreaks. A hollow and a ridge can differ by several degrees on a still night, enough to change a frost-protection decision. Log leaf wetness, temperature and humidity together, because disease models use them in combination.
6. Grain bins and cold rooms
Metal bins block radio, so keep the antenna outside and run the sensor cable in. Alert on rate of change as well as thresholds, since a steady rise often warns of spoilage before any limit is crossed.
7. Pest and disease pressure
Send short results over LoRa, such as a count or a risk index, and run any image analysis on the device. Image-based traps are too heavy to send over LoRa.
Network Design: A Step-by-Step Method
- List use cases first. For each sensor, record what it measures, how often, how fast you must know of changes, and whether it needs a downlink.
- Check regulations. Frequency plans, power limits and duty cycles differ by country. Use the LoRa Alliance regional parameters and confirm with your national regulator.
- Place the gateway high. A gateway at 10–15 m on a mast or silo usually beats a stronger radio at ground level. Fit lightning and surge protection and proper grounding, because lightning is a common cause of rural gateway failure. Use low-loss cable and keep it short.
- Plan the backhaul with a failover. Use fibre or fixed wireless as primary and cellular as backup, or a satellite terminal where nothing else works. For very large or obstructed farms, a drone or vehicle-mounted gateway is an emerging option, supported by the 2026 oil palm study and the Walk-By/Drive-By extension.
- Pick a network server. ChirpStack is open source and self-hostable. The Things Stack offers open-source and managed options. Self-hosting gives data control and no per-device fees but makes you responsible for updates and backups. Check data-export rights before using any managed service.
- Run a pilot. Install one gateway and five to ten sensors at the hardest locations: the far corner, the valley, the densest block. Log signal strength (RSSI) and signal-to-noise ratio (SNR) for at least two weeks, across rain and dry spells.
- Use Adaptive Data Rate (ADR) for fixed sensors only. Turn it off for moving devices such as collars and machinery. Watch for devices stuck at the slowest, most battery-hungry setting.
Worked Battery Example (Illustrative, Replace With Datasheet Values)
For a soil sensor sending a 20-byte message every 30 minutes at a mid data rate, the radio uses on the order of a few thousandths of a milliamp-hour per message. Across 48 messages a day, sleep current and probe warm-up add a similar amount. The total is roughly a third of a milliamp-hour per day on paper. Real life is worse. Cold, self-discharge, retries and aging cells cut that sharply, so plan for several years, field-test, and send battery voltage as a regular reading.
Security: Rules That Actually Matter
LoRaWAN includes AES-128 encryption and authentication, but weak setup undoes it.
- Use OTAA (over-the-air activation) so every device gets fresh session keys.
- Give each device unique keys. Never reuse one key across a batch or leave factory defaults.
- Store keys in your network server or a vault, not in a shared spreadsheet.
- Protect devices physically. A valve controller can be tampered with directly.
- Secure the whole chain. The gateway, MQTT broker and dashboards are easier targets than the radio. Use TLS, strong passwords, current firmware and network segmentation.
- Plan firmware updates. Prefer devices with secure over-the-air updates and vendors that publish security fixes.
Common Failure Points and Fixes
- Gateway too low or poorly grounded: raise the mast, add surge protection.
- Too much airtime: reduce uplink frequency and let ADR work.
- Unplanned dead zones: valleys, dense orchards and metal buildings need a second gateway, a relay or a mobile gateway.
- Taking battery claims at face value: field-test and monitor voltage.
- No monitoring of the network itself: alert when devices go silent, not only when crops cross thresholds.
- Data in a silo: pick platforms that export via MQTT or an open API so data can reach dashboards and farm records.
Turning Data Into Decisions
- Dashboards and alerts (moisture low, tank empty, device offline).
- Local rules (close a valve after a set run time or at target moisture).
- Integration with farm records for irrigation logs and traceability.
- Models and forecasts, once you hold a full season of clean data.
Start at the first step and move up only once the data proves reliable. Many failed deployments jump straight to automation with uncalibrated sensors.
Also Read: Why Are Hybrid Human-AI Agritech Advisory Systems Emerging as a Middle Ground for Farm Decision Support
Community Networks and Shared Infrastructure
Neighbouring farms can share gateways and masts, and the Alliance notes that LoRaWAN supports roaming among public, private and community networks. Cooperatives and extension services can fund shared coverage. Agree in writing who owns the hardware, who maintains it, who sees which data and what happens when a member leaves. Check real coverage maps before depending on any public network, because rural coverage is often thin.
A 90-Day Rollout Plan
- Days 1–15: list use cases, check regulations, survey terrain, choose gateway and server.
- Days 16–40: install one gateway and a pilot group, logging signal quality and battery voltage.
- Days 41–70: fix weak spots, set alerts, verify calibration against manual checks.
- Days 71–90: scale up, document keys and device positions, write a maintenance checklist and test the failover.
Open Questions for Researchers in 2026
- How much does drone or vehicle gateway coverage improve on fixed gateways across different canopy types? The oil palm result needs replication on other crops.
- What is the real-world battery life of ear tags and soil nodes after one to three seasons, compared with datasheet claims?
- How well do satellite-backed LoRaWAN links hold up under heavy cloud, rain and canopy?
- What is the total cost of ownership over five years once gateway replacement, backhaul and labour are counted?
- How will standardised application data formats (planned for 2028) reduce integration cost for smallholders?
Conclusion
LoRaWAN will not fix every rural connectivity problem, but for small, frequent, battery-powered readings it is one of the most cost-effective tools a farm can own. The farms that benefit most match the technology to the job, treat security and maintenance as ongoing duties, and start with a pilot instead of a full rollout. With satellite backhaul, mobile gateways and easier onboarding arriving through 2026 and 2027, the network you build now can keep growing under your control.
Sources and References (External Links)
- LoRa Alliance, “From Remote Pastures to Satellite-Connected Fields: Why LoRaWAN Is Essential for Smart Agriculture” (July 7, 2026): https://lora-alliance.org/lora-alliance-press-release/from-remote-pastures-to-satellite-connected-fields-why-lorawan-is-essential-for-smart-agriculture/
- LoRa Alliance, 3-Year Technical Roadmap (Business Wire, June 2026): https://www.businesswire.com/news/home/20260601315147/en/LoRa-Alliance-Unveils-3-Year-Roadmap-for-Scaling-LoRaWAN-Globally
- GlobalSpec Electronics360, “There are now 150 million LoRaWAN devices deployed globally” (September 23, 2026): https://electronics360.globalspec.com/article/24154/there-are-now-150-million-lorawan-devices-deployed-globally
- Abd Aziz et al., “Flying LoRaWAN IoT Gateway for Oil Palm Plantation Monitoring,” Asian Journal of Agriculture and Development, 2026, vol. 23, issue 1: https://econpapers.repec.org/RePEc:ags:phajad:404803
- IoT M2M Council, “Farmers adopt LoRaWAN for remote monitoring” (July 13, 2026): https://iotm2mcouncil.org/iot-library/news/connected-industries-news/farmers-adopt-lorawan-for-remote-monitoring/
- LoRa Alliance, LoRaWAN specifications and regional parameters: https://resources.lora-alliance.org/technical-specifications
- ChirpStack, open-source LoRaWAN network server: https://www.chirpstack.io/
- The Things Industries, The Things Stack: https://www.thethingsindustries.com/stack/
- ETSI, short-range device standards (EN 300 220): https://www.etsi.org/
- US FCC, Part 15 unlicensed device rules: https://www.fcc.gov/
Frequently Asked Questions
How much does it cost to set up a basic LoRa network for a farm?
A basic LoRa network can be established quite affordably compared to alternatives. A single LoRa gateway costs typically between two hundred and one thousand dollars depending on capacity and features. Individual LoRa sensors range from twenty to one hundred dollars each depending on what they monitor and their sophistication. A starter system with one gateway and ten sensors might total around two thousand to three thousand dollars—comparable to just one year of cellular subscriptions for equivalent cellular sensors but without ongoing fees. Costs scale relatively linearly as sensors are added since a single gateway can support hundreds or thousands of sensors. Many farmers start small with a few sensors and expand as they see value, making entry costs quite manageable. Professional installation adds costs, but many farmers successfully self-install basic systems using available documentation and support.
What is the actual range of LoRa communication in rural farm settings?
Range varies significantly based on terrain, obstacles, antenna placement, and environmental factors. In open agricultural areas with good gateway antenna height, ranges of five to ten miles are regularly achievable, with some deployments reporting successful communication beyond fifteen miles in ideal conditions. Hilly terrain, dense vegetation, and buildings reduce range substantially—perhaps to one or two miles in challenging conditions. Most farms find that a single strategically placed gateway with elevated antenna covers their entire property even if spanning several square miles. For very large properties or those with challenging terrain, multiple gateways create overlapping coverage ensuring complete property monitoring. The practical approach involves starting with one gateway and testing actual coverage across specific properties before committing to extensive sensor deployment.
How does LoRa compare to cellular IoT solutions for agriculture?
The comparison involves tradeoffs rather than one being universally better. LoRa offers dramatically longer range from single gateways, years-long battery life versus months with cellular, no ongoing subscription fees, and complete independence from carrier coverage decisions. However, cellular IoT provides broader coverage beyond individual farm properties, can transmit more data when needed, and doesn’t require farmers to install and maintain gateway infrastructure. For monitoring assets that travel beyond farm boundaries or applications needing higher data rates, cellular may be preferable. For comprehensive on-farm monitoring with many sensors and predictable data needs, LoRa typically offers superior economics and reliability. Many farms use both—cellular for mobile equipment that travels and LoRa for field sensors with fixed locations.
Is LoRa network data secure from hackers or competitors?
LoRa includes encryption, authentication, and security features that prevent unauthorized access to network data when properly implemented. The LoRaWAN protocol uses AES-128 encryption, network session keys, and application session keys providing multiple security layers. However, security depends on proper implementation—using strong unique keys, keeping gateway firmware updated, and following security best practices. For farm applications, the greatest security concern is often physical access to sensors rather than digital hacking—someone removing a sensor from a field poses more realistic threat than remote hacking attempts. Farmers concerned about data privacy should work with providers who clearly explain security implementations and maintain sensors to prevent unauthorized physical access. Overall, properly implemented LoRa networks offer security appropriate for agricultural applications.
Can existing farm equipment and sensors be retrofitted to use LoRa communication?
This depends on specific equipment and sensors. Some manufacturers offer LoRa communication modules that can retrofit existing sensor designs, enabling upgrades without replacing functional equipment. Generic LoRa-enabled data loggers can interface with various sensors via analog or digital inputs, essentially adding LoRa connectivity to non-connected sensors. However, many existing farm sensors designed for cellular or wired communication cannot be retrofitted economically—the cost of modification exceeds simply deploying new LoRa-native sensors. The practical approach involves continuing to use existing equipment until replacement is warranted, then choosing LoRa-compatible options. For new deployments or major system upgrades, selecting LoRa-native solutions from the beginning typically provides better integration and lower total costs than attempting retrofits of incompatible existing equipment.
Andrew David writes about finance, agricultural technology, and the newest trends in those areas. He brings nine years of experience and holds both a BSc and an MSc in Economics. His work breaks down complex ideas into clear, practical writing for professionals and everyday readers.
Leave a Reply