Tado integration fails to log in after Home Assistant OS 15.0 update (403 error)

[Kevke]

The problem

Hi,

since updating to Home Assistant OS 15.0, the Tado integration is no longer able to log in. I receive the following error message:

UI: Error during Tado setup: Login failed for unknown reason with status code 403 / Log: Login failed for unknown reason with status code 403

In the previous version (before OS 15.0), the login worked without issues. Additionally, logging in via the Tado website still works without any problems, so the credentials are correct.

It seems that something in Home Assistant OS 15.0 might be affecting the integration. Please investigate and provide guidance on how to resolve this issue.

Steps to reproduce:

1. Update Home Assistant OS to version 15.0
2. Try to use the Tado integration
3. Observe the login failure with error 403

Expected behavior:
The Tado integration should successfully log in, as it did in previous Home Assistant OS versions.

What version of Home Assistant Core has the issue?

core-2025.3.4 / OS 15.0

What was the last working version of Home Assistant Core?

before OS 15.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

tado

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tado/

Diagnostics information

home-assistant_tado_2025-03-25T06-10-05.426Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @erwindouna, mind taking a look at this issue as it has been labeled with an integration (tado) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tado can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tado Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

tado documentation
tado source
_{^{(message by IssueLinks)}}

[sanderkoenders]

I am facing the same issue but after applying a backup from last week (with Home Assistant OS 14.2) the issue persists. So I do not think it is related to the OS update.

Update:
Issue is well documented here. Tado got rid of password auth.

Update 2:
The story is as follows, Tado deprecated password flow support as per this notice. They outline that password flow support will be removed on the 21st of March 2025. That day has passed now and therefore password auth flow has been removed from the Tado API.

The recent addition of support for the new OAuth device flow has been merged into home assistant. This pull request will resolve the issue. The update is expected to be available on their Beta channel by Wednesday, March 26th. The feature is likely to be included in the stable release with the 2025.4.0 update.

In the meantime you can also install the custom component, instructions here. People that do not currently experience this issue are advised not to reload the Tado plugin or restart home assistant as this will break Tado support.

Update 3:
More details about the fix of this issue and instructions on how to opt-in for the beta channel can be found here. Thanks @erwindouna.

[jblankes]

Same problem here

[ralfm12]

I have exactly the same issue after the update.

[JonavdBrink]

At my home the issue is as mentioned, HA has been updated and Tado is dead since that moment. On another site with HA OS which is not updated the Tado integration works well at the moment. This HA OS on RPI is running with the following versioning details:
Core 2025.1.4
Supervisor 2025.03.3
Operating System 14.2

[dvoijen]

Same here

[erwindouna]

A fix is on its way and can be obtained in the upcoming Beta of this Wednesday: #140761 (comment)