Verkada Geofencing Not Working? An Admin's Guide
Verkada's geofencing feature is a powerful tool for automating site security. It allows for the automatic arming and disarming of alarms and sites based on the location of authorised users. When a user with the Verkada Pass app leaves a defined geographical boundary, the site can arm itself, and it can disarm upon their return. If this process is failing, it can lead to false alarms or security lapses. This guide is designed for Verkada administrators to troubleshoot and resolve common geofencing issues.
The system's reliability hinges on three core elements: the user's mobile device settings, the configuration within Verkada Command, and stable connectivity.
## Step 1: Audit User Mobile Device Settings
The most common point of failure is the user's smartphone. The Verkada Pass app needs specific, persistent permissions to report its location accurately.
- Verkada Pass App is Required: The user must have the Verkada Pass app installed and be logged into their account.
- "Always Allow" Location Access: This is the most critical setting. For the app to detect when a user has left or entered the geofence, it needs to be able to check the location in the background.
- On iOS: Go to Settings > Privacy & Security > Location Services > Verkada Pass. The permission must be set to Always. The Precise Location toggle must also be ON.
- On Android: Go to Settings > Apps > Verkada Pass > Permissions > Location. The permission must be set to Allow all the time. The Use precise location option must be enabled.
- "While Using the App" is insufficient and will cause geofencing to fail.
- App and OS Updates: Ensure the user is running the latest version of the Verkada Pass app from their respective app store, as well as the latest operating system (iOS/Android) on their device.
- Battery Saver Modes: Aggressive battery saver or optimisation modes on some Android phones can restrict background app activity, including location tracking. The Verkada Pass app should be exempted from these restrictions in the phone's battery settings.
## Step 2: Verify Geofence Configuration in Command
As an administrator, you need to ensure the geofence itself is set up correctly in the Command portal.
- Log in to Verkada Command.
- Navigate to Admin > Geofence.
- Select the Site: Choose the site where geofencing is not working.
- Check the Map: Verify that the pin for the site's location is placed accurately on the map. An incorrectly placed pin is a common error.
- Review the Radius: The geofence is a circular area around the pin. If the radius is too small, users on the edge of the property might trigger the system inconsistently. Consider increasing the radius slightly (e.g., from 100m to 150m) to create a more stable buffer zone.
- Confirm User Assignment: Ensure that the users who are meant to trigger the geofence are correctly configured and have the appropriate permissions for that site.
## Step 3: Check Alarm and Site Arming Rules
Geofencing doesn't arm or disarm a site by itself; it acts as a trigger for rules you have defined.
- Alarm Event Triggers: Go to the Alarm settings for the site. Under Arming/Disarming, ensure you have rules set up that use geofencing as a trigger. For example, "Arm the site when the last person leaves the geofence."
- User Association: Check that the correct users or groups are associated with the geofencing rules. If a user isn't part of the rule, their location won't have any effect.
- Schedules: Be aware of how geofencing interacts with any existing arming/disarming schedules. A conflicting schedule could override the geofence trigger.
## Step 4: Ensure Connectivity
For the system to work, communication is key.
- User's Phone: The user's phone must have a working internet connection (Wi-Fi or mobile data) to report its location to Verkada's cloud.
- Verkada Site: The Verkada devices at the site (e.g., the Alarm Console, cameras) must also have a stable internet connection to receive the arm/disarm commands from the cloud.
If a user leaves the geofence but their phone has no signal, the "exit" event cannot be communicated, and the site will not arm until the phone is back online. By methodically verifying user device settings, Command configurations, and connectivity, you can effectively troubleshoot and restore the convenience and security of the Verkada geofencing feature.