El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
- 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
- How Can I Develop Codecs?
- What Is the Code Rule for Fields of the string and varstring Types?
- What Is the Code Rule for Fields of the array and variant Types?
- How Do I Use messageId During Online Codec Development?
- How Do I Configure a Command Delivery Response During Online Codec Development?
- What Do I Do If a Codec That Was Developed Online Fails to Be Deployed?
- What Do I Do If a Script-based Codec or a Codec Developed Offline Fails in Encoding or Decoding?
- What Do I Do If a Codec That Was Developed Offline Fails to Be Deployed?
- What Do I Do If a Codec That Was Developed Offline Fails to Be Uploaded?
Show all
Copied.
Codecs
How Can I Develop Codecs?
The IoT platform supports the codec online development. For details, see Online Development.
What Is the Code Rule for Fields of the string and varstring Types?
If Data Type of a field is string(string type) or varstring(variable-length string), the codec performs encoding and decoding using ACSII.
For details on the codec online development, see Codec for Strings and Variable-Length Strings.

What Is the Code Rule for Fields of the array and variant Types?
If Data Type is array(array type) or variant(variable-length array type), the codec performs encoding and decoding using Base64. For details on the codec online development, see Codec for Arrays and Variable-Length Arrays.

How Do I Use messageId During Online Codec Development?
When messages of the same type are created, such as two data reporting messages, messageId must be configured to distinguish these messages and this parameter in each message must be in the same place on the list. The messageId field applies to the following scenarios:
- There are two or more data reporting messages or command delivery messages.
- A command response can be regarded as a type of data reporting message. Therefore, if a command response exists, messageId must be added to the data reporting message.
- A data reporting response can be regarded as a type of command delivery message. Therefore, if a data reporting response exists, messageId must be added to the command delivery message.
How Do I Configure a Command Delivery Response During Online Codec Development?
- messageId must be configured in both the data reporting message and the command response, and this field in the two messages must be in the same place on the list, so that the codec can distinguish between the two.
- mid must be configured in the command delivery message and the command response, and this field in the two messages must be in the same place on the list, so that the codec can associate the two.
What Do I Do If a Codec That Was Developed Online Fails to Be Deployed?
Description:
You develop a codec on the development page and click Deploy. The deployment fails.
Possible Causes:
- If the codec is successfully downloaded but fails to be deployed, there may be network issues.
- If the codec fails to be downloaded, the possible causes are as follows:
- The value of messageId in the messages of the same type (for example, two data reporting messages) is duplicate or their positions in the messages are different.
- Data Type is not set to int for messageId.
- The default value of a field is not in hexadecimal format.
- A field name contains a Java keyword, for example, type or int.
Solutions:
- If the codec is successfully downloaded but fails to be deployed, check the network status and try again.
- If the codec fails to be downloaded, check whether the codec definition meets the requirements.
What Do I Do If a Script-based Codec or a Codec Developed Offline Fails in Encoding or Decoding?
- For a script-based codec, choose Products > Codec Development > Edit Script to debug the codec and modify the codec based on the debugging result.
- For a codec developed offline, debug the codec using the codec test tool and modify the codec based on the test result.
What Do I Do If a Codec That Was Developed Offline Fails to Be Deployed?
- Use the IoT codec test tool to check the codec.
- Rectify the fault based on the error code returned by the tool. For details on how to handle different errors, see User Guide for IoT Codec Test Tool in the tool package.
What Do I Do If a Codec That Was Developed Offline Fails to Be Uploaded?
Codecs that are developed offline must be checked before being uploaded to the IoT platform. Use the IoT codec test tool to check the codec package and rectify the fault based on the error message.
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