Do I Need a Gateway for LoRa? When You Do and When You Don’t

Do I Need a Gateway for LoRa? When You Do, When You Don’t, and What to Buy Instead

If your sensors are LoRaWAN, yes: a gateway is mandatory, along with a network server. If they are plain LoRa (point-to-point), no gateway is needed, but you still need a LoRa receiver at the other end, because a LoRa radio can only talk to another LoRa radio. There is no version of LoRa that reaches a phone, a laptop, a Wi-Fi router or the cloud on its own.

The rest of this guide explains each row, what it costs you, and how to tell which kind of sensor you’re about to buy.

Why This Question Gets Two Different Answers

“LoRa” names two different things, and they need different hardware.

• LoRa is the radio modulation. Two LoRa radios can talk to each other directly, with nothing in between. That’s point-to-point (P2P) LoRa.
• LoRaWAN is the network protocol built on top of LoRa. It defines how sensors join a network, how data is encrypted, and how a gateway forwards it to a server. A LoRaWAN sensor is built to talk to a gateway and nothing else.

So a chip vendor can truthfully say you don’t need a gateway for LoRa, while a sensor vendor truthfully says their LoRaWAN sensor is useless without one. Both are right; they’re describing different products. For the full distinction, see LoRa vs LoRaWAN: What’s the Real Difference?

The practical question is therefore: which kind of sensor do you have, or intend to buy?

If Your Sensors Are LoRaWAN: Yes, You Need a Gateway

A LoRaWAN gateway listens on all the band’s channels at once, decodes every packet it hears, and forwards them over Ethernet, Wi-Fi or 4G to a network server. Without one, a LoRaWAN sensor transmits into empty air.

Three things are worth knowing before you resent the extra box:

1. Gateways aren’t paired with sensors. Any gateway in range hears any sensor on the same network. One gateway on a roof typically covers a whole factory or campus, and hundreds of sensors can share it. See How Far Can a LoRaWAN Sensor Transmit?
2. You also need a network server. The gateway only forwards packets. A network server such as ChirpStack or The Things Stack handles joins, decryption and delivery to your dashboard. ChirpStack is free to self-host, some gateways include a built-in server, and vendor clouds offer it as a service. See How to Connect a LoRaWAN Sensor to ChirpStack.
3. The gateway needs backhaul. Ethernet or Wi-Fi where the building has internet; a 4G SIM where it doesn’t.

What the gateway buys you in return: AES encryption end to end, adaptive data rate that stretches battery life, remote configuration by downlink, a sensor count limited by airtime rather than by addressing, and a standard path to any cloud or on-premise platform.

For a single building, an indoor gateway is the usual starting point. For a campus, yard or farm, an outdoor gateway on a mast. The choice is covered in Indoor vs Outdoor LoRaWAN Gateway.

If Your Sensors Are Plain LoRa: No Gateway, but You Need a Receiver

A point-to-point LoRa sensor sends to a fixed receiver that you configure to match it. The receiver then hands the data to something wired: a PLC, an HMI, a datalogger or a PC.

This is the setup for sites that have no internet, already run a PLC or SCADA system, or simply want sensor readings on a local screen with no server involved.

Our MacTalk-DM range works this way:

Both ends are set to the same frequency, spreading factor, encryption key and slave ID through the Maya app, and the link runs on the Indian 865–868 MHz band. There’s no server, no internet, no subscription and nothing to maintain beyond the devices themselves.

The trade-offs are real, and you should know them before choosing this path:

• Fixed configuration. No adaptive data rate; you pick a spreading factor that reaches the furthest sensor and all of them use it.
• Fixed capacity. The receiver has a defined limit (20 devices at 5-minute intervals for MacTalk-DM). Beyond that you add another receiver, and each receiver is its own island.
• No cloud unless you add it. Data stops at the PLC or datalogger. If the plant later wants a dashboard, something has to forward it.
• Vendor-specific. P2P sensors from one maker won’t talk to another maker’s receiver, and they won’t talk to a LoRaWAN gateway either. See Will a LoRa Sensor Work With Your LoRaWAN Gateway?

