OTA Updates

Upswift provides a reliable and easy-to-use tool for deploying OTA updates on Linux based edge devices.

Deploying OTA Updates via Upswift

Upswift enables deploying OTA updates to remote devices swiftly and intuitively using the Updates tool.

The Updates tool is divided to 2 sections - Update Flows and Deployments. In order to deploy an OTA update you will need to create an Update Flow. After creating an Update Flow you can deploy that Flow to your devices by creating a "New Deployment".

For more information regarding each section:

pageUpdate FlowpageUpdate Deployment

Deployment best practice

To deploy an OTA update in a stable reliable way, make sure to have a few groups that are separated to: Test group - devices that are in your development lab and are similar to the devices that are in production. Production groups - from one to unlimited groups that include the deployed devices by location, product type, etc.

Update deployment best method: First, deploy the OTA update on the Test group, make sure that everything worked as expected, and your lab devices running in the way they should after the software deployment you did.

Then, Deploy the same update on the needed production group by going to the 'Recent updates' tab under the 'Updates' category, clicking on the 'Deploy to others' button and choosing the relevant production group to begin the deployment on.

Upswift OTA update methodology

By default, updates are being deployed in the order they were sent. In case the device is offline by the time the update was sent, the updates will roll out in the right order when the device gets back online.

Last updated