Upcoming changes to the tado° API
Following our recent exchanges with the Home Assistant developers (@erwindouna et 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 stabil
Posted by tado-com on Aug 27, 2025, 7:52 AM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
support (Sysadmin)
Support connecting to remote devcontainers (devcontainer on remote host)
Option to use Waffle menu or links displayed normally
I also attempted to package ROCM on musl.
But why is there no such pushback agains linux kernel?
OpenCode Support
Upcoming changes to the tado° API
Allow Mac users to use Apple native containerization
Support for the Containerization Framework on macOS
Upcoming changes to the tado° API
Following our recent exchanges with the Home Assistant developers (@erwindouna et 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 stabil
Comments (0)
No comments yet. Start the discussion.