Tado Integration - Authentication does not work anymore

Configuration
,
1

I recently replaced my domotic hub from OpenHab to Home Assistant so I’m pretty new on this system.
I don’t remember exately what is the initial HA release used when I’ve created my environment but this specific issue on “Tado” integration started yesterday after the update from 2025.10.4 to 2025.11.0.

My Tado integration was started already with the new Tado authentication method (since my installation have less than 1 month of life).

Everithing worked perfectly except that sometimes the integration request for a re-authentication, quite often but ok, I suppose it is something required from auth API on the Tado side, other integrations have the same behaviour for example Volvo.

Today the Tado integration requested for a re-authentication but there are no way to complete the process.

Everything work in the same way:

  • Tado generate a code with a link for the logon
  • In the Tado website accept the access
  • The Tado website respond successfully
  • Back in the HA Tado integration configuration banner and it report the error “The authentication process timed out. Please try again.”

I tried to:

  • Re-try the auth process (no way, same error every time)
  • Restart HA and re-try the auth process (no way, same error every time)
  • Reboot the entire HA system and re-try the auth process (no way, same error every time)
  • Removed the Tado integration and the rebooted HA system and re-tried the auth process (no way, same error every time)

In the community I found other users with the same issue but it was related to older version of the Tado integration (related to the period of the authentication method change by Tado, about May 2025) so I think they was related to a different issues already soved in previous releases of HA and Tado integration itself.

below the error log related to the issue:

Logger: homeassistant.components.tado.config_flow
Source: components/tado/config_flow.py:82
integration: Tado (documentation, issues)
First occurred: 2:29:01 PM (4 occurrences)
Last logged: 3:07:51 PM

Error while waiting for device activation
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/tado/config_flow.py", line 82, in _wait_for_login
    await self.hass.async_add_executor_job(self.tado.device_activation)
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.13/site-packages/PyTado/interface/interface.py", line 103, in device_activation
    self._http.device_activation()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/PyTado/http.py", line 567, in device_activation
    self._device_ready()
    ~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/PyTado/http.py", line 571, in _device_ready
    self._id = self._get_id()
               ~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/PyTado/http.py", line 582, in _get_id
    homes_ = self.request(request)["homes"]
             ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
KeyError: 'homes'
2 Likes
2

that helped me, view the last post from alixoft

3

Same problem here, bought a new Tado X and cant authenticate in HA. Any solutions?

4

Hello,
there were already some connection drops, probably related to the announced refresh restrictions, but since this morning authentication in H.A. has stopped working.
Am I the only one?
Thank you

image
image720×358 9.25 KB

image
image718×476 13.3 KB

Edit :
I just reloaded the integration from the official H.A. page and it’s working again, why???

5

Same issue here unfortunately. Managed to resolve it yesterday but same issue again today.

6

Same issue here.

Combined with their rate-limitting on the API… might be time to ditch Tado altogether.

7

That’s exactly what I did and I don’t regret it. I switched to Sonoff TRVZB without any problems.

8

Since no update seems to have reached an agreement between the developer and Tado GmbH, the only solution appears to be using HomeKit, which restricts data and API call frequency.

It’s a real shame to be forced to use a third-party integration to access your data in Home Assistant…

Especially if all the heating-related automation systems now need to be redone.

9

Problem instantly solved after I paid one month subscription fee. So it is about money. :frowning:

1 Like
10

I have already Auto-Assist and it stopped working since today. I’m still running HA 9.4. Was the integration changed since 9.4?

11

even after updating the issue is still not resolved.

12

Mine has required reauthorisation twice in 2 days. If it doesn’t immediately reauth, I leave it for a few hours and so far it has worked. Most of my Tado control is completely local in the Homekit device integration so I’m not that fussed when the cloud integration disconnects from HA.

13

is there any solution for folks without an apple device and be independent from tado cloud integration?

14

I don’t have any Apple devices. The Homekit Device integration is nothing to do with Apple.

Install the integration and put in the code on the Tado bridge when it is discovered. That will expose all your climate.xxxx entities locally for control in HA.

15

True, except for hot water.

16

Hot water is not a climate entity. It’s a water_heater.hot_water entity :wink:

17

This doesn’t seem to give me access to the climate mode though. I use proximity to switch between home and away mode. I can’t figure out how to do this with the HomeKit integration.

18

Homekit doesn’t expose home and away modes, but you can automate it with something like the Advanced Heating Control Blueprint.

OR

You could try this new custom component that’s recently been created: