Webcore for St will continue to work until they shut down the remaining parts of the groovy IDE (12/31/2020). After that you are limited to the “automations” native in the new app. No one is working on a port of WebCore for the new ST API because it isn’t possible.
Although, by then parts of “automations” will run locally (as promised)… lol
Are we about to witness a mass exodus from smartthings?? I have a funny feeling this forum is going to get quiet soon like it did when hubitat first came out.
@jkp i dont want to see that happen but with everything going on…its not looking good. Remember how the volume toned down here when hubitat first came out. Too many issues with all this flawed software called smartthings is pushing people away. Im.not a power user nor an expert but this migration was botched & not ready for prime time.
.
I am about to do the migration from the Classic Smartthing platform to new one. I have over 120 devices, many automations, moderately complex things handled via WebCore, and several custom device handlers I have written myself, for generic devices. Almost every fixed piece of electronic equipment I have is on ST. Wish me luck. I am genuinely terrified. Petrified. I feel like I’m about to go into a brutal operation, with no anesthesia.
I wish you replied 3 minutes earlier. Now that I did step 1, which was to actually migrate to the new app via the classic app banner, what are my options? Can I still carry on with my old “stuff business as usual”? Or am I now committed to testing and re-customizing everything?
Seriously, the best way to go with complex environments is to install newapp and login without migration first to see what’s broken before jumping in with both feet.
Lets see if the migration completes with ‘no issues’ then see how it lands. There’s plenty of folks willing to help… I mean - I have two whole bottles of whiskey here myself. (@swamplynx - is that a healthy enough supply?)
Well, the migration completed successfully. A handful of devices ended up being not assigned to a room, but I quickly corrected that in the app. Webcore-controlled automations still running smoothly.
Should I be expecting some breaking functionality?