I have been trying unsuccessfully to add a TP-Link HS100 plug to the gateway. I am using the standard Raspberry Pi 0.10 download on a Pi3. I have added the TP-Link add-on. The HS100 is plugged in and the wifi light is blinking green and amber.
The HS100 has never been linked to a Kasa account. My understanding from the thread below was that this is not necessary fror TP-Link devices [1].
When I scan for devices, the HS100 is not found. However, it does appear that it is found, as in the run-app.log I see the following:
2019-12-20 10:37:37.223 INFO : About to call startPairing on ThingURLAdapter
2019-12-20 10:37:37.225 INFO : About to call startPairing on TPLinkAdapter
2019-12-20 10:37:37.252 INFO : Opened a new things socket
2019-12-20 10:37:37.256 INFO : tplink: AddonManagerProxy: recv: b'{"messageType":4099,"data":{"timeout":60,"adapterId":"tplink-adapter","pluginId":"tplink-adapter"}}'
2019-12-20 10:38:37.229 INFO : Pairing timeout
2019-12-20 10:38:37.231 ERROR : Thing was not added
2019-12-20 10:38:37.233 ERROR : addNewThing cancelled
2019-12-20 10:38:37.237 INFO : tplink: AddonManagerProxy: recv: b'{"messageType":4100,"data":{"adapterId":"tplink-adapter","pluginId":"tplink-adapter"}}'
2019-12-20 10:38:37.241 INFO : thing-url: Adapter: ThingURLAdapter id thing-url-adapter pairing cancelled
I’ve tried a hard reset of the plug, with the same result.
Just started with the Gateway, so sorry if this is a newb error.
You’ll still need to use the Kasa app to set up the plug initially and get it on your Wi-Fi network. I believe you can do so without attaching it to an account, though.
That log doesn’t show any devices being found, so my guess is that it’s not on your network (confirmed by the flashing lights).
Adding the IP address manually didn’t work either; the log showed “no route to host”. That and your comment about mDNS helped: I moved the plug so that it was connecting to a different wifi access point and it was immediately found. So I have a network problem to sort out but the gateway problem is solved.