Keeping scheduled tasks local when connectivity is poor
Baztech’s smart-farming experience includes Orange Pi Compute Module 4 applications at sites with limited 4G connectivity. In the described setup, schedules and application scripts run locally, with MQTT and a database on the Orange Pi.
Local execution allows the configured schedule to continue during an internet interruption while the local system remains operational. Once connectivity returns, the application sends the stored offline data to the server and synchronises configuration updates from the farming dashboard.
The application therefore needs to define both local behaviour and reconnection behaviour. A cloud dashboard alone does not determine what equipment should do while the connection is unavailable.
Specify the offline requirement
For a new project, identify the tasks that must run locally, expected outage duration, data-retention needs and the rules for applying updated settings. Also specify who operates the site and how changes are made when remote access is unavailable.
Questions about this integration
Will the schedule still run without internet?
The described application runs its configured schedule locally. Continued operation still depends on the local controller, power and connected equipment.
What happens to data collected while offline?
In this application, it is stored locally and transferred to the server after connectivity returns. Storage capacity and synchronisation behaviour should be specified for each deployment.