# Built in Presence geofencing

**URL:** <https://community.homey.app/t/built-in-presence-geofencing/146978>\
**Category:** Ideas & Suggestions\
**Created:** [December 15, 2025, 9:12pm UTC](https://community.homey.app/t/built-in-presence-geofencing/146978 "2025-12-15T21:12:03Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Heckles](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mark_heckles/32/153019_2.png) [@Mark\_Heckles](https://community.homey.app/u/Mark_Heckles)\
**Post date:** [December 15, 2025, 9:12pm UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/1 "2025-12-15T21:12:04Z")

</div>

Is there any chance we can either be able to adjust the geofencing distance manually, or can you please make it a bit more accurate. I don’t really want flows to start when I’m nearly 5 minutes away from my house.

Thanks guys 😄

---

<div class="post-metadata">

**Author:** ![Asterix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/asterix/32/45768_2.png) [@Asterix](https://community.homey.app/u/Asterix)\
**Post date:** [December 16, 2025, 4:17pm UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/2 "2025-12-16T16:17:32Z")

</div>

You can control this yourself by adding a delay.

So if you are 5 minutes away when you enter the geofence, start the flow with a delay of 4 minutes.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [December 17, 2025, 9:54am UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/3 "2025-12-17T09:54:36Z")

</div>

1. That isn’t possible in general. When he enters the geofencing area, he is immediately and automatically set to “at home.”. Currently, there is no way to delay this.

2. Let’s assume that it were somehow possible. But then there would be the following problem:  
5 minutes away if he walks  
1 minute away if he drives  
So if he drives, he would have to wait 3 minutes before being registered as “at home”.

3. He enters the geofencing area by car and the 4-minute delay starts. Before the 4 minutes have elapsed, he leaves the geofencing area again. When the 4 minutes have elapsed, he is marked as being “at home”, even though he is no longer in the geofencing area.  
Instead of the delay, you could use a timer app. When leaving the geofencing area, you could then stop the timer. However, this would only work for Homey Pro owners, as all timer apps are community apps.

---

<div class="post-metadata">

**Author:** ![Asterix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/asterix/32/45768_2.png) [@Asterix](https://community.homey.app/u/Asterix)\
**Post date:** [December 17, 2025, 10:50am UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/4 "2025-12-17T10:50:17Z")

</div>

Hi Dirk, you got it wrong, it’s not about the delay of entry into the geofence, but about a delay after what happens next.

When: Geofence Enter

Then: Turn on the light with a delay of 4 minutes

Mark\_Heckles understood it 😉

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [December 17, 2025, 11:25am UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/5 "2025-12-17T11:25:16Z")

</div>

Okay, I did misunderstand that, sorry.

A possible workaround for my point 3 could then be the following:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/f/5f72d7bc872e562552f676639610f89905c151b1.png)

However, this would still not solve the problem I described in point 2.

I think all of us would appreciate it if Athom would make the geofencing distance adjustable, as it is already possible with various third-party geofencing apps, right?

---

<div class="post-metadata">

**Author:** ![Asterix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/asterix/32/45768_2.png) [@Asterix](https://community.homey.app/u/Asterix)\
**Post date:** [December 17, 2025, 1:57pm UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/6 "2025-12-17T13:57:31Z")

</div>

Yes, this is right.

But as you have probably already experienced yourself, Athom is not the fastest company when it comes to improving existing Functions, unfortunately.

On the other hand, there are a few other things that play a role in the correct functioning of Geofence.

I wanted to use my post to point out a solution that is currently possible.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [December 17, 2025, 3:26pm UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/7 "2025-12-17T15:26:24Z")

</div>

> [@Asterix](#):
>
> Athom is not the fastest company when it comes to improving existing Functions, unfortunately.

That’s why I use a third-party geofencing app, called [Geofency](https://www.geofency.com) for iOS, instead of the Homey built-in. With this app, you can adjust the geofencing area. When I enter or leave the geofencing area, web hooks are sent to Homey and my “home” status is changed accordingly. 😎

> [@Asterix](#):
>
> On the other hand, there are a few other things that play a role in the correct functioning of Geofence.

Definitively!

---

<div class="post-metadata">

**Author:** ![Mark\_Heckles](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mark_heckles/32/153019_2.png) [@Mark\_Heckles](https://community.homey.app/u/Mark_Heckles)\
**Post date:** [December 21, 2025, 5:41pm UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/8 "2025-12-21T17:41:28Z")

</div>

This is fine for those that use Apple devices. But alas I do not lol

And setting up most geofencing apps on Android is a ball ache ..🤣

---

<div class="post-metadata">

**Author:** ![deejayreissue](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/deejayreissue/32/81912_2.png) [@deejayreissue](https://community.homey.app/u/deejayreissue)\
**Post date:** [December 21, 2025, 11:01pm UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/9 "2025-12-21T23:01:10Z")

</div>

What’s wrong with using contact sensors, delays, logic and the standard presence?

”X has been set to AWAY for more than X hours”  
”Contact sensor is triggered AFTER X comes home”

I’ll be doing something similar soon when the new IKEA MYGGBETT sensor is released.

---

<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:** [December 22, 2025, 1:13am UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/10 "2025-12-22T01:13:55Z")

</div>

I’m fond of Macrodroid, a geofence trigger should be ‘doable’!

This automation checks if I leave geofence1 or geofence2 or when my wifi SSID is out of range - of course 1 geofence should do;  
When it detects I left, it sends a status webhook to Homey:

 ![Screenshot_20251222_021506_Google](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/0/d029a01e2a7d56989bd482c81d316b6e029f1581.jpeg)

This flow will get triggered

 ![Screenshot_20251222_021143_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/b/cbd42f4a3a7fd55aa0e939524bcc351965db90c6.jpeg)

---

<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, 3:50am UTC](https://community.homey.app/t/built-in-presence-geofencing/146978/11 "2026-03-18T03:50:20Z")

</div>

I’m having trouble getting third party geofencing solutions to work (ie. OwnTracks with Presence and Location) - see [[APP][Pro] Location and Presence (Owntracks) - #385 by Michael\_Stephens](https://community.homey.app/t/app-pro-location-and-presence-owntracks/5126/385) .

If there was just a little bit more control over the built in presence geofencing, specifically the ability to define the radius, I wouldn’t need to worry about third party solutions.

I would certainly vote for the suggestion to allow a user configurable radius 😀
