> 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/allegion-engage-interface/allegion-engage-configuration/commissioning-engage-doors-from-the-allegion-engage-mobile-app/performing-factory-resets-on-locks.md).

# Performing Factory Resets on Locks

A Factory Default Reset (FDR) returns the lock to the original settings as shipped from the factory. This removes configurations, databases, and requires the lock to be re-captured.

**Note:** The FDR process does not remove the lock from your Engage account.

Follow the appropriate procedure below for the type of lock you want to perform a factory default reset on.

### NDE and LE locks

1. Open the battery cover.
2. Press the button under the pin hole about the batteries.
3. Press and hold the FDR button for five seconds.

   The NDE will blink green two times and beep two times.
4. Turn the inside lever three times within 20 seconds.

   The LED will blink red and the lock will beep with each turn.

   The factory default reset is complete when you hear one long beep.
5. Install the cover and connect to the lock.

### Control Locks

1. Disconnect the batteries for at least ten seconds.
2. Reconnect the batteries.
3. Wait for the lock to beep and flash three times.
4. Within ten seconds, rotate the interior tail piece back and forth two times.

   The lock will flash one long green flash and beep one long beep to indicate the process was successful.


---

# 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/allegion-engage-interface/allegion-engage-configuration/commissioning-engage-doors-from-the-allegion-engage-mobile-app/performing-factory-resets-on-locks.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.
