I have tried for hours to get my new Tapo P105 plugs added to HA but I can’t seem to get them to authenticate to add them. All of my TP-Link (Kasa) plugs work just fine. I changed my Tapo password to be the same as it has always been, deleted all TP-Link devices to remove the integration and readded, reset the plugs, all to no avail. I am thinking about returning the Tapo plugs and just getting more TP-Link but got a great deal during black Friday
This is what happens on all 3.
Invalid authentication: Server response doesn’t match our challenge on ip 192.168.86.54
2024-12-20 08:12:25.062 DEBUG (MainThread) [kasa.transports.klaptransport] Created KLAP transport for 192.168.86.54 2024-12-20 08:12:25.064 DEBUG (MainThread) [kasa.device] Initializing 192.168.86.54 of type <class 'kasa.smart.smartdevice.SmartDevice'> 2024-12-20 08:12:25.064 DEBUG (MainThread) [kasa.protocols.smartprotocol] 192.168.86.54 multi-request-batch-1-of-1 >> '{"method":"multipleRequest","request_time_milis":1734711145065,"terminal_uuid":REDACTED,"params":{"requests":[{"method":"component_nego"},{"method":"get_device_info"},{"method":"get_connect_cloud_state"}]}}' 2024-12-20 08:12:25.064 DEBUG (MainThread) [kasa.transports.klaptransport] Starting handshake with 192.168.86.54 2024-12-20 08:12:25.064 DEBUG (MainThread) [kasa.httpclient] Posting to http://192.168.86.54/app/handshake1 2024-12-20 08:12:25.079 DEBUG (MainThread) [kasa.transports.klaptransport] Handshake1 posted at 2024-12-20 08:12:25.079727. Host is 192.168.86.54, Response status is 200, Request was REDACTED 2024-12-20 08:12:25.081 DEBUG (MainThread) [kasa.transports.klaptransport] Handshake1 success at 2024-12-20 08:12:25.081007. Host is 192.168.86.54, Server remote_seed is: REDACTED, server hash is: REDACTED 2024-12-20 08:12:25.081 DEBUG (MainThread) [kasa.transports.klaptransport] Server response doesn't match our challenge on ip 192.168.86.54 2024-12-20 08:12:25.081 DEBUG (MainThread) [kasa.protocols.smartprotocol] Unable to authenticate with 192.168.86.54, not retrying: Server response doesn't match our challenge on ip 192.168.86.54
There technically is not a “Tapo” integration as far as I can tell. Tapo is handled by TP-Link Smart Home integration which is working fine for all of my TP-Link Kasa plugs.
I have the same problem. I added two new EP25 switches. The Kasa app finds them without issue, Homekit does as well. HA sees them and asks for credentials for TP-Link Cloud. I use the same user and password as I do for the tplinkcloud, but it still fails to authenticate. As a side note, when I sign into the tplink cloud it only has provision to add cameras. My 15 other kasa devices work fine with HA
I have everything working now and I believe the fix was login exactly (case sensitive) as shown in the Tapo app. In my case my email address had the first letter capitalized.
Oddly, I can’t get my Tapo C120 camera to load into the integration any longer. Getting the same auth issue just on it.
Same here, the Tp-link integration does not see tapo devices. The Tapo app sees both Tapo and Tp-link, very frustrating as it renders them only semi-useful. This is a but that deeds to be addressed ASAP.
I have the same problem. The issue seems to be that the authentication requested by the TP-Link integration is actually not for the TP-Link cloud, but for a local account on the device.
That’s the way that the Tapo cameras work and the solution in that case is to enable an account on the device, through its advanced settings on the Tapo app I learned this from discussions on this forum, and it works.
But, the P105 has no such setting via the Tapo app. Nevertheless the error from the integration suggests that it is trying to authenticate on the device. See the screenshot attached.
I can’t find a way around this, at least using the “official” TP-Link integration.
I have 3 P105’s and they are all working now using the TP-Link Smart Home integration. The issue I was having was related to the username. In the Tapo app under account my email address had a capital letter in it. Once I used it exactly as shown it worked. Apparently, it is case sensitive. Beyond that I don’t know. I just added a KP115 I forgot about and it added right in without auth I assume because it is kasa.
Thanks for the reply. I’ve tried and retried the cloud credentials, to no avail.
What strikes me is that the error message reports that authentication has failed on the IP address of the device. Also this failure is immediate - consistent with something happening locally.
That’s the same situation I experienced with the Tapo cameras, before seeing up the local account and authentication on the device.
I wonder what’s the difference in my case and yours?
I’m not sure. I have been through probably 4 monthly HA updates since I got it working. Currently at HA 16.2, Core 2025.9.3 and Supervisor 2025.10.0. I also have 10 L535 bulbs and they too are working. I have always felt a lot of the Tapo issues are due to the consolidation of TP-Link, Kasa and Tapo. Are you in the US?
Funny thing, I have a C120 and last time I tried I couldn’t add it even using the local auth account. I don’t need in HA anyway but still…
Go to Tapo App - Me> Third-Party Services> and enable third party compatibility, restart HA and select Settings> Integrations> Tapo (you may be asked to login, use TP-link cloud credentials)
I’m just adding to the discussion in case anybody has the same issue as I did. I was going through the same hell with my Kasa smart Wi-Fi plugs. I could not get them to authenticate. I had them working in the Kasa app, but could not get them added to HA. After fighting with them for at least an hour, I finally remembered that these ones support Matter. I removed them from the Kasa app and just added them to HA as Matter devices. Took about one minute for each plug. I realize that most of the people in this thread are not talking about Matter enabled devices. I’m just adding this in case somebody else stumbles on the thread.
