From cfa31281429e5e156462e640c2032a7336fde59e Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Mon, 15 Feb 2021 08:08:37 +0100 Subject: [PATCH] Enquote YAML occurances of alias strings (#16576) --- .../automation_enocean_phue.markdown | 4 +- .../_cookbook/automation_first_light.markdown | 6 +-- .../automation_flashing_lights.markdown | 22 +++++----- .../dim_and_brighten_lights.markdown | 2 +- .../_cookbook/foscam_away_mode_PTZ.markdown | 4 +- source/_cookbook/notify.mqtt.markdown | 2 +- .../notify_if__new_ha_release.markdown | 4 +- .../notify_if_over_threshold.markdown | 4 +- ...orm_actions_based_on_input_select.markdown | 10 ++--- source/_cookbook/send_a_reminder.markdown | 2 +- ...r_10_minutes_when_motion_detected.markdown | 12 +++--- source/_docs/automation/yaml.markdown | 4 +- .../splitting_configuration.markdown | 16 ++++---- source/_docs/scripts.markdown | 12 +++--- source/_docs/tools/dev-tools.markdown | 2 +- source/_docs/z-wave/device-specific.markdown | 8 ++-- source/_docs/z-wave/events.markdown | 14 +++---- source/_integrations/arlo.markdown | 6 +-- source/_integrations/august.markdown | 2 +- .../_integrations/azure_service_bus.markdown | 2 +- .../binary_sensor.xiaomi_aqara.markdown | 40 +++++++++---------- source/_integrations/blink.markdown | 8 ++-- source/_integrations/caldav.markdown | 2 +- source/_integrations/cast.markdown | 8 ++-- source/_integrations/color_extractor.markdown | 4 +- source/_integrations/counter.markdown | 2 +- source/_integrations/deconz.markdown | 10 ++--- .../_integrations/device_automation.markdown | 2 +- source/_integrations/dexcom.markdown | 2 +- source/_integrations/doods.markdown | 2 +- source/_integrations/doorbird.markdown | 2 +- source/_integrations/dovado.markdown | 2 +- source/_integrations/downloader.markdown | 2 +- source/_integrations/emulated_roku.markdown | 2 +- source/_integrations/enocean.markdown | 2 +- source/_integrations/facebook.markdown | 2 +- source/_integrations/facebox.markdown | 6 +-- source/_integrations/feedreader.markdown | 4 +- source/_integrations/fireservicerota.markdown | 8 ++-- source/_integrations/flic.markdown | 4 +- source/_integrations/folder_watcher.markdown | 2 +- source/_integrations/foursquare.markdown | 2 +- source/_integrations/geniushub.markdown | 4 +- source/_integrations/geo_location.markdown | 2 +- source/_integrations/griddy.markdown | 2 +- source/_integrations/hangouts.markdown | 2 +- source/_integrations/homematic.markdown | 4 +- source/_integrations/html5.markdown | 10 ++--- source/_integrations/hyperion.markdown | 6 +-- source/_integrations/ifttt.markdown | 6 +-- .../_integrations/image_processing.markdown | 6 +-- source/_integrations/incomfort.markdown | 2 +- source/_integrations/input_boolean.markdown | 2 +- source/_integrations/input_number.markdown | 10 ++--- source/_integrations/input_select.markdown | 8 ++-- source/_integrations/input_text.markdown | 2 +- source/_integrations/insteon.markdown | 12 +++--- source/_integrations/isy994.markdown | 2 +- source/_integrations/keyboard_remote.markdown | 6 +-- source/_integrations/kira.markdown | 2 +- source/_integrations/kodi.markdown | 14 +++---- source/_integrations/life360.markdown | 4 +- source/_integrations/lifx.markdown | 2 +- source/_integrations/light.group.markdown | 2 +- source/_integrations/light.markdown | 4 +- source/_integrations/limitlessled.markdown | 2 +- source/_integrations/lirc.markdown | 2 +- source/_integrations/logbook.markdown | 2 +- source/_integrations/meteoalarm.markdown | 2 +- source/_integrations/miflora.markdown | 2 +- source/_integrations/minio.markdown | 4 +- source/_integrations/modem_callerid.markdown | 6 +-- source/_integrations/nest.markdown | 2 +- source/_integrations/netatmo.markdown | 8 ++-- source/_integrations/netgear_lte.markdown | 2 +- source/_integrations/nightscout.markdown | 2 +- source/_integrations/nzbget.markdown | 2 +- source/_integrations/openuv.markdown | 8 ++-- source/_integrations/point.markdown | 4 +- source/_integrations/qwikswitch.markdown | 2 +- source/_integrations/rainbird.markdown | 2 +- source/_integrations/rfxtrx.markdown | 2 +- source/_integrations/satel_integra.markdown | 2 +- source/_integrations/scene.markdown | 4 +- source/_integrations/script.markdown | 6 +-- source/_integrations/shell_command.markdown | 2 +- source/_integrations/smtp.markdown | 4 +- source/_integrations/sonos.markdown | 2 +- source/_integrations/spc.markdown | 2 +- .../_integrations/switch.mysensors.markdown | 4 +- source/_integrations/system_log.markdown | 6 +-- source/_integrations/tag.markdown | 2 +- source/_integrations/tensorflow.markdown | 2 +- .../_integrations/thermoworks_smoke.markdown | 2 +- source/_integrations/timer.markdown | 12 +++--- source/_integrations/transmission.markdown | 2 +- source/_integrations/twilio_call.markdown | 2 +- source/_integrations/twilio_sms.markdown | 2 +- source/_integrations/universal.markdown | 4 +- source/_integrations/upb.markdown | 2 +- source/_integrations/updater.markdown | 2 +- source/_integrations/vacuum.mqtt.markdown | 4 +- source/_integrations/vallox.markdown | 4 +- source/_integrations/velbus.markdown | 6 +-- source/_integrations/verisure.markdown | 2 +- source/_integrations/webostv.markdown | 2 +- source/_integrations/workday.markdown | 2 +- source/_integrations/xiaomi_aqara.markdown | 6 +-- source/_integrations/xiaomi_miio.markdown | 10 ++--- source/_integrations/zwave.markdown | 4 +- .../_posts/2015-03-22-release-notes.markdown | 6 +-- ...h-moteino-mqtt-and-home-assistant.markdown | 20 +++++----- ...-09-13-home-assistant-meets-ifttt.markdown | 2 +- ...19-alarm-sonos-and-itunes-support.markdown | 2 +- ...hat-cant-track-themselves-part-ii.markdown | 6 +-- ...6-08-03-laundry-automation-update.markdown | 10 ++--- .../2017-03-28-http-to-mqtt-bridge.markdown | 2 +- source/_posts/2017-06-17-release-47.markdown | 4 +- .../_posts/2017-08-26-release-0-52.markdown | 2 +- source/_posts/2018-01-14-release-61.markdown | 2 +- source/_posts/2019-12-11-release-103.markdown | 2 +- .../2020-02-11-android-16-17-release.markdown | 4 +- source/_posts/2020-05-20-release-110.markdown | 2 +- source/_posts/2020-07-01-release-112.markdown | 4 +- ...20-08-05-mobile-apps-new-features.markdown | 2 +- source/_posts/2020-08-12-release-114.markdown | 2 +- .../2020-09-15-home-assistant-tags.markdown | 2 +- source/_posts/2020-10-28-release-117.markdown | 2 +- source/_posts/2020-11-18-release-118.markdown | 2 +- 129 files changed, 303 insertions(+), 303 deletions(-) diff --git a/source/_cookbook/automation_enocean_phue.markdown b/source/_cookbook/automation_enocean_phue.markdown index e522d0ceca6..58de9813d52 100644 --- a/source/_cookbook/automation_enocean_phue.markdown +++ b/source/_cookbook/automation_enocean_phue.markdown @@ -24,7 +24,7 @@ binary_sensor: name: living_room_switch automation: - - alias: Turn on living room light + - alias: "Turn on living room light" trigger: platform: event event_type: button_pressed @@ -35,7 +35,7 @@ automation: service: light.turn_on entity_id: light.hue_color_lamp_3 - - alias: Turn off living room light + - alias: "Turn off living room light" trigger: platform: event event_type: button_pressed diff --git a/source/_cookbook/automation_first_light.markdown b/source/_cookbook/automation_first_light.markdown index b7d6b18799c..b693e5ee5f3 100644 --- a/source/_cookbook/automation_first_light.markdown +++ b/source/_cookbook/automation_first_light.markdown @@ -23,7 +23,7 @@ input_boolean: automation: #turns it on at 5am - - alias: Enable First Morning Trigger + - alias: "Enable First Morning Trigger" trigger: - platform: time at: "05:00:00" @@ -32,7 +32,7 @@ automation: entity_id: input_boolean.trigger_first_morning # turns it off an hour after sunrise - - alias: Disable First Morning Trigger + - alias: "Disable First Morning Trigger" trigger: - platform: sun event: sunrise @@ -45,7 +45,7 @@ automation: # This is the main automation. It triggers when my motion sensor is triggered # (in this case, a motion sensor from a security system attached to my Vera) - - alias: First Morning Motion + - alias: "First Morning Motion" trigger: platform: state entity_id: binary_sensor.livingroom_motion diff --git a/source/_cookbook/automation_flashing_lights.markdown b/source/_cookbook/automation_flashing_lights.markdown index d285e3e3d4a..625c5480b3c 100644 --- a/source/_cookbook/automation_flashing_lights.markdown +++ b/source/_cookbook/automation_flashing_lights.markdown @@ -55,54 +55,54 @@ automation: script: alarm_room1: - alias: Alarm room1 + alias: "Alarm room1" sequence: - - alias: Alarm Room1 Start + - alias: "Alarm Room1 Start" service: homeassistant.turn_on data: entity_id: switch.AlmSnd1 - - alias: Set Ack Room1 + - alias: "Set Ack Room1" service: homeassistant.turn_on data: entity_id: input_boolean.ack1 - - alias: email_Room1 + - alias: "email_Room1" service: notify.email data: message: "Movement alarm in Room1" - delay: # time interval for alarm sound and light flashing seconds: 60 - - alias: Alarm Room1 Stop + - alias: "Alarm Room1 Stop" service: homeassistant.turn_off data: entity_id: switch.AlmSnd1 flash_room1: - alias: Flash Room1 On + alias: "Flash Room1 On" sequence: - - alias: Light Room1 On + - alias: "Light Room1 On" service: homeassistant.turn_on data: entity_id: switch.REL1 - delay: # time for flash light on seconds: 1 - - alias: Light Room1 Off + - alias: "Light Room1 Off" service: homeassistant.turn_off data: entity_id: switch.REL1 - - alias: loop_room1 + - alias: "loop_room1" service: script.turn_on data: entity_id: script.flash_loop flash_loop: - alias: Flash loop + alias: "Flash loop" sequence: - delay: # time for flash light off seconds: 1 - - alias: loop_room1 + - alias: "loop_room1" service: script.turn_on data: entity_id: script.flash_room1 diff --git a/source/_cookbook/dim_and_brighten_lights.markdown b/source/_cookbook/dim_and_brighten_lights.markdown index 350a5a4746e..d55874a6da4 100644 --- a/source/_cookbook/dim_and_brighten_lights.markdown +++ b/source/_cookbook/dim_and_brighten_lights.markdown @@ -107,7 +107,7 @@ Now the script. ```yaml script: ramp_light: - alias: Ramp Light Brightness + alias: "Ramp Light Brightness" description: Ramp light brightness up or down fields: direction: diff --git a/source/_cookbook/foscam_away_mode_PTZ.markdown b/source/_cookbook/foscam_away_mode_PTZ.markdown index f9d73a4c66d..f0fe98c930a 100644 --- a/source/_cookbook/foscam_away_mode_PTZ.markdown +++ b/source/_cookbook/foscam_away_mode_PTZ.markdown @@ -64,14 +64,14 @@ To automate Foscam being set to "on" (facing the correct way with motion sensor ```yaml automation: - - alias: Set Foscam to Away Mode when I leave home + - alias: "Set Foscam to Away Mode when I leave home" trigger: platform: state entity_id: group.family from: "home" action: service: script.foscam_on - - alias: Set Foscam to Home Mode when I arrive Home + - alias: "Set Foscam to Home Mode when I arrive Home" trigger: platform: state entity_id: group.family diff --git a/source/_cookbook/notify.mqtt.markdown b/source/_cookbook/notify.mqtt.markdown index edf29132a2f..527f9e1622b 100644 --- a/source/_cookbook/notify.mqtt.markdown +++ b/source/_cookbook/notify.mqtt.markdown @@ -46,7 +46,7 @@ Use as [`script`](/integrations/script/) in automations. {% raw %} ```yaml automation: - alias: Send me a message when I get home + alias: "Send me a message when I get home" trigger: platform: state entity_id: device_tracker.me diff --git a/source/_cookbook/notify_if__new_ha_release.markdown b/source/_cookbook/notify_if__new_ha_release.markdown index 76a731db903..c4fcedf70cd 100644 --- a/source/_cookbook/notify_if__new_ha_release.markdown +++ b/source/_cookbook/notify_if__new_ha_release.markdown @@ -15,7 +15,7 @@ notify: recipient: recipient@jabber.org automation: - - alias: Update notification + - alias: "Update notification" trigger: - platform: state entity_id: binary_sensor.updater @@ -38,7 +38,7 @@ notify: name: pushbullet automation: - - alias: Update notification + - alias: "Update notification" trigger: - platform: state entity_id: binary_sensor.updater diff --git a/source/_cookbook/notify_if_over_threshold.markdown b/source/_cookbook/notify_if_over_threshold.markdown index f34c9d5a940..9ac53100330 100644 --- a/source/_cookbook/notify_if_over_threshold.markdown +++ b/source/_cookbook/notify_if_over_threshold.markdown @@ -15,7 +15,7 @@ notify me: name: mypushbullet automation: - - alias: FanOn + - alias: "FanOn" trigger: platform: numeric_state entity_id: sensor.furnace @@ -34,7 +34,7 @@ If you also want a notification when it drops back down below that limit, you co {% raw %} ```yaml - - alias: FanOff + - alias: "FanOff" trigger: platform: numeric_state entity_id: sensor.furnace diff --git a/source/_cookbook/perform_actions_based_on_input_select.markdown b/source/_cookbook/perform_actions_based_on_input_select.markdown index f8436cfe8ff..e264f5bf13a 100644 --- a/source/_cookbook/perform_actions_based_on_input_select.markdown +++ b/source/_cookbook/perform_actions_based_on_input_select.markdown @@ -26,7 +26,7 @@ media_player: automation: # If you select "Rain", play the "rain.mp3" file - - alias: Play Rain Lullaby + - alias: "Play Rain Lullaby" trigger: platform: state @@ -42,7 +42,7 @@ automation: # If you select "Babbling Brook", play the "babbling_brook.mp3" file - - alias: Play Babbling Brook Lullaby + - alias: "Play Babbling Brook Lullaby" trigger: platform: state @@ -57,7 +57,7 @@ automation: media_content_type: music # If you select "None, turn the Chromecast off - - alias: Stop the Lullaby + - alias: "Stop the Lullaby" trigger: platform: state @@ -100,7 +100,7 @@ input_select: icon: mdi:airplay automation: - - alias: Stop Streaming Radio + - alias: "Stop Streaming Radio" trigger: - platform: state entity_id: input_select.radio_station @@ -125,7 +125,7 @@ automation: none {% endif %} - - alias: Stream Radio - Template + - alias: "Stream Radio - Template" trigger: - platform: state entity_id: input_select.radio_station diff --git a/source/_cookbook/send_a_reminder.markdown b/source/_cookbook/send_a_reminder.markdown index 0e1c9236692..9b4509bbf83 100644 --- a/source/_cookbook/send_a_reminder.markdown +++ b/source/_cookbook/send_a_reminder.markdown @@ -21,7 +21,7 @@ and automation part to your `configuration.yaml` file. ```yaml automation: - - alias: Send message at a given time + - alias: "Send message at a given time" trigger: platform: time at: "12:15:00" diff --git a/source/_cookbook/turn_on_light_for_10_minutes_when_motion_detected.markdown b/source/_cookbook/turn_on_light_for_10_minutes_when_motion_detected.markdown index 9b46804f285..dce4b55bb26 100644 --- a/source/_cookbook/turn_on_light_for_10_minutes_when_motion_detected.markdown +++ b/source/_cookbook/turn_on_light_for_10_minutes_when_motion_detected.markdown @@ -10,7 +10,7 @@ This recipe will turn on a light when there is motion and turn off the light whe ```yaml automation: -- alias: Turn on kitchen light when there is movement +- alias: "Turn on kitchen light when there is movement" trigger: platform: state entity_id: sensor.motion_sensor @@ -19,7 +19,7 @@ automation: service: light.turn_on entity_id: light.kitchen_light -- alias: Turn off kitchen light 10 minutes after last movement +- alias: "Turn off kitchen light 10 minutes after last movement" trigger: platform: state entity_id: sensor.motion_sensor @@ -35,7 +35,7 @@ Or in the case of multiple sensors/triggers: ```yaml automation: -- alias: Turn on hallway lights when the doorbell rings, the front door opens or if there is movement +- alias: "Turn on hallway lights when the doorbell rings, the front door opens or if there is movement" trigger: - platform: state entity_id: sensor.motion_sensor, binary_sensor.front_door, binary_sensor.doorbell @@ -50,7 +50,7 @@ automation: data: entity_id: timer.hallway -- alias: Turn off hallway lights 10 minutes after trigger +- alias: "Turn off hallway lights 10 minutes after trigger" trigger: platform: event event_type: timer.finished @@ -71,7 +71,7 @@ timer: You can also restrict lights from turning on based on time of day and implement transitions for fading lights on and off. ```yaml -- alias: Motion Sensor Lights On +- alias: "Motion Sensor Lights On" trigger: platform: state entity_id: binary_sensor.ecolink_pir_motion_sensor_sensor @@ -87,7 +87,7 @@ You can also restrict lights from turning on based on time of day and implement transition: 15 -- alias: Motion Sensor Lights Off +- alias: "Motion Sensor Lights Off" trigger: - platform: state entity_id: binary_sensor.ecolink_pir_motion_sensor_sensor diff --git a/source/_docs/automation/yaml.markdown b/source/_docs/automation/yaml.markdown index 3422ba0a7ad..2efe894ad7e 100644 --- a/source/_docs/automation/yaml.markdown +++ b/source/_docs/automation/yaml.markdown @@ -111,7 +111,7 @@ At startup, automations by default restore their last state of when Home Assista ```yaml automation: -- alias: Automation Name +- alias: "Automation Name" initial_state: false trigger: - platform: ... @@ -126,7 +126,7 @@ If you want to migrate your manual automations to use the editor, you'll have to ```yaml # Example automations.yaml entry. Note, automations.yaml is always a list! - id: my_unique_id # <-- Required for editor to work, for automations created with the editor the id will be automatically generated. - alias: Hello world + alias: "Hello world" trigger: - platform: state entity_id: sun.sun diff --git a/source/_docs/configuration/splitting_configuration.markdown b/source/_docs/configuration/splitting_configuration.markdown index 33bf5480b9a..ce3bc8a533e 100644 --- a/source/_docs/configuration/splitting_configuration.markdown +++ b/source/_docs/configuration/splitting_configuration.markdown @@ -231,7 +231,7 @@ These work recursively. As an example using `!include_dir_* automation`, will in ```yaml automation: - - alias: Automation 1 + - alias: "Automation 1" trigger: platform: state entity_id: device_tracker.iphone @@ -239,7 +239,7 @@ automation: action: service: light.turn_on entity_id: light.entryway - - alias: Automation 2 + - alias: "Automation 2" trigger: platform: state entity_id: device_tracker.iphone @@ -260,7 +260,7 @@ automation: !include_dir_list automation/presence/ `automation/presence/automation1.yaml` ```yaml -alias: Automation 1 +alias: "Automation 1" trigger: platform: state entity_id: device_tracker.iphone @@ -273,7 +273,7 @@ action: `automation/presence/automation2.yaml` ```yaml -alias: Automation 2 +alias: "Automation 2" trigger: platform: state entity_id: device_tracker.iphone @@ -370,7 +370,7 @@ speech: ```yaml automation: - - alias: Automation 1 + - alias: "Automation 1" trigger: platform: state entity_id: device_tracker.iphone @@ -378,7 +378,7 @@ automation: action: service: light.turn_on entity_id: light.entryway - - alias: Automation 2 + - alias: "Automation 2" trigger: platform: state entity_id: device_tracker.iphone @@ -399,7 +399,7 @@ automation: !include_dir_merge_list automation/ `automation/presence.yaml` ```yaml -- alias: Automation 1 +- alias: "Automation 1" trigger: platform: state entity_id: device_tracker.iphone @@ -407,7 +407,7 @@ automation: !include_dir_merge_list automation/ action: service: light.turn_on entity_id: light.entryway -- alias: Automation 2 +- alias: "Automation 2" trigger: platform: state entity_id: device_tracker.iphone diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown index d17ef32caf0..0a90a89aee2 100644 --- a/source/_docs/scripts.markdown +++ b/source/_docs/scripts.markdown @@ -47,7 +47,7 @@ script: The most important one is the action to call a service. This can be done in various ways. For all the different possibilities, have a look at the [service calls page]. ```yaml -- alias: Bedroom lights on +- alias: "Bedroom lights on" service: light.turn_on data: entity_id: group.bedroom @@ -74,7 +74,7 @@ The variables action allows you to set/override variables that will be accessibl - light.kitchen - light.living_room brightness: 100 -- alias: Control lights +- alias: "Control lights" service: light.turn_on data: entity_id: "{{ entities }}" @@ -290,7 +290,7 @@ The `event_data` accepts templates. The following automation example shows how to raise a custom event called `event_light_state_changed` with `entity_id` as the event data. The action part could be inside a script or an automation. ```yaml -- alias: Fire Event +- alias: "Fire Event" trigger: - platform: state entity_id: switch.kitchen @@ -306,7 +306,7 @@ The following automation example shows how to capture the custom event `event_li {% raw %} ```yaml -- alias: Capture Event +- alias: "Capture Event" trigger: - platform: event event_type: event_light_state_changed @@ -367,7 +367,7 @@ script: do_something: sequence: - service: script.get_ready_for_something - - alias: Repeat the sequence AS LONG AS the conditions are true + - alias: "Repeat the sequence AS LONG AS the conditions are true" repeat: while: - condition: state @@ -415,7 +415,7 @@ automation: state: "off" mode: single action: - - alias: Repeat the sequence UNTIL the conditions are true + - alias: "Repeat the sequence UNTIL the conditions are true" repeat: sequence: # Run command that for some reason doesn't always work diff --git a/source/_docs/tools/dev-tools.markdown b/source/_docs/tools/dev-tools.markdown index 3e874923cb1..c876f1a0120 100644 --- a/source/_docs/tools/dev-tools.markdown +++ b/source/_docs/tools/dev-tools.markdown @@ -65,7 +65,7 @@ state: on If there is an automation that handles that event, it will be automatically triggered. See below: ```yaml -- alias: Capture Event +- alias: "Capture Event" trigger: platform: event event_type: event_light_state_changed diff --git a/source/_docs/z-wave/device-specific.markdown b/source/_docs/z-wave/device-specific.markdown index b45d0c76549..28e62a69236 100644 --- a/source/_docs/z-wave/device-specific.markdown +++ b/source/_docs/z-wave/device-specific.markdown @@ -1153,7 +1153,7 @@ Let's see how this works in an automation for a Scene Master that's assigned as ```yaml - id: "1234567890" - alias: Double-press Button 2 to toggle all lights + alias: "Double-press Button 2 to toggle all lights" trigger: - platform: event event_type: zwave.scene_activated @@ -1202,7 +1202,7 @@ Here is an example configuration needed for the scene controller: ```yaml automation: - - alias: Sync the indicator value on button events + - alias: "Sync the indicator value on button events" trigger: - platform: event event_type: zwave.scene_activated @@ -1392,7 +1392,7 @@ Button four release|4|7740 Example Event: ```yaml -- alias: MatrixButton2 +- alias: "MatrixButton2" trigger: - event_type: zwave.scene_activated platform: event @@ -1594,7 +1594,7 @@ Button two triple tap|2|4 Example Event: ```yaml -- alias: JascoButton1 +- alias: "JascoButton1" trigger: - event_type: zwave.scene_activated platform: event diff --git a/source/_docs/z-wave/events.markdown b/source/_docs/z-wave/events.markdown index 2568854a801..4ce3284e6fc 100644 --- a/source/_docs/z-wave/events.markdown +++ b/source/_docs/z-wave/events.markdown @@ -8,7 +8,7 @@ description: "Events generated by the Z-Wave component." Home Assistant will trigger an event when the Z-Wave network is complete, meaning all of the nodes on the network have been queried. This can take quite some time, depending on wakeup intervals on the battery-powered devices on the network. ```yaml - - alias: Z-Wave network is complete + - alias: "Z-Wave network is complete" trigger: platform: event event_type: zwave.network_complete @@ -19,7 +19,7 @@ Home Assistant will trigger an event when the Z-Wave network is complete, meanin Home Assistant will trigger an event when the Z-Wave network is complete, but some nodes are marked dead, meaning all of the nodes on the network have been queried. This can take quite some time, depending on wakeup intervals on the battery-powered devices on the network. ```yaml - - alias: Z-Wave network is complete some dead + - alias: "Z-Wave network is complete some dead" trigger: platform: event event_type: zwave.network_complete_some_dead @@ -30,7 +30,7 @@ Home Assistant will trigger an event when the Z-Wave network is complete, but so Home Assistant will trigger an event when the Z-Wave network is ready for use. Between `zwave.network_start` and `zwave.network_ready` Home Assistant will feel sluggish when trying to send commands to Z-Wave nodes. This is because the controller is requesting information from all of the nodes on the network. When this is triggered, all awake nodes have been queried and sleeping nodes will be queried when they awake. ```yaml - - alias: Z-Wave network is ready + - alias: "Z-Wave network is ready" trigger: platform: event event_type: zwave.network_ready @@ -41,7 +41,7 @@ Home Assistant will trigger an event when the Z-Wave network is ready for use. B Home Assistant will trigger an event when the Z-Wave network is set up to be started. ```yaml - - alias: Z-Wave network is starting + - alias: "Z-Wave network is starting" trigger: platform: event event_type: zwave.network_start @@ -52,7 +52,7 @@ Home Assistant will trigger an event when the Z-Wave network is set up to be sta Home Assistant will trigger an event when the Z-Wave network is stopping. ```yaml - - alias: Z-Wave network is stopping + - alias: "Z-Wave network is stopping" trigger: platform: event event_type: zwave.network_stop @@ -64,7 +64,7 @@ Home Assistant will trigger an event when command_class_basic changes value on a Example: ```yaml - - alias: Minimote Button Pressed + - alias: "Minimote Button Pressed" trigger: platform: event event_type: zwave.node_event @@ -82,7 +82,7 @@ Some devices can also trigger scene activation events, which can be used in auto ```yaml # Example configuration.yaml automation entry automation: - - alias: Turn on Desk light + - alias: "Turn on Desk light" trigger: platform: event event_type: zwave.scene_activated diff --git a/source/_integrations/arlo.markdown b/source/_integrations/arlo.markdown index 3e46da9d7ac..19b2e8784ec 100644 --- a/source/_integrations/arlo.markdown +++ b/source/_integrations/arlo.markdown @@ -57,7 +57,7 @@ The Arlo integration also provides a camera service to enable/disable the motion ```yaml #automation.yaml -- alias: Enable Arlo upon HA start' +- alias: "Enable Arlo upon HA start'" initial_state: "on" trigger: platform: homeassistant @@ -104,7 +104,7 @@ Arming the Arlo Base Station when leaving. ```yaml - id: arm_arlo_when_leaving - alias: Arm Arlo cameras when leaving + alias: "Arm Arlo cameras when leaving" trigger: platform: state entity_id: group.family @@ -119,7 +119,7 @@ Setting Arlo to a custom mode (mapped to `home_mode_name` in `configuration.yaml ```yaml - id: disarm_arlo_when_arriving - alias: Set Arlo cameras to Home mode when arriving + alias: "Set Arlo cameras to Home mode when arriving" trigger: platform: state entity_id: group.family diff --git a/source/_integrations/august.markdown b/source/_integrations/august.markdown index d2c30db845c..ad17efa5e4e 100644 --- a/source/_integrations/august.markdown +++ b/source/_integrations/august.markdown @@ -82,7 +82,7 @@ Using the lock operation sensors, you can detect when a user operates a lock and ```yaml - id: "1583706446906" - alias: joe_doe_front_door_operate + alias: "joe_doe_front_door_operate" description: John Doe locks or unlocks the Front Door trigger: - entity_id: sensor.front_door_operator diff --git a/source/_integrations/azure_service_bus.markdown b/source/_integrations/azure_service_bus.markdown index 31d7b3183bc..9592459dbe6 100644 --- a/source/_integrations/azure_service_bus.markdown +++ b/source/_integrations/azure_service_bus.markdown @@ -79,7 +79,7 @@ See the example below for how an automation trigger translates to a message on t ```yaml automation: - - alias: Sunset Service Bus message + - alias: "Sunset Service Bus message" trigger: platform: sun event: sunset diff --git a/source/_integrations/binary_sensor.xiaomi_aqara.markdown b/source/_integrations/binary_sensor.xiaomi_aqara.markdown index 3fb58d7f2b7..72f3e340874 100644 --- a/source/_integrations/binary_sensor.xiaomi_aqara.markdown +++ b/source/_integrations/binary_sensor.xiaomi_aqara.markdown @@ -38,7 +38,7 @@ The requirement is that you have setup the [`xiaomi aqara` integration](/integra #### Motion ```yaml -- alias: If there is motion and its dark turn on the gateway light +- alias: "If there is motion and its dark turn on the gateway light" trigger: platform: state entity_id: binary_sensor.motion_sensor_158d000xxxxxc2 @@ -56,7 +56,7 @@ The requirement is that you have setup the [`xiaomi aqara` integration](/integra - service: automation.turn_on data: entity_id: automation.MOTION_OFF -- alias: If there no motion for 5 minutes turn off the gateway light +- alias: "If there no motion for 5 minutes turn off the gateway light" trigger: platform: state entity_id: binary_sensor.motion_sensor_158d000xxxxxc2 @@ -75,7 +75,7 @@ The requirement is that you have setup the [`xiaomi aqara` integration](/integra #### Door and/or Window ```yaml -- alias: If the window is open turn off the radiator +- alias: "If the window is open turn off the radiator" trigger: platform: state entity_id: binary_sensor.door_window_sensor_158d000xxxxxc2 @@ -86,7 +86,7 @@ The requirement is that you have setup the [`xiaomi aqara` integration](/integra entity_id: climate.livingroom data: operation_mode: "Off" -- alias: If the window is closed for 5 minutes turn on the radiator again +- alias: "If the window is closed for 5 minutes turn on the radiator again" trigger: platform: state entity_id: binary_sensor.door_window_sensor_158d000xxxxxc2 @@ -99,7 +99,7 @@ The requirement is that you have setup the [`xiaomi aqara` integration](/integra entity_id: climate.livingroom data: operation_mode: "Smart schedule" -- alias: Notify if door is opened when away +- alias: "Notify if door is opened when away" trigger: platform: state entity_id: binary_sensor.door_window_sensor_15xxxxxxc9xx6b @@ -118,7 +118,7 @@ The requirement is that you have setup the [`xiaomi aqara` integration](/integra #### Smoke ```yaml -- alias: Send notification on fire alarm +- alias: "Send notification on fire alarm" trigger: platform: state entity_id: binary_sensor.smoke_sensor_158d0001574899 @@ -141,7 +141,7 @@ The requirement is that you have setup the [`xiaomi aqara` integration](/integra {% raw %} ```yaml -- alias: Send notification on gas alarm +- alias: "Send notification on gas alarm" trigger: platform: state entity_id: binary_sensor.natgas_sensor_158dxxxxxxxxxx @@ -161,7 +161,7 @@ The requirement is that you have setup the [`xiaomi aqara` integration](/integra As indicated in the table on top of this page there are 3 versions of the button. For the round shaped button the available events are `single`, `double`, `hold`, `long_click_press` and `long_click_release`. Aqara branded buttons are square shaped. Model WXKG11LM only supports `single`, `double`, `long_click_press`and `hold` events. WXKG12LM supports `single`, `double`, `long_click_press` and `shake` events. For the Aqara versions the delay between two clicks to generate a double click must be larger than with the round button. Clicking too quickly generates a single click event. ```yaml -- alias: Toggle dining light on single press +- alias: "Toggle dining light on single press" trigger: platform: event event_type: xiaomi_aqara.click @@ -171,7 +171,7 @@ As indicated in the table on top of this page there are 3 versions of the button action: service: switch.toggle entity_id: switch.wall_switch_left_158d000xxxxx01 -- alias: Toggle couch light on double click +- alias: "Toggle couch light on double click" trigger: platform: event event_type: xiaomi_aqara.click @@ -181,7 +181,7 @@ As indicated in the table on top of this page there are 3 versions of the button action: service: switch.toggle entity_id: switch.wall_switch_right_158d000xxxxx01 -- alias: Let a dog bark on long press +- alias: "Let a dog bark on long press" trigger: platform: event event_type: xiaomi_aqara.click @@ -201,7 +201,7 @@ As indicated in the table on top of this page there are 3 versions of the button Available events are `flip90`, `flip180`, `move`, `tap_twice`, `shake_air`, `swing`, `alert`, `free_fall` and `rotate`. The integration stores the last action as the attribute `last_action`. ```yaml -- alias: Cube event flip90 +- alias: "Cube event flip90" trigger: platform: event event_type: xiaomi_aqara.cube_action @@ -213,7 +213,7 @@ Available events are `flip90`, `flip180`, `move`, `tap_twice`, `shake_air`, `swi entity_id: light.gateway_light_28xxxxxxxxxx data: color_name: "springgreen" -- alias: Cube event flip180 +- alias: "Cube event flip180" trigger: platform: event event_type: xiaomi_aqara.cube_action @@ -225,7 +225,7 @@ Available events are `flip90`, `flip180`, `move`, `tap_twice`, `shake_air`, `swi entity_id: light.gateway_light_28xxxxxxxxxx data: color_name: "darkviolet" -- alias: Cube event move +- alias: "Cube event move" trigger: platform: event event_type: xiaomi_aqara.cube_action @@ -237,7 +237,7 @@ Available events are `flip90`, `flip180`, `move`, `tap_twice`, `shake_air`, `swi entity_id: light.gateway_light_28xxxxxxxxxx data: color_name: "gold" -- alias: Cube event tap_twice +- alias: "Cube event tap_twice" trigger: platform: event event_type: xiaomi_aqara.cube_action @@ -249,7 +249,7 @@ Available events are `flip90`, `flip180`, `move`, `tap_twice`, `shake_air`, `swi entity_id: light.gateway_light_28xxxxxxxxxx data: color_name: "deepskyblue" -- alias: Cube event shake_air +- alias: "Cube event shake_air" trigger: platform: event event_type: xiaomi_aqara.cube_action @@ -270,7 +270,7 @@ The Aqara Wireless Switch is available as single-key and double-key version. Eac {% raw %} ```yaml -- alias: Decrease brightness of the gateway light +- alias: "Decrease brightness of the gateway light" trigger: platform: event event_type: xiaomi_aqara.click @@ -292,7 +292,7 @@ The Aqara Wireless Switch is available as single-key and double-key version. Eac 10 {% endif %} -- alias: Increase brightness of the gateway light +- alias: "Increase brightness of the gateway light" trigger: platform: event event_type: xiaomi_aqara.click @@ -314,7 +314,7 @@ The Aqara Wireless Switch is available as single-key and double-key version. Eac 10 {% endif %} -- alias: Turn off the gateway light +- alias: "Turn off the gateway light" trigger: platform: event event_type: xiaomi_aqara.click @@ -333,7 +333,7 @@ The Aqara Wireless Switch is available as single-key and double-key version. Eac This automation toggles the living room lamp on vibration/tilt. ```yaml -- alias: Turn on Living Room Lamp on vibration +- alias: "Turn on Living Room Lamp on vibration" trigger: platform: event event_type: xiaomi_aqara.movement @@ -344,7 +344,7 @@ This automation toggles the living room lamp on vibration/tilt. service: light.toggle data: entity_id: light.living_room_lamp -- alias: Turn on Living Room Lamp on tilt +- alias: "Turn on Living Room Lamp on tilt" trigger: platform: event event_type: xiaomi_aqara.movement diff --git a/source/_integrations/blink.markdown b/source/_integrations/blink.markdown index 661e89348f0..488987ce192 100644 --- a/source/_integrations/blink.markdown +++ b/source/_integrations/blink.markdown @@ -101,7 +101,7 @@ The following are some examples showing how to correctly make service calls usin This example script shows how to take a picture with your camera, named `My Camera` in your Blink app (this is **not necessarily** the friendly name in home-assistant). After snapping a picture, the image will then be saved to a local directory called `/tmp/my_image.jpg`. Note that this example makes use of services found in the [camera integration](/integrations/camera#service-snapshot) ```yaml -alias: Blink Snap Picture +alias: "Blink Snap Picture" sequence: - service: blink.trigger_camera data: @@ -122,7 +122,7 @@ Here, this example assumes your blink module is named `My Sync Module` and that ```yaml - id: arm_blink_when_away - alias: Arm Blink When Away + alias: "Arm Blink When Away" trigger: platform: state entity_id: all @@ -138,7 +138,7 @@ Similar to the previous example, this automation will disarm blink when arriving ```yaml - id: disarm_blink_when_home - alias: Disarm Blink When Home + alias: "Disarm Blink When Home" trigger: platform: state entity_id: all @@ -158,7 +158,7 @@ Again, this example assumes your camera's name (in the blink app) is `My Camera` ```yaml - id: save_blink_video_on_motion - alias: Save Blink Video on Motion + alias: "Save Blink Video on Motion" trigger: platform: state entity_id: binary_sensor.blink_my_camera_motion_detected diff --git a/source/_integrations/caldav.markdown b/source/_integrations/caldav.markdown index 24b70910b25..180e69eb3f0 100644 --- a/source/_integrations/caldav.markdown +++ b/source/_integrations/caldav.markdown @@ -163,7 +163,7 @@ calendar: # automations.yaml - id: wakeup - alias: worktime wakeup + alias: "worktime wakeup" trigger: platform: time at: "06:40:00" diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown index c1d86a816c7..8bf93345abc 100644 --- a/source/_integrations/cast.markdown +++ b/source/_integrations/cast.markdown @@ -25,7 +25,7 @@ Home Assistant has its own Cast application to show the Home Assistant UI on any ```yaml cast_downstairs_on_kitchen: - alias: Show Downstairs on kitchen + alias: "Show Downstairs on kitchen" sequence: - data: dashboard_path: lovelace @@ -52,7 +52,7 @@ Optional: ```yaml 'cast_youtube_to_my_chromecast': - alias: Cast YouTube to My Chromecast + alias: "Cast YouTube to My Chromecast" sequence: - data: entity_id: media_player.my_chromecast @@ -77,7 +77,7 @@ Optional: ```yaml 'cast_supla_to_my_chromecast': - alias: Cast supla to My Chromecast + alias: "Cast supla to My Chromecast" sequence: - data: entity_id: media_player.my_chromecast @@ -96,7 +96,7 @@ To cast media directly from a configured Plex server, set the fields [as documen ```yaml 'cast_plex_to_chromecast': - alias: Cast Plex to Chromecast + alias: "Cast Plex to Chromecast" sequence: - service: media_player.play_media data: diff --git a/source/_integrations/color_extractor.markdown b/source/_integrations/color_extractor.markdown index e35112f0064..ac2804212bf 100644 --- a/source/_integrations/color_extractor.markdown +++ b/source/_integrations/color_extractor.markdown @@ -59,7 +59,7 @@ Example usage in an automation, taking the album art present on a Chromecast and ```yaml #automation.yaml -- alias: Chromecast to Shelf Lights +- alias: "Chromecast to Shelf Lights" trigger: - platform: state @@ -76,7 +76,7 @@ With a nicer transition period of 5 seconds and setting brightness to 100% each ```yaml #automation.yaml -- alias: Nicer Chromecast to Shelf Lights +- alias: "Nicer Chromecast to Shelf Lights" trigger: - platform: state diff --git a/source/_integrations/counter.markdown b/source/_integrations/counter.markdown index ecc0c41d53f..1db050c705c 100644 --- a/source/_integrations/counter.markdown +++ b/source/_integrations/counter.markdown @@ -143,7 +143,7 @@ system_log: # Example configuration.yaml entry automation: - id: 'errorcounterautomation' - alias: Error Counting Automation + alias: "Error Counting Automation" trigger: platform: event event_type: system_log_event diff --git a/source/_integrations/deconz.markdown b/source/_integrations/deconz.markdown index 64abf427400..af6c13a0d65 100644 --- a/source/_integrations/deconz.markdown +++ b/source/_integrations/deconz.markdown @@ -195,7 +195,7 @@ Requesting support for additional devices requires the device model (can be acqu ```yaml automation: - - alias: 'Toggle lamp from dimmer' + - alias: "'Toggle lamp from dimmer'" initial_state: "on" trigger: platform: event @@ -207,7 +207,7 @@ automation: service: light.toggle entity_id: light.lamp - - alias: 'Increase brightness of lamp from dimmer' + - alias: "Increase brightness of lamp from dimmer" initial_state: "on" trigger: platform: event @@ -223,7 +223,7 @@ automation: {% set bri = state_attr('light.lamp', 'brightness') | int %} {{ [bri+30, 249] | min }} - - alias: 'Decrease brightness of lamp from dimmer' + - alias: "Decrease brightness of lamp from dimmer" initial_state: "on" trigger: platform: event @@ -260,7 +260,7 @@ automation: ```yaml automation: - - alias: React to color wheel changes + - alias: "React to color wheel changes" trigger: - platform: event event_type: deconz_event @@ -285,7 +285,7 @@ Note: Requires `on: true` to change color while the Philips Hue bulb is off. If ```yaml automation: - - alias: Flash Hue Bulb with Doorbell Motion + - alias: "Flash Hue Bulb with Doorbell Motion" mode: single trigger: - platform: state diff --git a/source/_integrations/device_automation.markdown b/source/_integrations/device_automation.markdown index e1ad32b361c..7d1df4a667b 100644 --- a/source/_integrations/device_automation.markdown +++ b/source/_integrations/device_automation.markdown @@ -20,7 +20,7 @@ Example: ```yaml - id: "123456789" - alias: Light turns off + alias: "Light turns off" trigger: - platform: device device_id: 7a92d5ee74014a0b86903fc669b0bcd6 diff --git a/source/_integrations/dexcom.markdown b/source/_integrations/dexcom.markdown index 4aafc076adc..55ccaedf8b4 100644 --- a/source/_integrations/dexcom.markdown +++ b/source/_integrations/dexcom.markdown @@ -44,7 +44,7 @@ If you have a sensor session running, and once you have enabled the Dexcom integ ```yaml - id: '1234567890123' - alias: overnight_low_kitchen_lights + alias: "overnight_low_kitchen_lights" description: Turn on the lights in the kitchen if my blood sugar drops low overnight trigger: - below: '65' diff --git a/source/_integrations/doods.markdown b/source/_integrations/doods.markdown index 029094d6650..691421502df 100644 --- a/source/_integrations/doods.markdown +++ b/source/_integrations/doods.markdown @@ -209,7 +209,7 @@ image_processing: ```yaml # Example advanced automations.yaml entry -- alias: Doods scanning +- alias: "Doods scanning" trigger: - platform: state entity_id: diff --git a/source/_integrations/doorbird.markdown b/source/_integrations/doorbird.markdown index 43e994a8039..bb6585e1332 100644 --- a/source/_integrations/doorbird.markdown +++ b/source/_integrations/doorbird.markdown @@ -173,7 +173,7 @@ Note: Remember to complete the schedule assignment steps above for each event ty ### Automation Example ```yaml -- alias: Doorbird Ring +- alias: "Doorbird Ring" trigger: platform: event event_type: doorbird_driveway_gate_somebody_pressed_the_button diff --git a/source/_integrations/dovado.markdown b/source/_integrations/dovado.markdown index 3e7923f228c..9bc766b5ba5 100644 --- a/source/_integrations/dovado.markdown +++ b/source/_integrations/dovado.markdown @@ -69,7 +69,7 @@ This is a notify platform and thus can be controlled by calling the notify servi ```yaml # Example automation notification entry automation: - - alias: The sun has set + - alias: "The sun has set" trigger: platform: sun event: sunset diff --git a/source/_integrations/downloader.markdown b/source/_integrations/downloader.markdown index b4957472fd7..15a65a93414 100644 --- a/source/_integrations/downloader.markdown +++ b/source/_integrations/downloader.markdown @@ -58,7 +58,7 @@ Along with the event the following payload parameters are available: #### Example Automation: ```yaml -- alias: Download Failed Notification +- alias: "Download Failed Notification" trigger: platform: event event_type: downloader_download_failed diff --git a/source/_integrations/emulated_roku.markdown b/source/_integrations/emulated_roku.markdown index c06b44b74f6..3e6bdb0b292 100644 --- a/source/_integrations/emulated_roku.markdown +++ b/source/_integrations/emulated_roku.markdown @@ -109,7 +109,7 @@ The following is an example implementation of an automation: ```yaml # Example automation - id: amp_volume_up - alias: Increase amplifier volume + alias: "Increase amplifier volume" trigger: - platform: event event_type: roku_command diff --git a/source/_integrations/enocean.markdown b/source/_integrations/enocean.markdown index ca72a39b60b..8c164366c85 100644 --- a/source/_integrations/enocean.markdown +++ b/source/_integrations/enocean.markdown @@ -133,7 +133,7 @@ Sample automation to switch lights on and off: ```yaml # Example automation to turn lights on/off on button release automation: - - alias: hall light switches + - alias: "hall light switches" trigger: platform: event event_type: button_pressed diff --git a/source/_integrations/facebook.markdown b/source/_integrations/facebook.markdown index 9a0a6f49229..04a0dd354aa 100644 --- a/source/_integrations/facebook.markdown +++ b/source/_integrations/facebook.markdown @@ -42,7 +42,7 @@ The phone number used in **target** should be registered with Facebook messenger ```yaml # Example automation notification entry automation: - - alias: Evening Greeting + - alias: "Evening Greeting" trigger: platform: sun event: sunset diff --git a/source/_integrations/facebox.markdown b/source/_integrations/facebox.markdown index c4ea7fabee6..466add0f713 100644 --- a/source/_integrations/facebox.markdown +++ b/source/_integrations/facebox.markdown @@ -99,7 +99,7 @@ Use the `image_processing.detect_face` events to trigger automations, and breako ```yaml - id: '12345' - alias: Ringo Starr recognised + alias: "Ringo Starr recognised" trigger: platform: event event_type: image_processing.detect_face @@ -144,7 +144,7 @@ You can use an automation to receive a notification when you train a face: ```yaml - id: '1533703568569' - alias: Face taught + alias: "Face taught" trigger: - event_data: service: facebox.teach_face @@ -174,7 +174,7 @@ you can create an automation to receive notifications on Facebox errors: ```yaml - id: '1533703568577' - alias: Facebox error + alias: "Facebox error" trigger: platform: event event_type: system_log_event diff --git a/source/_integrations/feedreader.markdown b/source/_integrations/feedreader.markdown index 5040a7e7ee2..2f053cdb2c0 100644 --- a/source/_integrations/feedreader.markdown +++ b/source/_integrations/feedreader.markdown @@ -56,7 +56,7 @@ Feedreader events can be used out of the box to trigger automation actions, e.g. ```yaml automation: - - alias: Trigger action when new element(s) in RSS feed + - alias: "Trigger action when new element(s) in RSS feed" trigger: platform: event event_type: feedreader @@ -69,7 +69,7 @@ automation: ```yaml automation: - - alias: Send notification of RSS feed title when updated + - alias: "Send notification of RSS feed title when updated" trigger: platform: event event_type: feedreader diff --git a/source/_integrations/fireservicerota.markdown b/source/_integrations/fireservicerota.markdown index 897b0d3b14f..e51d8cd6965 100644 --- a/source/_integrations/fireservicerota.markdown +++ b/source/_integrations/fireservicerota.markdown @@ -120,7 +120,7 @@ These are documented below. ```yaml automation: - - alias: 'Switch on a light when incident is received' + - alias: "Switch on a light when incident is received" trigger: platform: state entity_id: sensor.incidents @@ -128,7 +128,7 @@ automation: service: light.turn_on entity_id: light.bedroom - - alias: 'Play TTS incident details when incident is received' + - alias: "Play TTS incident details when incident is received" trigger: platform: state entity_id: sensor.incidents @@ -148,7 +148,7 @@ automation: {{ state_attr('sensor.incidents','message_to_speech_url') }} media_content_type: "audio/mp4" - - alias: 'Send response acknowledgement when a button is pressed' + - alias: "Send response acknowledgement when a button is pressed" trigger: platform: state entity_id: switch.response_button @@ -156,7 +156,7 @@ automation: service: homeassistant.turn_on entity_id: switch.incident_response - - alias: 'Cast FireServiceRota dashboard to Nest Hub' + - alias: "Cast FireServiceRota dashboard to Nest Hub" trigger: platform: homeassistant event: start diff --git a/source/_integrations/flic.markdown b/source/_integrations/flic.markdown index 95793595187..9b133683ec8 100644 --- a/source/_integrations/flic.markdown +++ b/source/_integrations/flic.markdown @@ -72,7 +72,7 @@ The flic integration fires `flic_click` events on the bus. You can capture the e ```yaml # Example configuration.yaml automation entry automation: - - alias: Turn on lights in the living room when flic is pressed once + - alias: "Turn on lights in the living room when flic is pressed once" trigger: platform: event event_type: flic_click @@ -97,7 +97,7 @@ To help detect and debug flic button clicks, you can use this automation that se ```yaml automation: - - alias: FLIC Html5 notify on every click + - alias: "FLIC Html5 notify on every click" trigger: platform: event event_type: flic_click diff --git a/source/_integrations/folder_watcher.markdown b/source/_integrations/folder_watcher.markdown index 2cce5d200ee..33b0f844d9b 100644 --- a/source/_integrations/folder_watcher.markdown +++ b/source/_integrations/folder_watcher.markdown @@ -60,7 +60,7 @@ Automations can be triggered on filesystem event data using a template. The foll ```yaml #Send notification for new image (including the image itself) automation: -  alias: New file alert +  alias: "New file alert" trigger:   platform: event   event_type: folder_watcher diff --git a/source/_integrations/foursquare.markdown b/source/_integrations/foursquare.markdown index a758bf39fd0..3e2e960cc3a 100644 --- a/source/_integrations/foursquare.markdown +++ b/source/_integrations/foursquare.markdown @@ -50,7 +50,7 @@ Foursquare check-in events can be used out of the box to trigger automation acti ```yaml automation: - - alias: Trigger action when you check into a venue. + - alias: "Trigger action when you check into a venue." trigger: platform: event event_type: foursquare.push diff --git a/source/_integrations/geniushub.markdown b/source/_integrations/geniushub.markdown index 0cbe4ed547e..d4ca5207c17 100644 --- a/source/_integrations/geniushub.markdown +++ b/source/_integrations/geniushub.markdown @@ -85,7 +85,7 @@ Each such entity has a state attribute that will contain a list of any such issu {% raw %} ```yaml -- alias: GeniusHub Error Alerts +- alias: "GeniusHub Error Alerts" trigger: platform: numeric_state entity_id: sensor.geniushub_errors @@ -106,7 +106,7 @@ This alert may be useful to see if the CH is being turned on whilst you're on a {% raw %} ```yaml -- alias: GeniusHub CH State Change Alert +- alias: "GeniusHub CH State Change Alert" trigger: platform: state entity_id: binary_sensor.dual_channel_receiver_2_1 diff --git a/source/_integrations/geo_location.markdown b/source/_integrations/geo_location.markdown index 99bb17982af..88e1dbee7b2 100644 --- a/source/_integrations/geo_location.markdown +++ b/source/_integrations/geo_location.markdown @@ -51,7 +51,7 @@ zone: passive: true automation: - - alias: 'Bush Fire Alert' + - alias: "Bush Fire Alert" trigger: platform: geo_location source: nsw_rural_fire_service_feed diff --git a/source/_integrations/griddy.markdown b/source/_integrations/griddy.markdown index 124e77eeb5c..d80eaae315a 100644 --- a/source/_integrations/griddy.markdown +++ b/source/_integrations/griddy.markdown @@ -51,7 +51,7 @@ The current price for the Load Zone will appear as a sensor: ```yaml - id: '1572630019168' - alias: Stop Tesla Charging if Power Price Spikes + alias: "Stop Tesla Charging if Power Price Spikes" description: "" trigger: - above: '30' diff --git a/source/_integrations/hangouts.markdown b/source/_integrations/hangouts.markdown index d86906b2af6..dbdec4615df 100644 --- a/source/_integrations/hangouts.markdown +++ b/source/_integrations/hangouts.markdown @@ -244,7 +244,7 @@ sensor: scan_interval: 10 automation: - - alias: Reconnect Hangouts + - alias: "Reconnect Hangouts" trigger: - entity_id: sensor.external_ip platform: state diff --git a/source/_integrations/homematic.markdown b/source/_integrations/homematic.markdown index e5a7bf3d784..3c8b7db2940 100644 --- a/source/_integrations/homematic.markdown +++ b/source/_integrations/homematic.markdown @@ -456,7 +456,7 @@ binary_sensor: {{as_timestamp(now()) - as_timestamp(states.sensor.office_voltage.last_changed) < 600}} automation: - - alias: Homematic Reconnect + - alias: "Homematic Reconnect" trigger: platform: state entity_id: binary_sensor.homematic_up @@ -503,7 +503,7 @@ automation: ```yaml automation: - - alias: Homematic CCU Reboot + - alias: "Homematic CCU Reboot" trigger: platform: state entity_id: sensor.v_last_reboot diff --git a/source/_integrations/html5.markdown b/source/_integrations/html5.markdown index ee266026a3f..5cd78f68317 100644 --- a/source/_integrations/html5.markdown +++ b/source/_integrations/html5.markdown @@ -171,7 +171,7 @@ Example of adding a tag to your notification. This won't create new notification {% raw %} ```yaml - - alias: Push/update notification of sensor state with tag + - alias: "Push/update notification of sensor state with tag" trigger: - platform: state entity_id: sensor.sensor @@ -272,7 +272,7 @@ You will receive an event named `html5_notification.received` when the notification is received on the device. ```yaml -- alias: HTML5 push notification received and displayed on device +- alias: "HTML5 push notification received and displayed on device" trigger: platform: event event_type: html5_notification.received @@ -283,7 +283,7 @@ notification is received on the device. You will receive an event named `html5_notification.clicked` when the notification or a notification action button is clicked. The action button clicked is available as `action` in the `event_data`. ```yaml -- alias: HTML5 push notification clicked +- alias: "HTML5 push notification clicked" trigger: platform: event event_type: html5_notification.clicked @@ -292,7 +292,7 @@ You will receive an event named `html5_notification.clicked` when the notificati or ```yaml -- alias: HTML5 push notification action button clicked +- alias: "HTML5 push notification action button clicked" trigger: platform: event event_type: html5_notification.clicked @@ -305,7 +305,7 @@ or You will receive an event named `html5_notification.closed` when the notification is closed. ```yaml -- alias: HTML5 push notification clicked +- alias: "HTML5 push notification clicked" trigger: platform: event event_type: html5_notification.closed diff --git a/source/_integrations/hyperion.markdown b/source/_integrations/hyperion.markdown index cdb61adb563..c8028ae5ee6 100644 --- a/source/_integrations/hyperion.markdown +++ b/source/_integrations/hyperion.markdown @@ -93,7 +93,7 @@ To start Hyperion with an effect, use the following automation: ```yaml automation: - id: one - alias: Turn Hyperion effect on when light goes on + alias: "Turn Hyperion effect on when light goes on" trigger: - platform: state entity_id: light.hyperion @@ -108,7 +108,7 @@ automation: To have the lights playing an effect when pausing, idle or turn off a media player like Plex you can use this example: ```yaml -- alias: Set hyperion effect after playback +- alias: "Set hyperion effect after playback" trigger: - platform: state entity_id: media_player.plex @@ -129,7 +129,7 @@ To have the lights playing an effect when pausing, idle or turn off a media play To capture the screen when playing something on a media_player you can use this example: ```yaml -- alias: Set hyperion when playback starts +- alias: "Set hyperion when playback starts" trigger: - platform: state entity_id: media_player.plex diff --git a/source/_integrations/ifttt.markdown b/source/_integrations/ifttt.markdown index 08c60b78f2d..89a44f95910 100644 --- a/source/_integrations/ifttt.markdown +++ b/source/_integrations/ifttt.markdown @@ -38,7 +38,7 @@ You then need to consume that incoming information with the following automation ```yaml automation: - id: this_is_the_automation_id - alias: The optional automation alias + alias: "The optional automation alias" trigger: - event_data: action: call_service @@ -131,7 +131,7 @@ You need to setup a unique trigger for each event you sent to IFTTT. ```yaml # Example configuration.yaml Automation entry automation: - alias: Startup Notification + alias: "Startup Notification" trigger: platform: homeassistant event: start @@ -149,7 +149,7 @@ IFTTT can also be used in scripts and with templates. Here is the above automati ```yaml # Example configuration.yaml Automation entry automation: - alias: Startup Notification + alias: "Startup Notification" trigger: platform: homeassistant event: start diff --git a/source/_integrations/image_processing.markdown b/source/_integrations/image_processing.markdown index 257528d283d..bbf22daa65e 100644 --- a/source/_integrations/image_processing.markdown +++ b/source/_integrations/image_processing.markdown @@ -19,7 +19,7 @@ The `found_plate` event is triggered after OpenALPR has found a new license plat ```yaml # Example configuration.yaml automation entry automation: -- alias: Open garage door +- alias: "Open garage door" trigger: platform: event event_type: image_processing.found_plate @@ -40,7 +40,7 @@ The `detect_face` event is triggered after a Face entity has found a face. ```yaml # Example configuration.yaml automation entry automation: -- alias: Known person in front of my door +- alias: "Known person in front of my door" trigger: platform: event event_type: image_processing.detect_face @@ -63,7 +63,7 @@ sensor: scan_interval: 10000 ... automation: -- alias: Scan for faces when motion detected +- alias: "Scan for faces when motion detected" trigger: - platform: state entity_id: sensor.door_motion_sensor diff --git a/source/_integrations/incomfort.markdown b/source/_integrations/incomfort.markdown index df39b46a922..8fed80e40c7 100644 --- a/source/_integrations/incomfort.markdown +++ b/source/_integrations/incomfort.markdown @@ -41,7 +41,7 @@ To send an alert if the CV pressure is too low or too high, consider the followi {% raw %} ```yaml -- alias: Low CV Pressure Alert +- alias: "Low CV Pressure Alert" trigger: platform: numeric_state entity_id: sensor.cv_pressure diff --git a/source/_integrations/input_boolean.markdown b/source/_integrations/input_boolean.markdown index 17fb74f5b66..77fd350c25a 100644 --- a/source/_integrations/input_boolean.markdown +++ b/source/_integrations/input_boolean.markdown @@ -71,7 +71,7 @@ Here's an example of an automation using the above `input_boolean`. This action ```yaml automation: - alias: Arriving home + alias: "Arriving home" trigger: platform: state entity_id: binary_sensor.motion_garage diff --git a/source/_integrations/input_number.markdown b/source/_integrations/input_number.markdown index f1264939204..0248fac164c 100644 --- a/source/_integrations/input_number.markdown +++ b/source/_integrations/input_number.markdown @@ -125,7 +125,7 @@ input_number: max: 254 step: 1 automation: - - alias: Bedroom Light - Adjust Brightness + - alias: "Bedroom Light - Adjust Brightness" trigger: platform: state entity_id: input_number.bedroom_brightness @@ -163,7 +163,7 @@ input_number: max: 254 step: 1 automation: - - alias: Bedroom Light - Custom + - alias: "Bedroom Light - Custom" trigger: platform: state entity_id: input_select.scene_bedroom @@ -195,7 +195,7 @@ input_number: # This automation script runs when a value is received via MQTT on retained topic: setTemperature # It sets the value slider on the GUI. This slides also had its own automation when the value is changed. automation: - - alias: Set temp slider + - alias: "Set temp slider" trigger: platform: mqtt topic: "setTemperature" @@ -207,7 +207,7 @@ automation: # This second automation script runs when the target temperature slider is moved. # It publishes its value to the same MQTT topic it is also subscribed to. - - alias: Temp slider moved + - alias: "Temp slider moved" trigger: platform: state entity_id: input_number.target_temp @@ -245,7 +245,7 @@ input_number: step: 10 automation: - - alias: turn something off after x time after turning it on + - alias: "turn something off after x time after turning it on" trigger: platform: state entity_id: switch.something diff --git a/source/_integrations/input_select.markdown b/source/_integrations/input_select.markdown index 2b4dd5238ec..df0f45ac534 100644 --- a/source/_integrations/input_select.markdown +++ b/source/_integrations/input_select.markdown @@ -135,7 +135,7 @@ The following example shows the usage of the `input_select.select_option` servic ```yaml # Example configuration.yaml entry automation: - - alias: example automation + - alias: "example automation" trigger: platform: event event_type: MY_CUSTOM_EVENT @@ -151,7 +151,7 @@ To dynamically set the `input_select` options you can call `input_select.set_opt ```yaml # Example configuration.yaml entry automation: - - alias: example automation + - alias: "example automation" trigger: platform: event event_type: MY_CUSTOM_EVENT @@ -183,7 +183,7 @@ input_select: # Automation. # This automation script runs when a value is received via MQTT on retained topic: thermostatMode # It sets the value selector on the GUI. This selector also had its own automation when the value is changed. -- alias: Set Thermostat Mode Selector +- alias: "Set Thermostat Mode Selector" trigger: platform: mqtt topic: "thermostatMode" @@ -196,7 +196,7 @@ input_select: # This automation script runs when the thermostat mode selector is changed. # It publishes its value to the same MQTT topic it is also subscribed to. -- alias: Set Thermostat Mode +- alias: "Set Thermostat Mode" trigger: platform: state entity_id: input_select.thermostat_mode diff --git a/source/_integrations/input_text.markdown b/source/_integrations/input_text.markdown index 7a6fb1b552e..e574b3246e9 100644 --- a/source/_integrations/input_text.markdown +++ b/source/_integrations/input_text.markdown @@ -127,7 +127,7 @@ input_text: name: Brightness automation: - - alias: Bedroom Light - Custom + - alias: "Bedroom Light - Custom" trigger: platform: state entity_id: input_select.scene_bedroom diff --git a/source/_integrations/insteon.markdown b/source/_integrations/insteon.markdown index 50a9e82f06b..26551c1eb19 100644 --- a/source/_integrations/insteon.markdown +++ b/source/_integrations/insteon.markdown @@ -103,7 +103,7 @@ Trigger an INSTEON scene on or off, is done via automations. Two services are pr automation: # Trigger an INSTEON scene 25 - id: trigger_scene_25_on - alias: Turn on scene 25 + alias: "Turn on scene 25" action: - service: insteon.scene_on group: 25 @@ -126,7 +126,7 @@ This allows the mini-remotes to be configured as triggers for automations. Here automation: # 4 or 8 button remote with button c pressed - id: light_on - alias: Turn a light on + alias: "Turn a light on" trigger: - platform: event event_type: insteon.button_on @@ -143,7 +143,7 @@ automation: # single button remote - id: light_off - alias: Turn a light off + alias: "Turn a light off" trigger: - platform: event event_type: insteon.button_on @@ -361,7 +361,7 @@ Trigger an INSTEON scene on or off is done via automations. Two services are pro automation: # Trigger an INSTEON scene 25 - id: trigger_scene_25_on - alias: Turn on scene 25 + alias: "Turn on scene 25" trigger: - ... action: @@ -387,7 +387,7 @@ This allows the mini-remotes to be configured as triggers for automations. Here automation: # 4 or 8 button remote with button c pressed - id: light_on - alias: Turn a light on + alias: "Turn a light on" trigger: - platform: event event_type: insteon.button_on @@ -404,7 +404,7 @@ automation: # single button remote - id: light_off - alias: Turn a light off + alias: "Turn a light off" trigger: - platform: event event_type: insteon.button_on diff --git a/source/_integrations/isy994.markdown b/source/_integrations/isy994.markdown index 5890a64e7fe..13581ea987b 100644 --- a/source/_integrations/isy994.markdown +++ b/source/_integrations/isy994.markdown @@ -117,7 +117,7 @@ A Home Assistant `isy994_control` event is emitted for every "control" event in ```yaml automation: - - alias: turn off living room on double tap lightswitch + - alias: "turn off living room on double tap lightswitch" trigger: platform: event event_type: isy994_control diff --git a/source/_integrations/keyboard_remote.markdown b/source/_integrations/keyboard_remote.markdown index 323c4c65109..db7d97d197b 100644 --- a/source/_integrations/keyboard_remote.markdown +++ b/source/_integrations/keyboard_remote.markdown @@ -84,7 +84,7 @@ And an automation rule to breathe life into it: ```yaml automation: - alias: Keyboard all lights on + alias: "Keyboard all lights on" trigger: platform: event event_type: keyboard_remote_command_received @@ -109,7 +109,7 @@ Here's an automation example that plays a sound through a media player whenever ```yaml automation: - - alias: Keyboard Connected + - alias: "Keyboard Connected" trigger: platform: event event_type: keyboard_remote_connected @@ -120,7 +120,7 @@ automation: media_content_id: keyboard_connected.wav media_content_type: music - - alias: Bluetooth Keyboard Disconnected + - alias: "Bluetooth Keyboard Disconnected" trigger: platform: event event_type: keyboard_remote_disconnected diff --git a/source/_integrations/kira.markdown b/source/_integrations/kira.markdown index 23a7bf55501..d3873cdbfe3 100644 --- a/source/_integrations/kira.markdown +++ b/source/_integrations/kira.markdown @@ -208,7 +208,7 @@ Example automation using these IR codes to toggle a Sonoff plug. ```yaml # Example kira_sensor - id: "1583339338363" - alias: Panasonic On + alias: "Panasonic On" description: Turn on sonoff s20 relay trigger: - entity_id: sensor.kira_wireless diff --git a/source/_integrations/kodi.markdown b/source/_integrations/kodi.markdown index 7a619008edd..383eb2c4d0d 100644 --- a/source/_integrations/kodi.markdown +++ b/source/_integrations/kodi.markdown @@ -230,13 +230,13 @@ This example and the following requires to have the [script.json-cec](https://gi ```yaml script: play_kodi_pvr: - alias: Turn on the silly box + alias: "Turn on the silly box" sequence: - - alias: TV on + - alias: "TV on" service: media_player.turn_on data: entity_id: media_player.kodi - - alias: Play TV channel + - alias: "Play TV channel" service: media_player.play_media data: entity_id: media_player.kodi @@ -266,9 +266,9 @@ script: ```yaml script: play_kodi_smp: - alias: Turn on the silly box with random Firefighter Sam episode + alias: "Turn on the silly box with random Firefighter Sam episode" sequence: - - alias: TV on + - alias: "TV on" service: media_player.turn_on data: entity_id: media_player.kodi @@ -286,9 +286,9 @@ script: ```yaml script: update_library: - alias: Update Kodi Library + alias: "Update Kodi Library" sequence: - - alias: Call Kodi update + - alias: "Call Kodi update" service: kodi.call_method data: entity_id: media_player.kodi diff --git a/source/_integrations/life360.markdown b/source/_integrations/life360.markdown index 72145df6444..6be2c18f9ca 100644 --- a/source/_integrations/life360.markdown +++ b/source/_integrations/life360.markdown @@ -211,7 +211,7 @@ life360: ```yaml automation: - - alias: Life360 Overdue Update + - alias: "Life360 Overdue Update" trigger: platform: event event_type: life360_update_overdue @@ -225,7 +225,7 @@ automation: trigger.event.data.entity_id }} is overdue. - - alias: Life360 Update Restored + - alias: "Life360 Update Restored" trigger: platform: event event_type: life360_update_restored diff --git a/source/_integrations/lifx.markdown b/source/_integrations/lifx.markdown index ca93a2d3ef9..cb0dbe383ea 100644 --- a/source/_integrations/lifx.markdown +++ b/source/_integrations/lifx.markdown @@ -42,7 +42,7 @@ Change the light to a new state. The LIFX platform supports several light effects. You can start these effects with default options by using the `effect` attribute of the normal [`light.turn_on`](/integrations/light/#service-lightturn_on) service, for example like this: ```yaml automation: - - alias: ... + - alias: "..." trigger: # ... action: diff --git a/source/_integrations/light.group.markdown b/source/_integrations/light.group.markdown index 4be4de0486c..3ca34f72dac 100644 --- a/source/_integrations/light.group.markdown +++ b/source/_integrations/light.group.markdown @@ -50,7 +50,7 @@ Here's an example of a script using the above light group. ```yaml script: turn_on_kitchen_lights: - alias: Kitchen lights on + alias: "Kitchen lights on" sequence: service: light.turn_on data: diff --git a/source/_integrations/light.markdown b/source/_integrations/light.markdown index e4c9f8d3356..2b89ee40d6f 100644 --- a/source/_integrations/light.markdown +++ b/source/_integrations/light.markdown @@ -52,7 +52,7 @@ In order to apply attributes to an entity, you will need to add `data:` to the c # Example configuration.yaml entry automation: - id: one - alias: Turn on light when motion is detected + alias: "Turn on light when motion is detected" trigger: - platform: state entity_id: binary_sensor.motion_1 @@ -67,7 +67,7 @@ automation: ```yaml # Ledlist morning on, red - id: llmor - alias: Stair morning on + alias: "Stair morning on" trigger: - at: '05:00' platform: time diff --git a/source/_integrations/limitlessled.markdown b/source/_integrations/limitlessled.markdown index 355deb895e9..d1d40480d07 100644 --- a/source/_integrations/limitlessled.markdown +++ b/source/_integrations/limitlessled.markdown @@ -106,7 +106,7 @@ Note that the `brightness`, `color` and `temperature` attributes cannot be used ```yaml automation: - - alias: ... + - alias: "..." trigger: # ... action: diff --git a/source/_integrations/lirc.markdown b/source/_integrations/lirc.markdown index a099ccd5b1c..114743564ba 100644 --- a/source/_integrations/lirc.markdown +++ b/source/_integrations/lirc.markdown @@ -83,7 +83,7 @@ The LIRC integration fires `ir_command_received` events on the bus. You can capt ```yaml # Example configuration.yaml automation entry automation: - - alias: Off on Remote + - alias: "Off on Remote" trigger: platform: event event_type: ir_command_received diff --git a/source/_integrations/logbook.markdown b/source/_integrations/logbook.markdown index d9f2ba10af5..2b24e905444 100644 --- a/source/_integrations/logbook.markdown +++ b/source/_integrations/logbook.markdown @@ -167,7 +167,7 @@ component to fire an event. # Example configuration.yaml entry script: add_logbook_entry: - alias: Add Logbook + alias: "Add Logbook" sequence: - service: logbook.log data: diff --git a/source/_integrations/meteoalarm.markdown b/source/_integrations/meteoalarm.markdown index 8c563bf1647..3d62ce222eb 100644 --- a/source/_integrations/meteoalarm.markdown +++ b/source/_integrations/meteoalarm.markdown @@ -91,7 +91,7 @@ Below you find an example of an automation. ```yaml automation: - - alias: Alert me about weather warnings + - alias: "Alert me about weather warnings" trigger: platform: state entity_id: binary_sensor.meteoalarm diff --git a/source/_integrations/miflora.markdown b/source/_integrations/miflora.markdown index 69f834de04a..a384fa18147 100644 --- a/source/_integrations/miflora.markdown +++ b/source/_integrations/miflora.markdown @@ -140,7 +140,7 @@ An automation example to report a battery failure: ```yaml - id: flower1_moisture_unavailable_check - alias: Flower 1 sensors available + alias: "Flower 1 sensors available" trigger: - entity_id: sensor.flower1_moisture for: 24:00:00 diff --git a/source/_integrations/minio.markdown b/source/_integrations/minio.markdown index 014438a248b..491237cc237 100644 --- a/source/_integrations/minio.markdown +++ b/source/_integrations/minio.markdown @@ -85,7 +85,7 @@ Automations can be triggered on new files created on the Minio server using the ```yaml #Automatically upload new local files automation: -- alias: Upload camera snapshot +- alias: "Upload camera snapshot" trigger: platform: event event_type: folder_watcher @@ -103,7 +103,7 @@ automation: data: file: "{{ trigger.event.data.path }}" -- alias: Download new Minio file +- alias: "Download new Minio file" trigger: - platform: event event_type: minio diff --git a/source/_integrations/modem_callerid.markdown b/source/_integrations/modem_callerid.markdown index 50c47eac9fb..4a2c34f0556 100644 --- a/source/_integrations/modem_callerid.markdown +++ b/source/_integrations/modem_callerid.markdown @@ -71,7 +71,7 @@ Some example automations: ```yaml automation: - - alias: Notify CallerID + - alias: "Notify CallerID" trigger: platform: state entity_id: sensor.modem_callerid @@ -80,7 +80,7 @@ automation: service: notify.notify data: message: "Call from {{ state_attr('sensor.modem_callerid', 'cid_name') }} at {{ state_attr('sensor.modem_callerid', 'cid_number') }} " - - alias: Notify CallerID webui + - alias: "Notify CallerID webui" trigger: platform: state entity_id: sensor.modem_callerid @@ -90,7 +90,7 @@ automation: data: title: "Call from" message: "{{ state_attr('sensor.modem_callerid', 'cid_time').strftime("%I:%M %p") }} {{ state_attr('sensor.modem_callerid', 'cid_name') }} {{ state_attr('sensor.modem_callerid', 'cid_number') }} " - - alias: Say CallerID + - alias: "Say CallerID" trigger: platform: state entity_id: sensor.modem_callerid diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index 50a5e52db52..0b039074864 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -326,7 +326,7 @@ The lower level Pub/Sub subscriber receives events in real time and internally f This automation will trigger when a `nest_event` event type with a type of `camera_motion` is received from the specified `device_id`. ```yaml -alias: motion alert +alias: "motion alert" trigger: - platform: event event_type: nest_event diff --git a/source/_integrations/netatmo.markdown b/source/_integrations/netatmo.markdown index e8e810626b6..317cde3602c 100644 --- a/source/_integrations/netatmo.markdown +++ b/source/_integrations/netatmo.markdown @@ -119,7 +119,7 @@ Example: ```yaml # Example automation for webhooks based Netatmo events -- alias: Netatmo event example +- alias: "Netatmo event example" description: "Count all events pushed by the Netatmo API" trigger: - event_data: {} @@ -137,7 +137,7 @@ Example: ```yaml # Example automation for Netatmo Welcome -- alias: Motion at home +- alias: "Motion at home" description: "Motion detected at home" trigger: - event_type: netatmo_event @@ -161,7 +161,7 @@ Example: ```yaml # Example automation for Netatmo Presence -- alias: Motion at home +- alias: "Motion at home" description: "Motion detected at home" trigger: - event_type: netatmo_event @@ -185,7 +185,7 @@ Example: ```yaml # Example automation -- alias: door or window open or movement +- alias: "door or window open or movement" description: "Notifies which door or window is open or was moved" trigger: - event_type: netatmo_event diff --git a/source/_integrations/netgear_lte.markdown b/source/_integrations/netgear_lte.markdown index 2dceb73ca24..7cd21983974 100644 --- a/source/_integrations/netgear_lte.markdown +++ b/source/_integrations/netgear_lte.markdown @@ -190,7 +190,7 @@ The following automation example processes incoming SMS messages with the [Conve ```yaml automation: - - alias: SMS conversation + - alias: "SMS conversation" trigger: - platform: event event_type: netgear_lte_sms diff --git a/source/_integrations/nightscout.markdown b/source/_integrations/nightscout.markdown index b5a5c2a7a1a..38b219f3be5 100644 --- a/source/_integrations/nightscout.markdown +++ b/source/_integrations/nightscout.markdown @@ -38,7 +38,7 @@ The state is the last reading from Nightscout, and you can see other information ```yaml - id: "1234567890123" - alias: overnight_low_kitchen_lights + alias: "overnight_low_kitchen_lights" description: Turn on the lights in the kitchen if my blood sugar drops low overnight trigger: - below: "65" diff --git a/source/_integrations/nzbget.markdown b/source/_integrations/nzbget.markdown index 660ee974cd5..5de505994d0 100644 --- a/source/_integrations/nzbget.markdown +++ b/source/_integrations/nzbget.markdown @@ -51,7 +51,7 @@ Example automation to send a Telegram message on a completed download: {% raw %} ```yaml -- alias: Completed Torrent +- alias: "Completed Torrent" trigger: platform: event event_type: nzbget_download_complete diff --git a/source/_integrations/openuv.markdown b/source/_integrations/openuv.markdown index 116ac22ad63..97108315d91 100644 --- a/source/_integrations/openuv.markdown +++ b/source/_integrations/openuv.markdown @@ -94,7 +94,7 @@ usage is to only retrieve data during the daytime: ```yaml automation: - - alias: Update OpenUV every 30 minutes during the daytime + - alias: "Update OpenUV every 30 minutes during the daytime" trigger: platform: time_pattern minutes: "/30" @@ -115,7 +115,7 @@ Update the UV index data every 20 minutes while the sun is at least 10 degrees a ```yaml automation: - - alias: Update OpenUV every 20 minutes while the sun is at least 10 degrees above the horizon + - alias: "Update OpenUV every 20 minutes while the sun is at least 10 degrees above the horizon" trigger: platform: time_pattern minutes: "/20" @@ -134,7 +134,7 @@ Update the protection window once a day: ```yaml automation: - - alias: Update OpenUV protection window once a day + - alias: "Update OpenUV protection window once a day" trigger: platform: time at: "02:12:00" @@ -148,7 +148,7 @@ etc.) might be to simply query the API less often: ```yaml automation: - - alias: Update OpenUV every hour (24 of 50 calls per day) + - alias: "Update OpenUV every hour (24 of 50 calls per day)" trigger: platform: time_pattern minutes: "/60" diff --git a/source/_integrations/point.markdown b/source/_integrations/point.markdown index be2d32f2496..1ca4a7fac9f 100644 --- a/source/_integrations/point.markdown +++ b/source/_integrations/point.markdown @@ -100,7 +100,7 @@ The following example show how to implement an automation for the **button_press ```yaml # Example configuration.yaml Automation entry automation: - alias: Point button press + alias: "Point button press" trigger: - platform: state entity_id: binary_sensor.point_button_press # Change this accordingly @@ -121,7 +121,7 @@ The events shown as [binary sensors](#binary-sensor) are sent to Home Assistant ```yaml # Example configuration.yaml Automation entry automation: - alias: Point button press (webhook) + alias: "Point button press (webhook)" trigger: - platform: event event_type: point_webhook_received diff --git a/source/_integrations/qwikswitch.markdown b/source/_integrations/qwikswitch.markdown index 347ef539cd3..16759635816 100644 --- a/source/_integrations/qwikswitch.markdown +++ b/source/_integrations/qwikswitch.markdown @@ -100,7 +100,7 @@ QwikSwitch devices (i.e., transmitter buttons) will fire events on the Home Assi ```yaml automation: - - alias: Action - Respond to A button press + - alias: "Action - Respond to A button press" trigger: platform: event event_type: qwikswitch.button.@12df34 diff --git a/source/_integrations/rainbird.markdown b/source/_integrations/rainbird.markdown index 5e2260c7396..2e33133204f 100644 --- a/source/_integrations/rainbird.markdown +++ b/source/_integrations/rainbird.markdown @@ -124,7 +124,7 @@ The service can be used as part of an automation script. For example: ```yaml # Example configuration.yaml automation entry automation: - - alias: Turn irrigation on + - alias: "Turn irrigation on" trigger: platform: time at: "5:30:00" diff --git a/source/_integrations/rfxtrx.markdown b/source/_integrations/rfxtrx.markdown index 29453b9e107..b9897cb45cb 100644 --- a/source/_integrations/rfxtrx.markdown +++ b/source/_integrations/rfxtrx.markdown @@ -280,7 +280,7 @@ scene: light.ceiling_lights: off automation: - - alias: Use doorbell button to trigger scene + - alias: "Use doorbell button to trigger scene" trigger: - platform: event event_type: rfxtrx_event diff --git a/source/_integrations/satel_integra.markdown b/source/_integrations/satel_integra.markdown index 49877af7fb4..61c808a7f83 100644 --- a/source/_integrations/satel_integra.markdown +++ b/source/_integrations/satel_integra.markdown @@ -166,7 +166,7 @@ Having configured the zones and the outputs, you can use them for automation, su For example: ```yaml - alias: Flick the input switch when movement in bedroom detected + alias: "Flick the input switch when movement in bedroom detected" trigger: platform: state entity_id: "binary_sensor.bedroom" diff --git a/source/_integrations/scene.markdown b/source/_integrations/scene.markdown index 8e1f34af395..36aaa670065 100644 --- a/source/_integrations/scene.markdown +++ b/source/_integrations/scene.markdown @@ -160,7 +160,7 @@ The following example turns off some entities as soon as a window opens. The sta ```yaml # Example automation using snapshot -- alias: Window opened +- alias: "Window opened" trigger: - platform: state entity_id: binary_sensor.window @@ -181,7 +181,7 @@ The following example turns off some entities as soon as a window opens. The sta data: entity_id: climate.ecobee hvac_mode: "off" -- alias: Window closed +- alias: "Window closed" trigger: - platform: state entity_id: binary_sensor.window diff --git a/source/_integrations/script.markdown b/source/_integrations/script.markdown index fff9c7a9643..9efdd9cc5f3 100644 --- a/source/_integrations/script.markdown +++ b/source/_integrations/script.markdown @@ -118,7 +118,7 @@ Mode | Description ```yaml script:  wakeup: - alias: Wake Up + alias: "Wake Up" icon: "mdi:party-popper" description: "Turns on the bedroom lights and then the living room lights after a delay" variables: @@ -137,7 +137,7 @@ script:  message: is waking up entity_id: device_tracker.paulus domain: light - - alias: Bedroom lights on + - alias: "Bedroom lights on" service: light.turn_on data: entity_id: group.bedroom @@ -145,7 +145,7 @@ script:  - delay: # supports seconds, milliseconds, minutes, hours minutes: "{{ minutes }}" - - alias: Living room lights on + - alias: "Living room lights on" service: light.turn_on data: entity_id: "{{ turn_on_entity }}" diff --git a/source/_integrations/shell_command.markdown b/source/_integrations/shell_command.markdown index bb6871df323..d349a15748b 100644 --- a/source/_integrations/shell_command.markdown +++ b/source/_integrations/shell_command.markdown @@ -40,7 +40,7 @@ Any service data passed into the service call to activate the shell command will ```yaml # Apply value of a GUI slider to the shell_command automation: - - alias: run_set_ac + - alias: "run_set_ac" trigger: platform: state entity_id: input_number.ac_temperature diff --git a/source/_integrations/smtp.markdown b/source/_integrations/smtp.markdown index 11aca820ceb..e42633e8400 100644 --- a/source/_integrations/smtp.markdown +++ b/source/_integrations/smtp.markdown @@ -104,7 +104,7 @@ To use the SMTP notification, refer to it in an automation or script like in thi ```yaml burglar: - alias: Burglar Alarm + alias: "Burglar Alarm" sequence: - service: shell_command.snapshot - delay: @@ -125,7 +125,7 @@ The optional `html` field makes a custom text/HTML multi-part message, allowing ```yaml burglar: - alias: Burglar Alarm + alias: "Burglar Alarm" sequence: - service: shell_command.snapshot - delay: diff --git a/source/_integrations/sonos.markdown b/source/_integrations/sonos.markdown index 1d11f960fab..b3b70a1d843 100644 --- a/source/_integrations/sonos.markdown +++ b/source/_integrations/sonos.markdown @@ -138,7 +138,7 @@ Removes an item from the queue. ```yaml # Example automation to remove just played song from queue -alias: Remove last played song from queue +alias: "Remove last played song from queue" id: Remove last played song from queue trigger: - platform: state diff --git a/source/_integrations/spc.markdown b/source/_integrations/spc.markdown index 4c347973ecc..3d7ab6595f3 100644 --- a/source/_integrations/spc.markdown +++ b/source/_integrations/spc.markdown @@ -53,7 +53,7 @@ The `changed_by` attribute enables one to be able to take different actions depe ```yaml automation: - - alias: Alarm status changed + - alias: "Alarm status changed" trigger: - platform: state entity_id: alarm_control_panel.alarm_1 diff --git a/source/_integrations/switch.mysensors.markdown b/source/_integrations/switch.mysensors.markdown index deedcba260d..c36c0962ef4 100644 --- a/source/_integrations/switch.mysensors.markdown +++ b/source/_integrations/switch.mysensors.markdown @@ -61,7 +61,7 @@ The service can be used as part of an automation script. For example: ```yaml # Example configuration.yaml automation entry automation: - - alias: Turn HVAC on + - alias: "Turn HVAC on" trigger: platform: time at: "5:30:00" @@ -71,7 +71,7 @@ automation: data: V_IR_SEND: "0xC284" # the IR code to send - - alias: Turn HVAC off + - alias: "Turn HVAC off" trigger: platform: time at: "0:30:00" diff --git a/source/_integrations/system_log.markdown b/source/_integrations/system_log.markdown index 58dda10f5b2..263da90fbf6 100644 --- a/source/_integrations/system_log.markdown +++ b/source/_integrations/system_log.markdown @@ -89,7 +89,7 @@ counter: icon: mdi:alert automation: - - alias: Count warnings + - alias: "Count warnings" trigger: platform: event event_type: system_log_event @@ -108,7 +108,7 @@ This automation will create a persistent notification whenever an error or warni ```yaml automation: - - alias: Create notifications for "service" errors + - alias: "Create notifications for "service" errors" trigger: platform: event event_type: system_log_event @@ -130,7 +130,7 @@ This automation will create a new log entry when the door is opened: ```yaml automation: - - alias: Log door opened + - alias: "Log door opened" trigger: platform: state entity_id: binary_sensor.door diff --git a/source/_integrations/tag.markdown b/source/_integrations/tag.markdown index 967f19b65f6..542d9d8e1c0 100644 --- a/source/_integrations/tag.markdown +++ b/source/_integrations/tag.markdown @@ -52,7 +52,7 @@ One of the most fun applications of tags is to pick music in your living room. T ```yaml automation: - id: handle_tag_scan - alias: Handle Tag Scan + alias: "Handle Tag Scan" mode: single # Hide warnings when triggered while in delay. max_exceeded: silent diff --git a/source/_integrations/tensorflow.markdown b/source/_integrations/tensorflow.markdown index 86636ab9d5f..4752c2dcdea 100644 --- a/source/_integrations/tensorflow.markdown +++ b/source/_integrations/tensorflow.markdown @@ -201,7 +201,7 @@ image_processing: ```yaml # Example advanced automations.yaml entry -- alias: TensorFlow scanning +- alias: "TensorFlow scanning" trigger: - platform: state entity_id: diff --git a/source/_integrations/thermoworks_smoke.markdown b/source/_integrations/thermoworks_smoke.markdown index 69fde0e96c5..a35918bb4e6 100644 --- a/source/_integrations/thermoworks_smoke.markdown +++ b/source/_integrations/thermoworks_smoke.markdown @@ -105,7 +105,7 @@ input_number: icon: mdi:thermometer automation: - - alias: Alert when My Smoke Probe 1 is above threshold + - alias: "Alert when My Smoke Probe 1 is above threshold" trigger: platform: template value_template: >- diff --git a/source/_integrations/timer.markdown b/source/_integrations/timer.markdown index 3d276826fc9..f38ee30c6f1 100644 --- a/source/_integrations/timer.markdown +++ b/source/_integrations/timer.markdown @@ -128,7 +128,7 @@ timer: ```yaml # Example automations.yaml entry -- alias: Timerswitch +- alias: "Timerswitch" id: "Timerstart" # Timer is started when the switch pumprun is set to on. trigger: @@ -140,7 +140,7 @@ timer: entity_id: timer.test # When timer is stopped, the time run out, another message is sent -- alias: Timerstop +- alias: "Timerstop" id: "Timerstop" trigger: - platform: event @@ -160,22 +160,22 @@ With the [`script`](/integrations/script/) integration you would be able to cont ```yaml script: start_timer: - alias: Start timer + alias: "Start timer" sequence: - service: timer.start entity_id: timer.test pause_timer: - alias: Pause timer + alias: "Pause timer" sequence: - service: timer.pause entity_id: timer.test cancel_timer: - alias: Cancel timer + alias: "Cancel timer" sequence: - service: timer.cancel entity_id: timer.test finish_timer: - alias: Finish timer + alias: "Finish timer" sequence: - service: timer.finish entity_id: timer.test diff --git a/source/_integrations/transmission.markdown b/source/_integrations/transmission.markdown index d13e286813d..3d730cb05d4 100644 --- a/source/_integrations/transmission.markdown +++ b/source/_integrations/transmission.markdown @@ -97,7 +97,7 @@ Example of an automation that notifies on successful download and removes the to {% raw %} ```yaml -- alias: Notify and remove completed torrent +- alias: "Notify and remove completed torrent" trigger: platform: event event_type: transmission_downloaded_torrent diff --git a/source/_integrations/twilio_call.markdown b/source/_integrations/twilio_call.markdown index f799e7416f1..67a3cb8d60d 100644 --- a/source/_integrations/twilio_call.markdown +++ b/source/_integrations/twilio_call.markdown @@ -44,7 +44,7 @@ Twilio is a notify platform and thus can be controlled by calling the notify ser ```yaml # Example automation notification entry automation: - - alias: The sun has set + - alias: "The sun has set" trigger: platform: sun event: sunset diff --git a/source/_integrations/twilio_sms.markdown b/source/_integrations/twilio_sms.markdown index ba4276ca77c..88e8706b96d 100644 --- a/source/_integrations/twilio_sms.markdown +++ b/source/_integrations/twilio_sms.markdown @@ -47,7 +47,7 @@ Media can be included with messages by setting the optional `media_url` variable ```yaml # Example automation notification entry automation: - - alias: The sun has set + - alias: "The sun has set" trigger: platform: sun event: sunset diff --git a/source/_integrations/universal.markdown b/source/_integrations/universal.markdown index 910d15b933b..c93da60d6d5 100644 --- a/source/_integrations/universal.markdown +++ b/source/_integrations/universal.markdown @@ -211,7 +211,7 @@ media_player: command: standby automation: -- alias: Turn on the TV when Kodi is activated +- alias: "Turn on the TV when Kodi is activated" trigger: platform: state entity_id: media_player.kodi_tv @@ -221,7 +221,7 @@ automation: - service: media_player.turn_on entity_id: media_player.kodi_tv -- alias: Turn off the TV when Kodi is in idle > 15 min +- alias: "Turn off the TV when Kodi is in idle > 15 min" trigger: platform: state entity_id: media_player.kodi_tv diff --git a/source/_integrations/upb.markdown b/source/_integrations/upb.markdown index b06a1abd7a2..6d0515a5072 100644 --- a/source/_integrations/upb.markdown +++ b/source/_integrations/upb.markdown @@ -173,7 +173,7 @@ Start a scene blinking. ```yaml #automation: -- alias: 'Specific scene activated' +- alias: "'Specific scene activated'" description: "Trigger when scene 9 on network 42 is activated" trigger: platform: event diff --git a/source/_integrations/updater.markdown b/source/_integrations/updater.markdown index 78f629f926a..d25a8ec712e 100644 --- a/source/_integrations/updater.markdown +++ b/source/_integrations/updater.markdown @@ -66,7 +66,7 @@ For an added bonus, an automation integration can be created to send a message w ```yaml # Example configuration.yaml entry automation: - alias: Update Available Notification + alias: "Update Available Notification" trigger: - platform: state entity_id: binary_sensor.updater diff --git a/source/_integrations/vacuum.mqtt.markdown b/source/_integrations/vacuum.mqtt.markdown index 7b57856f1f9..3d426cbf4cf 100644 --- a/source/_integrations/vacuum.mqtt.markdown +++ b/source/_integrations/vacuum.mqtt.markdown @@ -520,7 +520,7 @@ If params are provided service sends JSON as payload with such structure: Service trigger example: ```yaml -- alias: Push command based on sensor +- alias: "Push command based on sensor" trigger: - platform: state entity_id: sensor.sensor @@ -595,7 +595,7 @@ If params are provided service sends JSON as payload with such structure: Service trigger example: ```yaml -- alias: Push command based on sensor +- alias: "Push command based on sensor" trigger: - platform: state entity_id: sensor.sensor diff --git a/source/_integrations/vallox.markdown b/source/_integrations/vallox.markdown index 769c614349f..7bd28a9ff4a 100644 --- a/source/_integrations/vallox.markdown +++ b/source/_integrations/vallox.markdown @@ -60,7 +60,7 @@ input_select: icon: mdi:fan automation: - - alias: Set Ventilation Profile + - alias: "Set Ventilation Profile" trigger: platform: state entity_id: input_select.ventilation_profile @@ -78,7 +78,7 @@ In order to also update the input select in case some external event changes the ```yaml automation: - - alias: Update Vallox input_select + - alias: "Update Vallox input_select" description: Update input_select when external event changes the profile trigger: - entity_id: sensor.vallox_current_profile diff --git a/source/_integrations/velbus.markdown b/source/_integrations/velbus.markdown index 435b9bbcb53..18b16a52269 100644 --- a/source/_integrations/velbus.markdown +++ b/source/_integrations/velbus.markdown @@ -88,7 +88,7 @@ Example: ```yaml script: trash_memo: - alias: Trash memo text + alias: "Trash memo text" sequence: - data: address: 65 @@ -104,7 +104,7 @@ The actual linking can be realized by two automation rules. One rule to control ```yaml # Control light living from Velbus push_button_10 - id: 'Control_light_living_from_Velbus' - alias: Control light living using Velbus push_button_10 + alias: "Control light living using Velbus push_button_10" trigger: - entity_id: binary_sensor.push_button_10 platform: state @@ -116,7 +116,7 @@ The actual linking can be realized by two automation rules. One rule to control # Keep status LED push_button_10 in sync to status light living - id: 'Update LED of push_button_10' - alias: Update LED state of push_button_10 + alias: "Update LED state of push_button_10" trigger: - entity_id: light.living platform: state diff --git a/source/_integrations/verisure.markdown b/source/_integrations/verisure.markdown index 5bc51728233..97a90b73d59 100644 --- a/source/_integrations/verisure.markdown +++ b/source/_integrations/verisure.markdown @@ -116,7 +116,7 @@ The `changed_by` attribute enables one to be able to take different actions depe ```yaml automation: - - alias: Alarm status changed + - alias: "Alarm status changed" trigger: - platform: state entity_id: alarm_control_panel.alarm_1 diff --git a/source/_integrations/webostv.markdown b/source/_integrations/webostv.markdown index 952b713a14c..db986bd0b1f 100644 --- a/source/_integrations/webostv.markdown +++ b/source/_integrations/webostv.markdown @@ -229,7 +229,7 @@ The icon can be overridden for individual notifications by providing a path to a ```yaml automation: - - alias: Front door motion + - alias: "Front door motion" trigger: platform: state entity_id: binary_sensor.front_door_motion diff --git a/source/_integrations/workday.markdown b/source/_integrations/workday.markdown index 94905076f75..23667b82221 100644 --- a/source/_integrations/workday.markdown +++ b/source/_integrations/workday.markdown @@ -133,7 +133,7 @@ Example usage for automation: ```yaml automation: - alias: Turn on heater on workdays + alias: "Turn on heater on workdays" trigger: platform: time at: "08:00:00" diff --git a/source/_integrations/xiaomi_aqara.markdown b/source/_integrations/xiaomi_aqara.markdown index 69b362d96c0..1c1a7ad5d26 100644 --- a/source/_integrations/xiaomi_aqara.markdown +++ b/source/_integrations/xiaomi_aqara.markdown @@ -161,7 +161,7 @@ This example plays the sound of a dog barking when the button is held down and s *Note: The sound will stop playing automatically when it has ended.* ```yaml -- alias: Let a dog bark on long press +- alias: "Let a dog bark on long press" trigger: platform: event event_type: xiaomi_aqara.click @@ -175,7 +175,7 @@ This example plays the sound of a dog barking when the button is held down and s ringtone_id: 8 ringtone_vol: 8 -- alias: Stop barking immediately on single click +- alias: "Stop barking immediately on single click" trigger: platform: event event_type: xiaomi_aqara.click @@ -193,7 +193,7 @@ This example plays the sound of a dog barking when the button is held down and s This example toggles the living room lamp on a double click of the button. ```yaml -- alias: Double Click to toggle living room lamp +- alias: "Double Click to toggle living room lamp" trigger: platform: event event_type: xiaomi_aqara.click diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown index d1e01aba030..42d7268cff1 100644 --- a/source/_integrations/xiaomi_miio.markdown +++ b/source/_integrations/xiaomi_miio.markdown @@ -1290,7 +1290,7 @@ Inline array: ```yaml automation: - - alias: Test vacuum zone3 + - alias: "Test vacuum zone3" trigger: - event: start platform: homeassistant @@ -1310,7 +1310,7 @@ Array with inline zone: ```yaml automation: - - alias: Test vacuum zone3 + - alias: "Test vacuum zone3" trigger: - event: start platform: homeassistant @@ -1331,7 +1331,7 @@ Array mode: ```yaml automation: - - alias: Test vacuum zone3 + - alias: "Test vacuum zone3" trigger: - event: start platform: homeassistant @@ -1376,7 +1376,7 @@ Example of `xiaomi_miio.vacuum_clean_segment` use: Multiple segments: ```yaml automation: - - alias: Vacuum kitchen and living room + - alias: "Vacuum kitchen and living room" trigger: - event: start platform: homeassistant @@ -1392,7 +1392,7 @@ Single segment: ```yaml automation: - - alias: Vacuum kitchen + - alias: "Vacuum kitchen" trigger: - event: start platform: homeassistant diff --git a/source/_integrations/zwave.markdown b/source/_integrations/zwave.markdown index 92e23354b23..d8143107beb 100644 --- a/source/_integrations/zwave.markdown +++ b/source/_integrations/zwave.markdown @@ -82,7 +82,7 @@ The following examples will instruct a Remotec ZXT-120 to turn the attached devi ```yaml automation: - - alias: Turn on Heater at 8pm + - alias: "Turn on Heater at 8pm" trigger: - platform: time at: "20:00:00" @@ -101,7 +101,7 @@ Generally, in Home Assistant, you can use the `homeassistant.turn_off` service t ```yaml automation: - - alias: Turn off Heater at 9pm + - alias: "Turn off Heater at 9pm" trigger: - platform: time at: "21:00:00" diff --git a/source/_posts/2015-03-22-release-notes.markdown b/source/_posts/2015-03-22-release-notes.markdown index 92c8c530bb3..e27d1bf6e96 100644 --- a/source/_posts/2015-03-22-release-notes.markdown +++ b/source/_posts/2015-03-22-release-notes.markdown @@ -17,16 +17,16 @@ Andythigpen has contributed a script component. This allows users to create a se script: # Turns on the bedroom lights and then the living room lights 1 minute later wakeup: - alias: Wake Up + alias: "Wake Up" sequence: - - alias: Bedroom lights on + - alias: "Bedroom lights on" execute_service: light.turn_on service_data: entity_id: group.bedroom - delay: # supports seconds, milliseconds, minutes, hours, etc. minutes: 1 - - alias: Living room lights on + - alias: "Living room lights on" execute_service: light.turn_on service_data: entity_id: group.living_room diff --git a/source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown b/source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown index 3ad4c1c0218..0b9e8d24a78 100644 --- a/source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown +++ b/source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown @@ -77,7 +77,7 @@ sensor 2: unit_of_measurement: "" automation: - alias: Dryer complete + alias: "Dryer complete" platform: state state_entity_id: sensor.dryer_status @@ -88,7 +88,7 @@ automation: service_entity_id: script.dryer_complete automation 2: - alias: Dryer emptied + alias: "Dryer emptied" platform: state state_entity_id: sensor.dryer_status @@ -100,39 +100,39 @@ automation 2: script: dryer_complete: - alias: Dryer Complete Script + alias: "Dryer Complete Script" sequence: - - alias: Pushbullet Notification + - alias: "Pushbullet Notification" execute_service: notify.notify service_data: message: "The dryer has finished its cycle, please empty it!" - - alias: Living Room Lights Red + - alias: "Living Room Lights Red" execute_service: scene.turn_on service_data: entity_id: scene.red - delay: seconds: 1 - - alias: Living Room Lights Off + - alias: "Living Room Lights Off" execute_service: light.turn_off service_data: entity_id: group.living_room - delay: seconds: 1 - - alias: Living Room Lights Red + - alias: "Living Room Lights Red" execute_service: scene.turn_on service_data: entity_id: scene.red dryer_cleared: - alias: Dryer Cleared Script + alias: "Dryer Cleared Script" sequence: - - alias: Living Room Lights Off + - alias: "Living Room Lights Off" execute_service: light.turn_off service_data: entity_id: group.living_room - delay: seconds: 1 - - alias: Living Room Lights Normal + - alias: "Living Room Lights Normal" execute_service: scene.turn_on service_data: entity_id: scene.normal diff --git a/source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown b/source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown index 0aeb42fc900..be4a26303a4 100644 --- a/source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown +++ b/source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown @@ -52,7 +52,7 @@ This will tweet a message when an MQTT message is received that the smoke alarm ```yaml # Configuration.yaml entry automation: -- alias: Post a tweet when fire alarm is triggered +- alias: "Post a tweet when fire alarm is triggered" trigger: platform: mqtt mqtt_topic: home/alarm/fire diff --git a/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown b/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown index 57c1f6060ed..82d7a2b127b 100644 --- a/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown +++ b/source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown @@ -37,7 +37,7 @@ Automation has gotten a lot of love. It now supports conditions, multiple trigge ```yaml # Example of entry in configuration.yaml automation: - alias: Light on in the evening + alias: "Light on in the evening" trigger: - platform: sun event: sunset diff --git a/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown b/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown index 50a6bffed20..ea498f8b96e 100644 --- a/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown +++ b/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown @@ -60,7 +60,7 @@ With the basic tracking working - you can use automation to do things like open ```yaml automation: - - alias: 'Open gate' + - alias: "Open gate" trigger: - platform: state entity_id: device_tracker.beacon_car @@ -81,7 +81,7 @@ Or warn you if you leave your keys behind ```yaml automation: - - alias: 'Forgotten keys' + - alias: "Forgotten keys" trigger: platform: template value_template: '{{ states.device_tracker.greg_gregphone.state != states.device_tracker.beacon_keys.state}}' @@ -92,7 +92,7 @@ automation: service: script.turn_on entity_id: script.send_key_alert - - alias: 'Forgotten keys - cancel' + - alias: "Forgotten keys - cancel" trigger: platform: template value_template: '{{ states.device_tracker.greg_gregphone.state == states.device_tracker.beacon_keys.state }}' diff --git a/source/_posts/2016-08-03-laundry-automation-update.markdown b/source/_posts/2016-08-03-laundry-automation-update.markdown index e50f95f3c6e..b95666b12ed 100644 --- a/source/_posts/2016-08-03-laundry-automation-update.markdown +++ b/source/_posts/2016-08-03-laundry-automation-update.markdown @@ -73,7 +73,7 @@ sensor: unit_of_measurement: "" automation: - - alias: Washer complete + - alias: "Washer complete" trigger: platform: state entity_id: sensor.washer_status @@ -83,7 +83,7 @@ automation: service: script.turn_on entity_id: script.washer_complete - - alias: Washer emptied + - alias: "Washer emptied" trigger: platform: state entity_id: sensor.washer_status @@ -95,13 +95,13 @@ automation: script: washer_complete: - alias: Washer Complete + alias: "Washer Complete" sequence: - - alias: Join Notification + - alias: "Join Notification" service: notify.join data: message: "The washing machine has finished its cycle, please empty it!" - - alias: Living Room Lights Blue + - alias: "Living Room Lights Blue" service: scene.turn_on data: entity_id: scene.blue diff --git a/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown b/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown index 49be7e99aa7..30668843a00 100644 --- a/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown +++ b/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown @@ -50,7 +50,7 @@ rest_command: method: get automation: - alias: HTTP to MQTT keep alive + alias: "HTTP to MQTT keep alive" trigger: platform: time_pattern minutes: "/10" diff --git a/source/_posts/2017-06-17-release-47.markdown b/source/_posts/2017-06-17-release-47.markdown index dca11468bea..8976e6e8ee6 100644 --- a/source/_posts/2017-06-17-release-47.markdown +++ b/source/_posts/2017-06-17-release-47.markdown @@ -134,7 +134,7 @@ notify: - Z-Wave node and scene activated trigger events now use the full entity ID ([@armills] - [#7786]) ([zwave docs]) (breaking change) ```yaml automation: - - alias: Button 1 + - alias: "Button 1" trigger: platform: event event_type: zwave.scene_activated @@ -144,7 +144,7 @@ automation: ``` ```yaml automation: - - alias: Event 1 + - alias: "Event 1" trigger: platform: event event_type: zwave.node_event diff --git a/source/_posts/2017-08-26-release-0-52.markdown b/source/_posts/2017-08-26-release-0-52.markdown index 2ed7e471711..608bc72d12b 100644 --- a/source/_posts/2017-08-26-release-0-52.markdown +++ b/source/_posts/2017-08-26-release-0-52.markdown @@ -18,7 +18,7 @@ To use the scripts editor, create a new file in your config directory named `scr ```yaml # scripts.yaml turn_on_some_lights: - alias: Turn on the lights + alias: "Turn on the lights" sequence: - data: {} service: light.turn_on diff --git a/source/_posts/2018-01-14-release-61.markdown b/source/_posts/2018-01-14-release-61.markdown index 1c366775108..9f79b384bc1 100644 --- a/source/_posts/2018-01-14-release-61.markdown +++ b/source/_posts/2018-01-14-release-61.markdown @@ -136,7 +136,7 @@ Note however, that this feature was replaced by a new ignore_string config optio entity_config: switch.kitchen: expose: false - alias: roof lights + alias: "roof lights" name: nice lights type: light ``` diff --git a/source/_posts/2019-12-11-release-103.markdown b/source/_posts/2019-12-11-release-103.markdown index ea96afa1c48..b8af8e09a35 100644 --- a/source/_posts/2019-12-11-release-103.markdown +++ b/source/_posts/2019-12-11-release-103.markdown @@ -232,7 +232,7 @@ All services for use in Home Assistant are moved to their integration naming spa ```yaml - id: plant_unreachable - alias: plant unreachable + alias: "plant unreachable" trigger: - entity_id: sensor.plant_moisture for: 01:00:00 diff --git a/source/_posts/2020-02-11-android-16-17-release.markdown b/source/_posts/2020-02-11-android-16-17-release.markdown index c623d7ce03c..9173ee84f6e 100644 --- a/source/_posts/2020-02-11-android-16-17-release.markdown +++ b/source/_posts/2020-02-11-android-16-17-release.markdown @@ -21,7 +21,7 @@ Here's an example to check with a user if they want to close the garage door aft ```yaml automation: - - alias: Notify apps when the garage door opens + - alias: "Notify apps when the garage door opens" trigger: platform: state entity_id: cover.garage_door @@ -38,7 +38,7 @@ automation: - action: "close_garage" # The key you are sending for the event title: "Close Garage Door" # The button title - - alias: Close the garage when notification action is tapped + - alias: "Close the garage when notification action is tapped" trigger: platform: event event_type: mobile_app_notification_action diff --git a/source/_posts/2020-05-20-release-110.markdown b/source/_posts/2020-05-20-release-110.markdown index 52eac734a40..6a3409f5cce 100644 --- a/source/_posts/2020-05-20-release-110.markdown +++ b/source/_posts/2020-05-20-release-110.markdown @@ -203,7 +203,7 @@ for writing automations in YAML: ```yaml # Example automation -alias: Turn kitchen lights off when alarm is armed. +alias: "Turn kitchen lights off when alarm is armed." trigger: - platform: state entity_id: alarm_control_panel.home_alarm diff --git a/source/_posts/2020-07-01-release-112.markdown b/source/_posts/2020-07-01-release-112.markdown index 0b3511569a8..aab7b7d93b5 100644 --- a/source/_posts/2020-07-01-release-112.markdown +++ b/source/_posts/2020-07-01-release-112.markdown @@ -334,7 +334,7 @@ Experiencing issues introduced by this release? Please report them in our [issue ```yaml automation: - - alias: Test vacuum zone + - alias: "Test vacuum zone" trigger: - event: start platform: homeassistant @@ -354,7 +354,7 @@ to: ```yaml automation: - - alias: Test vacuum zone + - alias: "Test vacuum zone" trigger: - event: start platform: homeassistant diff --git a/source/_posts/2020-08-05-mobile-apps-new-features.markdown b/source/_posts/2020-08-05-mobile-apps-new-features.markdown index 299ee6ff657..6ace58687cc 100644 --- a/source/_posts/2020-08-05-mobile-apps-new-features.markdown +++ b/source/_posts/2020-08-05-mobile-apps-new-features.markdown @@ -38,7 +38,7 @@ In 1.10.0 we further enhanced our notifications to allow for many new options. U ```yaml automation: - - alias: Alarm triggered + - alias: "Alarm triggered" trigger: platform: state entity_id: alarm_control_panel.home diff --git a/source/_posts/2020-08-12-release-114.markdown b/source/_posts/2020-08-12-release-114.markdown index 4e50a760654..c974770e757 100644 --- a/source/_posts/2020-08-12-release-114.markdown +++ b/source/_posts/2020-08-12-release-114.markdown @@ -106,7 +106,7 @@ multiple time values. ```yaml automation: - - alias: Example with multiple time values in a single time trigger + - alias: "Example with multiple time values in a single time trigger" trigger: - platform: time at: diff --git a/source/_posts/2020-09-15-home-assistant-tags.markdown b/source/_posts/2020-09-15-home-assistant-tags.markdown index e69069d4f95..5f35ef710f5 100644 --- a/source/_posts/2020-09-15-home-assistant-tags.markdown +++ b/source/_posts/2020-09-15-home-assistant-tags.markdown @@ -70,7 +70,7 @@ All previous things put the pieces in place for us to be able to build our own j # Note, this is using new automation features introduced in Home Assistant 0.115 automation: - id: handle_tag_scan - alias: Handle Tag Scan + alias: "Handle Tag Scan" mode: single # Hide warnings when triggered while in delay. max_exceeded: silent diff --git a/source/_posts/2020-10-28-release-117.markdown b/source/_posts/2020-10-28-release-117.markdown index 0eb7ee9aaec..4ba29998eb3 100644 --- a/source/_posts/2020-10-28-release-117.markdown +++ b/source/_posts/2020-10-28-release-117.markdown @@ -207,7 +207,7 @@ After that, you can do things like this: ```yaml script: my_script: - alias: Example + alias: "Example" description: Example script with native lists in templates variables: entities: diff --git a/source/_posts/2020-11-18-release-118.markdown b/source/_posts/2020-11-18-release-118.markdown index d284c3d806d..5f016ca6e06 100644 --- a/source/_posts/2020-11-18-release-118.markdown +++ b/source/_posts/2020-11-18-release-118.markdown @@ -146,7 +146,7 @@ even if you made a list. ```yaml script: my_script: - alias: Example + alias: "Example" description: Example script with native lists in templates variables: entities: