[OBSOLETE] FAQ: An Overview of Using Custom Code in SmartThings (SmartThings Classic, Groovy Code)

[JDRoberts]

@Mike89

Has anyone used the new smartthings app? My devices using a custom device handler seem to be in a stuck “Checking status…”

This FAQ is specific to the classic app.

If you read one of the threads on the new app, you’ll find the answer to your question:

New app — which CUSTOM DTH’s will work?

I was encouraged by other forum community members to start a topic to discuss which custom device handlers a.k.a. DTH’s will be supported in the new app. (If any ) For those of you that are using the new app, can you confirm any custom device handlers that are working? Below are the ones that I use and am seeking info on… Thanks in advance… @posborne [image] [image] Also, if custom DTH’s are not going to work, Will those devices show up in the new app? Or do I have to exclude them and then add them again using their default device handler?

SPECIFIC differences between "SmartThings Classic" (the V2 app) and “SmartThings (Samsung Connect)” (the V3 app)

this thread is intended only as a listing of specific differences between the two apps, not for complaints, suggestions, discussions of design philosophy, bug reports, questions about migration, joke memes or anything else. Just individual feature differences. We originally used the abbreviation STSC for “SmartThings (Samsung Connect)”, but that never caught on, so now we are calling it the V3 app since it came out with the V3 hub. The V3 app is changing rapidly, so feel free to edit this as needed. The official knowledgebase FAQ is at the following link. Read it. https://support.smartthings.com/hc/en-us/articles/360000114006-New-SmartThings-app-FAQ The “how to” official articles for the V3 app are at the following link: https://support.smartthings.com/hc/en-us/categories/115…