TP-Link Plugin v 0.9.9 / v1.0

Plugins that users have built. NOTE: plugins that were developed for Indigo versions older than 2022.1 will have to be updated to work with Indigo 2022.1 (Python 3 - see this blog post for details). If the plugin listed here is not in the Plugin Store (which will show updated plugins) then you will need to ask on the appropriate thread below if it has been updated and where you get get the update.
Post Reply
vvrangler
Posts: 39
Joined: Mon Sep 01, 2014 11:50 am

Re: TP-Link Plugin v 0.9.9 / v1.0

Post by vvrangler »

I have a TP-Link KL135 dimmable color bulb and each time it communicates I get these errors in the log.

Code: Select all

TP-Link Devices                 Pantry Bulb found set to On, brightness 2
   Error                           device "Pantry Bulb" state key Hue not defined (ignoring update request)
   Error                           device "Pantry Bulb" state key Saturation not defined (ignoring update request)
   Error                           device "Pantry Bulb" state key colorTemp not defined (ignoring update request)
Anyone else seeing this or know how to resolve it?
Top
User avatar
jtburgess
Posts: 78
Joined: Wed Jan 17, 2018 7:00 pm
Location: NJ

Re: TP-Link Plugin v 0.9.9 / v1.0

Post by jtburgess »

TP-Link Devices Pantry Bulb found set to On, brightness 2
Error device "Pantry Bulb" state key Hue not defined (ignoring update request)
Error device "Pantry Bulb" state key Saturation not defined (ignoring update request)
Error device "Pantry Bulb" state key colorTemp not defined (ignoring update request)
That’s odd, a color bulb without hue, saturation and color?
They must have changed to a different coding (RGB?)

I’m leaving for Texas tomorrow and won’t be able to look at it for a week.

While I’m gone, could you please collect some data for me.

