Issue #775 Related: Integration Only Accepts Original Password

[WxrthlessLiquid]

Description

I’ve encountered a persistent issue with the TP-Link integration's password authentication, even after updating to version 6.0.0. Here’s the sequence of events:

Initially, I set up the integration using Password A (before any issues arose).
TP-Link later notified me that Password A had been breached, so I changed it to Password B.
At some point, the integration started showing "Invalid cloud password" errors, even though Password B worked directly with TP-Link’s services.
After the recent 6.0.0 update, the issue persisted. In an attempt to resolve it, I changed to Password C, but the integration still didn’t work.
Out of desperation, I reverted back to Password A, and surprisingly, the integration began working again.
It appears the integration only accepts the original password (Password A) and refuses to authenticate with any new passwords, even though these passwords are valid on TP-Link’s side.

Reproduction Steps

See description.

Expected behavior

The integration should authenticate successfully with the current, valid password (e.g., Password B or Password C) after being updated in TP-Link’s cloud.

If applicable, add error logs.

"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. Ensure you have Third-Party compatibility turned on in Tapo App (Me -> Tapo Lab -> Third-Party Compatibility - On)."

Device Firmware

1.1.15

Integration Version

6.0.0

Using stream component

Yes

Does camera work via official integrations?

Yes

Camera has all attributes filled out in developer tools

Yes

HASS Environment

HASSIO on Raspi

Search for similar issues

Yes

Additional information

No response

[JurajNyiri]

Please stop creating new issues about something that is answered in another issue that was just created, this is answered in FAQ as well. I answered under your previous issue, following FAQ will solve your problem and this is not an integration problem.