Yes but I have had to set them up using the app / cloud account first. And the led status light shows red when I block their Internet access but they still work.
I was also getting authentication errors. I use a password manager so I had a complicated password that included all kinds of symbols. I changed it to a long string with a few numbers and basic symbols and was able to authenticate.
For anyone that might have the same issue. My fix steps were mentioned separately earlier.
We have some HS300s and KP303s, 5 in total. All of them lost communication due to an auth issue after firmware upgrades. Our HS103s don’t have any firmware updates and never disconnected.
My fix steps:
1 - Log in to the TP-Link Cloud webpage and change my password
2 - Sign back in to the Kasa app after it forced me to sign out from the password change
3 - In the Kasa app, navigate to ‘Me > Settings’ and enable ‘Third-Party Compatibility’
The Third-Party Compatibility option specifically mentions integrating “seamlessly with third-party ecosystems like Home Assistant” (see the screenshot below). From there, I didn’t even have to reauthenticate the strips. They all started coming back on their own.
I also don’t know that the password reset option was necessary, but it was a step I took.
Hi everyone. Very new to HA and appreciating all of the community support here!
I had the same issue as many reported earlier:
“Unable to authenticate: Device response did not match our challenge on ip xxx.xxx.xxx.xxx, check that your e-mail and password (both case-sensitive) are correct.”
Weirdly this only happened on the last of 4, KP125M smart plugs, the first 3 did not ask for authentication.
Anyway, I tried the suggestions provided earlier but no luck for me. However I did manage to solve the issue with the steps below. Not sure if this will work in other regions but worked here in Canada…
- Initial device setup required Kasa Smart app to be installed (Aurora Store worked fine) and Kasa account be created.
- All devices added to Kasa and then to HA no problem until the last plug.
- The last plug asked for verification via the Tp Link Cloud account, so I created this account and logged in ok. However this would return the error in HA when used for authentication.
- What fixed the issue for me was logging into the Tp Link Cloud page with the account info created in the Kasa app. These credentials were accepted, so Kasa obviously speaks to Tp Link in the background.
- I then returned to HA and used the Kasa credentials to authenticate the plug. So what it seems is that the account connection in the background (this case Kasa/Tp Link) needs to be formalized by logging into both before the HA will authenticate.
Hope this makes sense? Maybe it will work similarly with other TP Link sister products? Hope it helps someone!
I’ve got the KP303 power strip.
What worked for me was using the Kasa app to set the following setting to on: Me->Settings->Third-Party Compatibility.
All of my switches are now showing unavailable. HA fix this!
It is not HA that needs to fix this. If you are using the TP-Link Integration, an issue needs to be logged with the TP-Link integration developers here:
Also have had this issue recurring for quite some time.
For me the fix was similar to some of the responses above.
Once you get the failure to authenticate, doing the following has worked for me.
Reboot HA
Once you can access the TPLink integration to reconfigure, attempt login and fail.
Go to the Kasa app and toggle Third-Party Compatibility Off, count to 10, toggle Third-Party Compatibility back to On.
Go back to HA and try to authenticate and it works.
YMMV......