Collection of Markdown/YAML cleanups (home-assistant#16817)

advait · Mar 3, 2021 · fad2a45 · fad2a45
1 parent 38d2297
commit fad2a45
Show file tree

Hide file tree

Showing 19 changed files with 446 additions and 396 deletions.
diff --git a/source/_docs/authentication/multi-factor-auth.markdown b/source/_docs/authentication/multi-factor-auth.markdown
@@ -94,7 +94,7 @@ message:
 homeassistant:
   auth_mfa_modules:
     - type: totp
-      name: Authenticator app
+      name: "Authenticator app"
     - type: notify
       message: "I almost forget, to get into my clubhouse, you need to say {}"
 ```

diff --git a/source/_docs/automation/action.markdown b/source/_docs/automation/action.markdown
@@ -11,23 +11,24 @@ You can also call the service to activate [a scene](/integrations/scene/) which
 automation:
   # Change the light in the kitchen and living room to 150 brightness and color red.
   trigger:
-    platform: sun
-    event: sunset
+    - platform: sun
+      event: sunset
   action:
-    service: light.turn_on
-    data:
-      brightness: 150
-      rgb_color: [255, 0, 0]
-      entity_id:
-        - light.kitchen
-        - light.living_room
+    - service: light.turn_on
+      target:
+        entity_id:
+          - light.kitchen
+          - light.living_room
+      data:
+        brightness: 150
+        rgb_color: [255, 0, 0]
 
 automation 2:
   # Notify me on my mobile phone of an event
   trigger:
-    platform: sun
-    event: sunset
-    offset: -00:30
+    - platform: sun
+      event: sunset
+      offset: -00:30
   variables:
     notification_service: notify.paulus_iphone
   action:
@@ -47,9 +48,9 @@ Conditions can also be part of an action. You can combine multiple service calls
 automation:
 - alias: "Office at evening"
   trigger:
-    platform: state
-    entity_id: sensor.office_occupancy
-    to: "on" 
+    - platform: state
+      entity_id: sensor.office_occupancy
+      to: "on" 
   action:
     - service: notify.notify
       data:

diff --git a/source/_docs/automation/basics.markdown b/source/_docs/automation/basics.markdown
@@ -15,7 +15,7 @@ We can break up this automation into the following three parts:
 (action)     Turn the lights on in the living room
 ```
 
-The first part is the [trigger](/docs/automation/trigger/) of the automation rule. Triggers describe events that should trigger the automation rule. In this case, it is a person arriving home, which can be observed in Home Assistant by observing the state of Paulus changing from 'not_home' to 'home'.
+The first part is the [trigger](/docs/automation/trigger/) of the automation rule. Triggers describe events that should trigger the automation rule. In this case, it is a person arriving home, which can be observed in Home Assistant by observing the state of Paulus changing from `not_home` to `home`.
 
 The second part is the [condition](/docs/automation/condition/). Conditions are optional tests that can limit an automation rule to only work in your specific use cases. A condition will test against the current state of the system. This includes the current time, devices, people and other things like the sun. In this case, we only want to act when the sun has set.
 

diff --git a/source/_docs/automation/condition.markdown b/source/_docs/automation/condition.markdown
@@ -15,19 +15,19 @@ Example of using condition:
 automation:
   - alias: "Enciende Despacho"
     trigger:
-      platform: state
-      entity_id: sensor.mini_despacho
-      to: "on"
+      - platform: state
+        entity_id: sensor.mini_despacho
+        to: "on"
     condition:
-      condition: or
-      conditions:
-        - condition: numeric_state
-          entity_id: sun.sun
-          attribute: elevation
-          below: 4
-        - condition: numeric_state
-          entity_id: sensor.sensorluz_7_0
-          below: 10
+      - condition: or
+        conditions:
+          - condition: numeric_state
+            entity_id: sun.sun
+            attribute: elevation
+            below: 4
+          - condition: numeric_state
+            entity_id: sensor.sensorluz_7_0
+            below: 10
     action:
       - service: scene.turn_on
         target:
@@ -44,9 +44,9 @@ The `condition` option of an automation, also accepts a single condition templat
 automation:
   - alias: "Enciende Despacho"
     trigger:
-      platform: state
-      entity_id: sensor.mini_despacho
-      to: "on"
+      - platform: state
+        entity_id: sensor.mini_despacho
+        to: "on"
     condition: "{{ state_attr('sun.sun', 'elevation') < 4 }}"
     action:
       - service: scene.turn_on

diff --git a/source/_docs/automation/templating.markdown b/source/_docs/automation/templating.markdown
@@ -127,19 +127,19 @@ The following tables show the available trigger data per platform.
 # Example configuration.yaml entries
 automation:
   trigger:
-    platform: state
-    entity_id: device_tracker.paulus
+    - platform: state
+      entity_id: device_tracker.paulus
   action:
-    service: notify.notify
-    data:
-      message: >
-        Paulus just changed from {{ trigger.from_state.state }}
-        to {{ trigger.to_state.state }}
+    - service: notify.notify
+      data:
+        message: >
+          Paulus just changed from {{ trigger.from_state.state }}
+          to {{ trigger.to_state.state }}
 
 automation 2:
   trigger:
-    platform: mqtt
-    topic: /notify/+
+    - platform: mqtt
+      topic: "/notify/+"
   action:
     service: >
       notify.{{ trigger.topic.split('/')[-1] }}