Geofence actions not triggering on boundary cross

Android

Geofence actions (such as device lock or alarm) require both the correct Esper Agent version and a published Blueprint configuration to work properly. If your geofence actions aren't triggering when devices cross a boundary, follow these steps to diagnose and fix the issue.

Before you begin

Make sure you're using the new Geofence feature (accessible from the top-level Esper Console navigation), not the legacy geofence feature. The new Geofence feature requires specific setup steps to function correctly.

Step 1: Verify your Blueprint has geofence configured

1. In the Esper Console, go to Blueprints.
2. Select the Blueprint you're using for geofence configuration.
3. Navigate to the Geofence section.
4. Confirm that at least one geofence location is added with:
   • A desired action (Lock Device or Alarm)
   • A boundary radius set in meters

Step 2: Publish and converge your Blueprint

1. In the Blueprint, click Save to save your geofence settings.
2. Click Publish.
3. Go to Devices & Groups and select your target device or group.
4. Open the Blueprint tab.
5. Click Converge to push the updated configuration to your devices.

Saving the Blueprint alone is not enough—you must publish and converge it for geofence actions to take effect on devices.

Step 3: Check your Esper Agent version

1. Go to Devices & Groups and select your device.
2. Open the Device Info tab.
3. Locate the Esper Agent version.
4. If the version is below v9.0, proceed to Step 4. Geofence actions require Esper Agent v9.0 or later.

Step 4: Update Esper Agent

1. Follow the Deploying Esper Software Updates guide to push the latest Esper Agent to your devices.
2. Confirm the update has completed by checking the agent version again in Devices & Groups → [Device Name] → Device Info.

Step 5: Verify Blueprint convergence

1. Go to Devices & Groups and select your device.
2. Open the Blueprint tab.
3. Confirm the Blueprint status shows Converged (not Pending or Failed).

Step 6: Test geofence boundary crossing

1. Use a cellular-connected device for testing (WiFi-only devices may lose connectivity near boundaries, preventing geofence events from being reported).
2. Physically move the test device beyond the configured boundary threshold.
3. Confirm the expected action (lock or alarm) triggers on the device within a reasonable time.

If geofence actions still don't trigger

• Using a WiFi device: Confirm the device maintains WiFi connectivity throughout the boundary crossing. WiFi signal loss before or at the threshold will prevent geofence events from being reported. Test with a cellular-connected device instead.
• Agent update didn't apply: Check deployment status in Apps → Deployment Status to confirm the Esper Agent update completed successfully. Re-check the agent version in Devices & Groups → [Device Name] → Device Info.
• Blueprint Blueprint convergence failed: Verify the Blueprint status is Converged (not Pending or Failed) under Devices & Groups → [Device] → Blueprint tab.
• All checks pass but actions still don't trigger: Contact Esper Support if your agent is confirmed at v9.0 or later, your Blueprint is converged, your device has active network connectivity, and geofence actions still do not trigger after multiple boundary-crossing tests.

Key requirements

• Esper Agent version must be v9.0 or later. No workaround exists for older agent versions.
• Your Blueprint must be published and converged to your devices. Saving alone is not sufficient.
• Available geofence actions: Lock Device and Alarm.
• For reliable testing, use a cellular-connected device rather than WiFi-only.

Still need help?

If you've completed all steps above and your geofence actions still aren't triggering, submit a support ticket with details about your device, agent version, and test results. You can also review the Creating and Managing a Geofence (New) guide for additional configuration details.