FAQ
Q1: How to upload integer/float data points in the numerical form?
A: It is recommended to upload data points in the form of type=3 or type=1 (refer to the “Device Terminal Access Protocol-EDP” for details). Example:
type=3 integer： {"temperature":22}
Float： {"pi":3.14159}
type=1 integer： {"datastreams":[{"id":"temperature","datapoints":[{"value":22}]}]}
Float： {"datastreams":[{"id":"pi","datapoints":[{"value":3.14159}]}]}
Q2: How to upload location information?
A: The geographic location is displayed in the JSON format in the data stream. It is recommended to use type=3 or type=1 to upload (refer to the “Device Terminal Access Protocol-EDP” for details). Example:
type=3：{"loc":{"lon": 117.48,"lat": 39.96}}
type=1：{"datastreams":[{"id":"loc","datapoints":[{"value":{"lon":117.48,"lat":39.96}}]}]}
Q3: The EDP is used to issue control commands. What is the role of cmd_id?
A: cmd_id is randomly generated by the server. Each EDP-cmd corresponds to a unique cmd_id. Users can obtain the command response of the device and the execution status of the command via RESTFUL API according to the cmd_id. (See the API document for details.)
Q4: After the device receives an EDP command request, is it necessary to respond to the EDP command?
A: The EDP command request is usually used to send commands to controls. When a command is sent, the server will generate a unique cmd_id and corresponding execution status. After the device receives the command and sends the EDP command response, the execution status of the server will change to successful execution. If the device does not respond, the execution status of the server will be set to execution timeout. The execution status of the command can be queried by RESTFUL API and cmd_id. If the device does not send a response, only the execution status of the command saved in the server will be affected, and command issuing will not be affected.