Different questions. So let’s see if we can sort it out.
Samsung Will no longer offer a free groovy cloud where you can host custom smart apps and custom DTHs
So what’s going away is the place where custom smart apps and custom DTH is currently run. So anything that you have now that you had developed to run in that custom cloud is no longer going to run.
Option 1 for DTHs
The replacement for DTHs written in Groovy are edge drivers written in LUA which run on your own hub. You can run the production versions offered by Samsung for most zigbee and zwave devices. But just as with the previous architecture, there are also individual community members and device manufacturers creating custom edge drivers. There are quite a few of these already, and normally they are created to offer support for features not handled by the standard versions.
To read more about these options, see the community FAQ:
FAQ: I have no idea what Edge is. Is that a new developer tool? (2022)
So that’s pretty straightforward. If you currently use a custom Groovy DTH, check and see if there’s a custom edge driver for the same device offering the same features.
Option 1 for groovy smartapps: replace them with the official features.
If you previously were running a groovy smartapp that ran in the free Samsung Groovy cloud, you’ll have to find a new option for that functionality.
The first thing to do is to try the current routines in the SmartThings app. This has a lot of features that were not available in previous app versions, and it may be all you need for some use cases. It’s certainly worth checking.
SmartThings also has a new feature called the Rules API But it is still in development and not fully documented. It was intended to give power users ability to create something sort of like webcore pistons but using official features, but it doesn’t have full parity with webcore yet and it feels very technical. worth a look if you’re comfortable with scripting. And it doesn’t have a web interface: I’m pretty sure you have to have a PC to work with it.
Option 2: SharpTools
One of the most popular options is the third party SharpTools rules engine. They have a free version for simple use cases and a more powerful pro version at $30 a year. Many people find they can do everything they did in their custom smartapps with this. It’s also been a pretty good substitute for Webcore for many people. The developers are also very responsive if you post in their community forum with features that you’d like to see.
I’m putting this as the second option because I think it’s really the easiest to use after the smartthings app itself. It has a nice visual interface and a very understandable structure. And it works in a browser: you don’t have to have a laptop. Just a mobile device with an Internet connection.
It’s true that it doesn’t run locally, but then your previous Groovy smart apps didn’t run locally either. I think it’s definitely worth a look.
Option 3: Ask the author (or at least in the author’s thread)
Also, check with the author of the previous smartapp. They may already have a recommendation for what to do after Groovy. The answer could be complicated: it might involve Ifttt or Alexa routines or MQTT or node red or Some other kind of integration. But it’s certainly worth asking. For example, an author of a previous MyQ Lite integration is working on a new version now. And if you check in the homebridge thread in this community, there are a couple of suggestions for replacements for that that you can try.
Option 4: Hubitat
If none of those meet your needs, it’s worth considering Hubitat. It’s a competitor hub, created by previous smartthings users, which has a version of Groovy that runs locally and can support most of the custom Groovy code that was written for smartthings. For example, some people who just couldn’t imagine doing without WebCore end up running it on Hubitat.
You’ll have two possible configuration options. Either you can just move everything, including all your devices, over to Hubitat and run the groovy code there and only continue to use smartthings for Devices/Integrations that Hubitat doesn’t have. Like Matter.
Or you can leave your devices on smartthings, and just run the smartapps over on Hubitat.
You’ll need a way for smartthings and Hubitat to communicate with each other, of course. MQTT is one possibility, although that’s fairly technically complicated to set up. But I would ask in the Hubitat forum for how people are going to approach this kind of combination. It’s definitely doable, it will let you keep most of your custom Groovy code, but it’s certainly a much more complex solution than just using SharpTools.
Option 5: write brand-new smartapps, host them yourself, and use the new architecture
You can still have custom smartapps, it’s just that smartthings isn’t giving you a free place to host them anymore. You can write them in any language you want and then connect with smartthings through their API. But this is a real programming project. I’m sure you can hire a professional to do it, but I have no idea what it would cost. And you would still have to pay for the hosting unless you set it up on a local server on your LAN.
Summary
So different solutions will work for different people, depending both on the exact use cases you are trying to replace and your own preferences about technical complexity etc. there are still custom edge drivers, but they aren’t written in Groovy. And there are still custom smartapps, but you have to host them yourself.
The groovy custom code that you have right now is going to be homeless once this transition is complete. so that’s why you’ll have to decide whether you want to move it to a new groovy home, like Hubitat, or replace it with something that works with the new architecture.