Discovery not working for Tapo L900 devices

[mark3267]

The problem

I am unable to add Tapo L900 devices to HA.

These were previously added via the HACS Tapo Controller integration.

When adding a device via the TP Link Smart Home integration I receive the following error

Connection error: Unable to connect to the device: 192.168.0.137:9999: [Errno 113] Connect call failed ('192.168.0.137', 9999)

What version of Home Assistant Core has the issue?

core-2024.7.3

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

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-07-22 13:12:25.513 DEBUG (MainThread) [kasa.iotprotocol] 192.168.0.137 >> {"system":{"get_sysinfo":null}}
2024-07-22 13:12:26.956 DEBUG (MainThread) [kasa.iotprotocol] Unable to query the device: 192.168.0.137, not retrying: Unable to connect to the device: 192.168.0.137:9999: [Errno 113] Connect call failed ('192.168.0.137', 9999)

Additional information

No response

[home-assistant[bot]]

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]

Do you have a vlan or firewall? It seems that the discovery is not working properly. When you try to add the device via the integration and leave the host blank does it find the device on your network?

[mark3267]

No VLAN or Firewall.

It has worked fine for over 6 months then seemed to stop following the latest core update

Discovery doesn't work. I deleted all of the L900 lightstrips and re-ran discovery but nothing is found

---

From: Steven B. @.> Sent: 27 July 2024 11:11 To: home-assistant/core @.> Cc: Mark Smith @.>; Author @.> Subject: Re: [home-assistant/core] Unable to add Tapo L900 devices (Issue #122383)

Do you have a vlan or firewall? It seems that the discovery is not working properly. When you try to add the device via the integration and leave the host blank does it find the device on your network?

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/122383#issuecomment-2254102089, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALLU4KKZQ67EAVXUVES27TLZONW4XAVCNFSM6AAAAABLIGIAHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGEYDEMBYHE. You are receiving this because you authored the thread.Message ID: @.***>

[sdb9696]

Could you try installing the kasa library and running kasa discover?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[BettySwallocks]

This is probably held up by the OP (and me with a similar problem) running HAOS and the suggestion to install the kasa library is not practical.

[rytilahti]

The problem is simply that the device does not seem to be responding to. Considering how few users are affected, it's unlikely a problem with the integration, but it is hard to rule out without further information.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.