Tado authentication not working

[fharten]

The problem

I'm sttuck in a loop where tado wants me to re-authenticate

You need to reauthenticate with Tado. Press Submit to start the authentication process.

I do so and tado.com returns:

Successfully connected device

But then the integration returns:

The authentication process timed out. Please try again.

By clicking on submit I simply get this error:

Unknown error occurred

What version of Home Assistant Core has the issue?

core-2026.1.2

What was the last working version of Home Assistant Core?

No response

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

No response

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, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@fharten Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20tado%22%20
_{^{(message by IssueContext)}}

---

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

[erwindouna]

It's quite likely due to an API rate limit you're experiencing. Please see the important section here: https://www.home-assistant.io/integrations/tado/#connect-with-tado

It covers an potential self-help solution that you can tweak the update interval to your needs.
What you’re most likely are experiencing is that you’re being rate limited. Thus authentication checks will fail and result in the timeout behavior you’re seeing.

[YewTreeWeb]

I'm also getting this issue after restarting HA and now it won't connect even though I follow the auth steps like I normally do. I will check out the link also

[mfiordi]

getting same issue with 2026.1.2; definetely NOT a API rate limit issue: downgrading to 2026.1.0 would instantly allow the re-authentication of TADO addon

[markwalet]

Doesn't feel like an API rate limit to me. Same issue and retried immediately after 12:00 CET

[cogweg]

I had the same problem this morning. At around 13:40 CET I could re-authenticate sucessfully again.

[speeskeek]

same issue. I'm on 2026.1.2. Tried several times.... no luck

[range-of-motion]

Same here, on 2026.1.2.

[bod0221]

Same here, on 2026.1.2.

[speeskeek]

same issue. I'm on 2026.1.2. Tried several times.... no luck

Works now. At 12:00 CET there is a reset.
Since 1/1/2026 there is a changed polling interval i guess. So i adjusted cfr the manual (https://www.home-assistant.io/integrations/tado/) and made a manual polling every 10minutes. So the login procedure is working - it’s Tado that is kicking you for spamming I guess

[range-of-motion]

same issue. I'm on 2026.1.2. Tried several times.... no luck

Works now. At 12:00 CET there is a reset. Since 1/1/2026 there is a changed polling interval i guess. So i adjusted cfr the manual (https://www.home-assistant.io/integrations/tado/) and made a manual polling every 10minutes. So the login procedure is working - it’s Tado that is kicking you for spamming I guess

What's the default polling behaviour tho? Shorter than 10 minutes? Imo the Home Assistant integration should default to an interval that does not trigger the rate limit 😬

[speeskeek]

same issue. I'm on 2026.1.2. Tried several times.... no luck

Works now. At 12:00 CET there is a reset. Since 1/1/2026 there is a changed polling interval i guess. So i adjusted cfr the manual (https://www.home-assistant.io/integrations/tado/) and made a manual polling every 10minutes. So the login procedure is working - it’s Tado that is kicking you for spamming I guess

What's the default polling behaviour tho? Shorter than 10 minutes? Imo the Home Assistant integration should default to an interval that does not trigger the rate limit 😬

Depends on total number of devices. Depends on how many tomes HA is setting/changing values.
I think you have a max of 100 api calls a day, no matter how many devices you got.
See also: https://smarter-home.blog/tag/tado-api-limits/

The automation/schedule is in my tado app .. so for me its only viewing and sometimes (1-2 a day) changing a value (ex heat the bathroom to 24 to have a nice bath in stead of the standard 21)

So really depends on your installation.

[cmdrrobin]

Issue come and goes here. When authenticated it works fine for the moment. The next day it is gone.

Also noticed this log message in HA:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 416, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tado/coordinator.py", line 97, in _async_update_data
    tado_home = tado_home_call["homes"][0]
                ~~~~~~~~~~~~~~^^^^^^^^^
KeyError: 'homes'

I'm running HA version 2026.1.2.

[gjwinkel]

Same here. Contacted Tado. They seem to be aware that a change on their end in how they handle 3rd party integrations is why this happens. I have yet to receive any solution or actual support.