# \[APP\]\[Pro\] Location and Presence (Owntracks)

**URL:** <https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126>\
**Category:** Apps\
**Tags:** app, tools, presence, howto\
**Created:** [December 8, 2018, 6:56pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126 "2018-12-08T18:56:48Z")\
**Posts on this page:** 20\
**Page:** 21

<div class="post-metadata">

**Author:** ![Headstand8213](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/headstand8213/32/56443_2.png) [@Headstand8213](https://community.homey.app/u/Headstand8213)\
**Post date:** [May 14, 2026, 3:36pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/416 "2026-05-14T15:36:50Z")

</div>

Installed Mosquito (MQTT) on my Raspberry Pi and now using Location and Presence without many problems.

FYI, could not find any mention of it.

Read in the Owntracks booklet  
from this URL:  
[Region Monitoring](https://owntracks.org/booklet/features/ios/#region-monitoring-with-automatic-monitoring-mode-change)

### Region Monitoring with automatic monitoring mode change[#](https://owntracks.org/booklet/features/ios/#region-monitoring-with-automatic-monitoring-mode-change)

_Available in version \> 16.x.x_

Create a region with a name ending with `'|<monitoring mode on enter>|<monitoring mode on exit>`. E.g. `Home|1|2` will switch to monitoring mode 2 (Move Mode) when exiting the region `Home` and will switch back to monitoring mode 1 (Significant Mode) when entering the region `Home`.

Please note automatic change to monitoring mode -1 (Quiet Mode) will stop all further region detection.

As the automatic change to monitoring mode 2 (Move Mode) does not work reliably under all circumstances, we recommend to add a `+follow` region, which will trigger a wake up of the app when moving.

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 3, 2026, 2:46pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/417 "2026-06-03T14:46:22Z")

</div>

I am having the same issue. I get an Error: java.net.UnknownHostException: Unable to resolve host “(homey ID)…” from OwnTracks. I have checked the address so many times, and it matches the required format per the first message.

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 3, 2026, 2:47pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/418 "2026-06-03T14:47:04Z")

</div>

I’m getting and unresolved host error using this format in OwnTracks.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 3, 2026, 6:43pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/419 "2026-06-03T18:43:41Z")

</div>

> [@BV-homey](#):
>
> Unable to resolve host “(homey ID)…

- Did you add `.connect.athom.com` right after the homey cloud ID number?  
You’re supposed to look up the actual Homey ID (a long token), and insert it to the URL.

- Check your URL for hidden characters, an whitespaces on both ends

Please share your (anonimised) URL used

This URL should look like:

> [@Peter\_Kawa](#):
>
> ‘[https://663xxxxxxxxxxxx.connect.athom.com/api/app/nl.scanno.owntracks/events/54f9xxxxxxxxxxxxxxx’](https://663xxxxxxxxxxxx.connect.athom.com/api/app/nl.scanno.owntracks/events/54f9xxxxxxxxxxxxxxx%E2%80%99)
> 
> ![Screenshot_20260316_230545_OwnTracks](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/0/7030548b89ae5fb5b38598c7bc42004b00cc638b.jpeg)

The format:

> [@scanno](#):
>
> The URL you have to enter here is as follows:
> 
> > **https://[homey cloud-id].connect.athom.com/api/app/nl.scanno.owntracks/events/[tokenid]**
> 
> where is the Athom Cloud ID of your homey that you can find in Settings/System.  
> The tokenid is the id that is generated when you added the user.

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 3, 2026, 11:19pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/420 "2026-06-03T23:19:00Z")

</div>

Yes, I did. Here is my screenshot

 ![4266](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/9/09a115b49e10300cc626edf688d38a79404277d5.jpeg)

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 4, 2026, 10:06am UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/421 "2026-06-04T10:06:23Z")

</div>

I see.  
My guess would be Homey ID is not entirely correct.  
You can also find it in the URL of my.homey.app, and make sure to select the correct Homey first.

Can you run a test by sending a webhook to Homey?  
You can just open it with a browser, and it should return `ok`:

This one per Cloud:  
[https://webhook.homey.app/your\_homey\_id/my\_event](https://webhook.homey.app/your_homey_id/my_event)

And this one per LAN (local):  
http://my\_homey\_ip/webhook?event=my\_event  
(note: use http, not https)

First create this flow; it should respond to it:  
_please leave out the “And” card!_

 ![17359420564131103472856122805556](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/8/d8053356b9fb87d78b4c78820675d59f21074474.png)

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 4, 2026, 1:56pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/422 "2026-06-04T13:56:40Z")

</div>

I get the OK on the web browser when testing the Cloud web hook. I can’t get the notification to generate though. Is my flow wrong?

 ![4270](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/8/f890be36d319839a8256002a6521dbc61ee8aab0.jpeg)

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 4, 2026, 2:04pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/423 "2026-06-04T14:04:38Z")

</div>

Here is the webhook test screen

![Screenshot 2026-06-04 090355](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/7/373905f1424cd1264c52d26c81121e5a5dc7e217.png)

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 4, 2026, 5:23pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/424 "2026-06-04T17:23:23Z")

