Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

...

Info

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

Troubleshooting

Issue

Anchor
mobile
mobile
Mobile unlock is not working

...

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

  2. Check error codes received from the mobile app

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

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

  5. Check if valid card reads work

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

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

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

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

...

  1. Check user access through the User Access Audit report in the Control Center ReportsAlta 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

...

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

...

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

...

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

...

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.

...

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

04.1214.0001

BE467B

04.1012.0100

04.1214.0001

FE410BM

05.11.39

05.13.01

BE467BM

05.11.39

05.13.01

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@10c00
maxCheckboxfalse
showSpacefalse
sortmodified
typepage
reversetrue
labelskb-troubleshooting-article
cqllabel = "kb-troubleshooting-article" and type = "page" and space = "EHC"