Invalid authentication

Question

Invalid authentication

petretiandrea opened this issue 2 years ago · comments

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.

rfnunes · Answer 1 · Wed Feb 02 2022 23:29:05 GMT+0800 (China Standard Time)

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.

Greg Zajac · Answer 2 · Sat Feb 05 2022 00:01:59 GMT+0800 (China Standard Time)

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.
I even changed my e-mail address, my username for camera and nothing works

petretiandrea · Answer 3 · Thu Feb 10 2022 16:17:36 GMT+0800 (China Standard Time)

@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()

chconil · Answer 4 · Wed Feb 16 2022 17:54:27 GMT+0800 (China Standard Time)

Hi there,
Not sure it helps, but maybe it will :-) I remember from I-don't-know-where, that the devices store the password when they first get added to the Tapo App. If you change your password later, it's still the initial one in the device!
Deleting/re-adding the devices in the app updates the password to the latest one.
Good luck!
Christophe

Francesco · Answer 5 · Tue Feb 22 2022 02:57:34 GMT+0800 (China Standard Time)

Hello,
Thanks for this integration.
I encounter an ''Invalid authentication'' (my email is all lower case).

I would like to use my Home Assistant (located in my house) to control a P100 switch (located in my office).
Does this integration work via cloud?
Or does it need to work in the same LAN?
Thank you,

gpbicego · Answer 6 · Tue Feb 22 2022 19:34:51 GMT+0800 (China Standard Time)

Hello
I had an "Invalid Authentication" problem with version 1.2.8, but v1.2.4 works fine.

petretiandrea · Answer 7 · Tue Feb 22 2022 23:47:28 GMT+0800 (China Standard Time)

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

petretiandrea · Answer 8 · Tue Feb 22 2022 23:52:32 GMT+0800 (China Standard Time)

Hello, Thanks for this integration. I encounter an ''Invalid authentication'' (my email is all lower case).

I would like to use my Home Assistant (located in my house) to control a P100 switch (located in my office). Does this integration work via cloud? Or does it need to work in the same LAN? Thank you,

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)

Francesco · Answer 9 · Sun Feb 27 2022 18:03:03 GMT+0800 (China Standard Time)

Thanks Andrea.
It would be useful to be able to manage this integration in Cloud Polling.
Thank's for your job

Karl Wilde · Answer 10 · Sat Mar 05 2022 20:37:08 GMT+0800 (China Standard Time)

Auth issue as well - p/w and ID all lower case.

rfnunes · Answer 11 · Sat Mar 05 2022 21:27:49 GMT+0800 (China Standard Time)

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.

Karl Wilde · Answer 12 · Sun Mar 06 2022 20:18:13 GMT+0800 (China Standard Time)

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.

petretiandrea · Answer 13 · Tue Mar 08 2022 04:35:30 GMT+0800 (China Standard Time)

This has stopped working for me too. In my case, after updating to HA 2022.3. Have tried removing and installing the integration, changing cam's user password, user and password...

No luck at all. Haven't seen logs about the error.

Any idea on what to try?

Why are you talking about cams? This integration doesn't support cameras

Luis Alberto Pérez García · Answer 14 · Tue Mar 08 2022 07:00:12 GMT+0800 (China Standard Time)

My bad, just got to the wrong repo.

Sorry!

vindbrann · Answer 15 · Tue Mar 22 2022 23:49:21 GMT+0800 (China Standard Time)

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 can't add the L900 back with the authentication error. (No capital in my email adress).
I removed the intergration, installed back and it works.

Daniel Carl Jones · Answer 16 · Wed May 04 2022 02:50:56 GMT+0800 (China Standard Time)

I'm seeing transient failure here too. My e-mail contains a +.

I tried reaching the device using the plugp100 package directly. When it wasn't working, I'd get:

aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.153:80 ssl:default [Connect call failed ('191.168.1.153', 80)]

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.

chrisuk-web · Answer 17 · Wed May 04 2022 22:11:40 GMT+0800 (China Standard Time)

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)]

chrisuk-web · Answer 18 · Thu May 05 2022 01:00:32 GMT+0800 (China Standard Time)

Ok it worked - didn't seem to like an upper case letter in the password. IP address was that of the device.

josecarlospaulo · Answer 19 · Tue May 17 2022 17:33:43 GMT+0800 (China Standard Time)

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
“switch:
platform: tapo_p100_control
ip_address: 192.168.x.x
email: email@gmail.com
password: Password123”
Putting the ip of p100 my personal email and a new password and i already restart the HA and nothing changed still having the same error.
Btw i downloaded from here “GitHub - petretiandrea/home-assistant-tapo-p100: A custom integration to control Tapo devices from home assistant. 1”.
And i am using the home assistant core on ubuntu lastest version btw.
Thanks for the help.

Richard Scott · Answer 20 · Tue Jun 07 2022 20:52:33 GMT+0800 (China Standard Time)

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.

viba1 · Answer 21 · Sat Jun 18 2022 02:36:23 GMT+0800 (China Standard Time)

Previously same problem.
Fixed using the last 1.2.12 version.

Configuration :

