Australian agriculture has a structural problem for connected hardware: the land is enormous and the network is thin. A sensor that works perfectly on a demo farm near a town can go silent forty kilometres out. Designing for Australia means designing for absence — of signal, of grid power, of shade, and of anyone nearby to press reset.
Connectivity: plan for gaps, not coverage
Australia's 3G networks shut down in 2024. Anything still relying on 3G stopped working, which is a lesson in itself: connectivity choices outlive network decisions you don't control.
| Option |
Strengths |
Trade-offs |
| LTE-M / NB-IoT |
Low power, uses existing mobile infrastructure |
Coverage still patchy in remote areas |
| LoRaWAN |
Long range, very low power, private networks possible |
Needs gateways; low data rates |
| Satellite IoT |
Works almost anywhere |
Higher cost per message; small payloads |
| On-farm Wi-Fi or mesh |
High bandwidth near buildings |
Short range, needs power |
Most serious agtech systems combine two: a low-power local network on the property, backhauled by cellular or satellite from a gateway. LoRaWAN in Australia uses the AU915 frequency plan, so hardware and gateways need the right band configuration.
Offline-first by design
Whatever the network, assume it disappears.
- Make decisions locally. Irrigation valves, pump controllers and alarms must act on local sensor data and schedules, not cloud commands.
- Store and forward. Readings go into a persistent queue in flash and upload when a link exists. Size the queue for the longest outage you'll tolerate.
- Batch transmissions. Sending once an hour instead of once a minute saves power and airtime, especially over satellite.
- Keep good time offline. Use a real-time clock and correct drift when connectivity returns.
- Update safely. OTA over thin links needs resumable downloads, signed images and automatic rollback.
Our automated hydroponics system runs its watering and nutrient logic on local schedules and thresholds. Network loss doesn't stop the system. Open-field agriculture takes the same principle much further.
Power: solar, batteries and sleep
Remote devices rarely have grid power.
- Design the power budget first. Measure sleep current, wake time and transmit energy. A device that sleeps badly kills its battery in weeks.
- Size solar for winter and cloud, not summer averages.
- Protect batteries from heat. Lithium cells degrade fast at high temperature. Enclosure placement, shading and charge limits matter.
- Report battery health. Farmers need warning before a device dies, not after.
RCM compliance and the responsible supplier
Electronic products supplied in Australia generally need to meet ACMA requirements for electromagnetic compatibility and radiocommunications, and carry the Regulatory Compliance Mark, RCM.
Key points for overseas design teams:
- A responsible supplier must register on the national database before applying the RCM. Registration requires an Australian manufacturer, importer or an Australian agent acting for them — an overseas company can't register on its own.
- International test reports can often support compliance, which helps when you design to EU or US standards.
- Consumer smart devices face cybersecurity rules. Australia's smart device security rules, which took effect in March 2026, cover requirements like unique passwords. Check whether your product falls in scope; many farm-business products may not, but consumer-facing devices may.
- Mains-powered equipment may also fall under electrical safety rules with their own registration levels.
Plan your Australian distribution partner or entity alongside the hardware design. It decides who holds the compliance file.
Time zones and support
Australian Eastern time runs 4.5 hours ahead of India in winter and 5.5 hours ahead in summer. Perth sits 2.5 hours ahead. The Australian afternoon overlaps the Indian working morning, which works well for weekly reviews and field-trial debugging.