+1 on this.
Everything seems fine again for me…
+1 on this.
I can login to App but I don’t see hub and any of my things. The ST app is empty.
I have never been subjected to a 5 day outage to this extent , if I did this at work … I wouldn’t have a job anymore. But everything appears to be up and running again for the moment , I am lucky as I did look at the new app. My smartthings devices were there , but everything else wasn’t but went back to classic and everything was ok.
Working here as well. Fingers crossed.
So it sounds like this is pretty unusual, and has happened (maybe coincidentally, likely not) when they’ve been releasing a new app? So the best case scenario might be just a botched app release / migration?
I’d be pretty happy if that were the case. It’s poor, but better than it being an infrastructure or operational issue.
It is really frustrating not being able to log in to the app. As I said before at least I can still control it via Alexa and the likes. so it still works. just any alerts fail. and manual control or checks is frustrating. I have no idea if my house auto armed when out.
can @slagle or someone comment? whats going on?
Now they have updated the status page to say issues fixed. Anymore know what the problem was?
The cause of the issues in EU has to do with the rollout of the new SmartThings application and the consolidation of Samsung’s IoT services into the SmartThings platform. Specifically what happened was this - we are performing a slow rollout of the application to all existing users (not just ST users but to users in the rest of the Samsung ecosystem). As more products/users are using this app - so did the load we generate on our Authentication provider, Samsung Account. While SA was able to scale fine in North America and Asia, there were difficulties in the EU region. When we began to notice a slowdown we stopped the rollout completely though at that point new users were still beginning to use the new app and the load continued to slowly increase. This eventually caused latency issues, which eventually became timeouts and flat out failures. Over the period of the outage, ST and the Samsung Account team were working closely together to try various mitigations. While there are still capacity issues in EU for Samsung Account, our team was able to implement very heavy caching on the backend to bring it down to functional levels, at this time the caching is still in place and the SA team is working on increasing capacity in EU. Also, because the new app is still in its early days and there is a ton of development work ongoing across many teams to bring everything together, the presence of bugs and inefficiencies in regards to how it communicates with the backend is a factor, these are also being looked at by the mobile teams too.
I do just want to say… in the recent months ST has become much more of a central player at Samsung - which has forced us to scale quickly as we support new users with different usage patterns. While growth is good, unfortunately this type of approach has resulted in a loss of reliability. Fortunately, the recent issues have helped highlight the need to put reliability back in the forefront - for example the priorities of my development team have completely switched towards reliability and making the new app more usable for our current customers instead of focusing on new features. I am hopeful this will pay off - as we had a similar exercise a couple of years ago and we were able to significantly improve the stability of the platform. I just wish that we didn’t have to go through months of incidents to get here.
Will Smartthings be suitable for medium to large scale projects?
App not loading
Offline..... is anyone offline (April 2, 2018)
Thank you for this. Nothing is more important than communication - so this is welcome.
Thank you for the reply and for the explanation as to what the issue was.
Really appreciate the information, it gives us something to cling too when we do have issues. At least we know better things are coming from all the issues and that everything is moving forward.
Yea - totally understand. I’ll try and be more active in providing more explanations in the future.
I get this error when trying to access the Smart Home Monitor on the Classic app on my Android phone. My wife uses an IOS iPhone and has the Classic version on her phone and it works find. I have even tried logging on as her on my phone and it still does not work.