[APP][PRO] Smart Presence - Presence detection based on smartphones connected to your Wi-Fi

Hi.

Here is the log code: 79a04300-4d5a-4e4f-a9f3-875e92708faa

I unfortunately am travelling and internet access is rare. Therefore I could not comply with the procedure you requested. - But from my own logs I could see, that the „last person left“ event triggered at 13:16 and the individual „person x left“ event fired at 14:18.

The „absence delay“ is set to 1800 instead of the default 900.

Maybe this can give you some hints…

Well without the logs as requested, it’s hard to guess… even with limited connection, you can still obviously access Homey and restart the app and provide logs just after.

Anyway, please test Smart Presence | Homey

A new version has been pushed to production. Hopefully, everything works correctly for you.

If you notice a new inconsistency that you can reliably reproduce, please send me a debug report together with all relevant details and the exact steps needed to reproduce the issue.

Please note:

  • I only respond to debug reports and support requests written in English.
  • For configuration advice, usage tips, and general questions, please use the Community Forum.
  • I will not respond to debug reports written in an inappropriate or disrespectful manner, or to messages suggesting that I am personally obliged to provide support or implement a requested change.

0.9.11

24. 6. 2026
Fixed stale absence flow triggers after return, improved presence capability display, and added migration guard for missing presence capability on older devices.

0.9.10

7. 2. 2026
Reduced log noise by aggregating offline probe failures

0.9.9

7. 2. 2026
Fixed async presence error handling, stress-mode bounds, and host input trimming.

0.9.8

19. 1. 2026
Adjusted the Korean Flow condition titles

0.9.7

4. 1. 2026
Changed year date format to 2 digits

0.9.6

3. 1. 2026
New logo + re-added combined last seen date time

Before I will push new test version (I will take some cooldown - week or so to confirm we have no issues), what would you think about this functionality :

I was thinking about an older proposal to make Smart Presence useful for incidental guests, people without a trackable phone, and situations where Wi-Fi detection temporarily gives the wrong result.

What would you think about adding manual and timed presence overrides?

The idea is to let the existing presence quick action temporarily mark any configured person as present or away. Each person would have a configurable default override duration, initially five minutes. New Flow actions could also provide their own duration in seconds, minutes, or hours:

  • Keep a person present
  • Keep a person away
  • Resume automatic presence detection

While an override is active, the device would show whether the person is being kept present or away, together with the number of whole minutes remaining. The displayed countdown would update only once per minute, while the override itself would still end at the exact configured time.

For devices with an IP address, normal Wi-Fi checks would continue in the background. They would not cancel an active override, but the latest detected state would take over immediately when the timer ends.

Existing devices would remain in automatic mode unless someone explicitly uses the new controls. Existing Flows and normal presence detection would therefore continue working as before.

It would also be possible to add a manually controlled person without entering an IP address. This could be used as a reusable “General guest” device, but the feature would not be limited to guests—it would also work for household members and kids.

For example, a Flow could keep “General guest” present for three hours when guest mode is enabled. After those three hours, the device would automatically return to its normal state.

Would this approach fit how you use Smart Presence?

If so and I will not see any new issues, it will be relased in TEST within week or so.

Available in test :

0.9.12

Add timed manual presence overrides

Hi, since a few weeks Smart Presence has become unreliable for me.

Leaving home is detected correctly. However, when I return home, the app often does not detect that my phone has connected to the Wi-Fi again. The phone has a static IP address and nothing has changed in my network configuration. It is pingable.

The strange part is that restarting the Smart Presence app in Homey immediately fixes the problem. As soon as the app has been restarted, my phone is detected as present again.

This makes me suspect that the Smart Presence app somehow gets stuck or stops checking the device after some time. It still shows the device, but apparently no longer detects that it has become reachable again.

Has anyone else experienced this recently?

I would be happy to provide a diagnostic report if that helps. It would also be interesting to know whether the app has some kind of background process that can stop responding without generating an obvious error.

Device: iPhone 15 Pro

Thanks.

Can you make that more precise ? 1,2 …5 weeks ?

Please create diagnostic log before, observing the error …

Please create diagnostic log right after, when you see it got fixed.

…it will always shows the device but did you actually check the time stamps on it and history, that’s why I actually added it there.

…yeah, that could be problematic…any recent iOS update ? Also, did you check ?

ca. 4 Weeks.

Diagnostic Log before: 55ccf036-7dd2-4820-a921-93a4945fcb9e

Diagnostic Log after: 5d65a931-4ab3-46e7-82d3-816920bab90b

no iOS Update available. iOS 26.6.1

Wifi assist is turned off.

Thank you!

Are you sure your flows are right ?
I see only specific device being online, nothing else. Naturally after app restart, flow triggers First Person and First HouseHold Member fires. There is no issue observed. To troubleshoot it, I would suggest first to start with very simple flow with conditions, like those above + or naturally the basic flows.

The flows are correct. The problem is not that the flows are not triggering. The problem is that Smart Presence does not detect that I am back home.

For example:

  1. I leave home. Smart Presence correctly detects that my phone is offline and marks me as away.

  2. I return home and my phone is connected to the same Wi-Fi again.

  3. Smart Presence does not detect the phone as online, so my presence remains “away”.

  4. I restart the Smart Presence app in Homey.

  5. Immediately after the restart, the phone is detected as online again and the presence changes to “home”.

So the flows themselves are not the issue. They work correctly as soon as Smart Presence provides the correct presence state.

This has been happening for about 4 weeks. Nothing has changed in my network configuration. My iPhone has a fixed IP address, Wi-Fi Assist is disabled and I am running iOS 26.6.1.

The fact that restarting the app immediately fixes the problem makes me think that something inside the Smart Presence app stops checking the device or gets stuck after some time.

I have attached diagnostic logs from before and after restarting the app. Hopefully these can show what is happening.

Diagnostic Log before: 55ccf036-7dd2-4820-a921-93a4945fcb9e

Diagnostic Log after: 5d65a931-4ab3-46e7-82d3-816920bab90b

Could you please check whether the app stops polling/checking the device or otherwise gets stuck? The issue is reproducible by waiting until the next time I return home without restarting the app first.

Can you try with latest Smart Presence | Homey , if the issue persists ?

It works. Did you find anything suspicious in the diagnostic logs or was there a fix in the latest version related to presence detection?

Yes, the latest version includes a fix for presence detection. The diagnostic logs did not show a specific network error, as I mentioned already. but I have found that an internal update operation could occasionally remain pending and block later presence changes. Restarting the app cleared that operation, which explains why detection immediately worked again. The new version prevents automatic presence checks from becoming blocked this way.

It did not affect everyone because it was a rare timing issue. It only occurred when a Homey capability, storage, or Flow operation remained pending at exactly the wrong moment. Different devices, Flows, system load, and occasional app restarts meant that many users never encountered it.