Kasa Switches Not Discovered

[gklimo]

Would appreciate some guidance on the following. Thanks in advance,

I recently purchased and installed the TP-Link Kasa Node Server on my eisy. I'm running the current 3.1.4 version. My eisy is running IoX Version 5.9.1 with PG3x Version 3.3.18.

Unfortunately, the Kasa Node Server is not discovering any of my Kasa switches. I currently have two Kasa HS220 switches that are Hardware Version 3.26 and Firmware Version 1.1.1. I also currently have two Kasa HS200 switches that are Hardware Version 5.26 and Firmware Version 1.0.3. 

These switches work from other resources on my network. They work fine from the Kasa app and also work fine from within Home Assistant.

Since Discovery was not finding the switches, I performed the following steps without success.

• Assigned a static IP address to each Kasa switch.
• Increased the discover_timeout significantly.
• Installed the eisy Development Packages via the Admin Console (as mentioned by some).
• Manually added each switch IP into the Node Server Configuration section. 
• Stopped and restarted the Node Server numerous times.
• Exited and relaunched the Admin Console numerous times.
• Invoked Reinstall all Plugins from within PG3x.
• Rebooted the eisy.

Unfortunately, the eisy Admin Console still only shows the Kasa Controller node. No switches appear. The Kasa Node Server also reports only one node (Kasa Controller) with NodeServer Online within PG3x. Since the Kasa HS220 (US) is listed as supported, I hoped to see at least that switch model appear.

After attempting to manually define each switch IP (since discovery was not finding them), the logs observed indicate "Unsupported device" as follows.

Any suggestions on how to get things to work?

Line  5499: 2025-05-13 07:22:53.398 Thread-10 (run_forever) udi_interface      ERROR    Controller:_add_manual_devices: Unsupported device 192.168.1.231: {'result': {'device_id': '2072eb696f928b3b0209fd2439cfb420', 'owner': 'D0B6B8020FB760512729A714F99DBD1E', 'device_type': 'SMART.KASASWITCH', 'device_model': 'HS220(US)', 'ip': '192.168.1.231', 'mac': '8C-90-2D-80-9F-FC', 'is_support_iot_cloud': True, 'obd_src': 'tplink', 'protocol_version': 1, 'factory_default': False, 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'KLAP', 'http_port': 80, 'lv': 2}}, 'error_code': 0} trying to connect to 192.168.1.231
    Line  5501: 2025-05-13 07:22:53.416 Thread-10 (run_forever) udi_interface      ERROR    Controller:_add_manual_devices: Unsupported device 192.168.1.241: {'result': {'device_id': '6eb0794588d4ee5eb5f0e3c050b15789', 'owner': 'D0B6B8020FB760512729A714F99DBD1E', 'device_type': 'SMART.KASASWITCH', 'device_model': 'HS200(US)', 'ip': '192.168.1.241', 'mac': 'DC-62-79-9A-27-F2', 'is_support_iot_cloud': True, 'obd_src': 'tplink', 'protocol_version': 1, 'factory_default': False, 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'KLAP', 'http_port': 80, 'lv': 2}}, 'error_code': 0} trying to connect to 192.168.1.241
    Line  5503: 2025-05-13 07:22:53.424 Thread-10 (run_forever) udi_interface      ERROR    Controller:_add_manual_devices: Unsupported device 192.168.1.210: {'result': {'device_id': '29fa577f06cfa6d09781e25548b35471', 'owner': 'D0B6B8020FB760512729A714F99DBD1E', 'device_type': 'SMART.KASASWITCH', 'device_model': 'HS220(US)', 'ip': '192.168.1.210', 'mac': '8C-90-2D-80-A7-A0', 'is_support_iot_cloud': True, 'obd_src': 'tplink', 'protocol_version': 1, 'factory_default': False, 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'KLAP', 'http_port': 80, 'lv': 2}}, 'error_code': 0} trying to connect to 192.168.1.210
    Line  5505: 2025-05-13 07:22:53.432 Thread-10 (run_forever) udi_interface      ERROR    Controller:_add_manual_devices: Unsupported device 192.168.1.220: {'result': {'device_id': '177b54ce12e07e4380c01f455eac6cd5', 'owner': 'D0B6B8020FB760512729A714F99DBD1E', 'device_type': 'SMART.KASASWITCH', 'device_model': 'HS200(US)', 'ip': '192.168.1.220', 'mac': 'DC-62-79-9A-11-9F', 'is_support_iot_cloud': True, 'obd_src': 'tplink', 'protocol_version': 1, 'factory_default': False, 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'KLAP', 'http_port': 80, 'lv': 2}}, 'error_code': 0} trying to connect to 192.168.1.220

[atmarosi]

According to the python library that the PG node uses - this model + FW combo you have (HS200  HW 5.26/FW 1.0.3) requires auth....

You may need to do something extra in the config of the device/node server to get it to talk to it...seems like this post has mentioned a beta version that might fix it:

 

 

[gklimo]

RESOLVED

I switched to the Non-production Store within the PG3x Plugin Store and installed the 3.2.4 / Standard [Beta] version of the Kasa Node Server to the same slot previously used. 

The Key section within the Node Server Custom Configuration Parameters then offered the following entries.

user 

password

I entered my Kasa account username (case sensitive) as the user Key Value and my Kasa account password (case sensitive) as the password Key Value. 

I restarted the Kasa Node Server and relaunched the Admin Console after giving the Node Server a chance to discover the Kasa devices.

All of my Kasa HS220 and HS200 switches were successfully found. They now appear in my eisy Admin Console node list and can be controlled.
 

Edited 9 hours ago by gklimo

[Ross]

I've had issues with this nodeserver.  I've paid my $30 twice, but I still get a "subscription has expired" notice.

I downloaded the non-production 3.2.4 as you've done.  My Custom Configuration Parameters were: change_node_names, discover_timeout and auto_discover.  User and Password weren't the options.  So, I added them.  

Unfortunately, it still shows as disconnected.

[gklimo]

Sorry to hear my outcome didn't work in your situation. Possibly one of the bulleted items listed in my original post at the top of this thread allowed mine to work. For example, my installing the Development Packages via the Admin Console might be related.

Unfortunately, I've since discovered I can only turn my dimmable Kasa HS220 switches on and off from within my eisy. Kasa dimming control doesn't seem to work using the Kasa Beta Node Server. Hopefully that gets resolved. 

However, full Kasa switch control works just fine from within Home Assistant, including dimming. As a result, I'll use native Home Assistant Automations for my Kasa devices and continue to use eisy Network Resources to externally control Home Assistant via its API as needed. The majority of my environment is Insteon based, which has been rock solid. As a result, I've been a long time ISY then Polisy and now eisy user.

Best of luck. I hope to see an update with some success.