Skip to main content
LoRa wireless module connected to microcontroller development board for IoT prototyping

Getting Started with LoRa in India: Why 433 MHz Deserves Your Attention

GSAS Engineering · · 4 min read

India's Department of Telecommunications permits both the 433 MHz band (433.05 to 434.79 MHz) and the 865 to 867 MHz band for unlicensed low-power use, while the 915 MHz band used in North America is not authorised in India. For LoRa in India that makes 433 MHz a valid choice rather than a workaround, and its lower frequency penetrates foliage and masonry better than 868 MHz.

Most LoRa tutorials and reference designs focus on 868 MHz (Europe) or 915 MHz (North America). Indian engineers following these guides often default to 868 MHz modules without considering that India authorises 433 MHz as an ISM band, and for many IoT applications, 433 MHz offers meaningful technical advantages over higher frequencies.

India’s ISM Band Landscape

India’s Department of Telecommunications permits the use of several ISM (Industrial, Scientific, and Medical) bands for low-power devices. The 433 MHz band (433.05 - 434.79 MHz) and the 865-867 MHz band are both available for unlicensed IoT use, subject to power limits. The 915 MHz band used extensively in North America is not authorised in India.

For LoRa deployments, both 433 MHz and 865-867 MHz are viable. The Reyax module family covers both: the RYLR498 operates at 433 MHz, while the RYLR998 operates at 868/915 MHz. Both share the same Semtech SX1262 chipset, AT command interface, and pin-compatible footprint, meaning the frequency choice is a module swap, not a redesign.

433 MHz Advantages for Indian Deployments

Better vegetation penetration. Lower frequencies experience less attenuation when passing through foliage, crop canopy, and vegetation. For agricultural IoT deployments, the largest LoRa use case in India, 433 MHz signals travel further through planted fields than 868 MHz signals. This directly translates into fewer gateways needed to cover the same area.

Better building penetration. In urban deployments across Mumbai, Delhi NCR, and Bengaluru, 433 MHz signals penetrate concrete and brick structures more effectively than 868 MHz. For smart metering and building automation where sensor nodes are inside structures, this improved penetration reduces dead zones.

Longer wavelength, more forgiving antenna tolerances. A quarter-wave antenna at 433 MHz is approximately 17 cm, larger than the 8.6 cm quarter-wave at 868 MHz, but more forgiving of manufacturing tolerances and ground plane imperfections. For products manufactured in Indian facilities where antenna assembly is manual, the wider tolerance margin at 433 MHz reduces yield loss from antenna-related performance variation.

Less crowded spectrum. In Indian industrial environments, the 433 MHz band sees less interference from other devices compared to 2.4 GHz (crowded with Wi-Fi, Bluetooth, and microwave ovens) and increasingly populated sub-GHz bands. Lower interference means more reliable communication.

Tradeoffs to Consider

Antenna size. The 17 cm quarter-wave antenna at 433 MHz is larger than the 8.6 cm antenna at 868 MHz. For compact wearable or handheld devices, the larger antenna may be a constraint. For sensors in enclosures, gateway antennas on poles, and vehicle-mounted trackers, the size difference is usually acceptable.

Data rate. LoRa data rate is influenced by bandwidth, and the available bandwidth at 433 MHz (1.74 MHz band) is narrower than at 868 MHz. In practice, most LoRa applications transmit small payloads (20-100 bytes) at low duty cycles, so the data rate limitation is rarely a constraint.

Regulatory power limits. Check the current DoT regulations for maximum EIRP (Effective Isotropic Radiated Power) at 433 MHz versus 865-867 MHz. Power limits affect maximum range, and the allowed power may differ between bands.

First LoRa Project: Hardware Setup

