So, according to the ST API it is possible to edit the size of the area around geolocations with a minimum value of 20 meters and 500000 maximum. However there is an issue with this function because whenever you set it between 20 and 149 it will default to 250.
I raised this issue a year ago and got no reply.
150 meters is entirely too big when you live in an apartment building for location based automations to be accurate.
Any word on this getting fixed any time soon?
Well you can no longer set the diameter of the geofence to smaller than 150 meters. We’re stuck with it. I tried the web interface and it no longer allows to set geofencing to smaller than 150. Why Samsung made the geofence minimum diameter to 150 is beyond me. I do agree it needs to be 20 to 50 meters minimum.
I believe that on Android the geofencing uses network Location and the latency can be a couple of minutes or more. So 100-150m is the minimum recommended.
Certainly when arriving home on foot with a 150m geofence it is not unprecedented to be at the door when the geofence triggers, and when arriving by car it is unremarkable to already be inside the house.
It would be nice if the API reference matched reality. If it is a case of the client apps implementing their own limits then sadly the API limits ought to be changed to match them.
