19.10.2020, 10:58
I've tested IFTT ~1,5 years ago and it wasn't enough reliable on both Android and iOs. From time to time smartphone changed source of coordinates from GPS to WiFi and in one minute you are in one place, in next minute you are 2km away. Another thing that also in case when positioning uses GPS it wasn't enogh realtime and for example you drove back home and IFTT sent you notification after e.g. ~1 minute.
Geofence could be helpful if:
- based on real GPS sender which is dedicated for this and cannot be limited e.g. by energy optimization,
- its data should be send to LM or other server over https,
- should have possibility to send its position at least 15s (can also check geofence but with some timestamp so when you cross geofence while you haven't internet then it wouldn't open your gate later when connection return).
I've prepared a few years ago some example of geolocalization based on Traccar:
https://openrb.com/geolocalization-with-...ar-service
Geofence could be created on top of geolocalization. But Traccar is not ideal because it probably until today doesn't have HTTPS. But its client app can be connected directly to LM and it has all necessary options.
Geofence could be helpful if:
- based on real GPS sender which is dedicated for this and cannot be limited e.g. by energy optimization,
- its data should be send to LM or other server over https,
- should have possibility to send its position at least 15s (can also check geofence but with some timestamp so when you cross geofence while you haven't internet then it wouldn't open your gate later when connection return).
I've prepared a few years ago some example of geolocalization based on Traccar:
https://openrb.com/geolocalization-with-...ar-service
Geofence could be created on top of geolocalization. But Traccar is not ideal because it probably until today doesn't have HTTPS. But its client app can be connected directly to LM and it has all necessary options.
Done is better than perfect