For a factory with five to twenty monitoring points and an existing PLC, this is often the right answer. For anything that will grow or needs a dashboard, LoRaWAN usually is.

Can a LoRa Sensor Send Data Straight to My Phone, Laptop or Wi-Fi?

No. Phones, laptops and routers don’t contain LoRa radios, so nothing you already own can receive a LoRa transmission.

Two things cause confusion here:

• Bluetooth configuration. Many LoRa sensors, including ours, are set up over Bluetooth from a phone app. That’s for configuration and installation checks, not for carrying the readings. The data still travels over LoRa to a receiver or gateway.
• USB LoRa dongles. A LoRa dongle plugged into a PC is a receiver, which is fine for development and for P2P setups where the PC is the destination. It is not a LoRaWAN gateway, and a single-channel dongle used as one will miss most of a LoRaWAN sensor’s packets.

If you want sensors with no new infrastructure at all, the answer isn’t LoRa. A Wi-Fi sensor such as the MacSync WT1 joins your existing network and posts straight to a server over MQTT or HTTPS, with no gateway. The trade-offs, mainly battery life, range through walls and dependence on the IT network, are in LoRaWAN vs Wi-Fi Temperature Sensor.

Can I Use a Public LoRaWAN Network Instead of Buying a Gateway?

n India, plan on your own gateway.

Sigfox and cellular work on a subscription: you buy the device, pay the operator, and coverage is their problem. LoRaWAN can work that way too, and in some European cities public LoRaWAN networks are dense enough to rely on. In India they aren’t. The Things Network has community gateways in a few cities, but they’re volunteer-run, patchy, and nobody guarantees they’ll be there next month. Carrier LoRaWAN networks exist mainly for the carriers’ own metering and enterprise contracts, not as a service a warehouse can sign up for.

The good news is that a private gateway is a one-time purchase with no recurring fee, and it gives you control over coverage that a public network never would.

Which Setup Do You Need?

Pick by what the data has to do, not by the hardware you’d rather avoid.

What the Gateway Really Costs

For most sites past about ten sensors, the gateway is a small share of the project, and it’s the part you buy once.

Account for three things:

• Hardware. An indoor gateway costs less than an outdoor one with a mast-mount antenna. Buy for the site you have, not the one you might have.
• Network server. Self-hosted ChirpStack is free software; the cost is the engineer’s time and a small server or VPS. The Things Stack’s community tier is free for development. Vendor clouds charge per device or per gateway.
• Backhaul. Nothing if the building has Ethernet or Wi-Fi; a data SIM if it doesn’t.

Set against that, a P2P receiver costs less than a gateway and needs no server at all, but every sensor beyond its capacity means another receiver, and every “can we see this on a dashboard?” request later means an integration project. The cheaper option on day one isn’t always cheaper by year two.

How to Tell Which Kind of Sensor You’re Buying

Check these before you order, because the wrong assumption here is the most expensive mistake in a first deployment.

1. The datasheet says “LoRaWAN” and lists OTAA/ABP, DevEUI and AppKey. It needs a gateway.
2. The datasheet says “LoRa” with a channel, spreading factor and a matching receiver, and talks about RS485, Modbus or “transparent mode”. It’s point-to-point; it needs that receiver.
3. It lists a LoRaWAN region (IN865, EU868, US915). LoRaWAN. Buy the IN865 variant for India.
4. It’s sold as a kit with “receiver” or “master” hardware. P2P, and usually locked to that vendor’s receiver.

If a datasheet is ambiguous, send it to us and we’ll tell you which it is: contact Macnman. The full checklist is in the compatibility guide.

Mistakes We See Most

