FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

KP 125M / support for matter devices · Issue #450 · python-kasa/python-kasa · GitHub

Repository navigation

KP 125M / support for matter devices #450

Closed

Description

Are there any plans to add support for the new KP 125M models?

I understand these are Matter capable devices, but they should support conventional connections as well.

I'd like to add some new automations into home assistant, but I can't on my newer KP125M devices.

Activity

  1. rytilahti commented on Apr 16, 2023

    Member

    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.

  2. 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.

  3. 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.

  4. changed the title [-]KP 125M Support[/-] [+]KP 125M / support for matter devices[/+] on Jul 6, 2023
  5. pinned this issue on Jul 6, 2023
  6. 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.

  7. rytilahti commented on Aug 26, 2023

    Member

    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.

  8. DaveGut commented on Aug 26, 2023

    understood. My job will be to convert to Groovy using the white-listed Hubitat Environment Protocols.

  9. rytilahti commented on Nov 28, 2023

    Member

    #509 and #552 are related to this issue.

  10. rytilahti commented on Dec 3, 2023

    Member

    The tapo plugs can now be controlled thanks to #509, and #560 added support for emeter readings.

  11. unpinned this issue on Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL