> 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/airdome/history.md).

# history

The History tab displays performance trends for the AirDome filtration system over time, showing volume flow, motor status, and cleaning events.

## 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 and motor status over time

### Data series

| Series              | Color     | Description                      |
| ------------------- | --------- | -------------------------------- |
| **Volume Flow**     | Blue line | Air volume flow in m³/h          |
| **Motor Status**    | Area fill | Operating state (on/off)         |
| **Cleaning Cycles** | Markers   | Automatic filter cleaning events |

### Time range

Default view shows 24-hour history with configurable ranges:

* 24 hours (default)
* 7 days
* 30 days

{% hint style="info" %}
Default view: 24 hours.
{% endhint %}

### Chart legend

| Element          | Description                                  |
| ---------------- | -------------------------------------------- |
| Volume Flow line | Air volume being filtered                    |
| Status area      | Device operating state (shaded when running) |
| Cleaning markers | Points indicating cleaning cycles            |

## Reading the chart

### Volume flow line

* Shows air filtration rate over time
* Higher values indicate more air being processed
* Drops to zero when motor stops

### Motor status area

* Shaded area indicates motor running
* Clear area indicates motor stopped
* Correlates with volume flow changes

### Cleaning events

* Markers show automatic filter cleaning
* Indicates filter maintenance activity
* Normal operation includes periodic cleaning

## Chart interaction

### Hover

* Shows exact values at cursor position
* Displays timestamp
* Shows volume flow and status

### Legend toggle

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

## Historical patterns

### Normal operation

* Consistent volume flow when running
* Regular cleaning cycles
* Expected on/off patterns

### Performance issues

* Decreasing volume flow over time
* Increased cleaning frequency
* Irregular patterns

### Filter loading

* Gradual decrease in flow
* More frequent cleanings
* Indicates filter approaching capacity

## Data resolution

| Time range | Resolution            |
| ---------- | --------------------- |
| 24 hours   | 5–15 minute intervals |
| 7 days     | Hourly intervals      |
| 30 days    | Daily aggregates      |

## Export and analysis

Historical data supports:

* Trend analysis
* Performance monitoring
* Maintenance planning
* Compliance reporting

## Related documentation

* [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current status
* [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - Operating information
* [Service](file:///monitoring/service/overview.md) - Maintenance tracking


---

# 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.kemperconnect.de/asset-types/airdome/history.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.