Use extra switch buttons Smartthings

They actually did hire the author of Webcore several years ago. He worked for them for a couple of years, then moved on to another company.

SmartThings staff have said multiple times that they believe the new “rules API” will offer parity with Webcore, but it’s not quite there yet, and it’s just not as easy to create the rules as it was in Webcore.

If you were a Heavy webcore user and you don’t find that the rules API meets your needs, I think the most popular options are:

  1. subscribe to the Premium level of SharpTools. Lots of features, very responsive, developer community, probably the easiest user interface of the options. Does not require that you have a laptop to create the rules. The biggest negative is that you do have to pay an annual $30 subscription fee. Whether that’s worth it to you or not it’s just an individual decision, they’ve obviously put a lot of work into it. They have a free trial if you want to check it out. Some people have also decided to subscribe for a year to carry them over while they figure out what their long-term strategy is going to be. It has a nice visual interface, so it’s a pretty easy learning curve. :thinking:
  1. As @csstup mentioned, the version of webcore that you are already used to is still available over on the hubitat platform. In fact, they’ve included it in the official features now. There are also quite a few members that are now running both smartthings and habitat, using one of the community created edge drivers to keep the two in sync. That setup allows you to leave your smartthings network as it is and to continue to use the smartthings app, you just run your pistons over on hubitat. Obviously that adds complexity and some cost and some ongoing maintenance time, but it is doable.

You can read about these and other options in the following thread.

Replace Groovy with Automations—what’s your plan?

And as @jaidank said, Webcore was an amazing community project, but resource intensive for the company. They felt the Rules API would be a better match to what they wanted to do. Maybe, if they ever get it finished…