I am still using the classic app. A couple months ago I got a prompt or notification in the classic app to upgrade to the new one. I created a Samsung account and downloaded the new app. However, nothing came over. So I am still using the classic app, but I am curious if that was my “prompt” to upgrade.
Do you mean the Samsung Connect app shows none of your devices or do you see your devices and none of them work properly?
Of course, it is recommended that you continue using the Classic app.
I am confused by reading your issue, did you migrate to a new Samsung account or did you just create a new Samsung account?
1 Like
Thanks for following up.
I was prompted in the Classic SmartThings app to move to the new SmartThings app. So I followed the prompts, including creating a Samsung Account. But when I go into the new SmartThings app none of my devices are listed. It is empty.
Everything is still working in the Classic app.
Strange, you can login to IDE at https://account.smartthings.com and see how many home locations you might have.
In the Samsung Connect app, click on the devices tab, at the very top, center is a pull-down menu. See if there are multiple home locations. You should be able to switch
So when I log into IDE, I see two “Home” - when I view in the App, I only see one. And I have nothing.
Weird thing, it seems I have my Smarttings login for IDE, and now my Samsung account login. What a mess.
Did yo use the same password for both your SmartThings and sumsung account?
I don’t think so. I use a password manager and generate random passwords. But I used my email for username on both.
Of course this all gets confusing since you have Smartthings Hub login, and a support login, and now a Samsung. They have made a mess of this.
Probably time for you to contact ST support to resolve this.
https://support.smartthings.com
I am about done with Smartthings. It is clunky, not user friendly at all. It shouldn’t be this confusing. I shouldn’t have all these log ins. Support, Community, Smarthings Hub, Samsung.
That’s exactly THE REASON that Samsung is converting everyone to a “Samsung Login” … This is Account / Login Federation.
Samsung wants everyone to use their single “Samsung Login” for SmartThings, SmartThings NEW Developer Website, Samsung SmartThings NEW Community Website, phone login, TV login, fridge login … you get the point.
I just find it ironic that you’re complaining about multiple logins when this is exactly what Samsung is actively in the process of resolving.
Personally, I hate consolidated logins! This is a huge security risk. I absolutely don’t want my Community Forum login to be the same ID and Password as the system that manages my home.
Fair point. I guess when it is all done, it will be good. Right now, it is just confusion. I don’t think I can log into smartthings hub using my smartthings login because I used same email address for samsung account, so now it wants my samsung password when I enter my email.
1 Like
I just did.
Weird that I have two “Home” locations when I log into the IDE but in the new Smartthing app, I only have one. I tried to delete one of them (the blank one) and the site would not let me.
try this to delete a Home Location that has nothing in it:
- Login to IDE at https://account.smartthings.com
- Goto Locations
- If you have multiple Locations, select the invalid one
- Make sure there is no Hub associated to it
- Scroll to the right and click Edit
- If the Default Location shows “true” (will be read only)
- If it is “true”, go back to Locations and select your primary (Real) location and set the default location to “true”
- Now you can edit/delete the additional Home location as it will automatically be set to “false”.
This may or may not help you resolve the issue.
2 Likes
This really is a FAQ! 
️
So I’m now using both apps. I think both the classic and new apps have their good and bad sides. Lately I’ve been reverting some of my custom DH for Fibaro motion sensors so they actually work with the new app but that leads me to my questions:
-
Does the ST team have a list of custom Smart Apps and DHs to that they will migrate or will that be up to each developer to migrate? Knowing this will either get the community to develop the necessary updates to support the new rules engine.
-
Why are routines being phased out? I like the new IFTTT style rules interface but the fact that we cannot control locks with mobile presence is an absolute deal breaker and is the #1 reason I haven’t switched to the new app completely. I understand there are likely legal risks involved but we as users have to assume some risk by using such rules. I’m assuming I can transition my routines to the new rules engine but can’t seem to figure out “when things quiet down” and “when things start happening”. I use these events for key automation triggers.
-
The new app doesn’t work in Landscape mode, I use an 8-inch tablet as a home controller and it’s mounted on the wall in landscape mode so the new app can’t be used there. What is the roadmap for the app and will it support landscape before they sunset the Classic app?
I’ve looked for answers to these questions in other areas of the community but haven’t found the answers. But for those of us who have had 3+ years on this platform, knowing a bit more of the future will help us better plan for changes. For instance, I just got the new Smartthings WiFi and I love the system but I haven’t transitioned to the integrated Smart Hub, still relying on my standalone V2 Hub because I don’t want to migrate my 75+ things over manually to the new Hub and don’t want to lose by any capability like locks.
If the answers are elsewhere in the community, thanks for pointing me in the right direction and if they don’t exist, I hope this helps continue the conversation.
1 Like
I presume you’re using ActionTiles which is optimized for “home view & control” of SmartThings households?
It took years for SmartThings to add landscape & tablet compatibility to the Classic App. Unfortunately, the new App is entirely based on a different foundation - the Samsung Connect App, and so various hard won Classic features have not been inherited automatically. There’s no guessing how long it might take.