Home Assistant Core 2022.6.6 installed via docker method
home-assistant-tapo-p100 1.2.12 installed via "Manual way"
TAPO L530 in both 1.0 (with 1.2.2 firmware) and 2.0 (with 1.0.8 firmware)

What works:

after reloading the home assistant container, "Tapo Controller" is well recognized and seems functional (GUI loads)
host: 192.168.x.x
username: xxx@xxx.xxx (no special character, no uppercase)
password: xxxx (no special constraint identified)

Thanks for this update and your great job!

jackielegs98 · Answer 22 · Sat Jun 25 2022 11:48:11 GMT+0800 (China Standard Time)

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.

Ihab · Answer 23 · Sun Jun 26 2022 12:50:59 GMT+0800 (China Standard Time)

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:
Config flow could not be loaded: undefined
Any suggestions?

stain3565 · Answer 24 · Mon Jun 27 2022 20:03:55 GMT+0800 (China Standard Time)

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).
Now, 5 have not connected in the integration. I have tried reloading but to no avail. The plugs are working in the Tapo app so the issue is in the Home Assistant integration. I did want to add 4 more plugs but these are failing too.
I had not changed any of the existing plugs in the app (editing did seem to be some form of issue before) so now am struggling to logically explain the reason why some work and some don't.

The logs are below (after a reload - same every time):

`Logger: homeassistant.config_entries
Source: config_entries.py:370
First occurred: 23:02:28 (18 occurrences)
Last logged: 23:32:36

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
Config entry 'Tapo 5' for tapo integration not ready yet: None; Retrying in background
Config entry 'Tapo 1 - TV2' for tapo integration not ready yet: None; Retrying in background
Config entry 'Tapo 4' for tapo integration not ready yet: None; Retrying in background
Config entry 'Tapo 7 - TV1' for tapo integration not ready yet: None; Retrying in background`

petretiandrea · Answer 25 · Fri Jul 01 2022 01:05:43 GMT+0800 (China Standard Time)

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:
Config flow could not be loaded: undefined
Any suggestions?

Pc os? Architecture?

Ihab · Answer 26 · Wed Jul 06 2022 00:41:56 GMT+0800 (China Standard Time)

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:
Config flow could not be loaded: undefined
Any suggestions?

Pc os? Architecture?

can i add log details for ERROR here?
Thank u

nithikalisamy · Answer 27 · Thu Jul 07 2022 22:09:39 GMT+0800 (China Standard Time)

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,

Removed the device and added it again to the existing email.
Even though my email had lower cases, I created a new email id for the Tapo account and configured the device.
Changed pwd to lower cases too and tried but no luck.
Changed the device host IP to a different one.

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,
Home Assistant Core: 2022.6.7
Home Assistant Supervisor: 2022.7.0

aialenti · Answer 28 · Sat Jul 09 2022 07:08:36 GMT+0800 (China Standard Time)

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:

