TP-Link Smart Home integration authentication

Configuration
21

I had the same issue, tried everything mentioned in the thread.

Then I went to the Kasa app and saw firmware updates were available for all of the plugs/switches I have.

Installed the updates (two devices failed to install for some reason), restarted HA, and reauthenticated the two devices that I got the notification for.

The error messages went away and the plugs are back in business, although some sensors are unavailable (e.g. overheating).

Update: I’m pretty sure this has to do with the firmware update, the two devices that failed to update the firmware are giving me the authentication error again. Everything else works ok.

22

Hiya

I cant evenget them to connect in the Kasa app.

im not having much luck at all

:frowning:

23

I am kind of reliefed. Got crazy not being able to solve the issue but it does not seem to be uniqe. All my TAPO 110’s fail to authenticate giving me unknown error message.

24

I’ve found a working solution (for me at least) at TP-Link P100 goes offline then refuses authentication · Issue #121953 · home-assistant/core · GitHub

Tapo App → Device → LED state : Change from Auto to Off and back to Auto.
Then unplug the plug and replug in. Then it is available in HA again (needed to reload configuration).

2 Likes
25

Ive noticed they have included some TP link kasa python updates in the HA that I have just loaded.

I have no idea what that evens means or even if thats the issue but lets see if that fixes it

26

pretty sure changing the LED status is optional. unplugging it is the critical part in fixing the issue

27

I came in today and was having this problem with my KP125M. NFC automation didnt work and I realized it was asking me to re-auth and I entered my account into but it wouldnt authenticate. I installed the latest HA update and immediately fixed the issue. :+1:

28

Thank you for this.
I tried this, and it WORKED.
Who would have thought that the email address was case sensitive!

Thanks again

29

Thank you for this!

I was getting crazy with this. And this is my first day with HA…

30

Hi guys, the issue still seems to persist. I have a Tapo Cam C210 with Firmware Version 1.4.4. After Restarting HomeAssistant sometimes (Not always) the Cloud Authentication gets lost. I tried hard rebooting, waiting some 30 seconds and then trying to reenter. It also gets autodiscovered (see picture) and it has a static IP so that can’t be the issue. Also using password manager for the upper/lowercase issues, but to no avail. However I found pressing the reset button works, but this way I have to always reset the cam which is a huge hassle. Using ffmpeg to get a camera feed from the Commandline also works (from my laptop in the same network as well as from the HA docker Container itself)

image
image596×434 21.7 KB

31

Hey everyone! I’m having the same issue as @jerematix (C210 with 1.4.4), the login credentials are not accepted even after confirming they’re correct. Did someone find a solution?

32

My new TAPO C121 (1.2.3) was auto-discovered by the TPLINK integration but HA will not accept my TP-Link/Kasa/Tapo user name and password resulting in “Invalid authentication: Server response doesn’t match our challenge on ip 192.168.2.237”. I made a “camera account” on my Tapo app with a simple username and password but still can’t connect via RTSP in HA TPLINK integration but can in VLC.

33

I had to go into my Tapo app, to “me”, Tapo labs, then toggle third-party compatibility to “on”. Rebooted the camera. Then, I was able to authenticate the camera using my tp-link username and password (NOT the “camera account” username and password in the app’s advanced setting that I successfully used to network stream in VLC.

1 Like
34

For those coming across this thread, I had the same issue after just adding a new TPLink wall switch to replace an old problematic Wemo switch. Home Assistant saw the new switch but then came up with the “Login” screen.

And sure enough, it was a case sensitive username thing - apparently my username at TpLink has the first letter of the email address capitalized, and when I did the same at HA, boom, logged in and all good.

35

I am still having this issue with 2 Kasa Motion Switches (ES20M). I have about 30 other Kasa devices that have no integration issue. I have confirmed my username/email and password. I have confirmed the case in both and have even tried to change my password. Honestly when I submit my login/password it seems to return with “unable to authenticate” before I feel it has time to actually check anything. I’m out of options :frowning:

Looking for more ideas please

36

Thank you. This worked for me.

37

It is May 2025, I still have the authentication issue for my 2 out of 4 my TS200 switches - after a power outrage in my house.

Screenshot 2025-05-26 at 16.32.22
Screenshot 2025-05-26 at 16.32.221710×584 57.7 KB

BTW: those were not discovered automatically when I create a new HA VM instance. All other Kasa devices were discovered for the first HA run.

Tried to reconfigure them, but ran into authenctication issue:

Screenshot 2025-05-26 at 16.39.27
Screenshot 2025-05-26 at 16.39.271460×1004 50.9 KB

I have checked email/password and cases many times.
One trick I found: after HA reboots and having setup issue for those devices, if you push the “restart” button on TS200 panel (very thin button under Rocker, right one), they become available very quickly. Still it is bother to push button for each of such device everytime HA reboots.

Is this an issue in Kasa firmware/cloud or bug in Integration? Kasa/Tapo app works flawless always.

38

Having the same issue, I check upper/lowercase, restarted the C200 camera, no luck, I still get auth issues :frowning:

Screenshot_20250527-144632~2
Screenshot_20250527-144632~21080×261 16.8 KB

39

A follow up on my issue (fixed):
Yesterday morning I found my Kasa/Tapo devices remain available after HA reboots. I made mulitple changes before it but I think the most relevant change that did the fix is that I removed device_tracker setting for my router. I guess device_tracker may interference the Wifi device authentication. Also another issue that I had was resolved at the same time: cannot add Matter devices into Matter integration in HA - may due to the same reason

40

I have some older TPLink switches and wall plugs that have worked perfectly.
They did not require a cloud account, and since I discovered the python-kasa command line tool I was able to provision the older devices, without using a phone app at all.
Brilliant!!

I just bought a new TPLink HS220-LA (Wall dimmer switch), running firmware version 1.1.1.
I was hoping for the same blissfully wonderful experience that I’ve come to expect, but…
The newer devices seem to require a cloud login…
I can’t say how much I really HATE having to even entertain TP-Link’s requirement to create a cloud account.
Does anyone know if these devices will even work without an internet connection? That’s an experiment I should probably do!

In any case, I sucked it up, created a tplink cloud account, and proceeded to configure and install the new wall dimmer.
I was seeing the same error that others have posted here:
“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.”

Reset the device a number of times… No worky!
Changed the IP address (via the python-kasa cli)… No worky!
Turned off 2-factor authentication (via phone app)… No worky!
Rebooted HA a number of times to have it rediscover my device… No worky!

Finally, I changed my tplinkcloud.com password to a string that did not have any upper case characters, or any symbols, and that finally worked.

At this point, my wall dimmer is working, configured, and is currently accessible by home assistant.

Reading other posts in the thread, I am still concerned that the login may not stick over multiple days without some sort of manual interaction.
I have rebooted my HA instance a couple of times now, and so far no issue.

I don’t know if this info will be helpful to anyone else.
I think the reason for this post was about my own personal therapy, but I do truly hope my experience helps someone else!

Happy Home Automationing!