Tado Away mode via HomeKit Device integration

Configuration
,
1

Hello
I managed to successfully add my Tado Bridge and TRVs to Home Assistant via the HomeKit Device integration. However, I’m not seeing the “Home/Away” mode pre-set

I saw a couple of posts but they’re referring to the Tado integration which is reliant on the Tado cloud whereas I want the control to be completely local

2

Hi there! Can the “Home/Away” mode pre-set be controlled through HomeKit natively? By that I mean, if you added the devices directly into HomeKit instead of through Home Assistant, are those controls available?

3

I’ve added mine directly via HomeKit. I cannot see any option for Home/Away anywhere. I can, however, turn on/off individual TRVs and set temperature

4

Unfortunately, if the controls are not available when adding the device directly to HomeKit, then they won’t be exposed through the HomeKit Device Home Assistant integration either. You may need to use the Tado integration (which does use a cloud connection) for that particular option.

Someone that has experience with Tado may be able to chime in.

5

Would it be possible to use both HomeKit (as a local non-cloud option) and the Tado integration (cloud-based) to control the same devices? It would be quite confusing if the integration duplicates the same devices

6

I had the same issue and just recently solved it by creating an input boolean helper (aka dummy switch), which I subjected to a few automations and included in Homekit via Homekit Bridge.
With that in place, I can change the tado preset mode in HA or Homekit and the switch is automatically updated in the respective other interface.
Only caveat: It’s a separate on/off switch (on being home and off being away) and not included in the device integration.

Step-by-step:

  • Create an input boolean helper under Settings → Devices & Services → Helpers. I called mine tado_preset_mode with entity id input_boolean.tado.
  • Create an automation under Settings → Automations & Scenes and copy the following code:
alias: tado_manual_set_mode
description: "Manual switch for Homekit to change the tado preset mode"
triggers:
  - trigger: state
    entity_id:
      - input_boolean.tado
    from: null
    to: "on"
    id: tado_switch_on_1
  - trigger: state
    entity_id:
      - input_boolean.tado
    from: null
    to: "off"
    id: tado_switch_off_1
  - trigger: state
    entity_id:
      - climate.[your tado device]
    attribute: preset_mode
    from: away
    to: home
    id: tado_switch_on_2
  - trigger: state
    entity_id:
      - climate.[your tado device]
    attribute: preset_mode
    from: home
    to: away
    id: tado_switch_off_2
conditions: []
actions:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - tado_switch_on_1
              - tado_switch_on_2
        sequence:
          - device_id: [your tado device id]
            domain: climate
            entity_id: [your tado entity id]
            type: set_preset_mode
            preset_mode: home
          - action: notify.[your device you want to notify]
            data:
              title: tado
              message: tado changed to home.
          - action: input_boolean.turn_on
            target:
              entity_id: input_boolean.tado
            data: {}
      - conditions:
          - condition: trigger
            id:
              - tado_switch_off_1
              - tado_switch_off_2
        sequence:
          - device_id: [your tado device id]
            domain: climate
            entity_id: [your tado entity id]
            type: set_preset_mode
            preset_mode: away
          - action: notify.[your device you want to notify]
            data:
              title: tado
              message: tado changed to away.
          - action: input_boolean.turn_off
            target:
              entity_id: input_boolean.tado
            data: {}
mode: single
  • After that, you can simply push the switch to Homekit via Homekit Bridge and add the input boolean to your preferred lovelace.

Automation - explanatory remarks:

  • The first two triggers are for the case when you change the input boolean switch.
  • The last two triggers are for the case when you switch the preset mode in the tado app. If you have multiple tado devices, it is sufficient to just include one (I use the main thermostat) as the other valve thermostats automatically update.
  • The defined actions make sure that the switch and the tado app are synchronized. For instance, when the boolean is turned on, the tado app switches to home, the input boolean is turned on and I get a notification to my phone that the preset mode changed.

Hope this is helpful :v:

7

Hi, I appreciate this is a year old.
I understand climate.[your tado device] but am unsure of where I get
device_id: [your tado device id] and
entity_id: [your tado entity id]
info from.
Bit of a noob, but slowly getting there!
TIA

Paul

8

Hello, I’m looking at implementing scheduling locally via HA for Tado as they are restricting their API. I’m coming from scheduling via the app and thus far controlled geofencing by swithching the ‘home/away’ status. However, this is not available in Homekit just as swithch back to ‘auto’ is not availble from Homekit as it is with the API.

From what I see with a little research this custom integration available via HACS is probably very useful for implementing proper geofencing together with HA scheduling: GitHub - toringer/home-assistant-thermostat-setback: A Home Assistant custom component that automatically controls climate devices based on schedule devices, implementing temperature setback functionality.