TylerDurden
December 12, 2017, 1:45am
105
You don’t have to code anything, but you have to install custom code that’s already been developed. It’s not too difficult to do. (First time is the hardest.)
Here is a link to a thread that discusses the custom code that will integrate TPLink devices to SmartThings via the cloud.
April 26, 2018. Added support for the HS220 Dimming Switch.
January 30, 2018. Update to Version 2. Changes
a. Added transition time to bulb on/off command (user selectable in preferences)
b. Fixed Energy Monitor to accommodate HS110(AU) data formats.
c. Commonized menus between Hub and Cloud versions.
d. Updated naming conventions to function based, supporting TP-Link’s expanding product line.
e. Changed naming conventions to support GitHub integration.
Upgrade Recommendation: Do not recommend upgrade unless you need to add device models not in previous baseline.
Verification Status:
HS100, HS105, HS200 - verified on exact device.
HS110 - previous version verified by other users.
HS115 - future product, same control as HS110.
KP100 - assumed same control as HS100.
HS2…
This is a link that explains how to install custom code in general.
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 …
3 Likes