“Enjoy it while it lasts”?
ICYMI, here’s that official statement
Thank you HalD
Yes, here
ah, they got smart and are taking the gentle kill approach. LOL
Quick question on the migration:
I have not used the migration tool, but have been using the two apps in parallel and have
-
deleted all routines in Classic (and recreated Scenes and Automations in the new app to replace them)
-
changed presence settings, so that my (phone) location for ST comes from the new app (instead of Classic)
-
not been using Smart Home Monitor
-
not been using any smart locks
All devices work in the new app (some custom DTH show up different or weird, but I can live with that).
Do I still have to execute the “migrate now” tool in the old app?
I am a bit reluctant to just do it, as I put quiet some work into the (manual) setup of the new app and do not want it to be reset or changed by the migration tool.
Thanks!
You should be good. No need for you to use the migration tool since you have already done it manually.
For what it’s worth, I did all the same things you mentioned. I think I had even uninstalled the classic app.
When I got the email about migrating, I went ahead and did it. There were no discernible effects.
No guarantees, of course.
Yes… this one drives me nuts. While I’m driving away from home it was very helpful to see that I left a rear window ajar (don’t need to turn around) vs. the front door (I need to go home) - Without having to open the app and scroll!
Almost as bad as going to clear an incident and only being told “a text message was sent”!
I still have one of my motion sensors that keeps showing offline in the api and app. However, it registers all activity, just shows offline until motion, then goes back offline after motion. Support has not been able to help. I moved it next to the hub so it only has the single connection, same results. Only happened after migrating. I have three of the same models only one is messed up. Already tried resetting as well. No luck.
what brand and model number is the motion detector
Bosch * model: ISW-ZPR1-WP13
Had a custom device handler before migrating. After migrating it had the SmartSense Motion applied. I have switched it back and forth but still offline. My other two, same model are fine.
interesting, i have 17 of these, some outside, and they all migrated over with the custom dh. look in the ide and see how they are linked back to the hub, directly or if they go thru other powered zigbee devices.
i would change the dh back to the custom dh. also, slide open the back and try pressing the tamper a couple of times. still if not, then take the top 2 of the 4 batteries out and put them back in. else, remove and re-pair by sliding open the back and taking out the top 2 batteries and then hold the tamper down and re-inserting the top 2 batteries with in 15 seconds.
I actually reset the device by following the instructions (crazy battery priority) and that still didn’t fix it. I will try the old device handler, although the old one does move it back to cloud instead of local.
Is the IDE going away at some point? Concerned that I could be stuck with one device type and need to change it in the future.
Yes, ST has announced that sometime in 2021, the legacy Groovy IDE will be shut down.
So at that point there would be no way to switch the device type…
We really do not know what will replace the Legacy Groovy IDE at this time for Hub-Connected devices (at least I don’t know 
) Samsung has been a bit quiet regarding any details in this area, and with their apparent move to get out of the hardware-side of home automation, perhaps they expect their WASH partners to deal with it? Just a guess.
After weeks of back and forth on migration, the date came and went fine… new apps been fine, however today everything went “offline” and the new app shows the hub as offline, its not offline as third parties such as Alexa can still control things tied only Smarrthings hub. I suspect my link between my account still didnt migrate properly now Im totally orphaned. First sign something was wrong sirens started going off today randomly.