327
edits
Changes
no edit summary
It is also possible to use the [[Constraint: Geofence|Geofence (Location)]] constraint to limit when functionality can run based on your current location.
It is also possible to use the [[Constraint: Geofence|Geofence (Location)]] constraint to limit when functionality can run based on your current location.
=== Defining Geofences ====
You can access the list of current Geofences from the Geofence tile on the application home screen. From the list you can add a new Geofence or edit an existing one. This will take you to the Geofence configuration screen.
On this screen you can see a grey circular area around a point. This represents the area of the Geofence (the area that will trigger if you enter/exit). You can drag the map around or use the search functionality to move to a new location entirely. The radius value can also be changed by dragging the slider or tapping the textual value. A large radius is recommended to ensure the trigger fires more reliably when an accurate location is hard to determine.
=== Location Trigger ===
=== Location Trigger ===
The Geofence trigger functionality relies on Google Play services to operate. On devices without Google Play services or in rare cases where the Play services functionality doesn't work correctly an alternative [[Trigger: Location Trigger|Location Trigger]] is provided. This uses a custom MacroDroid implementation and has no dependency on Google Play.
The Geofence trigger functionality relies on Google Play services to operate. On devices without Google Play services or in rare cases where the Play services functionality doesn't work correctly an alternative [[Trigger: Location Trigger|Location Trigger]] is provided. This uses a custom MacroDroid implementation and has no dependency on Google Play.