[RELEASE] OwnTracks for Hubitat Presence Detection

[lpakula]

@danabw

I think this is the week for it, and I think we're all in agreement, we are going to nominate you for an Oscar.

NOICE!

[lpakula]

@parish99

So things have been running well on 1.6.12, so I was leary abount updating but couldnt help myself. Probably should have listened to my gut, as things appear to be broken now.

Oh, simple fix. You need to go into the HE app, Regions, and select 'Home' again. It was a breaking change in a past release.

Noted that it's throwing errors though -- should be more graceful on that -- I'll fix that.

[DGBQ]

@nh.schottfam

For context sensitive IDE, it is challenging because of device variable 'redirection', that the IDE does not know what is in the device variable.

Thanks @nh.schottfam, my hope is @lpakula considers

@DGBQ

Could we explore the possibility of creating a clone named “otstatus”, with exactly the same data as “status” (direct link) for Webcore users? This could be a solution! What do you think?

proving a clone for use with Webcore.

Edit:
Thinking an Alias is a better word to describe this, not a clone.

[lpakula]

@DGBQ

@lpakula

I "borrowed" the name "status" from Life360. I think think "status" is a best fit word for it. Any other suggestions? It's showing the region you in, or the distance from home.

Oh, that's a bit of a bummer! It seems like there's a conflict preventing it from working with Webcore, using the current name if I understand @nh.schottfam correctly. Could we explore the possibility of creating a clone named “otstatus”, with exactly the same data as “status” (direct link) for Webcore users? This could be a solution! What do you think?

I would really like to use "status" in my piston but as of now I can not.

Thanks for consider it.

Oh shoot.. Pie eyed when I typed that original message. I meant "I DON'T think 'Status' is the best name for it'.

I'll query a jury of my peers today and see if they have a suggestion for an attribute that displays a place + time.

It can be anything other than 'status' for a name. If you are having issues, others will have issues, and the question about it will just get raised again.

[lpakula]

@JustinL

I fumbled around on GitHub looking at the iOS app. I don't think they publish the address information. Some asked a few years ago for it, but they declined in the interest of keeping data transfer low (hmmm...). I did see, though, that someone mentioned the Recorder is capable of doing reverse geocoding server-side? Wondering if that means, for those of us with iOS, we could install the recorder and pull the address into HE from the recorder? That would perhaps be an easier way to get the address, as opposed to adding reverse geocoding lookups in this integration for iOS folks.

I haven't found them to be overly responsive to changes either. Let me investigate 'Plan B' of having the HE app doing the looking on incoming locations.

I'm using the regular 'Recorder', but don't see any address info. I have the code pulled down, and will take a look tonight around this, but regardless, Google does have an API to do the check and it can be done in HE (phone was just cleaner since it's linked and done with each location).

[JustinL]

@lpakula

Google does have an API to do the check

Yup, I have used the geocoding API in my MultiPlace app and it works well.

[DGBQ]

@lpakula

It can be anything other than 'status' for a name. If you are having issues, others will have issues, and the question about it will just get raised again.

Thanks for clearing that up! An Alias reference from 'status' would be just as awesome. I find my words flow more smoothly after indulging in two cups of morning coffee. (my earlier wording left a lot to be desired). Cheers!

[lpakula]

@JustinL

Yup, I have used the geocoding API in my MultiPlace app and it works well.

Let me take a look!

[jb1]

@JustinL

Yup, I have used the geocoding API in my MultiPlace app and it works well.

I loved to use MultiPlace. Is there a chance to get this to work with OwnTrack? Due to the fact Life360 isn't working it would be nice to use MultiPlace in combination with OwnTrack!

[dnickel]

Will I still run into the map not working because I don't have the Google api key set up?
Unlike the Playstore one that does?

[JustinL]

@jb1

Is there a chance to get this to work with OwnTrack?

Glad you like it. Yes, I will update MultiPlace to work with OwnTracks once OwnTracks is at a stable state, or at least when reverse geocoding is implemented so that OwnTracks has addresses like Life360 did.

[danabw]

Yes, the custom version of the app does not include the Google Maps API key. It's the same as the previous version. Use the Play Store version if you want to use Google Maps w/out having to go through the steps required to add the Google Maps API key to @lpakula's custom version of the Android app.

[jb1]

@JustinL

Yes, I will update MultiPlace to work with OwnTracks once OwnTracks is at a stable state, or at least when reverse geocoding is implemented so that OwnTracks has addresses like Life360 did.

That's awesome. Cannot give more than one heart Thanks

[Jani]

@Jani

"OwnTracks: The 'Latitude', 'Longitude' and 'Radius' of the selected home region in the Hubitat OwnTracks app does not the corresponding region in Jani's mobile app. Select this member to have their regions updated or manually"

Can you check the HE app to see if you are running 1.6.23? There was an issue in the previous version that would display that error (and should not have) when a member left home. The warning is supposed to catch a mismatch if the hub lat/lon/radius said you were home, but the phone's region for lat/lon/radius disagreed (or vice versa).

Still get this warning but this time it wasn't my phone. It was my daughter's.

" app:13842024-01-24 18:34:34.630warnOwnTracks: The 'Latitude', 'Longitude' and 'Radius' of the selected home region in the Hubitat OwnTracks app does not the corresponding region in XXXX's mobile app. Select this member to have their regions updated or manually correct the mobile app coordinates."

App is the latest 1.6.24. Location update did t take a long time and when it finally located itself it threw that warning line to log.

[lpakula]

@dnickel

Will I still run into the map not working because I don't have the Google api key set up?
Unlike the Playstore one that does?

By default the APK defaults to the Google Map overlay. You can tab the blue layers button (bottom right on the map) to select "OpenStreetView". That will give you opensource maps. Someone mentioned that they saw accuracy issues with this, but I have not seen any issues. Once selected, the app will use that as the default, and no key is required.

[lpakula]

@Jani

Still get this warning but this time it wasn't my phone. It was my daughter's.

Can you check the 'home' region in her phone to see if the lat/lon/radius is the same one listed in the HE app? Is it happening all the time when you send a location from home, or just departure?

[lpakula]

@TMLeafs

Am I doing something wrong with HPM, I do Match Up and it only matches the driver, not the app so it wants to install another copy of the app code

Poking this in case someone else knows. I'm not sure how the matchup works.

[dnickel]

Yes it was me. Google maps has me withing meters of my house. OpenStreetMaps had me 3 doors down. (Not the band)

[jbwrd3]

I had the same issue did a repair on owntrack seemed to fix it.

[Jani]

All settings are the same.
It happens occationally and it doesnt matter if client leaves home or leaves additional place.

By the way Im seeing red lines in my phone's owntracks log. At the moment im at home and there is most likely no issues but those red lines are saying that client is failing to send message. Dont know what is that all about.

And this is one of those lines

2024-01-24 21:58:52.021 E MessageProcessorEndpointHttp: java.net.UnknownHostException: Unable to resolve host "cloud.hubitat.com": No address associated with hostname

Dns error.. Or what.. Seems to happen more that once..