Batch Upgrading Firmware


After verifying the OTA process successfully, you can create a batch upgrade job, specify the upgrade strategy and method, and start pushing upgrade messages to devices.

EnOS supports the following upgrade strategies:

  • Cloud Push Upgrade: The cloud maintains a list of devices to be upgraded based on the upgrade strategy, pushing upgrade requests to devices sequentially. Devices accept the request and start upgrading when online; if offline, they accept the request upon reconnection.

  • Device Request Upgrade: The cloud maintains a list of devices to be upgraded. After a device proactively requests an upgrade, the cloud determines if it is within the upgrade scope. If so, it pushes the available firmware version, and the device starts upgrading after confirmation.


EnOS provides the following two upgrade methods, allowing you to choose the appropriate method based on your business needs:

  • Specified Device Upgrade: Suitable for small-scale or specific device upgrade operations.

  • Create OTA Job: Suitable for batch upgrades or scenarios requiring flexible configuration of upgrade scope and strategies.

Prerequisites


  • Ensure you have completed Verifying Firmware Upgrade Process.

  • Ensure that you have the device firmware version and deviceKey information.

  • Ensure that you have obtained the Developer role to have the access to Application Portal > Developer Console. If not, contact your OU administrator.

Upgrading Specified Devices


  1. Select Operation Monitoring > Firmware Management.

  2. Select a firmware with the status Verified or No Need, and click the View Details view button to enter the firmware details page.

  3. Click Verification > Upgrade Device in the upper right corner.

  4. Fill in the relevant information on the page:

Click to view OTA upgrade job configuration details

“Upgrade Scope” page, where you can specify the range of devices to be upgraded.

“Upgrade Strategy” page:

  • Maximum Task Concurrency: Set the maximum number of tasks running simultaneously. Only devices in the Pending and Pushed states are counted, excluding those in the Upgrading status.
  • Upgrade Timeout: Set the timeout duration for the verification tasks. If the device does not return a verification result (success or failure) within this time, the task will fail; otherwise, the device will enter the Pending list.
  • Retry Failed Tasks: Choose whether to automatically retry failed tasks.
    • Retry Interval: Options include 0 minutes (immediate), 10 minutes, 30 minutes, 1 hour, or 24 hours.
    • Max Retry Attempts: Options include 1, 2, or 5 times.
  • Schedule: Set the start and end date and time for the upgrade. EnOS only pushes upgrade requests within this window. If the start time is earlier than the current time, the upgrade executes immediately.
    • Repeat Every Day: Disabled by default; can be enabled only when the start and end dates are the same. When enabled, the OTA task is repeated daily within the specified time period. For example, setting a time window from 2025-03-21 09:00 to 2025-03-21 17:00 with daily repeat enabled will execute the task daily from 09:00 to 17:00.
  • Enable Upon Device Request Upgrade: When enabled, if the current number of concurrent tasks is less than the maximum task concurrency, the OTA task will start immediately.
  • Start Job Upon Creation: When enabled, the task starts immediately upon clicking OK.

5. Click OK to complete the job creation.

Create an OTA Job


  1. Access the feature through one of the following methods:

    • In EnOS Application Portal’s Developer Console, select Operation Monitoring > OTA Jobs, then choose New Job.

    • In the EnOS Application Portal’s Developer Console, select Operation Monitoring > Firmware Management. From the firmware list, select a firmware marked as Verified or No need, click the View Details view button, and in the top-right corner, select Verification > Create New Job.

  2. Fill in the relevant information on the page:

Click to view OTA upgrade job configuration details

“Basic Information” page:

  • Job Name: Enter the name of the OTA upgrade job.
  • Firmware Name: The name of the firmware to be upgraded.
  • Product: Automatically populated with the product associated with the firmware; if none is associated, it remains empty.
  • Type: The system automatically determines whether it is Upgrade or Verification based on the firmware status. For firmware marked as Verified or No need, it defaults to Upgrade.
  • Upgrade Method:
    • Snapshot: Uses a fixed set of eligible devices at the time of task creation; only these devices are upgraded, and newly added devices are excluded.
    • Incremental: Uses an open set of eligible devices; newly added devices that meet the criteria are included in the upgrade scope.

“Upgrade Scope” page: Specify the devices to be upgraded:

  • All Devices: Upgrade all devices for the selected firmware version.
  • Target Devices: Select individual devices.
  • By Attribute: Upgrade devices with attribute names and values within the specified range for the selected version.
  • By Device Tag: Upgrade devices with tags within the specified range for the selected version.
  • By Asset Tree: Click Select Asset Tree to select devices based on the root or parent nodes within the OU (root or parent nodes that are devices are also included). Child node devices must be specified by DeviceKey, with a maximum of 5 asset trees selectable.

“Upgrade Strategy” page:

  • Maximum Task Concurrency: Set the maximum number of tasks running simultaneously. Only devices in Pending Push or Pushed status are counted, excluding those in Upgrading status.
  • Upgrade Timeout: Set the timeout period for verification tasks. If a device does not return a verification result (success or failure) within this period, the task fails; otherwise, the device is added to the Pending Push list.
  • Retry Failed Tasks: Choose whether to automatically retry failed tasks.
    • Retry Interval: Options include 0 minutes (immediate), 10 minutes, 30 minutes, 1 hour, or 24 hours.
    • Max Retry Attempts: Options include 1, 2, or 5 retries.
  • Schedule: Set the start and end date/time for the upgrade. EnOS only pushes upgrade requests within this window. If the start time is earlier than the current time, the upgrade begins immediately.
    • Repeat Every Day: Disabled by default; can be enabled only when the start and end dates are the same. When enabled, the OTA task is repeated daily within the specified time period. For example, setting a time window from 2025-03-21 09:00 to 2025-03-21 17:00 with daily repeat enabled will execute the task daily from 09:00 to 17:00.
  • Enable Upon Device Request Upgrade: When enabled, if the current number of concurrent tasks is below the maximum concurrency limit, the OTA task starts immediately.
  • Start Job Upon Creation: When enabled, the task begins immediately upon clicking Confirm.

3. Click OK to complete task creation.

Result


  • Upon successful creation, in the Operation Monitoring > Firmware Management firmware details page, you can view the upgrade status from two perspectives: Devices or Jobs.

    • The Device List displays all records of device verification and upgrades for the firmware.

    • The Job List is identical to the Operation Monitoring > OTA Jobs page.

  • If you enabled Start Job Upon Creation during task setup, the task will start immediately. Alternatively, you can manually start the task from the Operation Monitoring > OTA Jobs page.

  • In Operation Monitoring > OTA Jobs, click View Details to view task progress.


Note

Developers need to independently verify whether the device functions normally after the firmware upgrade.

Next Steps