I agree, this is a great guide. While I've been using this Locative / Maker API setup for about two weeks, it seems to be rock solid. I hope more people come across this topic and realize this setup works great.
1 Like
Great tutorial @steve.maddigan. I think I might add this since I can't find a way to change the geofence in the home app.
For those using HomeKit, I've been using the apple home app for presence detection using automations in a very similar way to how OP has set up Locative. The nice part is I don't have to confirm running the automation when I arrive and leave, it just happens magically in the background. More info on that topic here:
https://community.hubitat.com/t/arrive-home-iphone-presence/104581
1 Like
Noob question here. Since Life360 is out, I wanted an alternative to know when my family member enter or exit a location.
I followed your great documentation and found it simplier than geofency.
My question, do I have to install locative to the other phones and create the locations which I already have on mine? Cant the locations I created on my phone be used by others?
Need help trying to find an slternative to Life360.
Yes. Each phone that uses locative needs to have geofence locations configured with the http request to send to your hub when the phone crosses the geofence.
1 Like
Remember, one of the benefits of Locative is that it is an app that only exists on your phone. There is no Locative Cloud service, whatsoever. Thus, your location data is kept 100% local to your phone. It allows multiple geofences to be created, and the webhooks for each as you enter and leave.
So, while a little less convenient than Life360 was, at least there is no third party cloud service between your phone and your Hubitat cloud endpoint (yes, Hubitat does run a cloud server to allow this to work, but unlike Life360, they aren’t trying to lock their own users out of it! 
)
2 Likes
Bingo. Exactly.
