@GetCarter I have the HS200 hooked up to ST using this:
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…
I was using the node.js hub version for a while, but switched to the ‘cloud’ version when it came out and it works great. The only thing is that if you hit the switch manually it can take up to 15 min for ST to see that. However you can change that in the code or use webcore to refresh it on a timer.
You can change the refresh frequency yourself and now. Follow these steps:
a. Open the Device Handler on the IDE.
b. Scroll down to a section as below:
def setSchedGetStates() {
unschedule()
runEvery15Minutes(refresh)
runIn(2, refresh)
}
c. Change the “runEvery15Minutes(refresh)” to "runEvery5Minutes(refresh).
d. Select “SAVE”, then “Publish”
e. In the application, open each device you need 5 minute refresh on.
f. Go to the settings tab (the cog-wheel in the top-right)
g. Select “Done” (this will cause the device to be updated which restarts the refresh schedule).
I will strongly consider a preference in the app for refresh. Not hard to implement, just never thought of it.
2 Likes