Skip to content

Conversation

@steveredden
Copy link
Contributor

@steveredden steveredden commented Jan 8, 2025

With KASA_USERNAME and KASA_PASSWORD set as env vars:

python -m devtools.dump_devinfo --host a.b.c.d --port 80 --encrypt-type KLAP

@adamckbatchelor
Copy link

Hi, have there been any updates on this? I have one of these locks so if there is anyway I can support the python-kasa integration, let me know.

@rytilahti
Copy link
Member

Someone needs to figure out the commands that are implemented in those lock-relevant modules & implement the modules.

If someone wants to contribute, I'm happy to help with reviewing code (and maybe with the implementation, after the commands and required payloads are known).

@bigsteve76
Copy link

FYI - these DL110 were usable via Smartthings until January 1, 2025 when Samsung changed their API to only be valid for 24 hours. I had two flawlessly working with the Smartthings integration in HA for about 6 months until Samsung borked it.

@mballoni
Copy link

FYI - these DL110 were usable via Smartthings until January 1, 2025 when Samsung changed their API to only be valid for 24 hours. I had two flawlessly working with the Smartthings integration in HA for about 6 months until Samsung borked it.

Is it still the case?
There is a new integration and I still control some devices with SmartThings (ACs and TVs).

@bigsteve76
Copy link

bigsteve76 commented Apr 15, 2025 via email

@mballoni
Copy link

Quick question: once implemented does it mean it could work locally or does it still needs tplink cloud to communicate? (excluding setup )

@bigsteve76
Copy link

bigsteve76 commented May 16, 2025 via email

@rytilahti
Copy link
Member

rytilahti commented May 21, 2025

@mballoni all devices supported by this library use local communications. So as soon as someone figures out the commands this device uses, it should be controllable locally. That is, assuming there is nothing special and different compared to other devices that use this local protocol.

Alas, as far as I know no one is actively looking into reverse engineering this at the moment.

@github-actions
Copy link

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
If you are the author of this PR, please leave a comment if you want to keep it open. Also, please rebase your PR onto the latest dev branch to ensure that it's up to date with the latest changes.
Thank you for your contribution!

@github-actions github-actions bot added the stale label Aug 20, 2025
@ZeliardM
Copy link
Contributor

I had a user with another older iot device for my Homebridge plug-in use a Mac computer with the Tapo/Kasa App installed using Wireshark to find the commands. If someone has a Mac that they can install the Tapo/Kasa App and Wireshark, they could use the App to send commands to the door lock and then find them in Wireshark and paste them here. Would be able to use those commands to help build a module for the door locks.

@github-actions github-actions bot removed the stale label Aug 24, 2025
@YazidJA
Copy link

YazidJA commented Aug 31, 2025

For those who made it work with Smarthings, can you please confirm if it's still working and what entities are exposed? A screenshot of the entities would also be appreciated, TIA !

@wantstoautomate
Copy link

I had a user with another older iot device for my Homebridge plug-in use a Mac computer with the Tapo/Kasa App installed using Wireshark to find the commands. If someone has a Mac that they can install the Tapo/Kasa App and Wireshark, they could use the App to send commands to the door lock and then find them in Wireshark and paste them here. Would be able to use those commands to help build a module for the door locks.

I take it that you're using the homekit protocol for devices that don't have homekit (as this doesn't come with it). If I could grab one and from a linux PC use an android emulator + wireshark would this maybe work? Haven't done this kind of thing before but would be sweet to get this locally integrated!

@ZeliardM
Copy link
Contributor

ZeliardM commented Oct 5, 2025

@wantstoautomate I believe using an Android Emulator and the APK would work as well with Wireshark. You need to be able to get the commands themselves so we would be able to program the commands into the api for control. Anything that you want to do with the api you need to capture, lock, unlock? Not sure what else you can do with the locks in the app, if they have different sensors?

@mballoni
Copy link

@rytilahti just validated that the Tapo app works on macos (m2).
If everything works as expected I should acquired a DL110 soon and will try to reverse engineer its commands.
Wish me luck! Just captured a few packages from tapo app, although I have no idea how to handle that right now but I'll figure it out eventually. Any tips?

@psilves1
Copy link

@wantstoautomate I believe using an Android Emulator and the APK would work as well with Wireshark. You need to be able to get the commands themselves so we would be able to program the commands into the api for control. Anything that you want to do with the api you need to capture, lock, unlock? Not sure what else you can do with the locks in the app, if they have different sensors?

You can create/modify pins, create temporary one time pins, add/remove fingerprints, etc.

Realistically I think most people are using this to automate locking/unlocking locally so maybe it would be best to start there as an MVP, then look at adding those other commands in the future? I'm not sure the level of effort/feasibility of adding some of those more complex commands.

If nobody can get those payloads, I may be able to help in a few weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants