# \[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:** 20

<div class="post-metadata">

**Author:** ![Meruem](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Meruem](https://community.homey.app/u/Meruem)\
**Post date:** [March 9, 2026, 3:10pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/395 "2026-03-09T15:10:38Z")

</div>

Hi Michael. I’m with the same problem as you. Are you also using Homey Self-Hosted or Homey Pro? I have exactly the same errors (400) of you. When I try to just call the URL:  
https://MY\_HOMEY\_ID.connect.athom.com/api/app/nl.scanno.owntracks/OWNTRACKS\_USER\_ID  
It shows the error: Cannot GET /api/app/nl.scanno.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:** [March 9, 2026, 4:18pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/396 "2026-03-09T16:18:20Z")

</div>

> [@Meruem](#):
>
> I try to just call the URL:  
> https://MY\_HOMEY\_ID.connect.athom.com/api/app/nl.scanno.owntracks/OWNTRACKS\_USER\_ID  
> It shows the error: Cannot GET /api/app/nl.scanno.owntracks/

That’s not the issue, and cannot be tested like that:  
I get the same error when calling the URL from a browser, and my Owntracks + L&P work just fine

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

---

<div class="post-metadata">

**Author:** ![Meruem](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Meruem](https://community.homey.app/u/Meruem)\
**Post date:** [March 9, 2026, 4:30pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/397 "2026-03-09T16:30:32Z")

</div>

Oh, nice to know @Peter_Kawa! Thank you for your feedback! I didn’t know that was a normal error.  
After some time trying to make it work I just installed the MQTT Broker app and after some long time configuring it it’s now working with MQTT!

---

<div class="post-metadata">

**Author:** ![Michael\_Stephens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_stephens/32/120715_2.png) [@Michael\_Stephens](https://community.homey.app/u/Michael_Stephens)\
**Post date:** [March 10, 2026, 2:32am UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/398 "2026-03-10T02:32:41Z")

</div>

Hi @Meruem ,  
I’m actually glad to hear that I’m not the only one experiencing this problem!! It’s really frustrating, as the combination of OwnTracks and L&P is exactly what I need for some automation flows I’d like to create. Is the original developer of L&P (@scanno) still active in this forum?

I am using a Homey Pro (2023). I did have a go at trying to get MQTT working using the Homey MQTT Broker app. I got it working (OwnTracks sending location data to L&P) within my home network, but this is not very useful for detecting when people enter and leave geofences outside of my home. I was able to setup port forwarding through my home modem, but I couldn’t get OwnTracks to send location data to L&P via my phones mobile network (ie. the internet). Are you able to explain what setup you used in _ **Location and Presence** _, _ **MQTT Broker** _ and _ **OwnTracks** _ to get this to work?

---

<div class="post-metadata">

**Author:** ![Meruem](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Meruem](https://community.homey.app/u/Meruem)\
**Post date:** [March 11, 2026, 11:53pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/399 "2026-03-11T23:53:51Z")

</div>

Hi @Michael_Stephens, sure, I can try to help you. I’m using Homey in Self-Hosted using docker. I’m using Cloudflared Tunnel as DDNS and also to remote connection.  
In my OwnTracks app I used Connection MQTT with my router Asus DDNS (because I don’t have fixed IP) and in my router there is a configuration witth Port Forwarding TCP connection in the port used in MQTT (EX: TCP 8880) to Internal IP Address of my Homey Self-Hosted internal IP (EX: 192.168.X.X) and I also fixed his internal IP in my router DHCP though MAC  
This worked and even when I’m outside of WiFi it connects successfuly.

I’ll try again soon the configuration without MQTT and see if I can see anything to make it work.

---

<div class="post-metadata">

**Author:** ![WeWillSee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wewillsee/32/120753_2.png) [@WeWillSee](https://community.homey.app/u/WeWillSee)\
**Post date:** [March 16, 2026, 5:39pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/400 "2026-03-16T17:39:09Z")

</div>

Hi was trying to install this app and get them

Connected main goals is to make sure the presence works correctly based on the locations my Phone. I followed the instructions but how do I give/create a geofence location? This is in homey or in Owntracks?

The connection error will it occur in the Owntracks app or in homey? Because don’t see much possibilities in own tracks

---

<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:** [March 16, 2026, 5:52pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/401 "2026-03-16T17:52:27Z")

</div>

You’re supposed to create waypoints (geofences) with the Owntracks app.

(_Tussenpunten_ = Dutch for Waypoints)

 ![Screenshot_20260316_185425_OwnTracks](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/2/a222e2fa226715907efdaa5ffb47bc859938cfab.jpeg)

> [@Peter\_Kawa](#):
>
> create a waypoint @ Owntracks
> 
> ![Screenshot_20260305_165027_OwnTracks](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/e/8e5239d143f85e61c7eba19ccc38014ada805f1a.jpeg)
> 
> That one should appear in L & P:
> 
> ![Screenshot_20260305_164734_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/e/fef8c81e5ab2f6f1f4a61a4c8a2de6ba56a4edbf.jpeg)

If all’s configured well, those show up in the Location & Presence settings page

> [@bvdbos](#):
>
> ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/f/fb4061c7b23a8c646fa7ba091211f060ca8a2a89.png)

> [@\[APP\]\[Pro\] Location and Presence (Owntracks)](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/24):
>
> Working perfectly for some days already, my settings in the Homey-app: [afbeelding] And in Owntracks using Significant changes: Connection Private HTTP Host : https://\<cloudid\>.connect.athom.com/api/app/nl.scanno.owntracks/events/?token=\<tokenid from user\> Identification empty Advanced Locator Displacement : 50 Locator Interval : 30

---

<div class="post-metadata">

**Author:** ![WeWillSee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wewillsee/32/120753_2.png) [@WeWillSee](https://community.homey.app/u/WeWillSee)\
**Post date:** [March 16, 2026, 6:11pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/402 "2026-03-16T18:11:09Z")

</div>

Thx added a waypoint in Owntracks suppose it takes a while before seeing it in homey? Or is their a way to force a retrieval call?

---

<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:** [March 16, 2026, 7:42pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/403 "2026-03-16T19:42:21Z")

</div>

You can publish the waypoint(s) by tapping the 3 dots on the top-right, on the waypoints screen

 ![Screenshot_20260316_203250_OwnTracks](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/b/2bfc5d39e64e75f54d54bbd5bdbb608127f8a15d.jpeg)

In the log you’d see a line with “received” … “waypoints”:

 ![Screenshot_20260316_203553_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/e/8e8883b3a8bb6978d88e492943e8dee9e4741eb0.jpeg)  
(timestamps are in UTC time)

---

<div class="post-metadata">

**Author:** ![WeWillSee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wewillsee/32/120753_2.png) [@WeWillSee](https://community.homey.app/u/WeWillSee)\
**Post date:** [March 16, 2026, 8:26pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/404 "2026-03-16T20:26:48Z")

</div>

I did this is see the status changes in app itself but not homey I think I do have the impression I get a 404 error so different from the explanation above i tried to set those values but it give an error on those also

Not sure I’m doing something wrong?

 ![IMG_2475](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/5/5501bf5dceebb5be90ff5af520c7708a8440cf40.jpeg)

 ![IMG_2476](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/6/d6d00882276d3300aa3d3e19e5d2205ab15214e5.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:** [March 16, 2026, 10:04pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/405 "2026-03-16T22:04:17Z")

</div>

Error 404 means “not found”

“Invalid key specified” most probably means: the key is not exactly the same  
‘[https://663xxxxxxxxxxxx.connect.athom.com/api/app/nl.scanno.owntracks/events/54f9xxxxxxxxxxxxxxx](https://663xxxxxxxxxxxx.connect.athom.com/api/app/nl.scanno.owntracks/events/54f9xxxxxxxxxxxxxxx)’

 ![Screenshot_20260316_230545_OwnTracks](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/0/7030548b89ae5fb5b38598c7bc42004b00cc638b.jpeg)

The last token in that URL should be the same as the one which was generated here @ the L&P app:

 ![Screenshot_20260316_225827_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/7/c713001de8f3951ad71cef8a1cfa210203454cd7.jpeg)

---

<div class="post-metadata">

**Author:** ![WeWillSee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wewillsee/32/120753_2.png) [@WeWillSee](https://community.homey.app/u/WeWillSee)\
**Post date:** [March 17, 2026, 6:18am UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/406 "2026-03-17T06:18:38Z")

</div>

Yes I checked this and seems the same also double checked the cloud ID. I did try to press the # symbol to once generate a new one but this doesn’t seem tondo anything

---

<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:** [March 17, 2026, 2:31pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/407 "2026-03-17T14:31:10Z")

</div>

Maybe the Homey ID you entered in the URL is not exactly right; in that case Owntracks isn’t allowed to connect to your Homey:

> [@Peter\_Kawa](#):
>
> can you test this with your phone?  
> `https://webhook.homey.app/your_homey_id/event_name`
> 
> When you open this URL, it should return `OK`:
> 
> ![Screenshot_20260307_144448_Ecosia](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/b/bbd6570accece0ca759c56399598bcb5b1fb8ef0.jpeg)

---

<div class="post-metadata">

**Author:** ![WeWillSee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wewillsee/32/120753_2.png) [@WeWillSee](https://community.homey.app/u/WeWillSee)\
**Post date:** [March 17, 2026, 5:19pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/408 "2026-03-17T17:19:17Z")

</div>

That one gives ok

For the user id it is the full number yes from beginning to end?

I know have this

[https://68xxxxxxxxxxxxxxxx65ecb3.connect.athom.com/api/app/nl.scanno.owntracks/events/?token=d83xxxxxxxxxxxxxxxxxxxxxx7442cd1](https://68xxxxxxxxxxxxxxxx65ecb3.connect.athom.com/api/app/nl.scanno.owntracks/events/?token=d83xxxxxxxxxxxxxxxxxxxxxx7442cd1)

---

<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:** [March 17, 2026, 5:36pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/409 "2026-03-17T17:36:43Z")

</div>

OK, thanks.  
Yes, you should use the complete string.

However, your used URL is not right

> [@WeWillSee](#):
>
> [https://68xxxxxxxxxxxxxxxx65ecb3.connect.athom.com/api/app/nl.scanno.owntracks/events/?token=d83xxxxxxxxxxxxxxxxxxxxxx7442cd1](https://68xxxxxxxxxxxxxxxx65ecb3.connect.athom.com/api/app/nl.scanno.owntracks/events/?token=d83xxxxxxxxxxxxxxxxxxxxxx7442cd1)

The part with `?token=` shouldn’t be there;

The correct URL, as shown before, is:

> [@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)

Maybe that solves it, Maxime.

---

<div class="post-metadata">

**Author:** ![WeWillSee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wewillsee/32/120753_2.png) [@WeWillSee](https://community.homey.app/u/WeWillSee)\
**Post date:** [March 17, 2026, 6:04pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/410 "2026-03-17T18:04:33Z")

</div>

Perfect indeed apparently I copied too much from above 😅 now I have the impression it works

---

<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:** [March 17, 2026, 6:34pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/411 "2026-03-17T18:34:41Z")

</div>

Ah I see, the manual in the start post is still using an older URL version:

> [@scanno](#):
>
> https://.connect.athom.com/api/app/nl.scanno.owntracks/events/?token=

@scanno Is is possible to adjust the example URL,  
or  
are you willing to convert the start post to a wiki post?

---

<div class="post-metadata">

**Author:** ![scanno](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/scanno/32/8358_2.png) [@scanno](https://community.homey.app/u/scanno)\
**Post date:** [March 17, 2026, 8:13pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/413 "2026-03-17T20:13:49Z")

</div>

Changed to  
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.

I am willing to change to a wiki post, let me know the best way to do so

---

<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:** [March 17, 2026, 11:58pm UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/414 "2026-03-17T23:58:08Z")

</div>

Thanks! Much appreciated, Menno.

I found this howto  
[https://meta.discourse.org/t/editing-and-creating-wiki-posts/30801](https://meta.discourse.org/t/editing-and-creating-wiki-posts/30801).  
In case you’re not allowed to convert it, you’ll have to request it to a moderator

All I know about wiki posts is any member with the proper rights is allowed to edit the post.  
I’ve not seen a wiki post here getting f-d up just because of this.  
Probably mainly just because it’s a relatively unknown feature 😬

Example:  
The Tuya Cloud community app starting post was turned into a wiki for example, so I could update the info (dev Jurgen moved to H.A.).

---

<div class="post-metadata">

**Author:** ![Michael\_Stephens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_stephens/32/120715_2.png) [@Michael\_Stephens](https://community.homey.app/u/Michael_Stephens)\
**Post date:** [March 18, 2026, 2:30am UTC](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/415 "2026-03-18T02:30:36Z")

</div>

Menno (@scanno ),

Great to see you back in the forum. Are you able to explain what might be the cause of “HTTP code 400”?

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

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