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
Allegion Wireless integration troubleshooting guide
Common issues and troubleshooting for Allegion Wireless Locks & Hardware
Cannot see the badge ID of the Schlage fob/card in the Avigilon Alta system
Cannot see the third-party tab under readers in the Avigilon Alta system
Removing the lock from the gateway doesn't update in Alta Access
Not enough licenses for non-Avigilon Alta-sourced locks
Gateway synced in Alta Access but the locks don't show up in Alta Access
Directions for turning on Allegion for legacy subscription accounts
How to upgrade/downgrade Allegion Lock and Gateway firmware
Where to find the approved firmware versions
Note: We recommend trying the steps in the sequence they are listed
Troubleshooting
Issue
Troubleshooting
Check that the mobile app is on the latest version
Check error codes received from the mobile app
Verify the number of users with access to the lock, ensuring it does not exceed the maximum user capacity supported by the Allegion lock. (Refer to the Allegion specification sheets to confirm the maximum capacity for your lock model.)
Check the BLE reader "Communication Range" (should be long) and "Performance" (should be max). This is changed/set in the Allegion ENGAGE app
Check if valid card reads work
Run "Identify" on the Wireless Lock Devices page in Alta Access (If it is a gateway-connected device)
Run activity report with entry filter to see if lock/gateway has reported errors (Example: “Offline”)
Check for "Doorfile Updated Successfully" message in the activity logs report (If it is a gateway-connected device) to ensure that the lock has successfully processed the last access update
Use the Send feedback on the Avigilon Alta Open mobile app
Needed information for support
Gateway connected or offline
Is this a No-Tour device
Intermittent unlocks or can never unlock
Lock and gateway serial numbers
Entry ID, user ID, and timestamps
Mobile app version
Any feedback
Issue
Troubleshooting
Check user access through the User Access Audit report in Alta Access Reports
Verify the number of users with access to the lock, ensuring it does not exceed the maximum user capacity supported by the Allegion lock. (Refer to the Allegion specification sheets to confirm the maximum capacity for your lock model.)
If the card is no-tour, verify that if the Schlage fob is being used it was purchased from Avigilon Alta
(Schlage cards/fobs not purchased from Avigilon are not supported)Power cycle the gateway
Power cycle lock
Remove/reattach network cable for gateway
Test network cable for the gateway on a laptop to ensure internet connectivity
Try another cable
Try another port
Run "Identify" on the Wireless Lock Devices page (If it is a gateway-connected device)
Hold card to reader for 5+ seconds to ensure all data is read for initial unlock
Run activity report with entry filter to see if lock/gateway has reported errors
Check for "Doorfile Updated Successfully" message in the activity logs report (If it is a gateway-connected device)
Is the gateway powered via PoE? Try an AC adapter
Needed information for support
Gateway connected or offline
Is this a No-Tour device
Intermittent unlocks or can never unlock
Lock and gateway serial numbers
Entry ID, user ID, and timestamps
Card type/version?
Issue
Troubleshooting
Reader not programmed with correct configuration card
Use the configuration card programming guide to ensure the reader is set up correctly.
Incorrect credential type
Make sure the credential being scanned is an Allegion/Schlage fob purchased directly from Avigilon Alta.
Issue
Cannot see the badge ID of the Schlage card/fob in the Avigilon Alta system
Troubleshooting
Card/Fob not scanned with MT20W
Use the enrollment reader (MT20W) to scan the credential and provision it to the organization.
Credential assigned to another user
If the credential is assigned to a different user, delete it from their account so it can be used again. (This can be found in the credential report.)
MT20W reader not provisioned to the organization
Follow the steps to add the Schlage MT20W enrollment reader to the system.
Make sure the Host Configuration is the correct URL.
Verify that the enrollment reader appears in the "Third-Party" tab within the Reader section of the Avigilon Alta system.
If it doesn’t appear, make sure it’s commissioned via the ENGAGE mobile app, then press the "Sync" button on the third-party reader page.
Schlage MT20W enrollment reader User Guide from Allegion
Issue
Cannot see the third-party tab under readers in the Avigilon Alta system.
Troubleshooting
Incorrect organization configuration
Contact your support representative to ensure your organization has the correct configuration.
Issue
Removing the lock from the gateway doesn't update in Alta Access
Troubleshooting
Click the "Sync Devices" button on the wireless locks/wireless gateways page in Alta Access
Power cycle gateway
Remove/reattach network cable for gateway
Issue
Troubleshooting
Power cycle the gateway
Remove/reattach network cable for gateway
Test network cable for the gateway on a laptop to ensure internet connectivity
Try another cable
Try another port
Run "Identify" on the Wireless Lock Devices page (If it is a gateway-connected device)
Is the gateway powered via PoE? Try an AC adapter
Issue
Not enough licenses for non-Avigilon Alta-sourced locks
Troubleshooting
Check if the lock is marked as Avigilon Alta Sourced, or not on the device page
Needed information for support
If not Avigilon Alta Sourced and should be, support needs this info:
SO/PO number
ORG ID
Model for locks (NDEB, LEB, etc.)
Serial numbers for locks
Issue
Gateway synced in Alta Access but the locks don't show up in Alta Access
Troubleshooting
Remove/reattach network cable for gateway
Is the gateway powered via PoE? Try an AC adapter
Issue
Directions for turning on Allegion for legacy subscription accounts
Troubleshooting
From the Partner Dashboard in Alta Access
Go to Manage organizations
Click on the organization you would like to add Allegion to
From the Edit organization page click “Subscriptions” at the top
From your selected plan, scroll down and toggle the tile labeled “Allegion Wireless Locks Purchased from Openpath” then click save at the bottom of the page
5. You should now see Wireless locks and Wireless lock gateways under Devices in the org you added it to
Issue
Troubleshooting
There is a hard limit. If you need a credential with access to more than 11 wireless lock entries, you need to mark the credential as non-no-tour and then tour the locks with the Admin App. Mobile no-nour has no limit.
Approved Firmware Versions
If you upgraded via the ENGAGE app, their versions are newer than what is approved and tested by Avigilon Alta. Please reach out to Support.
Wireless Gateways
Model | Approved Versions |
---|---|
GWE | 01.65.04 |
Wireless Locks
Model | Approved Versions |
---|---|
LEB (all variations) | 03.10.01 03.11.02 03.14.02 |
NDEB | 03.10.01 03.11.02 03.14.02 |
FE410B | 04.12.00 04.14.01 |
BE467B | 04.12.00 04.14.01 |
FE410BM | 05.11.39 05.13.01 |
BE467BM | 05.11.39 05.13.01 |