Arable Mobile 4.10.0 Release Notes

Doc Number: ARA2023-00022 Rev A / Date: Nov 28, 2023

Release Overview

The Arable Mobile 4.10.0 release is focused on making your operations more efficient, your user experience more delightful, and your device fleet management more seamless. In this release, we have expanded the Spray Timing forecast period to 7-days. For Vision subscribers, the Vision page has been updated to make it easier to locate current and historical images. Alerts settings have been updated. The tilt alert has 15 degrees as the default threshold and the inactive device alert is now requesting the user to check the device status.

We hope you will enjoy this new release. We always welcome your feedback through Customer Success (support@arable.com) or via your account manager. 

Change Log

New Features

• Arable Mobile 4.10.0 will allow you to optimize your spray schedule with an expanded forecast window as the forecast period has been expanded from 24 hours to 7 days. In the Map or Multi-site view, the Spray Timing Count Down now has an extended open/closed window assessment up to 7-days with an hourly expansion modal showing the next seven days of hourly forecast with open/closed window labelling and the expansion of the rainfall modal to show 7-days of hourly forecast along with performance improvements to the Spray Timing feature. 
• For Vision, the date filters (10 days, 30 days) have been removed. Now users will only be able to select between “All Images” and “Archived Images” for easier navigating and reduced risk of not seeing historical images. 
• Arable Mobile now retains language preference in the Arable database. Users can now ‘Save’ their language preference from the list of available languages from the ‘Settings’ section and the change will be maintained in the database for later and offline use. 

Defect Fixes

• The Mobile Map now goes to the current location of the user when loading and displays the nearest site to the user’s current location.
• The wind direction arrow has been corrected throughout the application so it points towards where the wind is blowing to. 
• Alerts settings have been updated. The tilt alert has 15 degrees as the default threshold. 
• The inactive device alert is now requesting the user to check the device status.

Known Issues

• In the Multi-site View, the Last Irrigation Runtime is displaying the hours for the last irrigation event that took place. If a given day had multiple irrigated events, the display would only be the most recent one, not the aggregation for the day.
• For Irrigation events, if a flow rate was improperly configured there is no way to go back and correct previous readings with a new flow rate to reflect accurate applied irrigation measurements. 
• The local Mark max/min temperature for the hour is taken as the max/min of all 5-min interval readings during that hour. Meanwhile, the current temperature is the average for the last hour, creating a discrepancy between the two values during weather alerts. We are investigating whether relying on a 5-min interval for Tmin/Tmax is vulnerable to noise, and if so, will change this algorithm.
• Terms & Conditions are e-mailed in English, regardless of what language is registered. A link to alternative languages is provided in the email. 
• The alerts in the My Alerts log are shown in English even if another language is selected in Arable Mobile. 
• Push notifications are presented based on the language configured on the phone and not the language set in Arable Mobile. 

• When clicking on a notification, the app will navigate to either the Heat Spikes or Frost Events screens, but won’t open the hourly records to point out the current-hour row. 

• Alert Message should be tailored for undeploy (dormant).
• Mobile Login works even if the User Active checkbox is unchecked in Arable AppAdmin. The mobile app will throw an error while the user is accepting terms and conditions.
• The summary page is showing average wind speed for the day. We are reviewing to change this to the latest hour in an upcoming release. 
• The logic for calculating the daily Tdew from hourly values in the Frost Event page is not always correct. This will be targeted to be fixed in the next release.