TP-Link not auto discovering in Home Assisistant version 103.5

[trentjw]

Home Assistant release with the issue: 103.5

Last working Home Assistant release (if known): possible 101.x

Operating environment (Hass.io/Docker/Windows/etc.): Venv

Raspberry Pi platform new Clean install no other devices on platform

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

Description of problem: will not discover devices KASA app finds them and works proper, Can manually add them and the HS200 works proper the KP200 does not but is found

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

[probot-home-assistant[bot]]

Hey there @rytilahti, mind taking a look at this issue as its been labeled with a integration (tplink) you are listed as a codeowner for? Thanks!

[trentjw]

well from a bare bones full clean install with version 103.5 it does not add the TP-Link from the configuration page as it cannot find any devices Kasa smart app finds them just fine and controls them proper

going to roll back to 101.x to see if it can discover them at that time

[trentjw]

No joy in TPlink town it flat will not auto discover them even at 101.1 will update to 103.5 on a new clean install and try to manually add tplink

[rytilahti]

Did it ever work for you? Are the devices in the same network as your homeassistant installation? If not, you need to manually configure the IP addresses.

You can also use the command line tool called pyhs100 for testing the connectivity.

[trentjw]

I did manage to figure how to get the KP200 proper, however it still does not auto discover them and they are on the same local net as my home assistant I have one HS200 and one KP200 neither of them gets discovered, both work as they should once manually installed

[Mattie]

Seeing this same issue. Really frustrating. Not sure why Kasa stuff keeps having these kind of problems.

[trentjw]

Are you able to manually install them?

On Sun, Jan 12, 2020 at 12:54 AM -0700, "Mattie" notifications@github.com wrote:

Seeing this same issue. Really frustrating. Not sure why Kasa stuff keeps having these kind of problems. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[bmreading]

I'm also having this issue. Brand-new install on 108.7 only works with manually-configured bulbs. Discovery is broken.

[lmontin]

note sure if this help but I had similar issue and I changed ha docker-compose yaml from : ports:

• "8123:8123" to use: network_mode: "host" then discovery worked. So after discovery I changed back to using ports and devices continued to work in HA

[bmreading]

Thanks for chiming in. I have the image containerized and operating in Kubernetes using Helm. I am currently using the "host" network mode, and it shows in that my pod recognizes the host's IP address as its own, and is able to discover other things, but not TP-Link things.

[stale[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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.