-
-
Notifications
You must be signed in to change notification settings - Fork 238
Add door lock fixture #1434
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Add door lock fixture #1434
Conversation
|
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. |
|
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). |
|
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? |
|
I believed they fixed it because I was able to get one working after that
date..
…On Tue, Apr 15, 2025, 8:08 AM Marcelo Balloni ***@***.***> wrote:
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).
—
Reply to this email directly, view it on GitHub
<#1434 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOSMGXZF5Z72C3X3RYHRJ532ZUAGDAVCNFSM6AAAAABU27DW5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBVGAYDGMBRG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
*mballoni* left a comment (python-kasa/python-kasa#1434)
<#1434 (comment)>
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).
—
Reply to this email directly, view it on GitHub
<#1434 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOSMGXZF5Z72C3X3RYHRJ532ZUAGDAVCNFSM6AAAAABU27DW5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBVGAYDGMBRG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Quick question: once implemented does it mean it could work locally or does it still needs tplink cloud to communicate? (excluding setup ) |
|
I'm not using tp-link cloud. I just added the device to smartthings and it
works in HA through the smart things plugin.
…On Fri, May 16, 2025, 9:18 AM Marcelo Balloni ***@***.***> wrote:
*mballoni* left a comment (python-kasa/python-kasa#1434)
<#1434 (comment)>
Quick question: once implemented does it mean it could work locally or
does it still needs tplink cloud to communicate? (excluding setup )
—
Reply to this email directly, view it on GitHub
<#1434 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOSMGX2DH3BSLTTJPDAQKUD26XXUHAVCNFSM6AAAAABU27DW5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBWHA2TMOBSGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
@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. |
|
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. |
|
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. |
|
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 ! |
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! |
|
@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? |
|
@rytilahti just validated that the Tapo app works on macos (m2). |
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. |
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