> 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-adapter/getting-started/leds.md).

# The LEDs explained

The colour shows the link mode.

| Colour | Link mode         |
| ------ | ----------------- |
| Green  | 2.4G              |
| White  | Wired             |
| Blue   | Bluetooth gamepad |

| Pattern                  | Meaning                                                    |
| ------------------------ | ---------------------------------------------------------- |
| Swoosh across the LEDs   | Looking for the dongle, or waiting for a computer or phone |
| Two flashes, then steady | Connected                                                  |

When connected to the dongle, one LED stays lit to show the console port the dongle is plugged into. Looking at the USB-C end, port A is the LED on the far right, next to the Power button, and port D is the LED on the far left, next to the Sync button. See [Hardware overview](/manuals/bitlink-dc-adapter/getting-started/hardware-overview.md). In Bluetooth gamepad mode all four LEDs stay lit.

You can change the colours, patterns and brightness, or give each player port its own colour. See [LED settings](/manuals/bitlink-dc-adapter/webui/led-settings.md).

Update mode has its own patterns. See [Update mode and recovery](/manuals/bitlink-dc-adapter/firmware/recovery.md).


---

# 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-adapter/getting-started/leds.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.