tado_ce

Tado CE - Community-maintained Tado integration for Home Assistant

About

Tado CE is an alternative Home Assistant integration for Tado, built around requests the built-in Home Assistant Tado integration (HA Core) hasn’t picked up. It is developed independently of Tado and works with Tado V2, V3 and V3+ hardware.

Why use Tado CE

Three situations where it’s worth considering:

1. You’ve hit the Tado API quota. Since 2025 Tado limits most households to 100 API calls a day, and the built-in integration only polls the cloud, so dashboards lag by 15 to 20 minutes. With an Internet Bridge V3 or V3+ paired over HomeKit, Tado CE reads room temperature and target temperature locally in about 2 seconds, without touching your quota. On a nine-zone test home, daily API usage dropped from about 394 calls to under 80. Learn more: Smart Polling & API Management →
2. Your TRV reads hot and the room never reaches target. A TRV (thermostatic radiator valve) sits on the radiator and reads warmer than the room, so Tado closes the valve before the room is warm. Smart Valve Control fixes that with an external sensor, either by changing the temperature offset Tado’s own algorithm sees (Offset Sync) or by overriding the setpoint (Valve Target). Learn more: Smart Valve Control →
3. You need a feature the built-in integration doesn’t have. Multi-home support, Weather Compensation for OpenTherm boilers, Actionable Insights, mould-risk monitoring, thermal analytics and a schedule calendar. See the comparison below. Learn more: Advanced Analytics, Automation & Integration →

If none of those apply, the built-in Tado integration is fine. Tado CE isn’t meant to replace a healthy install; it’s the option for when a specific need arises.

Feature comparison

Two of the checkmarks above are newer than they look. HA Core has since added its own quota-aware polling and a heating-circuit select, so the difference now is depth, not presence: Core’s polling runs one interval formula, tado_ce adds day/night scheduling, per-type refresh floors, and quota-reserve tiers on top (Smart Polling); Core fetches heating circuits unconditionally on every heating-zone install, tado_ce only when you turn the option on (Enhanced Controls).

Supported devices

Tado X uses Matter over Thread. For those devices, use Home Assistant’s native Matter integration.

Quick start

Prerequisites

• Home Assistant 2025.11 or newer
• A Tado account
• Tado V2, V3, or V3+ hardware (see Supported devices)
• Optional but recommended: an Internet Bridge V3 or V3+ for HomeKit local control

Upgrading from v4.0.x? See ROADMAP.md - Upgrade Paths for version compatibility and migration steps.

1. Install via HACS

Tado CE is in the HACS default store, so no custom-repository setup is needed.

1. Open HACS, search for Tado CE, and click Download.
2. Restart Home Assistant.

The button above takes you straight to the Tado CE page in HACS.

2. Add and authenticate

1. Settings → Devices & Services → Add Integration → Tado CE
2. Open the authorisation link shown (or visit the URL displayed and enter the code), authorise Home Assistant in your Tado account, and return.
3. If your Tado account covers more than one home, pick which one to add. Each home becomes its own Home Assistant config entry.

No SSH, no manual token extraction, no YAML.

3. Verify

Open Settings → Devices & Services → Tado CE. You should see a Tado CE Hub device and one device per zone, and the hub’s Last Sync sensor should show a recent time. If it doesn’t, check Settings → System → Logs for errors from tado_ce.

4. Enable HomeKit local control (recommended)

If you have an Internet Bridge V3 or V3+, pair it directly with Tado CE:

1. Find the 8-digit setup code printed on the side of the bridge (or shown in the Tado app once HomeKit is enabled). If the bridge is already paired with Apple Home, unpair it there first, because the bridge only pairs with one HomeKit controller at a time. Tado’s own walkthrough is at Tado support: How do I set up tado° with Apple HomeKit?.
2. In Home Assistant, open Tado CE’s Configure → General Settings → Hardware Connections → Local Control (HomeKit), enable it, and enter the code when prompted.

Tado CE drives the pairing itself, so don’t add the bridge through Home Assistant’s standard HomeKit Device integration first. The bridge allows only one HomeKit controller at a time, so an existing pairing blocks Tado CE.

