SmartThings Community

SPECIFIC differences between "SmartThings Classic" (the V2 app) and “SmartThings (Samsung Connect)” (the V3 app)

In your screenshots, yes. But the knowledgebase article says that the two apps have different starting default values.

How do I disable insecure rejoin?
In the SmartThings app, the insecure rejoin is disabled by default through the Secure Mode setting…
In the SmartThings Classic app, insecure rejoin is enabled by default.

But that’s just the initial settings.


they have different starting values because they are labelled differently. insecure in the classic app but Secure in the STSC but overall you end up with the same setting of either being insecure or secure in both apps. You can’t be insecure in one app without being insecure in the other app.

so your statement is incorrect --> Insecure rejoin for zigbee devices is enabled by default for the classic app and disabled by default for STSC.

It’s not my statement. It’s from the official support knowledgebase article. I didn’t paraphrase it, that’s exactly what it says. It’s not using two different terms in those statements. But I don’t know, maybe the author of the article wrote it incorrectly.

then this support knowledgebase is incorrect, it should read in the SmartThings app, Secure mode is disabled by default. because if I change the settings in one app, it changes in the other app :slight_smile:

STSC - secure mode = off and ST Classic - insecure rejoin = on
STSC - secure mode = on and ST Classic - insecure rejoin = off

The new app is much pickier about what your location is. There are many features which will not be available unless the location for your account is in the US or the UK or Canada. ( even adding a hub will not be available unless you are in one of those three countries – – that’s now considered a “feature.”)

The following threads discusses how to set the account location in the new app if you aren’t sure. Note that the process is different than setting your Geopresence location for your phone.

As of this writing, the iOS version of STSC needs to have the Geopresence used for the phone location refreshed from time to time. This seems like it is probably a bug, but it has now persisted through several updates to the app, so maybe not. With the classic app, it is the android version which is more likely to need location refreshed.

As of this writing, it appears the STSC does not recognize hue light strips attached to a hue bridge. However, they will be discovered automatically if you are using the classic app.

1 Like

Is everybody now supposed to be using the SmartThings (Samsung Connect) app? I’ve often thought this.

I’ve not received an email saying that I should (UK). So I’m still using the SmartThings Classic app.

Seems a long time to announce that they were mothballing the Classic app, and to not be told to move over to the new version.

Migration questions should be asked in the other thread.

This thread is only for a list of specific differences between the two apps. Please read post #1 in this thread if you’re not sure what goes here. Thanks. :sunglasses:

The new app version of Smart Locks (called Smart Lock Guest Access) is very similar to the classic version, but is actually two separate apps. The Classic version you can share a created code by SMS. The new app version you can share with any communication method.


@JDRoberts @prjct92eh2 @jkp @tgauchat , add this to any of the FAQ’s about the differences in the ST apps…

Specifically, if you have “x” number of devices (maybe? who knows how many the new app supports), and you have sync issues, it looks like the only option support is making available is for the customer to delete everything, start over, and hope that it fixes the problem.

Responding in the other thread so as to keep this one on topic.

1 Like

Absolutely unacceptable answer.

Though it’s no worse than if you bought a new Hub and had to manually migrate, due to the lack of a migration tool. Which could absolutely be necessary, if, it would be a real shame if, your current Hub were to have some sort of, ummm, “accident”, you see, hmmm? :imp:

1 Like

From @jkp in another thread:

If you use SHM in the Classic app, you can use smart plugs. It does not offer that option in SHM in STSC. Be sure to contact ST support to request it as a future feature.

1 Like

Interesting User Experience decision.

SmartThings has been “tagging” various DH with Capability “Light” (in addition to “Switch”) so that SmartApps like SHM and Alex/GA can tell the difference.

Wouldn’t want to switch on some dangerous appliance like a coffee maker as an SHM alert indicator, right?

1 Like

From a newbie perspective an awesome thread to read, been here just about a month and impressed


As of this writing, presence works quite differently in the two apps.

To quote @jkp

It depends on which app the phone sensor was created. If you created the phone presence sensor in the Classic app, then you can use it with webcore. If you created the phone location sensor using STSC, then you are out of luck as webCoRE does not work with that feature from STSC.

The new app also has a bug at least in iOS where it will repeatedly create new copies of a phone presence sensor, making it pretty much unusable.

And as already mentioned above, in the new app, you cannot use presence to change security mode or to unlock a lock. You can do both in the Classic app.


I believe This is the result of the bug where your phone location is disabled. When you enable it again, it creates the extra sensor(s).


This is exactly my problem. How do I get around this when I have four people, each with iPhones.

The V3 app now has the ability to group lights together. It’s only partial, you can’t use the groups in very many automations yet, But at least you can toggle them in the app.

A long long time ago, back in 2014, the V1 app had this ability.

The V2 app never had it, and now never will.

But in either app you can create a virtual master light and then have the others mirror that. So for the V2 app, you have to use that method or one of the other unofficial custom options.