Thanks Marcus,
For me, though one integration (Tado X) is working well, if I try to add a further entry I just get a dialog box with a spinning circle. It looks as though some text flashes up for a fraction of a second first, but this is gone too quickly to act on.
The lack of support does make me very nervous about further investment in Tado products. Is the company viable?
Robin
Hi everyone, Iām reading the full post since I would like to add Tado X to my new HA installation.
Iām in a pristine situation, so I would like to know if can I get somewhere a list of actions to get it working starting from scratch, because I read a lot of āuninstalling, reinstalling, ā¦ā which I think donāt apply in my case.
Thank you
Hi Karl. Fall and its lower temperatures are approaching, is there any chance weāll see an update of library and the integration in the coming months?
Hi!
Just yesterday, tado announced that they will introduce a rate limit on their servers. 100 API calls/day for free and 20.000/day for Auto-Assist users.
This will likely make significant changes to the tado integration necessary, as the integration as it currently is wonāt work anymore for free users. I hope that in the process of making these changes we will also get the Tado X changes into the integration properly, but these changes opens some questions on the future of this integration which will need to be adressed first.
Tadoās announcement over on GitHub: Upcoming changes to the tadoĀ° API Ā· Issue #151223 Ā· home-assistant/core Ā· GitHub
Hi,
youāll basically need to do two things:
tado folder over to the custom_integrations folder on your HA installation (you can use https://download-directory.github.io/ to make downloading a single folder easier)manifest.json file in the custom_integrations/tado folder to also include a version number, for example change:{
"domain": "tado",
"name": "Tado",
ā¦
to:
{
"domain": "tado",
"version": 2025.8,
"name": "Tado",
ā¦
Then, your last step is to restart your HA instance. After that, you should see a āred boxā icon on the tado integration, like this:
Hi Karl, Iāve tried to install the integration as you said here but i donāt get the red box and I donāt know what Iām doing wrongā¦
The integration will need to fetch most data locally then, I noticed itās not as accurate (in the amount of datapoints) than from the cloud (oh irony) but I guess it works well enough.
There is something that could fit very well with that API call-saving system. I am a tadoĀŗ X user, and I believe that most uses should be managed offline. For tadoĀŗ V3+ users, there is an option you can request so the system allows offline calendar management (https://www.reddit.com/r/tado/comments/1f74a2c/v3_users_can_now_request_offline_schedule/). I havenāt tried how it works, but itās something that has been available for a year now. As far as I know, itās a feature you have to ask to have activated. If tadoĀŗ is consistent with the new call-saving policy, they should enable this for all users by default. It would mean significant savings for them and (possibly) would make integration a bit simpler.
Thanks a lot Karl, working flawlessly 
Iāve installed your files into the custom folder and completed the OAuth2 process successfully. The integration added my Tado location āWohnungā but failed to setup the devices (Smart Radiator Thermostat X & Wireless Temperature Sensor X) with the following error.
This error originated from a custom integration.
Logger: custom_components.tado.coordinator
Source: helpers/update_coordinator.py:392
integration: Tado
First occurred: 02:07:30 (1 occurrence)
Last logged: 02:07:30
Unexpected error fetching tado data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 392, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/tado/coordinator.py", line 97, in _async_update_data
(device if isinstance(device, dict) else device[0])
~~~~~~^^^
IndexError: list index out of range
Hi folks. As weāre coming up to winter again Iām checking back in on this issue to see if an updated integration can solve the challenges with my heating setup.
Like many on here, I was using the integration last winter to correct (via offsets) the temperature readings from the tado trvs using other sensors in HA. BY correcting every few mins I was able to get a decent performance for it reaching and maintaining its target temperatures.
With the upcoming rate limiting, Iām wondering if this would be rendered even more difficult. Does anyone have a solution for this? Is there some way we can control the TRVs directly via HA given theyāre matter enabled? Or is it all fundamentally locked to the Tado service?
Apologies for the general question - I thought if any audience would know the answer it would be this one! tia
How disappointing! After everything working well for months, Iām back at square 1 with authentication issues. It seemed to coincide with HA 2025.9, but hard to be sure as it worked for a while after that was first installed.
The custom integration says āAttention requiredā. Clicking reconfigure I get the usual blank message box but can find the URL to do this using the developer tools. This connects to Tado and successfully connects the deviceā¦ but the integration doesnāt buy it and I just get a repeat (blank message box) popping up, presumably to authenticate again (which now fails until I restart HA).
I also have a āDiscoveredā native Tado integration showing, with a Reconfigure button on that. The process here is exactly the same, with no authentication sticking.
To say this is very frustrating is an understatement. It seems clear that even if you are lucky and get things to work, as I did previously, you canāt rely on this continuing.
OK, Iāve got it back. If anyone else faces this what I did was as follows:
Removed the Tado custom component (delete all the files)
Rebooted HA
Restore the custom component (with all edits as described by others)
Restart HA
Tado is ādiscoveredā. Select add new instance
Use developer tools to find the URL and do authentication
Restart HA
Lots of false starts to get there, and lots of rebooting and restarting
Now letās see how long it stays up this timeā¦
Itās strange indeed, at some point I had to re-auth as well but now Iāve updated several versions of HA and it kept going. Not sure what the trigger could be. Hopefully it keeps on working for you throughout the winter period!
Wellā¦ it worked for about 12 hours and then needed authorisation again. That would not complete successfully so I gave up for a few hours and prepared to reinstall again. However, just before doing that (and after backing up my system) I thought Iād try reauthorisation one last timeā¦ and that worked!
How long it will stay this time in anyoneās guess. It worked perfectly for months before, so hopefully I will be lucky
Hello,
I have the same problem since a few days. First time I noticed it was last Tuesday (September 16). At around 10pm my Tado integration lost connection the first time. I first thought it was due to the new limit off 100 API calls per day, so the next morning I subscribed for the Auto Assist Feature to get at least 20.000 API calls a day. A few hours later, at around 2 pm, it suddenly worked again - so I thought everything worked fine again now. But same day again at araound 10pm like the day before, the Tado integration was unavailable again. And it went on like that ā¦ Thursday at around 2pm Tado was back but again at around 10pm unavailable ??? So probably today it will be back again the next 4 hours ā¦ Something is definitely strange. I use a bridge and 7 radiators. So if I would be over the limit off 20.000 API Calls, I would expect to reset the limit with beginning of the new day and not at around 2 pm? Anyone else having those problems? For me, the question is now if I can live with the HomeKit integration or if I should change to another system -maybe Eve or Bosch (the Matter versions). What do you guys think?
Iāve had the problem recur yet again today and once more Iām locked out. It wonāt reauthenticate even though the link to Tado says it has successfully connected.
I do have the auto assist subscription, so should not have been timed out (or if I have, the limit is totally unrealistic).
Getting very frustrated with thisāI was about to buy a second Tado installation for another house, but that is on hold if this canāt be fixed.
Are you able to reauthenticate after it drops out, or does that rarely work (as in my situation)?
Since Tuesday nothing changed. Every day at around 10pm Home Assistant Tado integration looses connection. At around 2 pm the next day, so around 16 hours later, it automatically reconnects. Whe I restart HA before, I get an error message and I need to reauth manually but thatās only possible after 2 pm.
I talked to Tado support and they told me they have no official HA support but what I described loks for them I would be above the 20.000 limit. For me, that sounds very strange. I f I would be over that limit, I would expect the limit to be restet with the beginning of the new day and not at 2pm.
Iām getting exactly the same error since month and have now often repeated the steps from Post 225. Do you use the Tado X bridge? My Tado X devices are connected via my HomePod Minis to HA
I think I could fix my problem with the error: IndexError: list index out of range
"requirements": ["python-tado==0.18.15"] and rebooted. self.devices = [
device if isinstance(device, dict)
else device[0]
for device in self.devices
if (isinstance(device, dict) or (isinstance(device, list) and len(device) > 0))
]
for device in devices:
if self.is_x:
if isinstance(device, dict):
device_short_serial_no = device.get("serialNumber")
elif isinstance(device, list) and len(device) > 0 and isinstance(device[0], dict):
device_short_serial_no = device[0].get("serialNumber")
device = device[0]
else:
_LOGGER.warning("Skipping invalid device format: %s", device)
continue
else:
device_short_serial_no = device.get("shortSerialNo")
_LOGGER.debug("Updating device %s", device_short_serial_no)
I will see, if the authorization will survive 24 hours.
What I found out with a little debugging, the out of range errors is, that the last device in that list is empty:
2025-10-06 08:47:22.956 ERROR (MainThread) [custom_components.tado.coordinator] Device 10: type=<class 'list'>, value=[]
2025-10-06 08:47:22.956 ERROR (MainThread) [custom_components.tado.coordinator] Problematic device at index 10: value=[]
I have 10 Tado X devices, but the list starts with the index 0, so the correct range would be 0 - 9.