I have 27 various TP-LINK smart plugs and switches happily connecting to my Home Assistant for a very long time. I just now upgraded from 11.1 to 11.2 and now my HS300 power strip is not connecting.
The power strip responds locally 200 OK on port 80 and works correctly when using the official Kasa app. All other TP-LINK smart plugs/switches are working just fine in HA.
I’ve done a hard power reset on the HS300 (unplugged it from the wall, waited 10 seconds, and plugged it back in). It still responds 200 OK on port 80 locally and works fine with the Kasa app. I’ve rebooted HA twice.
What could be wrong with this device and how could I fix it?
Now without doing anything, the error message has changed to “enter username and password”, but only on this device (all others are fine, including the other HS300 I have).
Thank you for posting and welcome to the community!!
I’ve checked the 3rd Party setting and it’s on. All other TP-Link devices have been working correctly for years.
The troublesome HS300 device is hardware V2, firmware 1.1.2, and returns 200 OK when opening port 80 using a web browser, but times out on port 9999. The other HS300 that works fine is hardware V1, firmware 1.0.21, but it times out on ports 80 and 9999.
All devices work fine in the Kasa and Tapo apps.
Troubleshooting Actions:
Check for newest firmware (all up to date)
Confirm 3rd Party compatibility is turned on (is enabled)
Power-cycle device (unplug from wall, wait 10 seconds, plug into wall)
Restart Home Assistant
Remove troublesome device from Home Assistant and attempt to re-add (still asks for cloud credentials for the one device, all other 26 devices are fine)
Ok, I’ve narrowed the issue down to something wrong with my primary Home Assistant setup.
I factory reset the HS300 and re-added it to my home network. My primary HA recognized it as a new device, but still asked for cloud credentials.
I set up a new separate test HA instance. The test instance recognized the HS300 and immediately adopted it without asking for any credentials (exactly as it should).
How do I completely purge the HS300 from my primary HA setup so that it will retry with local authentication instead of asking for cloud credentials?
So I’m in the same boat. HA says 47 total tplink devices. All worked fine except hs300 hardware v 2
I have 3 HS300 that after a combination of HA update and TP update, broke.
I think the solution is easier than both of us originally tried. I did not find success using your method, I was just in login loop hell.
What did it for me was
Press and hold control button on power strip for 5 sec
Reconnect to wifi, but don’t reset.
Go to home assistant, ignore the prompt to add it. Instead note the IP address, and then hit the plus sign to add a device and follow typical procedure for tplink.
I had already deleted the devices from HA and fully factory reset one of the devices. It appears as though most, if not all of the automations, scenes, and other related info for these strips are completely gone. So frustrating… Guess I get to rebuild them on the weekend now.
I am in the same boat as well. Only I went from bad to worse. I had an issue with my Kasa power strips (KP303 and a KS300) and restarted HA (2025.12.1 Core/2025.12.2 Supervisor) and now the KS300 is toggling between normal connection and “failed setup…” and I also have one (1) HS103 that was working and now does not connect at all. Entering my TP-Link credentials does not work at all even though I can login online and through my Android phone app with no issues. I don’t think marking this one “solved” is appropriate at this time IMHO.
I’m in the same boat. Just tried the posted solution and still getting the same result with my HS300. It used to work before, but I’m setting up a new instance as I moved house, and in the process added it to a new network as well. I can’t be sure what exactly is different from before (though, I did allow it to firmware update itself, compared to the ~5yo firmware it was on before) but I’m running HAOS Core 2025.12.4, Supervisor 2025.12.3
Same. This issue started because I updated the HS300 to the latest 1.1.2 firmware. It was running 1.0.2 before and was working fine. After the firmware update, all broken. They changed the API and authentication for local communication, so unless the devs are kind enough to release an update, these are no longer compatible. If anyone has a way to share the older firmware, I’d be forever greatfull.
I am experiencing the same authentication failure (requesting Kasa Cloud credentials which continually fail) for only a single HS300 power strip that has worked for at least a year, but suddenly stopped being “registered” in HA after a brief power outage this morning (I managed to do a shutdown of my main computer, but HA remained on and simply cut out when the battery backup ran out of power)…so the HA shutdown (running on an older Dell mini PC (formerly a Chromebox) was not “clean”. But reading through the rest of the posts here, I don’t think that was the issue. I’m betting that something in the API changed and now needs to be tweaked by the devs to correct the situation, because the HS300 is the only one of 37 other Kasa/TP Link devices that has run into the issue. All others are working just the same as before.
I have verified the IP address of the HS300, and it is working in both the TP-Link Tapo App and in the Kasa App on my Galaxy. The only issue now is that it will not “authenticate” in HA. Here’s what I’ve done:
Tried to input my credentials for Kasa Cloud (as requested)-- verified they are correct by logging into the Kasa web instance. Even changed my password and retried that to verify that it was correct; also turned off and on 2-factor authentication just to see if that matter-- it did not…Still no joy.
I removed the HS300 from HA and allowed the HA TP Link Integration to “Discover” it again (it did), but trying to then add it by clicking on the green “Add” button, simply results in yet another “Authenticate” dialog where entering the username and password result in "Unable to authenticate: Device response did not match our challenge on ip 192.168.1.XXX, check that your e-mail and password (both case-sensitive) are correct. " So log-in loop hell…
After reading everyone else’s comments, I’m just going to wait to see if the devs fix this in the integration for TP Link…
Gotta go…another power failure is happening and need to shut down…Shit…
Did you try a full factory reset of the power strip (press and hold the button for plug #6 for 5 seconds) to restore the local connection? That worked for me, but just for a little while.
Although I don’t own it, the Tapo P316M is a rebrand of the Kasa power strip. Perhaps it does not suffer from the same issue as the HS300, but I don’t know for sure.
