The current Openpath Jira and Confluence instances will be migrated to the MSI On-Premise solution from August 9th-11th, the current platform will be set to read-only and all future usage will be in the Avigilon Instance. Please ensure access to MSI Jira & MSI Confluence, both are accessible through OKTA. For additional information and details please refer to the Atlassian migration page
What is Geofence?
- Chad Fay
Geofencing, or geo-proximity, is a location-based service utilized by our app. It uses Wi-Fi and cellular data to activate a pre-defined action when a mobile device enters or leaves a virtual boundary, called a geofence, around a specific geographical area.
To ensure privacy, we do not transmit the actual location. Instead, we send a hash or encoding of the location. This allows the ACU (Access Control Unit) to verify the correct location without recording or storing the actual location data. Currently, the default proximity distance is set to 500 meters and cannot be adjusted.
Note: Phone and ACU location measurements taken can vary in accuracy due to varying signal strengths, so a default 500m radius accounts for that variation.
If you're worried about distance accuracy, our recommendation is to avoid relying solely on geolocation-based proximity. Instead, you should focus on BLE-based proximity. This involves setting up an Entry State that excludes triggers like "in Geofence" (which uses geoproximity) and only allows triggers such as "near Reader" (which uses BLE-based proximity).
Example Entry State without Geofence enabled: