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

# dashboard

The AirDome dashboard provides real-time monitoring of the air filtration system, including motor status, air flow, filter condition, and service status.

## Dashboard Layout

### Header Section

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

### Motor Status Card

Displays motor operating state:

| Field           | Description               |
| --------------- | ------------------------- |
| **Status**      | Running or Stopped        |
| **Motor Power** | Current consumption in kW |

Visual indicator:

* Green icon when running
* Gray icon when stopped
* Red icon on error

### Volume Flow Card

Shows current air filtration rate:

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

Displays:

* Current flow rate value
* Unit label (m³/h)
* Trend indicator if available

### Filter Status Card

Filter health and cleaning information:

| Field                | Unit  | Description           |
| -------------------- | ----- | --------------------- |
| **Filter Pressure**  | Pa    | Pressure differential |
| **Filter Cleanings** | count | Total cleaning cycles |

{% hint style="info" %}
Higher filter pressure indicates loading. Cleaning cycles reflect filter utilization.
{% endhint %}

### Service Due Card

Maintenance tracking:

| Field                   | Description                      |
| ----------------------- | -------------------------------- |
| **Operating Hours**     | Total hours motor has run        |
| **Hours Until Service** | Time remaining until maintenance |
| **Service Progress**    | Percentage toward next service   |

Visual elements:

* Progress bar showing service status
* Warning indicator if service due soon
* "Service recommended soon" message at ≥90%

{% hint style="warning" %}
When Service Progress is ≥90% the dashboard shows "Service recommended soon" and displays a prominent warning indicator.
{% endhint %}

## Status Display

### Device Status Badge

| Badge                | Meaning                          |
| -------------------- | -------------------------------- |
| **Online - Running** | Connected and actively filtering |
| **Online - Stopped** | Connected but motor not running  |
| **Online - Idle**    | Connected, standing by           |
| **Offline**          | Not connected                    |
| **Error**            | Error code detected              |

<details>

<summary>Error Display</summary>

When an error is detected:

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

</details>

## Real-Time Updates

The dashboard updates when:

* Device transmits new data
* Motor state changes
* Error conditions occur

<details>

<summary>Offline State</summary>

When device is offline:

* Last known values displayed
* "Offline" badge shown
* Timestamp of last communication

</details>

## Related Documentation

* [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) - Performance over time
* [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Start/Stop control
* [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - Error codes and configuration


---

# 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/dashboard.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.