Invalid cloud password sins last update

[koenraadhaedens]

Description

after updating my Tapo integration. I can not get past the cloud password. Did verify with the tapo app on phone and even reset the password but still no luck

Reproduction Steps

after providing the local username and password I get prompted for the cloud password. When providing the correct cloud password i got Invalid cloud password

Expected behavior

that it would work

If applicable, add error logs.

No response

Device Firmware

1,3,9 build 231019 rel.40264n(4555)

Integration Version

5,4,12

Using stream component

Yes

Does camera work via official integrations?

Yes

Camera has all attributes filled out in developer tools

Yes

HASS Environment

homeassitant

Search for similar issues

Yes

Additional information

No response

[JurajNyiri]

What version did you update from? Do you have camera blocked in firewall?

[JurajNyiri]

Post debug logs.

[koenraadhaedens]

Is solved now. I read a post that only the original password is saved in the camera removing the camera from the tapo app and re-adding worked.

[bitcrumb]

Same issue here. Just upgraded and now cloud password is required (but I don’t have a cloud account).

Log details (WARNING)

Logger: homeassistant.config_entries
Source: config_entries.py:426
First occurred: November 21, 2023 at 23:54:39 (2 occurrences)
Last logged: 00:11:35

Config entry '192.168.100.200' for tapo_control integration could not authenticate: Invalid authentication data

[JurajNyiri]

It is the tplink account password.

[bitcrumb]

Well. The weird thing is, that password was not considered to be OK. So that made me thing that this dialog was talking about another account.

After your reaction I tried logging in on tplinkcloud.com and that does work.

So eventually I did what Koen said above: removed the camera via the Tapo app & re-onboarded it. After that the password was accepted. Note that I did not change the password in the meantime & tried several times (no typo's since I use a password manager and always verified).

Not sure if a reboot could have helped... but here we are :)

All in all this feels like a bug (not necesseraly in this integration).