</div>

The trigger card should listen to `my_event`  
not to `Test` as the event name here is **my\_event**  
And please avoid using capitals, linux sees `T` and `t` as different characters.

> [@BV-homey](#):
>
> I get the OK on the web browser when testing the Cloud web hook

OK, this confirms it reaches a certain Homey out there, but it’s not yet sure it’s _your_ Homey.

So adjust the flow and test again please.

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 4, 2026, 11:28pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/425 "2026-06-04T23:28:32Z")

</div>

Okay, I got a successful test!

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 5, 2026, 12:24am UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/426 "2026-06-05T00:24:41Z")

</div>

Cool. Did you test with the cloud webhook? Because that one uses the Homey ID we use in the Owntracks URL.  
If it works per cloud webhook, we’re sure the Homey ID you use is correct.

Next Q: did you already add a waypoint a.k.a. geofence in the Owntracks phone app?

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 5, 2026, 11:37am UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/427 "2026-06-05T11:37:13Z")

</div>

Yes, I tested with cloud webhook.

I added a geofence (waypoint) in Owntracks. It accurately shows when I’m home. I haven’t looked at it while away yet.

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 5, 2026, 9:23pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/428 "2026-06-05T21:23:09Z")

</div>

I’m now getting SSLHandshakeException.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 5, 2026, 10:19pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/429 "2026-06-05T22:19:15Z")

</div>

Very odd. Something is interfering here. If the webhook works, the Onvif URL should work as well…

1. Do you use _any_ network influencing tool at home, like permanentVPN, AdGuard, PiHole, vLANs, firewalls, Fr¡tzbox.

2. Do you have a fixed IP address, or does your provider use CGNAT ( = shared external IP address with other users)?  
If CGNAT, request for a dedicated IP address at your internet provider. They should honor your request.  
(CGNAT is a nasty way to make their problem your problem)

3. Does your phone always use a VPN connection when your away?

4. Do you use Homey port forwarding? (not necessarily related, but …)

5. I have to ask, sorry, but, is the Homey app Location & Presence actually running 24/7?

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 8, 2026, 6:11pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/430 "2026-06-08T18:11:45Z")

</div>

I’m back to the unknown host error. Not sure what changed.

No VPN on my phone or network tools.

I don’t have fixed IP, and I’m pretty sure my provider doesn’t offer it based on a quick search.

No port forwarding.

I guess I’m not sure on the app. I don’t have it turned off, so I assume it’s always running?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 8, 2026, 9:04pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/431 "2026-06-08T21:04:16Z")

</div>

> [@BV-homey](#):
>
> I don’t have fixed IP, and I’m pretty sure my provider doesn’t offer it based on a quick search.

No sorry, I put it wrong, I meant to say do you have a unique IP (which can be a DHCP address, those tend to stay unchanged for months), or does your provider connect you using the same IP for multiple customers (=CGNAT)?

Weird thing is, the cloud webhook works well. So should the URL used with Owntracks, _ **if** _ the L&P app runs @ Homey.

When these errors keep popping up, I’d like to suggest to uninstall both Owntracks and L&P, and reboot phone and Homey and start fresh.

> [@BV-homey](#):
>
> the app. I don’t have it turned off, so I assume it’s always running?

Not quite. It could crash, or get disabled by Homey memory/cpu thresholds, or it can just not be responsive without the “crashed” status.

I do have to mention it truly runs rock solid with my Pro 2019s and -2026

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 29, 2026, 2:05pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/432 "2026-06-29T14:05:53Z")

</div>

Finally got around to uninstalling, reinstalling, and trying everything again. Still getting a 400 error.

I have Starlink, so I’m wondering if the CGNAT is the problem.

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [June 30, 2026, 7:52am UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/433 "2026-06-30T07:52:07Z")

</div>

For webhooks, this shouldn’t be an issue. There are no ports forwarded for those, Homey uses a persistent connection to the servers, and then it becomes remotely reachable at `cloudid.connect.athom.com`, no port forwarding or P2P is used here so the cgNAT restrictions are not applicable.

---

<div class="post-metadata">

**Author:** ![BV-homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bv-homey/32/120799_2.png) [@BV-homey](https://community.homey.app/u/BV-homey)\
**Post date:** [June 30, 2026, 3:45pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/434 "2026-06-30T15:45:14Z")

</div>

So is there a typo in an address somewhere? I’m still getting an error from OwnTracks for Unknown Host Exception. It says No address associated with host name.

---

<div class="post-metadata">

**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\
**Post date:** [August 26, 2026, 10:12pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/435 "2026-08-26T22:12:08Z")

</div>

Is / would it possible to create an avatar for each user that shows up in OwnTracks?

I’m using the HTTP method and I see it should be possible by returning the following in response when the Android phone posts the location. :  
`[`  
` {`  
` "_type": "card",`  
` "tid": "AR",`  
` "name": "Adrian",`  
` "face": "iVBORw0KGgoAAAANSUhEUgAA..."`  
` }`  
`]`

Where “face” is the Base64-encoded PNG

[Previous page](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126.md?page=20)

[Next page](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126.md?page=22)
