> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/open-supervised-device-protocol-osdp-integration/moving-osdp-readers-between-controllers.md).

# Moving OSDP Readers between Controllers

To move an ODSP Compliant Reader from one Controller to another (within the same site) simply move that Reader FT Item from one Controller to another and swap the physical connections.

Should you need to move an OSDP Compliant Reader between sites, the reader will need to be placed into installation mode (as specified by the manufacturer), as it will have a secure key loaded. When the reader is configured on its new controller, it will get an "Encryption Keys tampered" status/event because communications are attempted to be initialised with the secure key, however it will not relate to the new FT Items Master Key.

A **Re-initialise encryption** override will need to be performed which will effectively put the controller into Installation mode, so a new key can be negotiated. The same procedure is used for replacing a reader, as it would result in the same issue, (i.e. either the reader had a secure key or it did not, but it was an incorrect one).


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/open-supervised-device-protocol-osdp-integration/moving-osdp-readers-between-controllers.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.
