core
core copied to clipboard
TP link AES KASAHUB issue
The problem
I want to use the tp link integration but I will get the error
unsupported device found at 192.168.0.161 << Unsupported device 192.168.0.161 of type SMART.KASAHUB with encrypt_type AES
I am Not really Sure what exactly the Problem is. The hub is working correctly the whole time in the kasa or tapo App .
What version of Home Assistant Core has the issue?
core-2024.5.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Tp Link
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tplink
Diagnostics information
Unsupported device 192.168.0.161 of type SMART.KASAHUB with encrypt_type AES
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @rytilahti, @thegardenmonkey, @bdraco, @sdb9696, mind taking a look at this issue as it has been labeled with an integration (tplink
) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of tplink
can trigger bot actions by commenting:
-
@home-assistant close
Closes the issue. -
@home-assistant rename Awesome new title
Renames the issue. -
@home-assistant reopen
Reopen the issue. -
@home-assistant unassign tplink
Removes the current integration label and assignees on the issue, add the integration domain after the command. -
@home-assistant add-label needs-more-information
Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. -
@home-assistant remove-label needs-more-information
Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
tplink documentation tplink source (message by IssueLinks)
The Kasa Hubs are not supported in the current version of the integration:
https://www.home-assistant.io/integrations/tplink/#supported-devices
They should be supported in the next HA release but please check the documentation when it ships to make sure.
@home-assistant close