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

# dashboard

The dashboard provides real-time monitoring of the self-cleaning Clean Air Tower, including device status, volume flow, filter cleaning cycles, and service status.

## Dashboard Layout

### Header Section

* Device name and model
* Status badge (On/Off/Idle/Offline/Error)
* Location (if configured)
* Last seen timestamp
* Subtitle: "Self-cleaning air filtration system monitoring"

### Device Status Card

Displays power state:

| Field      | Description |
| ---------- | ----------- |
| **Status** | On or Off   |

Visual indicators:

* Green icon when on
* Gray icon when off
* Red icon on error

### Volume Flow Card

Current air filtration rate:

| Field           | Unit | Description                 |
| --------------- | ---- | --------------------------- |
| **Volume Flow** | m³/h | Air volume being filtered   |
| Label           | —    | "Air volume being filtered" |

### Filter Status Card

Filter health and cleaning information:

| Field                | Description                |
| -------------------- | -------------------------- |
| **Filter Cleanings** | Total self-cleaning events |
| Label                | —                          |

{% hint style="info" %}
Notes:

* Shows cumulative cleaning cycles
* Higher count indicates active usage
* Normal operation includes regular cleaning
  {% endhint %}

### Service Due Card

Maintenance tracking:

| Field                   | Description               |
| ----------------------- | ------------------------- |
| **Operating Hours**     | Total device running time |
| **Hours Until Service** | Time until maintenance    |
| **Service Progress**    | Percentage toward service |

Visual elements:

* Progress bar showing service status
* "h operated" label for total hours
* "hours remaining" label for service countdown

{% hint style="warning" %}
Service Warnings:

* Normal: Progress bar only
* ≥90% to service: "Service recommended soon" message
* Service overdue: Critical warning
  {% endhint %}

## Status Display

### Device Status Badge

| Badge             | Meaning                    |
| ----------------- | -------------------------- |
| **Online - On**   | Connected and running      |
| **Online - Off**  | Connected but powered down |
| **Online - Idle** | Connected, standing by     |
| **Offline**       | Not connected              |
| **Error**         | Error code detected        |

### Error Display

When an error is detected:

* "Service Required" alert
* Error code shown
* Error description

## Real-Time Updates

Dashboard updates on:

* Device data transmission
* State changes
* Error conditions

## Offline State

When offline:

* Last known values shown
* "Offline" badge displayed
* Last seen timestamp visible

## Key Metrics Summary

Quick reference for operators:

| Metric          | Good               | Warning           |
| --------------- | ------------------ | ----------------- |
| Status          | On/Off as expected | Error state       |
| Volume Flow     | Normal range       | Zero when running |
| Cleaning Cycles | Incrementing       | Not changing      |
| Service         | >10% remaining     | ≤10% remaining    |

## Related Documentation

* [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) - Volume flow over time
* [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Start/Stop control
* [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - System information


---

# 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:

```
GET https://docs.kemperconnect.de/asset-types/cleanairtower/dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.