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 Alta Access app.
| Info |
|---|
Note: Privacy Mode is supported for Allegion wireless lock integrations. |
| Info | |
|---|---|
Note: Supported features and limitations for Allegion Schlage wireless locks. | |
| Panel | |
| panelIconId | atlassian-info |
| panelIcon | :info: | bgColor | #FFBDAD
Note: Please read /wiki/spaces/EHC/pages/1890287619 |
To enable this feature, refer to How to enable features in Avigilon Alta Access.
Requirements
Allegion ENGAGE app.
For iOS devices: Download on the App Store.
For Android devices: Download on the Google Play Store.
Alta Access app.
For iOS devices: Download on the App Store.
For Android devices: Download on the Google Play Store.
ENGAGE™ Gateway.
Schlage NDEB, LEB, or Control™ wireless locks.
Open Avigilon Alta Access access and go to the org you’re commissioning locks to (at minimum Hardware Read/Write permissions).
| Info |
|---|
Note: The org’s Site site in the Alta Access system must have an address in order to get accurate timestamps on Allegion events. Go to Sites > Site > Edit Site and edit site to enter an address. |
Overview of setup
Note: You must perform these steps in the specified order.
Install Gateways and locks (refer to Allegion documentation)
| Anchor | ||||
|---|---|---|---|---|
|
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.
| Anchor | ||||
|---|---|---|---|---|
|
Open the Open Admin Alta Access app first.
Tap the name of the Org org to which you’ll provision these locks and gateways.
Tap 3rd Party Devices.
...
On the web page, accept Allegion’s terms and create an account using the email address associated with your Avigilon Alta account.
| Anchor | ||||
|---|---|---|---|---|
|
...
gateway:
Open the ENGAGE app and log in.
Tap on the plus sign to add a device.
Tap on Gateway.
Tap the gateway’s serial number.
Enter a name for the gateway.
For Gateway gateway communication mode, tap IP.
On IP Configuration, enable IP Behind Firewall and tap DHCP.
On the IP Behind Firewall screen, enter the following:
Code Block Server URL: https://ozone.prod.openpath.com CA Server URL: http://ozone.prod.openpath.com/cert
| Info |
|---|
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. |
| Anchor | ||||
|---|---|---|---|---|
|
Tap on the plus sign to add a device.
Tap on the model of lock you’re commissioning (Avigilon Alta supports LEB, NDEB, and Control locks).
The app will ask if you want to use default settings — tap Yes (you can adjust lock configurations later in the Avigilon Alta Access).
Tap the lock’s serial number.
Follow the in-app instructions for connecting the lock.
Enter a name for the lock.
(NDEB and LEB only) On the Select the lock function page, select Storeroom.
...
8. Skip the Wi-Fi configuration step if able, since the lock will connect to the Internet via the Gatewaygateway. 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 gateway’s configuration.
| Anchor | ||||
|---|---|---|---|---|
|
...
lock to the
...
gateway:
Tap on the gateway from the list of devices.
Tap Linked Devices.
Tap on the plus sign to link a lock.
Tap on the name of the lock to link it to the Gatewaygateway.
| Info |
|---|
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 Gatewaygateway.
| Anchor | ||||
|---|---|---|---|---|
|
...
gateways and
...
locks to Avigilon Alta:
Open the Open Admin Alta Access app.
Tap the name of the Org org to which you’ll provision these locks and gateways.
Tap 3rd Party Devices.
Tap Allegion Wireless Gateways (Schlage).
Tap Sync Gateways.
Review the list of gateways and locks.
| Anchor | ||||
|---|---|---|---|---|
|
...
gateways and locks:
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.
Go to Devices > Wireless Gateway.
Under the Actions column, click Update Firmware next to each Gateway.
Go to Devices > Wireless Locks.
From this page, select locks and click Batch Actions to update the firmware.
| Info |
|---|
Note: To downgrade Allegion Lock lock and Gateway gateway firmware follow these steps. |
| Anchor | ||||
|---|---|---|---|---|
|
| Info |
|---|
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):
|
| Iframe | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
To configure an NDEB or LEB lock:
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.
Go to Devices > Wireless Locks.
Click on the name of the lock to edit it.
Under Basic Settings, you can do the following:
From the Power Failure dropdown, select how the lock will behave in the event of the battery failing.
As Is – the lock will remain in the same state.
Safe – unlocked.
Secure – locked.
Enable or disable the Beeper on the lock when a credential is scanned.
Adjust the interior LED settings.
Enable or disable the Invalid Card Audit, which logs invalid credentials.
Under Reader Settings, choose which type of card and fob credentials may be used at this lock.
For Openpath DESFire EV1, EV2, and EV3 enable 14443 UID (CSN).
For Openpath DESFire EV3-A, select 14443 EV1 (NOC).
...
Under Mobile Credential, choose whether to enable mobile credentials on this lock.
Adjust the Communication Range to determine how close the mobile credential needs to be to the lock before appearing as a nearby entrYou . You cannot enable 14443 UID (CSN) and 14443 Secure Mifare/Mifare Plus/EV1 (NOC) at the same time .y in the app.
Adjust Performance to determine how often the mobile app scans for locks.
Click Save.
| Iframe | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
To configure a Control lock:
From Wireless Locks, click on the name of the lock to edit it.
Under Basic Settings, you can do the following:
Enable or disable the Beeper on the lock when a credential is scanned.
Enable or disable the Invalid Card Audit, which logs invalid credentials.
Reader Settings cannot be edited on Control locks; high-frequency cards and fobs are enabled by default.
Under Mobile Credential, choose whether to enable mobile credentials on this lock.
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.
Adjust Performance to determine how often the mobile app scans for locks.
Click Save.
| Anchor | ||||
|---|---|---|---|---|
|
...
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 Readersreaders.
| Anchor | ||||
|---|---|---|---|---|
|
...
gateway from another
...
organization
If you need to move a Gateway gateway from one org to another, you will need to use the ENGAGE app to remove it from the original org and then Sync 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 gateway to the new org using the ENGAGE app, Step 4.
...