Mobile device presence broken with iOS 11

This. It is a good reminder, and I did check, but considering the majority of this forum is power users, I’m sure that was checked off the list a long time ago.

2 Likes

How many times @Brad_ST?

1 Like

Just search on iOS mobile presence under my alias @smart. Last 3 yrs now. Also, check @JDRoberts threads as well. He is the guru of all things.

2014: Setting up multiple iPhones (separate linked accounts) as presence sensors for dummies

On top of that since the favorites on dashboard was introduced, even though you are present or away, the background refresh fails even if your app is running in the background. When you bring the app to the foreground, it will take a few seconds to refresh to the correct presence status.

And on top of that do you really expect your missus to do all this crap? :wink: Force kill and relaunch the app? She will much rather kill us. :wink:

Ouch! Another related thread here.

Brad, with all respect, it’s broken. What you point to is not the issue. It was bad before iOS11 and now it’s worse. It’s all over the forum in multiple threads. I can’t speak for others but I can confirm my settings match what you state and always have.

Your Support group have even acknowledged it’s an issue and it’s being researched (supposedly).

3 Likes

As the title of the thread says, it’s the upgrade to iOS 11 (betas in my case) that broke this. Never had a problem before. There’s no point checking settings, it’s quite clear what the trigger was.

1 Like

Broke on my phone also as soon as I installed iOS 11. Opened a ticked with SmartThings and they acknowledged the problem. This is definitely an iOS 11 issue since I have another iPhone still running iOS 10.3.3 and it works as a presence sensor. I’m new to SmartThings and have made minimal investment in hardware and am reluctant to spend more money because of some basic issues such as this and false device health status. What amazes me is this was first reported 28 days ago and there is still no solution. This should have been a priority and fixed already.

As I said, I’m holding off with further investment in this system. I like it but it still seems like a hobby project then a commercial release.

@Brad_ST those settings have been in place for me forever as well - I would assume that the application would alert users if it doesn’t have the required access, right?

Doing some testing it seems that location does not get updated after the application has been jettisoned due to memory pressure while running in the background. My guess is that when the application is launched in the background due to a location change, it is trying to load things (the Dashboard with favorites which always take forever to load?) other than what is required to perform the actual location update and the system terminates the background process for taking too much time. I hope that launching the app in the background due to a location change doesn’t go through the normal startup process but only performs the presence update…

1 Like

@Brad_ST

All,

I just upgraded to iOS 11 on my iPhone 7 which has always worked flawlessly as a ST presence device. As soon as I exit the ST app, presence detection is broken. This appears the be the exact same behavior as other users have reported. Yes, Location Services and Background app refresh are enabled for the ST App.

I have reverted back to iOS 10.3.3 while Apple is still signing the old firmware. If presence detection is important to you as a ST User, I would recommend reverting to 10.3.3 while you still can. Apple will most likely stop signing 10.3.3 very soon.

1 Like

Please do make sure you contact support and utilize reviews. As Terry pointed out, community members can be less likely to contact support.

Also, I know you all want attention and a speedy resolution but I see new replies without @mentions.

3 Likes

Not sure why bad reviews on the AppStore would be more helpful than detailed reports here on the forum or support tickets but since you ask for them…

1 Like

I have submitted a support case and a negative App Store review. Hope it helps.

1 Like

Ditto…

1 Like

Just opened a ticket myself. The person who’s had like 0 issues up until about 4 weeks ago when I decided to upgrade to a v2 hub. Since then its been down hill…new hub…new shard…then new app update…then ios update. All crap. And sucks that ST refuses to take us seriously until we open a ticket and/or leave an app review in the app store.

Seeing this as well. Mainly piling on here to watch the thread - I sure hope this gets fixed soon!

ST must have a very weird bug triage system if it needs pointless emails to support wasting both party’s time for what is quite clearly a new confirmed bug that breaks a critical part of the system. I’d rather support deal with more nuanced bugs. Surely you’re not waiting for x hundred reports before you make it a priority?

Sometimes just one report of a critical bug is enough to get it fixed. What we used to call an ‘A class’ bug when I was a games dev for one of the major games platforms in-house studios…

5 Likes

If anyone uses webCoRE and wants access to the beta presence sensor embedded in it, I can send invitations to TestFlight. Will need a PM with name and email and will send an invite. It’s being tested by over 30 people so far and it is stable though requires a secondary blank webCoRE install (install webCoRE again) because deleting the device it creates at setup time will automatically delete the instance along with all of that instance’s pistons (ST is working to fix this). Also supports up to ten places (only one drives the presence attribute).

5 Likes

It’s interesting that we’re being told this by several ST staff members that participate on this forum for various issues now. For example, Wink announces support for a ton of new devices - #13 by vlad

While they have always encouraged opening tickets with support, letting us know that negative reviews in the apple and google app stores may also help with getting issues resolved seems to be a newer thing.

It implies to me that the priorities of mid or upper level management may not be aligned that well with those of ST staffers and users.

Maybe I’m way off. Just a thought.