Page Comparison

Common issues and troubleshooting for Allegion Wireless Locks & Hardware

Mobile unlock is not working

Card unlock is not working

No response from the reader

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 the Control CenterAlta Access

Not enough licenses for non-Avigilon Alta-sourced locks

Gateway synced in the Control Center Alta Access but the locks don't show up in the Control CenterAlta Access

Gateway is offline

Directions for turning on Allegion for legacy subscription accounts

No-Tour Limit Issue

How to upgrade/downgrade Allegion Lock and Gateway firmware

Where to find the approved firmware versions

Info
Note: We recommend trying the steps in the sequence they are listed

Troubleshooting

Issue

Anchor
mobile mobile

Mobile unlock is not working

Troubleshooting steps

1. Check that the mobile app is on the latest version

2. Use the Send feedback on the Avigilon Alta Open mobile app

3. Check Check error codes received from the mobile app

4. 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.)

5. Check the BLE reader "Communication Range" (should be long) and "Performance" (should be max). This is changed/set in the Allegion ENGAGE app

6. Check if Low Frequency valid card reads work

7. Run "Identify" on the Wireless Lock Devices page in Alta Access (If it is a gateway-connected device)

8. Run activity report with entry filter to see if lock/gateway has reported errors (Example: “Offline”)

9. 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

10. Use the Send feedback on the Avigilon Alta Open mobile app

Needed information for support

• Gateway connected or offline/no-tour?

• Is this a No-Tour device

• Intermittent unlock unlocks or never unlocks?can never unlock

• Lock and gateway serial numbers

• Entry ID, user ID, and timestamps

• Mobile app version?

• Any feedback?

...

Issue

Anchor
card card

Card unlock is not working

Troubleshooting steps

1. Check user access through the User Access Audit report in Alta Access Reports

2. 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.)

3. 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)

4. Power cycle the gateway

5. Power cycle lock

6. Remove/reattach network cable for gateway

7. Test network cable for the gateway on a laptop to ensure internet connectivity

8. Try another cable

9. Try another port

10. Run "Identify" on the Wireless Lock Devices page (If it is a gateway-connected device)

11. Hold card to reader for 5+ seconds to ensure all data is read for initial unlock

12. Run activity report with entry filter to see if lock/gateway has reported errors

13. Check for "Doorfile Updated Successfully" message in the activity logs report (If it is a gateway-connected device)

14. Is the gateway powered via PoE? Try an AC adapter

Needed information for support

• Gateway connected or offline/no-tour?

• Is this a No-Tour device

• Intermittent unlock unlocks or never unlocks?can never unlock

• Lock and gateway serial numbers

• Entry ID, user ID, and timestamps

• Card type/version?

...

Issue

Anchor
response response

No response from the reader

Troubleshooting

1. Reader not programmed with correct configuration card

   • Use the configuration card programming guide to ensure the reader is set up correctly.

2. Incorrect credential type

   • Make sure the credential being scanned is an Allegion/Schlage fob purchased directly from Avigilon Alta.

...

Issue

Anchor
badgeid badgeid

Cannot see the badge ID of the Schlage card/fob in the Avigilon Alta system

Troubleshooting

1. Card/Fob not scanned with MT20W

   • Use the enrollment reader (MT20W) to scan the credential and provision it to the organization.

2. 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.)

3. 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

Anchor
thirdparty thirdparty

Cannot see the third-party tab under readers in the Avigilon Alta system.

Troubleshooting

1. Incorrect organization configuration

   • Contact your support representative to ensure your organization has the correct configuration.

...

Issue

Anchor
remove remove

Removing the lock from the gateway doesn't update in the Control CenterAlta Access

Troubleshooting steps

1. Click the "Sync Devices" button on the wireless locks/wireless gateways page in the Control CenterAlta Access

2. Power cycle gateway

3. Remove/reattach network cable for gateway

...

Issue

Anchor
offline offline

Gateway is offline

Troubleshooting

1. Power cycle the gateway

2. Remove/reattach network cable for gateway

3. Test network cable for the gateway on a laptop to ensure internet connectivity

4. Try another cable

5. Try another port

6. Run "Identify" on the Wireless Lock Devices page (If it is a gateway-connected device)

7. Is the gateway powered via PoE? Try an AC adapter

...

Issue

Anchor
sourced sourced

Not enough licenses for non-Avigilon Alta-sourced locks

Troubleshooting steps

1. Check if the lock is marked as Avigilon Alta Sourced, or not on the device page

...

• 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

...

Anchor
gateway gateway

Gateway synced in the Control Center Alta Access but the locks don't show up in the Control CenterAlta Access

Troubleshooting steps

1. Remove/reattach network cable for gateway

2. Is the gateway powered via PoE? Try an AC adapter.

...

Issue

Anchor
directions directions

Directions for turning on Allegion for legacy subscription accounts

Troubleshooting steps

From the Partner Dashboard in the Control CenterAlta Access

1. Go to Manage organizations

2. Click on the organization you would like to add Allegion to

3. From the Edit organization page click “Subscriptions” at the top

4. 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

Iframe
src https://info.openpath.com/hubfs/Openpath/images/kustomer-articles/legacy_clean.png width 383 frameborder hide title legacy allegion align left height 106 longdesc Allegion Legacy

...

Anchor
limit limit

No-Tour Limit Issue

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.

...

Anchor
approved approved

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

Wireless Locks

\uD83D\uDCCE Related articles

Filter by label (Content by label)
page showLabels false max 5 spaces com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@10c00 maxCheckbox false showSpace false sort modified showSpacetype falsepage reverse true type labels kb-troubleshooting-article cql label = "kb-troubleshooting-article" and type = "page" and space = "EHC" labels kb-troubleshooting-article