-
-
Notifications
You must be signed in to change notification settings - Fork 28.4k
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
TP-Link Component: Failure to find one switch results in entire component failing #21725
Comments
according to the I've submitted a pull request as I had this issue as well |
I have the exact same setup and issue 😄 |
Fixed now in dev branch, thanks to @ljmerza! |
Thanks 🙏 That was fast! |
any news about this ? |
Merged in dev but not in 89.1 or 89.2 unfortunately.... |
Just pulled dev(0.90.0b1) and I'm getting this:
Am I missing something? |
Home Assistant release with the issue:
0.89
Last working Home Assistant release (if known):
0.87
Operating environment (Hass.io/Docker/Windows/etc.):
Docker on RHEL7
Component/platform:
TPLink
https://www.home-assistant.io/components/tplink/
Description of problem:
I have a number of TP-link switches, some of which are only used part of the year. For example, I keep one for my Christmas tree. They have static IP addresses, and I don't want to use discovery (I have a complex network configuration, HA is on a different network than the IoT stuff). If one switch is unavailable, then the entire component doesn't load.
I can comment them out, but I'd prefer not to.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: