If you set the Verify Update Package? parameter to Yes when you add an update package, you must verify the update package on tested devices before you perform a batch update. The update package can be pushed to devices for an over-the-air (OTA) update only after tested devices are properly updated. This article describes how to verify an update package in the IoT Platform console.


An update package is added. For more information, see Add an update package.


  1. Log on to the IoT Platform console.
  2. In the left-side navigation pane, choose Maintenance > OTA Update.
    Note To provide better services, IoT Platform improves the OTA update feature and adds statistics on update package versions. When you use the new OTA update feature in the console for the first time, you must associate the uploaded update packages with products. You can associate an update package with only one product. For more information about how to associate update packages with products, see the instructions in the console.
  3. On the Update Packages tab, find the update package that you want to verify and click Verify in the Actions column. In the Verify Update Package dialog box, set the parameters as required and click OK to verify the update package on one or more devices.
    Parameter Description
    Version number to be upgraded
    • If you perform a full update, this parameter is optional.

      The drop-down list displays the OTA module versions of all devices in the current product, except for the version to be updated to. You can select one or more versions. After you select the required versions, the related devices are added to the Device to be verified list as candidate devices.

      If you do not set this parameter, no limit is set on the version number for the OTA module of the devices to be verified.

    • If you perform a differential update, the value of this parameter is the version number that you specify when you add the update package.
    Device to be verified Select one or more devices to be verified.
    Device upgrade time-out (minutes) The timeout period of the update. If a specified device has not been updated within this period, the update times out. Valid values: 1 to 1440. Unit: minutes.

    If you perform an OTA update by using the update package for the first time, we recommend that you set this parameter to its maximum value. This increases the success rate of the update. The console suggests to you an appropriate value for this parameter based on update records.

    • The update period starts from the first time the specified device submits the update progress.

      During the update, the update package may be repeatedly pushed to the specified device because the device goes online and offline multiple times. However, the start time of the update period does not change.

    • After the device is updated, the device must submit the updated version number as soon as possible. Otherwise, the update may fail due to a timeout.

    Assume that you set the timeout period to 60 minutes and the device first submits the update progress at 10:00. In this case, if the device does not submit the updated version number before 11:00, the update fails due to a timeout.


In the Verify Update Package dialog box, click Close.

On the Update Packages tab, find the update package that is in the Verifying state and click View in the Actions column. On the Update Package Information tab, you can view the verification progress.

Verification Progress

What to do next

After tested devices are updated and the status of the update package is displayed as Verified, you can perform a batch update. For more information, see Initiate a batch update task.

Related API operations

Operation Description
CreateOTAVerifyJob Creates a verification task for an update package.
QueryOTAFirmware Queries the details of an update package.

For more information about API operations related to the OTA update feature, see API operations for OTA updates.