> 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/troubleshooting.md).

# Troubleshooting

> Below are solutions to some common issues that you may experience when working with RelayKeys.

{% hint style="info" %}
**AceCentre is a charity and we are providing this as-is. If you need something urgently and can pay we ask you to donate to us - or another developer to help fix your problem**
{% endhint %}

## Installation Issues

### I can install it - but when I send keystrokes nothing is appearing on the second device?

Try and go through these steps:

1. **Is your relaykeys stick properly attached?** Make sure the blue light is showing. If not you may have a loose connection somewhere.&#x20;
2. **Is it paired and connected?** - you will know this if the blue light is steady (*not* flashing) on the relaykeys stick
3. **check your COM port**. Lastly, it may be that the software cannot find the RelayKeys stick in its list of COM ports. [Read this guide](/products/relaykeys/developers/relaykeys-cfg.md#dev-defining-your-port-of-the-relaykeys-hardware) to configure and fix your COM port manually.
4. **Check your casing and spacing**. If you are using the command line applications, be careful - the application is case-sensitive. It should be *type:* and not *Type:* for example

### It was working all fine but now its not!

Is it paired and been shown to be connected with the receiving device? If so - and its still not sending text you may need to remove the Bluetooth AceRK device and then pair the AceRK again. To do this open RelayKeys-QT app on the sending device - click on "Add device" and then pair on the receiving device.&#x20;

### So I send LSHIFT,2 and I was expecting " but I get a @ - What gives?

Have a look at the [keyboard map.](https://docs.acecentre.org.uk/products/v/relaykeys/developers/reference-2#defining-a-keymap-c) You'll need to define/edit a keyboard map for the keyboard you are expecting it to be.&#x20;


---

# 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.acecentre.org.uk/products/relaykeys/troubleshooting.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.
