How Farmo Devices Process Data at Two Levels

Updated on
How Farmo Devices Process Data at Two Levels

How Farmo Devices Process Data at Two Levels

Farmo devices analyse data in two locations:

  1. On the device itself (Edge Processing)

  2. On the server after data upload (Server Analytics)



1. Edge Processing | Thresholds

When data is processed on the device, this is called edge processing.
The device evaluates each data point against a set of conditions (thresholds) to decide whether to:

  • Upload immediately (if conditions are met)

  • Wait until the next scheduled report

This approach improves responsiveness, reduces data transmission load, and extends battery life.

We call the set of conditions on the device “Thresholds”. With recent firmware updates, thresholds can be set over the air via the Farmo App.


2. Server Analytics | Trigger Levels

Once data is uploaded to the cloud, it is analysed against customer-defined trigger levels to determine if actions should be taken.

Example actions include:

  • Sending email or SMS alerts

  • Turning pumps on or off


Why Synchronising Thresholds and Trigger Levels Matters

For best performance, it’s important to understand the difference:

  • Thresholds = Device-side conditions that decide when data is sent.

  • Trigger Levels = Cloud-side conditions that decide when actions occur.

Sometimes these should be synchronised for optimal results.

Example:
If you want an SMS alert when your tank level drops to 40%:

  1. Set the Alert Trigger Level (server) to 40% and choose email/SMS recipients.

  2. Set the Device Threshold to 40% so data is uploaded immediately when this level is reached.

If these values aren’t aligned, the device might wait until the next scheduled (e.g. 8-hour) report to upload the reading—delaying your alert.


💡 Key takeaway:
Synchronising thresholds and trigger levels ensures alerts and actions happen exactly when they should, without unnecessary delays.

 

 

 

 

Updated on