I think you can already do what you’re asking for if you use some of the community-contributed code. @tslagle13 has written several popular “director” apps that might fit the bill. See the following topics for an overview of how things work. These aren’t technical topics, but they’ll give you an overview of how the pieces fit together.
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 …
.
(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.
You’ll have to ask about the logging. The system keeps 7 days, but I don’t know if anyone’s set up a scraper yet.
1 Like