Click on “Show Events Log Folder” in the top left of the log window, then open the com.*.TP-Link-Device folder, then double-click plug-in.log. This will open it with Console, which follows the end as it grows.
Look for a message with XML that starts {‘system’: {‘get_sysinfo’: etc.

If you don’t see that message, set the plug-in config to have log level set to THREADDEBUG (or it may say DeepDebug).
You’ll definitely see that message then. :)

Copy at least that entire message . You can copy a bigger chunk of the log, as long as it has that “sysinfo” message.

Send me an email with that copied log fragment, and then you can set the log level back to normal. I will be checking email.
Top
timrowledge
Posts: 46
Joined: Sat May 14, 2011 10:51 am

Re: TP-Link Plugin v 0.9.9 / v1.0

Post by timrowledge »

I'm attempting to use the plugin with a newly bought TP-Link HS200 and... not having luck.

First problem was working out that I still needed to download & use the kasa phone app - just as well I had the day before got an iPhone 13 mini to replace my iPhone 4, other wise I would have been dead out of luck. Eventually I got the switch started and talking to my router. I can use `ping` to its IP without problems.

However, I can't get anything working via the plugin within indigo so far. The plugin is installed and I can create a new device entry with tp-link. I chose the 'dimmer' after reading that the dimmer and switch worked the same for the plugin. After setting the log output to debug level I see a lot of stuff. Some of it probably means something :-)

Possibly the first issue is that the 'configure' window does not seem to detect any devices and only presents 'manual entry'. That makes me a tad suspicious of my setup, but if I add the IP number my router declares is active, we get log output -

Code: Select all

Nov 4, 2024 at 3:25:10 PM
   TP-Link Devices                 (plugin.py:selectTpDevice:544): called for: tplinkSmartSwitch, 1749274324, 192.168.0.0.
   TP-Link Devices                 (plugin_base.py:threaddebug:52): called for: 1749274324, UiValuesDict : (dict)
     SlowDown :  (string)
     StopPoll :  (string)
     WarnInterval :  (string)
     actionButton :  (string)
     address : 192.168.0.0 (string)
     addressSelect : manual (string)
     devPoll : false (bool)
     displayManAddress : false (bool)
     displayManAddressButton : false (bool)
     displayOk : false (bool)
     initialize : false (bool)
     manualAddressResponse : false (bool)
     newDev : true (bool)
     offPoll :  (string)
     onPoll :  (string)
     simpleSeparator1 :  (string).
   TP-Link Devices                 (plugin.py:selectTpDevice:544): called for: tplinkSmartSwitch, 1749274324, 192.168.51.49.
   TP-Link Devices                 (plugin_base.py:threaddebug:52): called for: 1749274324, UiValuesDict : (dict)
     SlowDown :  (string)
     StopPoll :  (string)
     WarnInterval :  (string)
     actionButton :  (string)
     address : 192.168.51.49 (string)
     addressSelect : manual (string)
     devPoll : false (bool)
     displayManAddress : true (bool)
     displayManAddressButton : true (bool)
     displayOk : false (bool)
     initialize : false (bool)
     manualAddressResponse : true (bool)
     newDev : true (bool)
     offPoll :  (string)
     onPoll :  (string)
     simpleSeparator1 :  (string).
   TP-Link Devices                 (plugin_base.py:threaddebug:52): 192.168.51.49 -- True

   TP-Link Devices                 (plugin.py:validateDeviceConfigUi:222): called with typeId=tplinkSmartSwitch, devId=1749274324, and address=192.168.51.49.
   TP-Link Devices                 (plugin_base.py:threaddebug:52): for devId=1749274324 valuesDict=UiValuesDict : (dict)
     SlowDown :  (string)
     StopPoll :  (string)
     WarnInterval :  (string)
     actionButton :  (string)
     address : 192.168.51.49 (string)
     addressSelect : manual (string)
     devPoll : false (bool)
     displayManAddress : true (bool)
     displayManAddressButton : true (bool)
     displayOk : false (bool)
     initialize : false (bool)
     manualAddressResponse : true (bool)
     newDev : true (bool)
     offPoll :  (string)
     onPoll :  (string)
     simpleSeparator1 :  (string).
   TP-Link Devices                 (tplink_relayswitch_plugin.py:validateDeviceConfigUi:27): called with typeId=tplinkSmartSwitch, devId=1749274324, and address=192.168.51.49.
   TP-Link Devices                 (plugin.py:getDeviceStateList:492): called for: 'new device 2'.
   TP-Link Devices                 (plugin_base.py:threaddebug:52):    dev: address : 192.168.51.49
batteryLevel : None
blueLevel : None
brightness : 0
buttonConfiguredCount : 0
buttonGroupCount : 0
configured : False
defaultBrightness : 100
description : 
deviceTypeId : tplinkSmartSwitch
displayStateId : brightnessLevel
displayStateImageSel : DimmerOff
displayStateValRaw : 0
displayStateValUi : 0
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState : 
folderId : 0
globalProps : MetaProps : (dict)
     com.JohnBurgess.indigoplugin.TP-Link-Device : (dict)
          SlowDown :  (string)
          StopPoll :  (string)
          WarnInterval :  (string)
          address : 192.168.51.49 (string)
          addressSelect : manual (string)
          devPoll : false (bool)
          displayManAddress : true (bool)
          displayManAddressButton : true (bool)
          displayOk : false (bool)
          initialize : false (bool)
          manualAddressResponse : true (bool)
          newDev : false (bool)
          offPoll :  (string)
          onPoll :  (string)
greenLevel : None
id : 1749274324
lastChanged : 2000-01-01 00:00:00
lastSuccessfulComm : 2000-01-01 00:00:00
ledStates : []
model : TP-Link Smart Dimmer Switch
name : new device 2
onBrightensToDefaultToggle : False
onBrightensToLast : False
onState : False
ownerProps : com.JohnBurgess.indigoplugin.TP-Link-Device : (dict)
     SlowDown :  (string)
     StopPoll :  (string)
     WarnInterval :  (string)
     address : 192.168.51.49 (string)
     addressSelect : manual (string)
     devPoll : false (bool)
     displayManAddress : true (bool)
     displayManAddressButton : true (bool)
     displayOk : false (bool)
     initialize : false (bool)
     manualAddressResponse : true (bool)
     newDev : false (bool)
     offPoll :  (string)
     onPoll :  (string)
pluginId : com.JohnBurgess.indigoplugin.TP-Link-Device
pluginProps : com.JohnBurgess.indigoplugin.TP-Link-Device : (dict)
     SlowDown :  (string)
     StopPoll :  (string)
     WarnInterval :  (string)
     address : 192.168.51.49 (string)
     addressSelect : manual (string)
     devPoll : false (bool)
     displayManAddress : true (bool)
     displayManAddressButton : true (bool)
     displayOk : false (bool)
     initialize : false (bool)
     manualAddressResponse : true (bool)
     newDev : false (bool)
     offPoll :  (string)
     onPoll :  (string)
protocol : Plugin
redLevel : None
remoteDisplay : True
sharedProps : com.indigodomo.indigoserver : (dict)
states : States : (dict)
     alias :  (string)
     brightnessLevel : 0 (integer)
     doubleClick : 0 (integer)
     fadeOffTime : 0 (integer)
     fadeOnTime : 0 (integer)
     gentleOffTime : 0 (integer)
     gentleOnTime : 0 (integer)
     hardOn : 0 (integer)
     longPress : 0 (integer)
     minThreshold : 0 (integer)
     onOffState : off (on/off bool)
     rampRate : 0 (integer)
     rssi : 0 (integer)
     softOn : 0 (integer)
subModel : 
subType : 
supportsAllLightsOnOff : False
supportsAllOff : False
supportsColor : False
supportsOnState : True
supportsRGB : False
supportsRGBandWhiteSimultaneously : False
supportsStatusRequest : True
supportsTwoWhiteLevels : False
supportsTwoWhiteLevelsSimultaneously : False
supportsWhite : False
supportsWhiteTemperature : False
version : None
whiteLevel : None
whiteLevel2 : None
whiteTemperature : None.
   TP-Link Devices                 (tplink_relayswitch_plugin.py:getDeviceStateList:85):  called for: States : (list)
     Item : (dict)
          Disabled : false (bool)
          Key : rssi (string)
          StateLabel : rssi (string)
          TriggerLabel : rssi (string)
          Type : 100 (integer)
     Item : (dict)
          Disabled : false (bool)
          Key : alias (string)
          StateLabel : alias (string)
          TriggerLabel : alias (string)
          Type : 150 (integer).
   TP-Link Devices                 (plugin.py:deviceStartComm:257): called for: new device 2@192.168.51.49.
   TP-Link Devices                 (plugin.py:getDeviceStateList:492): called for: 'new device 2'.
   TP-Link Devices                 (plugin_base.py:threaddebug:52):    dev: address : 192.168.51.49
batteryLevel : None
blueLevel : None
brightness : 0
buttonConfiguredCount : 0
buttonGroupCount : 0
configured : True
defaultBrightness : 100
description : 
deviceTypeId : tplinkSmartSwitch
displayStateId : brightnessLevel
displayStateImageSel : DimmerOff
displayStateValRaw : 0
displayStateValUi : 0
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState : 
folderId : 0
globalProps : MetaProps : (dict)
     com.JohnBurgess.indigoplugin.TP-Link-Device : (dict)
          SlowDown :  (string)
          StopPoll :  (string)
          WarnInterval :  (string)
          address : 192.168.51.49 (string)
          addressSelect : manual (string)
          devPoll : false (bool)
          displayManAddress : true (bool)
          displayManAddressButton : true (bool)
          displayOk : false (bool)
          initialize : false (bool)
          manualAddressResponse : true (bool)
          newDev : false (bool)
          offPoll :  (string)
          onPoll :  (string)
greenLevel : None
id : 1749274324
lastChanged : 2000-01-01 00:00:00
lastSuccessfulComm : 2000-01-01 00:00:00
ledStates : []
model : TP-Link Smart Dimmer Switch
name : new device 2
onBrightensToDefaultToggle : False
onBrightensToLast : False
onState : False
ownerProps : com.JohnBurgess.indigoplugin.TP-Link-Device : (dict)
     SlowDown :  (string)
     StopPoll :  (string)
     WarnInterval :  (string)
     address : 192.168.51.49 (string)
     addressSelect : manual (string)
     devPoll : false (bool)
     displayManAddress : true (bool)
     displayManAddressButton : true (bool)
     displayOk : false (bool)
     initialize : false (bool)
     manualAddressResponse : true (bool)
     newDev : false (bool)
     offPoll :  (string)
     onPoll :  (string)
pluginId : com.JohnBurgess.indigoplugin.TP-Link-Device
pluginProps : com.JohnBurgess.indigoplugin.TP-Link-Device : (dict)
     SlowDown :  (string)
     StopPoll :  (string)
     WarnInterval :  (string)
     address : 192.168.51.49 (string)
     addressSelect : manual (string)
     devPoll : false (bool)
     displayManAddress : true (bool)
     displayManAddressButton : true (bool)
     displayOk : false (bool)
     initialize : false (bool)
     manualAddressResponse : true (bool)
     newDev : false (bool)
     offPoll :  (string)
     onPoll :  (string)
protocol : Plugin
redLevel : None
remoteDisplay : True
sharedProps : com.indigodomo.indigoserver : (dict)
states : States : (dict)
     alias :  (string)
     brightnessLevel : 0 (integer)
     doubleClick : 0 (integer)
     fadeOffTime : 0 (integer)
     fadeOnTime : 0 (integer)
     gentleOffTime : 0 (integer)
     gentleOnTime : 0 (integer)
     hardOn : 0 (integer)
     longPress : 0 (integer)
     minThreshold : 0 (integer)
     onOffState : off (on/off bool)
     rampRate : 0 (integer)
     rssi : 0 (integer)
     softOn : 0 (integer)
subModel : 
subType : 
supportsAllLightsOnOff : False
supportsAllOff : False
supportsColor : False
supportsOnState : True
supportsRGB : False
supportsRGBandWhiteSimultaneously : False
supportsStatusRequest : True
supportsTwoWhiteLevels : False
supportsTwoWhiteLevelsSimultaneously : False
supportsWhite : False
supportsWhiteTemperature : False
version : None
whiteLevel : None
whiteLevel2 : None
whiteTemperature : None.
   TP-Link Devices                 (tplink_relayswitch_plugin.py:getDeviceStateList:85):  called for: States : (list)
     Item : (dict)
          Disabled : false (bool)
          Key : rssi (string)
          StateLabel : rssi (string)
          TriggerLabel : rssi (string)
          Type : 100 (integer)
     Item : (dict)
          Disabled : false (bool)
          Key : alias (string)
          StateLabel : alias (string)
          TriggerLabel : alias (string)
          Type : 150 (integer).
   TP-Link Devices                 (plugin_base.py:threaddebug:52): for attribute devPoll, using [False, 'dev']
   TP-Link Devices                 Polling thread is disabled for new device 2, 192.168.51.49.
And then if I try to turn on the switch we get

Code: Select all

Nov 4, 2024 at 3:26:32 PM
   TP-Link Devices                 (plugin.py:actionControlDevice:351): called with: TurnOn for new device 2.
   TP-Link Devices                 (plugin.py:getSubProtocol:176): called with tplink_relayswitch addr: 192.168.51.49
   TP-Link Devices                 (protocol.py:debugLog:222): addr=192.168.51.49, port=9999, isatty=False
   TP-Link Devices                 (protocol.py:debugLog:222): Sent:  {"system":{"set_relay_state":{"state":1}},"smartlife.iot.dimmer": {"set_brightness": {"brightness": 100}}} == on
   TP-Link Devices                 (plugin.py:actionControlDevice:395): send(on) result: {'error': 'python error \'[Errno 61] Connection refused\' from command {"system":{"set_relay_state":{"state":1}},"smartlife.iot.dimmer": {"set_brightness": {"brightness": 100}}}'}
   TP-Link Devices Error           (plugin.py:actionControlDevice:413): send "new device 2" "on"" failed with result "{"error": "python error '[Errno 61] Connection refused' from command {\"system\":{\"set_relay_state\":{\"state\":1}},\"smartlife.iot.dimmer\": {\"set_brightness\": {\"brightness\": 100}}}"}"
What have I broken ;-)
Top
timrowledge
Posts: 46
Joined: Sat May 14, 2011 10:51 am

