There is an ugly issue with Presence on this build. If presence was working before either using your mobile device or life360 this build has broke it. I have reported this 2 weeks ago and was very detailed on the issue as I spent the better part of 2 days working through the issue. Going back to the previous build app works just fine but you’ll be updated automajically and it will break again.
After 2 weeks I gave up and move all 50 of my device to Hubitat and put the ST hub away. Presence works perfectly with Hubitat and don’t need Life360, devices run faster and actually for the first time the wife said things are running faster and better.
Your welcome! It was nice working from home doing this at the same time, it made things easier in the end. I have had the HE hub for some time now, I tried the move about a year ago and the wife wasn’t buying into the whole thing. This time with what has happened she was fine with it and even said buy more stuff if needed! lol
Once I got going it went pretty good. One thing that bit me a few times, once I removed a device in ST and added it HE, I noticed that ST picked up the device again even though It was excluded, so 3 devices out of the 50 I had to exclude again on ST (and then power off the hub for bit) and the include on HE. Outside of that it wasn’t bad at all.
Not sure if this has been discussed
So I read somewhere or maybe misread it. Someone created automation/scene for each mobile phone. For example
Wife’s IOS - mobile presence
My android S10- Placeholder
I was having the issue/problem on Arrival/Back Home
So i created 2 separate Arrival/Back Home automation.
Going good so far and my Issue with mobile presence hasn’t returned.
I was having a similar issue where the Disarm on Arrival automation would not disarm the STHM. (I’m on Android.) Here’s how I fixed it.
My automation was created by the migration wizard, as I just recently migrated from Classic. I was rooting around the IDE and noticed that there are two entries for my phone, one as a placeholder and one as a mobile presence device. (I only remember the placeholder when looking before, so the mobile presence entry is either new or I missed it. I found it this time by sorting.)
In any event, I have 2 devices with the same name. In the Disarm on Arrival automation, I selected the “Who” to edit it and discovered my identical devices. I unchecked the one that had been checked and checked the other one, and the automation now works. I suspect that the automation was using the placeholder device and not the mobile presence devices and that was causing the automation to fail.
(As an aside, prior to discovering this, I also went into the Advanced Options for the Location mode and turned on the precondition. I haven’t turned it off as of yet, so I have no idea if that’s absolutely required or not.)
And thus your problem, If your Wife’s IOS device says Mobile Presence, and your device says Placeholder, then your device will never work. Placeholder is not Mobile Presense and this is an issue. I’d be surprised if they fixed mobile presence as they don’t even have my ticket opened anymore. Sorry you’re having the Presence issue, one of ST downfall for a long time.
My Android location issues of late are definitely a Google Location Services problem.
Earlier today my Internet provider dropped completely for about 5 minutes. Both Nest and SmartThings notified that I was suddenly Away. Neither one of them recovered to Home status so I changed them both manually and went on with my day.
A couple of hours later I realized that Nest was popping motion notifications that should not go off when I’m Home.
At this point I was outside on the unroofed sun deck. I opened up Google Maps and saw it’s “circle of uncertainty” was large, probably a couple of miles across. It only took a few seconds before it zeroed in on my exactly location. As soon as Google maps CofU shrank down, I got a “Hal is Home” notification from SmartThings.
I’ve experimented a bit. The “GPS Status and Toolbox” app is pretty useful. I can see all the satellite fixes dropping off when I step under the metal roof. When that happens the Maps CofU grows larger and location sometimes jumps to a town about 20 miles southwest of my location.