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? 
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
Jools
2 Likes
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.
3 Likes
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).
3 Likes
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.
Methods to use with the V2 classic app:
https://thingsthataresmart.wiki/index.php?title=How_to_Group_Lights_Together
1 Like
Hi, I am a new member to the SmartThings world, and brought myself a SmartThings Hub v3 from the USA back to Australia. I already had three LIFX WiFi colour lights and an August Door Lock Pro + Connect (American import).
As a trial I bought a NUE Zigbee 3.0 Smart 3 Gang Switch (for lights) from eBay. After downloading the device handler from the vendors website and importing that into the IDE, I am able to operate the three lights (behind the switches) with the Classic App. It shows up as a single “Thing”, but once you select it, you get the three sub-switch options.
Unfortunately on the SmartThings Connect (new) App, the switch shows up as a single “Device”, and when selecting it, it present an On/Off switch option, that doesn’t do anything. It certainly doesn’t present the three switches available on the device!?
The same problem exists when integrating the SmartThings (Samsung) account in Google Home. It imports the “Device”, but only presents a single non-working On/Off option.
Is this the limitation of the new SmartThings Connect App, or can we get it to work by changing something in the handler through the IDE?
Thx, Niels
Good question, but offtopic for this thread, which is just supposed to be a list of specific differences. 
Please repost your question as a new thread in the following section:
You can now automate unlocking a lock in The V3 app via scenes and the custom automation creator.
3 Likes
Wow, that’s great! 
Can you trigger it from Geopresence?
2 Likes
Can you change security.mode based on Geopresence?
Nope 
…
1 Like
I wish they would fix the things they broke, like playing Sonos, before implementing long overdue features 
2 Likes
Yeah I know, and it stinks. Security mode changes based on geopresence is something we really need. I’m trying to move to the new app, but I still find that some of my custom SHM rules in Classic can’t be done in the new app, and I really don’t want to use webcore. If you have any ideas on how I can accomplish these, I’d be super happy:
-
Repeat notifications setting (eg. once every 60 minutes vs every change in state).
-
Temperature thresholds not low/high enough (32-104 hard coded in the new app). Why ST hard coded limits is dumb because I want to know if my freezer is at 20 degrees (vs 0) because something has failed, not 32 when it’s almost too late to save any food.
-
Notifications don’t specify which device if the automation uses multiple devices for conditions to be met. I miss this badly because if I have a custom automation to monitor when a window opens, I’d sure like to know which window was opened in the notification vs having to open the app and then navigate to the Room and try and find it. I can certainly have a custom automation per device, but that’s dumb.
-
No “countdown timer” or wait time before sending notifications (eg. door open for 45 minutes). I may not need to know when a door/window was opened, but I would like to know if it’s been open too long (like a freezer or fridge door).
Once that functionality makes it from the Classic app to the new app, I can see myself using the new app more often, kind of. I still have scenes in the new app that won’t fire, but the matching Routine in Classic works every time; and now SHM is broke 
Don’t get me wrong, there’s been really great progress on the new app, but I really wish that ST would prioritize carrying over useful functionality from Classic to the new app if they want those legacy app uses to move over quicker.
3 Likes
For the most part, you can’t use webcore with STHM in the new app even if you wanted to.
4 Likes
I spoke too soon. Can’t create any new custom automations now. Looks like I’ve fell victim to the same issue I’ve seen in the community regarding the error “A network or server error occurred. Try again later.” when creating a custom automation. Oh well, at least I’ve tried. Looks like I’ll have to move things back until ST gets their act together on the new app.
UPDATE: Here’s a good one for you guys. So last night I spent a good chuck of time moving scenes from the new app back to Routines in Classic, as well as all custom automations back to custom rules in SHM Classic. SO I was very surprised this morning to get push notifications from the new app about automations and scenes executing (multiple times in fact). Funny thing is that I have NO scenes or automations in the new app to trigger this stuff but somehow they still executed? This new app continues to surprise and disappoint me. See for yourself, and note that I do not have a Goodbye! automation in the new app:
Gonna need some help with this one @Brad_ST.
Oh yeah, I’ve stopped receiving SMS/text messages too. (yes I’m in the US and yes I’ve opted in already) Great…
1 Like