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