Re: TP-Link Plugin v 0.9.9 / v1.0

Post by timrowledge »

Oh, as an extra - if I use the test Python app, I Get

Code: Select all

Amtiskaw:TP-Link-Device.indigoPlugin tim$ python ./tplink_test.py  -t 192.168.51.49 -c info
addr=None, port=None, isatty=True
Connection to 192.168.51.49 on port 9999 failed: [Errno 61] Connection refused
unknown device type: False
Amtiskaw:TP-Link-Device.indigoPlugin tim$ python ./tplink_test.py  -t 192.168.51.49 -c on
addr=None, port=None, isatty=True
Connection to 192.168.51.49 on port 9999 failed: [Errno 61] Connection refused
unknown device type: False
I am not a Python programmer (Smalltalk is my thing)
Top
pgershon
Posts: 516
Joined: Sat Jul 10, 2004 1:07 am

Re: TP-Link Plugin v 0.9.9 / v1.0

Post by pgershon »

Do you have it working? I use this plugin rather extensively with about 40 TP-link HS200 and HS220 devices (probably more). It is not without its issues, but I have worked with it for several years now. Let me know if I can help you.
Top
pgershon
Posts: 516
Joined: Sat Jul 10, 2004 1:07 am

Re: TP-Link Plugin v 0.9.9 / v1.0

