In v3 via Owntracks, you could retrieve the entry and exit zone events (Waypoints - OwnTracks Booklet)
The accuracy is what it is, but this allows detecting the presence of a user at home.
The use case is rather simple, a user having configured Owntracks via open API emits an entry or exit zone event. A scene on Gladys will act to mark or not the user as present. All kinds of scenarios can follow.
Thanks for the post!
Can you tell me exactly about your use case? What do you need it for?
I updated my original post
Oh, I see, so now you’re really talking about managing Owntracks zones.
I thought you were referring to Gladys’s native zones.
Why Owntracks zones vs. Gladys’s native zones?
And what is your use case for using zones in general?
It doesn’t matter, the goal is to have an event.
It’s in my post.
Owntrack sends the location, if I enter the zone then an event is emitted, I can trigger a scene (mark me as at home, turn on the outdoor lights, etc.)
Or even open the electric gate.
Ok thanks for the details!
For me, we need to develop this natively, so if OwnTracks disappears or we want to use another location app, we can still create scenes 
We need to redevelop the entire v3 stack.
Functional Specification:
Hello,
I’m following up on this post if it interests anyone, I had started on the subject Handle_Owntracks_MQTT_messages and I digressed
So for the moment I’m at:
ToDo
Technically:
I have a branch here.
I’m not very comfortable with this, so it’s not a topic that’s moving fast. Let me know if it’s to be discarded or if someone wants to lend a hand or even take over the subject to move forward faster.
Great! Top if you give us a hand with these features.
Don’t hesitate if you have any questions along the way
Hello everyone!
I just finished developing this feature, which is currently being built on the Docker dev image 
To show you, it looks like this.
The Map tab is now full-screen, with the displayed areas:
You can click on « Create an area » to display this screen:
And it is possible to edit an area by clicking on the area to edit (simply):
Then, in the scenes, it is possible to create 2 types of triggers.
User enters the area:
User leaves the area:
The DEV build is in progress here: https://github.com/GladysAssistant/Gladys/actions/runs/901904397
I developed this feature with frontend tests on Cypress, and honestly it was awesome! @AlexTrovato Cypress really rocks!!
I’m open to any feedback as usual!
Hello 
I was able to test this evening and here are my comments:
Last point, I find that it’s starting to be complicated to distinguish these notions:
For those interested in Owntracks => MQTT, I can work on this issue (since I already have something that works). But there are still tests, configuration, front-end, documentation …
Hello @cicoub13 and thank you so much for taking the time to test!
Well spotted, it’s true that in the house we indicate it, I will add it!
Indeed!
Great!
Not bad, this development was done a long time ago and indeed there are no websockets. It can be easily added, I will change that.
What do you find unclear?
I find the names quite explicit though.
After what may be confusing, is the difference between the « house » and the areas. We need to make the user understand that the house is a « concept » in Gladys, and that to make a scene where the user enters/exits the house via an area, you need to make 2 scenes:
The labels are easy to understand. It’s more about how these actions are triggered.
In some cases, it will be automatic (like the zones).
In other cases, you need to trigger the action via a scene (user presence via a Bluetooth device if I understand correctly).
I haven’t used user presence and empty home much, I will test.
In the case of detecting presence in the house, it’s up to the user’s choice, absolutely everything is possible:
Perhaps a link in each box to an explanation in the documentation would be better?
In any case, I try to explain all this as much as possible in the videos I have been making recently. After that, I don’t know if we can do better in the UI, the labels and descriptions of each box seem quite clear.
@cicoub13 I’ve made all the fixes you suggested
The small hint « click on the map »:
User positions are now updated in real-time with websockets
The PR is here:
Also, there was a bug I noticed while using the feature, the distance calculation between a user and an area was in kilometers and not in meters, and therefore the zone exit was not working (gladys was comparing meters with kilometers.. )
I’ll merge this as soon as the tests pass, and I’ll do a new dev build!
Edit: it’s merged, dev build in progress: https://github.com/GladysAssistant/Gladys/actions/runs/927307843
The corrected dev build is available on the Docker dev tag
Super I’m testing tomorrow
Indication « click on the map » 
Live update via websocket on the map
Test zone exit trigger
Very intuitive and easy to use (whether on the map or in the scenes)
Thank you for taking the time to test @cicoub13 
It will be included in the next release!
This feature is now live in Gladys v4.4
