The idea was to work around unreliable presence sensors as best as theoretically possible. It can do nothing with a faulty sensor that doesn’t update at all. That’s like having no sensor.
3 Likes
Thank you for your app it's wonderfull!
If I can suggest something, could you add a delay to Boolean-OR Combiners?
I tried an automation:
When I arrive, unlock the door
Is nobody home start a playlist.
It didn't work because as soon as I arrive, the combine presence is turn on and therefore, my condition is not met.
If I could add a delay, for example 30 seconds, the rule will start and the someone is home will still be off. My condition will be true!
Thanks!
Practically everyone WANTS the most immediate presence change, based on every single OwnTracks, HomeKit, Life360, and other presence threads. First use case I've heard that wants a delay! 
Aside from whether or not the author implements the idea, I have a somewhat similar situation with turning on certain lights but use a different implementation. My rule simply says when I arrive, if no one ELSE is home, then do XYZ. My wife does things differently, so her arrival routine is different, so if she arrives and no one else (me) is home, the routine will do ABC.
1 Like
I have separate rules for when individuals arrive vs when the combined "Someone home" arrives. They work simultaneously, so they both work regardless of the timing of the combiner.
If you are ONLY wanting the music to turn on when YOU arrive and no one else is home, select the other presence devices that make up the "SOMEONE" combiner in the logic of "If nobody is home"
If you want the music to start anytime ANYONE arrives, then make a separate rule for when the combiner presence arrives.
I'm seeing Not present for combined presence with this diag log info. This has always worked flawlessly in the past. Rebooting and rolling back a few hub updates made no difference. Mobile app shows inside geofence but Away.
I'm wondering if this is the intended behavior. I've only had this issue lately, like the last few months. Occasionally, when my phone GPS thinks I've teleported outside the geofence and reports not present, the combined presence also changes to not present. I thought the standard container was supposed to prevent that? I've used this app for years now with no issues until recently. Sometimes I'm at home and all my lights just turn off because Hubitat thinks everyone has left and no one is home.
I know the wifi sensor isn't used to detect departures but for faster arrivals. But does it not protect against erroneous GPS departures as well?
EDIT: I went scrolling up a bit and found someone else with the same issue, so maybe the solution is to switch to using the advanced containers. I'm on an Android phone, so don't think it's an iOS issue.
If you are on android, try downloading the GPS Status app. In that app, go to the calibrate compass settings and see if it reports as red. EVERY time I had issues with my phone jumping in and out of geofence areas, this was the cause (Any magnetic mounts or cases with magnetic closures will instantly decalibrate the compass)
If it is red like the above, you have to rotate it on each of the axes until it returns to green.
1 Like
Is the advanced combiner solving the issue?
I have the same recent 'hubitat app inside the geofence but not present' issue, and it made me question how Combined Presence is supposed to work
It's always hard to tell with intermittent issues, but do far it seems to have fixed it. I configured it the way I had assumed the standard container already worked, like this
3 Likes
Thank you this has been driving me nuts. GPS should NOT trigger a departure if wifi based sensors are still present. I don't know why this isn't the default because it seems the most logical. What happens is inside the home the gps can drop satellites so Google location reverts to cellular triangulation, which puts me about 1/2mi outside my home. I don't want the zone that large. I will give the advanced combiner a try
