Home Technical Questions

tado API

MikeMike ✭✭
edited January 2019 in Technical Questions

Does tado have an API ? Where can I find the documentation ?


  • Although we do have an API, at this time we do not provide any documentation or support for it.

    At this time, the best documentation for the API can be found here:
    And here:

    Please feel free to discuss any question you might have about the API in this topic together with other community members.

  • It looks like the room (zone) temperature is read-only?

    (My intention is to use the API to add small wireless temperature sensors to some rooms, where the human space is often very different than the TRV’s location.)

  • Hello gerwitz,

    As commented before, we don't support the API.

    However, what you intend can probably be achieved easily through some of the free official integrations, eg. IFTTT



  • gerwitz, did you get anywhere with this??
  • You can use the offset setting in the app to compensate for this. Just measure temp difference in the “human space” and check difference to TRV. Adjust the offset in the app in rooms setting.

  • dennisoliver, I’ve only found this useful up to a point. Sometimes the valves get warm before the room and shut off, then cool and come back on, rather than staying on until the room is up to temp. Would be neat to be able to add a small sensor.

    Obviously you can add more Tado wall thermostats, but they’re not cheap!

  • Adjusting the offset only works to some degree and takes a long time to get right. Setting the system up this way also appears to affect the reporting side of the app, ie if you want a temp of 19 deg and to achieve this you have to offset 3 deg, then the human space temp will be 19 deg, the valve will show 19 deg but the temp at the valve will actually be 22 deg. However, the Air Comfort report appears to use the 'shown' temp with the offset, ie 19 deg. So, the report is actually incorrect. Might as well just set the valve to 22 deg.
  • I just wrote a python script to correct the read temperature using an external sensor and it works great; now if I set a temperature, that temperature is effectively reached
  • samdsamd ✭✭✭

    @jacoscar Can we hear more about this please?

  • jacoscarjacoscar ✭✭✭
    edited December 2019
    My script connects to the Tado server to retrieve the current offset and the current temperature; then using home assistant API it retrieves the real temperature from another sensor (this could be any sensor as long as it can be used in Home Assistant)
    It then calculates the new offset and applies it!
    It repeats the cycle after a defined number of minutes (using 5 at the moment)
    This effectively means that the Tado valve can pick up the heat of the radiator, but it will be dynamically corrected every 5 minutes

    I would attach a picture but I am not in front of my computer now; I have opened a discussion in the italian Tado forum: if you find it, you’ll see a plot with the real temperature and the one reported by Tado with dynamic offset correction; you’ll see they are pretty much the same, meaning Tado is using the real temperature to request the right amount of heat
  • Really interesting jacoscar. Waiting for the script to use without an additional sensor of temp. Great job!
  • edited December 2019

    I've had a play, and written some code that directly sends offset information from an ESP8266 to Tado, using a DHT22 as the temperature sensor.

    It's not great code, but it does work. It's probably a bad idea to use more than one, in case they try and connect at the same time.

    I intend to replace it with several feeding into Home Assistant, to reduce the number of API calls


    ps, I hesitated to publish this, if you don't understand it, it's probably not for you ;-)

  • @jacoscar, would you mind showing me your script home assistant script? I am looking for a similar solution, where my Hue motion sensors, which are already in all the rooms, deliver the correct room temperature. I'm just not sure how to write a script that pulls the pulls the real temperature, calculates the required offset and then pushes it to the right room in Tado.

    Btw, is @Jacopo also your user?

  • Has anyone had any experience with Gérman’s suggested IFTTT integration? Using a third party thermostat to switch TRVs on and off?
  • Anyone else using HomeAssistant who thinks that adding the offset the existing integration would be a good idea, vote here: -

    It also contains details of my work-around

  • In combination with a Homey from Athom (and there Tado App for Homey) and for example Aqara/Xiaomi zigbee sensors it is possible to do a lot extra with Tado.

    I my self use the integration to switch between smart and not smart, but also for open window detection.

    if windows is opened, set tado temp to 12 degr. for ever.

    If window is closed, set back to smart.

    If someone changes room temp and windows is still open, set it temp again to 12 degr after 10 second

  • @jacoscar would be great if you didn't mind sharing you python script that works for home assistant?

  • @Jurian integrating through IFTT or any other existing platform is not a problem. But the API should be provided by the gateway itself. You guys created a great product, but it depends on your servers. It's fine for many personal use cases, but you could greatly expand your target by allowing it to work with closed systems. I should be able to control my TRV even even if my Internet is down or your servers are down or if tado servers don't exist anymore.

    It really would be amazing to have a simple REST API on the gateway itself allowing your system to work without connecting to your servers. For some companies it is important not to share info with outside world when somebody is in the office or not, and a simple TRV can leak a lot of that kind of info. Same goes for home security.

    I know it's a bit of a mess to use local API by your own app because people are sometimes at home not connected to their wifi, have different LAN for wireless and wired and so on. But adding such API on the gateway.. It would make your product go from great to amazing. Personally I'd order 10+ TRVs right away.

    For more complex installations it would also allow installators to check RSSI to know how many gateways are necessary and so on. Home security systems would more realidy integrate with you.

    You've made great hardware but you also seem to be a great software company, so I'm sure at some level you understand my crave for that local API. If you've dealt with more complex home automation installations you know that relying on external servers is always problematic. They all can be very reliable, but if you use 20 services, really often one of them temporarily have some problems, or somebody decided to change their web API etc. The end result is that things don't work way too often. With local API I can cut my tado off the Internet, use my integrations and it will work as long as hardware works.

    Maybe that's enough begging. Thanks again for awesome product, I hope you'll consider the above. Cheers.

    PS. Alternatively maybe realese specs for your 868 MHz TRV API, but I'm not sure if you do some firmware updates and whether it can change.

    All of the above goes for Smart AC control too which other companies could integrate into their solutions if it would not rely on your server.

  • If you are of a technical nature, and you want to integrate your tado products into a home automation system, then you may be interested in the following links

    • The openHAB home automation system tado binding is described here
    • The openHAB binding uses the API (described via "Swagger") here
    • Also look at Terence Eden's blog about the tado API here and Stephen Philips blogs here

  • @AndrewFG Thank you, I'm familiar with the links but I think they exploit API that tado uses for their website. Local API would be ideal as explained earlier, but if using API on their servers it should at least be official. Otherwise it may just change with the website redesign. There's also this client secret which can be easily used to cut off unofficial API use even without any redesign.

    Time put into integration, testing and so on, may end up costing more than devices themselves. If API is gone then it all goes to waste.

  • @comboy @jurian @Germán and anyone else from tado, I read comboys most recent posts here and registered to just say that while I really like what tado provides, the one niggling doubt about the whole system is the total reliance on tado servers, internet connection and such. Local API, I guess via some sort of hub or new bridge, would be top of my list for improvements. Geo fencing, weather updates and such I can live without temporarily on the odd occasion there are issues, but to lose the scheduling functionality in such circumstances is too much (not to mention the possible scenario of the servers being switched off altogether).
Sign In or Register to comment.