Presence+
Test v1.10.38Reliable Home/Away automations without reacting to brief presence glitches.
Why Presence+?
A phone or presence source can briefly report Away and then Home again. Starting an alarm, changing the heating or turning everything off directly from that first Away event can therefore run an automation nobody wanted.
Presence+ treats Away as a candidate event. It starts a background countdown and triggers your Flow only when the person, or the whole household, remains away for the chosen number of minutes. A return during the countdown cancels it.
Trigger cards
[Person] has been away for [minutes]
Starts when the selected Homey user becomes Away. Only that person's return cancels this countdown.
Tags: person name, minutes away and away-since timestamp.
Everyone has been away for [minutes]
Starts when the last present Homey user leaves. Any person's return cancels this countdown.
Tags: minutes away, away-since timestamp, people counted and the last person to leave.
The delay must be a whole number from 1 to 10,080 minutes (seven days).
Examples
Turn the house off after the last person leaves
WHEN: Everyone has been away for 10 minutes THEN: Turn off all lights THEN: Set heating to Away
Notify when one person stays away
WHEN: Alex has been away for 30 minutes THEN: Send notification "Alex has been away since [Away since]"
How countdowns behave
- The wait runs in the app background; it does not keep a Flow card open.
- Each unique person-and-delay or everyone-and-delay configuration gets one countdown, even when several Flows use it.
- All matching Flows are triggered when their shared threshold is reached.
- A return followed by a new departure starts a new episode from that departure time, even if the previous trigger call is still finishing.
- Countdown state survives an app restart, and a threshold already fired during the same continuous absence is not fired twice.
- Changing, enabling, disabling or deleting a Flow refreshes the active countdown configurations.
Scope and limitations
- Presence+ uses enabled Homey users whose presence state is available.
- It filters short Away/Home glitches; it cannot improve how a phone or presence source decides the state itself.
- If the app is stopped for an entire Home-to-Away-to-Home cycle, Homey only exposes the current state after startup, so the missed transitions cannot be reconstructed.
See all parameters and output tags in the Flow Cards reference →