> For the complete documentation index, see [llms.txt](https://docs.kemperconnect.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kemperconnect.de/asset-types/cleanairtower-sf/history.md).

# history

The History tab displays performance trends for the disposable filter Clean Air Tower, showing volume flow, motor status, and power consumption over time.

## Accessing History

Navigate to the device detail page and select the "History" tab.

## Performance History Chart

### Chart Title

"Performance History (24 Hours)"

### Chart Subtitle

"Volume flow, motor status, and power consumption over time"

### Data Series

| Series           | Description                 |
| ---------------- | --------------------------- |
| **Volume Flow**  | Air flow rate in m³/h       |
| **Motor Status** | Running/Stopped (area fill) |
| **Motor Power**  | Power consumption in W      |

### Chart Legend

| Element          | Description               |
| ---------------- | ------------------------- |
| Volume Flow line | Air volume being filtered |
| Status area      | Motor operating state     |
| Power line       | Power consumption         |

## Time Range

Default 24-hour view with options:

* 24 hours (detailed)
* 7 days (hourly)
* 30 days (daily)

### Data Resolution

| Range    | Resolution            |
| -------- | --------------------- |
| 24 hours | 5-15 minute intervals |
| 7 days   | Hourly aggregates     |
| 30 days  | Daily aggregates      |

## Reading the Chart

### Volume Flow Line

* Shows filtration rate over time
* Higher = more air processed
* Drops when motor stops

### Motor Status Area

* Shaded when running
* Clear when stopped
* Correlates with flow

### Power Consumption

* Shows energy usage
* Higher during boost mode
* Correlates with operation

## Chart Interaction

<details>

<summary>Hover Details</summary>

* Exact values at cursor
* Timestamp
* All metrics shown

</details>

<details>

<summary>Legend Toggle</summary>

* Click to show/hide series
* Focus on specific metrics

</details>

## Historical Patterns

<details>

<summary>Normal Operation</summary>

* Consistent flow when running
* Stable power consumption
* Expected on/off patterns

</details>

<details>

<summary>Boost Mode Periods</summary>

* Higher power consumption
* Potentially higher flow
* Short duration typically

</details>

<details>

<summary>Potential Issues</summary>

* Declining volume flow
* Increasing power draw
* Irregular patterns

</details>

## Use Cases

### Performance Monitoring

* Track filtration efficiency
* Monitor power usage
* Identify anomalies

### Energy Analysis

* Power consumption trends
* Efficiency optimization
* Cost tracking

### Maintenance Planning

* Observe performance decline
* Plan filter replacement
* Schedule interventions

## Related Documentation

<table data-view="cards"><thead><tr><th>Title</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td>Dashboard</td><td><a href="broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3">Broken link</a></td></tr><tr><td>Settings</td><td><a href="broken://pages/77771dd7529569caf13202321a8310a71766035b">Broken link</a></td></tr><tr><td>Energy Consumption</td><td><a href="file:///monitoring/energy-consumption/overview.md">file:///monitoring/energy-consumption/overview.md</a></td></tr></tbody></table>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kemperconnect.de/asset-types/cleanairtower-sf/history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.