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

TPLink/Tapo L530E bulbs not adding to HA after Discovery #135219

Open
OrangeGitHubber opened this issue Jan 9, 2025 · 2 comments
Open

TPLink/Tapo L530E bulbs not adding to HA after Discovery #135219

OrangeGitHubber opened this issue Jan 9, 2025 · 2 comments

Comments

@OrangeGitHubber
Copy link

The problem

I recently bought four Tapo L530E bulbs. Added them to the Tapo app and can control them from the app. In the same Tapo app I can also control other TP-Link/Kasa Devices.

Once the four new bulbs are added to the Wifi and Tapo app, they appear as discovered in Home Assistant. When I click on Add The username and password prompt comes up. I enter the same credentials I use for the Tapo app but it results in the error message.

tplink tapo error

I followed the instructions here , but it did not help either. 3rd Party Integration is on, and TFA is off.

What version of Home Assistant Core has the issue?

core-2025.1.1

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 Smart Home

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tplink

Diagnostics information

log file is 1.6GB in size.....I opened it and tried to copy just the last section from where the IP address of the attempted addition is mentioned..192.16.120.107.
L530E bulb failure to add log.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

All other original Kasa switches and bulbs still work, just these four new Tapo bulbs.

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Jan 9, 2025

Hey there @rytilahti, @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)

@sdb9696
Copy link
Contributor

sdb9696 commented Jan 10, 2025

Could you find the part of the log where the device 192.168.120.107 responds to DISCOVERY? Are you sure you're using the correct credentials (case-sensitive)?

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

No branches or pull requests

4 participants