[APP][Pro] Presence Fusion — combine several devices into Homey’s native user presence

Apps
,
1

Presence Fusion — combine several devices into Homey’s native user presence

Presence Fusion automatically drives Homey’s native presence from several devices (phone / Smart Presence, Beacon, Nut, etc.).

The goal: fewer false home / false away events when a single source is flaky. It replaces a custom Flow to combine multiple devices — link your sources, Fusion writes Homey presence, and your presence-based automations keep working.

:link: App Store

:sparkles: What it does

  • Merges multiple sources into user.present (Homey native presence)

  • Settings: automatically lists Homey users — enable a person, link devices, set mode and delays

  • OR / AND / quorum modes + confirmation delays (home / away)

  • Presence overview widget — who’s home and since when, each linked source detected or not, + optional Auto / Home / Away force

  • UI in English and French

:gear: Setup (a few minutes)

  1. Install the app (Homey Pro)

  2. Create a Homey API key with Presence (required — apps cannot write presence otherwise)

  3. Apps → Presence Fusion → Configure → API key tab → paste → Save

  4. Enable a person, link devices, set mode / delays

  5. (Optional) Add the Presence overview widget to a dashboard

API key:

  1. my.homey.app → Settings → API Keys → New API Key

  2. Check Presence (homey.presence)

  3. Copy the key (shown once)

  4. Paste it in the app

:warning: Avoid conflicts

For each managed person:

  • turn off Homey location-based presence

  • don’t use other Flows / apps that also force home/away

Otherwise they conflict and presence becomes unreliable.

:light_bulb: Usage ideas

  • Phone Wi‑Fi + Beacon / Nut for more reliable presence than one source alone

  • OR mode: as soon as one source sees the person → home (responsive)

  • AND / quorum: require several sources before switching (fewer false homes)

  • Longer away confirmation delay to reduce flapping

  • Widget: who’s home, since when, which sources are detected

  • Force Home / Away from the widget when a source misbehaves, then return to Auto

  • Several Homey people: each profile with its own sources and rules

:wrench: Support & links

Feedback, ideas and bug reports welcome :slightly_smiling_face:

2

Presence is flipped.

Just started trying your app. It is working for my iphone and apple watch but it inverts my wife’s presence with her iphone and/or apple watch.

Scenario: She is home and I see is marked as being home in homey. I add her iphone and/or watch to fusion and a few seconds later Presence ‘events’ she is not home.

I sent you a diagnostic report I took just after the event.

3

Hi Chuck,

Thanks a lot for the diagnostic report — that helped pinpoint it quickly.

This isn’t really “presence flipped” for Mary. The logs show that for her iPhone and Apple Watch, Presence Fusion auto-selected the wrong capability: alarm_battery instead of alarm_is_home.

alarm_battery is a low-battery alarm (false = battery OK). Fusion currently maps that as “away”, so as soon as you link those devices it thinks she’s away even though she’s home. After the away delay, it then writes that to Homey’s native presence.

For you it works because your devices are on alarm_is_home (the real home/away signal).

Fix you can apply right now:

  1. Open Presence Fusion settings → Mary
  2. On each linked source, tap Edit → set the capability to alarm_is_home (not Automatic / not alarm_battery)
  3. Save

I’ve already fixed auto-detection for the next release (alarm_is_home preferred, alarm_battery never auto-picked; existing Automatic links will correct themselves on restart). It still needs to go through Homey review, so it won’t be available immediately — the steps above should unblock you in the meantime.

Sorry for the hassle, and thanks again for the clear report!

4

Wow, thanks for such a quick response. I changed the iPhones and watches to ‘Is device at home’ and 60 seconds later I correctly got the ‘away’ event.

Did I miss this setup step?

Anyway, it’s working now. Thank you!

5

Glad it’s working now!

You didn’t really miss a setup step — Automatic is supposed to pick the right capability. In your case it wrongly chose the battery alarm instead of “Is device at home”. That’s on the app, not on you.

Tip: after adding a source, it’s still worth a quick look at the capability chosen by Automatic, and change it if needed — devices can expose several alarms, and the right one isn’t always obvious.

v1.1.5 is live and fixes that auto-detect. Homey should update Presence Fusion automatically; after the update, a restart of the app is enough for remaining Automatic links. Since you already set “Is device at home” manually, you’re all set either way.

Thanks again for the report — it helped a lot.

6

Another question.

I didn’t get the ‘home’ event until well after she was already inside. I’d like the event much earlier.

Enough time to:

  • determine if she’s really coming home (instead of just passing by)
  • open garage door or unlock front door
  • turn on lights, set HVAC, music, etc.
7

Presence Fusion doesn’t detect presence itself. It only combines several devices you choose and writes Homey’s native presence from that — so your Flows keep using the usual home/away cards.

The point is reliability: one stronger presence signal built from several devices, instead of trusting a single flaky source.

The “home” event can’t arrive earlier than those devices flip to home. In your setup that’s Find My (“Is device at home”), plus Fusion’s Confirm home delay (settings for that person). If Find My updates only after she’s already inside, Fusion — and anything driven by native presence (garage, door, lights…) — will be late too.

Fusion doesn’t invent an earlier arrival — it only fuses the signals you give it.