Operating System Updates


EDGEHOG OS based on Yocto Linux is the Operating System optimized for the SECO IoT Gateways.
Every time a new version of the OS is released, the user can check the update status of his devices from the Dashboard and from the Software Update dedicated sections.
Different update campaigns can be created for each release, deciding which and how many devices must be updated in each campaign, filtering them, for example, by Models or Tags. For example, you can decide to update only some devices that are in a test lab or only those in certain geographical areas.

Operating System Update Management

In the side navigation menu click on Device Update Status.
In this overview an Update Status of every Device is available. You can check the OS version of each device and see which one needs to be updated.

Operating System Campaign list

In the side navigation menu click on Update Campaigns List.
For all new releases on the OS, you can create different Update Campaign.
In this section a list of all created campaigns and their status is available.
Here it’s possible to select a single campaign clicking on the appropriate info icon. Once the campaign is selected the Campaign Recap page is going to open.

Create Update Campaign

In this section, you can create an update campaign by deciding which of the devices should be updated, filtering them by Tags, for example.
The table on the right of the page is updated with the number of gateways that can be updated as information is selected and added in the filter fields on the left.
As you select and add information in the filter fields on the left, the table on the right of the page is updated with the number and specifications of the gateways that OS can be updated to.
You can filter the boards that need to be updated by selecting:
  • Operating System: The operating system for which a new version is available
  • Name: The name to give to the update campaign. Useful as a reference to be searched for later
  • Tags: Through the tags, you can filter the devices of the fleet to which the campaign should arrive.
    You can filter devices by device tags or tags inherited from the assigned model.
Other parameters that can be selected are:
  • Rollout Rate: Specifies the maximum number of devices that will be informed of the update per minute.
  • Execution Timeout: Specifies the maximum amount of time (in minutes) a device should take to install the update.
If the operation on the individual device is not completed (with success or error) before the end of the Execution Timeout, the campaign will report the Timeout status on that device. The server will no longer wait for a response from the device, which may continue operations in the background and complete them successfully despite the online interface reports the Timeout.
Once you have filtered the right devices to update you can create the update campaign by clicking on the button. You will be redirected to the status page of the update campaign to see the status of each device being updated.

Release History

In the side navigation menu click on Release History.
In this section a list of all issued Releases is available. The following information about each release is available.
  • Version number;
  • Release Date;
  • Dimension;
  • Release changelog.
Copy link
On this page
Operating System Update Management
Operating System Campaign list
Create Update Campaign
Release History