Question

Gonna start sliding over to the the new app. what will I be lacking that I had in the classic? Looks like the dashboard is gone?  

Answer 1

I keep hearing lots of things are missing. But to be fair, it's becoming fewer and fewer

Answer 2

Smart locks still only works in the old app. It shows in the new app but if I try to add a code it says I don't have a lock

Comments

@detention same issue here

---

@gerdy that's the one that will not let me enter new codes

---

@gerdy old app will let me add a new code

---

@gerdy new app will not let me add a new code

---

@gerdy I have that installed, all functions work except adding new codes.  

---

@detention same error here

---

@gerdy does the rboy apps work in the new smartthings app or only in the classic app? i thought i read somewhere "smartapps" were going away

Answer 3

Most of the Apps are missing still. But I found if you install them in Classic you can still use them in the new app. So I'm installing a bunch as I'm making the switch now, just in case I want them later.  

Answer 4

It rather depends on how you use the apps. If you actively use the apps to control devices then you might find custom device handlers don't yet have an effective UI in the new app. I don't so it is no big deal to me. There is a new endpoint app named SmartThings Home Monitor that does a similar job to Smart Home Monitor but isn't all the way there yet. Just be aware they are two separate things and you might only want to use one or the other. Routines are not available, instead you use a custom automation creator to build simple 'if . then . ' automations and they anticipate more focus on scenes. Unfortunately the custom automation creator is a bit too cut down to effectively replace routines one to one and you typically need to use more than one automation or just think differently. Don't forget your routines will keep running unless you disable them. Mobile presence is in the new app but in being tarted up as 'Member location' for use in automations, they seem to have forgotten about exposing it as a device on the home screen so you can actually see the current status. It is sometimes suggested that mobile presence is more reliable on Android if only one app is installed. They seem to be taking the opportunity to review what SmartApps were in the 'marketplace' and to release them to the new app gradually (if at all). Your custom SmartApps are available. Your installed SmartApps should appear and be controllable. Things like Google and Alexa are now classed as 'Connected Services', which would be perfectly reasonable had they not been inexplicably hidden away in the settings, and had it not been a bit arbitrary (you could argue 'ActionTiles' and 'webCoRE' are also connected services but those are classed as SmartApps). The dashboard is replaced by the home screen, which does something similar but in four times the space and less effectively. Unfortunately that seems to be typical of the One UI which I have discovered seems to be designed for people who hold their phones completely differently to the way I do. I uninstalled the Classic app a couple of weeks after finally being able to install the new app. I don't really miss it.  

Answer 5

The issue is if you use the Samsung as a home alarm system. Classic app you can get the system to trigger when everyone leaves but the SmartThings Connect app does have that ability. I’m staying with the classic app. I gave the new version several try’s and I always went back to the classic.  

Comments

@armes yes it does have that capability now, but seems to only work with mobile phone presence sensors. However what you can’t do is to disarm a lock in any automation

---

@noisette fair enough, I will have a look. Thank you for the update

---

@armes surely you can recreate this in Webcore though?  

Answer 6

For me everything went fine, I moved to the new app. Security works more or less the same way. I use a variety of sensors, flood, motion, loads of hue bulbs and contact sensors. Also z wave as well as zigbee. Have a few odd Xaiomi sensors too and they have all worked, so custom handlers seem ok at least for some things

Answer 7

The bigger question is what is the advantage of the new app? I know they will migrate eventually but if it doesn't work with DTH or custom Smart Apps (Webcore) then it isn't worth it.  

Answer 8

I've been using the old app mostly, but had the new one installed too. In the last couple of weeks I've swapped, so still have the old one installed but am primarily using the new app. To support this I've removed all my routines and just have scenes. I've just realised I've still got SHM in ActionTiles and WebCore and it's not causing problems, it's just that I can't interact with it from the new app. As I have the old app still, I get SHM notifications. I found the lack of "when things get busy" is a pain, I had to come up with a piston to change mode based on motion and time of day. In summary, it's not a disaster unless you're using SHM as your alarm. I got too many false positives really so wouldn't mind just ditching it totally.  

Answer 9

Actually just had a brainwave. What I have done is set up three automations. If (away) then (arm STHM) If (home) then (disarm STHM) If (night) then (arm STHM home) That way I can use my old WebCore pistons which used to both arm/disarm SHM *and* set the home mode, it's just that these automations will handle STHM based on home mode as well.