I can’t help with the hub migration issues, but let’s start with the basics.
The following FAQ will explain the terms, abbreviations, and concepts behind using custom code, so that should clear some things up. (The topic title is a clickable link):
The original FAQ information in this thread refers to the original smartthings architecture, which was in place through the end of 2022 and a little beyond. Custom code was written in the groovy programming language and ran in the smartthings cloud.
As of May 2023, you can no longer add new Groovy DTH‘s or smartapps to your smartthings account. So if you came here because of a link in an old forum thread, or on another site, I’m afraid the Groovy information is no longer usable.
All of this was replaced by a new architecture. Cloud to cloud integrations use the smartthings API. Hub connected devices, mostly Zigbee and zwave, now use “Edge Drivers,” written in the LUA programming language. Here’s the official announcement on those:
The process for using a custom Edge Driver in the new …
Also, this might help a little:
The SmartThings platform is currently in transition to a new hub (V3), new app (“SmartThings (Samsung connect)“) new Alexa skill, and a new cloud platform ( The old one used the groovy programming language, the new one doesn’t).
This means that a lot of the information you will find in both this forum and the official knowledge base may be a little confusing.
The Mobile Apps ( yes, there are two right now)
FAQ: how to tell which version of the SmartThings mobile app that you have
The classic app has now officially been discontinued, but some members continue to use an old version of it and you will see references to both in the forum.
Official SmartThings Tutorials for New Customers
If you just want to learn more about using smartthings, there’s a decent get started section in the o…
Oh, and we do need to ask what country you are in, as some features are region-specific.