Comments on: Control your TP-Link HS100 smartplug with Tasker http://itnerd.space/2017/02/26/control-your-tp-link-hs100-smartplug-with-tasker/ Blog about Cloud, Automation, Android, Smart things... Thu, 27 Jul 2017 22:01:00 +0000 hourly 1 https://wordpress.org/?v=4.7.5 By: Angela Slaney http://itnerd.space/2017/02/26/control-your-tp-link-hs100-smartplug-with-tasker/#comment-151 Thu, 15 Jun 2017 11:36:00 +0000 http://itnerd.space/?p=252#comment-151 24 days after setting this up it stopped working. It turns out the tokenID had been changed by Kasa. DeviceIDs remained the same. The plugs have been offline – maybe that caused a tokenID rewrite?

]]> By: Angela Slaney http://itnerd.space/2017/02/26/control-your-tp-link-hs100-smartplug-with-tasker/#comment-124 Sun, 21 May 2017 21:02:00 +0000 http://itnerd.space/?p=252#comment-124 This, as coded above doesn’t quite work for me in Tasker. The problem lies in this section:-

Data / File:{“method”:”passthrough”, “params”: {“deviceId”: “%deviceId”, “requestData”: “{“system”:{“set_relay_state”:{“state”:%state}}}” }}

The Tasker variable %deviceId is in quotes and as such Tasker will see it as a String Literal and not decode it.

I got around this by removing the quotes BUT replacing them around the deviceId string when the variable %deviceId is first declared.

Thanks for posting this article.

]]>