Feature request - allow using other climate entities (for example from ha-tado-x)

[p1ranha]

I know that your plugin is not compatible with TadoX, but is there a chance you could allow selection of entities from any climate entities? I used ha-tado-x integration to bring Tado into HA, but I love the functionalities your integration has!

Especially the insights.. This got me really addicted (I use your integration with my other home that has older Tado installation).

[hiall-fyi]

@p1ranha Thanks for the kind words about Tado CE, and glad you're enjoying the insights on your older Tado home!

I had a look at ha-tado-x and this is actually more interesting than I initially thought. Tado X's cloud API appears to expose very similar data to V3/V3+:

Feature	Tado V3/V3+ (Tado CE)	Tado X (ha-tado-x)
Heating power %	Yes	Yes
Battery status	Yes	Yes
Open window detection	Yes	Yes
API quota monitoring	Yes	Yes
Temperature/Humidity	Yes	Yes
HVAC modes	Yes	Yes
Schedules/Presets	Yes	Yes
Geofencing	Yes	Yes
Energy IQ	No	Yes

This means native Tado X support in Tado CE is actually feasible - the data that powers our insights and analytics exists in the Tado X API too. It wouldn't be a case of wrapping generic climate entities (which would lose most insights), but rather adding Tado X as a supported device type with its own API adapter.

There's a related feature request in #143 (and the original #106) for using external sensors to override displayed values - that's a different use case (faster local updates) but shows the direction we're heading with data source flexibility.

What this would look like:

• During setup, Tado CE would detect whether your account has V3/V3+ or X devices (or both)
• The insights, analytics, and monitoring features would work the same way for both device types
• Tado X-specific features like Energy IQ could be added as well

Current priorities:
We're in the middle of a major multi-home refactor right now, which is a prerequisite for both HomeKit local support and cleaner data source abstraction. Once that lands, adding Tado X support becomes much more realistic since the architecture will already support multiple data sources per home.

I'm going to keep this issue open and label it as a Tado X support feature request. No timeline yet, but it's definitely on the radar now. Thanks for prompting me to look into this more closely!

Related:

• Feature suggestion - Specify my own temperature/humidity entity #143 - External sensor override for climate card display
• Open window detection. (may or may not be a bug) #106 - Per-Zone External Sensor Override
• Unable to manage more than one home (different accounts) #110 - Multi-home support (prerequisite refactor in progress)

[hiall-fyi]

Hey @p1ranha, just a quick update on the progress since we last spoke!

A few of the building blocks I mentioned have shipped since then:

• Multi-Home Support (v3.0.0) — The multi-home refactor is done. You can now run multiple Tado accounts/homes in a single HA instance, each fully isolated. This was the prerequisite I mentioned for cleaner data source abstraction.

• External Sensor Override (v3.1.0) — Per-zone external temperature & humidity sensor support is live (Open window detection. (may or may not be a bug) #106, Feature suggestion - Specify my own temperature/humidity entity #143). You can use any HA sensor (HomeKit, Zigbee, etc.) to override Tado's built-in readings via Options Flow → Zone Configuration.

• Real-Time External Sensor Updates (v3.2.0) — External sensors now update the climate card immediately when the sensor value changes, instead of waiting for the next Tado API poll cycle.

These lay the groundwork for the Tado X integration I outlined. The architecture now supports multiple data sources per home, which is exactly what's needed for adding Tado X as a supported device type.

Native Tado X support is still on the roadmap — no timeline yet, but the hardest infrastructure work is behind us. I'll update this issue when there's more concrete progress.

Thanks for your patience and for prompting this direction!

[hiall-fyi]

Hey @p1ranha, closing this for now since it's been a while.

The core of what you were asking for — using sensor data from another integration with Tado CE — actually shipped back in v3.1.0. You can assign any HA temperature or humidity sensor (including ones from ha-tado-x) as an external override per zone via Settings → Tado CE → Configure → Zone Configuration. Tado CE's insights, mold risk, thermal analytics, and comfort level all use the overridden values, so you'd get the full analytics experience with your Tado X sensor data.

Native Tado X API support (so you wouldn't need ha-tado-x at all) is still something I'd like to explore, but that's a bigger piece of work. The infrastructure is ready for it whenever the time comes.

Feel free to reopen or start a new issue if you want to pick this up again. Cheers!

[p1ranha]

hi @hiall-fyi ,

how do I configure the zones? I linked it to my TadoX accounts and have only global settings available?

[hiall-fyi]

Hey @p1ranha, sorry for the confusion in my earlier reply.

The reason you're not seeing any zones is that Tado CE only works with the older Tado devices (V3/V3+ bridge, Smart Radiator Thermostats, Smart Thermostats). Tado X is a newer product line that works differently under the hood, so Tado CE can't see your rooms or devices — which is why you're getting an empty setup with just global settings.

The external sensor feature I mentioned before only helps if you already have older Tado devices set up. It can't create rooms from scratch for a Tado X-only account.

For your Tado X setup, ha-tado-x is the right integration. It's built specifically for Tado X and will give you climate controls, temperature, humidity, and heating data.

I'd love to support Tado X in Tado CE eventually, but I don't own any Tado X hardware myself. Building and testing support for devices I can't actually try would be really hard to get right. If there's enough interest down the line and someone with Tado X is willing to help test, I'd be happy to revisit it.

Sorry I can't do more right now!