Resolved - We identified and resolved the root cause of the problem which may have prevented the SmartThings App from loading, caused issues with device control, and automation executions.
Jan 21, 14:05 EST
Investigating - Something is not quite right. We’re looking into it and will provide additional details as they become available.
Jan 21, 13:16 EST
imagine that…and 7 days after the 14th total outage things are STILL not back to normal as I have 2 automations which refuse to work correctly even after deleting and rebuilding them. Becoming quite ridiculous. Had never even contemplated moving to Hubitat before this fiasco but am now and if I do I’ll also leave the Samsung ecosystem completely and work toward LG TVs (far superior to Samsung), LG appliances, Pixel phones, and Hubitat smarthome, which is what I should have done from the start.
I noticed something interesting that I did as a test. I moved one of my Automations controlling lights back to Smart Lighting, and what a difference for the better. In fact, it worked compared to a similar Automation that failed. I’m sure it’s related to the backend rules API work they’re doing, but my lighting automations work better now with SL than they have been with Automations. In fact, I should be paying attention in a meeting right now but instead I’m moving more of my Automations back to Smart Lighting.
Not sure you’re going to get many responses in this thread, which is about today’s outage. I know you already posted once in the thread about the nest integration, but I would try there again. from one user:
The main thing is that nothing is exposed to groovy smart apps, so it won’t work with webcore or action tiles or sharptools. But it looks like you can create some automations in the new V3 app.