Closed bjruberg closed 2 years ago
tplink documentation tplink source (message by IssueLinks)
Hey there @rytilahti, @thegardenmonkey, @bdraco, 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!
(message by CodeOwnersMention)
This type of setup isn't supported as the extender isn't acting as a bridge.
I suspect the same solution used in https://github.com/home-assistant/core/pull/73411 would solve this issue if one of the other codeowners wants to support this.
A fact I forgot to mention: This worked flawlessly in my previous setup using HA Core. Since I switched to a dedicated Raspberry for Home Assistant OS and restored a backup.
The problem
I have a TP-Link HS-110 that is connected to HA via an wireless extender (GL-Inet AR300M). The plug has an IP in the 192.168.2.* net - as has the extender.
The plug can be reached by configuring the plug's IP. No issue here.
The problem is that the integration ALWAYS changes the configured host to the IP of the router. I cannot stop it, it just happens after a few minutes. Using that IP the plug cannot be reached and therefore becomes unavailable in HA.
I suspect a problem with auto-discovery - as auto-discovery discovers the device also with the IP of the extender. That is not that problematic. Bad is the constant overwriting of my configuration with the wrong IP.
What version of Home Assistant Core has the issue?
2022.6.6
What was the last working version of Home Assistant Core?
Home Assistant OS
What type of installation are you running?
Home Assistant OS
Integration causing the issue
TP-Link Kasa
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?
No response
Additional information
No response