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

# overview

AirDome is KEMPER's air filtration tower system, designed for large-scale air cleaning in industrial environments. It features a self-cleaning filter system with automated maintenance.

## Device Identification

| Property        | Value                |
| --------------- | -------------------- |
| **Slug**        | `airdome`            |
| **Type**        | Air Filtration Tower |
| **Filter Type** | Self-Cleaning        |

## Purpose

AirDome units are designed to:

* Filter large volumes of air in industrial halls
* Remove welding fumes and particulate matter
* Operate with automatic filter cleaning
* Integrate with air quality sensors for automated control

## Key Measurements

### Motor Status

| Measurement       | Unit    | Description                                     |
| ----------------- | ------- | ----------------------------------------------- |
| **Motor Running** | Boolean | Current motor operating state (Running/Stopped) |
| **Motor Power**   | kW      | Current power consumption                       |

### Air Flow

| Measurement     | Unit | Description                        |
| --------------- | ---- | ---------------------------------- |
| **Volume Flow** | m³/h | Air volume being filtered per hour |

### Filter Status

| Measurement          | Unit  | Description                         |
| -------------------- | ----- | ----------------------------------- |
| **Filter Pressure**  | Pa    | Pressure differential across filter |
| **Filter Cleanings** | Count | Total automatic cleaning cycles     |

### Service

| Measurement             | Unit | Description                      |
| ----------------------- | ---- | -------------------------------- |
| **Operating Hours**     | h    | Total motor running time         |
| **Hours Until Service** | h    | Time remaining until maintenance |

## Status Indicators

| Status      | Description                             |
| ----------- | --------------------------------------- |
| **Running** | Motor actively operating, filtering air |
| **Stopped** | Motor not running                       |
| **Idle**    | Online but not actively filtering       |
| **Error**   | Device has reported an error code       |

## Error Codes

AirDome reports both errors and warnings.

### Errors (FEHLERCODE)

| Code | Description                  |
| ---- | ---------------------------- |
| 0    | No error (OK)                |
| F90  | Frequency inverter error     |
| F94  | Critical filter pressure     |
| F95  | Control error                |
| F96  | Compressed air not connected |

### Warnings (WARNING)

| Code | Description              |
| ---- | ------------------------ |
| 0    | No warning               |
| SER  | Maintenance overdue      |
| A03  | Filter pressure too high |
| A04  | No flow rate calculation |

## Device Tabs

When viewing an AirDome device:

| Tab       | Description                     | Documentation                                                        |
| --------- | ------------------------------- | -------------------------------------------------------------------- |
| Dashboard | Current status and measurements | [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) |
| History   | Performance history charts      | [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8)   |
| Functions | Start/Stop control              | [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) |
| License   | License management              | [License](file:///common/license.md)                                 |
| Settings  | Error codes and info            | [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b)  |

## Automation Target

Automation flow example:

{% stepper %}
{% step %}

### Trigger: Elevated PM10

* AirWatch sensor detects elevated PM10.
* Automation rule triggers AirDome start.
  {% endstep %}

{% step %}

### Monitoring: PM10 Falls

* PM10 falls below threshold.
* Automation rule triggers AirDome stop.
  {% endstep %}
  {% endstepper %}

See [Automation Rules](file:///automation/rules.md) for configuration.

## Scheduler Support

AirDome supports time-based scheduling:

* Define operating hours
* Set days of week
* Automatic on/off control

See [Schedulers](file:///automation/schedulers.md) for setup.

## Service Intervals

AirDome tracks service requirements:

* Operating hours counter
* Hours until maintenance
* Service progress percentage
* Warning at 14 days remaining
* Critical at 0 days remaining

## Related Documentation

* [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current measurements
* [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Start/Stop control
* [Error Codes](file:///reference/error-codes.md) - Complete error reference


---

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