From what I've read about this stuff, it sounds like Apple and Google intentionally make this difficult (for lack of a better term) so that 3rd-parties don't abuse tracking and thusly crush battery life and OS resources. Sort of like how the military can tweak GPS's CEP at will -- they hold all those cards.
Bigger/specialized companies like L360 have the resources & bandwidth to better "keep up" with how Apple & Google tweak that access, but smaller clients (presumably Hubitat) who don't have the bandwidth to dedicate resources solely to this effort end up just doing the best they can - so it sometimes works better than other times.
Sounds like an excuse, to be honest. At this point, the APIs are well known and documented both on iOS and Android and hundreds of apps track location for different purposes. I am sure they can find a specialized consultant to address the issue. I don't know if HomeAssistant's presence is much better but its mobile apps are opensource (ios for example)
I get that Hubitat is unlikely to have dedicated mobile developers and is likely to outsource that work but as a tablestake, they should make sure that functionality is reliable.
EDIT, moreover, the Hubitat mobile app doesn't need to communicate with Hubitat most of the time, it could store the n locations that you have a hub at (1 for most people) and with every mobile location change, calculate whether it's left or arrived at one. So the impact on battery should be minor.
This is what I do/or what I did as well. I did all of the stuff you mentioned in your post. Connecting to WiFi, Google Home, Smartthings arrival sensors (long time ago - I have a lot of them, currently they "sleep" in boxes at my attic), Hubitat native, and so on. Nothing worked almost so reliable like the combination of HD+ and Life360.
Now I have to look for a combination beside HD+ I've never used before. Life360 + HD+ was such a solid solution.
I agree. If Owntracks can work, which I believe is developed by a small group, it should be possible to dedicate some resources to make Hubitat app work.
I think it's a valid request but one that does unfortunately require a lot of resources and evolves over time. I haven't worked on iOS in years so I can't talk about it -- but I have done a lot of Android development and it just takes time to really figure out the best way to get geofencing to work reliably.
Yes, there's some well known API's -- but they just don't work reliably across all devices. There's lots of reasons for this.. some of them relating to the OS just trying to maximize device battery at the cost of delaying notifying an app when you enter or exit a geofence. I believe that's why Hubitat's app doesn't work as reliably as most of us would like.
I ended up writing my own presence feature in HD+ and it's been working reliably for me over the past few years. I can't think of a time when I've left home (with my phone) and haven't gotten a notification that my Hubitat went into 'armed away' mode. I did this not just with a geofence API but using other API's like Activity Detection, charging detection, connection (cellular/wifi) detection. It took weeks of testing to get it to work with my devices and that doesn't mean it'll work great with some other device manufacturer either.. and of course it doesn't work with iOS so I don't recommend it as a solution for most -- I just happen to use an Android phone.
Anyway, this would probably be better served in another thread just comparing the various options out there -- ie: Hubitat vs Life360 vs OwnTracks vs ??; I'm sure some already exist.
For Life360, I'm hopeful there's enough interest in Life360 that someone will figure out another way to support logging in...
HELP? Can you explain to me how to use HD+ as a presence sensor for Hubitat? I just installed to use as a replacement of Life360 presence. It's just an Android App, no device is created in Hubitat to monitor, that I can find. What am I missing? Thank you if you are able to help.
So I have tried every tip to log in to the app that I have found and every attempt results in the dreaded "Connection Error: 403". While trying to ensure that my phone/email & password were correct I logged in into both the phone app and the life360 website and noticed that I was never asked for a password, they simply sent me a confirmation code to use. Am I trying to use the wrong credentials to log into Life360+? Is it not phone/email & password anymore?
If it's asking for a code, 2FA has been turned on. You won't be able to log in using that acct. You can try resetting the password. Some users have reported that it turns the 2FA back off but I don't know that for sure.
Oh...that would explain things. Any idea how I might have turned that on? I don't recall doing it, could another member of the family have done it for everyone?
Well, resetting my password did not help. Funny thing is I had a userid/password option on the phone app until I verified my phone number and then it disappeared. I think my wife is the admin on the "family" group, I'll check her phone to see if there's an option for 2FA. Thanks for the tip.
@joe.c.richmond and @RC51_Tofuman, there is no option to turn 2FA on or off in the app. It's turned on by verifying your phone number in the app which it's been prompting us to do. It per sign in also, not per "circle".
On iOS Geofency, Owntracks, and Locative are all performing essentially the same as Apple Home native presence. I have 3 of the 4 running and there is no perceptible battery performance issue. Not sure why the Hubitat app has its issues.
I'm calling it dead too. I just killed mine when I removed the access token to see if it would obtain a new one. I'll keep an eye on the Github forums for a fix but I think they may have given up. I'm sure @jpage4500 will be doing the same.
