> For the complete documentation index, see [llms.txt](https://docs.unwaste.energy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unwaste.energy/en/unwaste-robot-operation/technical-details/time-model-and-data-storage.md).

# Time model and data storage

Learn how Unwaste handles time, data intervals, and historical data storage.

### Raw readings

When the system is STARTED:

* the Unwaste Robot reads configured sensors every **5 seconds**.

These readings may include, depending on configuration:

* power sensors (W, kW),
* energy counters (Wh / kWh),
* state-of-charge, modes, and other device-specific values.

### Aggregation blocks

To store consistent history and align with control decisions:

* readings are aggregated into **15-minute blocks**,
* blocks are aligned to full quarters (00, 15, 30, 45 minutes).

A 15-minute block is a practical compromise:

* small enough to reflect typical changes in production and load,
* large enough to store efficiently and produce stable charts.

### Storage rule

* Aggregated 15-minute totals are stored in the database.
* Power Flow "current" values are not stored.
* Graphs and historical views rely on stored aggregation, not raw samples.

### STOPPED periods

When the system is STOPPED:

* there is no data collection,
* and therefore no aggregation for that period.

This is why:

* daily totals "pause" while STOPPED,
* historical graphs show zeros for those intervals (timeline continuity),
* and aggregated totals exclude those missing intervals.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.unwaste.energy/en/unwaste-robot-operation/technical-details/time-model-and-data-storage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.