Invalid cloud password / Invalid authentication data after HA 2026.6.0 and recent Tapo firmware updates

[marcobto58]

Description

Description

After recent updates, multiple Tapo cameras stopped authenticating in Tapo Camera Control.

The issue was noticed on the same morning Home Assistant was upgraded to 2026.6.0. One camera also received a recent firmware upgrade.

It is unclear whether this is caused by:

• recent Tapo firmware authentication changes
• Home Assistant 2026.6.0
• Python 3.14
• pytapo / python-kasa dependency behavior

Environment

• Home Assistant Core: 2026.6.0
• Tapo Camera Control: 7.1.14
• pytapo: 3.4.14
• python-kasa: 0.10.2
• Installation: Docker
• Python: 3.14

Affected cameras

Tapo C510W

Firmware: 1.3.4 Build 260523 Rel.33481n

Tapo C100

Firmware: 1.4.4 Build 260303 Rel.5638n

Symptoms

• Tapo mobile app works normally.
• RTSP works.
• ONVIF works.
• Cameras are reachable from the Home Assistant host.
• Open ports: 443, 554, 1024, 2020, 8443, 8800.
• Re-adding the camera fails with:

Invalid cloud password

Relevant log

Exception: Invalid authentication data

Traceback points to:

pytapo.transport.pytapo.pytapo._refreshStok()

Troubleshooting already performed

• Removed and re-added cameras in Tapo app.
• Recreated camera accounts.
• Enabled Third-Party Compatibility.
• Restarted cameras.
• Reinstalled integration.
• Verified LAN connectivity with nmap.
• Verified pytapo version 3.4.14.
• Verified python-kasa version 0.10.2.

Additional context

This may be related to issue #551, but this case involves Home Assistant Core 2026.6.0, Python 3.14, pytapo 3.4.14 and two different Tapo camera models.

Reproduction Steps

1. Upgrade Home Assistant Core to 2026.6.0.
2. Ensure Tapo Camera Control 7.1.14 and pytapo 3.4.14 are installed.
3. Use a Tapo C510W running firmware 1.3.4 Build 260523 Rel.33481n or a Tapo C100 running firmware 1.4.4 Build 260303 Rel.5638n.
4. Open Devices & Services and add the camera through Tapo Camera Control.
5. Enter valid cloud account credentials and camera account credentials.
6. Complete configuration.

Expected result:
Camera is added successfully.

Actual result:
Configuration fails with "Invalid cloud password".

Logs contain:
Exception: Invalid authentication data

Traceback points to:
pytapo.transport.pytapo.pytapo._refreshStok()

Expected behavior

The camera should authenticate successfully and be added to Home Assistant through Tapo Camera Control using valid credentials.

The integration worked previously with the same cameras and network configuration.

If applicable, add error logs.

Exception: Invalid authentication data

Traceback points to:

pytapo.transport.pytapo.pytapo._refreshStok()

Additional errors observed:

HTTPSConnectionPool(host='192.168.100.182', port=443):
Max retries exceeded with url: /
(Caused by NewConnectionError:
Failed to establish a new connection: [Errno 111] Connection refused)

Device Firmware

C510W: 1.3.4 Build 260523 Rel.33481n C100: 1.4.4 Build 260303 Rel.5638n

Integration Version

7.1.14

Last known working integration version

Unknown - issue appeared after firmware and/or Home Assistant update

Using stream component

Yes

Does camera work via official integrations?

Yes

HASS Environment

Docker on ubuntu 24.04 lts

Search for similar issues

Yes

Additional information

No response

Debug Logs (Required)

Tapo C510W (192.168.100.182)

2026-06-05 08:27:52
ERROR [custom_components.tapo_control]

HTTPSConnectionPool(host='192.168.100.182', port=443):
Max retries exceeded with url: /
(Caused by NewConnectionError(
HTTPSConnection(host='192.168.100.182', port=443):
Failed to establish a new connection:
[Errno 111] Connection refused
))

2026-06-05 08:28:44
ERROR [custom_components.tapo_control]
Unexpected error fetching Tapo resource status data

Traceback:

urllib3.exceptions.MaxRetryError:
HTTPSConnectionPool(host='192.168.100.182', port=443)

requests.exceptions.ConnectionError:
HTTPSConnectionPool(host='192.168.100.182', port=443)

File "/usr/local/lib/python3.14/site-packages/pytapo/transport/pytapo/pytapo.py", line 565
if self._isSecureConnection()

2026-06-05 10:02:51
ERROR [custom_components.tapo_control]
Unexpected error fetching Tapo resource status data

File "/usr/local/lib/python3.14/site-packages/pytapo/transport/pytapo/pytapo.py", line 763

Exception: Invalid authentication data

[github-actions]

This issue was automatically closed because it matches a known FAQ solution.

Note: This action has been done automatically, owner is notified about this issue and if there is a need he will reopen.

[JurajNyiri]

Debug logs not provided.
Device is refusing the connection, double check whether IP is correct and it did not change. Then check if it is reachable from ha and reset/restart.

[marcobto58]

The cameras are reachable from inside the Home Assistant container.

Commands executed inside the HA container:

docker exec -it ha-campana16p5 curl -k -I https://192.168.100.182

Result:

HTTP/1.0 405 Method Not Allowed
Cache-Control: no-cache
Connection: close
Content-Type: application/json;charset=UTF-8
Content-Length: 0

Also tested with:

docker exec -it ha-campana16p5 curl -k -v https://192.168.100.182

The TLS handshake completes successfully:

