> 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/command-centre-configuration/upgrading-engage-firmware.md).

# Upgrading Engage Firmware

### Introduction

Upgrading Engage firmware can be done via Command Centre for Gateway versions 1.52.16 and above. For customers using an older version they will need to manually upgrade their devices to 1.52.16 or later in order to take advantage of upgrading firmware via Command Centre.

This procedure for upgrading firmware is split into two parts, as follows:

* Creating an Engage Software item
* Assigning Engage Software to the Gateway and devices

### Procedure

To configure Engage firmware, perform the following procedures in Gallagher Configuration Client:

#### Creating an Engage Software item

1. Click **Configure** from the menu bar, then **Device Software**.

   The **Device Software** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** and select **New\...Engage Software**.

   By default the **General** tab displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9e87e50c64ab88dce3494966e41892d0b00aefec%2Fallegionengage_devicesw.png?alt=media)
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Version** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ef31e78195a375a9062c4c74af7be9edbe446fa8%2Fallegionengage_devicesw_versiontab.png?alt=media)
5. Click the **Browse…** button and locate the Engage Firmware package (\* **.gglsec** ) on your computer.
6. Highlight the file once located and click the **Open** button.

   The version of software displays in the **Software Version** field.

   The name of any software selected will automatically populate the **Name** field on the **General** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-feeb46500fa8dae562ba0095c0bcc991ecabf1a1%2Fallegionengage_devicesw_generaltab.png?alt=media)

   When an Engage Firmware package is selected, once the software has downloaded, the individual firmware versions for the different device models that are included in the ENGAGE file package display on the **Version** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-585a0b2a7b31b742968483fd1ed196c42a0b5c64%2Fallegionengage_devicesw_versiontab_populated.png?alt=media)
7. Click the **Notes** tab if you want to add a note(s) about this Engage Software item.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
8. Click **OK** to save the Engage Software item.

#### Assigning Engage Software to the Gateway and devices

9. Click **Configure** from the menu bar, then **Engage**.

   The **Engage** List Window opens.
10. **Right click** on the Engage Gateway to have firmware applied to it, and select **Properties**.

    By default the **General** tab displays.
11. Click the **Software** tab.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2880396fbfff3c64f826202c46bfe29e14449d49%2Fallegionengagegateway_softwaretab1.png?alt=media)
12. Select the required firmware version from the **Update To** drop-down list.

    The **Upgrade Now** button and **Schedule Update** checkbox both become enabled, and the "Update To" column is populated.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f2418bc601cad460611aff44676167833ae5d67b%2Fallegionengagegateway_softwaretab3.png?alt=media)

    This gives you the option to either update the firmware now or schedule it for another time.

    **Note:** During a firmware update, the Gateway pushes the firmware one by one to each device and no door files can be sent while this is occurring. Updates can take up to 40 minutes per device.
13. Do you want to update the firmware now or schedule it for another time?

    <table><thead><tr><th width="94">If update...</th><th>then...</th></tr></thead><tbody><tr><td>later,</td><td><ol><li><p>Tick the <strong>Schedule Update</strong> checkbox.</p><p>The Date and Time fields become enabled.</p></li><li><p>Enter the date and time you want the upgrade to occur, and click <strong>Apply</strong>.</p><p>An event is generated indicating the date and time the update is scheduled for, and the following message displays:</p><p><em>"Software update cannot be cancelled once started. Do you wish to continue?"</em></p></li><li>Click <strong>OK</strong> to close the message dialog.</li></ol></td></tr><tr><td>now,</td><td><ol><li><p>Click the <strong>Upgrade Now</strong> button. The following message displays:</p><p><em>"Software update cannot be cancelled once started. Do you wish to continue?"</em></p></li><li><p>Click <strong>OK</strong> to close the message dialog.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c78da5f1ecb58fd669a8cbe2907997f20859b0f3%2Fallegionengagegateway_softwaretab4.png?alt=media" alt=""><br>The status (in the "Status" column) for each device changes as the firmware upgrade progresses through the queue.<br>Once complete, the versions in the "Version" column will match those in the "Update To" version on the <strong>Software</strong> tab of the Gateway.</p><p><strong>Notes:</strong></p><ul><li>Similar statuses will appear on the <strong>Status and Overrides</strong> tab of the Gateway/devices also.</li><li>If a door already has the latest firmware configured, it will show <em>"Update successful"</em> afterwards, even though it was never actually updated.</li><li>If the currently selected version does not allow downgrading, this will be displayed as a prompt. Once the selected version is installed, it will be persisted as a message on the <strong>Software</strong> tab of the Gateway. Command Centre will still allow firmware to be downgraded, even if the firmware version does not allow this, however the downgrade will eventually fail.</li></ul></li></ol></td></tr></tbody></table>
14. Click **OK** to exit the Gateway properties and save your changes.

### Result

A new Engage Software item has been created, and a new version of the Engage Firmware has been added to Engage Gateway and devices.


---

# 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/command-centre-configuration/upgrading-engage-firmware.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.
