core: TP Link switches unavailable
The problem
Updated to 0.109.3 and all (2) my TP - Link switches became unavailable. Removed the integration and tried to re-add, “Aborted. No TP-Link devices found on the network”. Restarted and tried to re-add, integration added but none of my switches appear even after multiple restarts. Switches appear in TP Link app (Kasa) and are functional. Switches have latest firmware and I have power cycled them. I’m going to reset one soon to test.
UPDATE: I removed the integration again and now no matter what I cannot re-add because it cannot find any switches on the network.
I tried to manually setup one via the switches.yaml:
- platform: tplink
switch:
- host: 192.168.1.83
But I get the error: “The tplink platform for the switch integration does not support platform setup. Please remove it from your config.”
Environment
- Home Assistant Core release with the issue: 0.109.3
- Last working Home Assistant Core release (if known): 0.109.2
- Operating environment (Home Assistant/Supervised/Docker/venv): Docker
- Integration causing this issue: tplink
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/tplink/
Problem-relevant configuration.yaml
Traceback/Error logs
Additional information
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 51 (6 by maintainers)
I seem to be having the same problem as the original poster: all my TP-Link switches and lights have disappeared from home assistant. I have tried many things: deleting and re-adding the TP-Link integration, deleting all of the switches from TP-Link’s Kasa app, completely re-imaging home assistant, etc, but still the TP-Link integration says that it can’t discover any devices on my network and then aborts.
Anybody got any ideas what I can try?
https://github.com/home-assistant/core/pull/30719 looks like the PR to follow.
Thanks for that. I will try this over the weekend, and see how I go.
Dear rytilahti, I have not forgotten. A few network setbacks and some COVID-19 distractions but I plan to have public-key ssh access set up for you soon. Your dedicated network with the HS300 is still set up. Thank you for your patience. -Bruce
I can confirm that the Home Assistant -> SmartThings -> Kasa setup works without issue. I will be using this until the Kasa integration is fixed
Had the same issue, reserving static IPs in my router and defining those IPs in the home assistant yaml config fixed this for me.
Using the UI Kasa integration does not work
This is exactly what I had going on. If you want a quick fix, I suggest linking Kasa with Smartthings and adding Smartthings to Home Assistant.
I keep running into this same issue and I just switched to connecting them to the SmartThings app and using that to connect to Home Assistant. It’s not local but at least it works!
Yes, the PR has not been merged and is still WIP, so it’s hardly unexpected that the issues are still there. The most problematic part is the HS300 with emeter support requiring separate queries. Making this working properly is not as simple as I thought originally, especially without a test device at hand.
One approach would be to simply remove the emeter support from HS300 which would eradicate the one last bigger issue immediately, the other one is having some more patience. @Sidlinger (https://github.com/home-assistant/core/issues/28912#issuecomment-651475019) has offered to contribute to the latter approach by making a device available for me to use for development.
i have been able to set it up manual be the config.yam and auto discovery dose not work