...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting steps
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
...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting steps
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
...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting steps
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.
...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting steps
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.
...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting Steps
Incorrect organization configuration
Contact your support representative to ensure your organization has the correct configuration.
...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting steps
Click the "Sync Devices" button on the wireless locks/wireless gateways page in Alta Access
Power cycle gateway
Remove/reattach network cable for gateway
...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting steps
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
...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting steps
Check if the lock is marked as Avigilon Alta Sourced, or not on the device page
...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting steps
Remove/reattach network cable for gateway
Is the gateway powered via PoE? Try an AC adapter
...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting steps
From the Partner Dashboard in Alta Access
...
Anchor | ||||
---|---|---|---|---|
|
Troubleshooting steps
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.
...