00uzwz961
(AzmJEE5829SHvy46)
May 27, 2025, 6:38pm
1
I’ve noticed that since a recent update Tado requires to be reauthenticated very often. This is super annoying and make the Tado integration much less reliable in HA, as it’s simply not always available anymore for all users.
Is there anyway to circumvent this or fix it?
1 Like
Edwin_D
(Edwin D.)
May 27, 2025, 7:06pm
2
It started a while ago when a new authentication method was forced by Tado. It was reported by me and others back then and was supposed to be fixed, but I still experience the same. It had become less for a while, but is not gone and got worse lately again. Below is one of those issues:
opened 09:03AM - 17 Apr 25 UTC
closed 05:44AM - 24 Apr 25 UTC
integration: tado
### The problem
The new Tado OAuth authentication flow works well (and has rest… ored the functionality of the Tado integration). However I am finding that whenever I restart HA (not usually that often but moreso when doing development work) it tells me that the authentication has expired and I then need to reauthenticate. This is intrusive and annoying but could also be problematic because in some cases (host reboot for example) HA gets restarted while someone is not logged into the GUI (often in the middle of the night) so the issue may remain unnoticed for several hours.
Is there anyway to avoid needing a reauthentication on (apparently) every HA restart? Most other integrations (that I use anyway) only need a reauth very, very infrequently (if ever).
### What version of Home Assistant Core has the issue?
2025.4.1
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant Container
### 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
```yaml
```
### Anything in the logs that might be useful for us?
```txt
2025-04-17 09:48:46.557 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Jenkins’s Home' for tado integration could not authenticate: Device login flow status is PENDING. Starting re-authentication.
```
### Additional information
_No response_
2 Likes
00uzwz961
(AzmJEE5829SHvy46)
May 27, 2025, 7:14pm
3
That sucks. Thanks for sharing.
Its certainly quite annoying, I experience the same thing.
willy230
(Vasilis)
June 7, 2025, 5:56pm
5
ditto here. especially last week it feels like it asks me every day
Jrrs
(jrrs)
June 7, 2025, 11:40pm
6
Same here. I installed the update that should solve it, but it didn’t.
iChris
July 15, 2025, 6:45pm
7
Same problem here. This is still really annoying because the locks repeatedly cannot be activated by Home Assistant - I don’t always see straight away that re-authentication is required.
I recently switched over from Homebridge and used the Tado Plugin on there with the new authentication method, and never got these constant requests to reauth
Seems to be some issue with however HA has implemented the integration
Any news on this issue. It is not yet resolved in my installation
I’m also still experiencing issues…
ikreis
(Jeroen Komen)
August 4, 2025, 7:35pm
11
I experience the same annoyance
jcvsin
August 7, 2025, 5:42am
12
same here. Had the issue for a long time and didn’t experience for about 2 months. After the latest update this annoying thing returned.
Maffewem
(Matthew)
August 12, 2025, 8:00pm
13
Similar to others, I’ve had this issue for months - I gave up trying to authenticate a few months ago, tried it again a few times but it almost instantly asks for re-authentication.
neurot
August 14, 2025, 12:06pm
14
Same here. Super annoying. All my Tado history/stats have huge gaps.
Same for me, changed over from Nest as they are only going to support USA and they gave a discount on Tado X. I’m the developer of a different integration so I understand how difficult and time consuming it can be, but are there timescales for a fix? Especially as winter is only a few months away here in the UK, and time to put the heating on.
It’s not just on restarts, it asks to reauthenticate about 5 seconds after the previous authentication, over and over.
I’m experiencing the same issue as well. The frequent reauthentication makes the integration pretty unreliable for me too.
MarkusJ
(Markus Jasinski)
September 5, 2025, 5:46pm
17
Same here and it looks like it will get worse, because TADO just wrote a mail to inform me that API limits will be introduced (100 calls/day w/o subscription).
woempiej
(Woempiej)
September 5, 2025, 5:54pm
18
Hi
Based on problems related to my own HA (not related) in the past, I get often directed to the github platform. I found some related issues.
opened 07:52AM - 27 Aug 25 UTC
integration: tado
Following our recent exchanges with the Home Assistant developers (@erwindouna e… t al.) over the past few months, we’d now like to track the upcoming changes in the form of a GitHub issue to ensure full transparency.
We have an important update for users of our REST API, which - while never officially supported for third parties - we’ve historically left open and unrestricted. We’ve always believed in fair use, and we intend to continue supporting that principle.
The API is commonly used by third-party and open-source platforms, like Home Assistant, as well as by users running their own custom scripts. Nevertheless, a small fraction of very frequent API users are currently responsible for a disproportionately high share of our server expenses.
In general, simple requests should be handled locally whenever possible - both to reduce server load and to save energy. That’s why, on our V3+ generation, we offer local access via HomeKit, which is also already supported by Home Assistant. With our newer generation, tado° X, we support Matter. For tasks that involve intensive polling - such as frequent read-back of temperature or humidity, or updates of setpoint - these should be handled via local communication.
We understand that not all tado° capabilities are accessible through these local APIs. For more advanced use cases, such as controlling domestic hot water, we will continue to offer access via our Cloud API to cover those extended functionalities.
To ensure long-term stability and to avoid having to restrict access for everyone, we will **begin introducing daily usage limits for API calls**.
The new daily quota will depend on whether you have an active Auto-Assist subscription:
Without Auto-Assist: 100 requests/day
A small daily quota, which should still support basic use cases that are not available via tado’s local APIs: HomeKit for V3/V3+ devices or Matter for tado° X devices. We have updated the documentation on how to access the REST API to reflect these changes.
With Auto-Assist: 20.000 requests/day
This should cover even more demanding use cases, and the subscription fees enable us to offset the increased costs associated with additional server calls.
To ensure the smoothest transition possible, we will introduce a six-month ramp-down phase, over which time the request limits per day will be decreased until they reach the above values. Additionally, we began engaging with Home Assistant several months ago to explore possible solutions since we are aware that these adaptations can create challenges for community-driven projects like Home Assistant.
Thank you!
The tado° Team
### What version of Home Assistant Core has the issue?
all
### What was the last working version of Home Assistant Core?
all
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
_No response_
### Link to integration documentation on our website
_No response_
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
```
### Anything in the logs that might be useful for us?
```txt
```
### Additional information
_No response_
JelleKoster
(Jelle Koster)
September 6, 2025, 5:51am
19
Tado has published this in their documentation today.
Reading between the lines they would like us to either move to the local homekit integration or, if that doesn’t cover our use cases, pay for a subscription.
https://support.tado.com/en/articles/12165739-limitation-for-rest-api-usage
Time to start looking into HomeKit and provide a warning about this server-side limitation on this integration’s documentation.
1 Like
beurdy
September 6, 2025, 8:34am
20
Currently device names aren’t synched between the integration and homekit. In other words; I have no idea which device is which when I use homekit.
That’s basically the only issue for me