Automation condition off ecobee climate?

Third party integrations
1

hey all,

trying to figure out how to monitor via trigger or condition against the “climate” service; specifically from ecobee

refs:

one example is:

  • TRIGGER: if sensor.master_bedroom_temperature >22 for 20mins
  • CONDITION: if HVAC is off (heat=off, ac=off)
  • ACTION: turn on the fan

YAMLS:

TRIGGER
above: '22'
entity_id: sensor.master_bedroom_temperature
for: '00:20:00'
platform: numeric_state

CONDITION
condition: state
entity_id: climate.redbrick
state: 'hvac_mode: off'

ACTION
data:
  fan_mode: 'on'
entity_id: climate.redbrick
service: climate.set_fan_mode

This isn’t working however. I suspect my “state” hvac_mode: off isn’t working (though it is valid syntax).

Per the climate documentation, it is a “service” … so I’m wondering if this excludes it from being able to be leveraged in TRIGGERS or CONDITIONS?

Any insight appreciated.

x post from https://www.reddit.com/r/homeassistant/comments/gp4kyd/automation_condition_off_ecobee_climate/

if I look at Automation for Climate Thermostat … maybe I need to look into the difference between “states” and “attributes” of a device?

or maybe https://www.reddit.com/r/homeassistant/comments/5l3sb6/automation_with_state_attributes_as_conditions_or/ …

2

after more review of documentation …

TRIGGERS

entity_id: climate.redbrick
for: '02:00:00'
platform: state
to: 'fan_mode: on'

I think this is a problem I don’t see in the docs how to trigger based on an ATTRIBUTE state …

CONDITIONS

Now I have:

condition: state
entity_id: climate.redbrick
state: 'off'

, this seems to be correct

ACTION


data:
  fan_mode: auto
entity_id: climate.redbrick
service: climate.set_fan_mode

, this is uncertain as well … data requires key-value pairs, but if I’m calling a climate.set_fan_mode service, it seems strange to have to include the fan_mode key … but maybe it is right?