waterloo
(waterloo)
November 30, 2023, 4:13pm
1
Hello there, I have a stock HS103 Kasa Smart Plug that Home Assistant informed me it detected automatically as a new device on my network, and wants to set it up! Amazing! That’s convenient!
Except - it doesn’t work
It now just says FAILED SETUP WILL RETRY and it’s stuck in a loop, with zero useful output or any kind of information as to what it’s problem is
Thanks for any help!
GeneB
(Gene)
November 30, 2023, 9:32pm
2
You’re not alone. This is an ongoing issue for the last couple of weeks, involving an update to python-kasa
. It’s being worked on, but the fix hasn’t made it into an update yet.
opened 06:38PM - 14 Nov 23 UTC
integration: tplink
### The problem
All devices using the TP-Link Kasa integration show "Failed s… etup, will retry". Hovering over the status shows "Unable to get discovery response for [device's hostname]."
Issue appeared immediately after updating to Home-Assistant v2023.11.
The integration was known to work before upgrading (I upgraded from v2023.9 to v2023.11, skipping 2023.10).
Debug log shows evidence of successful connection to device.
### What version of Home Assistant Core has the issue?
core-2023.11.2
### What was the last working version of Home Assistant Core?
core-2023.9 (or closest build)
### What type of installation are you running?
Home Assistant Container
### Integration causing the issue
tplink
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/tplink
### Diagnostics information
[home-assistant_tplink_2023-11-14T17-58-32.092Z.log](https://github.com/home-assistant/core/files/13353903/home-assistant_tplink_2023-11-14T17-58-32.092Z.log)
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
Nothing abnormal was found.
### Additional information
- Multiple devices of varying models produce similar error and logs. None of the devices work.
- All devices were added by manually entering their hostname/FQDN.
- Devices are on different VLAN (with routing rules configured), so I do not expect auto discovery to work. These devices worked prior to update.
–Gene
rperkins
(Robert Perkins)
March 15, 2024, 7:16am
3
Try months! I’ve got 30 TP-Link devices with the same failed setup problem. It’s now mid March 2024, and it’s been going on for over a year.