# Person presence

For each person, I've created a logic boolean variable, such as i.e. `presence-andreas`

Strictly it is not needed to create an aggregate variable for presence, since I'm currently only using the Homey mobile app as input for this state. But the reason I've done this, is that I expect that I might want to add multiple input sources for this value at a later stage to improve reliability.

If you are happy with the iOS app, you may stick that that for presence tracking, but to increase reliability you may add multiple input sources. I can reccomend using Geofency for iOS users. [I've documented how to setup Geofency](/aggregated-state/person-presence/geofency-and-webhooks.md). If you do not use iOS, most likely there is a similar app for Android. Life360 is another option.

![](/files/-LtnZdBuz7VDku9L0ohw)

For each person, I need two flows for each input source. If I need to expand this with multiple input sources later, the logic will be like:

* If Andreas came home \[mobile app], then set `presence-andreas` to true.
* If Andreas left home \[mobile app], then set `presence-andreas` to false.
* If Andreas came home \[geofency], then set `presence-andreas` to true.
* If Andreas left home \[geofency], then set `presence-andreas` to false.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://homey.solweb.no/aggregated-state/person-presence.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.