PushDeviceData - Energy Expert - Alibaba Cloud Documentation Center

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

energy:PushDeviceData

none

*All Resource

*

None

Request syntax

POST /api/v1/data/increment/push HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
body	object	No	The request body.
deviceType	string	Yes	The type of the device. For more information, see Device Type Definitions.	1
devices	array<object>	Yes	A list of devices to push data for.
	array<object>	Yes
deviceId	string	Yes	If deviceType is 12, 13, or 17, pass the system_id (the field name remains deviceId). If deviceType is 15 or 16, do not pass this parameter. This parameter is required in all other cases.	设备ID
recordTime	string	Yes	The time when the data was recorded.	2021-09-08 18:40:00
data	object	Yes	The data point information. To avoid precision issues, pass all data point values as strings. The feature does not work if required fields are missing. Some features might be affected if recommended fields are missing. For details, see the device data point remarks in the appendix. For more information, see Data Point Definitions.	{ "dp_imp": "329.0", "F": "148.0", "eq_imp": "363.0", "Ep_imp_1": "128.0", "Ep_imp_2": "157.0", "Ua": "226.0", "Ub": "285.0", "Ep_imp": "325.0", "Uc": "342.0", "Ep_imp_3": "109.0", "Ep_imp_4": "94.0", "P": "514.0", "Pa": "443.0", "Q": "265.0", "dp_exp": "261.0", "eq_exp": "399.0", "COSQ": "223.0", "Ia": "240.0", "Ib": "216.0", "Ic": "229.0", "Ep_exp": "115.0", "VdisPer": "120.0" }

Response elements

Element	Type	Description	Example
	object	The response parameters.
requestId	string	The request ID.	83A5A7DD-8974-5769-952E-590A97BEA34E
data	string	Indicates whether the data was pushed successfully. A value of success indicates a successful push.	success

Examples

Success response

JSON format

{
  "requestId": "83A5A7DD-8974-5769-952E-590A97BEA34E",
  "data": "success"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.