Don’t know why exactly, but in my case, I used a capital for the first character of my username (e-mail address), and then it worked. Thanks all.
1 Like
So I am still getting these TP-Link issues on a daily basis but it seems to authenticate just fine? Why is this a daily occurrence?
Thank you, this did it for me in the KASA app.
Still getting some strange behavior though all cameras are working just fine in HA so not sure what is causing these to stay:
- Remove device from Tapo app
- Reset the Tapo device
- Connect phone to same WiFi access point as device.
- Add device in Tapo app. DO NOT USE QUICK LINKS OR FOUND DEVICE
- Choose network to connect to. Add password for WiFi network
- If it says this device has been configured before. Choose delete old configuration.
- Once you have finished connecting you should now be able to add it in Home Assistant.
This is bascially crap programming in the Tapo App.
2 Likes
Fixed my issues after finding some old Tapo Camera Control and TP-Link HACS integrations that needed to be removed since HA now has built in integration.
The KASA App itself now has Third Party Compatibility as well. I enabled that but then like others found out the first letter of my email address in the Kasa app was a capital letter so once I used that it added all the other devices.
Yup this worked perfectly
I’m having this issue with two C211 cameras. The only way I was able to get them to integrate to HA was to set a device password on each, and add them as ONVIF devices.
- Remove device from Tapo app
- Reset the Tapo device
- Connect phone to same WiFi access point as device.
- Add device in Tapo app. DO NOT USE QUICK LINKS OR FOUND DEVICE
- Choose network to connect to. Add password for WiFi network
- If it says this device has been configured before. Choose delete old configuration.
- Once you have finished connecting you should now be able to add it in Home Assistant.
This is bascially crap programming in the Tapo App.
This is the process that finally worked for me. Thanks.
2 Likes
Solved with your instrutions and this for my Tapo TC72:
Thank you for the insight!!
1 Like
same problem
tried caps email but that is not the problem
turning third party compatibility made it worse and knocked out the camera that were working fine
this is no good
I think after using lowercase letters in the email it worked for me.
wow, been fighting this for a week trying to sort it, turns out this was the issue I was having as well, had a space after my email saved in my password manager… Thanks for posting this.
Hello Everyone,
I recently managed to fix this issue for a couple of my devices that randomly stopped working a couple months ago. Specifically a KP115 and an EP10.
I tried most of the various fixes above; enabling third party compatibility in Tapo/Kasa, changing/resetting my TP-Link password, trying weird variations on capitalizing parts of my username etc. About the only thing I didn’t do was remove/reinstall home assistant or the integration.
One thing I noticed after resetting the devices is that when HA discovered them, they were lacking their Alias and only showed a short alphanumeric string and their part number.
Eventually, I found something about manually provisioning TP-Link devices with Python Kasa so I thought I would try that. After getting it setup on my regular computer and running the discovery command to test it was working, I noticed that the KP115 I was testing, and hadn’t yet reset again to try the provisioning, was discovered successfully AND showed its alias without having to use any credentials.
I tried controlling it through python kasa commands, and it worked with NO authentication. This seemed weird given that HA seemed to think I had to authenticate to use this plug.
I went back to HA and the device was still showing in the auto discovery without its alias so I rebooted HA and when it came back, the plug was there in the auto discovery section with its alias showing. Attempting to add it worked and did not ask for my username and password.
I then got my other problematic device working as well. I Plugged it back in(again, still fully connected to Kasa/Tapo), ran python discovery, forced discovery without a reboot in HA (Add Device>TP-Link>TP Link Smart Home> (Blank Host)Submit).
I have no idea why this worked and I suspect it won’t for newer Kasa/Tapo devices, but if you are having this problem and nothing else in this thread worked, maybe give it a try?
1 Like
Go to TP Link Cloud page (Google it) and sign in with your account, then update the password to the same one you had.
It works
1 Like
I just ran into this with two of my power strips. The rest of my devices worked fine and everything was working in the Kasa app. I finally found the solution though:
Kasa App > Me (profile icon) > Settings > Third-Party Compatability > Set to “ON”
Mine was set to “OFF” for some reason, but once I switched it on, they were able to reconnect in HAOS again.
Hope that helps.
1 Like
I have the same problem trying to add my P110M. I tried the changing “Compatability”, doesn’t work. I tried username only, doesn’t work. Double checked uppercase lowercase username as email, doesn’t work.
What worked was having to change the password on the Tapo app to a new password and then using that new password. This method worked for me.
This did work for me. I went to https://www.tplinkcloud.com/, changed password to the one same as before, and I was able to add my Tapo P110.