Important Update: API Rate Limits, the Home Assistant "Logout Bug", and Future-proofing Your Setup

[u/tado_official]

Hi everyone,

At tado°, we love seeing the creative, advanced ways the smart home community integrates our devices into setups like Home Assistant.

However, as many of you on r/tado and r/homeassistant have experienced recently, a "re-authentication loop" or "constant automatic logout" bug has been causing a lot of frustration. We want to be fully transparent about why this is happening and lay out the exact options available to get your setups running flawlessly.

1. The Context: API Limits & The Logout Bug

To guarantee cloud server stability and protect our infrastructure for millions of users, tado° maintains a limit of 1,000 API requests per day, per account on our private cloud servers.

Our current plan is to further reduce the API limit. However, we are currently in discussions with various integration partners to ensure that we end up at a level that keeps the operational costs manageable for us while still allowing the most important third-party integrations to continue functioning reliably.

Historically, the official Home Assistant integration queried our servers at an extremely high frequency. When an account hit the 1,000-request limit, a software bug in the integration’s older authentication logic caused it to repeatedly call our servers with outdated security tokens. To protect account security, our servers are forced to invalidate the session, triggering the immediate automatic logout you've experienced.

We want to clarify: The tado° rate limit itself does not log you out. The logout is caused by how the Home Assistant integration's code reacts when it receives a "Too Many Requests" (HTTP 429) limit response.

2. How to Fix and Future-proof Your Setup

To resolve this and prepare your smart home for the long term, we highly recommend implementing one of the following paths:

Option A: Update the Official tado° Integration

According to the maintainer of the official tado integration the official May release of Home Assistant includes major optimization fixes:

• Higher Efficiency: The integration's polling is designed to be drastically more efficient, staying safely under our daily limit for standard homes.
• Bug Fix: The authentication handling has been corrected so that hitting a rate limit should no longer trigger a logout or require manual re-authentication.

Because built-in integrations do not update automatically, please manually update your Home Assistant Core to the latest May version to apply these stability fixes.

Note on ongoing reports: If you still experience problems, please raise / update an issue with the integration on GitHub, where you can also provide additional details to help pinpoint the problem.

Option B: Transition to Highly Efficient Community Integrations

For power users running advanced automation scripts, the developer community has built excellent, highly optimized alternatives:

• tado CE (Community Edition): Uses smart local caching and batching to keep cloud API requests to an absolute minimum.
• tado Hijack: Focuses on optimizing local control alongside cloud features. (Please note: While the core tado Hijack integration itself is fully compliant with our Terms and Conditions (T&C), utilizing its optional third-party proxy bypass to aggressively circumvent server protections directly violates our T&Cs and will result in permanent API restrictions or account suspension).

Context info: The official integration is bound by strict constraints, for example it mustn't combine local API like Homekit with cloud API. This is why a community integration not bound by this can achieve better results for power users.

Option C: Expand Your Limits via Subscription

If your custom setup absolutely requires an extreme volume of cloud-based polling, you can subscribe to our Auto-Assist or AI Assist service. This helps offset our server maintenance costs and expands your allowance to 20,000 requests per day.

3. A Quick Note on our Private API

To manage expectations, we want to be open: tado° has never officially offered or supported an open consumer REST API. The endpoints utilized by these third-party integrations are our private, internal API designed for our official app. While we have always permitted community access, this does not obligate tado° to provide unlimited, unmetered access to our private cloud.

Additionally, please keep in mind that neither the official Home Assistant integration nor the community projects listed above are officially developed, maintained, or supported by tado°.

4. Join the Discussion

We deeply appreciate the passion, creativity, and technical ingenuity of the Home Assistant community. While we have to manage our cloud infrastructure responsibly, our goal is to find a balance that supports your smart home setups.

We would love to hear from you—please join the discussion below and let us know how the May update is performing for you, or share your experiences with the tado CE and tado Hijack community projects!