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

# functions

The Functions tab provides remote control and data management capabilities for the self-cleaning Clean Air Tower.

## Accessing Functions

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

## Device Control

### Available Functions

| Function                | Description                       |
| ----------------------- | --------------------------------- |
| **Start Tower**         | Turn on the filtration system     |
| **Stop Tower**          | Turn off the filtration system    |
| **Request Data Update** | Force immediate data transmission |

### Start Tower

Initiates air filtration.

{% stepper %}
{% step %}

### Start Tower — Initiate air filtration

* Click "Start Tower" button
* Confirmation modal appears
* Confirm to execute
* Device begins filtering
* Status updates to "On"
  {% endstep %}
  {% endstepper %}

### Stop Tower

Stops air filtration.

{% stepper %}
{% step %}

### Stop Tower — Stop air filtration

* Click "Stop Tower" button
* Confirmation modal appears
* Confirm to execute
* Device stops filtering
* Status updates to "Off"
  {% endstep %}
  {% endstepper %}

### Request Data Update

Forces immediate data transmission.

{% stepper %}
{% step %}

### Request Data Update — Force immediate measurements

* Click "Request Data Update" button
* Device sends current measurements
* Dashboard updates with fresh data
  {% endstep %}
  {% endstepper %}

Use when:

* Data seems stale
* Verifying current status
* After configuration changes

## Function Execution Modal

### Confirmation Dialog

| Element       | Description            |
| ------------- | ---------------------- |
| Function name | Action to be performed |
| Device name   | Target device          |
| Warning       | Confirmation prompt    |
| Buttons       | Confirm / Cancel       |

### Execution States

| State     | Display            |
| --------- | ------------------ |
| Idle      | Buttons available  |
| Executing | Loading spinner    |
| Success   | Success message    |
| Error     | Error with details |

## Remote Control Notes

### Timing

* Commands may take seconds to reach device
* Status update may be delayed
* Refresh if status doesn't update

### Requirements

* Device must be online
* Commands fail if offline
* Check connectivity first

### Safety

* Ensure safe conditions
* Verify area is clear
* Follow safety procedures

## Automation Alternative

Instead of manual control, consider:

### PM-Based Automation

* AirWatch monitors PM levels
* Rule triggers tower on high PM
* Rule stops tower on low PM

### Time-Based Scheduling

* Define operating hours
* Automatic on/off
* Day-of-week configuration

See:

* [Automation Rules](file:///automation/rules.md)
* [Schedulers](file:///automation/schedulers.md)

## Error Handling

### Command Failed

If a function fails, follow these steps.

{% stepper %}
{% step %}

### Command Failed — Troubleshooting steps

* Error message displayed
* Verify device online
* Check network
* Try again
  {% endstep %}
  {% endstepper %}

### Compressed Air Error

If E03 error:

* Check air supply connected
* Verify adequate pressure
* Device needs air for cleaning

## Permissions

Requires:

* Member or Admin role
* Active license
* Device online

Viewers cannot execute functions.

## Related Documentation

* [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current status
* [Automation Rules](file:///automation/rules.md) - Automated control
* [Schedulers](file:///automation/schedulers.md) - Time-based control


---

# 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/cleanairtower/functions.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.