Verkada Pass Not Working? Bluetooth Unlock and App Troubleshooting

Find the right troubleshooting path

Use these observations to narrow the cause; they are not a definitive diagnosis.

Work through the checks

1. 1

   Record a reproducible failure

   Note the door, time, phone model, OS version, Pass version and whether you tapped a remote unlock control or approached the reader. Keep a valid approved alternative entry method available during testing. Compare one attempt with its Command event rather than repeatedly trying different settings without a record.

   Reference: Verkada Pass App (opens in a new tab)
2. 2

   Confirm the account and intended access

   Sign in using the email invited by the access administrator and select the intended organization in Pass. The administrator should check the access-user profile, applicable groups and the enabled Remote Unlock or Bluetooth Unlock method. An invitation alone does not establish permission to every door.

   Reference: Verkada Pass App (opens in a new tab)
3. 3

   Check door authorization at the attempt time

   Have the administrator review the access level’s doors, groups, schedule and applicable exceptions. Compare the timestamp and door time zone. If a physical badge and Pass both fail for the same person, verify authorization before treating this as a phone fault. Make only changes approved for that user’s duties.

   Reference: Access Level Schedules and Exceptions (opens in a new tab)
4. 4

   Verify Bluetooth at every required level

   Bluetooth unlock requires a Verkada reader and must be enabled at organization, site, door and user levels. Ask the administrator to verify the existing settings at each level. Avoid bulk-enabling access while diagnosing one phone. Keep the current configuration recorded before making an approved correction.

   Reference: Bluetooth Unlock (opens in a new tab)
5. 5

   Check phone permissions and background operation

   On iOS, Verkada specifies Bluetooth permission, Bluetooth enabled, location access set to Always and Pass running in the background. On Android, it specifies Bluetooth enabled, location access while the app is in use and the Pass notification present. Follow managed-device policy and the current OS-specific reference when labels differ.

   Reference: Bluetooth Unlock (opens in a new tab)
6. 6

   Test proximity without breaking badge access

   Test at the configured reader distance and allow a few seconds for the phone to respond. If a wallet or NFC scan produces a keycard denial, have the administrator inspect that distinction. Do not disable the NFC antenna when the site depends on high-frequency cards; use the documented proximity guidance with the installer.

   Reference: Bluetooth Unlock (opens in a new tab)
7. 7

   Verify the result and collect the remaining fault

   Repeat the same authorized attempt with the door closed, then confirm the physical release and corresponding event. If the app still fails, document permission and version details before a supervised app reinstall or phone restart. Recheck access afterward rather than assuming a successful sign-in proves unlocking works.

   Reference: Verkada Pass App (opens in a new tab)

Verify the result

Confirm the intended unlock method works for the user at the intended door and schedule. Verify physical entry and the recorded event; Verkada notes that Bluetooth unlock events are not logged while the door shows open. Check an approved badge still works if reader settings changed.

If the issue remains

Provide door and attempt timestamps, phone/OS/Pass versions, selected organization and whether remote, Bluetooth or physical-badge access fails. Send event details privately to the access administrator or support. Never include passwords or active credentials in a public discussion.