To get started with LoRa using the Reyax RYLR498 (433 MHz), you need:

  1. Two RYLR498 modules: one as transmitter, one as receiver
  2. Two microcontrollers with UART, Arduino, STM32 Nucleo, ESP32, or any MCU with a serial port
  3. Two 433 MHz antennas: quarter-wave whip or helical, connected to the module’s U.FL connector or soldered to the PCB antenna pad
  4. 3.3 V power supply: the module operates at 2.0 to 3.6 V

Wire each module to a microcontroller: VCC to 3.3 V, GND to GND, TX to MCU RX, RX to MCU TX. Open a serial terminal at 115200 baud.

Basic AT Command Walkthrough

Configure both modules to the same network ID and frequency:

AT+NETWORKID=6
AT+BAND=433000000
AT+PARAMETER=12,7,1,4

The AT+PARAMETER command sets spreading factor 12, bandwidth 125 kHz (code 7), coding rate 4/5 (code 1), and preamble length 4. This configuration maximises range at the cost of data rate, ideal for initial testing.

On the transmitter, send data:

AT+SEND=0,11,Hello India

On the receiver, the data arrives as:

+RCV=0,11,Hello India,-45,12

The -45 is RSSI (signal strength in dBm) and 12 is SNR (signal-to-noise ratio in dB). These values tell you the link quality, useful for optimising antenna placement and spreading factor for your deployment environment.

From Bench to Field

Once basic communication works on the bench, the next steps are:

  1. Range test: move the transmitter progressively further from the receiver, noting RSSI at each distance. This characterises your specific environment.
  2. Antenna elevation: raise the gateway antenna to 3-5 metres and repeat. You will see a dramatic range improvement.
  3. Parameter optimisation: reduce spreading factor (SF12 → SF10 → SF9) until the link becomes unreliable, then step back one level.

Lower SF means faster data rate and lower power consumption per transmission. 4. Sleep mode integration: implement wake/transmit/sleep cycles in the MCU firmware to validate battery life projections.

Scaling to Production

The RYLR498’s FCC and CE pre-certification means the module can be used as a certified module within a host product. For Indian teams building products for export, this eliminates the need for separate RF testing of the wireless subsystem. For domestic Indian deployments, confirm compliance with DoT’s current ISM band regulations for 433 MHz.

Why Buy from GSAS

GSAS Micro Systems provides Reyax RYLR498 (433 MHz) and RYLR998 (868 MHz) LoRa modules from Indian inventory with INR invoicing. Our team supports frequency selection guidance, antenna design review, and regulatory compliance consultation for Indian IoT deployments. Engineers across Bengaluru, Hyderabad, Chennai, Pune, Mumbai, and Delhi NCR can access local technical support. Contact GSAS for evaluation modules or to discuss your LoRa project.

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

Embedded engineering bench in India, illustrating the hardware a developer can act on today, supported by GSAS
Technical Guides Arm

Arm's Agentic AI Push: What Indian Embedded Teams Can Actually Use Today

Arm has set out its platform strategy for the agentic era, putting inference everywhere it has compute. Indian embedded teams can start on that direction this quarter with the Cortex-M toolchain they already own: Helium, CMSIS-NN, Ethos-U and Vela, on boards you can order today.

13 Sept 2026 · 7 min read
Side by side comparison of a 10BASE-T1S multidrop mixing segment, one balanced pair with four nodes on short stubs and a termination at each end, against a point to point star of four separate links into switch ports, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

10BASE-T1S and PLCA: Multidrop Ethernet Explained

10BASE-T1S is the one member of the T1 single-pair Ethernet family that keeps a shared medium, and PLCA is the reconciliation sublayer that stops the nodes on it from colliding. This article covers what IEEE 802.3cg standardises, how the beacon and transmit opportunities schedule a cycle, the node count and segment length figures the OPEN Alliance interoperability test suite works to, and the failure modes that put a segment quietly back into contention while every link still looks up. Written by the GSAS Micro Systems engineering team in India for teams bringing up multidrop segments on the bench.

29 Aug 2026 · 12 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