Connected to 192.168.100.182 port 443
SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
Server certificate subject: CN=TPRI-DEVICE; O=TPRI; C=US

The same test works for the second camera:

docker exec -it ha-campana16p5 curl -k -I https://192.168.100.180

Result:

HTTP/1.0 405 Method Not Allowed

So the cameras are reachable from HA. The failure seems to occur later inside pytapo during _isSecureConnection() / _refreshStok(), ending with:

Exception: Invalid authentication data

[JurajNyiri]

Please post debug logs as per the template of issue.

[marcobto58]

I attached the debug log.

The relevant error seems to be:

2026-06-05 08:46:49.318 ERROR (MainThread) [custom_components.tapo_control]
Unable to connect to Tapo: Cameras Control controller:
Error: -40214, Response: {"error_code": -40214}

Additional information:

• Home Assistant 2026.6.0
• pytapo 3.4.14
• python-kasa 0.10.2
• Tapo C510W firmware 1.3.4 Build 260523 Rel.33481n
• Tapo C100 firmware 1.4.4 Build 260303 Rel.5638n

Both cameras stopped working at the same time.

HTTPS connectivity from inside the Home Assistant container works:
curl -k -I https://camera-ip
returns HTTP/1.0 405 Method Not Allowed

So the cameras are reachable, but authentication fails with error -40214.

[JurajNyiri]

Those are not debug logs, it is an error, not debug. Follow template guide on how to enable debug logs.

[marcobto58]

DEBUG LOG EXTRACT

2026-06-05 11:04:16.544 DEBUG [custom_components.tapo_control]
Setting up controller using cloud password.

2026-06-05 11:04:16.546 DEBUG [custom_components.tapo_control] [pytapo]
Refreshing stok...

2026-06-05 11:04:16.548 DEBUG [custom_components.tapo_control] [pytapo]
New request:
{'method': 'login', 'params': {'encrypt_type': '3', 'username': 'admin'}}

2026-06-05 11:04:16.740 DEBUG [custom_components.tapo_control] [pytapo]
Response:
{'error_code': -40211}

2026-06-05 11:04:16.741 DEBUG [custom_components.tapo_control] [pytapo]
Connection is insecure.

2026-06-05 11:04:16.742 DEBUG [custom_components.tapo_control] [pytapo]
New request:
{'method': 'login', 'params': {'hashed': True, 'username': 'admin'}}

2026-06-05 11:04:17.140 DEBUG [custom_components.tapo_control] [pytapo]
Response:
{'error_code': -40211}

2026-06-05 11:04:17.140 DEBUG [custom_components.tapo_control] [pytapo]
Unexpected response (-40211), raising Exception: {'error_code': -40211}

Additional information:

Affected cameras:

• Tapo C510W - Firmware 1.3.4 Build 260523 Rel.33481n
• Tapo C100 - Firmware 1.4.4 Build 260303 Rel.5638n

Working camera on same HA instance:

• Tapo C200 - Firmware 1.3.5 Build 260228 Rel.36932n

Home Assistant: 2026.6.0
Tapo Control: 7.1.14
pytapo: 3.4.14
python-kasa: 0.10.2

The cameras are reachable from inside the HA container via HTTPS and RTSP.
The Tapo mobile app works normally.
Issue started after recent firmware updates and/or HA 2026.6.0 upgrade.

[marcobto58]

home-assistant_tapo_control_2026-06-05T09-05-13.972Z.zip

[JurajNyiri]

#1190 (comment)

[marcobto58]

Additional findings after further testing:

I have a separate Home Assistant lab environment that was normally powered off.

Test procedure:

1. Started the lab environment.
2. Upgraded it to Home Assistant Core 2026.6.0.
3. Tried to add the same Tapo cameras.
4. The exact same problem occurred on all three cameras.

Then:

1. Rolled back the lab environment to Home Assistant Core 2026.5.4.
2. Removed the Tapo C510W integration entry.
3. Added the camera again from scratch.

Result:

The camera was added successfully and works normally on Home Assistant Core 2026.5.4.

Summary:

• Home Assistant Core 2026.6.0 -> authentication fails (-40211 / Invalid cloud password)
• Home Assistant Core 2026.5.4 -> camera can be added successfully
• Same camera
• Same firmware
• Same TP-Link account
• Same network
• Same Home Assistant host

This seems to indicate a regression introduced in Home Assistant Core 2026.6.0 or one of its dependencies rather than a camera firmware issue.

[JurajNyiri]

Regression introduced in 2026.6.0, is unlikely, most likely something else changed while you were downgrading (as per FAQ). Try updating back to 6.0

[marcobto58]

Update:

After additional testing, I can no longer reproduce the issue.

I downgraded to 2026.5.4, reconfigured the camera successfully, and then upgraded back to 2026.6.0.

The cameras continue to work on 2026.6.0.

So at this point I cannot confirm a regression in Home Assistant 2026.6.0.

It is possible that one of the troubleshooting steps (reconfiguration, camera restart, Third-Party Compatibility reset, etc.) resolved the issue.

[marcobto58]

Update:

The issue happened again after updating the firmware of my Tapo C200.

I found a workaround that consistently fixed the problem:

1. Open the Tapo mobile app.
2. Go to the user/profile settings.
3. Disable Third-Party Compatibility.
4. Close the app.
5. Wait about 30 seconds.
6. Open the app again.
7. Enable Third-Party Compatibility again.
8. Re-authenticate / re-add the camera in Home Assistant.

After doing this, authentication started working again.

So the issue seems to be related to the camera / Tapo app keeping an inconsistent Third-Party Compatibility state after firmware updates.