Skip to main content
LoRa-connected soil moisture sensor deployed in an Indian agricultural field

LoRa for Smart Agriculture in India: Building Wireless Sensor Networks That Actually Work in the Field

GSAS Engineering · · 4 min read

Precision agriculture in India faces a connectivity problem. Farm fields are large, spread across terrain with no cellular infrastructure, and populated with hundreds of sensor points that need to transmit small data packets, soil moisture, temperature, humidity, water level, to a central gateway. Wi-Fi range tops out at 100 metres.

Cellular modules require SIM cards and monthly subscriptions that multiply across hundreds of nodes. LoRa fills the gap: multi-kilometre range, no subscription fees, and battery life measured in years.

Why LoRa Fits Indian Agriculture

Indian farms present specific challenges for wireless connectivity. Fields in Hyderabad, Pune, and Chennai agricultural belts can span 50 to 500 hectares. The terrain is flat or gently rolling, with crop canopy heights varying from ground-level vegetables to 3-metre sugarcane. Ambient RF interference is low compared to urban environments, but the sheer distance between sensor nodes and the gateway demands a radio technology designed for range.

LoRa’s spread-spectrum modulation achieves 16+ km line-of-sight range from a single module. In practical agricultural deployments with crop obstruction and terrain effects, real-world range typically falls between 3 km and 8 km, still sufficient for a single gateway to cover an entire farm or a cluster of adjacent fields. The Reyax RYLR998 operating at 868 MHz, or the RYLR498 at 433 MHz (India’s authorised ISM band with better vegetation penetration), provides the radio link.

Sensor Node Architecture

A typical farm sensor node consists of four components: a soil moisture sensor (capacitive type for durability), a microcontroller (STM32, ESP32, or even an ATmega328), a LoRa module, and a battery with optional solar charging. The sensor reads soil moisture and temperature at programmed intervals, every 15 minutes is common for irrigation decision-making, and the microcontroller formats the reading into a compact data packet and sends it over UART to the LoRa module.

The Reyax AT command interface simplifies the firmware. A typical transmission sequence in the microcontroller firmware:

  1. Wake from sleep
  2. Power on the sensor and read ADC values
  3. Format a 20-byte payload: node ID, soil moisture %, temperature, battery voltage
  4. Send AT+SEND=0,20,<payload> to the RYLR998 over UART
  5. Wait for +OK confirmation
  6. Power down the module and return to deep sleep

The entire wake-transmit-sleep cycle takes under 2 seconds. At a 15-minute interval, a 3.7 V lithium cell with 2000 mAh capacity can power the node for over two years, the LoRa module’s sub-2 uA sleep current means the battery drain is dominated by the sensor and microcontroller, not the radio.

Gateway and Cloud Architecture

The gateway receives data from all sensor nodes within its radio range and forwards the aggregated data to a cloud platform. A common gateway configuration uses a Raspberry Pi or similar Linux SBC with a Reyax LoRa module on UART for the radio link, and Wi-Fi, Ethernet, or a cellular modem for the cloud uplink.

For farms near Bengaluru or Hyderabad with reliable cellular coverage at the farmhouse, a 4G modem on the gateway provides the cloud connection. For remote locations without cellular coverage, a satellite backhaul (increasingly affordable with LEO satellite services) or a store-and-forward architecture where a field worker collects data via Bluetooth from the gateway periodically can bridge the connectivity gap.

Cloud platforms, ThingsBoard, Grafana with InfluxDB, or custom dashboards, display real-time soil moisture levels, send irrigation alerts when moisture drops below thresholds, and log historical data for crop planning. The data granularity enabled by LoRa sensor networks transforms irrigation from scheduled flooding to demand-driven precision watering.

Frequency Selection: 433 MHz vs. 868 MHz

India authorises both 433 MHz and 868 MHz for ISM band use. For agricultural deployments, 433 MHz offers a meaningful advantage: lower frequency signals penetrate vegetation and soil moisture more effectively than higher frequencies. A 433 MHz signal passing through a sugarcane field experiences less attenuation than an 868 MHz signal over the same path.

The Reyax RYLR498 operates at 433 MHz with the same AT command interface and pin-compatible footprint as the 868 MHz RYLR998. Teams can prototype with either module and switch frequencies by swapping the module, no PCB layout changes required.

Antenna Placement in the Field

Antenna height is the single most impactful factor for LoRa range in agricultural settings. Raising the gateway antenna to 3-5 metres on a pole significantly improves range compared to a ground-level installation. Sensor node antennas should be elevated above the crop canopy when possible, a simple 30 cm standoff from the enclosure mounting point can make the difference between reliable and intermittent links through dense crop cover.

For sensor nodes using the RYLR998 or RYLR498 with U.FL connector, a quarter-wave whip antenna provides omnidirectional coverage suitable for sensor nodes. The gateway benefits from a higher-gain collinear antenna (6 dBi or higher) mounted vertically to maximise range to all nodes in the field.

Scaling from Pilot to Production

Many Indian agritech startups begin with a 10-20 node pilot on a single farm and then need to scale to hundreds of nodes across multiple locations. The LoRa approach scales naturally: each farm gets its own gateway, and the cloud platform aggregates data from all gateways. The per-node hardware cost remains constant, and there are no recurring connectivity fees to multiply with scale.

Why Buy from GSAS

GSAS Micro Systems provides Reyax LoRa modules from Indian inventory with INR invoicing, both the 868 MHz RYLR998 and the 433 MHz RYLR498. Our team supports agritech projects with module selection guidance, antenna recommendations for agricultural environments, and network architecture consulting. Engineering teams across Bengaluru, Hyderabad, Chennai, Pune, Mumbai, and Delhi NCR can access local support for smart agriculture deployments at any scale. Contact GSAS to discuss your precision agriculture wireless requirements.

Interested in REYAX tools?

Talk to our application engineers for personalized tool recommendations.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.

Related Articles

Solid Sands campaign artwork for SuperTest Van Gogh 6.0, C++ source code set against Van Gogh's The Starry Night
Functional Safety Solid Sands

SuperTest Van Gogh 6.0: C23, C++23 and the C++20 Modules Gap

Solid Sands has released SuperTest Van Gogh 6.0 with more than 1,900 new tests, including 480 for C23 and 440 for C++23. The number worth your attention is a different one: GCC, Clang and MSVC each currently fail about 20% of its 173 C++20 modules tests.

6 Oct 2026 · 7 min read
Horizontal stacked bar showing where an ADAS test vehicle's bandwidth budget is spent, split into cameras, lidar, radar and bus traffic, with the logger uplink limit drawn as a vertical rule crossing the bar, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

ADAS Sensor Data Logging: Bandwidth Budgets That Add Up

Every page that tells you an ADAS test vehicle produces terabytes a day states the headline and skips the arithmetic, so you cannot redo it for your own sensor set. This article publishes the arithmetic instead: one formula, every table row derived on the page, a worked eight-hour drive that chains those rows into a sustained write rate, a media count and an offload window, and the five places bandwidth budgets go wrong. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 15 min read
The bench to harness adapter path drawn left to right: the ECU connector, a test lead, a media converter or pluggable T1 module, RJ45, and the host, showing where each connector family sits between the device under test and the laptop, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Ethernet Connectors: H-MTD, MATEnet, MQS

An ECU arrives on the bench with a connector nobody has a mate for, and the day is gone. Search the family names and you get connector product pages that describe their own part and stop there. This article puts the families side by side in one table using only what their public pages state, then makes the point those pages leave out: the IEEE link segment definition, not the connector, is what sets reach and loss limits, and shielding is a channel decision rather than a preference. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 12 min read