Guide · LoRa sensor monitoring
Monitoring a farm with no mobile coverage: how LoRa sensor nodes actually work.
The tank you most need to watch is the one three ridges away with no phone signal. Cellular sensors want a SIM, a monthly fee and coverage you haven't got; WiFi dies somewhere around the house-yard fence. LoRa is the technology built for exactly this gap, and this page explains how a working system fits together: what the sensor nodes do, what the gateway does, and why a few bytes can cross kilometres of paddock that defeat everything else.
Last reviewed: 18 July 2026 · by Rural IoT
The short version, then the detail
LoRa monitoring splits the job in three: battery nodes in the paddock that wake, read, transmit a few bytes and sleep; one gateway at the homestead that hears them all and forwards readings over your existing internet; and a dashboard that alerts you. Tiny slow messages at 915 MHz cross kilometres that kill WiFi, which is the deliberate trade: data by the byte, not the megabyte. Wondering what monitoring is worth doing at all? Start with the farm monitoring guide, then come back here for how it works.
The chain: node, gateway, dashboard
A LoRa monitoring system has three parts, and only one of them needs internet.
Sensor nodes
Out in the paddock: on the tank, in the soil, on the gate. Each is a small battery-powered box with a sensor and a low-power radio. It spends nearly all its life asleep. On a schedule, every ten minutes, every hour, whatever the job needs, it wakes, takes a reading, transmits a few bytes, and goes back to sleep. Total awake time per day: a few seconds.
One gateway
At the homestead, or wherever your internet connection is. It listens continuously for those transmissions and forwards each one over your normal connection: NBN, Starlink, fixed wireless, anything. One gateway serves every node on the property; you don't add infrastructure per sensor.
The dashboard
Wherever the readings end up: a phone app, a web page, an alert that fires when the tank drops below a quarter. This part runs on ordinary internet plumbing. All the rural-specific magic happened before the data reached the gateway.
The nodes never touch the internet, never need a SIM, and never need coverage. They only need to reach your gateway.
Why a few bytes travel kilometres where WiFi dies at the fence
WiFi and LoRa make opposite bets. WiFi moves millions of bytes a second, and pays for it in range. Streaming video needs a wide, fast channel, and wide fast channels need strong signal. A shed wall or a few hundred metres of air and the link is gone.
LoRa moves a handful of bytes and spends everything else on distance. Three things stack up.
Slow, stubborn transmission. LoRa spreads each message out in time using a chirp scheme the receiver can pick out from below the background noise. A signal too weak for WiFi to detect at all is still readable LoRa.
Lower frequency. LoRa in Australia uses the 915 MHz band, which bends around terrain and pushes through trees far better than WiFi's 2.4 and 5 GHz.
Tiny payloads. A tank level is a couple of bytes. A soil moisture reading with temperature is a handful more. Small messages tolerate slow links, and slow links reach a long way.
The trade is absolute: you cannot stream video, browse, or even fetch a web page over LoRa. A node sends readings the size of a text message a few dozen times a day. For monitoring, that's the whole job, and it's why a coin-sized radio on AA-class batteries reaches paddocks that a mains-powered WiFi access point never will.
Real-world reach depends on terrain. Line of sight from a high-mounted gateway antenna, several kilometres is routine and more is common. Over a ridge or through heavy timber it shrinks, which is why gateway placement (high, clear) matters more than any spec sheet number.
What runs for months on batteries, and what needs solar
The wake–report–sleep pattern is what makes battery life work. A node that sleeps at microamps and transmits for under a second per report barely touches its battery. Rough sorting from our bench and field experience:
Runs for months to years on primary batteries: tank level senders, soil moisture probes, gate and door sensors, rain gauges, temperature and humidity nodes. Anything that wakes, reads, transmits and sleeps. Report interval is the main lever: a node reporting every ten minutes uses many times the energy of one reporting hourly, so match the interval to the decision you'll make with the data. Nobody acts on tank level ten minutes faster.
Needs solar or mains: the gateway, because it listens all the time. Receiving continuously costs more than transmitting rarely, and it also needs to run your internet uplink. Likewise anything that can't sleep: a node doing continuous logging or frequent GPS fixes, or any repeater. If a device must be awake to do its job, budget for a panel and a battery.
The design rule that falls out: put the always-on parts where power already exists, and let the paddock devices be the sleepy ones.
What this looks like in practice
A typical small setup on a property with no coverage past the house: one gateway on the homestead roof using the existing internet, a tank sensor two kilometres out, two soil moisture probes, and a gate sensor on the road entrance. Total mains power points needed beyond the homestead: zero. Batteries changed: roughly once a year, on a calendar reminder, checked against the battery voltage each node reports alongside its readings. The system tells you before a node dies.
The platform economics work the same way as the radio: one gateway and one dashboard carry every sensor you add after them, which is covered properly in one platform, many uses.
If your problem is the other one, getting internet, cameras or WiFi out to sheds and yards across the property, that's a farm networking job, not a sensor job, and different gear does it: that's what Paddock Networks is for. The sensor layer described here rides on whatever internet connection the homestead already has.
General guidance from field experience: terrain, mounting and report intervals change every number here.
Eyes on the paddock with no bars.
Tell us what you need to watch and how far out it is. We will come back with a node and gateway plan and a price, no pressure, no jargon.
Get a quote