Skip to content
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

Kasa devices leaking through via skills (1/2 bug report, 1/2 feature request) #2637

Open
Abba- opened this issue Oct 20, 2024 · 5 comments
Open
Labels
bug Something isn't working enhancement New feature or request todo 🗒️

Comments

@Abba-
Copy link

Abba- commented Oct 20, 2024

IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.

Describe the bug

According to the documentation “It will NOT add smart devices connected to Alexa via Skills.”
However, some Kasa devices do show up and are controllable. (Personally this is a feature!!, not a bug).

I have ~7 devices (outdoor dual plug, dual outlet, individual plugs). I had 1 individual plug leak through.
After enabling advanced debugging and parsing the list of "Found unsupported device" the first difference I noticed was I had set the type of plug in Alexa (i.e. customerDefinedDeviceType) for the working switch. After manually picking that, the remaining smart plugs populated!

Further comparing to the dual devices that didnt appear, they return an additional key ('parent.deviceId) that isnt in the smart plug's output:

.......'softwareVersion': '1.0.1 Build 201109 Rel.150108', 'parent.deviceId': '8006E83A21DA6FC8F54924152D8F63C920XXXXXX'}}, 'firmwareVersion'......

Presumably that key is what's preventing this from working.
To be clear, its a bug report in the sense that it goes against the documentation, but this would be an amazing feature to have, even if not fully supported!

To Reproduce
Link some Kasa smart plugs and/or other devices to Alexa.
Set device type in Alexa
Smart plugs show in HA, Dual devices don't.

Expected behavior

According to the documentation, Kasa devices shouldn't show up.
However, I would humbly prefer this behavior be extended! Not eradicated!

Screenshots

System details

  • Home Assistant version: 2024.10.3
  • alexa_media version (from const.py or HA startup log): 4.13.5
  • alexapy version (from pip show alexapy in homeasssistant container or HA startup log): 1.29.3
  • Is Amazon 2FA/2SV enabled <!---We will not debug login issues if unanswered---> (y/n): y
  • Amazon Domain: .com

Debug Logs (alexa_media & alexapy)
Please provide logs.

Happy to provide whatever section as requested, too much censoring needed to paste everything.

Additional context

Copy link

The issue has received no activity for 60 days and will be closed in a week.

@danielbrunt57 danielbrunt57 added bug Something isn't working enhancement New feature or request help wanted Extra attention is needed todo 🗒️ and removed no-issue-activity labels Dec 20, 2024
@danielbrunt57
Copy link
Collaborator

Do you have the TP-Link Smart Home integration installed?
It should add the devices locally into HA for you.

@Abba-
Copy link
Author

Abba- commented Dec 20, 2024

Yes I used it for other installs. The use case here is for a few remote plugs that are on a different network/location and it's impractical to link the networks.

@github-actions github-actions bot removed the help wanted Extra attention is needed label Dec 21, 2024
@danielbrunt57
Copy link
Collaborator

Got it. Have to see if I can borrow the dual plug outdoor from my gf that I installed for her for patio fountain but serves double duty for Christmas lighting. Could be a couple weeks before I can test...

@Abba-
Copy link
Author

Abba- commented Dec 22, 2024

No rush, Thanks (I waited long enough lol)

Definitely don't risk ruining Christmas automations for this 🙃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request todo 🗒️
Projects
None yet
Development

No branches or pull requests

2 participants