Get ready to make the switch!

Isn’t the ability to continually innovate and integrate new devices and features what makes ST so awesome? Unfortunately that “standard” models from ST are very basic, the custom controls is the juice.
What happened to “upcoming” ability of the new app to provide custom controls?


Does this also mean that WebCoRE will not be able to have ‘view-only’ access to STHM states please (e.g. If STHM is Away then do X)?

1 Like

Custom automations in the new app allow you to use multiple conditions but there are some limitations on them to make sure users don’t inadvertently create infinite loops. The specific case you’re referring to can be accomplished using a scene to control the location mode and automation to activate the scene.

“IF location.mode is home and Gene arrives, THEN start scene ‘guest’”
Scene ‘guest’ = change location.mode to Guest

1 Like

There’s absolutely ZERO way NewApp is ready for my move. I’ve been trying it.

Better than it used to be - but nowhere close.


Going Away. I have already transitioned to Hubitat. I keep my SmartThings account and integration to support the TP-Link Integration (largely replaced by the new official integration) and the Samsung Multi-room Speaker integration (never will be available). When I get the banner, I will announce sunset on the integrations, unregister and unplug the SmartThings Hub, delete the apps from my phone. The GitHub repositories will remain with a clear not maintained statement.

For those saying the Hubitat app is not as good. Yes, out of the box; however, it is far better once you create your phone, tablet, or pc dashboards. It just takes some learning and some easy development (that can be fun).

My thanks to this community. This user community and the SmartThings staff have continually helped, encouraged, and been kind and I thank all. I hope both SmartThings and the community members the best going forward. Remember, he who dies with the most toys wins.

Dave Gutheinz


Is there an approved DTH for a virtual device that is both a switch and a sensor? This is a popular method for integration with Alexa routines (not SmartThings routines). So that would be great to have an official version. :sunglasses:


Blake I suggest you guys reach out and find out WHY we’ve been using classic rathern than a blanket - get ready to migrate.

Personally I need two things before I’ll even consider it close to ‘ready’

  1. WebCore can see cloud connected devices using the new APIs etc.
  2. Your new Nexia integration properly working (right now it doesn’t show my thermostat after connecting)

Also, there is a SharpTools option for Hubitat which is pretty cool and I personally think is somewhat easier to setup. :sunglasses:


It seems that Samsung Connect doesn’t desire my services as a user

1 Like

I’ve made the switch. This was my third attempt. Things aren’t fully working yet and I’m trying to find sustainable solutions for some old behaviors:

  • I had a bunch of alerts (just notifications) when certain doors or windows were opened for more than 5 minutes or if there was movement in the kids after 9pm. I can replicate this behaviors with automation, but I’ll have to have one per sensor in order to distinguish the notifications.
  • Changing the home mode based on a number of different conditions currently require multiple automations. Also, a bug that if you had the mode as a condition you can’t add it as an action. Doing it the other way around works.
  • No way to see if users are at home or not. Makes it hard to figure out why certain actions don’t run when people leave/arrive.
  • Why was the delay on SMH triggering the alarm removed? That by itself was my singular motivation to move to the new app.
  • Notifiy to arm/disarm on arrival/leave is kind of useless. My kids aren’t going to be able to distinguish that notification from the other 100 they get while getting back from school and I’m not going to spend a minute loading the app to disarm it in the car before arriving home.

Things are a lot better than before, I’m trying to be optimistic. If you’re phasing out smartapps, introduce JavaScript based advanced automations (with a functioning sharing/community feature) to cover the gap that’s so obviously there…


1 Like

Will Routines in the Classic be transitioned into Scenes and Automations using the “transition tool”?
Yes. The migration tool will break routines into component scenes and automations.

Oh and what about behaviors? Could you please give us an update, if there have been any changes?
The goal of limits and guardrails is basically to make sure that we don’t get a device or smartapp spamming the platform with events and degrading stability and performance. We try to set what look like reasonable limit levels based on the data we see on our end, but if you run into issue, please surface them in the community and we can look into changing things. We’re 100% behind supporting the community and our power users as much as we possibly can.


The end is near…


Hate to pile on here @blake.arnold, but this isn’t true. The automation creator checks within the scene for device and mode conflicts too :frowning:


Currently I’m still using the classic app and SHM to record video clips with my Arlo cameras. Will this feature be added to the new app?

As of right now I can only turn my cameras on and off with the new app. @blake.arnold


Someone said this started working last week. Arlo was pick able from the record option in STHM.


Tagging @TheSmartestHouse @Eric_Inovelli @joshua_lyon @625alex


We feel the same way too. Looking at the metadata, most (not all) of the custom DTHs out there would get the same functionality from an ST approved DTH. That said, we know that custom DTHs are the secret sauce on the platform for more advanced users. With the architecture of the new app, UI metadata is required to get custom capabilities to render properly and frankly the current UI metadata architecture is a real pain to work with right now. We’ve been redeveloping that for a long term solution and some interim tools to help get users some more functionality in the meantime. We’ll make sure it’s fully there and documented before we consider deprecating classic.


I’m curious if there support for the daikin dth that allows daikin ductless units to be controlled in the new app?

luckily it sounds like there is months of time before Classic is totally deprecated.

  1. The Rule API can see cloud devices, so hopefully the Rules API version of webcore comes out sooner than later
  2. if this is a cloud integration, then it’s up to Nexia to support. Although it sounds like ST has had some issues in early January with other cloud integration too (Kasa and Merros)

Thanks Nathan - we did that outreach last year and plan to continue to listen to the community as we go through the transition. You’ll notice there’s no firm end date on this yet because we know there will be some additional needs uncovered as we hear more from the community. I’ve added your specific concerns to our list for discussion with the team.