このページは、お客様の言語ではご利用いただけません。Huawei Cloudは、より多くの言語バージョンを追加するために懸命に取り組んでいます。ご協力ありがとうございました。
- 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
Copied.
Device Management
After a device is registered, you can manage the device, view device information, and freeze the device on the IoTDA console.
- Access the IoTDA service page and click Access Console. Click the target instance card.
- In the navigation pane, choose Devices > All Devices. By default, all devices in the current instance are displayed in the device list.
Figure 1 Device - Device list
Table 1 Device list functions Function
Description
Search for a device
Search for a specific device based on the status, device name, node ID, device ID, resource space, product, and node type.
View device information
View the device status, device name, and node ID in the device list. Click View in the row of a device to access the device details.
Delete a device
Click Delete in the row of a device to delete the device.
NOTE:
After a device is deleted, the related device data is deleted. Exercise caution when performing this operation.
To delete a large number of devices, you can call the API for creating a batch task or delete devices in batches on the IoTDA console. For details, see Deleting a Batch of Devices.
Freeze a device
Click Freeze in the row of a device to freeze the device.
NOTE:
A frozen device cannot go online. Only devices that are directly connected to the platform can be frozen.
To freeze a large number of devices, you can call the API for creating a batch task.
Unfreeze a device
Click Unfreeze in the row of a device to unfreeze the device.
To unfreeze a large number of devices, you can call the API for creating a batch task.
Debug a device
Click Debug in the row of a device to debug the device.
Device Status
You can view the device status (online, offline, inactive, abnormal, or frozen) on the IoTDA console. You can also learn the device status by means of subscription. The table below describes the device statuses.
Type |
Status |
Short-Connection Device (Such as NB-IoT Devices) |
Persistent Connection Device (MQTT Device) |
---|---|---|---|
Connection status |
Online |
If a device has reported data within 25 hours, the device status is Online. If no data has been reported within the past 25 hours, the device status is Abnormal. |
The device is connected to the platform. |
Offline |
If a device reports no data for 49 hours after connecting to the platform, the platform sets the device status to Offline. |
After the device is disconnected from the platform for 1 minute (the data is automatically updated every minute), the device status is set to Offline. If you manually refresh the status on the page, the device status is displayed as Offline. |
|
Abnormal |
If a device reports no data for 25 hours after connecting to the platform, the platform sets the device status to Abnormal. |
This status does not apply to persistent connection devices. |
|
Inactive |
The device is registered with but does not connect to the platform. The device activation procedure is described in Initializing a Device. |
The device is registered with but does not connect to the platform. The device activation procedure is described in Initializing a Device. |
|
Management status |
Frozen |
After a device is frozen, it cannot be connected to the IoT platform. Currently, only devices directly connected to the IoT platform can be frozen. |
Viewing Device Details
In the device list, click View in the row of a device to access its details.

Tab |
Description |
---|---|
Device Info |
|
Cloud Run Logs |
IoTDA records connections with devices and applications. You can view the information on the console. For details, see Run Logs (New Version). |
Cloud Delivery |
You can create a command or message (MQTT device only) delivery task for an individual device on the IoTDA console. For details, see Data Delivery. |
Device Shadow |
The platform provides the device shadow to cache the device status. When the device is online, delivered commands can be directly obtained. When the device is offline, it can proactively obtain the delivered commands after going online. For details, see Device Shadow. |
Message Trace |
The platform supports quick fault locating and cause analysis through message trace. For details, see Message Trace. |
Device Monitoring |
|
Child Devices |
Devices can be directly or indirectly connected to the IoT platform. Indirectly connected devices access the platform through gateways. For details, see Gateways and Child Devices. |
Tags |
You can define tags and bind tags to devices. For details, see Tags. |
Groups |
You can add devices to different groups for batch operations. For details, see Groups and Tags. |
Deleting a Batch of Devices
To delete devices in batches on the IoTDA console, perform the following steps:
- Access the IoTDA service page and click Access Console. Click the target instance card.
- In the navigation pane, choose Devices > All Devices, click the Batch Deletion tab, and click Batch Deletion.
- In the displayed dialog box, download Batch Device Deletion Template, enter the IDs of the devices to be deleted in the template, specify Task Name, upload the file, and click OK. Alternatively, you can specify a product to delete devices in batches.
Figure 3 Device - Deleting devices in batches (by file)Figure 4 Device - Deleting devices in batches (by product)
The task execution status and result are displayed. If the success rate is not 100%, click the task name to open the task details page and view the failure cause.
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