> 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/developers/relaykeys-daemon.md).

# Server (Daemon) reference

The *server* (*RPC server* or *daemon* as we sometimes refer to it) is the component that opens up a connection to the COM port and sends the correct AT command to the board. You can control it with some arguments

When you use our installer it installs this as a service. If you run the code without installing (or you turn the service off for some reason) you can run it as `relaykeysd.py` or `relaykeysd.exe` 

## --noserial

Run the daemon and dont try and connect to hardware. If you are on linux/MacOS you can fake a serial port [following these tips](/products/relaykeys/installation/supported-boards.md#developing-without-a-board). If you are on Windows just fix a COM port in the config file or use the `--dev` option - just choose a non-existent COM port

## --dev

Force the daemon to use a COM port rather than auto detecting one.

e.g.

`python relaykeysd.py --noserial --dev=COM7`

For more info see [here](https://github.com/AceCentre/RelayKeys/blob/master/developers/relaykeys-cfg.html#dev-defining-your-port-of-the-relaykeys-hardware)

## --debug

Sets a more verbose debugging output on the console.

## --pidfile=file

Give a pidfile for the daemon to crate - or link to one.

**Default: pidfile**

## --logfile=logfile

File to use as a log file for the debugging messages.

**Default: logfile**

## --config=configfile

File to use as a config file. For more info see [here](/products/relaykeys/developers/relaykeys-cfg.md)

**Default: relaykeys.cfg**

## --**ble\_mode=True|False**

Use the daemon in wireless (ble\_mode) or wired mode.

**Default: false**


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.acecentre.org.uk/products/relaykeys/developers/relaykeys-daemon.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.