This is just a hobby project by some volunteers who wanted to control some tplink devices in the past, so there is no real "plan" here.
That being said, if the devices are discoverable using the kasa command line tool and are speaking the same protocol, it might be fairly straightforward to add support for those with some help. Did you already try to use the kasa tool?
if they use a different low-level communication protocol (zigbee instead of wifi?), then it's out of the scope for this project.
The KP125M does not expose port 9999 like the other devices supported by this project. A Nmap of one of my KP125M's shows only port 80 exposed, so it might only be saving the energy monitoring to the Kasa cloud, not exposed locally. I have a ticket open with TP-Link because Sense seems to be using a process similar to this project on its monitoring device, and it can't detect the KP125M.
The KP125M uses the same protocol as the Tapo Devices from one week ago. I have built and tested on Hubitat Environment using Groovy. 20003 UDP Poll signatures at the mgt_encrypt_scheme
new KLAP handshake, encryption: 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'KLAP', 'http_port': 80, 'lv': 2} Legacy Tapo handshake, encryption: 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'AES', 'http_port': 80, 'lv': 2}' Legacy Kasa (XOR) devices: NOT DISCOVERED Tapo RoboVac (another case): mgt_encrypt_schm:[is_support_https:true, encrypt_type:AES, http_port:4433]
Note: I fear that all newer Tapo devices, the Kasa Matter devices, and the Kasa Hub are all going to go to KLAP in near-term releases.
See the linked PRs for adding support for discovering these devices as well as support for the klap protocol, #499 contains a draft PR to add support for tapo plugs using an external library.
Activity
rytilahti commented on Apr 16, 2023
This is just a hobby project by some volunteers who wanted to control some tplink devices in the past, so there is no real "plan" here.
That being said, if the devices are discoverable using the kasa command line tool and are speaking the same protocol, it might be fairly straightforward to add support for those with some help. Did you already try to use the kasa tool?
if they use a different low-level communication protocol (zigbee instead of wifi?), then it's out of the scope for this project.
kb1ibt commented on May 4, 2023
The KP125M does not expose port 9999 like the other devices supported by this project. A Nmap of one of my KP125M's shows only port 80 exposed, so it might only be saving the energy monitoring to the Kasa cloud, not exposed locally. I have a ticket open with TP-Link because Sense seems to be using a process similar to this project on its monitoring device, and it can't detect the KP125M.
kb1ibt commented on May 6, 2023
After more searching around this project it looks like KP125M uses a similar firmware as #115 since I didn’t notice UDP 20002 was also open.
DaveGut commented on Aug 26, 2023
The KP125M uses the same protocol as the Tapo Devices from one week ago. I have built and tested on Hubitat Environment using Groovy. 20003 UDP Poll signatures at the mgt_encrypt_scheme
new KLAP handshake, encryption: 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'KLAP', 'http_port': 80, 'lv': 2}
Legacy Tapo handshake, encryption: 'mgt_encrypt_schm': {'is_support_https': False, 'encrypt_type': 'AES', 'http_port': 80, 'lv': 2}'
Legacy Kasa (XOR) devices: NOT DISCOVERED
Tapo RoboVac (another case): mgt_encrypt_schm:[is_support_https:true, encrypt_type:AES, http_port:4433]
Note: I fear that all newer Tapo devices, the Kasa Matter devices, and the Kasa Hub are all going to go to KLAP in near-term releases.
rytilahti commented on Aug 26, 2023
See the linked PRs for adding support for discovering these devices as well as support for the klap protocol, #499 contains a draft PR to add support for tapo plugs using an external library.
DaveGut commented on Aug 26, 2023
understood. My job will be to convert to Groovy using the white-listed Hubitat Environment Protocols.
rytilahti commented on Nov 28, 2023
#509 and #552 are related to this issue.
rytilahti commented on Dec 3, 2023
The tapo plugs can now be controlled thanks to #509, and #560 added support for emeter readings.