SmartThings Community

SPECIFIC differences between "SmartThings (Samsung Connect)" and "SmartThings Classic"

project_getstarted
#64

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

(Stephen Hill) #65

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.

0 Likes

#66

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:

0 Likes

(Jimmy) #67

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.

2 Likes

#68

@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.

0 Likes

#69

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

1 Like

(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy) #70

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

#71

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

(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy) #72

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

(Julian ) #73

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

2 Likes

#74

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.

1 Like

(jkp) #75

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).

1 Like