Support of Kasa EP25 and others requiring authentication

[Andy P]

Hi, hoping to use this plugin with my Kasa EP25 devices. According to the Github info, it is the intent to support any devices in the python-kasa library. That library lists the EP25 but with an asterisk saying new devices need authentication. Do you plan to support that? Currently it just responds with 

ERROR Controller:_add_manual_devices: Unsupported device 192.168.3.118:

Thanks, Andy

[KSP1138]

Also getting "Unsupported device" with a new HS220 I tried to add today (hardware version 3.26, firmware 1.1.1).  No issues with older HS220's running 3.0/1.0.11.

[btreinders]

Any news here?  I have a new HS220 3.26 hardware version and firmware 1.1.1 and it is not being discovered either.  Is the Home Assistant integration from TP-Link itself?  Or is it unofficial like this plugin?  I ask because this new device does work in HA.

Edited November 16, 2024 by btreinders

[btreinders]

So I bought some HS200 switches hardware version 5.26 and firmware 1.0.1 and I did not let it update and it isn't being discovered either.  I tried putting in the IP as well.  Appreciate any answers.

[Jimbo.Automates]

Please try Beta version mentioned here: 

 

and post in that thread if you have issues once it can be installed.

 

[Andy P]

I installed 3.2.24. The node server created a node which is visible in the admin console and shows connected.

No devices were discovered. I added a secondary discover network broadcast address for the IOT network (which I can ping no problem - no blocking). Still no discovery. I manually added the IP address of a kasa EP25. Restarted everything including rebooting the EISY. Still no device. Turned on debug logging. Did not expect anything on the 3.* network, the devices are on the 11.* network - and the manual discovery got an "unexpected keyword argument 'address' trying to connect"

2025-01-11 06:48:10.377 Thread-9 (handler_start) udi_interface INFO Controller:discover: enter: 192.168.3.255
2025-01-11 06:48:10.377 Thread-10 (run_forever) udi_interface DEBUG Controller:_discover: enter: target=192.168.3.255
2025-01-11 06:48:10.378 Thread-10 (run_forever) kasa.discover DEBUG discover:do_discover: [DISCOVERY] 192.168.3.255 >> {'system': {'get_sysinfo': {}}}
2025-01-11 06:48:10.516 Thread-10 (run_forever) kasa.discover DEBUG discover:discover: Waiting 5 seconds for responses...
2025-01-11 06:48:15.566 Thread-10 (run_forever) kasa.discover DEBUG discover:discover: Discovered 0 devices
2025-01-11 06:48:15.566 Thread-10 (run_forever) udi_interface INFO Controller:_discover: Discover.discover(192.168.3.255) done: checking for previously known devices
2025-01-11 06:48:15.566 Thread-10 (run_forever) udi_interface DEBUG Controller:_discover: exit
2025-01-11 06:48:15.566 Thread-9 (handler_start) udi_interface DEBUG Controller:discover: result=None
2025-01-11 06:48:15.567 Thread-9 (handler_start) udi_interface INFO Controller:discover: calling: _discover(target=192.168.11.255)
2025-01-11 06:48:15.567 Thread-10 (run_forever) udi_interface DEBUG Controller:_discover: enter: target=192.168.11.255
2025-01-11 06:48:15.567 Thread-10 (run_forever) kasa.discover DEBUG discover:do_discover: [DISCOVERY] 192.168.11.255 >> {'system': {'get_sysinfo': {}}}
2025-01-11 06:48:15.568 Thread-10 (run_forever) kasa.discover DEBUG discover:discover: Waiting 5 seconds for responses...
2025-01-11 06:48:20.619 Thread-10 (run_forever) kasa.discover DEBUG discover:discover: Discovered 0 devices
2025-01-11 06:48:20.619 Thread-10 (run_forever) udi_interface INFO Controller:_discover: Discover.discover(192.168.11.255) done: checking for previously known devices
2025-01-11 06:48:20.619 Thread-10 (run_forever) udi_interface DEBUG Controller:_discover: exit
2025-01-11 06:48:20.619 Thread-9 (handler_start) udi_interface DEBUG Controller:discover: result=None
2025-01-11 06:48:20.619 Thread-9 (handler_start) udi_interface INFO Controller:discover: exit
2025-01-11 06:48:20.620 Thread-10 (run_forever) udi_interface INFO Controller:_add_manual_devices: Adding manual device 192.168.11.175
2025-01-11 06:48:20.620 Thread-10 (run_forever) udi_interface ERROR Controller:_add_manual_devices: Controller.discover_single() got an unexpected keyword argument 'address' trying to connect to 192.168.11.175
2025-01-11 06:48:20.620 Thread-10 (run_forever) udi_interface INFO Controller:_add_manual_devices: Adding manual device 192.168.11.179
2025-01-11 06:48:20.620 Thread-10 (run_forever) udi_interface ERROR Controller:_add_manual_devices: Controller.discover_single() got an unexpected keyword argument 'address' trying to connect to 192.168.11.179
2025-01-11 06:48:20.620 Thread-9 (handler_start) udi_interface DEBUG Controller:add_manual_devices: result=None
2025-01-11 06:48:20.620 Thread-9 (handler_start) udi_interface INFO Controller:add_manual_devices: exit
2025-01-11 06:48:20.620 Thread-9 (handler_start) udi_interface INFO Controller:handler_start: exit Kasa Controller

 

Edited January 11 by Jimbo.Automates

[Jimbo.Automates]

5 hours ago, Andy P said:

I installed 3.2.24. The node server created a node which is visible in the admin console and shows connected.

No devices were discovered. I added a secondary discover network broadcast address for the IOT network (which I can ping no problem - no blocking). 

Discovery does not use ping, it sends UDP packets, which do not cross subnet boundaries.  There is a discussion about this on the python-kasa issues https://github.com/python-kasa/python-kasa/issues/1431

5 hours ago, Andy P said:

I manually added the IP address of a kasa EP25. Restarted everything including rebooting the EISY. Still no device. Turned on debug logging. Did not expect anything on the 3.* network, the devices are on the 11.* network - and the manual discovery got an "unexpected keyword argument 'address' trying to connect"

I'll look into that error.  Issue created https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/23