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.
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.
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).
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.
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)
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?
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.
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.
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.
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
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.
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
