Supposedly this is just part of how it works, or doesn’t work. The blame tends to get pushed to the phone and geo location, even though other apps seem to be a bit more reliable. I don’t get it, nor do I like it, as we heavily rely on the presence to automate our house. Even though this seems to have been an issue for quite a while now, I truly hope it is still being looked at and worked on, and not just accepted as is. My fear though, from reading between the lines of the comments of “how to help”, is that we just have to accept it, as there is nothing additional ST can do. I really hope that isn’t the case.
There are numerous threads regarding presence issues for both ios and andriod going back over numerous builds.
I have an Android, Samsung S6, and I have found that disabling battery optimisation and stopping apps going to sleep, a feature of Android, has made my presence issues virtually go away.
As an aside if I go into ST settings and have the location map open, I can see may presence moving around (not by much). This is not, I would suggest, an ST issue but more the way the phone triangulates your location.
PS. I had the same issues with my Tado presence detection.
If SmartThings thinks you left when you are still home, that is almost always a problem with SmartThings, or at least SmartThings struggling to overcome local interference.
If SmartThings thinks you are still home when you have actually left, and you are only signed in on one device, that’s almost always a problem with your phone not reporting its new position, and that will usually affect multiple apps, not just SmartThings. The problem is that as soon as you open an app, your position will probably be updated, which makes it hard to prove that other apps aren’t having the same problem. So in order to troubleshoot this one, you have to set up a non-SmartThings app that also tracks you over time. The free life360 app is a good choice for this and has an official SmartThings integration. If it’s taking a long time to update your position, then to improve things you start looking at your own phone settings and use patterns.
If the problem is that you can’t set a Geopresence region which is working for you, but SmartThings is responding appropriately when you cross the region boundary, then you may need to switch to a different type of device or to a two-device system.
How important is presence to you right now?
I would also note the people seem to fall into two groups when it comes to troubleshooting presence problems. Both are legitimate. They just represent a different current need.
The first group is people who just want the SmartThings official mobile app presence to work the way it’s advertised. They don’t themselves want to spend much time on troubleshooting, they don’t want to look at alternative methods, they just want it to work the way they expected it to when they bought the system. Again, that’s an entirely legitimate position. For them, there are really only two things they can do: contact support and see if support can make things work any better, or try the SmartThings – branded presence sensor rather than the phone.
The second group is people (like me) who really need presence to work now because of requirements they have for their home automation system, and are willing to spend more time and money to come up with something that will work. (In my case, I am quadriparetic, use a wheelchair and have limited use of my hands. I need presence that works, even if it’s cobbled together from multiple systems and devices.) The good news is that there probably will be a way for most people to end up with presence that does work. The bad news is that it’s going to require some trial and error testing, it will probably require additional devices or apps, and it’s going to take time to get it set up right. Again, in my own case, it took about four months to get to the point where I had reliable presence detection. It was worth it to me, but I understand completely that it wouldn’t be worth it to a lot of people.
I contributed this to an error with smartthings updating the mobile app as that was the only change with my setup. The phones, devices and routines have been working perfectly for the last 6-8 months since I set it up. The app updated and I began having issues.
@Brad_ST I sent logs on Monday because my phone was showing I was home even though I was nearly 30 miles away.
Now…4 days later…My phone is showing the exact same thing along with the other phone in our Family. Both have been away from the home for over 2 hours, both over 30 miles away. If I open the app and give it time, it will refresh my status, but I have to reach out to the other person to do the same.
Nest shows we are in Eco/Away mode.
This is where it doesn’t make sense. It does seem like there is a “timeout” setting were it stops working after a few days. It has been fine since Monday, until today. I open the app numerous times a day as well.
I sent logs in again today, but last time I received the standard response about how phone’s presence sensors are not perfect, but to check settings… Hopefully these filed reports do make it to someone who can actually use and improve with them, not just to the representative who responds.
*It would be nice if there was a way for us to have ST refresh the “ping” to the phone from within the app. The pull down refresh doesn’t help. That way I could ping it for everyone when it gets stuck like this, and not have to reach out to them and have them open the app.
Dude… You might be my new superhero. That is awesome. Thank you for looking at it further. I realize things take time to get fixed, but from experience, the most difficult step is having someone listen and look into the problem. Thank you for taking it a step further. I truly appreciate it.
Please raise a ticket and if you can be as specific as possible, that helps. Comments about when the error occurred, if you had to open the app for presence to update, if you were connected to Wi-Fi, etc are all helpful.
One of the suggestions from ST, besides many other things to try, was to delete my wifes phone presence and re-install.
As I have numerous pistons/smartapps using it I was very reluctant to do it.
I finally bit the bullet and did as requested.
This did the trick. Yippee!!!
Not really a satisfactory way to cure the problem but it worked for me.
Lets see how long it continues to work for.