Verifying Firmware Upgrade Process


After a new firmware is added, you should select a few devices to verify the OTA process to reduce bricking the devices caused by wrong firmware.

EnOS provides two methods to verify the OTA process, allowing you to choose the appropriate method based on your business scenario:

  • Specified Device Verification: Suitable for small-scale firmware testing scenarios. If you are a developer who has just created a new firmware, it is recommended to first use Specified Device Verification to select a small number of devices (1-5 units) for testing to ensure the firmware is error-free. After successful verification, you can proceed with Create OTA Job for larger-scale validation or direct batch upgrades.

  • Create OTA Job: Suitable for scenarios requiring batch validation or upgrades. If you are already confident in the firmware or need to validate/upgrade multiple devices, using Create OTA Job directly is more efficient.


Note

EnOS only provides the message channels for verification. Developers will need to verify whether the firmware can be pushed to the device and whether the upgrading process is finished successfully and the device can function properly.

Prerequisites


  • Ensure that you have completed Adding Firmware in the Cloud.

  • 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.

  • Ensure that you have read the limitations for firmware. See Limitations.

Specified Device Verification


  1. In the Developer Console of EnOS Application Portal, select Operation Monitoring > Firmware Management.

  2. In the list, select a firmware with the status Not verified, and click its corresponding View Details view button to enter the firmware details page.

  3. Select Verification > Verify Device in the upper right corner.

  4. Fill in the required information on the page.

Click to view OTA verification task configuration details

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

“Upgrade Strategy” page:

  • Upgrade Timeout: Set the timeout duration for the verification task. 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 Push list.
  • Start Upon Creation: When enabled, the task starts immediately upon clicking OK.

5. Click OK to complete the job creation.

Create OTA Job


  1. Choose any of the following methods to access the feature entry:

    • In the developer console of EnOS Application Portal, select Operations Monitoring > OTA Upgrade, and then choose Create Job.

    • In the developer console of EnOS Application Portal, select Operations Monitoring > Firmware Management. In the firmware list, select an Unverified firmware, click the View view button, and then choose Verify > Create OTA Job in the upper right corner.

  2. Fill in the relevant information on the page.

Click to view OTA verification job configuration details

“Basic Information” page:

  • Job Name: Enter the name of the OTA verification job.
  • Firmware Name: The name of the firmware to be verified.
  • Product: Automatically populated with the product associated with the firmware; if no product is associated, it remains empty.
  • Type: The system automatically determines it as Upgrade or Verification based on the firmware status. The Verification type can only be selected when the firmware status is Unverified.

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

  • All Devices: Upgrade all devices of the selected version.
  • Specify Devices: Select specific devices.
  • Specify Device Attribute Values: Upgrade devices of a specific version whose attribute names and values fall within the specified range.
  • Specify Device Tag Values: Upgrade devices of a specific version whose tags fall within the specified range.
  • Specify Asset Tree: Click Add Asset Tree to select devices based on the root node and parent nodes within the OU (root or parent nodes that are devices are also included in the upgrade scope). Devices at the lowest child nodes must be specified by DeviceKey, with a maximum of 5 asset trees selectable.

“Upgrade Strategy” page:

  • Upgrade Timeout: Set the timeout duration for the verification task. 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 Push list.
  • Start Upon Creation: When enabled, the task starts immediately upon clicking OK.

3. Click OK to complete the job creation.

Results


  • After successful creation, on the firmware details page under Operation Monitoring > Firmware Management, you can view the verification status from two different perspectives: Device List or Job List.

    • Device List will display all records of devices verifying and upgrading to this firmware.

    • Job List is the same as the Operation Monitoring > OTA Jobs page.

  • If you enabled Start Upon Creation when creating the job, the job will start immediately. Alternatively, you can go to the Operation Monitoring > OTA Jobs page to manually start the job.

  • In OTA Jobs, click Details to enter the job details page, where you can view the job progress. For more information, see Viewing Upgrade Details.


Note

After a device firmware upgrade, whether its functions are available needs to be verified by the developer based on the device’s condition.

Next Steps


Batch Upgrading Firmware