> 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/site-installation/mobile-connect/configuring-a-reader-for-mobile-connect.md).

# Configuring a reader for Mobile Connect

### Introduction

This procedure describes how to configure a reader for Mobile Connect.

***

### Before you begin

* HBUS Readers that support Bluetooth® have the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b8e873fb541db09de3926e93c28d6de43ff718a7%2Fbleicon.png?alt=media) icon printed on the reader fascia. HBUS Terminals that support Bluetooth® have Bluetooth® listed on the Information screen. To display the Information screen, press and hold the '#' key for 3 seconds.
* The HBUS Reader or HBUS Terminal must be connected to a Controller 6000 or 7000. Both the reader or terminal and the door must be assigned to the Controller. If a mobile credential is used to request access at a door not assigned to a Controller 6000, the alarm " *Mobile access unsupported - Door requires Controller* " will be generated.
* Assigning more than one Bluetooth® enabled reader to the same side of the Door is not supported.
* Assigning the same Bluetooth® enabled reader to multiple Doors is not supported; multiple Outputs will not be triggered. Use a Logic Block to trigger multiple Outputs from a Door.

Operators require the "Edit Site" privilege in the appropriate division to be able to create, edit and delete Bluetooth® enabled readers.

**Note:** The "View Site" privilege in the appropriate division will allow an operator to view (but not edit) Bluetooth® enabled readers.

***

### Configuration

To set up an additional Mobile Credential Type, perform the following procedures in Gallagher Configuration Client:

1. Complete the HBUS Reader configuration as per the procedure for [Creating Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-readers.md), and then go to Step 2 of this procedure.

   **Note:** If configuring an HBUS Terminal, refer to the procedure [Configuring an HBUS Terminal](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-hbus-terminals/configuring-an-hbus-terminal.md), and then go to Step 2 of this procedure.
2. Click each tab in turn to configure a reader for Mobile Connect:

<details>

<summary>Mobile Access Settings tab</summary>

1. Click the **Mobile Access Settings** tab.

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

   <table><thead><tr><th width="168">Field</th><th>Description</th></tr></thead><tbody><tr><td>Mobile Connect NFC</td><td>Select an option from the drop-down list. When ON, Android devices will use NFC to request access at the reader. NFC applies to Auto Connect only. If the user has NFC disabled on their device, their device will revert to Bluetooth® to make the access request. The default uses the <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-access-settings.md">Server Properties</a> settings, which is OFF by default.</td></tr><tr><td>Second factor always required for mobile</td><td>Select an option from the drop-down list. When ON, presentation of a second authentication factor is required at the reader at all times, unless the access mode is set to ‘Free-No PIN’. The default uses the <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-access-settings.md">Server Properties</a> settings, which is OFF by default. Second factor authentication is enforced for mobile credentials only.<br><br><strong>Note:</strong> If the access mode is set to ‘Free-No PIN’ and a personalised action has been assigned to the user, a second authentication factor will be required. Refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/configuring-personalised-actions-for-access-zones.md">Configuring Personalised Actions for Access Zones</a> for details on how personalised actions work.<br>NFC works over a short range, hence a user may take their device out of range to provide their second factor. When this happens, the App displays an icon encouraging the user to re-enter the field.</td></tr><tr><td>Use site default Bluetooth low energy settings</td><td>When checked, the reader will use the Bluetooth low energy settings, configured on the <strong>Mobile Access Settings</strong> tab in the <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-access-settings.md">Server Properties</a>. Default is ON.</td></tr><tr><td>Turn on Bluetooth low energy technology</td><td>When checked, Bluetooth® comms are enabled for the reader. Default is OFF.</td></tr><tr><td>Advertise reader name</td><td>When checked, the reader's name will be displayed in the Gallagher Mobile Connect App. Default is ON.<br>If the reader has been configured with a Short Name, the Short Name will be used. Names longer than 26 characters will be truncated. If set to OFF, a generic identifier incorporating part of the reader's HBUS serial number will be shown in the Gallagher Mobile Connect app, (e.g. Reader: 12345).</td></tr><tr><td>Transmit Power</td><td><p>Controls the Bluetooth® signal strength. Default is -26 dBm.<br><br><strong>Notes:</strong></p><ul><li>Increasing the transmit power will increase the Bluetooth® connection distance.</li><li>Reducing the transmit power can be used to prevent closely located readers from interfering with each other Bluetooth® communications.</li></ul></td></tr><tr><td>Auto connect range</td><td><p>When checked, all mobile devices will automatically initiate an access request when they sense a signal stronger than this value. Lower values indicate a stronger signal, and thus higher values will allow access from farther away. Default is 45 dBm.<br>Auto connect will be disabled when:</p><ul><li>the Door that this reader is assigned to has no Access Zone assigned to it, or</li><li>the Door that this reader is assigned to has one Access Zone that is in access mode 'Free-No PIN', or</li><li>the reader is assigned to an Elevator with all floors in access mode 'Free-No PIN'.</li><li>the Door's Emergency Release has been triggered.<br><br><strong>Note:</strong> Auto connect may not be suitable for all reader installations, (e.g. if a user is situated close to the reader, continual connection attempts from the reader will reduce the device's battery).</li></ul></td></tr><tr><td>Manual connect range</td><td>When checked, the user will be able to manually initiate an access request from this range (which must be a longer range than the auto-connect range), using the Gallagher Mobile Connect App. Default is 64 dBm.</td></tr></tbody></table>

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

   **Notes:**

   * Increasing the path loss value will increase the reader's Bluetooth® read range.
   * Consideration should be given to the installation environment, as environmental factors may reduce the reader's Bluetooth® read range. It is advised that each reader's transmit power and connection ranges are individually calibrated. The Gallagher Mobile Client App can be used to calibrate the signal strength for each reader.
   * Consideration should be given to the signal strength of readers that are installed back-to-back. For example, a reader installed at the front door is set to ‘Secure-PIN’ and the exit reader on the other side of the wall is set to ‘Secure’, a user could connect to the exit reader and gain entry without entering a PIN.
   * If the reader is assigned to an Elevator, the user will be required to enter a second authentication factor, if any of the Elevator's floors require a PIN.

