I posted this issue to HA’s forums and received no response, hoping someone here has some idea to help.
I have a lot of TP-Link Kasa devices in my home. When I first installed HA, it automatically discovered all of them. I was using a 4-year-old TP-Link Deco mesh system at the time.
For reasons unrelated to HA, I had to replace that system. I replaced it with a newer TP-Link Deco system, X55. Once that was installed, HA could no longer access the Kasa devices. It still sees all my other IoT devices.
First, I removed all the Kasa devices from HA and tried to rediscover them; no luck. I tried using each device’s IP address for the host to discover them. When I used 192.168.68.67, e.g., I got this error message:
Connection error: Unable to connect to the device: 192.168.68.67:9999: [Erno 113] Connect call failed (‘192.168.68.67’, 9999)
I rebooted at all places, including resetting a couple of the Kasa devices to see if that worked. My sneaking suspicion was that this new Deco system has a Smart Devices Manager in the app, which only recognizes my Kasa devices on my network (none of the other IoT devices), and somehow that’s interfering with HA’s access to these devices.
Since then, I managed to make some progress, but not much. I managed to remove my Kasa devices from the Deco app management by “removing” each one. This deleted the custom name for each so that now each shows as its generic model type on my network (e.g., KL110).
After I did that, HA found nine of the 14 devices automatically. It still won’t find the other five. Every week or so, it discovers a new one on its own, so maybe someday it’ll find all of them.
However, I still get the error “Failed setup, will retry” for all of the ones it has found. When I reload, it goes through the initializing stage, then right back to “Failed setup, will retry.” I have debug logging on, but I don’t see any logs for these devices in my logs. When I go to a specific device, it indicates “No logbook events found.”
I’m still able to control these devices via the Kasa app, but I can’t incorporate them into any HA automations.
Any help or suggestions is much appreciated. Thanks!
Not a silly question, but no, no change. In fact, the new mesh network has the same name and pw as the old one, and I did not change my kasa or HA credentials.
I recently added a kasa smart plug using matter. Then the tp-link integration noticed it and forced me to reauthenticate.
That’s my closest match to your story.
It had been given my username and password before. But it needed them all over again. I’ve had that happen for other things before, too.
Not sure if would help or if you have done it… But it takes about a literal minute to do.