This will explain how to get smart apps that are not in the market place as well as a bunch of other things.
(March 2018: All of the following applies only to the SmartThings Classic app. If you purchased your hub after March 1, 2018 and are using the new “SmartThings (Samsung Connect)” app, creating rules works differently.)
You’ve got your hub. You’ve got some devices. Now how do you schedule what happens when?
SmartThings doesn’t have a rules engine/scheduler, so there’s no one tutorial for how to do this. But it’s an open platform, and there are about 12 different ways to set up various kinds of schedules. Some require custom code, some don’t.
A “scheduler” in this context is anything that causes a networked device to perform an action, even if it’s just to toggle on or off immediately. (Network engineering definition, forgive me.
If you just want to jump straight to learning how to find and use custom code, here’s that FAQ:
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 …
Meanwhile, there are a whole bunch of different ways to give you one tap control of whether the doorbell sounds or not. What code/rule did you use to set up the doorbell sound in the first place?