# Meter Data

# Meter - Hourly Energy
Hourly Energy Consumption values: total or net energy (ENETO), import energy (ENEIM) and export energy (ENEEX). The parameters of the devices depends on devices type and the device model is also avaiable.
# HTTP Request
GET {url}/data/meter/energy/hourly?startTime={startTime}&endTime={endTime}&deviceIds={device_ids}¶ms={params}&sum={sum}
# Request Headers
| Key | Value |
|---|---|
| x-language | en |
| Authorization | Bearer {YOUR_API_TOKEN_HERE} |
# Request Params
| Parameter | Required | Type | Description |
|---|---|---|---|
| startTime | YES | datetime | Initial DateTime (UTC) for collecting the data |
| endTime | YES | datetime | Final DateTime (UTC) for collecting the data. The maximum allowed time interval is 30 days |
| deviceIds | YES | Array of String | Array of Devices ID. The device ID could be specified more than 1 device by comma (,) |
| params | YES | Array of String | Array of tag code (XXXXX). The tag code could be specified more than 1 parameters by comma (,) |
| sum | NO | Number | If you need to summarized energy from devices per hour (device + device), please specified 1 |
# Response
When successfully redirect to the assigned redirect_uri or posts according to the form with the parameters below attached.
| Parameter | Type | Description |
|---|---|---|
| count | Number | The count of the energy hourly data in the requested period time. |
| deviceId | String | Devices ID |
| energy.date | datetime | The UTC datetime of the energy hourly |
| params | double | The tag code or Energy hourly's parameters as requested |
{
"data": {
"count": 6,
"energy": [
{
"date": "2021-08-30T08:00:00.000Z",
"deviceId": "60d42870d9cd632d3cc01661",
"ENEIM": 9.51699999999255,
"ENETO": 9.51699999999255
},
...
{
"date": "2021-08-30T08:00:00.000Z",
"deviceId": "60d428a1d9cd632d3cc01663",
"ENETO": 0.022216796879547474
},
...
]
}
}
Example
As the response above, we have got the hourly import energy (ENEIM) and the hourly total energy (ENETO) in local timestamp "2021-08-30T15:00:00.000Z" of the device "DEVICE_NAME1" and "DEVICE_NAME2".
# Meter - Daily Energy

