> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/widgets/vordefinierte-widgets/schalter.md).

# Switch

The "Switch" widget makes it possible to switch one or more devices between two states.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/MZDED4FSrxYjcPpDqPb5/04CE2FAE-3CDD-4F28-91BB-EB4AE614825B.png" alt=""><figcaption></figcaption></figure></div>

## When should this widget be used?

Switches should be used if you want to switch an asset exclusively between two states (e.g. "On" and "Off"). A likely use case is lamps.

However, if you want to control dimmable lamps, use the widget -> Lamp control.

## Configure Widget

{% @supademo/embed url="<https://app.supademo.com/demo/KS_36muoBJWvH6P0wCVdI>" demoId="KS\_36muoBJWvH6P0wCVdI" fullWidth="true" %}

1. Make sure you are in the "Dashboard" menu
2. Click "Add widget"
3. Click "Input"
4. Click on "Switch"
5. Select the primary asset. The name of this asset will appear in the widget title bar.
6. Select the asset you want to control via the switch.
7. (Optional) Give the asset a name
8. Select the target value
9. Select the current value
10. (Optional) Repeat the previous steps to create switches for additional assets
11. Optional: Choose how much space your new widget should take up on the dashboard.
12. Click "Add widget"

## Using the widget

### Overview

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/R6TZJ7JQdDkozkDBxqLb/835BFCBA-60AF-4BF1-91A7-916FDABE925E.png" alt=""><figcaption><p>The "Switch" widget in detail</p></figcaption></figure></div>

<table><thead><tr><th width="81.33333333333331"></th><th width="275"></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Widget title</td><td>Title of the widget. Is influenced by the selection of the "primary asset".</td></tr><tr><td><strong>[B]</strong></td><td>Icon</td><td></td></tr><tr><td><strong>[C]</strong></td><td>Individual assets</td><td>The individual assets that were added to the widget</td></tr><tr><td><strong>[D]</strong></td><td>More options</td><td></td></tr><tr><td><strong>[E]</strong></td><td>Individual switches</td><td></td></tr></tbody></table>

### Operate Widget

Each added individual asset **\[C]** is its own switch **\[E]** assigned.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/uibJQtnIenfDOwhMt7TQ/98D43939-AC3D-414E-B546-1C9ECC35A7C5.png" alt=""><figcaption><p>Left: switch in the "ON" state<br>Right: switch in the "OFF" state</p></figcaption></figure>

* Click a switch that is in the "ON" state to set this switch to "OFF"
* Click a switch that is in the "OFF" state to set this switch to "ON".


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/english-v14/documentation/widgets/vordefinierte-widgets/schalter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.