# 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:** 1\
**Showing post:** 11

<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 😀

---

_[View the full topic](https://community.homey.app/t/built-in-presence-geofencing/146978)._