Temperature sensors will then show data_source: homekit when values arrive locally. The humidity sensor shows it when HomeKit fills in because Tado’s humidity reading is missing. See FEATURES_GUIDE.md for details.

5. Configure

Open the gear icon on the Tado CE integration card. Settings take effect immediately, with no restart needed. Start with General Settings to enable the features you want; Advanced Settings only exposes tuning parameters for features you’ve enabled (plus the always-present polling and API settings).

Features

Core climate, AC, and hot water

Full Home Assistant climate.*, water_heater.*, sensor.*, and binary_sensor.* entity coverage for every Tado zone and device type. Preset modes (Home / Away, on heating zones), timer overlays (Tado’s term for a temporary override: manual, until the next schedule block, or a set time), and geofencing are mapped onto Home Assistant-native controls, so no custom cards are required.

HomeKit Local Control

With an Internet Bridge V3 or V3+ paired, Tado CE uses HomeKit for temperature reads, humidity reads, target-temperature writes, and HVAC-mode writes on heating zones. Three cases still go to the cloud. When the Override duration is the default, Until you resume schedule, a temperature or heat-mode change to a zone that is off goes through the cloud, because a HomeKit setpoint only stores the number and doesn’t turn the thermostat on. On heating zones, other overlay modes always use the cloud, since HomeKit writes don’t carry their termination; a zone with no Override behaviour of its own follows the hub’s Override duration to decide. And a heating zone you set to Send changes via: Tado cloud (Zone Configuration) always uses the cloud. The cloud API is used for features HomeKit doesn’t expose (schedules, geofencing, the Tado app’s calibration engine) and for everything Smart AC Control V3+ does. Those units are standalone WiFi accessories with their own HomeKit pairing, separate from the bridge, and Tado CE doesn’t currently handle that pairing flow.

If the bridge is factory-reset (which issues a new HomeKit identity), Tado CE raises a Home Assistant Repairs notification and stops retrying until you re-pair from Configure → Advanced Settings → HomeKit. A data_source attribute on each temperature sensor reports whether the current value came from HomeKit or cloud, and the HomeKit sensor tracks how many API calls local control has saved you. (One quiet-TRV edge case is covered under Known Limitations below.)

Smart Valve Control

For rooms where the TRV reading differs from the actual room temperature (common with radiator TRVs, because of draughts, cold external walls or sensor placement), Tado CE can use an external temperature sensor to correct Tado’s algorithm. Two modes:

• Offset Sync (recommended): writes a device temperature offset so Tado’s own heating algorithm sees your external sensor’s reading. Tado then modulates as normal.
• Valve Target (advanced): overrides the TRV setpoint directly. Use when Offset Sync’s -9.9 to +10 °C range isn’t enough.

Valve Target yields to manual changes (Tado app, physical TRV dial), resumes on the next schedule block, and prefers HomeKit for the write when available (zero API cost). Offset Sync writes its offset through the Tado cloud. Valve Target reads the zone’s Tado schedule to know what target to hold; that schedule is fetched automatically as needed and refreshed on demand via the Refresh Schedule button, rather than polled continuously, keeping the cloud-call budget for state that actually changes.

Weather Compensation

For homes with an OpenTherm-compatible boiler, Tado CE can adjust the boiler’s flow temperature based on outdoor temperature. You set the maximum and minimum flow temperature, the shutoff temperature and the design outdoor temperature, and Tado CE works out the heating curve from those. The Heating System Type dropdown lists standard radiators, low-temperature radiators and underfloor heating, but for now those three behave the same. Choose Custom to set your own slope. Boiler flow temperature is read directly from the bridge every 60 seconds, independent of your cloud polling interval, since the bridge API doesn’t count against your Tado quota.

Smart Polling

Tado’s per-home quota varies (100 / 1,000 / 20,000 calls per day depending on tier). Tado CE detects it, tracks remaining calls, and adapts its cadence automatically: quick polls during the day when activity matters, longer intervals overnight. The fastest it will poll on its own is every 5 minutes, the same on every plan. A bigger quota doesn’t make it poll faster, because your room temperature doesn’t change any faster just because Tado granted you more calls; polling faster would only spend calls re-reading the same numbers. If you genuinely want faster than 5 minutes, set a custom interval under Configure → Advanced Settings → Polling, Delays & Defaults and it’s honoured as long as your quota can sustain it.

