Get ready to make the switch!

I REALLY like the flow of the Classic App but I liked it better before they changed things around but… I got use to it and adjusted.

The New App has its perks such as filters and graphs. There’s a lot of wasted space and some items are hidden and others are disabled. Some users have options that others don’t have such as monitoring rules and linked places. There’s no way of knowing what devices are tied to rules and what rules triggered actions.

The most frustrating thing for me is IT’S TOO SLOOOOOWWWWW!!!

Saying all that, it’s not that bad of a layout. Just have to think, this is not Classic. This is not Classic. This is not Classic. :weary:

Umm no. It’s bad layout.

I’m not a fan of the home screen but the menu has most things right there.

It even has a search feature:

It took a little while for me to get the flow but, IMHO, there are some good features. From where it started, the current version is miles better.

Well done again… Trying to set temperature by typing in. I’ve just deleted the first number by backspace.

@blake.arnold - I cannot even imagine how this can be given to anybody who needs text to voice. I can not even read what it wants to say, because it is blank!

That’s the understatement of the century. I can get use to the inefficient use of space, and the gigantic amount of scrolling around needed, and even the inconsistent sort order of devices in selection lists, but performance and speed is horrendous and unacceptably slow. If you just leave the app in the Dashboard in any spot for any length of time, you’ll notice the thin scroll bar on the right flash as if something is constantly being refreshed. That happens on all my Android phones and tablets.

It sucks and there’s nothing I can do about it.

EDIT: You know what else sucks? Mobile presence has been ruined. I’ve been gone for almost an hour and the POS app still thinks I’m home.

Well I finally migrated yesterday given the impending deadline and then spent the next 2 hours cleaning up the mess. Had to remove 2 virtual hubs and nearly 70 virtual devices named either “sensor” or “meter” that I finally found out from another thread were because I’d used the IDE simulator in the past (which almost any developer will have done). Of course these simulator devices never appeared in Classic or in the IDE. Why anyone thought they should show up in the new app is a mystery.

I’ve also got what looks like a still-unresolved bug with location mode preconditions. Just seems to be plain broken.

Other than that the app performance is OK for me and I’ve mostly been able to get things back how I want them, with the exception of my virtual DTHs for Pollen and Air Quality. Having glanced at the new developer documentation it looks like they would require a near-complete rewrite, if I could even get them working at all. Given the still incomplete info there I have almost zero motivation to do that, especially combined with the changes on the roadmap to how SmartApps work. Hats off to those developers who are trying to stick with SmartThings but I am out as far as development goes.

Overall I give the new app 6/10. It’s not ready yet and they should not be retiring the Classic app while there are obvious automation bugs that have not been addressed. Combined with the lack of device filtering in the new Google Assistant integration, SmartThings has become considerably less polished in the last few months. I know there have been statements about how so much developer time is currently being eaten up triaging problems with the classic platform, and if they really do sunset the classic app next week as planned I hope they genuinely will be able to spend more time moving things forward again and get this mess straightened out.

@rontalley graphs! Very cool, did not notice them until you mentioned them!

What are filters?

In the history tab, you can filter which events to reflect on.

So finally migrated to the “new” app due to the impending deadline and have come across an issue that I can’t see the solution for! We were previously using the Smart Home Monitor with routines to Arm and Disarm based on the presence of two mobile phones and two of the Samsung SmartThings Presence Sensors. It seems that I can create an Automation to Arm and Disarm the SmartThings Home Monitor based on the presence of the mobiles, if this was working reliably enough, but the Samsung SmartThings Presence Sensors can’t seem to be used for presence in the Automation!

Interestingly there is the option in the SmartThings Home Monitor to setup Security mode reminders for when everyone leaves and when anyone arrives which allows the SmartThings Presence Sensors to be selected as members!

Any suggestions, ideas or telling me what I’ve completely missed welcomed!

I use Virtual Switches and webCoRE.

They are under “Device status” when creating the automation.

Do you realize how long that takes when you have over 120 devices?

And that if you logout/login or uninstall/reinstall the app, all that customization is gone and has to be redone?

EDIT re-installing STHM fixed it, but I’m not holding my breath…

Ok, so I’ve started this horrific process and am just having issue after issue. But a BIG ONE is that STHM defaults to using ALL OF MY SENSORS (including virtual/alexa switches) anytime I arm/disarm/arm stay.

I’ve repeatedly gone in, turned the ‘use all’ switches off and then selected the ones I want to use before saving. But every time I arm the house it goes back to using everything, so the alarm hasn’t stopped kicking off.

Can anyone help with a fix? I’m seconds away from just trashing this entire thing and heading over to you know where. I’m soooooo gutted my perfectly functioning smarthome has just been decimated by this shocking app/forced migration :disappointed:

Thanks @Bry have some automations that now need testing if we all ever leave the house at the same time!

upper right menu > edit and you can do it in mass

Thanks, that helps. At least I was able to deselect them all so the app starts quicker now.

bet it loads real fast when it’s empty :joy:

I’ve noticed that when STHM Arms and a sensor is opened, it doesn’t tell you which one. Is there a setting I need to turn on is this a complete oversight?

when does the countdown clock start