Readings & Aggregations
You can use the Readings API to observe the state of an Entity over time.
What is a Reading?
A Reading represents a single snapshot of the state of an Entity. Using the Readings API, you can retrieve a list of Readings within a timespan, with each reading representing a single moment in time.
Entities of the same type, produce similarly structured Readings. This allows you to process them uniformly, regardless of type of device or vehicle your working with. However, it is important to note that depending on the type of Entity or it’s manufacturer, some properties can be unavailable (omitted) due to manufacturer limitations.
Aggregations
The amount of time between each Reading (the resolution) varies per Entity type and manufacturer and mostly depends on manufacturer limitations. Some Entities produce many of Readings in a relatively short amount of time. The more Readings are produced within a given timespan, the greater the detail with which you can observe changes on the state of that Entity. But, it can also make it more cumbersome to process them.
That’s why our Readings API supports Aggregations right out the box. Aggregations reduce the resolution of a list of Readings, combining multiple Readings into one by statistically averaging them.
Aggregations are currently only supported for certain types of Entities.
Retrieving Readings
To retrieve Readings, we’re using the Get /entities/{entityId}/readings endpoint.
Parameters
start
required
Start (date & time) of the timespan for which you want to list all Readings.
end
optional (defaults to current date & time)
End (date & time) of the timespan for which you want to list all Readings.
Note: input and output of time on the re.alto platform is in Zulu time (UTC)
Access the full list of available parameters through the API References.
Example Request
Example Responses
Note: The values marked ‘positive’ relate to consumed energy, while ‘negative’ power always relates to the production of energy.
Example of an EV Reading:
Example of a Retrofitmeter Reading:
Retrieving Aggregations
To retrieve Readings, we’re using the Get /entities/{entityId}/aggregations endpoint.
Parameters
start
required
Start (date & time) of the timespan for which you want to list Aggregations.
end
optional (defaults to current date & time)
End (date & time) of the timespan for which you want to list Aggregations.
resolution
required
The granularity at which Readings are combined or summarised. It determines the size of the time intervals over which data is Aggregated.
Note: input and output of time on the re.alto platform is in Zulu time (UTC)
Access the full list of available parameters through the API References.
Example Request
Example Response
Was this page helpful?