IoT Where There Is No Signal: Connectivity Options for Plantations, Mines and Remote Sites
November 11, 2026 · 7 min read · Etzal Group Team
A plantation company wants to monitor water levels in forty drainage canals, rainfall at six points and fuel in a dozen tanks, across twelve thousand hectares. The sensors are chosen in a week. Then someone opens a coverage map: mobile signal reaches the main office and the road in, and almost nothing beyond. Projects of this kind succeed or fail on one question: how to do IoT where there is no signal.
Two links, not one
Think of connectivity as two separate hops.
- The field link: from each sensor to a collection point on site, a gateway.
- The backhaul: from the gateway to the internet or the office.
They have different requirements. The field link must reach many scattered, battery-powered devices. The backhaul carries everything from one powered location. Choosing them separately opens up far more options than looking for one technology that does both.
How much data, how often
Before choosing anything, write down for each sensor:
- Size of a reading. A level or a temperature is a few bytes.
- How often. Every fifteen minutes, hourly, daily?
- How quickly it must arrive. Within a minute, or by the end of the day?
- What happens if it is late. A missed alarm, or simply a gap in a chart?
Most environmental monitoring is small, infrequent and tolerant of delay. That makes low-power, low-bandwidth options suitable and keeps costs down. Video and high-frequency vibration data are a different problem.
Option 1: LoRaWAN
Long-range, low-power radio in unlicensed spectrum. Sensors send small messages to a gateway that may be kilometres away.
- Strengths. Batteries last years. One gateway covers a wide area. Devices are inexpensive and many types are available. You own the network.
- Limits. Very small messages, sent infrequently. Range falls sharply under dense canopy and behind hills. Not suitable for images or fast control.
- Practical notes. Antenna height matters more than transmit power: a gateway on a tower or a hilltop transforms coverage. Use the frequency plan permitted in your country, and check local regulations for the band.
For scattered sensors reporting small readings, this is usually the first candidate for the field link.
Option 2: private radio links
Point-to-point or point-to-multipoint links, including long-range wireless bridges.
- Strengths. High bandwidth over many kilometres with line of sight. Good for backhaul from a field gateway to the office, and for cameras.
- Limits. Needs a clear path, so towers or high ground. Needs power at both ends. Alignment and weather affect it.
Often the right answer for the backhaul: a bridge from the gateway's tower to an office that has internet.
Option 3: cellular, with help
Coverage maps describe a phone at ground level. A device with an external high-gain antenna on a mast can often find a usable signal where a phone shows none.
- Strengths. Simple, inexpensive, no infrastructure of your own. Low-power cellular variants designed for IoT, where operators offer them, give long battery life.
- Limits. Depends on the operator. Fringe signals come and go with weather and load.
- Practical notes. Survey with a test device and antenna at the actual mounting height. Try more than one operator. A multi-operator SIM helps at the edges.
Option 4: satellite
For sites nothing else reaches.
- Satellite IoT services. Small messages sent directly from a device or a gateway. Low power, small antennas, priced for small data. Suitable for a few readings a day from each point.
- Satellite broadband. A dish at one location providing ordinary internet. Suitable as backhaul for a gateway serving a whole site, and for everything else the site office needs.
- Limits. Per-message or monthly costs. A clear view of the sky. Power for broadband terminals. Licensing and availability differ by country, so confirm what is permitted and offered where you operate.
A common pattern: LoRaWAN across the estate, one gateway at the field office, satellite broadband as its backhaul.
Option 5: store and collect
Sometimes no continuous link is justified.
- Devices log readings to local memory.
- A person visits with a phone or tablet and downloads over short-range radio, or a vehicle fitted with a reader collects as it passes.
- Strengths. Lowest cost. Works anywhere.
- Limits. Data is days old. No alarms.
Suitable for slow-changing measurements used for analysis. Unsuitable for anything that needs a response.
Comparing them
| Option | Typical role | Data size | Power need | Running cost |
|---|---|---|---|---|
| LoRaWAN | Field link | Very small | Very low | Low |
| Private radio bridge | Backhaul | Large | Mains or solar | Low |
| Cellular with antenna | Either | Small to large | Low to moderate | Low to moderate |
| Satellite IoT | Either, remote points | Very small | Low | Per message |
| Satellite broadband | Backhaul | Large | Moderate | Monthly |
| Store and collect | Field link | Any | Very low | Labour |
Most remote deployments combine two or three.
Design for outages first
Whatever the radio, links at remote sites fail: rain, a flat battery, a fallen branch, an operator fault. The design that matters most is what happens then.
- Buffer at the device. Each sensor keeps recent readings with timestamps and sends them when the link returns.
- Buffer at the gateway. It stores everything received while the backhaul is down.
- Timestamps at the source. Data that arrives late must carry the time it was measured, not the time it arrived.
- Local action for critical cases. If a pump must stop when a tank is full, that logic lives on site. Never route a safety or control decision through a link that may be down.
- Know when you are blind. The system must show clearly that a device or gateway has gone quiet, and raise an alert. A flat line that is really a dead link is worse than no data.
A network that loses nothing during a two-day outage is more valuable than one with a slightly better signal.
Power is half the problem
A gateway needs continuous power, and remote sites often have none.
- Solar with battery, sized for the wettest month, not the average. Several consecutive overcast days are normal in the rainy season.
- Protection against lightning, moisture, insects and theft.
- Low-power design for sensors, so batteries are changed every few years, not every few months. Every site visit costs a day.
Survey before you buy
Coverage on paper and coverage on your land are different things.
- Walk or drive the site with a test gateway on a temporary mast and a handful of test devices.
- Record signal at every planned sensor location.
- Test backhaul at the planned gateway position: cellular with the actual antenna, or line of sight for a bridge.
- Repeat in bad weather if you can.
- Adjust gateway positions and heights, then decide how many gateways you need.
Two days of survey prevents months of chasing gaps after installation.
A phased start
- Pilot one block: a gateway and ten to twenty sensors of the types you need.
- Run it through a full rainy month. Watch battery levels, missed messages and outages.
- Fix what the pilot shows: antenna height, enclosure sealing, reporting interval.
- Expand block by block.
Estate-wide rollouts that skip the pilot usually repeat one mistake across hundreds of devices.
Common mistakes
- Choosing sensors before checking connectivity.
- Trusting the coverage map.
- Gateways mounted too low.
- No buffering, so every outage is a permanent gap.
- Control decisions that depend on the cloud.
- Solar sized for sunny weather.
- No alert when a device goes silent.
- Ignoring maintenance access. A device that needs a boat and a day to reach should need attention rarely.
We design connectivity for remote monitoring as part of IoT and Control Systems, starting with a site survey. If your sites are beyond the coverage map, contact us.
Summary
Treat the field link and the backhaul as separate choices, sized to how much data you send and how quickly it must arrive. LoRaWAN suits scattered low-power sensors, radio bridges and satellite broadband suit backhaul, cellular with a proper antenna reaches further than maps suggest, and satellite IoT serves isolated points. Buffer at device and gateway, keep control logic on site, alert on silence, size power for the worst month, and survey and pilot before rolling out.
Frequently asked questions
Can IoT work without mobile coverage?
Yes. Sensors can report over long-range low-power radio to a gateway several kilometres away, and the gateway can send the data onward through whatever link reaches the site: a cellular signal on a hilltop, a radio bridge to the office, or satellite. Where no link exists, devices store data until it can be collected.
How far can LoRaWAN reach?
Range depends heavily on terrain, antenna height and vegetation. In open country with a well-placed gateway, several kilometres to more than ten is achievable. Dense tree cover and hills reduce it considerably. A site survey with test devices is the only reliable way to know the coverage on your land.
Is satellite IoT affordable for small data?
For small, infrequent messages, such as a tank level a few times a day, satellite services aimed at IoT are far cheaper than broadband satellite, though pricing varies by provider and region. It becomes costly when sending frequent readings or large payloads. It suits sites where nothing else reaches.
Related service
WhatsApp AI Chatbot
We build, train, and run a WhatsApp AI agent that answers customers 24/7, qualifies leads, and follows up.
