Why solar is the obvious answer for remote sites
Boreholes, reservoirs, river gauges, weather stations, remote tanks and paddock sensors share a problem: they're where you need data but where grid power is far away, expensive to bring in, or simply absent. Trenching a cable to a remote borehole can cost more than the entire monitoring system. And where there is grid power, load shedding takes it away on a schedule.
Solar sidesteps both. At the power levels a monitoring node needs, you're not running a pump or a building — just a little electronics — and the sun delivers that almost anywhere in South Africa, one of the sunniest countries on earth. No connection fee, no cable, no power bill, no load-shedding gap.
The scale that makes it easy: a monitoring node sips power — think a handful of watt-hours a day, not the kilowatt-hours a pump or a home needs. That's why a panel and battery you could carry in one hand can keep it running for years.
What a solar monitoring node contains
- Low-power sensors — level, flow, pressure, soil-moisture, weather — chosen to sleep between readings.
- An edge device that wakes, reads, buffers and transmits, then sleeps again to save power.
- A long-range, low-power radio — LoRaWAN or NB-IoT — which sends small data packets over kilometres on minimal energy (see our connectivity guide).
- A solar panel and battery sized for the node and the local sun.
How to size it (so it survives cloudy weeks)
- Estimate daily energy use. Add up what the node consumes per day — mostly driven by how often it reads and transmits. Reporting every 15 minutes uses far more than every few hours; match the interval to what the decision actually needs.
- Size the battery for autonomy. Choose a battery that can run the node for several days with no sun — enough to ride out a cloudy spell. Days of autonomy, not hours, is what makes a remote node reliable.
- Size the panel for the worst day, not the best. The panel must fully recharge the battery on a short, overcast winter day, not just a bright summer one. Sizing to the best case is the classic mistake that leaves a node dead in July.
- Add margin and the right battery chemistry. Allow headroom for ageing and dust on the panel, and pick a battery suited to outdoor temperature swings.
- Buffer data at the edge. If the radio link drops, the node stores readings and forwards them when it reconnects — so a connectivity gap never becomes a data gap (the same principle in our load-shedding guide).
The discipline is simple: size for the worst week, not the average. A node sized to survive a cloudy winter spell will run for years; one sized to summer averages will fail exactly when the weather turns.
What it unlocks
Off-grid solar monitoring turns places you previously visited in person into places that report themselves. A borehole that texts you its water level and pump status. A reservoir that alerts on a sudden drop. A weather station that feeds your irrigation scheduling. A remote tank you no longer drive out to check. Fewer site visits, faster response, and a continuous record — with no grid and no Eskom dependency.
This is how addanode powers remote sensing across our water, irrigation and livestock solutions on one addaNet platform. Because we build both the hardware and the software in-house and support it locally, we size the solar, battery and reporting interval together for your site and your sun — so a remote node reports reliably for years, engineered for South African conditions rather than guessed at.
Frequently asked questions
Can solar really run IoT monitoring with no grid power?
Yes. A monitoring node — edge device, low-power sensors and a long-range radio — draws only a few watt-hours a day, so a small solar panel and battery run it indefinitely, completely off-grid. There's no grid connection to install and no load shedding to survive, which makes solar the natural choice for remote sites.
What happens during a long cloudy spell?
A properly sized node keeps running because the battery is sized for several days of autonomy and the panel is sized to recharge on a short, overcast winter day rather than a bright summer one. Sizing for the worst week instead of the average is exactly what lets a remote node ride out cloudy weather.
How big a panel and battery do I need?
It depends on the node's daily energy use, which is driven mainly by how often it reads and transmits. Reporting every few hours needs far less than every 15 minutes. You size the battery for days of autonomy and the panel to recharge it on a poor-sun day — both calculated from your reporting interval and site, not guessed.
What can I monitor this way?
Anything remote and low-power: borehole and reservoir levels, pump status, flow and pressure, river gauges, weather stations, soil moisture, remote tanks and livestock read points. The node reports over LoRaWAN or NB-IoT, so distance from the grid and from a tower isn't a barrier.
Is data lost if the signal drops at a remote site?
No. The edge device buffers readings locally and forwards them when the radio link returns, so a connectivity gap never becomes a data gap. Combined with solar power and days of battery autonomy, the node keeps both running and recording through outages and poor weather.