I got it to work, but had to wait a short while at the end of the driveway where the gate is. I made the circle more than the standard 330 feet, but maybe not enough to account for the lag?
Plus, somehow I was thinking radius instead of diameter, so I'll bump it up and see what happens.
Has not been difficult for me for some time, thanks to below...
).Making the diameter larger did not help with response.
I had to wait like 20 seconds at the end of the driveway before presence was detected.
Geofency. It's a community app. has been 100% reliable. Habitat's own geofencing has always been sketchy at best. Stop pulling your hair out, just use Geofency and relax.
@velvetfoot I've not read the entire thread so I don't know what Apple devices you have....but do you have something Apple that acts as the hub for Homekit (Apple TV 4K or HomePod mini)? That's needed to remotely control devices in Homekit so I'd guess that if you didn't have one of those devices, the automation might not work while your device was using mobile data and it's not registering you as arrriving until the device connects to your home WiFi network; likewise it might show departed immediately as your device switches from WiFi to mobile dat as you leave the house rather than leave your defined geofence.
He bought some homepod minis
I'm still futzing around with it.
It worked well when I came home just now, so I'm optimistic.
I missed that
In the same boat. Isn't all this meant to make our lives easier? Instead we are jumping through hoops...
Here is my situation: for 2 years I have been battling HE for a geofence that works, all for naught! Presently, HE geofence shows me being ~2 miles from where I am in my house. iOS app Compass, shows me exactly where I am. Ifttt also "knows" where I am along with a couple other apps. Yet HE cannot get it correct. So is anybody from HE listening and can offer some resolution instead of having to goto HomeKit jump through a couple of hoops, etc.?
And BTW, I have rebooted the iPhone, sent geo events in the HE app, checked for updates, walked outside for a clear view of the sky, patted my head and rubbed my tummy simultaneously...
I finally found a solution although it won't work unless you're an Alexa user.
I created a virtual switch in Hubitat and then created an Alexa routine that uses Alexa's geofencing to determine my location and manage the switch.
When I leave, Alexa turns the switch off. When I arrive, Alexa turns the switch on. I have a Webcore piston that changes location mode to home when the switch is turned on and changes location mode to away when the switch is turned off.
It's unfortunate I have to do this but using Hubitat's geofencing to manage location modes was an abysmal failure. The app ALWAYS knew where I was but rarely triggered an event when I left or entered the geofence. If I manually hit Send Geoevent, the event trigger was sent and all of my rules ran immediately.
Given the number of people having problems with this and the length of time it's been broken, one would think the devs at HE would spend the time necessary to get this working. One would think.
Edit to add that in the short time I've used this, Alexa has been 100% reliable in managing the virtual switch when I enter or leave the geofence defined in the Alexa app. Perhaps the devs at HE can deconstruct that functionality and fix Hubitat.
Thought I would give it a try, I set up a couple rules ..
i'll let you know if it works for me too!
This works well but on iOS you will get the app tracking nag.
I'm not familiar with that. Can you explain?
Alexa is running a routine when I arrive or leave that just manages a switch. I would think Alexa wouldn't know that Webcore was reacting to switch state. And Hubitat wouldn't know how the switch's state changed.
Maybe better said, neither Hubitat or Alexa know what the other is doing?
iOS devices will frequently question if you know an application is using location services and give an opt in/out type of nag screen. The WAF factor was very low.
Ah, got it. I see that occasionally with other apps that I allow to track location.
Yes, I look at those occasionally but my older remote buttons aren't yet ready for the landfill, so I resist the temptation. Good to know they work well at distance.... if homekit geofencing stops working I will have to acquire one for the car 
I've implemented one out of the many laying unused, and I like! WAF is good too. The click is more reliable and more satisfying than regular garage door opener, the button is smaller, and easily mountable in so many hidden but convenient places. I've even made button 1 for open, and button 2 for close and the rule already checks for open/opening/closed/closing status before "toggling" the garage door, so no chances of multiple conflicting triggers. Thank you!
Rule also checks presence and toggles appropriately, though it's not needed anymore because, in addition to the flawless HomeKit presence, I've also added Alexa presence, and removed Hubitat presence. Combined Presence is now seemingly bulletproof.
I've been using Navigation lately, and Presence via Home is quite reliable.
Coincidence?
edit: I don't think so. With no nav on this afternoon, took a minute wait.
Download the Hubitat app
