> For the complete documentation index, see [llms.txt](https://docs.acecentre.org.uk/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecentre.org.uk/products/relaykeys/installation/connecting-with-relaykeys/wireless-mode.md).

# Wireless Mode

{% hint style="warning" %}
Warning: This mode definitley is slightly more laggy and can be fiddly to setup. 
{% endhint %}

Note that this mode is useful on devices where you can't plug anything into your device. The setup can feel *strange -* what we need to do is tell your relaykeys hardware the device to connect to.

1. Plug in device and follow instructions [as above](#plug-in-your-relaykeys-stick-and-pair-with-a-computer-wired-mode)
2. Pair the main AAC/Host device with it. So pair the computer you have attached it to with RelayKeys hardware. This can feel a bit strange - you are connecting the hardware to the same machine you are on. See [here](#undefined-1) for how to put it into pairing mode.
3. Disconnect the relaykeys hardware. In your bluetooth settings you actually need to click on the item and "Remove" device. (NB: If you cant do this it might be because you need to be an admin. The trick is open the Control Panel -> Devices & Printers -> Relaykeys -> Right click, Remove and you will be asked for an Admin password)
4. Plug relaykeys into a power source - away from the computer. Your RelayKeys may have a battery or you might need to plug into a wall USB power source.
5. Double press the User switch It should now shine a nice <mark style="color:blue;">blue</mark> colour!
6. Run RelayKeysd with `--ble_mode` See [here](/products/relaykeys/developers/relaykeys-daemon.md) for more details


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.acecentre.org.uk/products/relaykeys/installation/connecting-with-relaykeys/wireless-mode.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 `build a script that syncs our docs to a CMS` 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.