The current Openpath Jira and Confluence instances will be migrated to the MSI On-Premise solution from August 9th-11th, the current platform will be set to read-only and all future usage will be in the Avigilon Instance. Please ensure access to MSI Jira & MSI Confluence, both are accessible through OKTA. For additional information and details please refer to the Atlassian migration page

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 91 Next »

You can connect Allegion’s Schlage® Gateways and NDEB, LEB, and Control™ wireless locks to your Avigilon Alta system by using the ENGAGE app and the Open Admin app.

Note: Privacy Mode is supported for Allegion wireless lock integrations.

Note: Supported features and limitations for Allegion Schlage wireless locks.

To enable this feature, refer to How to enable features in Avigilon Alta Access.

Requirements

Note: The org’s Site in Alta Access must have an address in order to get accurate timestamps on Allegion events. Go to Sites > Site > Edit Site to enter an address.

Overview of setup

Note: You must perform these steps in the specified order.

  1. Install Gateways and locks (refer to Allegion documentation)

    1. Schlage LE Lock Installation Guide

    2. Schlage NDE Lock Installation Guide

    3. Schlage Control Deadbolt Installation Guide

    4. Schlage Control Interconnected Installation Guide

    5. Engage Gateway Installation Guide

  2. Present Configuration Card to the lock

  3. Accept the invitation to Allegion Site

  4. Add the Gateway in the ENGAGE app

  5. Add the lock in the ENGAGE app

  6. Link the lock to the Gateway

  7. Sync gateways and locks to Avigilon Alta

  8. Update firmware on gateways and locks

  9. Adjust lock settings in Avigilon Alta Access

  10. Create an entry with the wireless lock

  11. How to add a Gateway from another Org

Present Configuration Card to lock:

If you purchased locks outside of Avigilon Alta, and you’re using Openpath DESFire card credentials, present the appropriate Configuration Card to the lock within the first minute of powering on. A triple beep followed by a full reader reset indicates success.

(Open Admin) Accept the invitation to the Allegion Site:

  1. Open the Open Admin app first.

  2. Tap the name of the Org to which you’ll provision these locks and gateways.

  3. Tap 3rd Party Devices.

Note: This option is only visible if the Allegion integration is enabled. If you don’t see this option, contact your sales rep.

4. Tap Allegion Wireless Gateways (Schlage).

  1. You’ll receive an email invitation to the Allegion Site.

  1. Open your email app and accept the invitation.

  1. On the web page, accept Allegion’s terms and create an account using the email address associated with your Avigilon Alta account.

(ENGAGE) Add the Gateway:

  1. Open the ENGAGE app and log in.

  2. Tap on the plus sign to add a device.

  3. Tap on Gateway.

  4. Tap the gateway’s serial number.

  5. Enter a name for the gateway.

  6. For Gateway communication mode, tap IP.

  7. On IP Configuration, enable IP Behind Firewall and tap DHCP.

  8. On the IP Behind Firewall screen, enter the following:

    Server URL: https://ozone.prod.openpath.com 
CA Server URL: http://ozone.prod.openpath.com/cert

Note: These URLs must be entered correctly in order for the integration to work. If you entered them incorrectly during setup, you can edit them later by tapping on the Gateway > Settings > Host Configuration.

(ENGAGE) Add the Lock:

  1. Tap on the plus sign to add a device.

  2. Tap on the model of lock you’re commissioning (Avigilon Alta supports LEB, NDEB, and Control locks).

  3. The app will ask if you want to use default settings — tap Yes (you can adjust lock configurations later in the Avigilon Alta Access).

  4. Tap the lock’s serial number.

  5. Follow the in-app instructions for connecting the lock.

  6. Enter a name for the lock.

  7. (NDEB and LEB only) On the Select the lock function page, select Storeroom.

Note: If during the commission process, something goes wrong, the device name will show as "Captured" in both Alta Access and the Engage app, causing syncing to stop. To fix this, delete the device named "Captured", and factory default the device. After factory defaulting, re-add and recommission the device.

Note: If you select a different mode, the integration may not work. You cannot change the mode once the lock has been commissioned – if you select the wrong mode, you’ll need to delete and re-commission the lock.

8. Skip the Wi-Fi configuration step if able, since the lock will connect to the Internet via the Gateway. Some lock models might require that you specify a Wi-Fi configuration, in which case, you can enter an IP address like 8.8.8.8, since this will be overridden by the Gateway’s configuration.