Buying P2P sensors and expecting a cloud dashboard. The data stops at the receiver. Either add a datalogger that forwards it, or start with LoRaWAN.

Buying LoRaWAN sensors and expecting them to show up on a laptop. They’ll join nothing until a gateway and network server exist.

Using a single-channel “gateway” for LoRaWAN. A single-channel board hears one of the band’s channels, so a sensor that hops channels as the standard requires loses most of its packets. Use a multi-channel gateway; our guide to single-channel vs multi-channel gateways explains why.

Assuming a public network covers the site. In India it almost certainly doesn’t. Budget for a gateway from the start.

Start With Everything You Need in One Box

Macnman designs and manufactures LoRa and LoRaWAN hardware in India for the 865–868 MHz band, on both sides of this choice:

• LoRaWAN: sensors and gateways, with ChirpStack integration guides and published decoders
• LoRa P2P: the MacTalk-DM sensors and RS485 gateway node for PLC and offline sites
• No gateway at all: Wi-Fi sensors for small sites with good coverage

Not sure which you need? Tell us the site, the number of monitoring points, and where the data has to end up, and a product engineer will recommend a setup within one working day: get in touch. To try LoRaWAN without sourcing anything separately, the pilot kit ships sensors and a gateway together, ready to join.

Frequently Asked Questions

Do I need a gateway for LoRa?
Only for LoRaWAN. Plain point-to-point LoRa needs no gateway, but it does need a LoRa receiver at the other end, usually one with an RS485 or USB output into a PLC, datalogger or PC. A LoRa radio can only communicate with another LoRa radio.

Do LoRaWAN sensors need a gateway?
Yes, always. A LoRaWAN sensor transmits to a gateway, which forwards the packet to a network server. Without both, the sensor’s data goes nowhere. One gateway can serve hundreds of sensors across a building or campus.

Can LoRa work without internet?
Yes. A point-to-point LoRa link to a local receiver needs no internet at all, and the data can be read by a PLC or HMI on site. A LoRaWAN gateway can also run with an on-site network server such as ChirpStack and no internet connection, though cloud dashboards obviously need one.

Can a LoRa sensor connect directly to a PLC?
Not directly, but through a LoRa receiver with a Modbus RS485 output, such as the MacTalk-DM gateway node. The PLC polls the receiver’s registers as it would any Modbus slave, with no gateway, server or internet involved.

Can a LoRa sensor send data to my phone?
No. Phones have no LoRa radio. Bluetooth is often used to configure LoRa sensors from a phone app, but the readings themselves travel over LoRa to a receiver or gateway, and reach your phone only through a server or dashboard.

How many LoRa sensors can work without a gateway?
It depends on the receiver. Macnman’s MacTalk-DM gateway node handles up to 20 sensors reporting at 5-minute intervals. Beyond that you add another receiver, or move to LoRaWAN, where a gateway serves hundreds of sensors.

Is there a public LoRaWAN network in India I can use instead of a gateway?
Not one you can rely on for a commercial deployment. The Things Network has volunteer community gateways in a few Indian cities, with no guarantee of coverage or uptime. Plan on installing your own gateway, which is a one-time cost with no subscription.

What is the cheapest way to receive LoRa sensor data?
For a few sensors feeding a PLC or PC, a point-to-point receiver is cheapest: no gateway, no server. For a dashboard or anything that will grow, an indoor LoRaWAN gateway with free self-hosted ChirpStack is the lower-cost path over time.

Do I need a network server as well as a gateway?
Yes for LoRaWAN. The gateway forwards packets; the network server handles device joins, decryption and delivery to your application. Options include self-hosted ChirpStack, The Things Stack, a server built into some gateways, or a vendor cloud.

Can one gateway cover my whole site?
Often, yes. An indoor gateway usually covers a large building; an outdoor gateway on a mast covers a campus of a few square kilometres. Sites with several steel-clad buildings, cold stores or heavy racking may need one gateway per building. A short site survey settles it.