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
Copied.
Groups and Tags
Group Introduction
A device group is a collection of devices. You can create groups for all the devices in a resource space based on rules (such as regions and types), and operate these devices by group. For example, you can perform a firmware upgrade on a group of water meters in the resource space. Devices in a group can be added, deleted, modified, and queried. A device can be bound to and unbound from multiple groups.
Group Type |
Description |
---|---|
Static group |
You need to manually add devices to or remove devices from a group. Group nesting is supported. Restrictions:
|
Dynamic group |
Devices are automatically added to or removed from the group based on the dynamic query rules of SQL-like statements. You cannot manually manage devices in a dynamic group. Restrictions:
|
Managing Groups
- Access the IoTDA service page and click Access Console. Click the target instance card.
- In the navigation pane, choose Devices > Groups.
- You can add, modify, or delete a group.
Figure 1 Device - Group
Static Group
- Access the IoTDA service page and click Access Console. Click the target instance card.
- In the navigation pane, choose Devices > Groups.
- Click Add Root Group to add a group. Set group type to Static Group, set parameters as prompted, and click OK.
Figure 2 Group - Creating a static group
- Access the static group details page. Bind or unbind devices in the group. For details, see Table 2.
Figure 3 Static group - Binding a device
Table 2 Description Operation
Description
Binding
Click Bind to bind a device to a group.
Batch unbinding
Select multiple devices (up to 100 devices at a time) and click Batch Unbind to unbind the selected devices from the current group.
Unbinding
Locate the target device and click Unbind to unbind the device from the group.
- In the navigation pane, choose Devices > All Devices. On the displayed page, locate the target device, click View in the Operation column. Click the Groups tab page to check and manage the associated groups. For details, see Table 2.
Figure 4 Device - Group management
Dynamic group
- Access the IoTDA service page and click Access Console. Click the target instance card.
- In the navigation pane, choose Devices > Groups.
- Click Add Root Group to add a group. Set Group Type to Dynamic.
- Set parameters as prompted, enter SQL-like statements, and click Configure Rule to check the matched devices. Click OK to complete the dynamic group creation.
Figure 5 Group - Creating a dynamic group
NOTE:
- For details about the dynamic rule syntax, see Advanced Search.
- The difference between dynamic group rules and advanced search is that dynamic group rules do not support app_id and group_id filtering.
- You can click Try to enter a dynamic rule. After you enter a dynamic rule, click OK. The rule is automatically written back.
Dynamic Group Example
Create a dynamic group based on the device name fuzzy match rule (other conditions can be selected based on the site requirements) and select the dynamic group to execute the OTA upgrade task.
Devices in a dynamic group are dynamically adjusted based on device names, and the status of the OTA upgrade task associated with the dynamic group also changes dynamically.
For details, see Upgrading the Firmware for a Batch of Devices and Dynamic group.
- Create a dynamic group named HuaweiDeviceGroup and set the group rule to device_name like'HuaweiDevice %'.
Figure 6 Dynamic group - Details
- Create a device firmware upgrade task and select the dynamic group HuaweiDeviceGroup.
Figure 7 Creating a firmware upgrade task - Dynamic group
- After the dynamic group is created, you can view that the devices in the dynamic group are added to the upgrade task.
Figure 8 Firmware upgrade task - Details (dynamic group)
- Register a device by referring to Registering a Single Device. The device name is HuaweiDevice011. After the registration is successful, you can view that the device has been automatically added to the dynamic group HuaweiDeviceGroup.
Figure 9 Dynamic group - Adding a device
- View the sub-task details of the software and firmware upgrade task. You can see that the device has been automatically added to the upgrade task.
Figure 10 Firmware upgrade task - Adding a device to a dynamic group
- On the HuaweiDevice001 details page, change the device name to AbandonedHuaweiDevice001.
Figure 11 Device - Changing device name
- After the device name is changed successfully, the device is automatically removed from the HuaweiDeviceGroup dynamic group.
Figure 12 Dynamic group - Removing a device
- Check the sub-task details of the software and firmware upgrade task. The upgrade status of the device is Removed.
Figure 13 Firmware upgrade task - Removing a device from a dynamic group
Tags
Tags are used to classify devices. You can bind tags to devices on the device details page to manage devices.
- Access the IoTDA service page and click Access Console. Click the target instance card.
- In the navigation pane, choose Devices > All Devices. On the displayed page, locate the target device, and click View in the Operation column to access its details page.
- On the Tags tab page, click Bind Tags to bind one or more tags to the device.
Figure 14 Device - Binding a tag
Group-related APIs
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