Remote water and irrigation control
Smart Irrigation SIM Cards
Connect irrigation controllers, pumps, tanks and field sensors where fixed internet is unavailable or impractical.
In brief
A smart irrigation SIM links remote controllers and gateways to monitoring or automation software. Good design balances rural coverage, antenna placement, low-power operation, seasonal inactivity and the safety of remote commands.
What you can connect
- Parks and sports-field irrigation
- Agricultural pumps and valves
- Tank, flow and pressure monitoring
- Remote sprinkler and landscape controllers
Connectivity is only one part of reliability
Rural coverage maps do not account for terrain, enclosures or low-mounted antennas.
A dormant seasonal device may still require health checks, secure updates and lifecycle control.
Remote actuation needs local fail-safe behaviour when connectivity or cloud services are unavailable.
Technical planning
Design the complete connection
Architecture
The cellular device may sit in each controller or in a gateway serving local valves and sensors. Local schedules, manual override and safe valve states must continue when the cloud or link is unavailable. Rural terrain, low mounting and metal pump cabinets often matter more than a carrier coverage-map colour.
Data and power sizing
Combine sensor reports, controller polling, commands, weather data and health checks, then reserve a separate allowance for firmware. For battery or solar sites, measure radio attach time and failed retries as well as bytes. Seasonal suspension must still allow planned health and security activity.
Solution design
What we qualify before recommending a SIM
Coverage maps and headline data allowances are a starting point. A production design needs the device, traffic, locations and operating model.
- Controller/modem compatibility and supported bands
- Site coordinates, terrain and external antenna options
- Telemetry interval and command frequency
- Sleep cycle, solar and battery constraints
- Local manual override and fail-safe rules
- Seasonal activation, alerts and cost model
Multi-provider by design
Choose Onomondo, Telnyx or another fit
Onomondo can fit low-data seasonal estates where pay-for-use economics, network choice and remote diagnostics matter. Telnyx can fit router-based controllers needing explicit traffic policies or API automation. Radio technology support such as LTE-M or NB-IoT must be validated per country and network.
Onomondo can fit low-data seasonal fleets where network choice, diagnostics and active-use economics matter. Telnyx can fit router-based controllers needing API lifecycle control or traffic policies. LTE-M, NB-IoT and Cat-1 support must be checked for each device, country and available network.
Availability note: networks, radio technologies, IP features, regions and platform controls vary by provider, country and plan. We verify the proposed configuration during the pilot.
Primary product sources reviewed 26 July 2026:
What the pilot should prove
- Test low points, pump sheds and external antenna options.
- Measure attach energy, sleep current and several command cycles.
- Disconnect cloud and cellular paths to confirm local fail-safe behaviour.
- Model active season, dormant season and firmware-update usage.
Discover
Confirm devices, sites, traffic, security, support and commercial constraints.
Pilot
Test representative hardware and locations, then measure attachment, usage and recovery.
Scale
Document the approved profile, alerts, ownership and rollout or rollback process.
Frequently asked questions
How much data does an irrigation controller use?
Simple telemetry and commands may be modest, but polling, firmware, weather integrations and retries add overhead. Pilot the real controller and protocol.
Will it work in a rural pump shed?
It may, with the right network, modem bands and antenna placement. We recommend testing at the cabinet with doors closed and equipment operating.
Can devices be inactive outside the growing season?
SIM lifecycle and charging rules vary. The device may still need periodic health checks and security updates, so seasonal policy should be deliberate.
Is NB-IoT always the best choice?
No. NB-IoT can suit stationary low-data devices, but availability, roaming, latency and module support vary. LTE-M or Cat-1 may be better for some controllers.
Can connectivity prevent over-watering?
Connectivity carries data and commands; sensors, control logic, valve condition and local fail-safes determine the operational result.
Prove the connection before you scale it.
Tell us what you are connecting, where it operates and what must happen when coverage changes. We will shape a representative iSIM pilot.