Traceback (most recent call last):
  File "/config/custom_components/tapo/config_flow.py", line 58, in async_step_user
    entry_metadata = await self._validate_input(user_input)
  File "/config/custom_components/tapo/config_flow.py", line 91, in _validate_input
    tapo_api = await self._test_credentials(
  File "/config/custom_components/tapo/config_flow.py", line 110, in _test_credentials
    await client.login()
  File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 84, in login
    await self._handshake()
  File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 157, in _handshake
    resp_dict = await response.json()
  File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1103, in json
    raise ContentTypeError(
aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('http://192.168.x.x/app')

It looks like something that should be handled in the library that calls the API

nithikalisamy · Answer 29 · Sat Jul 09 2022 08:55:36 GMT+0800 (China Standard Time)

It looks like something that should be handled in the library that calls the API

I think its related to Issue#199 and Python 3.10 support not yet available for this integration on HA core 2022.7.x versions.

VictoriousCupid · Answer 30 · Sat Jul 09 2022 23:53:45 GMT+0800 (China Standard Time)

worked until issue#199. after this was resolved the invalid authentication issue popped up for me.

email is only lowercase letters
Home Assistant 2022.7.2
Supervisor 2022.07.0
Operating System 8.2
Frontend 20220707.0 - latest
Running in VM on proxmox

Readded the p100 plug to the app - no fix
redownloaded repo - no fix

liamlain · Answer 31 · Sun Jul 10 2022 01:12:18 GMT+0800 (China Standard Time)

same getting "Invalid authentication" error message
email-lowercase
Home Assistant 2022.7.2
Supervisor 2022.07.0
Operating System 8.2
Rpi4

look like P110 no problem adding. only the P100 getting error message

FilipeLeite · Answer 32 · Sun Jul 10 2022 02:03:14 GMT+0800 (China Standard Time)

same getting "Invalid authentication" error message email-lowercase Home Assistant 2022.7.2 Supervisor 2022.07.0 Operating System 8.2 Rpi4

look like P110 no problem adding. only the P100 getting error message

Same problem here. P110 all good, P100 invalid authentication.

pietrouk · Answer 33 · Sun Jul 10 2022 03:09:04 GMT+0800 (China Standard Time)

Same authentication issue for me on Raspberry Pi 4 -
Home Assistant 2022.7.2
Supervisor 2022.07.0
Operating System 8.2
Frontend 20220707.0 - latest
Tapo Controller v1.2.13

@petretiandrea this is possibly a different issue as my email has no capital letters, also everything had worked fine until update to v1.2.13 and 2022.7.2

irarkh · Answer 34 · Sun Jul 10 2022 18:34:59 GMT+0800 (China Standard Time)

Hi there, same issue here. No capital letters in email. Everything worked fine until recent upgrade for supporting HA v7.0. Both topics referred to each other but I could not manage to solve auth error problem.

Solved After different tests I managed to add my tapo p100 back in HA. First I remove n add in tapo add without success in adding back in HA. Same auth error! Then, I changed my tapo app password. remove device in tapo app and add it back. Finally, could add the device back in HA. Hope helps people with the same issue.

Viderek · Answer 35 · Sun Jul 10 2022 20:30:56 GMT+0800 (China Standard Time)

Hi there, same issue here. No capital letters in email. Everything worked fine until recent upgrade for supporting HA v7.0. Both topics referred to each other but I could not manage to solve auth error problem.

Solved After different tests I managed to add my tapo p100 back in HA. First I remove n add in tapo add without success in adding back in HA. Same auth error! Then, I changed my tapo app password. remove device in tapo app and add it back. Finally, could add the device back in HA. Hope helps people with the same issue.

Thank you! It worked. I managed to get things working too, by changing the password not to include capital letters and re-adding all devices in the Tapp app.

FilipeLeite · Answer 36 · Mon Jul 11 2022 01:46:39 GMT+0800 (China Standard Time)

For me, nothing worked. Only Tapo P110 works, Tapo 100 doesn't (tried to change password, remove and add tapo in tapo app).

pietrouk · Answer 37 · Mon Jul 11 2022 06:09:34 GMT+0800 (China Standard Time)

Tried the suggestion of changing the password and readding the plugs to the Tapo app, still not working.

petretiandrea · Answer 38 · Mon Jul 11 2022 14:59:16 GMT+0800 (China Standard Time)

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:

Traceback (most recent call last):
  File "/config/custom_components/tapo/config_flow.py", line 58, in async_step_user
    entry_metadata = await self._validate_input(user_input)
  File "/config/custom_components/tapo/config_flow.py", line 91, in _validate_input
    tapo_api = await self._test_credentials(
  File "/config/custom_components/tapo/config_flow.py", line 110, in _test_credentials
    await client.login()
  File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 84, in login
    await self._handshake()
  File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 157, in _handshake
    resp_dict = await response.json()
  File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1103, in json
    raise ContentTypeError(
aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('http://192.168.x.x/app')

It looks like something that should be handled in the library that calls the API

version of plugp100?

FilipeLeite · Answer 39 · Mon Jul 11 2022 16:12:17 GMT+0800 (China Standard Time)

Mine is:
Tapo P100
Hardware version: 1.20.0
Firmware version: 1.4.10 Build 20211104 Rel. 35882

neildsb · Answer 40 · Mon Jul 11 2022 16:29:40 GMT+0800 (China Standard Time)

+1, change the password (no caps, 8 digit long) and email (no underscore) always invalid

Plugs P100

1.2.13

Home Assistant 2022.7.3
Supervisor 2022.07.0
Operating System 8.2
Frontend 20220707.0 - latest

petretiandrea · Answer 41 · Mon Jul 11 2022 16:42:23 GMT+0800 (China Standard Time)

Mine is: Tapo P100 Hardware version: 1.20.0 Firmware version: 1.4.10 Build 20211104 Rel. 35882

I mean version of plugp100 library, is 2.1.17? Or alternatively, is integration version 1.2.13?

FilipeLeite · Answer 42 · Mon Jul 11 2022 16:44:09 GMT+0800 (China Standard Time)

Mine is: Tapo P100 Hardware version: 1.20.0 Firmware version: 1.4.10 Build 20211104 Rel. 35882

I mean version of plugp100 library, is 2.1.17? Or alternatively, is integration version 1.2.13?

Yes, its 1.2.13

neildsb · Answer 43 · Mon Jul 11 2022 16:44:34 GMT+0800 (China Standard Time)

Mine is: Tapo P100 Hardware version: 1.20.0 Firmware version: 1.4.10 Build 20211104 Rel. 35882

I mean version of plugp100 library, is 2.1.17? Or alternatively, is integration version 1.2.13?

Yes, its 1.2.13

same here 1.2.13

VictoriousCupid · Answer 44 · Mon Jul 11 2022 16:50:03 GMT+0800 (China Standard Time)

Mine is: Tapo P100 Hardware version: 1.20.0 Firmware version: 1.4.10 Build 20211104 Rel. 35882

I mean version of plugp100 library, is 2.1.17? Or alternatively, is integration version 1.2.13?

Yes, its 1.2.13

same here 1.2.13

Idem. Also attempted the above mentioned solution. No joy.

petretiandrea · Answer 45 · Mon Jul 11 2022 16:50:03 GMT+0800 (China Standard Time)

By using this script here https://github.com/petretiandrea/plugp100 you can turn on device?

neildsb · Answer 46 · Mon Jul 11 2022 17:27:40 GMT+0800 (China Standard Time)

even tried 1.2.13 with Home Assistant Core 2022.6.7 no luck, and all lowercase Password

Colster69 · Answer 47 · Mon Jul 11 2022 18:05:58 GMT+0800 (China Standard Time)

Same issue here, only thing to add is my plugs are ok but the bulb shows the invalid auth. Tried with email and password all lower case, same issue

petretiandrea · Answer 48 · Mon Jul 11 2022 18:08:28 GMT+0800 (China Standard Time)

Same issue here, only thing to add is my plugs are ok but the bulb shows the invalid auth. Tried with email and password all lower case, same issue

I think that this problem is related only to Tapo Device configuration, which in some way is not "synced" with your cloud username/password. If plug works, there is no reason that break bulbs (in terms of my library). Please guys, reports a log, without it, I can't help

Sam Ross · Answer 49 · Mon Jul 11 2022 18:08:30 GMT+0800 (China Standard Time)

Having the same issues:

Removed devices (P100) from tapo app
Reset password (8 chars - lowercase & numbers only)
Re-added devices
Removed integration from HA
Restarted HA
Installed HACS repo
Restarted HA
Located Tapo_Controller integration in HA
Entered ip address as shown in tapo app (matches on router config)
Entered email (all lowercase - matches tapo app)
Entered new password

component version 1.2.13
HA Core version 2022.7.3

"Invalid Authentication"

petretiandrea · Answer 50 · Mon Jul 11 2022 18:09:12 GMT+0800 (China Standard Time)

Having the same issues:

Removed devices (P100) from tapo app

Reset password (8 chars - lowercase & numbers only)

Re-added devices

Removed integration from HA

Restarted HA

Installed HACS repo

Restarted HA

Located Tapo_Controller integration in HA

Entered ip address as shown in tapo app (matches on router config)

Entered email (all lowercase - matches tapo app)

Entered new password

component version 1.2.13 HA Core version 2022.7.3

"Invalid Authentication"

logs?

Sam Ross · Answer 51 · Mon Jul 11 2022 18:24:41 GMT+0800 (China Standard Time)

Having the same issues:

Removed devices (P100) from tapo app

Reset password (8 chars - lowercase & numbers only)

Re-added devices

Removed integration from HA

Restarted HA

Installed HACS repo

Restarted HA

Located Tapo_Controller integration in HA

Entered ip address as shown in tapo app (matches on router config)

Entered email (all lowercase - matches tapo app)

Entered new password

component version 1.2.13 HA Core version 2022.7.3

"Invalid Authentication"

logs?

When I attempt to add and get the "Invalid Authentication" message I don't get anything in the logs

Colster69 · Answer 52 · Mon Jul 11 2022 18:36:01 GMT+0800 (China Standard Time)

Same issue here, only thing to add is my plugs are ok but the bulb shows the invalid auth. Tried with email and password all lower case, same issue

I think that this problem is related only to Tapo Device configuration, which in some way is not "synced" with your cloud username/password. If plug works, there is no reason that break bulbs (in terms of my library). Please guys, reports a log, without it, I can't help

Because the device is not added, there isn't much to see in logs

_```
This error originated from a custom integration.

Logger: custom_components.tapo.common_setup
Source: helpers/update_coordinator.py:237
Integration: tapo_p100 (documentation, issues)
First occurred: 10:26:05 AM (1 occurrences)
Last logged: 10:26:05 AM

Error fetching tapo data:

Colster69 · Answer 53 · Mon Jul 11 2022 18:59:32 GMT+0800 (China Standard Time)

I tried removing all devices (2 plugs (P100) and 1 bulb (L150)) and the first bulb added fine, the next one gives me this:

Unexpected exception
Traceback (most recent call last):
File "/config/custom_components/tapo/config_flow.py", line 57, in async_step_user
entry_metadata = await self._validate_input(user_input)
File "/config/custom_components/tapo/config_flow.py", line 94, in _validate_input
state = await tapo_api.get_state()
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 89, in get_state
state=await self.get_state_as_dict(),
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 213, in get_state_as_dict
return await self._execute_method_request(device_info_method)
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 233, in _execute_method_request
response = await self.http.async_make_post_cookie(f"{self.url}?token={self.token}", request_body,
File "/usr/local/lib/python3.10/site-packages/plugp100/core/http_client.py", line 19, in async_make_post_cookie
async with self.session.post(url, json=json, cookies=cookie) as response:
File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 1138, in aenter
self._resp = await self._coro
File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 559, in _request
await resp.start(conn)
File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 898, in start
message, payload = await protocol.read() # type: ignore[union-attr]
File "/usr/local/lib/python3.10/site-packages/aiohttp/streams.py", line 616, in read
await self._waiter
aiohttp.client_exceptions.ClientOSError: [Errno 104] Connection reset by peer

I get an unexpected error when adding that and an auth error when adding the bulb. Only thing I could see as different between the bulbs in the last octet of the IP address was 2 digits for the device that adds ok and 3 for the other plug and the bulb

petretiandrea · Answer 54 · Mon Jul 11 2022 19:32:58 GMT+0800 (China Standard Time)

I tried removing all devices (2 plugs (P100) and 1 bulb (L150)) and the first bulb added fine, the next one gives me this:

Unexpected exception
Traceback (most recent call last):
File "/config/custom_components/tapo/config_flow.py", line 57, in async_step_user
entry_metadata = await self._validate_input(user_input)
File "/config/custom_components/tapo/config_flow.py", line 94, in _validate_input
state = await tapo_api.get_state()
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 89, in get_state
state=await self.get_state_as_dict(),
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 213, in get_state_as_dict
return await self._execute_method_request(device_info_method)
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 233, in _execute_method_request
response = await self.http.async_make_post_cookie(f"{self.url}?token={self.token}", request_body,
File "/usr/local/lib/python3.10/site-packages/plugp100/core/http_client.py", line 19, in async_make_post_cookie
async with self.session.post(url, json=json, cookies=cookie) as response:
File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 1138, in aenter
self._resp = await self._coro
File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 559, in _request
await resp.start(conn)
File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 898, in start
message, payload = await protocol.read() # type: ignore[union-attr]
File "/usr/local/lib/python3.10/site-packages/aiohttp/streams.py", line 616, in read
await self._waiter
aiohttp.client_exceptions.ClientOSError: [Errno 104] Connection reset by peer

I get an unexpected error when adding that and an auth error when adding the bulb. Only thing I could see as different between the bulbs in the last octet of the IP address was 2 digits for the device that adds ok and 3 for the other plug and the bulb

Even UI shows invalid authentication, the logs suggest another type of error, likes device is not responding. Have you set static ip for your device?

Colster69 · Answer 55 · Mon Jul 11 2022 20:07:46 GMT+0800 (China Standard Time)

Tried making it static, changing it to something other than the original IP and removing it from Tapo app and re-adding. The other plug has added ok now (that has a 3 digit last octet and only DHCP). Still getting the same error on the bulb

petretiandrea · Answer 56 · Mon Jul 11 2022 21:52:30 GMT+0800 (China Standard Time)

Tried making it static, changing it to something other than the original IP and removing it from Tapo app and re-adding. The other plug has added ok now (that has a 3 digit last octet and only DHCP). Still getting the same error on the bulb

Stupid question: where you take the ip of device? From tapo app or from router page? Can you ping the devices with right ip?

VictoriousCupid · Answer 57 · Mon Jul 11 2022 21:54:58 GMT+0800 (China Standard Time)

Tried making it static, changing it to something other than the original IP and removing it from Tapo app and re-adding. The other plug has added ok now (that has a 3 digit last octet and only DHCP). Still getting the same error on the bulb

Stupid question: where you take the ip of device? From tapo app or from router page? Can you ping the devices with right ip?

Since I have identical results I can answer as well. Tapo app, router same info. Ping positive return. The IP address used does definitely point to the plug.

Colster69 · Answer 58 · Mon Jul 11 2022 21:59:55 GMT+0800 (China Standard Time)

Tried making it static, changing it to something other than the original IP and removing it from Tapo app and re-adding. The other plug has added ok now (that has a 3 digit last octet and only DHCP). Still getting the same error on the bulb

Stupid question: where you take the ip of device? From tapo app or from router page? Can you ping the devices with right ip?

Since I have identical results I can answer as well. Tapo app, router same info. Ping positive return. The IP address used does definitely point to the plug.

Yep same for me. Ping is ok and app and router agree on the IP

petretiandrea · Answer 59 · Mon Jul 11 2022 22:02:37 GMT+0800 (China Standard Time)

Ok, firmware info and hardware version of tapo? You take a screenshot from tapo app

Colster69 · Answer 60 · Mon Jul 11 2022 22:04:10 GMT+0800 (China Standard Time)

Ok, firmware info and hardware version of tapo? You take a screenshot from tapo app

VictoriousCupid · Answer 61 · Mon Jul 11 2022 22:04:27 GMT+0800 (China Standard Time)

VictoriousCupid commented 2 years ago

sandimartian · Answer 62 · Mon Jul 11 2022 22:55:25 GMT+0800 (China Standard Time)

Same problem here with two P100 plugs, static IPs, respond to ping

.

VictoriousCupid · Answer 63 · Mon Jul 11 2022 23:07:35 GMT+0800 (China Standard Time)

I thought to be clever for the time being and ad my 1 plug to Alexa and expose a input boolean from home assistant as well. Like that theoretically, with a routine for on and a routine for off, I should be able to switch the plug. Theory is sound, it works.... For a few minutes.

Now Alexa is incapable or reaching the plug. Re-adding doesn't work. Plug not found.

I have no clue if this is related, and if so how. But it might be worth to share here.

petretiandrea · Answer 64 · Mon Jul 11 2022 23:31:56 GMT+0800 (China Standard Time)

Please read this #206 (comment)

m-toso · Answer 65 · Tue Jul 12 2022 02:40:47 GMT+0800 (China Standard Time)

Maybe it can help someone.
Password with upper case and special characters does not work.
Password without upper case and special characters does not work.
Password without upper case and without special characters works.
I didn't have to remove and add devices from the tapo app.

FilipeLeite · Answer 66 · Tue Jul 12 2022 03:18:34 GMT+0800 (China Standard Time)

I don’t know what is failling but in the same account i have tapo P110 and is working…

Colster69 · Answer 67 · Tue Jul 12 2022 15:54:16 GMT+0800 (China Standard Time)

Maybe it can help someone. Password with upper case and special characters does not work. Password without upper case and special characters does not work. Password without upper case and without special characters works. I didn't have to remove and add devices from the tapo app.

Tried that, my plugs work but still not the bulb

FilipeLeite · Answer 68 · Tue Jul 12 2022 16:17:30 GMT+0800 (China Standard Time)

Maybe it can help someone.
Password with upper case and special characters does not work.
Password without upper case and special characters does not work.
Password without upper case and without special characters works.
I didn't have to remove and add devices from the tapo app.

O don’t know how you change password without special characters. When I try to change it, I get an error saying it's mandatory.
Also, it was the password I had before and it worked. Now only the P110 works the P100, don’t.

SkoobyDu · Answer 69 · Tue Jul 12 2022 16:48:42 GMT+0800 (China Standard Time)

I seem to have tried all options and my p100's are still failing to authenticate; nothing of consequence in the logs. Something to note is that the integration doesn't load and doesn't appear to retry.
Latest version of HA & TAPO integration.
I've also tried restoring from a previous full backup but that appears not to make any difference and my p100's remain unavailable.

stain3565 · Answer 70 · Wed Jul 13 2022 05:09:31 GMT+0800 (China Standard Time)

Since update to Home Assistant 2022.7, no P100s are available in Tapo Controller.

`Logger: homeassistant.config_entries
Source: config_entries.py:384
First occurred: 21:56:27 (14 occurrences)
Last logged: 22:07:38

Config entry 'Tapo 8' for tapo integration not ready yet: None; Retrying in background
Config entry 'Tapo 2 - Wholehome' for tapo integration not ready yet: None; Retrying in background
Config entry 'Tapo 4' for tapo integration not ready yet: None; Retrying in background
Config entry 'Pantry KL110(EU)' for tplink integration not ready yet: Unable to connect to the device: 192.168.1.74: [Errno 113] Connect call failed ('192.168.1.74', 9999); Retrying in background
Config entry 'Tapo 6 - Network hub' for tapo integration not ready yet: None; Retrying in background`

stain3565 · Answer 71 · Wed Jul 13 2022 05:39:39 GMT+0800 (China Standard Time)

stain3565 commented 2 years ago

petretiandrea · Answer 72 · Wed Jul 13 2022 06:24:17 GMT+0800 (China Standard Time)

The issue is related to hardware 2.0 versio. There Is another issue alredy opened about this.

Rudaro · Answer 73 · Wed Jul 13 2022 15:00:34 GMT+0800 (China Standard Time)

I have been having the same issue since updating to Home Assistant 2022.7 - Failed Authentication.

However, my P100s started working immediately after updating Tapo Controller to version 1.2.14 (was on 1.2.13 before). Also, I have the following Hardware and Firmware versions for 2 P100 plugs:

Hardware Version - 1.20.0
Firmware Version - 1.4.10 Build 20211104 Rel. 35882

@petretiandrea - Thanks for sorting it out (at least for me)!

pietrouk · Answer 74 · Wed Jul 13 2022 17:14:14 GMT+0800 (China Standard Time)

@petretiandrea - Thanks for the update! The authentication issue is now gone and both my p100 plugs are working

Sam Ross · Answer 75 · Wed Jul 13 2022 18:13:12 GMT+0800 (China Standard Time)

@SkoobyDu

#209

As described in the above (now closed) issue a number of people have resolved their problem with an update to the latest version of Tapo Controller.

GeoffMorg · Answer 76 · Wed Jul 13 2022 18:42:22 GMT+0800 (China Standard Time)

I'm pretty sure I'd contributed to this thread saying I had the same problem but I can't find it now.

Whatever, this new update of the integration 1.12.14 has corrected the issue and I added my L530 light first time :-)

Thanks

Colster69 · Answer 77 · Wed Jul 13 2022 19:26:10 GMT+0800 (China Standard Time)

I'm pretty sure I'd contributed to this thread saying I had the same problem but I can't find it now.

Whatever, this new update of the integration 1.12.14 has corrected the issue and I added my L530 light first time :-)

Thanks

Yes, same here. The new update allowed my bulb to add first time after updating. Thanks @petretiandrea

stain3565 · Answer 78 · Fri Jul 15 2022 07:57:10 GMT+0800 (China Standard Time)

The issue is related to hardware 2.0 versio. There Is another issue alredy opened about this.

Can you tell me the issue number please

aukdev · Answer 79 · Sat Aug 06 2022 22:25:39 GMT+0800 (China Standard Time)

Just very quick post as I was having a similar issue. Don't have time to read whole thread but have search 2FA and Two Fac... with no result. I don't suppose your TP-Link Cloud accounts have 2FA enabled, as reluctantly removing this was the solution here and thought this might help someone if not covered already?

jsuelwald · Answer 80 · Sun Aug 07 2022 13:13:01 GMT+0800 (China Standard Time)

TapoP110 in use here (Firmware 1.0.7).
IP is static (192.168.0.218)
reset user & password -> still "Invalid auth"

What am I doing wrong here?

jsuelwald · Answer 81 · Wed Aug 10 2022 18:33:22 GMT+0800 (China Standard Time)

PS: My email adress was all lowercase.

Francesco Raiola · Answer 82 · Thu Aug 11 2022 14:42:23 GMT+0800 (China Standard Time)

This has stopped working for me too. In my case, after updating to HA 2022.3. Have tried removing and installing the integration, changing cam's user password, user and password...
No luck at all. Haven't seen logs about the error.
Any idea on what to try?

Why are you talking about cams? This integration doesn't support cameras

Well the Cam like the C200 use the same application and I am assuming the same password? For example I am able to connect and integrate the C200 camera with the same username (first side of the e-mail) and password but no the two smart plugs P100 and P110.

Francesco Raiola · Answer 83 · Mon Aug 15 2022 21:28:09 GMT+0800 (China Standard Time)

This has stopped working for me too. In my case, after updating to HA 2022.3. Have tried removing and installing the integration, changing cam's user password, user and password...
No luck at all. Haven't seen logs about the error.
Any idea on what to try?

Why are you talking about cams? This integration doesn't support cameras

Well the Cam like the C200 use the same application and I am assuming the same password? For example I am able to connect and integrate the C200 camera with the same username (first side of the e-mail) and password but no the two smart plugs P100 and P110.

No, finally I integrate the Tapo P110 using the email and the new password. One thing I did, was to reinstall one of the device and the system finally accepted the new password. Funny enough the Tapo integration recognized the P110 while actually I just reinstalled only the P100. I will try to do the same with the P110 and see if it will work for P100.

Bloch-Boas · Answer 84 · Tue Aug 16 2022 16:11:26 GMT+0800 (China Standard Time)

Confirmed...

I removed both my plugs in the app, and readded them, then I could connect to them via HA...

Konrad Lother · Answer 85 · Fri Aug 19 2022 18:02:10 GMT+0800 (China Standard Time)

I had an issue with authentication, too. it was because my password had more than 8 charackters. setting it to a password with the length of 8 charackter fixed it.

Hany1212 · Answer 86 · Mon Aug 22 2022 04:36:15 GMT+0800 (China Standard Time)

I solved the problem..there was a space after the email I deleted it and the problem was solved

martindell · Answer 87 · Tue Aug 30 2022 02:07:04 GMT+0800 (China Standard Time)

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()

Invalid authentication issues here - plus I get nothing from the above script (substituting my IP, use & pass)
If I run it from HA's terminal I get:
zsh: parse error near `)'
/ import asyncio
from plugp100 import TapoApiClient

If I run it as a bash script I get:
/ bash /config/tplink.sh
/config/tplink.sh: line 3: import: command not found
/config/tplink.sh: line 4: from: command not found
/config/tplink.sh: line 7: syntax error near unexpected token (' /config/tplink.sh: line 7: async def main():'

andrewcrook · Answer 88 · Fri Sep 02 2022 06:44:33 GMT+0800 (China Standard Time)

@martindell that’s Python code.

pobkac · Answer 89 · Sun Sep 04 2022 10:30:52 GMT+0800 (China Standard Time)

Hello, Thanks for taking the time to write this integration.
I also have the invalid authentication.
my email address is word.word1234@emailcompany.com
my password is 23 characters long only comprising of [a-z] (lower case only) and [0-9], no spaces, upper case or special characters.
Sorry but I can't find the tapo p-100 version but it "should" be the latest.
Running on a Raspberry Pi
Home Assistant 2022.8.7
Supervisor 2022.08.5
Operating System 8.5
Frontend 20220802.0 - latest

The Tapo P110 is hardware version 1.0
Firmware 1.0.11 Build 210926 Rel 155241

Is there any other information that you need?

pobkac · Answer 90 · Sun Sep 04 2022 10:34:55 GMT+0800 (China Standard Time)

As an experiment I tried removing the plug from the mobile phone app and then adding it into Home Assistant. This doesn't work as it resets the Tapo P110 and you need to reconfigure the WiFi connection on the plug. So need to keep the plug connected to the mobile phone app.

migube · Answer 91 · Mon Sep 05 2022 13:17:52 GMT+0800 (China Standard Time)

Note that I had a Firewall between HA & the P100, and it would give auth failed.
Maybe the error message could point out when the Tcp socket can't connect?
Note 2: What ports is it using? (I didn't tcpdump it yet :)
tx!

pobkac · Answer 92 · Mon Sep 05 2022 13:50:08 GMT+0800 (China Standard Time)

hello again.
migube, I'm not sure if you making a comment to me, but my HA and P110 are on the same network segment, which is a dedicated IoT segment.
But you do raise something, as my firewall is only permitting the P110 to access two IP addresses.
54.72.86.3 from "https://community.home-assistant.io/t/tp-link-tapo-p110-energy-monitoring-not-possible-without-cloud-access/388688"
52.221.133.55 "from wireshark"
I'm not sure if this could have an impact.

I have also tried reducing the password length with out success.
I have removed the P110 from the app, reset my password to 8 characters in length, using lower & uppercase, numbers and basic special characters. re-added the P110 to the app and then tried to add the integration in HA. Same result "Invalid authentication"

Colin Robbins · Answer 93 · Tue Sep 06 2022 02:17:56 GMT+0800 (China Standard Time)

I am seeing the authentication error as well, and may be able to shed a bit more light on it. I do not have an capital letters etc.
I run home assistant in a python virtual environment.

I have two versions of hass, a development machine and a produiction machine.

On the development machine, the integration is working perfectly for a P110 plug.
Great stuff.

On the production machine I see the authentication error.

I've run the @martindell python code on my production linux box - it works fine.
HOWEVER, if I run the python code in the VENV that hass is running in I get an error...

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.9/site-packages/Crypto/PublicKey/RSA.py", line 121, in __getattr__
    return int(self._key[attrname])
KeyError: 'export_key'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/pi/tapo.py", line 13, in <module>
    loop.run_until_complete(main())
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "/home/pi/tapo.py", line 9, in main
    await sw.login()
  File "/srv/homeassistant/lib/python3.9/site-packages/plugp100/api.py", line 84, in login
    await self._handshake()
  File "/srv/homeassistant/lib/python3.9/site-packages/plugp100/api.py", line 145, in _handshake
    self.__generate_keypair()
  File "/srv/homeassistant/lib/python3.9/site-packages/plugp100/api.py", line 250, in __generate_keypair
    self.key_pair = self.encryption.generate_key_pair()
  File "/srv/homeassistant/lib/python3.9/site-packages/plugp100/core/encryption.py", line 19, in generate_key_pair
    private_key = key.export_key(pkcs=8, format="DER")
  File "/srv/homeassistant/lib/python3.9/site-packages/Crypto/PublicKey/RSA.py", line 123, in __getattr__
    raise AttributeError(attrname)
AttributeError: export_key
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0xb5268598>

So, my assertion is it is an issue with dependancies and the incorrect python modules being loaded in the hass environment.

So far I've not had any luck in finding out which...

robuk123 · Answer 94 · Thu Sep 08 2022 09:14:43 GMT+0800 (China Standard Time)

Hi, just to add.
Brand new install, no uppercase on either password or email and getting invalid authentication as well.

Only testing on one p100 plug with firmware version 1.0.5 build 210615 rel 135441

Hass is version:.(running on Raspberry PI 4 (4GB))
Home Assistant 2022.9.0
Supervisor 2022.08.5
Operating System 8.5
Frontend 20220907.0 - latest

I have tried adding with GUI and config.yaml neither work.

Colin Robbins · Answer 95 · Sat Sep 10 2022 23:57:42 GMT+0800 (China Standard Time)

In my case, I have solved the issue.
in my Python venv I ran...

pip3 -m pycryptodome -U

In theory it should not be needed. as HA should resolve the dependencies. However I have seen before with other integration, it does not always update to the latest version (I had an old version installed).

This may not be the cause of everyones issue, but it worked for me.

robuk123 · Answer 96 · Sun Sep 11 2022 19:47:56 GMT+0800 (China Standard Time)

In my case, I have solved the issue. in my Python venv I ran...
pip3 -m pycryptodome -U
In theory it should not be needed. as HA should resolve the dependencies. However I have seen before with other integration, it does not always update to the latest version (I had an old version installed).

This may not be the cause of everyones issue, but it worked for me.

Colin, for a complete noob at all of this, would you be able to provide some instructions on how to do this (assume no prior knowledge as I have little!). I can then try and feedback to see if this resolves my issue.
I am on a RaspberryPi if that makes any difference running:Home Assistant 2022.9.1
Supervisor 2022.08.6
Operating System 8.5
Frontend 20220907.0 - latest

Colin Robbins · Answer 97 · Sun Sep 11 2022 19:59:41 GMT+0800 (China Standard Time)

@robuk123, sorry not sure. I am running HA core, in a Python Venv. Whereas I think you are running the Supervisor version, which runs HA under Docker.
If you can login to the Docker image and get a shell, then the pip3 command may work in the shell.

Jezzerick · Answer 98 · Fri Sep 16 2022 00:16:40 GMT+0800 (China Standard Time)

Been trying to setup my L530 bulb and still getting this error. Email & password are all lowercase and host as device IP address. Not sure where it's going wrong

zgbee · Answer 99 · Sat Sep 24 2022 19:52:05 GMT+0800 (China Standard Time)

I was also able to resolve this by changing my password. The password that caused the authentication error was Z9LfEe2n3,P.L,j - I changed to a new password with only lowercase/numbers and was able to authenticate

Francesco Raiola · Answer 100 · Sat Sep 24 2022 19:57:30 GMT+0800 (China Standard Time)

I was also able to resolve this by changing my password. The password that caused the authentication error was Z9LfEe2n3,P.L,j - I changed to a new password with only lowercase/numbers and was able to authenticate

Sam for me, I solved the problem changing the password and using just lower case lettere and numbers. Also I had to reinitialized the devices (two plugs)