Migrating to new app - Many issues

Yes the classic app certainly interferes with ST new app, but for me the logoff problem still occurs even with Classic not installed (very frustrating). Refer Ongoing Auto-Logoff with new ST app

Yeah, that is correct. I was referring to location services.

1 Like

I switched back to ST Classic yesterday, and working as expected (rock solid) whilst also enjoying more complete automation routines including OOTB Smart Home Monitor integration with location services. ST v3 still installed (location disabled), but wonā€™t be uplifting until more complete and stable.

I tried migrating over, only to discover two Z-wave devices didnā€™t migrate. The devices are an Aeotec heavy duty switch I use on my water well pump and the other is an EcoNet Controls valve. These were set to turn off and close upon the detection of water from one or more of my Samsung moisture sensors through a Smartapp within the Classic app. This always worked great for the last few years. So, since these devices didnā€™t seem to go through the migration stage, I contacted Samsung. After a few days of receiving instructions on what to do (none worked), I wasnā€™t hearing back from them, so I reached out again, only to be told that ā€œupon review of my case, they decided they could not offer me any further assistance as they only offer support to the US, and where I am located in Canada, they canā€™t help.ā€ Sweet! So, one of the things they got me to do is remove the Smartapp within the Classic app which I did, but now, I still donā€™t have these devices in the new app and I canā€™t re-add the smartapp to the Classic app any longer. What now?

Did the devices not appear in the new app or could you see them in the new app but did not have the same capabilities you had in the Classic app? If they did not appear, ST support should be able to perform the sync. You may need to ask them to escalate the ticket to higher level support. If just not seeing the same capabilities that was available in the Classic app, maybe someone here can assist with modding the Custom DTH to work with the new app if that is what you used or guide you to an appropriate stock DTH.

As for reinstalling the app in the Classic appā€¦ you should still be able to add it back or also in the new app. If you provide the smartapp you were using or a link to it, maybe someone on here will be familiar with it and be able to provide assistance.

There is the option to close valves when a leak is detected with STHM under settings for leak sensors and you can also utilize automations.

The switch originally showed up in the new app, but they had me remove it. I was able to remove it from the new app but now I canā€™t re-add it.

The Smartapp Iā€™m referring to is the feature within the Classic app that does the ā€œif something occurs, do thisā€ feature. The photo attached shows the notice that I can no longer add this command back in the Classic app and because the z-wave device do not show in the new app, I canā€™t add it there either.

Regarding dealing with my case, as indicated, they are refusing to help me further or escalate it since Iā€™m in Canada and not the US.

Iā€™m not a programmer so I fumble my way through this stuff as best I can but any help would be much appreciated.

Yes, there is the message at the top saying you canā€™t but you can :). If you open smart lighting, you can still add smart lighting rules. :slight_smile:

Smart lighting is also available in the new app under menu (3 bars in the upper left of the screen) and select Smartapps . If it does not appear, add it from the main dashboard by clicking + in the upper right of the screen then select smartapp and add it.

There is also Automations that do If Then. To add an automation, on the main dashboard click + in the upper right of the screen and select Automation.

Thanks, but Iā€™m not trying to do anything with my lighting. I had a smartapp that would turn my switch off and close a valve when the sensors detected water. I canā€™t add this again in the Classic app, but perhaps Iā€™ve misunderstood what you are trying to get me to do.

Again, if you provide a link to this appā€¦ perhaps I or someone else can help.

I donā€™t know how to do that and that doesnā€™t sound secure.

Fair enough. I hope you are able to resolve the issue.

You may want to look at STHM in the new app and automations to perform the tasks you described.

As indicated, if someone uses layman terms to help me fumble my way through. I canā€™t use the new app since the two devices I need to operate do not appear. I do not see anything labelled STMH in there. How do I provide a link? I just donā€™t understand why Samsung refuses to help because Iā€™m in Canada.

STHM = SmartThings Home Monitor

Instructions for adding it and configuring it can be found in the following clickable link:

I finally bit the bullet and migrated yesterday. Other then the need to reset up presence (weā€™re using iOS) the migration actually went well. I needed to invite other family members using the bar code scan process (under the Members section) to get the app and presence working on the other iOS devices in the family after updating their devices to the new app as well. To do that, you need to access SmartThings settings from the main menu, and toggle ā€œGet your location from this phoneā€ to ON. Then revisit automations using presence to make sure they reference the correct devices as names may change.
Webcore, Core, SHM, custom apps etc. seem to work fine. I have a pretty extensive system including 200+ devices, theatre integration with Harmony etc. so I was expecting more issues. Iā€™d say it went quite well.

Iā€™m hoping to have the same experience as you. Have much less devices than you but do use Webcore extensively but not SHM, and very few devices with custom handlers. Did you have any old custom device handlers that you had to deal with? And if so, what did you do for those?

I use an old GOULNERā€™s RG Linear GD00Z Garage Door Opener device handler but canā€™t seem to find any info on how to migrate (if I can at all) to some generic garage door opener or something.

Search the tag migration2020 and you can see threads about the migration and check if any particular device/feature you were interested in already has a thread.

In this case:

GoControl (Linear) garage door openers can't connect in new app

1 Like

You are, and always have been, my most favorite resource in this great community. Always the noob, Iā€™ve been searching ā€œIinearā€ ā€œgarage door openersā€ the ā€œgd00zā€ the goulner name, you name it and could only find old links and old info.

So once again, as I have over the past, what 4 or 5 years of using ST and still being a noob, have to thank you @JDRoberts

3 Likes

Steve, I have about 10 custom device handlers, CORE, WEbCORE, and use a variety of rboy apps to manage my garage door relays, and Zwave door locks. My pool automation system uses tweaked Fibaro door sensors with external temp probes wired in and these too are still working fine. All of my custom or tweaked apps are working fine.

My garage door opener uses an LFM20 Zwave relay to toggle open/close in ā€œmomentary latch modeā€ and also no issues.

It looks like Iā€™ll have to redo a few scenes like ā€œall lights offā€ which generates an error. In those cases itā€™s faster just to delete and recreate problematic scenes.

To be honest, I was expecting a lot of pain, so good job ST crew.

1 Like

@denwood So happy to hear your experience. Iā€™ve been dreading and delaying switching but have a day to finally pull the trigger this week. Fingers crossed!

Surprisingly free of drama gb. That said, a Hubitat box showed up in the mail today. The lack of backup/migration in ST has me nervousā€¦