[Release] Tado (Connect)

This is how I have changed mine to poll users every 15 seconds while the system state is every 30 seconds.
Not sure if this helps.

// Schedule it to run every 5 minutes
//	runEvery5Minutes("poll")
//    runEvery5Minutes("userPoll")
    schedule("5/30 * * * * ? *", "poll")
    schedule("5/15 * * * * ? *", "userPoll")
}

You could change my example to...
image

Hi. I have tado connect since 2 years aprox. I update my hubitat and now it isn´t works. I don´t know what happend. I try to update the app driver. I can´t do it because it reports error on line 39. anyone can help me please? thanks in advance

i have installed: c7 hubitat with 2.3.8.120 and v2.8 tado connect version

Hi,

I've installed Tado Connect and the drivers from Bibbleq repo but when I attempt to authenticate the app with Tado I'm getting Bad Tado Creds error message. OAuth is enabled for the app.

Any ideas? Thanks

Have you entered Client ID and Client Secret correct?
You can use
Client ID: public-api-preview
Client Secret: 4HJGRffVR8xb3XdEUQpjgZ1VplJi6Xgw
See post nr 71 (Nov 2023)

Thanks for the reply. I had missed that completely. Can you confirm where exactly I should put these? I'm not familiar with groovy so a bit unsure here. Thanks in advance

After you have inserted the app code and drivers. Go to "Apps" - add user app - Choose Tado Connect

In the next screen you can put the Client ID, Client Secret and your username and password.

Thanks. In the version from the @Bibbleq repo it doesn't prompt me for the Oauth details

I've installed the alternate version from @user3860 and now get the same as your screenshot.

Thanks for the help

Hi, I installed the app and drivers from the @Bibbleq repo earlier this week and got the same problem as @echoes675, so following his example I replaced the app code with that of @user3860.

Now Tado is connected to my HE, and I can see all my Thermostats and TRVs which is great.

However, the devices in HE soon get out of sync with the Tado devices, and this is causing me a problem. I wanted to use the Tado thermostats to control the Zigbee switch controlling the electric towel radiator in the shower room. The Tado stat controls the underfloor heating, but the radiator is set in HE to come on for a couple of hours a day, my intention was to turn off the towel rad if the room temperature exceeded the Tado setpoint. I used HE's built-in Rule Machine 5.1 to create the automation. I only read data from the Tado devices and don't use HE to update TADO.

There are 2 problems that I can see.

  • Randomly the HE device representing the Tado thermostat, stops reporting the current temperature and remains at a constant temperature. Hitting refresh or poll on the HE device has no effect. Sometimes all the devices are reporting the wrong temperature, and sometimes it is only 1 or 2 out of 9 devices that are wrong.

  • The HE device gets locked in the Heating state and won't reset.

Reinitialisng the Tado Connect HE app seems to resolve the temperature reading (for a while) but the Heating state won't reset. I have also tried forcing state changes from Tado's app to see if that will force a change in the HE device state, but again no effect. My heating dashboard in HE constantly shows every room as heating even though the temperatures all exceed the set points.

It is impractical to have to remove and reinstall the Tado Connect app in HE.

Any help would be greatly appreciated.

In response to my previous post, I think I can see what is causing the problem with the HE device being stuck in Heating mode.

If the Tado device is running a schedule with a setpoint say a setback temp of 10degC and the room is at say 18degC; the Tado device has a state of Power ON. If the device is in 'Frost Protection' mode, the Power is OFF. The current state of whether the device is Heating seems to depend on the ActivityDataPoints - Heating Power element. I have included a sample from a call to /API/v2/homes/{homeId}/zones/{zoneId}/state to illustrate this; see below.

{
   "tadoMode": "HOME",
   "geolocationOverride": false,
   "geolocationOverrideDisableTime": null,
   "preparation": null,
   "setting":    {
      "type": "HEATING",
      "power": "ON",
      "temperature":       {
         "celsius": 10,
         "fahrenheit": 50
      }
   },
   "overlayType": null,
   "overlay": null,
   "openWindow": null,
   "nextScheduleChange":    {
      "start": "2024-04-17T15:00:00Z",
      "setting":       {
         "type": "HEATING",
         "power": "ON",
         "temperature":          {
            "celsius": 18,
            "fahrenheit": 64.4
         }
      }
   },
   "nextTimeBlock": {"start": "2024-04-17T15:00:00.000Z"},
   "link": {"state": "ONLINE"},
   "activityDataPoints": {"heatingPower":    {
      "type": "PERCENTAGE",
      "percentage": 0,
      "timestamp": "2024-04-17T09:49:24.921Z"
   }},
   "sensorDataPoints":    {
      "insideTemperature":       {
         "celsius": 18.38,
         "fahrenheit": 65.08,
         "timestamp": "2024-04-17T09:43:36.450Z",
         "type": "TEMPERATURE",
         "precision":          {
            "celsius": 0.1,
            "fahrenheit": 0.1
         }
      },
      "humidity":       {
         "type": "PERCENTAGE",
         "percentage": 48.9,
         "timestamp": "2024-04-17T09:43:36.450Z"
      }
   }
}

This does not resolve the other issue of devices randomly freezing the reported temperature.

I received a message from Tado that from March 21, 2025 the connection via Tado (Connect) would no longer be possible.

Their message that I received:

We’ve noticed that you’re using the unofficial tado° REST API with the password grant flow and the clients ‘tado-web-app’ or ‘public-api-preview’.

To meet strict security standards, we haven’t used the password grant flow in any official tado° applications for a while and we’ll be removing access to it on 21 March 2025.

If you’ve written your own software, we’ve provided an alternative method of authentication, please check out our article for details.
We’ve already informed Home Assistant and python-tado, the largest open-source software systems using this authentication method, and they’ve confirmed that they'll provide an update by the deadline. If you’re using any other open-source or commercial home automation software, we recommend reaching out to them directly.

Their alternative method: https://support.tado.com/en/articles/8565472-how-do-i-authenticate-to-access-the-rest-api

This is way too technical for me :pensive:.
Does anyone have an idea what needs to be done?

1 Like