Most successful presence detection?

I tried the "Convert to Shortcut" method in Home app. I then went for a drive around the block as a test and it appears to have worked for both my departure and arrival. Thanks for all of your help. I think you've got my automations to a good place.

I'm trying to do the same as @chicoquente. I noticed when I switched from the Shortcuts app to the Home app, per @aamann's suggestion, I could no longer trigger an action off of "When I leave" or "When I arrive". Instead, the only option was "When Anyone Leaves/Departs Home". Since I'm setting up this automation for each member of the family (each with their own virtual presence sensor via Maker API), how will this work? How does Home map "anyone" to the specific device for geofencing? TIA....

You missed a step where you set the people up.

  1. Open “Home” app.
  2. “Automation” tab.
  3. Top right corner select “Add Automation”
  4. Click “People Arrive” (and “People Leave” for your exit automation)
  5. Click the “i” beside “Anyone Arrives” and select just 1 person (do this over and over for each person you create an automation for). Hit “Next”.
  6. Scroll to the bottom and choose “Convert to Shortcut”.
  7. Follow the directions above.
3 Likes

I am in Android, HE app, life360, and Improved Mobile Presence aggregated with Presence Monitor, and that has been rock solid.

4 Likes

My birds look at me like... "yeah... and...?"

For me, redundancy has been key. In particular using a GEO fence solution plus local wifi.
For geofencing HomeKit has been the most reliable for me (I'm running an rPi with Homebridge on it).

See: [RELEASE] Combined Presence - #209 by SoundersDude
image

I'm just going to throw my two cents in here because I have had a rock-solid presence detection for years now, with no extra apps, all within Hubitat. There could be an easier way to do it now, I'm not sure with new things being added to Hubitat and new apps all the time, but I can't see changing something that has worked better than any application I have ever tried. I have tried Life360, Blue Iris implementation with their geofence, Tasker, etc. and somebody said that if one fails, they all do and that was accurate in my point.

I have two "virtual" WiFi Presence Sensors (one for me and one for my wife) that use a neat driver code from author Joel Wetzel (iPhone WiFi Presence Sensor). It has been some time but, if I recall, this driver searches for an IP Address every so often and and updates the presence sensors as needed. Of course, we have a very solid home network so this works for us and if our phones are off our network then we are not home and vice versa.

Of course, I have other triggers to make sure if there are hiccups here and there with this device/driver (maybe it will falsely say a phone is now on network or out of network after a restart or something); such as, I am a developer so I have a house panel next to the door we leave out most often where she or I click a leaving switch, which turns on outside lights, unlocks doors, opens garage door and shutting the garage door means that person has left and the garage opening and a person's phone being found on WiFi within the same minute means that person is home (if their presence has been gone). All done within Hubitat.

What I found is really nice with this is there are bugs in our phones sometimes and recently we have found that if our phone restarts, it connects to WiFi but has no internet. With this process, it checks the local network so it still finds our phone on the network and behaves as it should. I also pause rules with other rules as necessary to make sure there is no phantom such and such "is home" or "is away" stuff. Absolutely no hiccups unless the wife takes her phone off WiFi for some reason during the day while out of the house and forgets to turn it back on by the time she gets home.

Thank you for this. I was able to implement a version of this on Android with Llama and Automate. I am a die-hard Llama user, and just couldn't be bothered to recreate its very reliable cell polling feature in Automate. So, I just used Llama to create a Toast message when my phone leaves or enters an "area". This Toast message is one that Automate detects, then submits the HTTP request to toggle the virtual presence.
I had to use the cloud URL for the "departed home" scenario because I wouldn't be able to access it without VPN, and the local URL when "arrived home". Should I be concerned about any security issues because I exposed the cloud URL via Maker API?

Late to the party, but since this thread popped up, for others prerusing it...this has been perfect for me. Set it and forget it...

2 Likes

Your method has worked flawlessly since you first helped me set it up, however it has begun to lose reliability lately. Over the last couple weeks I have found for both my wife and I we are getting missed presence events based on departure or arrival. I have been using Combined Presence with other methods so the system is OK but I still find the builtin Hubitat method to be least reliable and want Homekit working rock solid again.

Have you experienced any issues as of late with the Apple method?

I'm not who you asked, but... I've seen some glitchy false present or not present events with Apple.

I use Apple Home, Alexa, Geofency, and my iPhone as presence detectors. I have switch to using the "Presence Monitor" app to combine those because I can specify that three of the four must be triggered to change presence. So far this method has been rock solid.

The only issue I’ve had at times was my wife’s phone running out of battery before coming home so her arrival wouldn’t trigger - can’t really blame the system for that…

Also, all our devices are always running the latest versions of iOS (including the (wired) AppleTV 4K acting as the home hub).

Since Hubitat came out with their beta HomeKit integration, I’ve changed to virtual presence sensors with switch capability so I don’t have to use the URL method/Maker API any longer.

Hi aamann - may I ask, what is the advantage(s) to using the virtual presence sensors you switched to instead of the URL method/Maker API? If you don't mind, could you describe your setup with the HomeKit integration, specific to presence? I've been probably around 98% successful with Maker API the last several weeks, but still glitches here and there. If there's something I can do to make this closer to 100%, that'd be nice. I'm using 3 iPhones and my wired AppleTV 4K for the hub, so very similar setup to yours, it sounds. Thanks in advance!

He is probably doing similar to what I do. I have the Apple home app flip the virtual presence switch as people arrive/leave using the Home app built in automation. It really doesn't get more simple than that, and for me is extremely effective.

I'm a fan of this method too. Since I set it up it hasn't let me down even once.

Not using the Maker API removes one additional level of indirection and make it more obvious in the Automations tab of the Home app as you can see directly what will happen without having to go into a shorthand then figure out which device the Maker API call corresponds to.

2 Likes

Nice, I’ve started using it. Too bad the virtual presence with switches can't be exposed to Alexa for routines (that I can tell). This would allow me to cut complexity even further. Thanks for the info!

The virtual presence with switch should be just as usable in Alexa. It shows up as a standard switch.

1 Like

To clarify, I do see it in Alexa devices (once exposed to Alexa, of course), but I can't seem to use it in routines. Do you see otherwise?

Sorry I know this is super old post, but how do I make Static IP address for my Hubitat hub to use this?