Rename time trigger 'after' to 'at' (#2731)

This commit is contained in:
Adam Mills 2017-06-02 01:41:02 -04:00 committed by Paulus Schoutsen
parent db428a5c2d
commit 6cf3cd0a24
10 changed files with 23 additions and 23 deletions

View File

@ -44,7 +44,7 @@ automation:
alias: Turn on heater on workdays alias: Turn on heater on workdays
trigger: trigger:
platform: time platform: time
after: '08:00:00' at: '08:00:00'
condition: condition:
condition: state condition: state
entity_id: 'binary_sensor.workday_sensor' entity_id: 'binary_sensor.workday_sensor'

View File

@ -44,7 +44,7 @@ Turn auxiliary heater on/off for climate device
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
- service: climate.set_aux_heat - service: climate.set_aux_heat
data: data:
@ -69,7 +69,7 @@ reflecting a situation where the climate device is set to save energy. This may
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
- service: climate.set_away_mode - service: climate.set_away_mode
data: data:
@ -96,7 +96,7 @@ temporary target temperature. The particular modes available depend on the clima
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
- service: climate.set_hold_mode - service: climate.set_hold_mode
data: data:
@ -122,7 +122,7 @@ Set target temperature of climate device
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
- service: climate.set_temperature - service: climate.set_temperature
data: data:
@ -146,7 +146,7 @@ Set target humidity of climate device
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
- service: climate.set_humidity - service: climate.set_humidity
data: data:
@ -169,7 +169,7 @@ Set fan operation for climate device
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
- service: climate.set_fan_mode - service: climate.set_fan_mode
data: data:
@ -192,7 +192,7 @@ Set operation mode for climate device
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
- service: climate.set_operation_mode - service: climate.set_operation_mode
data: data:
@ -215,7 +215,7 @@ Set operation mode for climate device
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
- service: climate.set_swing_mode - service: climate.set_swing_mode
data: data:

View File

@ -42,7 +42,7 @@ automation:
- alias: Turn on Heater at 8pm - alias: Turn on Heater at 8pm
trigger: trigger:
- platform: time - platform: time
after: "20:00:00" at: "20:00:00"
action: action:
- service: climate.set_operation_mode - service: climate.set_operation_mode
entity_id: climate.remotec_zxt120_heating_1_id entity_id: climate.remotec_zxt120_heating_1_id
@ -61,7 +61,7 @@ automation:
- alias: Turn off Heater at 9pm - alias: Turn off Heater at 9pm
trigger: trigger:
- platform: time - platform: time
after: "21:00:00" at: "21:00:00"
action: action:
- service: climate.set_operation_mode - service: climate.set_operation_mode
entity_id: climate.remotec_zxt120_heating_1_id entity_id: climate.remotec_zxt120_heating_1_id

View File

@ -41,7 +41,7 @@ Set cover position of one or multiple covers.
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
- service: cover.set_cover_position - service: cover.set_cover_position
data: data:
@ -64,7 +64,7 @@ Set cover tilt position of one or multiple covers.
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
- service: cover.set_cover_tilt_position - service: cover.set_cover_tilt_position
data: data:

View File

@ -66,7 +66,7 @@ automation:
- alias: turn hvac on - alias: turn hvac on
trigger: trigger:
platform: time platform: time
after: '5:30:00' at: '5:30:00'
action: action:
service: switch.mysensors_send_ir_code service: switch.mysensors_send_ir_code
entity_id: switch.hvac_1_1 entity_id: switch.hvac_1_1
@ -76,7 +76,7 @@ automation:
- alias: turn hvac off - alias: turn hvac off
trigger: trigger:
platform: time platform: time
after: '0:30:00' at: '0:30:00'
action: action:
service: switch.mysensors_send_ir_code service: switch.mysensors_send_ir_code
entity_id: switch.hvac_1_1 entity_id: switch.hvac_1_1

View File

@ -30,7 +30,7 @@ automation:
- alias: Enable First Morning Trigger - alias: Enable First Morning Trigger
trigger: trigger:
- platform: time - platform: time
after: '5:00' at: '5:00'
action: action:
service: homeassistant.turn_on service: homeassistant.turn_on
entity_id: input_boolean.trigger_first_morning entity_id: input_boolean.trigger_first_morning

View File

@ -35,7 +35,7 @@ _Note, Philips Hue is currently the only light platform that support transitions
automation: automation:
trigger: trigger:
platform: time platform: time
after: "07:15:00" at: "07:15:00"
action: action:
service: light.turn_on service: light.turn_on
entity_id: light.bedroom entity_id: light.bedroom

View File

@ -148,7 +148,7 @@ automation:
# zone: zone.barracuda_sj # zone: zone.barracuda_sj
# event: enter # event: enter
# - platform: time # - platform: time
# after: '07:15' # at: '07:15'
# before: '09:00' # before: '09:00'
# action: # action:
# service: ifttt.trigger # service: ifttt.trigger

View File

@ -127,7 +127,7 @@ automation:
### {% linkable_title Time trigger %} ### {% linkable_title Time trigger %}
Time can be triggered in many ways. The most common is to specify `after` and trigger at a specific point in time each day. Alternatively, you can also match if the hour, minute or second of the current time has a specific value. You can prefix the value with a `/` to match whenever the value is divisible by that number. You cannot use `after` together with hour, minute or second. Time can be triggered in many ways. The most common is to specify `at` and trigger at a specific point in time each day. Alternatively, you can also match if the hour, minute or second of the current time has a specific value. You can prefix the value with a `/` to match whenever the value is divisible by that number. You cannot use `at` together with hour, minute or second.
```yaml ```yaml
automation: automation:
@ -140,9 +140,9 @@ automation:
automation 2: automation 2:
trigger: trigger:
platform: time platform: time
# When 'after' is used, you cannot also match on hour, minute, seconds. # When 'at' is used, you cannot also match on hour, minute, seconds.
# Military time format. # Military time format.
after: '15:32:00' at: '15:32:00'
automation 3: automation 3:
trigger: trigger:

View File

@ -217,14 +217,14 @@ automation:
- alias: soft reset at 2:30am - alias: soft reset at 2:30am
trigger: trigger:
platform: time platform: time
after: '2:30:00' at: '2:30:00'
action: action:
service: zwave.soft_reset service: zwave.soft_reset
- alias: heal at 2:31am - alias: heal at 2:31am
trigger: trigger:
platform: time platform: time
after: '2:31:00' at: '2:31:00'
action: action:
service: zwave.heal_network service: zwave.heal_network
``` ```