Invalid authentication #122
Comments
petretiandrea
added
bug
|
My email address contains upper case letters and I was able to login after entering the email address case-sensitive, that is, using the exact same case as seen in the Tapo app. That worked for me as workaround and it's way more simple than creating another account. |
|
I don't have any capital letters in my email address (only lower case, dot and numbers), but still I can't authorize with this component in my HomeAssistant. |
|
@GrzegorzZajac000 Can you try to execute this snippet of code and report here the output? import asyncio
from plugp100 import TapoApiClient
async def main():
# create generic tapo api
sw = TapoApiClient("<ip>", "<email>", "<passwd>")
await sw.login()
print(await sw.get_state())
loop = asyncio.get_event_loop()
loop.run_until_complete(main())
loop.run_until_complete(asyncio.sleep(0.1))
loop.close() |
|
Hi there, |
|
Hello, I would like to use my Home Assistant (located in my house) to control a P100 switch (located in my office). |
|
Hello |
|
Thanks for your report, but as you can see here: v1.2.4...v1.2.8, there are no changes between the two version about authentication step. So retry the latest version and check if now works. N.B. A user on home assistant community forum says that changing the password for tapo account will not refresh the password changed on the already associated devices until you remove and re-add the device from tapo app. @gpbicego @francesco-bonassi |
For authentication issue, see the comment above. Regarding your question about "remote" control, this integration work on local polling, so you can't control it from an external home assistant instance. (Where external is intended as different network, like your office and home. So if you install home assistant on your home and the tapo is in your office, you can't control it. The only way is to install home assistant in your office and expose home assistant on "internet" and access to it from your home) |
|
Thanks Andrea. |
|
Auth issue as well - p/w and ID all lower case. |
|
Check if there are extra blank spaces before or after the e-mail address.
I've found that android's keyboard adds a extra blank spaces at the end
when inserting from auto-complete.
Maybe the integration could trim the e-mail string before attempting to authenticate.
|
|
After further investigation it would add some devices, some failed. However, rebooting HA in-between adding it eventually allowed me to add all devices - weird, no idea. |
Why are you talking about cams? This integration doesn't support cameras |
|
My bad, just got to the wrong repo. Sorry! |
|
Hello, I've installed this in order to manage my L900. Today it stops working so I decided to remove the L900 and add it again. |
|
I'm seeing transient failure here too. My e-mail contains a I tried reaching the device using the After a few retries, it starts working fine for both that client and the Home Assistant integration. Then 10 minutes later I'm getting unavailable data. |
|
I am having the same problem. What is the value of the host field? Is this the IP address of home assistant or the Tapo device? I've tried both and in the error below am trying with the device.
This is in home-assistant.log: aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.53:80 ssl:default [Connect call failed ('192.168.1.53', 80)] |
|
Ok it worked - didn't seem to like an upper case letter in the password. IP address was that of the device. |
|
Hi guys i am newbie with home assistant but its giving to me a “invalid authentication” when i am trying to put the host, username and the password and i already change the code on configuration.yaml to this |
|
I found that removing and re-adding my devices and auth started to work. I also noticed that the IP in the Tapo Mobile app assigned to a device was different to the actual IP the device had now. I could not use the IP that my DHCP server told me the device had, so I don't know if I was suffering from a stale password on the device or something else. |
|
Previously same problem. Configuration :
What works:
Thanks for this update and your great job! |
|
Also I have found that similar to other sorts of devices such as Tuya, ensure that you do not have the app open on another device. That was my fix anyway. |
|
Hey guys, thanks for this integration, but I can't connect to a server, it takes a lot of time to request and then shows this error: |
|
In my case, I have 8 plugs under the same Tapo account. 5 added successfully. 3 get the invalid authentication. Obviously, the userid and password cannot be the issue as they work fine for the other 5. I have double checked the ip addresses I am entering and they are correct. All plugs are working fine in the Tapo app. I have in the past used the manual TP100 Control github to implement these plugs but have changed over entirely to this TAPO CONTROLLER integration now, so it is possible something is left over in the depths of HA for these plugs but nothing showing in the UI. UPDATE Removing and Re-adding these 3 to the Tapo app and ensuring I made no amendments to the name or any other aspect, meant that these could then be added to TAPO CONTROLLER although not first time for all. So a little confusing but currently working. ANOTHER UPDATE BUT LESS POSITIVE All 8 of my plugs were correctly showing in the Integration until I restarted Home Assistant (no integration updates, just some unrelated yaml changes). The logs are below (after a reload - same every time): `Logger: homeassistant.config_entries Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.2', 3000)]; Retrying in background |
Pc os? Architecture? |
sorry iam a noob here, i just use this can i add log details for ERROR here? |
|
Hi Guys, Thanks for this wonderful integration and I was using the Tapo P110 device with this integration for the last 3 months without any issues. But today evening I upgraded HA Core and Supervisor to 2022.7.0 but then I lost access to the device. It's still accessible via the Tapo app but I could control it as it was the device was not available. Tapo Integration showed "Retiring setup: None". So I removed the existing installation and added it again. But then after that, I am getting "Invalid Authentication", I couldn't pass this step and got stuck. Now I tried everything it was suggested above,
I am not sure what else has gone wrong wiht this integration. All other integrations including TP-link add on is working fine. Can someone please help with this issue? Update:After trying everything, I restored it back to Home Assistant Core: 2022.6.7 from 2022.7.0 and it just started working again without any modifications. Not sure what changes are breaking this integration. Now my HA versions are, |
|
I am also having issues authenticating (obtaining "invalid credentials"). I tried to disable the error handing to see what was the actual exception, and I've got the following: It looks like something that should be handled in the library that calls the API |
|
Same here, with multiple C200 and C500 on two different HA instances |
|
i was having this issue with my p100, removed it and re-added it to home assistant and now it works |
|
@chicknwinner, how to remove it if it fails to be added in the first place? |
|
I have the same issue with not beeing able to connect H200 and T100 to HA. |
|
Got errors here with Tapo P110 plugs. Both HA and the plugs are on their latest version. |
|
"Failed to connect" error - it seems this should be removed until it's fixed. |
|
"Failed to connect" error for P110. HA version: 2024.2.1 
HA Log: |
Hi, I'm a completed newcomer to this but was able to resolve. My mesh WIFI was not in Access Point mode "AP mode". I tried this and the plug connected fine. Might help other new users. |
|
Same issues, with a P110 and a P300 Version of the integrationv2.14.0 & v3.0.0 With v3.0.0 however, the username and password field are blank. Configuration$ cat /mnt/docker/homeassistant/configuration.yaml [21:17:43]
# Loads default set of integrations. Do not remove.
default_config:
# Load frontend themes from the themes folder
frontend:
themes: !include_dir_merge_named themes
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
homeassistant:
internal_url: "http://192.168.50.2:8123"
external_url: "https://homeassistant.domain.com"
http:
use_x_forwarded_for: true
trusted_proxies:
- 172.16.0.0/12
- 162.158.0.0/15
- 192.168.0.0/16
ip_ban_enabled: true
login_attempts_threshold: 3
Describe the bugWhen attempting to connect, I get "Failed to connect", username/email is all lowercase. Debug log |
|
I was able to avoid the authentication issue after finding this:
|
|
Trying to add my P110 plugs and get the same error |
|
I was experiencing the same issues. My tapo registered email address has both upper and lower case characters. You must enter this exactly as seen into the TAPO HACS Controller when adding a new device. |
|
Exactly the same thing happens to me. I can't connect and I have entered the correct data. |
|
I have similar auth issue (maybe invalid credentials, Failed to setup cannot connect) ` ` and also: ` ` |
|
works whit p110 but no work whit h100 hub: 2024-04-23 23:44:26.027 ERROR (MainThread) [custom_components.tapo.config_flow] Failed to setup cannot connect The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
I had a similar issue, but I discovered that TP-Link had capitalized the first letter of my email address, which was not visible on the app where all letters were small. This issue was only visible when I logged into the TP-Link Cloud website. The issue was resolved once I changed the email in the code to the capitalized first letter. This problem occurred while using the Tapo PyPi library based on petretiandera on a Smartplug P115. |
|
Yep, same problem as reported above recently.
|
Thank you, i added successfully 4 P110 devices, but the 5th one was somehow returning invalid handshakes. Checked the registered email, everything OK lowercase. Then tried to change the cloud password as you said, and finally was able to add it. |
|
Same issue "Invalid authentication: Server response doesn't match our challenge" P110M Tried resetting, removing, and rebooting HA loads of times...didn't work. Solution, in this order: Madness eh...yes I wasted over an hour trying everything above individually lol...but that kitchen sink sequence worked. ...oh yeah, breaks other devices added previously, but new password added those back in without any hassle.. |
Had the same issue here, and ended up just using the admin page to reset the account password and it all worked. |
|
I Cant Connect my Tapo C200 Camera it says „Invalid cloud password. Make sure you are entering the password for your cloud account and NOT the password which you created via the camera settings (unless they are the same). You need to enter password which you used with your email when signing into the Tapo app.“ My Password is correct i changed it just to be sure. |
|
My P110s are working now after a few steps:
|
|
Sorry, aber das kann doch nicht die Lösung sein. Ich muss die ganze Zeit meine Cameras (Tapo C210 und Tapo C310) zurücksetzen und das Passwort ändern, dazu habe ich keine Lust. Nach nicht mal einer Stunde tritt der Fehler dann wieder auf ….. Das muss doch softwareseitig bei Tapo zu lösen sein, also bei der HA-Integration. Sorry, but that can't be the solution. I have to reset my cameras (Tapo C210 and Tapo C310) all the time and change the password, I don't feel like it. After not even an hour the error occurs again ..... This must be solved on the software side at Tapo, i.e. with the HA integration |
|
Where is the login credentials located locally? |
|
I was encountering this issue myself with a P115. Using the integration and trying to login with The case sensitiveness applies at the Name -- or at least that's how i managed to get it working. |
|
21:15 - Had an issue using an exotic password: UTskA1C?v39z^HY!GiX.2$fs"|I5X9tH Changing it to letters and numbers only fixed it for me. 21:54 - UPDATE: Only worked for the items that were linked in the app Adding a new item failed again. I think I will do a password update to check if it works twice. 22:20 - UPDATE Change the password for the second time seems to do the trick. As a wrap up I would strongly recommend that you first add all your devices in the Tapo app and then add them to HA. |
|
How does the 2-factor authentication play a role in making connection? |
|
Not at all |
and others
Version of the custom_component
Any
Describe the bug
A lot of people receive an "Invalid authentication" error message. Thanks to #120 and @mostlyvirtual, we have found an issue regarding username with capital letters. As reported by the user, in Tapo App settings is shown the email address, if this address contains capital letter, you probably receive "Invalid authentication" error from integration. In #120 they resolved by creating another account using an email all lower-case. In this way, the integration works.
So actually, only lower case E-mail works. I will investigate on this and fix asap
EDIT: Thanks to @rfnunes. When entering email, use the same case as seen in Tapo App.
The text was updated successfully, but these errors were encountered: