Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.
- 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 a Product Model?
- How Do I Select a Data Type When Developing a Product Model Online?
- Should the Values of serviceId and serviceType in a Product Model Be the Same?
- Why Does a Child Device Added Through the Gateway Not Belong to Any Product?
- How Can I Upload a Product Model with a Codec on the IoTDA Console?
- Why Is the Upload Button Unavailable When I Want to Upload a Product Model to the IoTDA Console?
- What Should I Do If the File Format Was Incorrect When I Was Uploading a Product Model to the IoTDA Console?
- Why Was a Message Displayed Indicating the Manufacturer ID and Device Model Exist When I Was Uploading a Product Model to the IoTDA Console?
Show all
Copied.
Products Models
This section describes the problems that may occur when you use product models and the solutions.
How Can I Develop a Product Model?
The IoT platform supports online and offline development of product models. For details, see Developing a Product Model Online and Developing a Product Model Offline.
How Do I Select a Data Type When Developing a Product Model Online?
The rules for configuring the data type are as follows:
- int: If the reported data is an integer or Boolean value, set the data type to int. The plug-in can be of the int or array type.
- decimal: If the reported data is a decimal, set the data type to decimal. The plug-in can be of the string, int, or array type.
- string: If the reported data is a string, enumerated value, or Boolean value, set the data type to string. If enumerated or Boolean values are reported, use commas (,) to separate the values. The plug-in can be of the string or array type.
- dateTime: If the reported data is a date, set the data type to dateTime. The plug-in can be of the string or array type.
- jsonObject: If the reported data is in JSON structure, set the data type to jsonObject. The plug-in can be of the string or array type.
Should the Values of serviceId and serviceType in a Product Model Be the Same?
Not necessary. For offline codec development, the values of serviceId and serviceType can be different. One serviceType can correspond to multiple serviceId values. For online codec development, to simplify the development process and make it easy for users to understand, serviceType is set to the same value as serviceId. The value should be consistent with the service type on the platform.
Why Does a Child Device Added Through the Gateway Not Belong to Any Product?
When a child device is added by calling an AgentLite API, the device information carried in the request must be consistent with the product model defined on the IoT platform for the child device. Otherwise, the child device cannot match with the product. Delete the child device that does not belong to any product and add it again. Ensure that the device information is correct.
How Can I Upload a Product Model with a Codec on the IoTDA Console?
IoTDA does not support the upload of product models with codecs.
If you want to use product models with codecs, develop or import product models and codecs on the IoTDA console.
Why Is the Upload Button Unavailable When I Want to Upload a Product Model to the IoTDA Console?
Description:
On the product details page, you upload a product model file, but cannot click OK.

Possible Causes:
- The file name does not meet requirements.
- The uploaded file is not in ZIP format.
Solutions:
- Check whether the name of the product model is in the format of deviceType_manufacturerId_model.zip and whether the values of deviceType, manufacturerId, and model are the same as those defined in the devicetype-capability.json file.
- Check whether the product model is compressed to a ZIP file. If it is compressed as something else, decompress the file, compress it as a ZIP file, and upload it.
What Should I Do If the File Format Was Incorrect When I Was Uploading a Product Model to the IoTDA Console?
Description:
On the product details page, you upload a product model file, and a message is displayed, indicating that the file format is incorrect.
Possible Causes:
- The JSON file format is incorrect.
- The value of commands/properties in the servicetype-capability.json file is not in array format.
- The package contains unrelated files.
Solutions:
- Check the format of each JSON file by using a format verification tool.
- Check whether the values of commands and properties in the servicetype-capability.json file are in the array format (the value should be enclosed in brackets).
- Check whether the compressed package contains unrelated files or hidden files. If yes, delete them and upload the package again.
Why Was a Message Displayed Indicating the Manufacturer ID and Device Model Exist When I Was Uploading a Product Model to the IoTDA Console?
Description:
On the product details page, you upload a product model file, and a message is displayed, indicating that the manufacturer ID and device model exist.
Possible Causes:
The product model and plug-in of the same device model and manufacturer ID already exist on the IoT platform.
Solutions:
- Delete the plug-in and product model of another product or account (delete the plug-in first), and then import the product model.
- Modify the device model and manufacturer ID, and then import the product model.
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