Querying Information About a Device

Updated on 2022-02-24 GMT+08:00

View PDF

Typical Scenario

If an NA needs to view detailed information (such as the manufacturer, model, version, status, and service attributes) of a device that has been registered with the IoT platform, the NA can call this API to obtain the information.

API Function

This API is used by an NA to query detailed information of a specified device based on the device ID on the IoT platform, such as configuration, status and service attributes.

API Description

1	public function querySingleDeviceInfo($deviceId, $select, $appId, $accessToken)

Parameter Description

Parameter	Mandatory or Optional	Location	Description
$deviceId	Mandatory	path	Identifies a device. The device ID is allocated by the IoT platform during device registration.
$select	Optional	query	Indicates the query condition. The value can be IMSI.
$appId	Mandatory	query	If the device belongs to the current application, set this parameter to null. Otherwise, set this parameter to the ID of the authorized application.
$accessToken	Mandatory	header	This parameter is set to the value of the access token obtained by calling the Authentication API.

Response Parameters

QuerySingleDeviceInfoOutDTO

Parameter	Description
$deviceId	Identifies a device.
$gatewayId	Identifies a gateway.
$nodeType	Indicates the node type. The value options are ENDPOINT, GATEWAY, and UNKNOW.
$createTime	Indicates the time when the device is created. The value is in the format of yyyyMMdd'T'HHmmss'Z'. An example value is 20151212T121212Z.
$lastModifiedTime	Indicates the last time when the device is modified.
$deviceInfo	Indicates information about the device. For details, see DeviceInfo structure.
$services	Indicates the device service list. For details, see DeviceService structure.

DeviceInfo structure

Parameter	Description
$nodeId	Identifies a device.
$name	Indicates the device name.
$description	Indicates the device description.
$manufacturerId	Uniquely identifies a manufacturer.
$manufacturerName	Indicates the manufacturer name.
$mac	Indicates the MAC address of the device.
$location	Indicates the device location.
$deviceType	Indicates the device type. The upper camel case is used, for example, MultiSensor, ContactSensor, and CameraGateway.
$model	Indicates the device model. In Z-Wave, the format is productType + productId. The value is a hexadecimal value in the format of XXXX-XXXX. Zeros are added if required, for example, 001A-0A12. The format in other protocols is still to be determined.
$swVersion	Indicates the software version of the device. In Z-Wave, the format is major version.minor version, for example, 1.1.
$fwVersion	Indicates the firmware version of the device.
$hwVersion	Indicates the hardware version of the device.
$protocolType	Indicates the protocol type used by the device. The value options are CoAP, huaweiM2M, Z-Wave, ONVIF, WPS, Hue, WiFi, J808, Gateway, ZigBee, and LWM2M.
$bridgeId	Identifies the bridge through which the device accesses the IoT platform.
$status	Indicates whether the device is online. The value options are ONLINE, OFFLINE, INBOX, and ABNORMAL.
$statusDetail	Indicates status details of the device. The value of this parameter varies with the value of status. For details, see status and statusDetail.
$mute	Indicates whether the device is in the frozen state. Based on the value of this parameter, the IoT platform determines whether to manage and store data reported by the device. TRUE: The device is in the frozen state. FALSE: The device is not in the frozen state.
$supportedSecurity	Indicates whether the security mode is supported. TRUE: The security mode is supported. FALSE: The security mode is not supported.
$isSecurity	Indicates whether the security mode is enabled. TRUE: The security mode is enabled. FALSE: The security mode is disabled.
$signalStrength	Indicates the signal strength of the device.
$sigVersion	Indicates the SIG version of the device.
$serialNumber	Indicates the serial number of the device.
$batteryLevel	Indicates the battery level of the device.

status and statusDetail

$status	$statusDetail
OFFLINE	NONE CONFIGURATION_PENDING
ONLINE	NONE COMMUNICATION_ERROR CONFIGURATION_ERROR BRIDGE_OFFLINE FIRMWARE_UPDATING DUTY_CYCLE NOT_ACTIVE

NOTE:

When the device status information is reported to the IoT platform, status and statusDetail must be included. It is recommended that statusDetail be used only for display but not for logical judgment.

DeviceService structure

Parameter	Description
$serviceId	Identifies a service.
$serviceType	Indicates the service type.
$serviceInfo	Indicates service information of the device. For details, see ServiceInfo structure.
$data	Indicates an attribute-value pair (AVP).
$eventTime	The value is in the format of yyyyMMdd'T'HHmmss'Z'. An example value is 20151212T121212Z.

ServiceInfo structure

Parameter	Description
$muteCmds	Indicates the device command list.

Error Codes

HTTP Status Code	Error Codes	Error Description	Remarks
400	100405	The request parameter is invalid.	The request message contains invalid parameters. Recommended handling: Check whether parameters in the API request are correct by referring to the request parameter description.
403	100203	The application is not existed.	The application does not exist. Recommended handling: Check whether appId carried in the HTTP request header is correct. Check whether appId in the request path (URL) is correct.
403	100217	The application hasn't been authorized.	The application has not been authorized. Recommended handling: In scenarios where applications are not authorized, ensure that request parameter appId is null.
403	1010009	app throttle exceed.	The NA calls the API at a frequency that exceeds the flow control threshold (100 calls per minute by default). Recommended handling: Contact IoT platform maintenance personnel to adjust the flow control threshold or control the API call frequency.
403	1010005	App_key or access_token is invalid.	The access token is invalid. Recommended handling: Check whether accessToken carried in the API request is correct.
404	100403	The device is not existed.	The device does not exist. Recommended handling: Check whether deviceId is correct.
404	100418	The deviceData is not existed.	The device data does not exist. Recommended handling: If deviceId carried in the request is incorrect, check whether deviceId belongs to appId or whether deviceId is incorrect. Check whether appId carried in the header contains deviceId. If the URL contains the optional parameter appId, check whether the value of appId is correct.
500	100203	The application is not existed.	The application does not exist. Recommended handling: Check whether appId carried in the HTTP request header is correct. Check whether appId in the request path (URL) is correct.
500	50252	Internal server error.	An internal server error occurs. Recommended handling: An internal error occurs on the IoT platform. Contact IoT platform maintenance personnel.

Parent topic: Data Collection

Previous topic: Data Collection

Next topic: Querying a Device Information List

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot