# Outputs

#### What Are Outputs?

**Outputs** are the things you control with your **Command(s).**

Each output is displayed as a square on the Control Tab.  

By default, there is one Output, with a smiley face emoji.  When this Output is activated, it says "hello".

<figure><img src="/files/b9LcOnmyVjhvvPBCzAzT" alt="" width="188"><figcaption></figcaption></figure>

### Enabling Outputs

To start using Outputs:

1. Tap the **Start** button.

When an Output is enabled:

* The border lights up
* This means it is ready to be used
* The name of the Command appears at the top of the Output

<figure><img src="/files/j7x2fWiTKfF2k1UW0NLo" alt="" width="188"><figcaption></figcaption></figure>

### Activating Outputs

When an Output is activated, something happens.

For example, an Output might:

* Play a sound
* Say a word
* Turn on a smart home device

(You can learn more in [Output Options](/think2switch-knowledge-guide/think2switch-2.5/setup-guide/control/output-options.md).)

#### Using your Command

Outputs are activated using your Command.

When you perform your Command:

* You will see the signal strength on the Output
* When the signal goes above the dashed line (the **threshold)**, the Output activates

<figure><img src="/files/8ysUEE6DwAV1D4yrnyqF" alt="" width="188"><figcaption></figcaption></figure>

#### Stopping an Output

To stop activating an Output:

* Stop performing your Command
* Relax and **return to Rest**

To disable all Outputs:

* Tap the **Stop** button

### Manual activation

You can also activate an Output by tapping it.

This is useful to:

* Check that the Output is working
* Test sounds or actions


---

# Agent Instructions: 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://think2switch.gitbook.io/think2switch-knowledge-guide/think2switch-2.5/setup-guide/control/outputs.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.