[RELEASE] OwnTracks for Hubitat Presence Detection

Guys, have been using since about the time that Life360 stopped working. Primarily just for presence, but also use the family map. I updated my hub and Owntracks earlier today. It would appear that the map still is tracking and the Hubitat Owntracks program is showing location updates, but my Owntracks - user in Hubitat is not updating.

Any suggestions as to what I have to do to get the presence detection working again within Hubitat? Thanks.

Ed

Am seeing this in my logs after forcing a manual update on the phone. Inside Owntracks shows the update time but not in Hubitat:

Have you updated to the latest version (1.8.26)? That looks like a mismatch between the driver version and the app version.

I have upgraded what has been offered to me. There is no outstanding updates. Could the update have gone wrong? How would I force an update again? Thanks

Would appear that my program is at 1.8.22 with no listed updates in the Package Manager. Not sure how to confirm the driver version, but I may appear to have 2 of them:

Looks like I also have 2 apps. The top one is 1.8.22 and the bottom is 1.8.26

I'm at 1.8.26.
It looks like the top one is in use by OT.
Personally I would try deleting the one that is not in use. (Bottom one).
Then do a repair of OT in HPM.
This is just my take on your situation.

1 Like

There will be 2 drivers, one driver one common driver. But you have some dual conflict thing going on there so I'd suggest what was mentioned above to clean up the installation.

They will get updated as a bundle from HPM, so the repair would fix that.

Thanks, but how do I delete the unused app? Thanks.

If you click on the app you want to delete in the screenshot you posted above, at the top right you will see the 3 dot icon.
Click on it and from the drop down select delete.
If this app is associated with any installed app/device it will not allow you to delete it.

Thank you. Getting rid of several apps that appear to be installed multiple times with only 1 active...

Ed

2 Likes

My daughter recently switched to an iPhone and the Owntracks client seems to shutdown for longer periods of time. So I constantly get her phone in the Device Activity Check notification. Can it be adjust d for iPhones to be a little longer?

Device Activity Check:
OwnTracks - "phone name here" - Sep 29, 2025, 7:58 PM

Is she not changing locations for 12 hours? Android defaults to a ping home every 30-minutes, but iPhone doesn't have that. 12-hours is the default that you can change here:

1 Like

Yes, if she's home early for the day, it could be 12 hours before she leaves for school the next day. I didn't realize there was a setting, I bumped it to 18 hours.

1 Like

Just wondering. I know there was an issue if the "cmd" slider wasn't set then the app couldn't set the +follow region to prevent it from sleeping when moving. Suppose I should have mentioned that instead of the weird question. :slight_smile:

The last 2 months I have been getting from Google asking me to secure my API key.
I'm not sure what I need to lock down in Google; it was all quiet for the last few years.
Do I have to restrict to my router WAN IP to keep it happy?
This is what I put in as a test.



image

1 Like

I just got an email on this myself.
Not sure what I need to do differently?




1 Like

I have the Geocoding API ticked as well. Google was showing a small bit of activity on that API.
Do I really need that or can I kill that one and have everything still work ok?
I'm wondering if I enabled it so the Family map tile would work?
With the WAN IP filtered I now get Oopps Something Went Wrong on the Family map tile.

I should have ignored the email warnings :wink:

PS I removed the WAN restriction and the Family tile came back. :slight_smile:

So… I just got the same email from Google Maps Platform about my API key being “unrestricted.” Honestly, it’s been set up that way for so long I’d completely forgotten about it. At first glance I thought it was some kind of scam (LOL) — but nope, it’s legit.

Has anyone figured out what triggered the sudden wave of these warnings? Or maybe even put together some “Best Practices” for locking things down without breaking everything?

Curious if I’m the only one who feels like Google just woke up one day and decided to check our homework. :sweat_smile:

@dnickel

I had put this as a note at the very first post a little while ago: [RELEASE] OwnTracks for Hubitat Presence Detection

For best practices, I'd recommend splitting the geocode and maps API into 2-keys. Geocode is really just hub out to Google, and unless you have a static IP for your router, that one is harder to lock down, and not as big of an issue.

The map's one can be called from anywhere, but locking it to cloud.hubitat.com at least restricts it to Hubitat.

3 Likes