Post by pgershon »

Looking for some general help here and I have posted a variation of this also in the a more general thread on Indigo forum.

I use the TP-Link plug-in to control 40+ Kasa devices (generally HS200 and HS220 dimmers and switches). The plug-in works great, with one exception. My devices periodically seem to lose their communication with the network, then get it back. Not normally as issue as the TP-Link plugin polls the devices and keeps track of consecutive failures to communicate. The problem is that periodically devices get deactivated and need to be (1) notices and then (2) manually re-activated in the console. Obviously the best solution would be to identify why the devices go on and off line and rectify the problem, but I suspect it is simply the general behavior of devices and wifi access point in multiple locations of a large house competing with one another (RSSI is very strong on all devices normally). I have been trying to nail this down for years now and have given up.

Absent a global solution to eliminate the problem, the next best thing would be to write a script that would poll all TP-Link devices that are deactivated (comm field set to off) and activate them. I imagine what I want to do is scan all devices where indigo.device.enable(dev.id, value=False) and reset the field value to true for them. I could then run this routine every 30 minutes or so so fix most of my issues. Unfortunately my programing skills in Python are limited so any help /suggestions would be most appreciated. I believe this is a relatively simple process to do.

Thanks in advance... I will play around with the existing code to see if I can come up with something too.

This is an example of the error messages that frequently come up. In the case below there were only a few polling errors for each device so nothing was deactivated. In the second example, the device was deactivate, even though 10 minutes later (or less) the device would be fully operational once it is reactivate.

