Add door lock fixture #1434
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. |
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