eurotrash:
So if I exclude the Valve then put this in as a device handler, when it includes again will it not automatically go with ST’s stock or native? how does that work? I’m a computer engineer but I don’t code. I can follow the code and I understand where the “Capabilities” parameters are set, but is it like Kornshell where I can just comment out what I don’t want set or is there delimiter, carriage return, etc that I need to know about ?
Do you think I could find an even more basic than this? just want it to be a switch that I can set by schedule and days of week, like every other switch…
You don’t have to re-add the device. You can just assign it to a different device type handler in your account, use that one for a while, and then swap it back whenever you want.
The following FAQ covers that process (this is a clickable link) and I think it will help explain the concepts as well.
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 …
2 Likes