Daily Energy Consumption values: total or net energy (ENETO), import energy (ENEIM) and export energy (ENEEX). The parameters of the devices depends on devices type and the device model is also avaiable. Energy on peak time and off peak time is calculated from Thailand's TOU.
# HTTP Request
GET {url}/data/meter/energy/daily?startTime={startTime}&endTime={endTime}&deviceIds={device_ids}¶ms={params}&sum={sum}&total={total}
# Request Headers
| Key | Value |
|---|---|
| x-language | en |
| Authorization | Bearer {YOUR_API_TOKEN_HERE} |
# Request Params
| Parameter | Required | Type | Description |
|---|---|---|---|
| startTime | YES | datetime | Initial DateTime (UTC) for collecting the data |
| endTime | YES | datetime | Final DateTime (UTC) for collecting the data. The maximum allowed time interval is 30 days |
| deviceIds | YES | Array of String | Array of Devices ID. The device ID could be specified more than 1 device by comma (,) |
| params | YES | Array of String | Array of tag code (XXXXX). The tag code could be specified more than 1 parameters by comma (,) |
| sum | NO | Number | If you need to summarized energy from devices per day (device + device), please specified 1 |
| total | NO | Number | If you need to summarized energy from days per device (day + day), please specified 1 |
# Response
When successfully redirect to the assigned redirect_uri or posts according to the form with the parameters below attached.
| Parameter | Type | Description |
|---|---|---|
| count | Number | The count of the energy hourly data in the requested period time. |
| deviceId | String | Devices ID |
| energy.date | datetime | The UTC datetime of the energy daily. |
| params | double | The tag code or Energy daily's parameters as requested |
{
"data": {
"count": 4,
"energy": [
{
"date": "2021-07-01T17:00:00.000Z",
"deviceId": "60d42870d9cd632d3cc01661",
"ENETO_ON": 144.23399999999674,
"ENETO_OFF": 29.62600000000384,
"ENETO_TOTAL": 173.86000000000058 al
},
...
{
"date": "2021-07-01T17:00:00.000Z",
"deviceId": "60d428a1d9cd632d3cc01663",
"ENETO_ON": 30.32897949219023,
"ENETO_OFF": 4.649902343760004,
"ENETO_TOTAL": 34.97888183595023
},
...
]
}
}
Example
As the response above, we have got the daily total energy (ENETO) (total, on-peak, off-time) on "2021-07-02" of the device "DEVICE_NAME1" and "DEVICE_NAME2".
TIP
ENETO_TOTAL on 2021-07-02 is energy daily since 2021-07-01T17:00:00.000Z (local 2021-07-01T00:00:00.000Z) to 2021-07-02T17:00:00.000Z (local 2021-07-02T00:00:00.000Z)
ENETO_ON on 2021-07-02 is energy daily on peak time since 2021-07-01T02:0:00.000Z (local 2021-07-01T09:00:00.000Z) to 2021-07-02T15:00:00.000Z (local 2021-07-02T22:00:00.000Z)
ENETO_OFF on 2021-07-02 is energy daily off peak time = ENETO_TOTAL - ENETO_ON
# Meter - Monhthly Energy
Monthly Energy Consumption values: total or net energy (ENETO), import energy (ENEIM) and export energy (ENEEX). The parameters of the devices depends on devices type and the device model is also avaiable.
# HTTP Request
GET {url}/data/meter/energy/monthly?startTime={startTime}&endTime={endTime}&deviceIds={device_ids}¶ms={params}&sum={sum}
# Request Headers
| Key | Value |
|---|---|
| x-language | en |
| Authorization | Bearer {YOUR_API_TOKEN_HERE} |
# Request Params
| Parameter | Required | Type | Description |
|---|---|---|---|
| startTime | YES | datetime | Initial DateTime (UTC) for collecting the data |
| endTime | YES | datetime | Final DateTime (UTC) for collecting the data. The maximum allowed time interval is 1 year |
| deviceIds | YES | Array of String | Array of Devices ID. The device ID could be specified more than 1 device by comma (,) |
| params | YES | Array of String | Array of tag code (XXXXX). The tag code could be specified more than 1 parameters by comma (,) |
| sum | NO | Number | If you need to summarized energy from devices per monthly (device + device), please specified 1 |
# Response
When successfully redirect to the assigned redirect_uri or posts according to the form with the parameters below attached.
| Parameter | Type | Description |
|---|---|---|
| count | Number | The count of the energy hourly data in the requested period time. |
| deviceId | String | Devices ID |
| energy.date | datetime | The UTC datetime of the energy monthly |
| params | double | The tag code or Energy monthly's parameters as requested |
{
"data": {
"count": 2,
"energy": [
{
"date": "2021-06-30T17:00:00.000Z",
"deviceId": "60d42870d9cd632d3cc01661",
"ENETO": 4124.405999999988
},
{
"date": "2021-07-31T17:00:00.000Z",
"deviceId": "60d42870d9cd632d3cc01661",
"ENETO": 3938.027000000002
}
]
}
}
Example
As the response above, we have got the monthly total energy (ENETO) in "2021-07" of the device "DEVICE_NAME".
# Meter - Average Power 15 Minutes

Average Active Power (PACTO) is for finding peak demand. Reactive Power (QACTO) is for finding excess power factor as follow the electricity tariff. The parameters of the devices depends on devices type and the device model is also avaiable.
# HTTP Request
GET {url}/data/meter/power/average?startTime={startTime}&endTime={endTime}&deviceIds={device_ids}
# Request Headers
| Key | Value |
|---|---|
| x-language | en |
| Authorization | Bearer {YOUR_API_TOKEN_HERE} |
# Request Params
| Parameter | Required | Type | Description |
|---|---|---|---|
| startTime | YES | datetime | Initial DateTime (UTC) for collecting the data |
| endTime | YES | datetime | Final DateTime (UTC) for collecting the data. The maximum allowed time interval is 30 days |
| deviceIds | YES | Array of String | Array of Devices ID. The device ID could be specified more than 1 device by comma (,) |
# Response
When successfully redirect to the assigned redirect_uri or posts according to the form with the parameters below attached.
| Parameter | Type | Description |
|---|---|---|
| count | Number | The count of the raw data in the requested period time. |
| data.date | datetime | The UTC datetime of the publish timestamp (average 15 minutes) from the device or summarized devices |
| data.params | double | The tag code or Average value 15 minutes's parameters as requested |
{
"data": {
"count": 4,
"data": [
{
"PACTO": 1.3698897759119666,
"QACTO": -0.31670162081718434,
"date": "2021-08-26T17:00:00.000Z"
},
...
]
}
}
Example
As the response above, we have got the average active power (PACTO) and average reactive power (QACTO) per device when specified 1 device and got the summarized average active power (PACTO) and summarized average reactive power (QACTO) all devices when specified more than 1 devices at the local timestamap "2021-08-26T00:00:00.000Z"
# Meter - Max Average power 15 mintues

