检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
If the device is an indirectly connected device, the gateway ID is the device ID of the directly connected device (that is, the gateway) with which it associates.
The desired properties can be delivered only when they have been defined in the product model and method is specified as W. Restrictions: Keys in the device shadow JSON file cannot contain periods (.), dollar signs ($), and the null character (hexadecimal ASCII code 00).
Only letters, digits, underscores (_), and hyphens (-) are allowed. Request Parameters Table 2 Request header parameters Parameter Mandatory Type Description Instance-Id No String Parameter description: instance ID.
What Are the Differences Between Device ID, Node ID, and IMEI and What Are They Used For? On the IoT platform, you need to enter a node ID (nodeId) when registering a device. A node ID is a physical identifier of a device. Generally, an IMEI or MAC address is used.
Restrictions: Keys in the device shadow JSON file cannot contain periods (.), dollar signs ($), and the null character (hexadecimal ASCII code 00). Otherwise, the device shadow file cannot be updated.
Only letters, digits, underscores (_), and hyphens (-) are allowed. Table 2 Query Parameters Parameter Mandatory Type Description limit No Integer Parameter description: number of records to be displayed on each page. The value is an integer ranging from 1 to 50.
The device node ID contains 1 to 64 characters, including letters, digits, hyphens (-), and underscores (). Note: Information cannot be modified once it is hardcoded to NB-IoT modules. Therefore, the node ID of an NB-IoT device must be globally unique.
Figure 10 Creating a linkage rule - Selecting a device Device-side rules can be created only for devices with the IoT Device SDK. Currently, only IoT Device SDK (C) v1.1.2 is supported. Click Add Trigger.
Secret authentication (SECRET) and certificate authentication (CERTIFICATES) are supported. If secret authentication is used, fill in secret. If certificate authentication is used, fill in fingerprint.
Secret authentication (SECRET) and certificate authentication (CERTIFICATES) are supported. If secret authentication is used, fill in secret. If certificate authentication is used, fill in fingerprint.
Only letters, digits, underscores (_), and hyphens (-) are allowed. Table 2 Query Parameters Parameter Mandatory Type Description limit No Integer Parameter description: number of records to be displayed on each page. The value is an integer ranging from 1 to 50.
If the device is an indirectly connected device, the gateway ID is the device ID of the directly connected device (that is, the gateway) with which it associates.
Only letters, digits, underscores (_), and hyphens (-) are allowed. device_name string Device name. The value can contain a maximum of 256 characters. Only letters, digits, and special characters (_?'#(),&%@!-) are allowed. node_id string Node ID.
Unit Name (for example, section) []: organization unit, for example, IoT Common Name (e.g. server FQDN or YOUR name) []: verification code for verifying the certificate.
If the device is an indirectly connected device, the gateway ID is the device ID of the directly connected device (that is, the gateway) with which it associates.
If the device is an indirectly connected device, the gateway ID is the device ID of the directly connected device (that is, the gateway) with which it associates.
Node ID Customize a unique physical identifier for the device. Enter 4 to 64 characters. Use only letters, digits, underscores (_), and hyphens (-). Device Name Customize the device name. Authentication Type Select Secret.
URI POST /URL (HTTP) determined when the application creates an asynchronous device command status change notification rule. The AMQP channel does not require the URL.
If the device is an indirectly connected device, the gateway ID is the device ID of the directly connected device (that is, the gateway) with which it associates.
It contains 1 to 64 characters, including letters, digits, hyphens (-), and underscores (_). (Note: Information cannot be modified once it is hardcoded to NB-IoT modules. Therefore, the node ID of an NB-IoT must be globally unique.)