No, because the purpose of an automation’s condition is to determine if the automation should, or should not, execute its actions.
What you can do is move the conditional logic out of condition and into action. Specifically into an if-then-else.
alias: example
trigger:
- platform: state
entity_id:
- sensor.toronto_hydro_electric_system_limited_residential_rate
attribute: active_peak
to: on_peak
condition: []
action:
- if:
- condition: state
entity_id: climate.my_ecobee_3
state: heat
- condition: numeric_state
entity_id: sensor.toronto_temperature
below: -1
then:
- service: climate.set_aux_heat
target:
device_id: e144dbd5b26383e5540eb630baa31d66
entity_id: climate.my_ecobee_3
data:
aux_heat: true
else:
- service: notify.notify
data:
message: "Currently on peak but conditions were not met."
BTW, the climate.set_aux_heat service call is setting two entities, one by entity_id and another by device_id. Are they in fact two different entities?