Tado Integration Stopped Working

lancer73 · April 17, 2025, 4:47pm

Same here, regular re-authentications. Bad thing is that you can’t trust your automations anymore.

What is a good alternative with remote thermostats?

lancer73 · April 19, 2025, 12:44pm

To add to my own comment, it seems like Tado is also working well as a HomeKit device and keeps all interactions local to boot. Main differences:

No battery sensor (will get a mail from Tado about empty batteries anyway)
No valve opening percentage statistics (was using this for information only)
When a Valve or Thermostat has a bad connection, you don’t notice much in the Tado app/integration, but using the HomeKit controller it is very obvious. Now I know why a valve didn’t seem to respond, while the app said connectivity was fine…
No auto/home/away mode for the climate controllers. You will have to do the planning in Home Assistant. With the scheduler addon this is really not a problem. You can add conditions that are continuously monitored to schedules. This can be used for geolocation, open windows etc.
No re-authentications

Chykan · April 20, 2025, 8:29am

@EDouna Here is some information from the tado-node-red-client. May provide some insight into fixing the issue.

Authentication Semantics

The new device flow could be slightly frustrating for headless apps so I’ve tried to cover all use cases and make the use as ergonomic as possible. The authenticate method below must be called before anything else

async authenticate( refreshToken?: string, timeout?: number, ): Promise<[DeviceVerification | undefined, Promise]> {

If a refresh token is provided
- Try to use it, otherwise revert to device auth flow
- If it works then return [undefined, Promise] - where the Promise will immediately resolve
No refresh token provided
- Start a device auth flow
- Device auth flow will return the DeviceVerification object that has the relevant URL, and a Promise that will resolve on successful authentication. It uses a timeout of Math.min(timeout, tado.expires_in)

All auth errors should be identifiable now;

NotAuthenticated - if the authenticate method call wasn’t made yet
InvalidRefreshToken - either the supplied refresh token has expired, was incorrectly typed, or you haven’t made an API call in the last 30 days (see note 1 below)
AuthTimeout - you didn’t hit the device auth URL quick enough

There’s also now an example in examples/auth.ts because it may be a little fiddly.

Note 1. I haven’t implemented any background polling to refresh the refresh token - you’ll need to call the API once every 30 days (That’s how long refresh tokens are currently useable)

sprat · April 24, 2025, 6:07pm

Are you going via HomeKit for it now fully?
Just wondering how you’re getting on with it.

I’ve got a spare hubitat hub so I’m going to install the integration onto there and see if it works but other than that I’m not too sure on my path forward if this can’t be fixed

Follow on after a Quick Look. The tado integration was updated last week and it has something to do with auth.
Not sure if it solved it or not but this link might be helpful for someone with the knowledge. Here the hubitat code:

github.com/tstretton/public

Tado-Connect-2025

e3652f9e7

/**
 *  Tado Connect
 *
 *  Copyright 2016 Stuart Buchanan
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 * 13/04/2025 v3.2 Updated token refresh scheduling, added faster polling option.
 * 08/04/2025 v3.1 Added HeatingPower, adjusted heat logic to report idle state when set temp reached. 
 * 22/11/2023 v3.0 Adjusted to Password Grant flow
 * 22/11/2023 v2.9 Adjusted to OAuth 2 authentication flow
 * 27/04/2018 v2.8 fixed issue with null values when trying to retrieve current setpoint when null as the try and catch arent working as expected.
 * 27/04/2018 v2.7 Modified for Hubitat

This file has been truncated. show original

Chykan · April 25, 2025, 3:39am

I have made a work around in NodeRED. Updated to V6.0
I primarily use the Action Calls through NodeRED, but when the Intergration needs reauthentication especially at 3am in the morning.
The new flow now diverts to the API Method.

https://flows.nodered.org/flow/f37879ba8806713478e34c1f613af7f2

lancer73 · April 25, 2025, 9:10am

Like nothing changed (with respect to how it was a couple of weeks ago). Works fine with HomeKit.

heula · April 29, 2025, 9:09am

Despite having removed and re-installed Tado several times, I still have to log in to Tado again, especially after restarting Home Assistant.
Without wanting to offend anyone, my question is: will this Tado app work the same as before Tado changed the authentication method?

If not, is there an alternative, and I don’t mean Node Red because I want to stay away from that.
Tado is no longer as reliable this way.
I have set up Tado via Homekit, but I miss various functionalities such as Home and Away, but especially the heating percentage.

Thanks

Chykan · April 29, 2025, 10:41am

I am sure they will fix it… If the NodeRED Auth flow works flawlessly, This TADO integration should be able to achieve the same.

Tado should really try pitch in a bit to help. HA users would have to be a reasonable percentage of their user base.

heula · April 29, 2025, 10:58am

Ok thanks, we will just have to be patient than.

Andre · April 30, 2025, 8:28pm

I am using Tado X via homekit and home assistent together.

Simply added the device to homekit, and then sharing the matter code with home assistant. It will connect to home assistent as a matter device, not a tado device and it works solid although it being very bare bones.

I have always used HA for all the schedules and open windows and such and it works almost perfect (and local).

Downside is that it will always say it’s heating, even when it’s not. There is only heating and off, and that’s an issue with how poorly Matter actually is.

As for issues with the Tado integration, regular re-authentications, like within 5 minutes every time

lethuer · May 2, 2025, 7:17am

Re-authentification works but need to do that approx one time a day.

@EDouna do you know there’s a solution in the making…?

Chykan · May 2, 2025, 11:36am

Look at the last post in the link you posted.

Fab78y · May 3, 2025, 3:05pm

Hi. Do you know if there will be something for people who havé Tado X and cant use Matter ( or thread). It worked before March. Thanks from Paris

Chykan · May 14, 2025, 11:19am

OK here is a new one. I get the below message from the integrations page and there is no re-authentication notification to re-authenticate.

Failed setup, will retry: Error during Tado setup: Login failed. Status code: 429 and reason: Too Many Requests

Going to try disable the integration for a while and see if it resets.

EDIT:
Blocked on TADO APP

Blocked on TADO Computer Login

NodeRED Authenticated but 502 Error

wayne_joyce · May 14, 2025, 12:09pm

Yes, exactly the same error here now.

pepe59 · May 14, 2025, 12:12pm

I have the same problem. I have no idea what happened. I didn’t modify or install anything.

arboeh · May 14, 2025, 12:19pm

It seems the tado servers are down. The app doesn’t work also.

krskrab · May 14, 2025, 8:12pm

This incident has been resolved.