Code: Select all

Nov 9, 2024 at 5:18:05 PM
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Basement Top
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Dining Room Chandelier
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Pool House Outside
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Master Bath Overhead
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Powder Room Overhead
   TP-Link Devices                 2 timeouts - Normal polling resuming for device TV Room Lights
   TP-Link Devices                 2 timeouts - Normal polling resuming for device master bedroom lights
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Guest Hall
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Garage inside
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Kitchen Overhead #2
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Rear Patio Lights #4
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Dining Room Sconces
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Back Porch Lights Garage
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Side Entry Hanging
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Kitchen Overhead #1
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Basement Playroom Back 
   TP-Link Devices                 2 timeouts - Normal polling resuming for device guest bedroom back
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Back Porch Lights Main
   TP-Link Devices                 2 timeouts - Normal polling resuming for device TV Room Sconce
   TP-Link Devices                 2 timeouts - Normal polling resuming for device kitchen Hanging
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Living Room Hall
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Basement Exercise Room1
   TP-Link Devices                 2 timeouts - Normal polling resuming for device guest bedroom front
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Basement Lower Stairs
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Living Room Sconce
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Basement Exercise Room Back
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Kitchen Foyer
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Foyer Sconce
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Master Bath Mirror

Code: Select all

   TP-Link Devices                 5 timeouts - Normal polling resuming for device Basement Water Pump Room
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Dining Room Sconces
   TP-Link Devices                 5 timeouts - Normal polling resuming for device Basement Bath Shower
   TP-Link Devices                 5 timeouts - Normal polling resuming for device basement top pair
   TP-Link Devices                 5 timeouts - Normal polling resuming for device Kitchen Overhead #2 - S1 on/off
   TP-Link Devices                 5 timeouts - Normal polling resuming for device basement Lower Stairs Pair1
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 10 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 2
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 20 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 3
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 30 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 4
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 40 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 5
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 50 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 6
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 60 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 7
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 70 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 8
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 80 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 9
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 90 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 10
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 100 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 11
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 110 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 12
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 120 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 13
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 130 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 14
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 140 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 15
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 150 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 16
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 160 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 17
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 170 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 18
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 180 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 19
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 190 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 20
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 200 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 21
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 210 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 22
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 220 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 23
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 230 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 24
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 240 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 25
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 250 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 26
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 260 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 27
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 270 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 28
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 280 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 29
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 290 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 30
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 300 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 31
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 310 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 32
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 320 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 33
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 330 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 34
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 340 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 35
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 350 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 36
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 360 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 37
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 370 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 38
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 380 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 39
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 390 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 40
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 400 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 41
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 410 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 42
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 420 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 43
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 430 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 44
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 440 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 45
   TP-Link Devices                 2 timeouts - Normal polling resuming for device Basement Top
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 450 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 46
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 460 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 47
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 470 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 48
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 480 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 49
   TP-Link Devices Error           (tpl_relay_poll.py:run:119): 490 consecutive polling errors for device Guest Bathroom Overhead: error python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}}. Polling internal now 50
   TP-Link Devices Error           (tpl_relay_poll.py:run:113): Unable to poll device "Guest Bathroom Overhead": python error '[Errno 64] Host is down' from command {"system":{"get_sysinfo":{}}} after 500 errors. Polling for this device will now shut down.
   TP-Link Devices                 Polling stopped for Guest Bathroom Overhead@192.168.1.197.