(ENGAGE) Link the Lock to the Gateway:

  1. Tap on the gateway from the list of devices.

  2. Tap Linked Devices.

  3. Tap on the plus sign to link a lock.

  4. Tap on the name of the lock to link it to the Gateway.

Note: You may need to refresh this page or turn the lock handle to make the lock appear on this list. Also, make sure the cover is secured on the lock.

5. Back out of the app so you're no longer connected to the Gateway.

(Open Admin) Sync Gateways and Locks to Avigilon Alta:

  1. Open the Open Admin app.

  2. Tap the name of the Org to which you’ll provision these locks and gateways.

  3. Tap 3rd Party Devices.

  4. Tap Allegion Wireless Gateways (Schlage).

  5. Tap Sync Gateways.

  6. Review the list of gateways and locks.

Update firmware on the Gateways and locks:

  1. Go to https://control.openpath.com/login and log in. To access the European Alta Access, please go to https://control.eu.openpath.com/login.

  2. Go to Devices > Wireless Gateway.

    1. Under the Actions column, click Update Firmware next to each Gateway.

  3. Go to Devices > Wireless Locks.

    1. From this page, select locks and click Batch Actions to update the firmware.

Note: To downgrade Allegion Lock and Gateway firmware follow these steps.

Adjust lock settings in Alta Access:

Note: Settings are dependent on the lock model and configuration. To configure the following wireless lock function, set it during the commissioning process or post-installation using the Schlage ENGAGE mobile app (and not Alta Access):

  • Apartment mode - Supported in LEB and NDEB series locks only. Ensures the gateway-connected or No-tour connected lock remains open or closed, when the credential is scanned. The door doesn't automatically relock when unlocked, and thus, lock out the user.

    Confirm the 'Openpath does not support Toggle Credential' message during initial configuration. For more information, see the Schlage ENGAGE documentation.

To configure an NDEB or LEB lock:

  1. Go to https://control.openpath.com/login and log in. To access the European Alta Access, please go to https://control.eu.openpath.com/login.

  2. Go to Devices > Wireless Locks.

  3. Click on the name of the lock to edit it.

  4. Under Basic Settings, you can do the following:

    1. From the Power Failure dropdown, select how the lock will behave in the event of the battery failing.

      1. As Is – the lock will remain in the same state.

      2. Safe – unlocked.

      3. Secure – locked.

    2. Enable or disable the Beeper on the lock when a credential is scanned.

    3. Adjust the interior LED settings.

    4. Enable or disable the Invalid Card Audit, which logs invalid credentials.

  5. Under Reader Settings, choose which type of card and fob credentials may be used at this lock.

    1. For Openpath DESFire EV1, EV2, and EV3 enable 14443 UID (CSN).

    2. For Openpath DESFire EV3-A, select 14443 EV1 (NOC).

Note: You cannot enable 14443 UID (CSN) and 14443 Secure Mifare/Mifare Plus/EV1 (NOC) at the same time.

c. For Openpath low frequency (LF) prox cards, enable HID.

  1. Under Mobile Credential, choose whether to enable mobile credentials on this lock.

    1. Adjust the Communication Range to determine how close the mobile credential needs to be to the lock before appearing as a nearby entrYou cannot enable 14443 UID (CSN) and 14443 Secure Mifare/Mifare Plus/EV1 (NOC) at the same time.y in the app.

    2. Adjust Performance to determine how often the mobile app scans for locks.

  2. Click Save.

To configure a Control lock:

  1. From Wireless Locks, click on the name of the lock to edit it.

  2. Under Basic Settings, you can do the following:

    1. Enable or disable the Beeper on the lock when a credential is scanned.

    2. Enable or disable the Invalid Card Audit, which logs invalid credentials.

  3. Reader Settings cannot be edited on Control locks; high-frequency cards and fobs are enabled by default.

  4. Under Mobile Credential, choose whether to enable mobile credentials on this lock.

    1. Adjust the Communication Range to determine how close the mobile credential needs to be to the lock before appearing as a nearby entry in the app.

    2. Adjust Performance to determine how often the mobile app scans for locks.

  5. Click Save.

Create an Entry in Alta Access:

Once you’ve set up and commissioned your Allegion wireless locks, you can create entries with them similar to how you would with Avigilon Readers.

How to add a Gateway from another Org

If you need to move a Gateway from one org to another, you will need to use the ENGAGE app to remove it from the original org and then Sync against Allegion using the Alta Access app, Step 7, or from the Wireless Lock Gateway Management page in Alta Access. Once you do that you can add the Gateway to the new org using the ENGAGE app, Step 4.

  • No labels