Weather, presence, and mobile device locations refresh on their own slower schedules (see the table above; the minimum waits are configurable in Configure → Advanced Settings → Polling, Delays & Defaults), so a fast polling interval doesn’t drag slow-moving data along and burn calls re-fetching values that haven’t moved.

With HomeKit connected, cloud polling drops further since temperatures arrive locally.

That trade-off runs one way, worth knowing going in: a change you make from Home Assistant reaches Tado in seconds, but a change made in the Tado app doesn’t come back the same way, it waits for the next cloud sync, so it can take up to the Cloud Data Refresh interval under Configure → Advanced Settings → HomeKit (30 minutes by default) to show up here, even with local HomeKit control active. A change made by hand at the thermostat is different: the bridge relays that locally, so it still arrives in real time.

Actionable Insights

Per-zone and home-wide insights that tell you what’s wrong and what to do about it, rather than just surfacing raw metrics. Examples: open-window detection (with confidence scoring), low-quota warnings with a recommended configuration change, mould-risk and ventilation tips, and cold-room alerts.

Related insights in a zone are merged into one, so a single problem doesn’t produce several near-identical entries.

Thermal Analytics

Per-zone heating-rate tracking, a preheat-time advisor, and thermal-inertia estimation. Uses a rolling window so the values adapt when you rearrange furniture, change windows, or upgrade insulation, with no manual retraining.

Multi-Home Support

If your Tado account covers more than one home, each becomes its own Home Assistant config entry with full data isolation.

Full feature reference

This page covers the features most users will notice first. See FEATURES_GUIDE.md for the complete reference including Smart Comfort, Adaptive Preheat, Hot Water Timer, Mould Risk monitoring, Environment Monitoring, Zone Features Toggles, and per-feature configuration.

Configuration

All settings live under Settings → Devices & Services → Tado CE → gear icon. Changes apply immediately without restart.

For usage scenarios (low-quota setup, high-quota setup, mixed zones, OpenTherm boiler), see FEATURES_GUIDE.md.

Entities and services

Tado CE creates entities covering hub-level diagnostics, per-zone climate and analytics, environment monitoring, hot water control, actionable insights, and weather compensation. See ENTITIES.md for the complete list of entity types and their attributes.

Tado CE exposes services for climate control, hot water timers, open-window mode, temperature offsets, restoring previous state, and more. All services appear under Developer Tools → Actions with parameter documentation. See FEATURES_GUIDE.md for full details and examples.

Automations that need to act right after Home Assistant starts can listen for the tado_ce_ready event instead of using delays. See Automation Events.

Known limitations

These are how the integration or the underlying protocol works today, not bugs. Check here before opening a report; each links to the fuller explanation.

FAQ

logger:
  default: info
  logs:
    custom_components.tado_ce: debug

For issues not covered here, check Settings → System → Logs (filter by tado_ce), search the existing GitHub Issues, and if it’s new, open a bug report. The bug-report form walks you through what to include (your versions, whether HomeKit is on, and a debug log), which is what turns a triage round-trip into a same-day fix.

Uninstall

1. Settings → Devices & Services → Tado CE → ⋮ → Delete
2. Restart Home Assistant.
3. In HACS: find Tado CE, ⋮ → Remove. Or for manual installs, delete the config/custom_components/tado_ce/ directory.
4. Restart Home Assistant again.

Documentation

External resources

• Tado API rate-limit announcement (HA community)
• Home Assistant’s built-in Tado integration

Contributing

Tado CE’s feature set is almost entirely driven by GitHub Issues and Discussions. Specific user reports, data, and testing turn into features or fixes. If you’ve hit a problem, open a bug report; if you want something changed or just want to ask, start a Discussion. Logs and screenshots are what make the difference between a triage round-trip and a same-day fix.

Code contributions are also welcome: fork, branch, commit, and open a PR. The Discussions tab is the best place to float an idea before writing code.

License

Released under the GNU Affero General Public License v3.0 (AGPL-3.0). Modifications must be released as open source under the same licence with attribution. See LICENSE for the full text.

Original author: Joe Yiu (@hiall-fyi)