> For the complete documentation index, see [llms.txt](https://8bitmods.gitbook.io/manuals/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://8bitmods.gitbook.io/manuals/bitlink-dc-dongle/webui/led-settings.md).

# LED settings

The **LED** page sets the LED for each input mode (**2.4G**, **Bluetooth**, **USB**) and each state (**Pairing**, **Waiting**, **Connected**).

1. Select the mode and state tabs.
2. Under **Behaviour**, choose **Default** for the built-in look, or **Override** to choose your own **Colour** and **Pattern**.
3. Set the **Brightness**.
4. Select **Save**.

<figure><img src="https://3745350575-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxE7fgXjmB9AkNFHd2vW0%2Fuploads%2Fgit-blob-8158025fc5be22e39b15785c6a32eeb41efa2a5a%2Fled-page.png?alt=media" alt="LED page, 2.4G Connected, Default behaviour" width="616"><figcaption><p>Default</p></figcaption></figure>

<figure><img src="https://3745350575-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxE7fgXjmB9AkNFHd2vW0%2Fuploads%2Fgit-blob-70179c8a7a6d53c689a7592247b8e6e0bd92eb85%2Fled-override.png?alt=media" alt="LED page, 2.4G Connected, Override with colour, pattern and brightness" width="616"><figcaption><p>Override</p></figcaption></figure>

The patterns are **Steady**, **Pulse**, **Fast Pulse**, **Swoosh**, **Breathe** and **Rainbow**. Rainbow cycles through all colours, so it ignores the colour setting.

The LED previews each change, then returns to its current state about 3 seconds after your last change.


---

# 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://8bitmods.gitbook.io/manuals/bitlink-dc-dongle/webui/led-settings.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.