If you don’t want the migration banner, you need to use Classic version 2.17, a lot of users stayed on that version because of the introduced bugs on following versions.
Is there a link to downgrade?
Not sure if I post the link if it violates some sort of TOS, so just do a google search for “how to downgrade android app to previous version”. As Alwas suggested, I went to 2.17 (which is several versions back) and that did the trick, no more banner. No idea if this is possible or how to do it in IOS if you have an Iphone.
@SmartThings @blake.arnold now that we are getting the message to migrate to new app… when(do?) will third party apps like ActionTiles & WebCore have API to execute Scenes, LightGroups, Automations and SmartThings Home Monitor?
The answer to date from Samsung is a firm, “Someday”.
I don’t believe they’ve ever said that third-party apps would be able to control STHM, have they? A lot of security systems lock that down.
I’m currently using Webcore “Set Smart Home Monitor Status to ___” to arm/disarm SHM in the classic app. Anyone knows what the alternative is since this functionality is no longer available in the new app (STHM)? Does that mean I’ll now have to perhaps write a piston to manually control my sirens…etc?
Webcore cannot directly change the security.mode for STHM (The equivalent of SHM in the new V3 app). It can be changed in a scene or an automation created in the new app so there are some workarounds. See the community FAQ
i believe webcore works in the new app . i am doing something simiar but using my version of rule machine and it works in the new app. I dumped their new sthm as their new automations do not work correcytlly as the precondition is not enforced as an AND . So I went back to using smart alarm, with modes for my arming disarming etc, and setting the mode ie home,away with rule machine… This seems to be working ok… Now if the stupid app would not come up blank with automations, rooms, scenes etc, 90% of thte time
but if you are bent on using the new shtm and webcore, you can settup virtual switches for each of the armed stay, disarmed etc in shtm and add automations to set the corresping shm armed stay etc with autmations in both directions, then you can control them with webcore via setting the virtual swtiches
I wasn’t specifically referring to STHM, which as you say, is a more complicated matter. I was speaking to the general availability of a new API that DTH & Webcore replacements will have to migrate to when Groovy and the IDE are sunset.
Yeah, I ended up figuring that out as well (not sure if I posted it though, so thanks for putting it here in case others have that problem). Seems ridiculous that the app won’t function at all without a tracking link working.
I totally agree. I have been with SmartThings since the Kickerstarter days, and I am not just frustrated at this forced change, I am angry.
NONE of my SmartApps work (or will even allow me to edit or view settings) without crashing the app.
And no way of viewing the status of presence sensors? Seriously? How are simple things like this deprecated?
Samsung has trainwrecked what was once a great, superior platform.
Just got the banner to switch to new app today and lucky enough nothing happens to my new app settings since I’ve already migrated myself. Deleted the classic app.
Just hoping I could ever see the mobile presence status, why is it so hard to do this? I guess they never wanna go this? How am I going to trouble shoot automations based on mobile presence? By checking the history page? Are you nuts?!
I also just got the banner. I don’t have any routines, smart home monitor, or smart locks in the Classic app. However, I have some integrations which don’t have an interface in the new app yet. If I “migrate” will I be unable to access those in the classic app?
What integrations do you have that don’t appear in the new app?
All the custom Smartapps I have, they are still accessible from the Classic app but they are also in the new app and work.
Mainly the Ecobee suite. The devices show up in the new app and work but with very limited interfaces and functionality. The smartapp is probably fine.
I got the banner a few days ago and converted to the new app. It went completely smoothly but it’s likely because:
- I have no ST Routines ( I DO use Alexa routines when possible)
- I don’t use ST’s Lock Code Management (I use RBoy’s app and DTH)
- I don’t use SHM at all (have a stand-alone monitored security system)
- I only use webCoRE’s presence
- I only use webCoRE for automations - I have about 50 pistons or so (many are 250 lines or more)
- I haven’t loaded the new Alexa or Google services (I hear I should be waiting for the bugs to be worked out)
So, this transition phase to the new app was fairly easy for me. I know that during the next transition phase, webCoRE will quite possibly be a major issue for me as I use it exclusively (no Smart Lighting either). Hopefully, the replacement will be ready by then.
Got the banner yesterday. I’ve had the new app 6+mo’s now but never us it.
Is there a summary anywhere of what the “migration” does, or more importantly, doesn’t do?
Is the migration one-way (i.e. classic app won’t work anymore)?
I gather webcore still works but some pistons may need to be modified - are there guidelines on that anywhere?
Custom DTH’s work or no?
I’m OK with some pain/effort to migrate but would like to go into it knowing what works/doesn’t and reading this 1K+ thread to get that is not a BKM.
thanks anyone!