Finding Maximum Average active power (PACTO) 15 mintues and Maximum Average reactive power (QACTO) 15 mintues with timestamp on the period time to find the behavior maximum load consumption. The parameters of the devices depends on devices type and the device model is also avaiable.
# HTTP Request
GET {url}/data/meter/power/average.max?startTime={startTime}&endTime={endTime}&deviceIds={device_ids}
# Request Headers
| Key | Value |
|---|---|
| x-language | en |
| Authorization | Bearer {YOUR_API_TOKEN_HERE} |
# Request Params
| Parameter | Required | Type | Description |
|---|---|---|---|
| startTime | YES | datetime | Initial DateTime (UTC) for collecting the data |
| endTime | YES | datetime | Final DateTime (UTC) for collecting the data. The maximum allowed time interval is 30 days |
| deviceIds | YES | Array of String | Array of Devices ID. The device ID could be specified more than 1 device by comma (,) |
# Response
When successfully redirect to the assigned redirect_uri or posts according to the form with the parameters below attached.
| Parameter | Type | Description |
|---|---|---|
| count | Number | The count of the raw data in the requested period time. |
| data.date | datetime | The UTC datetime of the publish timestamp (max.average 15 minutes per day) from the device or summarized devices |
| data.params | double | the tag code or Maximum Average value per day's parameters as requested |
{
"data": {
"PACTO": {
"max": 19.07049560546875,
"date": "2021-06-26T12:00:00.000Z"
},
"QACTO": {
"max": 7.247457822163899,
"date": "2021-06-27T06:15:00.000Z"
}
}
}
Example
As the response above, we have got the Max Average active power (PACTO) and Max Average reactive power (QACTO) per device when specified 1 device and got the Max Summarized Average active power (PACTO) and Max Summarized Average reactive power (QACTO). All devices specified more than 1 devices at the local timestamap "2021-06-26T19:00:00.000Z" for active power (PACTO) and the local timestamap "2021-06-27T13:15:00.000Z" for active power (QACTO)
# Meter - Demand Charge

Finding Demande Charge or Maximum Average active power (PACTO) 15 mintues which comply with Trarff Thaland standard with timestamp on the period montly time to find the behavior maximum demand charge. The parameters of the devices depends on devices type and the device model is also avaiable.
# HTTP Request
GET {url}/data/meter/power/demandCharge?startTime={startTime}&endTime={endTime}&deviceIds={device_ids}
# Request Headers
| Key | Value |
|---|---|
| x-language | en |
| Authorization | Bearer {YOUR_API_TOKEN_HERE} |
# Request Params
| Parameter | Required | Type | Description |
|---|---|---|---|
| startTime | YES | datetime | Initial DateTime (UTC) for collecting the data |
| endTime | YES | datetime | Final DateTime (UTC) for collecting the data. The maximum allowed time interval is 30 days |
| deviceIds | YES | Array of String | Array of Devices ID. The device ID could be specified more than 1 device by comma (,) |
# Response
When successfully redirect to the assigned redirect_uri or posts according to the form with the parameters below attached.
| Parameter | Type | Description |
|---|---|---|
| count | Number | The count of the raw data in the requested period time. |
| data.date | datetime | The UTC datetime of the publish timestamp (max.average 15 minutes per month) from the device or summarized devices |
| data.PACTO | double | the demand charge per months as requested |
{
"data": [
{
"date": "2022-06-30T02:00:00.000Z",
"PACTO": 809.2933333331715
},
{
"date": "2022-07-02T07:45:00.000Z",
"PACTO": 798.2048888887293
}
]
}
Example
As the response above, we have got the Demand Charge Power (PACTO) 809.29 kW on 9:00, 30-Jun-22 (June 2022) and 798.20 kW on 14:45, 2-Jul-22 (July 2022)