> 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/products/cc-software/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/middleware-framework-ademco-685-plugin.md).

# Middleware Framework - Ademco 685 plugin

Import Ademco 685 events and mappings through the Middleware Framework.

The Ademco 685 plugin lets a third-party system **input events into Command Centre** as events or alarms. It is supplementary to the Ademco 685 install note. The licence must contain `[Plugin] Plugin(n)=Ademco-685`.

> ⚠️ **Perform a database backup first. The event-mapping import is irreversible.**

## Mapping files

Mapping files (`ContactID_Default.xml`) are on the install media under `Utilities/System Interfaces/Ademco x.xx.xx/Mappings`. Place them on **both** the middleware computer and the server.

## Import procedure

Use **`CCFTExternalEvents.exe`** (in `…\Command Centre\Bin\`). It has a GUI, which is easier than the release note's command-line method.

1. Log in with Command Centre credentials.
2. Choose **Import Configurations** and browse to `…\Command Centre\Mappings\ContactID\`.
3. Import `Events_Default.xml`.
4. Choose the External Event Groups (default 0).
5. Choose **apply**. This is irreversible, and a pop-up warns you.
6. Edit the events.
7. Choose **Export Event Mappings** as `Events_Default_out.xml`.
8. Copy it to the middleware machine's `…\FTCAPI\Middleware Framework\Plugin\Mappings\ContactID\`.

## Expected files

* **Server** `…\Command Centre\Mappings\ContactID\`: `Events_Default.xml` and `Events_Default_out.xml`.
* **Middleware** `…\Middleware Framework\Plugin\Mappings\ContactID\`: `ContactID_Default.xml` and `Events_Default_out.xml`.

Extra files cause errors or wrong functionality.

***

🔗 **Related**

* [Controller API - Server and Middleware](/knowledge-hub/products/cc-software/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/controller-api-server-and-middleware.md). The middleware this plugin runs under.


---

# 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/products/cc-software/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/middleware-framework-ademco-685-plugin.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.