The issue is the iOS (maybe Android too) presence reliability is pretty bad. I have a rule to trigger when our Life360 presence doesn't match our App presence after 3 minutes - and it triggers a LOT.
I believe the issue is the App is "missing" the crossing of the GEO fence and just never sending the event.
What I would suggest is to add a capability to request from the hub to the App to "send a GEO event". In this case, when our presence doesn't match, my RM rule could request a GEO event from the offending app. My thought is, if HE can send "messages" to the App - it should be able to send a "message" that tells the App to respond back a GEO event. This works with the Life360 "refresh" request (though I realize that is unrelated to HE).
But it is rough on the battery, last time I checked.
Since the way the hubitat mobile app’s geolocation functions is more privacy-oriented than most other apps, I think that can contribute to it being killed off in the background more readily by iOS. Using high-accuracy presence presumably works around that, but keep an eye on battery usage after enabling it, since it can be a dealbreaker unless you’re able to top off your phone over the course of a day.
There is also Life 360 free..A lot of people use that. Myself I use "Combined Presence" from HPM and use a combination of my presence fob on my keychain and wifi presence on my phone . Both of these working together work well for me.
Yes, I've done that as I have 3 iPhones in total and none of them work reliably.
I've deleted/reinstalled/recreated a virtual device from scratch and read every forum post on the topic that I've come across.
I've changed today to use locative instead and turned off all the geostuff in the app and works reliably so far today without issues. I've used Smartthings prior to Hubitat and that worked without issue.
Seems like the app despite any setting you change to keep it awake, it simply does not as checking the logs on the device, it never wakes back up.
All I know is homekit Geofencing in iOS 14 was very reliable, that's all I would use for location based automations. iOS 15 is hit or miss when it comes to geofencing for me. I had to sign out iCloud and log back in. Also had to turn off & on personal requests inside HomeKit to get things working. Geofencing is still not working on 2 of my phones no matter what I do, so yeah something is definitely broken/some setting is wrong in my phones. I have to always have both my phone and watch with me at all times to get accurate locations now, which is just crazy stupid. I can imagine how messed up geofencing is on third party apps if I'm having this much trouble with iOS geofence within homekit.