Tado API limits

Add-ons Bindings
21

That one does give a different response for me:

{
    "PRE_2025_FREE_FEATURES": [
        {
            "source": "TADO_MANAGED",
            "status": "ACTIVE",
            "type": "TADO_MANAGED",
            "startDate": "2025-07-07T16:10:18.918Z"
        }
    ]
}

No idea where it gets that date from, since I’ve installed my tado devices almost two years ago…

22

I found the old packages in my cellar and both V3 and V3+ have “Works with Apple Homekit” on them.

Then it doesn’t matter which bridge is used. Sorry for the confusion! I’ll edit my post above to avoid false information :slight_smile:

23

How to check how many requests my Tado installation is sending to API?

24

To see the API calls, you need to set the binding log level to TRACE and check the “Api response” logs.

For users with an Amazon Echo it might be an option to use the Echo Binding and control the heating via the Echo. But I did not test this yet on my own.

I wonder if tado also restricts these API calls which come from the tado Alexa Skill. They most likely cannot distinguish between real Alexa voice commands or commands coming from the Echo binding via the heating things.
Or one could also just fake a voice command instead of using the heating thing from the Echo binding :melting_face:

25

You can calculate the basic daily count from your number of devices N as (24 x 60 x 60 x N / refreshInterval) (assuming that all devices have the same refreshInterval).

The number N includes all Tado controller devices and your geofencing mobile phones.

On top of the basic daily call count will be:

  • one per hour for each battery device.
  • one for every control action issued by OH (based on a rule of something..)
26

I created a very limited substitution for the binding: Very partial tado binding alternative.