tado X

tadoº X

Basics

In may 2024 tadoº introduced their new product generation named X (previous generations are known as V2, V3 or V3+). Devices belonging to the X generation cannot be combined with devices from previous generations as a different technology is used for the communication between devices.

Regardless of which generation of tadoº devices you use in your home, you use the same mobile or webapp to control them

When the home you control via the app is equipped with tadoº X devices, the app uses the https://my.tado.com/api/v2 API (which is the API to which this website is dedicated) for some functionality, like managing users and mobile devices.

However, the more fundamental features like managing rooms and tado devices are supported via another tado API which is hosted on https://hops.tado.com. The functionality of that API is not defined in the API definition documented here.

More info on tado API support for tadoº X can be found here:

• https://community.tado.com/en-gb/discussion/25101/tado-x-api
• https://community.tado.com/en-gb/discussion/25399/zones-and-devices-in-the-tado-x-api
• https://community.tado.com/en-gb/discussion/23573/tado-x-breaking-api-changes
• https://github.com/wmalgadey/PyTado
• https://github.com/gedhi/tadox-postman-collection

tadoº X support via https://my.tado.com/api/v2

The summary of operation groups (and sometimes of individual operations) in the API definition for https://my.tado.com/api/v2 contains a label which indicates if it is supported for tadoº X supported homes.

Why can't you create an API definition for https://hops.tado.com as well?

As the owner of the https://github.com/kritsel/tado-openapispec-v2 repo, I heavily depend on my own tadoº V3+ enabled home to test the correctness of the API definition and maintain an API definition which is as accurate as possible.

Without access to a tadoº X enabled home, I cannot take ownership of an API definition geared towards tadoº X as I won't be able to test it myself.