As I understand things, In the new ST ecosystem apps are developed in more standard languages like Node.js and publishing to others is not so easy (may not be supported at all). So, as a mobile app I do think it is reasonable. Whether their new ecosystem for supporting DIY enthusiasts like us is reasonable is a whole different matter. And of course I don’t think it is.
That’s the intention, but the new ecosystem doesn’t even have any way to work with the zigbee and zwave devices yet, so it’s all pretty theoretical. I think it has to be judged on what it does today.
There’s a topic in the forum where people have put things that they like about the V3 app.
There’s been a lot of discussion about the negatives of the new app, so I thought I’d start one about the positives. Who knows, maybe there is some SmartThings dev out there that is having a bad day and will read this and feel better
Feel free to add your feedback and let’s keep this thread positive!
the UI. Obviously this is opinion, but I like the design of the new app better.
Smart Home Monitor now has an entry delay. As I understand it, SHM in the new app is designed from scratch using the new REST API and they added an entry delay. You can pick 0, 15, 30, 45 or 60 seconds. You can also dismiss alarms from the card on the dashboard.
The custom rule builder. They brought over some of the smart apps from the Classic marketplace, but th…
Meanwhile and I know I am as guilty as anyone on this account, let’s try to keep this thread on topic for discussions of what to call the two currently available apps.
If you want to discuss features of either of the apps, use the following thread instead:
"SmartThings Classic" (V2 app) vs "SmartThings (Samsung Connect)" (V3 app)