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.
Advanced Search
Overview
To quickly find the desired device, you can use advanced search to set flexible search criteria using SQL-like statements to search. For example, you can search for devices by prefix fuzzy match or by tag. This section guides you on using advanced search and SQL-like syntax.
Constraints
- This API is supported only by Standard and Enterprise editions.
- The maximum TPS for an account to call this API is 1 (one request per second).
Scenarios
Device search: On the All Devices > Device List page, use SQL-like statements to search for specified devices for subsequent management operations.
Dynamic device grouping: Based on the rules of SQL-like statement, devices that meet the filter criteria are automatically added to the group for management.
Procedure
- 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 under your account are displayed in the device list.
- Click Advanced Search, enter an SQL-like statement, and click Search to display the target devices.
Figure 1 Device - Advanced search
SQL-like Syntax Description
When using SQL-like statements on the console, omit the select, from, order by, and limit clauses. You only need to enter a where clause to edit user-defined conditions. The maximum length of a statement is 400 characters. The content in the clause is case sensitive, but keywords in SQL statements are case insensitive. On the console, data is sorted based on the marker field desc by default.
A where clause:
[condition1] AND [condition2]
Example:
product_id = 'testProductId'
Up to five conditions are supported. Conditions cannot be nested. For details about the parameters that support query, see Table 1 and Table 2.
AND and OR are supported. For details about the priority, see the standard SQL syntax. By default, the priority of AND is higher than that of OR.
Parameter |
Data Type |
Description |
Value Range |
---|---|---|---|
app_id |
string |
Resource space ID. |
The value can contain up to 36 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. |
device_id |
string |
Device ID. |
The value can contain up to 128 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. |
gateway_id |
string |
Gateway ID. |
The value can contain up to 128 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. |
product_id |
string |
ID of the product associated with the device. |
The value can contain up to 36 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. |
device_name |
string |
Device name. |
The value can contain up to 256 characters. Only letters, digits, and special characters (_?'#().,&%@!-) are allowed. |
node_id |
string |
Node ID. |
The value can contain up to 64 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. |
status |
string |
Device status. |
The value can be ONLINE, OFFLINE, ABNORMAL, INACTIVE, or FROZEN. |
node_type |
string |
Device node type. |
The value can be GATEWAY (a directly connected device or gateway) and ENDPOINT (an indirectly connected device). |
tag_key |
string |
Tag key. |
The value can contain up to 64 characters. Only letters, digits, underscores (_), periods (.), and hyphens (-) are allowed. |
tag_value |
string |
Tag value. |
The value can contain up to 128 characters. Only letters, digits, underscores (_), periods (.), and hyphens (-) are allowed. |
sw_version |
string |
Software version. |
The value can contain up to 64 characters. Only letters, digits, underscores (_), hyphens (-), and periods (.) are allowed. |
fw_version |
string |
Firmware version. |
The value can contain up to 64 characters. Only letters, digits, underscores (_), hyphens (-), and periods (.) are allowed. |
group_id |
string |
Group ID. |
The value can contain up to 36 characters, including hexadecimal strings and hyphens (-). |
create_time |
string |
Device registration time. |
Format: yyyy-MM-dd'T'HH:mm:ss.SSS'Z', for example, 2015-06-06T12:10:10.000Z |
marker |
string |
Result record ID. |
The value is a string of 24 hexadecimal characters, for example, ffffffffffffffffffffffff. |
Operator |
Supported By |
---|---|
= |
All parameters |
!= |
All parameters |
> |
create_time and marker |
< |
create_time and marker |
like |
device_name, node_id, tag_key, and tag_value |
in |
Parameters except tag_key and tag_value. |
not in |
Parameters except tag_key and tag_value. |
SQL Restrictions
- like: Only prefix match is supported. Suffix match or wildcard match is not supported. At least four characters must be contained for prefix match. Special characters cannot be contained. Only letters, digits, underscores (_), and hyphens (-) are allowed. The prefix must end with %.
- Other SQL statements, such as nested SQL statements, union, join, and alias, are not supported.
- The SQL statement can contain up to 400 characters. Up to five request conditions are supported.
- The condition value cannot be null or an empty string.
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