Now getting this:
This error originated from a custom integration.
Logger: custom_components.tado_x.api
Source: custom_components/tado_x/api.py:376
integration: tado_x (documentation, issues)
First occurred: 07:47:29 (1 occurrence)
Last logged: 07:47:29
Rate limit exceeded (429). Quota remaining: 0, Reset time: 2026-02-20 12:00:00+00:00
There is nothing wrong.
The fact that you canāt re-authenticate anymore today is because you have a free subscription.
Thatās why you have a rate limit of 100 requests per day.
On the other hand, i have a paid subscription and everything is ok here.
Just ordered a Drayton Wiser with local API and look forward to ripping out the Tado at the weekend. Sorry, but their half-baked local integration and this degradation of the cloud service nails it for me. Itās done good service, but itās gone and will be on eBay.
All is OK now with the tado x integration after API limit reset. Iām curious to see in the coming days/weeks if I hit the 1000 calls Iām allowed. Otherwise I might have to go through Homekit or the local Matter support I suppose
I was finally able to reconnect my tado X devices to the tado app via the HomePod Minis, which means I can finally test/use your integration.
It worked right away!
Are there different API limits?
Your Git page says 5,000 for free, but in the integration sensor I see 1,000?
What exactly causes an API call?
Just installing the integration seems to have used up 4 API tokens?
Restarting HA used up another 3 !?
API call usage: Any change in state you do, or periodic updates e.g. temperature/humidity, possibly some other things as well.
Burning through the 1000 allowed calls will highly depend on how many devices you have.
The limit seems different for different people, I also have 1000.
In other news, I had to reauthorize this morning for some reasonā¦
Am I the only one who seem to have to reauthenticate every day?
@Skye I migrated an old tado Bridge, which allowed me to activate the windows open and geo functions.
I can still use these without a subscription. Maybe itās because we have 1,000 tokens?
I have 5 rooms and 6 radiator thermostats, so not a large number of devices.
Currently, I only control the thermostats to OFF and Auto based on whether the windows are open/closed.
Unfortunately, you can no longer adjust the offset, which I miss, but for now Iām happy that I no longer have to control the windows via Matter HomeKit Automationā¦ which is incredibly inflexible.
I just migrated from the customized Tado solution that was shared here earlier to the new Tado X integration by @exabird and it worked flawlessly! Since I was using a blueprint to adjust the valve offset based on an external temperature sensor, I forked the original to make it work with the new integration as well, in case anyoneās interested: Homeassistant blueprint to set Tado offset using separate temperature sensor Ā· GitHub
Thanks a lot for your work!
@exabird can you also implement the offset correction?