Hey all - as you can see from above, we’re starting to ask SmartThings Classic users to migrate from the Classic app to the new SmartThings app. Here’s a little more detail on how switching from Classic to the new app will impact you.
First off, we want our most dedicated users on the community to know three key things:
- There will be plenty of time to make this transition.
- We will be timely and transparent about any changes and how they impact you.
- We are listening! The community helped us plan for this transition and prioritize features in the new app - if you have questions or suggestions, we would like to hear them - please comment below.
Community users told us transparency and clear communication was important during app migration. This post is meant to help explain why app migration is happening and how it impacts you.
Why is SmartThings asking me to use the new app?
Put simply, the new app lets us give you a better experience. It is more stable, more flexible in handling a variety of device types and provides improved security and privacy. Overall, it provides a much better platform to build on as we add new features and functionality.
It also allows us to put all our resources into developing new features and debugging a single app. We maintain largely separate systems to run Classic and the new app. Consolidating to a single app lets us focus on making SmartThings even more awesome for our users.
When should I migrate?
We will let you know when it’s time through a banner at the top of your Classic app - not all users will migrate at the same time. Because development and testing of a few features is ongoing, we’re rolling out to some users later than others so that they have a great experience when they start using the new app. The complexity and features used in your setup will determine when you are asked to migrate, but rest assured that we will still make sure everyone has plenty of time to complete migration.
Please see the App Migration FAQ page for the most up-to-date info on all changes - we will update this page with new information on features and troubleshooting suggestions as it becomes available.
Overall, a few major changes are happening:
Smart Home Monitor - Smart Home Monitor is changing from a Groovy SmartApp to an EndPoint app.
Lock Code Management - Lock Code Management is changing to a new SmartApp called Smart Lock Guest Access which is currently available in the US and will be expanded to other countries in the future.
Routines - Routines will become Scenes and Automations in the new app. The triggers for a Routine will be changed to Automations and the actions for the Routine will become a Scene.
Smart Home Monitor and Lock Code Management settings will be migrated to their new versions and Routines will be broken up into Scenes and Automations automatically when you begin app migration.
There are some features that we’ve had to change because of privacy, regulatory, or functional reasons. All of these are detailed in the FAQ page, but here are a few big ones to be aware of:
Community SmartApps - Installing community SmartApps used to be done through a combination of the IDE and the Classic app. Going forward, the steps completed in the Classic app can be done in the new SmartThings app.
Self-published DTHs - The new app still supports self-published DTHs, but we found that over 90% of the devices on the SmartThings platform can be run by less than 100 ST Approved DTHs and most would actually work better. We’ve already rebuilt the most popular DTHs, tested them in the new app, and made them execute locally where possible. We recommend you transition any self-published DTHs to ST Approved DTHs to get the best experience in the new app.
Custom Capabilities - Custom attributes are changing to custom capabilities in the new app. This means that if a device hasn’t had custom capabilities UI metadata created to match its attributes, they won’t display properly in the new app. We’ve already done this for the most popular devices (see info above on ST approved DTHs) and are finishing development on a way for you to create your own custom capabilities. Additional user front-ends that will help with this are under development and should be ready in the coming months, so we’d recommend waiting until that is released before beginning any work on custom capabilites yourself.
Smart Home Monitor in WebCore - Because of security and privacy concerns, we can’t support SHM state changes in webCORE pistons moving forward. We know this is important functionality though, so we’ve provided a workaround. Use a custom automation in the new app to change SHM state by using presence detection, location mode, or a virtual switch as a trigger and then reference that trigger in your webCORE piston to accomplish the same thing.
Where do I get more information?
The App Migration FAQ is the best place for the most up to date information on app migration. We will continue to update this page as we receive feedback from users and make changes to the app.
How do I get help?
Our support teams are ready to help with app migration if you run into any issues. We encourage you to look at the FAQ page first as most issues should be easily solved with that information, but if you’re still having trouble, you can get support through links in either app or by calling our customer support team at 1-800-SAMSUNG.
What happens if I don’t migrate?
You will need to migrate as the Classic app will eventually be deprecated. We will provide an exact date for that in the coming months to give you plenty of advance notice, but if you do not eventually migrate before that date, SmartThings Classic will no longer work and you may lose some of your settings or migration may be more difficult.
We will continue to post reminders and more information as migration gets going. Please watch this thread and the FAQ page for more information.