I'm seeing a huge delay as well, OnePlus 9. It has been working fine until recently. Settings haven't changed.
1 Like
There appears to be a setting where you can turn that automatic removal of permissions off, under the permissions settings for the app.
Putting my comment aside, I'd add to the list of people experiencing delayed capture of returning home.... I have a (now old) Google Pixel 2XL.
Issues here as well. It was working quite well for some time. Now, seeing a large delay if it works at all for both my wife's S10 and mine. Both on latest beta & android 12. My wife's phone was more reliable than mine but now it's giving me fits as it is not consistently changing. I was looking at it last night because hers did not register as home. Changing the geofence size registered her correctly inside and would then immediately go back to out. Logged her out and back in and that stopped. Both phones worked for our departures this morning but mine was delayed by about 30 minutes and hers by 15.
I am also having this issue again as well. My location will clearly be far outaide the geofence but the app says im in the geofence and vice versa. Only way to get presence to change is to change the geofence radius but that only fixes it till the next time i leave/enter the geofence. Sending a geo event with the button doesnt help.
I am also on a Samsung Galaxy device. An S10. App has unrestricted access to battery and location. Toggle set to not remove permissions.
I'm on the beta version of the app, version 1.6.8 build 128. Im on the beta version because one of the many other times ive had this issue, support told me to install the beta.
Its really odd that when locking at the app I'm clearly outaide the geofence but the app still says I'm inside it. The fact the the app is open and i can be driving and watch my dot leave the geofence makes me think its not a location or battery optimization issue (as thr app is open and its clearly tracking my location propwrly) it seems like an issue with the Hubitat app and I've had this issue in the past so I dont think its anything google/android or samsung has recently done.
1 Like
So this morning without making any changes its started working again on both mine and the wife phone?
UPDATE - seems to have fixed its self here only one day but has works correctly between me and the wife's phones 8 times in the last 24 hours
I have the same issue with me and my wife's S20. I use combine presence with Life360 and it's certainly seems like it's in the phone. When I arrive home and no presence events have taken place all I need to do is wake up my phone and open life360 then within 5s the presence event happens (dont know which event triggered the presence, Life360 or Hubitat but it does happen consistently like that). I've nauseatingly gone thru all the phone settings numerous times and there have been no smoking gun. There must be some under the hood obscure setting that hasn't been ID'd yet. But sometimes it does work so it's almost like there's a poll rate or update rate issue between the app(s) and the OS. Just haven't been able to pinpoint the issue yet. Hopefully there will a revelation soon.
1 Like
I guess I trusted the updated version of the Android app, and updated. WHAT a BIG mistake!
I do have 1.6.3 apk on my phone so I deleted 1.6.8 and re-installed 1.6.3 because it worked great.
We'll see if it still does though with the same phone I have had for several years... a Sammy S8.. yeah, I know... old... but it works and does everything I need.
The 1.6.8 version had the geo circle, then I logged out (on the phone) and logged back in and NO geo circle! No lat/long geo distance, all zero. So buh bye to 1.6.8!
This has been an ongoing problem that MANY have had, and there doesn't seem to be much priority to fix it.... bad news! Oh well, I will stick with 1.6.3
The missing geofence isn't necessarily a 1.6.3 issue. I'm on the latest 1.6.8 build and my geofence disappeared a couple months ago. It's discussed in a different thread. But no fix has been found. So now my Hubitat apps watches my comings and goings and always compares it to a lat/lon of 0.0/0.0. And since I'm never in the Atlantic near Africa, I never enter my geofence anymore.
I now use my Alexa presence to try to trigger my rules in Hubitat. But that only works about 70% of the time and even then usually pretty delayed. I just had to make a bunch of buttons on my app to declare when my wife or I has left or arrived. And then I have to check the app and hit a button if things aren't working. Kinda sucks doing it this way now.
Well from what I have experienced and tried, 1.6.8 never worked for me, and when I reverted to 1.6.3, things worked again.
On .8, I never had any long/lat or geofence circle and with .3 I did.
.3 also worked pretty good too.
just sayin'
There have been some conversations around this.
FWIW, I have all of the issues mentioned in this thread, right today, right now and haven't been able to identify the root of the problem. On very rare occasions HE will work but the general experience is HE app will show me inside the fence when I can be 10+ miles away, an update can sometimes be received anywhere from 15 minutes to 2+ hours late, but mostly it just doesn't work at all.
This is using a Samsung Galaxy S22 Ultra and version 1.6.8.128 of HE app.
On this phone, I also have Alexa and Samsung Smartthings apps. One peculiar observation I've made is that HE hardly ever works, Alexa is hit & miss but Smartthings seems to work almost every time. I wonder if Smartthings might have a little insider advantage that others may not have. Samsung = Smartthings
Another observation just for illustrative purposes only, I can bring up Google maps and if I zoom in far enough, GM can track my movement and show what side of the house I'm standing in in near real time, so the accuracy is there. Why can't apps like HE capture this same information?
Ok, so today I conducted an experiment. On my device (S22 Ultra) I have Samsung Smartthings, Alexa, IFTTT and Hubitat. They are all set up to send a message when exiting or entering the geofence area.
- Samsung ST - Reports exiting geofence at 5:46PM and returning at 6:01PM. Dead accurate
- IFTTT - Reports exit at 5:47PM and returning at 6:15PM. Fairly accurate on exit, ~15 minute delay on return.
- Alexa - No report either direction
- Hubitat - No report either direction. In examining the debug file there were no events logged for exit or return.
Just a heads up, there is another optimization menu through the battery settings. I don't think Samsung did a very good job integrating their setting with the android setting so it can be finicky. I'm not sure if they fixed it, but as of a couple months ago, to get some apps to work you needed to do both.
The worst thing about it is that if you set the app to Unrestricted from the app info page, it will disappear from the battery settings page. Basically you have to set it in both places, but do it in the battery menu first.
2 Likes
@RodM are you referring to Adaptive Batter?
I would like to know, because My setup has worked without issue until recently. Those options haven't changed but that doesn't mean that the service hadn't been updated to make it not work.
Unrestricted and all have been setup that is the only option that haven't changed 2-3 years. Thank you for the information.
Adaptive Power Saving is another one that I completely forgot about. I have heard that can cause problems too.
I was thinking of Settings>Battery and device care>Battery>Background usage limits> add Hubitat(or whatever other apps you are having trouble with) to never sleeping apps. The issue is that the app must be added to never sleeping apps before switching to unrestricted in the app info menu.
I just confirmed that I was already using this setup, but my presence departures have been delayed recently as well, so who knows.
Once you select unrestricted in the app, it gets removed from the 'never sleeping apps' list. Those 2 look to be mutually exclusive.
I heard about doing both while tracking down issues with Spotify. I believe one setting is android, the other is from one ui. They seem redundant, but others have seen that they are not completely integrated as you would expect.
But yes that was my point, never sleeping apps has to be first in order to cover up for whatever bug in programming.
Ok, I'll see what happens, that's how I'm setup now. Thanks.
I've been playing around with the presence sensors for a few days. I'm still finding this being very inconsistent. All presence sensors fail in one way shape or form.
Has anyone able to get a consistent trigger? I've tried Alexa, google, IFTTT, Life360, and Hubitat without any success.
Has anyone seen and has anyone worked around this yet?
I use Life360 on my wife's phone and mine. Works without a hitch for arrival. We occasionally get a one minute or so delay when departing. Caveats being, we both have Pixel 6 Pros, we don't leave the house every day, and I only have rules written around departure.