</details>

<details>

<summary>Bluetooth Actions tab</summary>

1. Click the **Bluetooth Actions** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6bdd9dc9233e0cae58e8806f02f42bee2d8c4615%2Fbluetoothactionstab.png?alt=media)
2. From the Hardware List Window, select the Outputs you wish to trigger (On/Off) using the Mobile Connect App.

   Drag and drop them into the **Bluetooth Actions** tab window.

   The Output Name will be used within the Mobile Connect App. To use a different name within the Mobile Connect App, enter a **Label** for the Output. Maximum of 20 characters.

   If you require a non-authorised user, (i.e. a user who has not been assigned the "Lock and unlock access zones" privilege for the Door’s Access Zone) to be able to trigger an Output, check the **Available to All** checkbox for the Output. The Output will appear in the Mobile Connect App.

   **Notes:**

   * In order to perform actions at the reader, the reader must be configured for Manual Connect.
   * NFC cannot be used to perform an action at a reader, only Bluetooth® comms.
   * When a second authentication factor is required, the second factor must be presented before the action can be requested. The user will have up to 30 seconds to perform the action without needing to re-enter their second factor.
   * Actions are not available when the reader is assigned to an Elevator. Entry to the Access Zone will be the only action available.
   * Other users can continue to request access at the reader while a user decides which action to perform. Bluetooth® comms are only used to perform the privilege check and the action.
   * A maximum of 10 Outputs can be assigned to a reader.
   * An Output whose state should be changed by a Command Centre operator only, should not be assigned here.
   * An Output can be configured to perform various functions in Command Centre when triggered, (i.e. an Action Plan assigned to the Output contains a Macro that when triggered perform various actions in Command Centre).
3. Once you have all the Outputs you require in the window, you can re-order the Outputs by using the **up** and **down** arrow buttons to the right of the window. The order you sort the Outputs in here will be the order they appear in the Mobile Connect App.

</details>

3. Click **OK** to save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/site-installation/mobile-connect/configuring-a-reader-for-mobile-connect.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.
