Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- What's New
- Product Bulletin
- Service Overview
- Billing
-
Getting Started
-
Quick Device Access - Property Reporting and Command Receiving
- Subscribing to IoTDA
- Connecting a Smart Smoke Detector to the Platform (Quick Usage)
- Registering a Simulated Smart Street Light Device
- Using MQTT.fx to Simulate Communication Between the Smart Street Light and the Platform
- Using a Virtual Smart Street Light to Communicate with the Platform (Java SDK)
- Using a Virtual Smart Street Light to Communicate with the Platform (C SDK)
- Quick Device Access - Message Sending and Receiving
- Quick Application Access
-
Quick Device Access - Property Reporting and Command Receiving
-
User Guide
- Overview
- IoTDA Instances
- Resource Spaces
- Device Access
- Message Communications
- Device Management
-
Rules
- Overview
- Data Forwarding Process
- SQL Statements
- Connectivity Tests
- Data Forwarding to Huawei Cloud Services
- Data Forwarding to Third-Party Applications
- Data Forwarding Channel Details
- Data Forwarding Stack Policies
- Data Forwarding Flow Control Policies
- Abnormal Data Target
- Device Linkage
- Monitoring and O&M
- Granting Permissions Using IAM
-
Best Practices
- Introduction
-
Device Access
- Developing an MQTT-based Simulated Smart Street Light Online
- Developing a Smart Street Light Using NB-IoT BearPi
- Developing a Smart Smoke Detector Using NB-IoT BearPi
- Connecting and Debugging an NB-IoT Smart Street Light Using a Simulator
- Developing a Protocol Conversion Gateway for Access of Generic-Protocol Devices
- Connecting a Device That Uses the X.509 Certificate Based on MQTT.fx
- Connecting to IoTDA Based on the BearPi-HM_Nano Development Board and OpenHarmony 3.0
- Testing MQTT Performance Using JMeter
- Device Management
- Data Forwarding
- Device Linkage
-
Developer Guide
- Before You Start
- Obtaining Resources
- Product Development
- Development on the Device Side
- Development on the Application Side
-
API Reference
-
API Reference on the Application Side
- Before You Start
- Calling APIs
- API Overview
-
API
- Product Management
- Device Management
- Device Message
- Device Command APIs
- Device Property
- AMQP Queue Management
- Access Credential Management
- Data Forwarding Rule Management
-
Transition Data
- Push a Device Status Change Notification
- Push a Device Property Reporting Notification
- Push a Device Message Status Change Notification
- Push a Batch Task Status Change Notification
- Push a Device Message Reporting Notification
- Push a Device Addition Notification
- Push a Device Update Notification
- Push a Device Deletion Notification
- Push a Product Addition Notification
- Push a Product Update Notification
- Push a Product Deletion Notification
- Push an Asynchronous Device Command Status Change Notification
- Rule Management
- Device Shadow
- Group Management
- Tag Management
- Instance Management
- Resource Space Management
- Batch Task
- Device CA Certificate Management
- OTA Upgrade Package Management
- Message Broadcasting
- Device Tunnel Management
- Stack policy management
- Flow control policy management
- Device Proxy
- Device Policy Management
- Bridge Management
- Pre-provisioning Template Management
- Custom Authentication
- Codec Function Management
- Permissions and Supported Actions
- Examples
- Appendix
-
MQTT or MQTTS API Reference on the Device Side
- Before You Start
- Communication Modes
- Topics
- Device Connection Authentication
- Device Commands
- Device Messages
- Device Properties
-
Gateway and Child Device Management
- Platform Notifying a Gateway of New Child Device Connection
- Platform Notifying a Gateway of Child Device Deletion
- Gateway Synchronizing Child Device Information
- Gateway Updating Child Device Status
- Responding to a Request for Updating Child Device Statuses
- Gateway Requesting for Adding Child Devices
- Platform Responding to a Request for Adding Child Devices
- Gateway Requesting for Deleting Child Devices
- Platform Responding to a Request for Deleting Child Devices
- Software and Firmware Upgrade
- File Upload and Download
- Device Time Synchronization
- Device Reporting Information
- Device Log Collection
- Remote Configuration
- Device Tunnel Management
- HTTPS API Reference on the Device Side
- LwM2M API Reference on the Device Side
- Security Tunnel WebSocket API Reference
- Module AT Command Reference
- Change History
-
API Reference on the Application Side
- SDK Reference
-
FAQs
- Top FAQs
-
Solution Consulting
- In What Scenarios Can the IoT Platform Be Applied?
- What Are the Changes Brought by the Integration of IoT Device Management and IoTDA?
- Can I Enable IoTDA for IAM Users or Sub-Projects?
- Which Regions of Huawei Cloud Are Supported by the IoT Platform?
- Does Huawei Provide Modules, Hardware Devices, and Application Software?
- What Should I Do If I Want to Call an API But Have No Permissions to Do So as an IAM User? (Is It Edition-specific?)
- Why Was I Prompted to Grant Security Administrator Permissions When I Create a Rule or Set Resource File Storage?
- Which Resource Space Will Be Set As Default on the IoT Platform?
- How Does IoTDA Obtain Device Data?
- Is There Any Limitation on the Number of Resource Spaces and Devices I Can Add on the IoT Platform?
- Does the IoTDA Support Device Registration in Batches?
- Are There Any Limitations on the Use of the IoT Platform?
- What DTLS Encryption Algorithms Are Supported by the IoT Platform?
- Does the IoT Platform Support Conversion Between Big-Endian and Little-Endian for Binary Data?
- What Is NB-IoT?
- What Are the Components of the IoT Platform and What Hardware Architectures Does It Support?
- How Do I Obtain the Platform Access Address?
- Device Integration
- IoT Device SDKs
- LwM2M/CoAP Device Access
- MQTT-based Device Access
- Products Models
- Message Communications
- Subscription and Push
- Codecs
- OTA Upgrades
- Application Integration
- General Reference
- What Is a Software or Firmware Upgrade?
- Can the IoT Platform Download Software or Firmware Packages from Third-party Servers?
- Can the Target Version Be Earlier Than the Source Version?
- How Do I Obtain Software or Firmware Packages and Their Version Numbers?
- What Are Common Software or Firmware Upgrade Errors?
- What Should I Enter for the Source Versions When I Upload a Firmware Package on the IoTDA Console?
- Are Services Interrupted During a Software or Firmware Upgrade?
- How Can I Retry When Some Devices in the Group Fail to Be Upgraded?
- Is Resumable Transmission Supported When the IoT Platform Is Sending Software or Firmware Packages to the Devices?
- Why Does a Software/Firmware Upgrade Task Fail to Be Created When I Select Multiple Upgrade Packages?
- Which Devices Will Be Retried If I Click Retry All on the Task Details Page?
- Why Does a Device Fail to Download the Upgrade Package During the Upgrade?
- Why Does an Upgrade Package Fail to Be Downloaded After the Upgrade Result Is Reported?
- What Do I Do If a Device Upgrade Task Times Out?
Show all
Copied.
OTA Upgrades
What Is a Software or Firmware Upgrade?
A software upgrade refers to the upgrade of the system software and application software of the device. A firmware upgrade refers to the upgrade of the underlying drivers of the device hardware.
You can upload a software/firmware upgrade package to the IoTDA platform or use a file associated with an object on OBS for device remote upgrades.
Can the IoT Platform Download Software or Firmware Packages from Third-party Servers?
No. Currently, you can only use software/firmware packages uploaded to the IoT platform or associated with objects on OBS. To upload a software/firmware package, choose Devices > Software/Firmware Upgrades in the navigation pane, and go to the Software List or Firmware List tab page.
Can the Target Version Be Earlier Than the Source Version?
Yes. Software or firmware can be rolled back from a later version to an earlier version. The IoT platform checks whether the target version is the same as the source version. If they are consistent, the message "The current version is the same as the target version" is displayed, and the platform does not initiate a rollback or upgrade. If they are inconsistent, the platform starts a rollback or upgrade.
How Do I Obtain Software or Firmware Packages and Their Version Numbers?
Obtain the software package and its version number from the device manufacturer. Obtain the firmware package and its version number from the module manufacturer.
What Are Common Software or Firmware Upgrade Errors?
If an error occurs during upgrade, you can view the error messages on the Execution Details tab page. (To access this page, choose Software/Firmware Upgrades in the navigation pane of the IoTDA console, go to the upgrade task list, and click View in the row of a task.) Common error messages are as follows:
Error Message |
Description |
Recommendation |
---|---|---|
Device Abnormal is not online |
The device is not online. |
Check whether the device is online. |
Task Conflict |
A task conflict has occurred. |
Check whether there is an ongoing software or firmware upgrade for the current device. |
Waiting for the device online timeout |
The device did not go online within the specified time. |
Check whether the device is connected to the network. |
Waiting for report cellId timeout |
The device did not report the cell ID within the specified time. |
View the module logs to check whether the device has reported the cell ID. |
Waiting for report device firmware version timeout |
The device did not report the firmware version within the specified time. |
View the module logs to check whether the device has reported the firmware version. |
Wait for the device to report upgrade result timeout |
The device did not report the upgrade result within the specified time. |
View the module logs to check whether the device has reported the upgrade result. |
Updating timeout and query device version for check timeout |
The device did not report the upgrade result or device version within the specified time. |
View the module logs to check whether the device has reported the upgrade result and device version. |
Waiting for device downloaded package timeout |
The device did not download the firmware package within the specified time. |
View the module logs to check whether the device has downloaded the firmware package. |
Integrity check failure for new downloaded package |
The integrity check of the downloaded firmware package failed. |
View the module logs to check whether the downloaded firmware package is complete. |
Unsupported package type |
The firmware package type is not supported. |
View the module logs to check whether the device status and firmware package provided by the manufacturer are correct. |
Not enough storage for the new firmware package |
The storage space is insufficient for the firmware package. |
Check the storage space of the device. |
Out of memory during downloading process |
The memory was insufficient during the download. |
Check the device memory. |
Connection lost during downloading process |
The connection was interrupted during the download. |
Check the device connection status. |
Invalid URI |
The URI is invalid. |
Check whether the download address of the firmware package is correct. |
Firmware update failed |
The firmware failed to be upgraded. |
View the module logs to check the device firmware. |
What Should I Enter for the Source Versions When I Upload a Firmware Package on the IoTDA Console?