Top
timrowledge
Posts: 46
Joined: Sat May 14, 2011 10:51 am

Re: TP-Link Plugin v 0.9.9 / v1.0

Post by timrowledge »

pgershon wrote: ↑Sat Nov 09, 2024 4:47 pm Do you have it working?
Sadly not; no change since my problem messages.

I'm not sure what I should do for initial setup of the HS200; was using the Kasa app correct? I s there any other action I should take? It works perfectly well from the iphone app to turn on/off but I get just that refusal to connect from the indigo+plugin end. Is there anything approaching actual documentation that I failed to spot?
Top
pgershon
Posts: 516
Joined: Sat Jul 10, 2004 1:07 am

Re: TP-Link Plugin v 0.9.9 / v1.0

Post by pgershon »

I will try to help you here. I have nearly 100 HS-200's and HS-220's working well with Indigo for several years so I know the plugin works, and works well. Quick disclaimer, I made a few "minor" edit's to John's version to get it to work here and he and I have tried to keep in sync but it's often tough. I do nto think John (developer) has HS-200 and 220 units to try.

First thing I noticed as I read your posts. The HS-200 is an on/off relay - not a dimmer. So when you go to set up in Indigo, you need to select product type and you want the TP-LInk smart plug as opposed to the dimmer switch. That should give you some variation of the attached screenshot.

Let me know if this helps and we can try other steps if you think we are on the right track. I do vouch for the software.
Attachments
Screenshot 2024-11-14 at 10.51.00 PM.png
Screenshot 2024-11-14 at 10.51.00 PM.png (479.87 KiB) Viewed 228 times
Top
Post Reply

Return to “User Plugins”