Nope. It’s a cloud-based architecture still. If your Internet connection is down, The smartthings mobile app cannot talk to your hub even if they are both on your same LAN and that is still up.
This is in sharp contrast to, say, Staples connect, where the tablet control app can connect locally.
If your cloud connection is down, the only things that run are things that are already in the firmware of your hub. And right now that’s not much.
Smartthings has already suggested that you preprogram a button controller device like the Aeon Minimote to be able to change modes manually if you lose cloud connection since your phone app will not work.
I am quadriparetic with limited hand control, so this is actually a big issue for me, as I cannot physically use a minimote. Not having tablet access is a big deal for me. But as of now, we don’t have it. They’re working their way backwards from cloud architecture.
You might want to talk to @pstuart He knows a great deal about how a server can and cannot interact with the ST hub Beyond the official position.
But if you’re thinking that the smart things hub, either generation, is the home automation server like Homeseer that you can get access to and and run your own programs on locally, it’s just not. It operates pretty much like a web service. No TCP. No UDP except the stuff that Patrick has been able to get working. No way, for example, to interface with a Lutron bridge even though that has an open local API.
But again, some of the other deep coders can answer your questions much better.