The source versions should include the current versions of devices whose firmware you want to upgrade. Otherwise, the upgrade is not allowed. To obtain the current version of a device, log in to the IoTDA console, choose Devices > All Devices in the navigation pane, and click View in the row of the target device.
Are Services Interrupted During a Software or Firmware Upgrade?
Yes. Services are interrupted during the upgrade. Services such as data reporting and property modification cannot be conducted during a module or chip upgrade.
How Can I Retry When Some Devices in the Group Fail to Be Upgraded?
If the entire task fails, only the failed subtasks are retried. The devices that have been successfully upgraded will not be upgraded again.
The retry interval and retry times can be configured for software upgrade, but only the retry times can be configured for firmware upgrade.
Is Resumable Transmission Supported When the IoT Platform Is Sending Software or Firmware Packages to the Devices?
Yes. Devices must record the fragment location of the software or firmware packages when the transmission is interrupted, so that package fragments that are not transmitted can be sent after the transmission is restored. If the device detects that the verification code of the upgrade package changes after the transmission is restored, the upgrade package is a new one. You need to clear the previous fragments and download the upgrade package again.
Why Does a Software/Firmware Upgrade Task Fail to Be Created When I Select Multiple Upgrade Packages?
The source versions supported by the selected upgrade package are duplicate, or the number of selected upgrade packages exceeds the upper limit. When creating an upgrade task, you can select up to 10 upgrade packages. Supported source versions of the upgrade packages must be unique. If no source version is specified for an upgrade package, the package can be used to upgrade devices of all source versions by default.
Which Devices Will Be Retried If I Click Retry All on the Task Details Page?
If you click Retry All, the system retries the failed, to-be-retried, or stopped status batch tasks.
Why Does a Device Fail to Download the Upgrade Package During the Upgrade?
Check whether the upgrade package link times out. For details about the upgrade link timeout duration, see section Platform Delivering an Upgrade Event.
Why Does an Upgrade Package Fail to Be Downloaded After the Upgrade Result Is Reported?
After the platform delivers an upgrade package, the device downloads the upgrade package and reports the upgrade result to the platform. If the upgrade result is reported, the platform considers that the upgrade is complete. Therefore, you cannot download the upgrade package again.
What Do I Do If a Device Upgrade Task Times Out?
A software/firmware upgrade task consists of multiple phases. Different phases have different timeout periods. If the device does not report a response within the timeout period of a phase, the upgrade task times out. For details about the timeout period, see Firmware Upgrades.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot