Tado

Description: Add support for turning of a hot water device. Follow up from #29191. cc @springstan ## Checklist: - [x] The code change is tested and works locally. - [x] Local tests pass with `tox`. Your PR cannot be merged unless tests pass - [x] There is no commented out code in this PR. - [x] I have followed the [development checklist][dev-checklist] If the code communicates with devices, web services, or third-party tools: - [ ] [_The manifest file_][manifest-docs] has all fields filled out correctly. Update and include derived files by running `python3 -m script.hassfest`. - [ ] New or …

Excerpt saved from GitHub on 2026-10-23.

Using Tado for 2 years now with no issues (14 valves + thermostat + bridge)

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

You should look into Tado. Although I'm not sure if it's available in the US. It's a smart thermostat with smart radiator knobs with a built in thermostat. So you can heat each room individually with an app. Also links with home assistant

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

Using Tado for the past 3 years with HA and works great. You can also control it locally via the HomeKit integration in HA

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

… 30-ish wifi devices of all kind and I dont even own a single zigbee or zwave one. For some of my devices, I have to accept that they dont work locally. My Tado thermostats depend on the cloud using the Tado integration (I think I could make them work locally only but Im not 100% sure). I have some tuya smart switches and blinds controllers that can not be flashed to tasmota, so I use the tuya integration that depends in the cloud. Worst case, in the morning if the clouds have evaporated, I have to press some buttons; I can live with that. And if or when I eventually replace them Ill look for …

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

… frequent API users are currently responsible for a disproportionately high share of our server expenses. In general, simple requests should be handled locally whenever possible - both to reduce server load and to save energy. That’s why, on our V3+ generation, we offer local access via HomeKit, which is also already supported by Home Assistant. With our newer generation, tado° X, we support Matter. For tasks that involve intensive polling - such as frequent read-back of temperature or humidity, or updates of setpoint - these should be handled via local communication. We understand that not …

Excerpt saved from GitHub on 2026-10-23.

… a 'smart' air conditioning unit. It's hard to predict how long they'll continue to support firmware upgrades. I'd go with an IR based control for it - Tado make AC controllers which interface over IR and seem to have a good catalogue of different AC remotes. They have a cloud based API, or you can add the AC modules as homekit devices and interact with them over the local network.

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

Have mitsubishi but control it with Tado device (which mimic the remote IR signal). Tado is not great per se but i'm sure any other IR device can work (especially since HA implemented it in the March update).

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

The problem HomeAssistant entity control features missing after upgraded the tado firmware. Before: Tado: Firmware: 59.6 ---------------- After: Tado: Firmware: 118.3 After upgrading the Tado firmware, at Tado have a new feature of my ac: swag and it is working well. But At home assistant and HomeKit, all the control (Fan mode: small, middle, large auto) and Swag Mode , all the features are missing, except only one can control ac mode. ### What version of Home Assistant Core has the issue? Home Assistant 2023.7.3 ### What was the last working version of Home Assistant Core? _No response_ ### …

Excerpt saved from GitHub on 2026-10-23.

Tado is entirely cloud based, if the internet goes down so does your heating. Home assistant integration is also cloud based, so could be removed at any time. That said I've got a tado system and it seems to work pretty well, have had the odd dropout though. I probably would have gone for a more DIY solution, but I live with my parents so any whole house stuff needs to be easy for them to use and maintain once I'm gone.

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

… problem hello, I have been looking for several weeks without finding a cause, and how to solve the problem, sometimes it happens that when I ask one of my tado thermostats to change the temperatures via the homekit integration, it does not seem to be sent , let me explain, at the level of ha my thermostat has the new temperature, however a few sec/min later the old values ​​reappear. this is not systematic, and I cannot identify the cause of this, and above all I do not know how to correct this problem, because the rollback time is variable ### What version of Home Assistant Core has the …

Excerpt saved from GitHub on 2026-10-23.

