Yup. My HEM does, as well as my last 2 old in wall microcontrollers.
How does this impact the ADT smartthings hub?
Iâm only still using the classic app for a few things:
- Triggering routines from WebCore and ActionTiles. All of my classic app routines simply trigger a scene. I know there are ways to kludge this together in the new app, but I want a nice easy official way to do this.
- Presence. I need to be able to actually see the status of my presence sensors in the app, without relying on 3rd parties
- App stability. The new app crashes a lot, especially when touching things that were carried over from the classic app. My scenes created in the classic app have me a lot of trouble in the new app until I managed to get them saved in the new app. After that the crashes reduced. Additionally, I canât get into the âGoogleâ connected service in the new app, it just throws errors and hangs
- A handful of devices for which I have custom device handlers and/or smartapps
3 Likes
Not nearly enough to put a dent in the 50+ millions who have installed the new app. They can kill the Classic app today and wouldnât hurt Samsung a bit.
4 Likes
For what itâs worth, I switched over to the new App last November. The only time Iâve opened the Classic app since then was to verify that both apps agreed that a particular device was offline.
But Iâve kept my deployment as simple as I can.
-
Never connected my Nest outdoor cams
-
Iâve resisted adding my Chamberlain garage openers
-
Honeywell thermostats cloud to cloud is connected but I donât control them via ST
-
Harmony hubs connected, never used
-
Sonos devices same, connected but not doing anything
-
Iâve avoided dipping into the WebCoRE pool.
-
I change all my smart switches (mostly Zooz) to the stock DTH after initial setup.
-
All automations are in Smart Lighting and scenes
-
I think the current crop of smart door locks and door/window sensors are unspeakably ugly. Luckily I live in a place that I donât feel the need of locking down my house
On a daily basis we almost exclusively use Alexa to adjust individual lights or trigger scenes. Iâve got a couple of Alexa routines as well.
I donât find it any more difficult to open a separate app for thermostats, garage openers, Sonos, etc than it would be to open a unified app and then hunt down the specific devices in a long and ever growing list.
Yes! We need to be able to see which presence sensors are home, like the classic app.
2 Likes
This is a biggie. I often look at the presence sensors to see when I left work and returned to keep track of my time. Easily open the app to see if a family member is home and/or when they left.
Quickly view the last week activityâŚ
Finally, having the ability to get a quick snapshot of whoâs at home and whoâs not is often used by all family members.
P.S. Potty Time comes on if back door hasnât been opened after 5 hours.
4 Likes
This is the migration that the announcement is describing. Sometime soon, youâll get a banner in the Classic app giving you the opportunity to migrate. Once you do that, your routines will be migrated to Automations and Scenes.
Iâve already half made the switch.
Iâve replaced the routines with rules made using automations and scenes in the new app.
Everything seems to be working fine with the new app, apart from the video clips, which are no longer generated from my Samsung SmartCams in the event of an intrusion.
I understand that this is because Samsung withdrew support for their own cameras.
(Iâll remember to avoid Samsung cameras in the future!)
Although Iâve removed my phone presence detection and deleted all the routines, my wifeâs presence sensor is still recognised and working in the classic app, although the arrivals and departures now only affect the new app.
Can anyone advise me as to how to delete the classic app?
Is it safe to just uninstall and forget it, or should I delete the account too?
No, no, no! Just delete the app. Or leave it for a while.
To expand a bit: all the info about your SmartThings system is stored in the cloud using your account. Deleting the primary account will wipe all that out leaving your hub as a nice paperweight.
The one possible account you could delete would be the case where your spouse or children have the Classic App, are added as âMembersâ, and are using SmartThings accounts.
If the Members are using Samsung accounts and have or will have the new App, you should keep the accounts.
2 Likes
Hi @blake.arnold - Iâve just got a couple of questions:
-
Please can you confirm if the above is still the case?
-
When it comes to Webcore, whilst you have said we wonât be able to change the STHM state from within Webcore anymore, can you confirm if Webcore will still be able to see the STHM state so rules can be based on its status? I.e. âIf STHM state is AWAYâ then âturn onâŚâ etc. etc?
-
Do we need to be on the latest version of the Classic app before we switch over? I rolled back to 2.17.0 (build 448328) after the last update broke everything - I hear this has been fixed, but things like icons etc are still not working so Iâm refraining from upgrading for nowâŚ
-
I take it both of my Samsung Smart Cameras will not work in the new app? I have the Smartcam pro and the 6410 versions in my home linked to SHM.
Thanks for letting me know.
1 Like
Is there written documentation somewhere on the correct way to remove presence sensing from the Classic App so it can be set up in the new App?
I followed advice to delete the Device several months ago. The Device keeps reappearing and I think that deleting it turns off presence sensing in the new App.
I found a Smart App in my list of Installed Smart Apps in the IDE and removed that. That seemed to clear up some remains of the Classic App presence sensing and has not affected the new App.
@chris1256 I just ordered a smartthings camera. It says it works with smartthings, should.i cancel the order?
STHM states (armed/away, armed/stay and unarmed) are completely separate from the location modes (home, night, away and any custom mode you set up).
WebCoRE can not see nor set/manage STHM state but can see/manage Location modes in the new app.
Unless they make changes at some point in the future.
Eidt @JDRoberts corrected me on the right name to use
3 Likes
Now called âlocation.modesâ unless theyâve changed the name again. 
In the new âhub optionalâ design you no longer need to have a hub to have a location.
3 Likes
- SHM will be automatically deleted from Classic when migrating. So you donât need to manually delete anything.
- Webcore can not see STHM security states. Iâm using a virtual switch in the new app to do this.
1 Like
Probably a good idea to update if you choose. But they did start embedding the migration tools in that version I believe.
Hi Dominic, I would certainly check with Samsung if theyâre supported.
My Samsung Smartcams say âworks with smartthingsâ on the box, but they donât because Samsung decided to withdraw support for them.
Mine are a few years old now though.
I think the newer ones might be okay, but you certainly canât trust what Samsung print on the boxes.
1 Like
Can you have the team look at this issue? It seems there is a problem with this app created by @arnb when saving/creating child devices. It works fine in classic but not in the new app.
1 Like
I purchased the new one & if anything I will return it. Thanks.