The problem I have a Tado Thermostat in HomeKit via the HA HomeKit Controller. When turning the thermostat on or changing the temperature via Siri, I get two errors within the HA logs.... however the temperature still changes as expected. The thermostat only supports heating (off, heat) and there is no cooling element. I am unsure if it is related, though I did report a _simular_ issue this time last year https://github.com/home-assistant/core/issues/44076 These particular errors showed when asking Siri to turn the temperature to 22 degrees. (The current temp was 21 and the thermostat was in …

Excerpt saved from GitHub on 2026-10-23.

… config_entry-homekit-0459c2ff1824173a5941180209300def.json ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? [code] ### Additional information I am using a Tado thermostat which is integrated via the Tado integration.

Excerpt saved from GitHub on 2026-10-23.

The problem I am using homekit to expose my tado devices. The reason for this is because tado themselves don't seem to provide an option to filter which devices are exposed, so I end up with a lot of thermostats I'm not interested in. The humidity sensors are not exposed to homekit however, as they require both the unit of measurement (%) and device-class (humidity) set. The tado integration is missing the latter. ## Environment - Home Assistant Core release with the issue: 0.118.5 (that's what I'm running) - Last working Home Assistant Core release (if known): n/a - Operating environment …

Excerpt saved from GitHub on 2026-10-23.

… release (if known): Operating environment (Hass.io/Docker/Windows/etc.): Hass.io Proxmox Integration: Homekit Description of problem: After i moved my Tado brigde from ios homekit to homekit-controller and then trying to add the thermostats back to ios thru the homekit component i get the error above. The thermostats has been my ios homekit before moving them to HA. Problem-relevant `configuration.yaml` entries and (fill out even if it seems unimportant): [code] Traceback (if applicable): ``` Traceback (most recent call last): File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line …

Excerpt saved from GitHub on 2026-10-23.

… (Hass.io/Docker/Windows/etc.): Ubuntu running hassio in docker. Component/platform: https://www.home-assistant.io/components/homekit/ Description of problem: I have a couple of thermostats from Tado that support operation mode Manual, Timer, Tado mode, Smart schedule and Off. But for some reason it shows Off, Heat, Cool, Auto in the home app as choosable modes. The logical option would be only on/off in homekit and then to set the on "mode" in hassio.^C The cool option is especially confusing becuase this is a valve thermostat for a water based heating system. Problem-relevant …

Excerpt saved from GitHub on 2026-10-23.

… should be handled locally whenever possible - both to reduce server load and to save energy. That’s why, on our V3+ generation, we offer local access via HomeKit, which is also already supported by Home Assistant. With our newer generation, tado° X, we support Matter. For tasks that involve intensive polling - such as frequent read-back of temperature or humidity, or updates of setpoint - these should be handled via local communication. We understand that not all tado° capabilities are accessible through these local APIs. For more advanced use cases, such as controlling domestic hot water, we …

Excerpt saved from GitHub on 2026-10-23.

You're not using the official Tado integration or the homekit integration? Because both of them don't really work anymore properly.

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

Tado connection broken. Hi everyone, I've had my Tado smart thermostat connected to Home Assistant for four weeks now. The connection has been broken since yesterday. Once I've removed Tado from Home Assistant, I can't connect it at all. I've gotten to the point where I can get the unique pairing code through the Tado website, but then the process hangs and I get an "unknown error occurred." I then have to restart Home Assistant to get the pairing code, but it's stuck again with the "unknown error occurred" error. Does anyone have any ideas how I can reconnect the Tado using the information …

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

Proposed change Add support for TadoX thermostatic radiator valves (TRV) which has some API changes to the old Tado V3. This doesn't change any functionality for Tado V3 systems. This PR will only add support for the TadoX radiator valve, it may work with the Smart Thermostat X and the Wireless Temperature Sensor X but not tested, will probably not work with Heat Pump Optimizer X. ~This also changes the PyTado dependency from 0.17.6 to 0.17.7~ Library version bump is in PR

Excerpt saved from GitHub on 2026-10-23.