diff --git a/source/_docs/automation/yaml.markdown b/source/_docs/automation/yaml.markdown
index 1929edab832..b21bcea57c4 100644
--- a/source/_docs/automation/yaml.markdown
+++ b/source/_docs/automation/yaml.markdown
@@ -117,6 +117,8 @@ automation:
If you want to migrate your manual automations to use the editor, you'll have to copy them to `automations.yaml`. Make sure that `automations.yaml` remains a list! For each automation that you copy over, you'll have to add an `id`. This can be any string as long as it's unique.
+{% raw %}
+
```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.
@@ -131,11 +133,13 @@ If you want to migrate your manual automations to use the editor, you'll have to
entity_id: sensor.temperature
above: 17
below: 25
- value_template: '{% raw %}{{ float(state.state) + 2 }}{% endraw %}'
+ value_template: "{{ float(state.state) + 2 }}"
action:
- service: light.turn_on
```
+{% endraw %}
+
### Deleting Automations
When automations remain visible in the Home Assistant Dashboard, even after having deleted in the YAML file, you have to delete them in the UI.
diff --git a/source/_integrations/beewi_smartclim.markdown b/source/_integrations/beewi_smartclim.markdown
index 8bf844bdb3a..62b357cf17c 100644
--- a/source/_integrations/beewi_smartclim.markdown
+++ b/source/_integrations/beewi_smartclim.markdown
@@ -51,7 +51,7 @@ To use your Mi Temperature and Humidity sensor in your installation, add the fol
# Example configuration.yaml entry
sensor:
- platform: beewi_smartclim
- mac: 'xx:xx:xx:xx:xx:xx'
+ mac: "xx:xx:xx:xx:xx:xx"
```
{% configuration %}
@@ -73,6 +73,6 @@ A full configuration example could look like the one below:
# Example configuration.yaml entry
sensor:
- platform: beewi_smartclim
- mac: 'xx:xx:xx:xx:xx:xx'
+ mac: "xx:xx:xx:xx:xx:xx"
name: Garden
```
diff --git a/source/_integrations/binary_sensor.mqtt.markdown b/source/_integrations/binary_sensor.mqtt.markdown
index 7e12e59a19f..428f376dfaf 100644
--- a/source/_integrations/binary_sensor.mqtt.markdown
+++ b/source/_integrations/binary_sensor.mqtt.markdown
@@ -195,7 +195,7 @@ binary_sensor:
payload_not_available: "offline"
qos: 0
device_class: opening
- value_template: '{{ value_json.state }}'
+ value_template: "{{ value_json.state }}"
```
{% endraw %}
diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown
index 9993a904cd3..ff5b3509524 100644
--- a/source/_integrations/cast.markdown
+++ b/source/_integrations/cast.markdown
@@ -117,8 +117,8 @@ You can play MP3 streams like net radios, FLAC files or videos from your local n
service: media_player.play_media
data:
entity_id: media_player.chromecast
- media_content_type: 'video'
- media_content_id: 'http://192.168.0.100/movies/sample-video.mkv'
+ media_content_type: "video"
+ media_content_id: "http://192.168.0.100/movies/sample-video.mkv"
```
```yaml
@@ -126,8 +126,8 @@ data:
service: media_player.play_media
data:
entity_id: media_player.chromecast
- media_content_type: 'image/jpeg'
- media_content_id: 'http://via.placeholder.com/1024x600.jpg/0B6B94/FFFFFF/?text=Hello,%20Home%20Assistant!'
+ media_content_type: "image/jpeg"
+ media_content_id: "http://via.placeholder.com/1024x600.jpg/0B6B94/FFFFFF/?text=Hello,%20Home%20Assistant!"
```
Extra media metadata (for example title, subtitle, artist or album name) can be passed into the service and that will be shown on the Chromecast display.
@@ -138,15 +138,15 @@ For the possible metadata types and values check [Google cast documentation > Me
service: media_player.play_media
data:
entity_id: media_player.chromecast
- media_content_type: 'video/mp4'
- media_content_id: 'http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4'
+ media_content_type: "video/mp4"
+ media_content_id: "http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4"
extra:
metadata:
metadataType: 1
- title: 'Big Buck Bunny'
- subtitle: 'By Blender Foundation, Licensed under the Creative Commons Attribution license'
+ title: "Big Buck Bunny"
+ subtitle: "By Blender Foundation, Licensed under the Creative Commons Attribution license"
images:
- - url: 'https://peach.blender.org/wp-content/uploads/watchtrailer.gif'
+ - url: "https://peach.blender.org/wp-content/uploads/watchtrailer.gif"
```
```yaml
@@ -154,15 +154,15 @@ data:
service: media_player.play_media
data:
entity_id: media_player.chromecast
- media_content_type: 'audio/mp3'
- media_content_id: 'http://stream.tilos.hu:8000/tilos'
+ media_content_type: "audio/mp3"
+ media_content_id: "http://stream.tilos.hu:8000/tilos"
extra:
metadata:
metadataType: 3
- title: 'Radio TILOS'
- artist: 'LIVE'
+ title: "Radio TILOS"
+ artist: "LIVE"
images:
- - url: 'https://tilos.hu/images/kockalogo.png'
+ - url: "https://tilos.hu/images/kockalogo.png"
```
## Advanced use
diff --git a/source/_integrations/clicksend.markdown b/source/_integrations/clicksend.markdown
index d5b6e09f501..ebc067930c0 100644
--- a/source/_integrations/clicksend.markdown
+++ b/source/_integrations/clicksend.markdown
@@ -57,7 +57,7 @@ sender:
description: The name or number of the sender. (Limited to 11 characters.)
required: false
type: string
- default: 'hass'
+ default: "hass"
{% endconfiguration %}
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
diff --git a/source/_integrations/climate.markdown b/source/_integrations/climate.markdown
index 338233d60b3..324390b81ca 100644
--- a/source/_integrations/climate.markdown
+++ b/source/_integrations/climate.markdown
@@ -68,7 +68,7 @@ automation:
- service: climate.set_preset_mode
data:
entity_id: climate.kitchen
- preset_mode: 'eco'
+ preset_mode: "eco"
```
### Service `climate.set_temperature`
@@ -157,7 +157,7 @@ automation:
- service: climate.set_fan_mode
data:
entity_id: climate.kitchen
- fan_mode: 'On Low'
+ fan_mode: "On Low"
```
### Service `climate.set_hvac_mode`
diff --git a/source/_integrations/color_extractor.markdown b/source/_integrations/color_extractor.markdown
index c4998926dd5..e35112f0064 100644
--- a/source/_integrations/color_extractor.markdown
+++ b/source/_integrations/color_extractor.markdown
@@ -68,7 +68,7 @@ Example usage in an automation, taking the album art present on a Chromecast and
action:
- service: color_extractor.turn_on
data_template:
- color_extract_url: '{{ states.media_player.chromecast.attributes.entity_picture }}'
+ color_extract_url: "{{ states.media_player.chromecast.attributes.entity_picture }}"
entity_id: light.shelf_leds
```
@@ -85,7 +85,7 @@ With a nicer transition period of 5 seconds and setting brightness to 100% each
action:
- service: color_extractor.turn_on
data_template:
- color_extract_url: '{{ states.media_player.chromecast.attributes.entity_picture }}'
+ color_extract_url: "{{ states.media_player.chromecast.attributes.entity_picture }}"
entity_id: light.shelf_leds
brightness_pct: 100
transition: 5
diff --git a/source/_integrations/command_line.markdown b/source/_integrations/command_line.markdown
index 2d58016c048..78d177f5980 100644
--- a/source/_integrations/command_line.markdown
+++ b/source/_integrations/command_line.markdown
@@ -19,7 +19,7 @@ To use your Command binary sensor in your installation, add the following to you
# Example configuration.yaml entry
binary_sensor:
- platform: command_line
- command: 'cat /proc/sys/net/ipv4/ip_forward'
+ command: "cat /proc/sys/net/ipv4/ip_forward"
```
@@ -81,7 +81,7 @@ Check the state of an [SickRage](https://github.com/sickragetv/sickrage) instanc
binary_sensor:
- platform: command_line
command: 'netstat -na | find "33322" | find /c "LISTENING" > nul && (echo "Running") || (echo "Not running")'
- name: 'sickragerunning'
+ name: "sickragerunning"
device_class: moving
payload_on: "Running"
payload_off: "Not running"
@@ -95,7 +95,7 @@ Check if [RasPlex](https://github.com/RasPlex/RasPlex) is `online`.
binary_sensor:
- platform: command_line
command: 'ping -c 1 rasplex.local | grep "1 received" | wc -l'
- name: 'is_rasplex_online'
+ name: "is_rasplex_online"
device_class: connectivity
payload_on: 1
payload_off: 0
@@ -133,8 +133,8 @@ A binary command line sensor can check this:
binary_sensor:
- platform: command_line
command: '/bin/systemctl is-active home-assistant@rock64.service'
- payload_on: 'active'
- payload_off: 'inactive'
+ payload_on: "active"
+ payload_off: "inactive"
```
## Services
diff --git a/source/_integrations/cover.mqtt.markdown b/source/_integrations/cover.mqtt.markdown
index 40ffc1f021f..4b350bf1e2b 100644
--- a/source/_integrations/cover.mqtt.markdown
+++ b/source/_integrations/cover.mqtt.markdown
@@ -288,7 +288,7 @@ cover:
payload_available: "online"
payload_not_available: "offline"
optimistic: false
- value_template: '{{ value.x }}'
+ value_template: "{{ value.x }}"
```
{% endraw %}
@@ -319,7 +319,7 @@ cover:
payload_available: "online"
payload_not_available: "offline"
optimistic: false
- value_template: '{{ value.x }}'
+ value_template: "{{ value.x }}"
```
{% endraw %}
@@ -351,9 +351,9 @@ cover:
payload_available: "online"
payload_not_available: "offline"
optimistic: false
- value_template: '{{ value.x }}'
- tilt_command_topic: 'home-assistant/cover/tilt'
- tilt_status_topic: 'home-assistant/cover/tilt-state'
+ value_template: "{{ value.x }}"
+ tilt_command_topic: "home-assistant/cover/tilt"
+ tilt_status_topic: "home-assistant/cover/tilt-state"
tilt_status_template: '{{ value_json["PWM"]["PWM1"] }}'
tilt_min: 0
tilt_max: 180
diff --git a/source/_integrations/cover.template.markdown b/source/_integrations/cover.template.markdown
index 215db5e5844..6817460ba63 100644
--- a/source/_integrations/cover.template.markdown
+++ b/source/_integrations/cover.template.markdown
@@ -199,15 +199,15 @@ cover:
open_cover:
service: script.cover_group
data:
- modus: 'open'
+ modus: "open"
close_cover:
service: script.cover_group
data:
- modus: 'close'
+ modus: "close"
stop_cover:
service: script.cover_group
data:
- modus: 'stop'
+ modus: "stop"
set_cover_position:
service: script.cover_group_position
data:
@@ -255,7 +255,7 @@ automation:
trigger:
- platform: sun
event: sunset
- offset: '+00:30:00'
+ offset: "+00:30:00"
action:
- service: cover.set_cover_position
data:
@@ -280,15 +280,15 @@ cover:
open_cover:
service: script.cover_group
data:
- modus: 'open'
+ modus: "open"
close_cover:
service: script.cover_group
data:
- modus: 'close'
+ modus: "close"
stop_cover:
service: script.cover_group
data:
- modus: 'stop'
+ modus: "stop"
value_template: "{{is_state('sensor.cover_group', 'open')}}"
icon_template: >-
{% if is_state('sensor.cover_group', 'open') %}
@@ -315,15 +315,15 @@ cover:
open_cover:
service: script.cover_group
data:
- modus: 'open'
+ modus: "open"
close_cover:
service: script.cover_group
data:
- modus: 'close'
+ modus: "close"
stop_cover:
service: script.cover_group
data:
- modus: 'stop'
+ modus: "stop"
value_template: "{{is_state('sensor.cover_group', 'open')}}"
icon_template: >-
{% if is_state('sensor.cover_group', 'open') %}
diff --git a/source/_integrations/deconz.markdown b/source/_integrations/deconz.markdown
index 73cec5f60ad..67892c607af 100644
--- a/source/_integrations/deconz.markdown
+++ b/source/_integrations/deconz.markdown
@@ -280,7 +280,7 @@ automation:
trigger:
- platform: state
entity_id: binary_sensor.doorbell_motion
- to: 'on'
+ to: "on"
action:
- service: deconz.configure
data:
diff --git a/source/_integrations/delijn.markdown b/source/_integrations/delijn.markdown
index 29776604907..80e9670a635 100644
--- a/source/_integrations/delijn.markdown
+++ b/source/_integrations/delijn.markdown
@@ -27,7 +27,7 @@ To enable this sensor, add the following lines to your `configuration.yaml` file
# Example configuration.yaml entry
sensor:
- platform: delijn
- api_key: 'API_SUBSCRIPTION_KEY'
+ api_key: "API_SUBSCRIPTION_KEY"
next_departure:
- stop_id: 'STOP_ID'
```
@@ -64,7 +64,7 @@ The example below shows a full configuration with two sensors, only the abcdefg
sensor:
# De Lijn public transport
- platform: delijn
- api_key: 'abcdefg'
+ api_key: "abcdefg"
next_departure:
- stop_id: '200018'
- stop_id: '201169'
diff --git a/source/_integrations/deutsche_bahn.markdown b/source/_integrations/deutsche_bahn.markdown
index 6ecb09bfbcf..6944f4011df 100644
--- a/source/_integrations/deutsche_bahn.markdown
+++ b/source/_integrations/deutsche_bahn.markdown
@@ -42,14 +42,18 @@ only_direct:
This sensor stores a lot of attributes which can be accessed by other sensors, e.g., a [template sensor](/integrations/template).
+{% raw %}
+
```yaml
# Example configuration.yaml entry
sensor:
platform: template
sensors:
next_departure:
- value_template: '{% raw %}{{ state_attr('sensor.munich_to_ulm', 'next') }}{% endraw %}'
- friendly_name: 'Next departure'
+ value_template: "{{ state_attr('sensor.munich_to_ulm', 'next') }}"
+ friendly_name: "Next departure"
```
+{% endraw %}
+
The data is coming from the [bahn.de](https://www.bahn.de/p/view/index.shtml) website.
diff --git a/source/_integrations/device_tracker.mqtt.markdown b/source/_integrations/device_tracker.mqtt.markdown
index 678a65cd092..f30a81bcc6a 100644
--- a/source/_integrations/device_tracker.mqtt.markdown
+++ b/source/_integrations/device_tracker.mqtt.markdown
@@ -20,8 +20,8 @@ To use this device tracker in your installation, add the following to your `conf
device_tracker:
- platform: mqtt
devices:
- paulus_oneplus: 'location/paulus'
- annetherese_n4: 'location/annetherese'
+ paulus_oneplus: "location/paulus"
+ annetherese_n4: "location/annetherese"
```
{% configuration %}
@@ -37,12 +37,12 @@ payload_home:
description: The payload value that represents the 'home' state for the device.
required: false
type: string
- default: 'home'
+ default: "home"
payload_not_home:
description: The payload value that represents the 'not_home' state for the device.
required: false
type: string
- default: 'not_home'
+ default: "not_home"
source_type:
description: Attribute of a device tracker that affects state when being used to track a [person](/integrations/person/). Valid options are `gps`, `router`, `bluetooth`, or `bluetooth_le`.
required: false
@@ -56,11 +56,11 @@ source_type:
device_tracker:
- platform: mqtt
devices:
- paulus_oneplus: 'location/paulus'
- annetherese_n4: 'location/annetherese'
+ paulus_oneplus: "location/paulus"
+ annetherese_n4: "location/annetherese"
qos: 1
- payload_home: 'present'
- payload_not_home: 'not present'
+ payload_home: "present"
+ payload_not_home: "not present"
source_type: bluetooth
```
diff --git a/source/_integrations/dexcom.markdown b/source/_integrations/dexcom.markdown
index 6771e3db619..0c82d9375ae 100644
--- a/source/_integrations/dexcom.markdown
+++ b/source/_integrations/dexcom.markdown
@@ -49,8 +49,8 @@ If you have a sensor session running, and once you have enabled the Dexcom integ
entity_id: sensor.dexcom_YOUR_USERNAME_glucose_value
platform: numeric_state
condition: time
- after: '22:00:00'
- before: '06:00:00'
+ after: "22:00:00"
+ before: "06:00:00"
action:
- service: light.turn_on
data:
diff --git a/source/_integrations/dovado.markdown b/source/_integrations/dovado.markdown
index 4a9f22ba37b..8a597aae16b 100644
--- a/source/_integrations/dovado.markdown
+++ b/source/_integrations/dovado.markdown
@@ -73,8 +73,8 @@ automation:
action:
service: notify.dovado
data:
- message: 'The sun has set'
- target: '+14151234567'
+ message: "The sun has set"
+ target: "+14151234567"
```
## Sensor
diff --git a/source/_integrations/dweet.markdown b/source/_integrations/dweet.markdown
index ee755d4ab81..8ef019d5ddc 100644
--- a/source/_integrations/dweet.markdown
+++ b/source/_integrations/dweet.markdown
@@ -66,7 +66,7 @@ To use Dweet.io sensors in your installation, add the following to your `configu
sensor:
- platform: dweet
device: THING_NAME
- value_template: '{{ value_json.VARIABLE }}'
+ value_template: "{{ value_json.VARIABLE }}"
```
{% endraw %}
@@ -103,7 +103,7 @@ sensor:
- platform: dweet
name: Temperature
device: THING_NAME
- value_template: '{{ value_json.VARIABLE }}'
+ value_template: "{{ value_json.VARIABLE }}"
unit_of_measurement: "°C"
```
diff --git a/source/_integrations/dynalite.markdown b/source/_integrations/dynalite.markdown
index e3ba2739b04..159661f381c 100755
--- a/source/_integrations/dynalite.markdown
+++ b/source/_integrations/dynalite.markdown
@@ -284,9 +284,9 @@ dynalite:
template: time_cover
preset:
'1':
- name: 'On'
+ name: "On"
'4':
- name: 'Off'
+ name: "Off"
template:
room:
room_on: 1
diff --git a/source/_integrations/ebusd.markdown b/source/_integrations/ebusd.markdown
index 5045f451091..a974c48a005 100644
--- a/source/_integrations/ebusd.markdown
+++ b/source/_integrations/ebusd.markdown
@@ -18,7 +18,7 @@ Enable the sensor by adding the following to your `configuration.yaml` file:
# Example configuration.yaml entry
ebusd:
host: 127.0.0.1
- circuit: '700'
+ circuit: "700"
```
{% configuration %}
diff --git a/source/_integrations/ecovacs.markdown b/source/_integrations/ecovacs.markdown
index 9699d5c664d..5cbe6bfc275 100644
--- a/source/_integrations/ecovacs.markdown
+++ b/source/_integrations/ecovacs.markdown
@@ -90,7 +90,7 @@ sensor:
sensors:
vacuum_filter:
friendly_name: "Vacuum Filter Remaining Lifespan"
- unit_of_measurement: '%'
+ unit_of_measurement: "%"
value_template: "{{ state_attr('vacuum.my_vacuum_id', 'component_filter') }}"
```
diff --git a/source/_integrations/edimax.markdown b/source/_integrations/edimax.markdown
index 0871a5c912a..02c04b885c4 100644
--- a/source/_integrations/edimax.markdown
+++ b/source/_integrations/edimax.markdown
@@ -52,12 +52,12 @@ Starting with [version 2 of the firmware](https://www.edimax.com/edimax/download
sensors:
edimax_current_power:
friendly_name: Edimax Current power consumption
- unit_of_measurement: 'W'
+ unit_of_measurement: "W"
value_template: "{{ state_attr('switch.edimax_smart_plug', 'current_power_w') | replace('None', 0) }}"
edimax_total_power:
friendly_name: Edimax Accumulated daily power consumption
- unit_of_measurement: 'kWh'
+ unit_of_measurement: "kWh"
value_template: "{{ state_attr('switch.edimax_smart_plug', 'today_energy_kwh') | replace('None', 0) }}"
```
diff --git a/source/_integrations/egardia.markdown b/source/_integrations/egardia.markdown
index 2a924b0b312..e998443a23c 100644
--- a/source/_integrations/egardia.markdown
+++ b/source/_integrations/egardia.markdown
@@ -45,7 +45,7 @@ version:
description: The version of the Egardia system. `GATE-01`, `GATE-02` and `GATE-03` are currently supported.
required: false
type: string
- default: 'GATE-01'
+ default: "GATE-01"
port:
description: The port of the alarm panel.
required: false
diff --git a/source/_integrations/envisalink.markdown b/source/_integrations/envisalink.markdown
index b5ec83cfe76..a0ce1a4745c 100644
--- a/source/_integrations/envisalink.markdown
+++ b/source/_integrations/envisalink.markdown
@@ -33,7 +33,7 @@ envisalink:
panel_type: HONEYWELL or DSC
user_name: YOUR_USERNAME
password: YOUR_PASSWORD
- code: '1234'
+ code: "1234"
port: 4025
evl_version: 3
keepalive_interval: 60
@@ -42,14 +42,14 @@ envisalink:
panic_type: Police
zones:
11:
- name: 'Back Door'
- type: 'opening'
+ name: "Back Door"
+ type: "opening"
21:
- name: 'First Floor Motion'
- type: 'motion'
+ name: "First Floor Motion"
+ type: "motion"
partitions:
1:
- name: 'Home Alarm'
+ name: "Home Alarm"
```
{% configuration %}
diff --git a/source/_integrations/epson.markdown b/source/_integrations/epson.markdown
index fea9839eb27..875dcce5576 100644
--- a/source/_integrations/epson.markdown
+++ b/source/_integrations/epson.markdown
@@ -40,7 +40,7 @@ name:
description: The name of the device used in the frontend.
required: false
type: string
- default: 'EPSON Projector'
+ default: "EPSON Projector"
{% endconfiguration %}
### Supported features
diff --git a/source/_integrations/eq3btsmart.markdown b/source/_integrations/eq3btsmart.markdown
index c35923f11a9..8f86ec3fbd2 100644
--- a/source/_integrations/eq3btsmart.markdown
+++ b/source/_integrations/eq3btsmart.markdown
@@ -42,7 +42,7 @@ climate:
- platform: eq3btsmart
devices:
room1:
- mac: '00:11:22:33:44:55'
+ mac: "00:11:22:33:44:55"
```
{% configuration %}
diff --git a/source/_integrations/etherscan.markdown b/source/_integrations/etherscan.markdown
index 206fba68dd9..964385d31dd 100644
--- a/source/_integrations/etherscan.markdown
+++ b/source/_integrations/etherscan.markdown
@@ -17,7 +17,7 @@ To add the Etherscan sensor to your installation, specify an Ethereum address to
# Example configuration.yaml entry
sensor:
- platform: etherscan
- address: '0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359'
+ address: "0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359"
- platform: etherscan
address: "0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359"
token: OMG
diff --git a/source/_integrations/ezviz.markdown b/source/_integrations/ezviz.markdown
index a7f29fbbc1e..4c51daab4cb 100644
--- a/source/_integrations/ezviz.markdown
+++ b/source/_integrations/ezviz.markdown
@@ -74,7 +74,7 @@ camera_view: live
elements:
- icon: 'mdi:arrow-up'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
bottom: 50px
right: 25px
tap_action:
@@ -86,7 +86,7 @@ elements:
type: icon
- icon: 'mdi:arrow-down'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
bottom: 0px
right: 25px
tap_action:
@@ -98,7 +98,7 @@ elements:
type: icon
- icon: 'mdi:arrow-left'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
bottom: 25px
right: 50px
tap_action:
@@ -110,7 +110,7 @@ elements:
type: icon
- icon: 'mdi:arrow-right'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
bottom: 25px
right: 0px
tap_action:
@@ -122,7 +122,7 @@ elements:
type: icon
- icon: 'mdi:run-fast'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
top: 25px
right: 25px
tap_action:
@@ -134,7 +134,7 @@ elements:
type: icon
- icon: 'mdi:run'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
top: 25px
right: 0px
tap_action:
@@ -146,7 +146,7 @@ elements:
type: icon
- icon: 'mdi:eye'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 25px
top: 50px
tap_action:
@@ -158,7 +158,7 @@ elements:
type: icon
- icon: 'mdi:eye-off'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 0px
top: 50px
tap_action:
@@ -170,7 +170,7 @@ elements:
type: icon
- icon: 'mdi:volume-high'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 25px
top: 75px
tap_action:
@@ -182,7 +182,7 @@ elements:
type: icon
- icon: 'mdi:volume-off'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 0px
top: 75px
tap_action:
@@ -194,7 +194,7 @@ elements:
type: icon
- icon: 'mdi:led-on'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 25px
top: 100px
tap_action:
@@ -206,7 +206,7 @@ elements:
type: icon
- icon: 'mdi:led-off'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 0px
top: 100px
tap_action:
@@ -218,7 +218,7 @@ elements:
type: icon
- icon: 'mdi:brightness-4'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 25px
top: 100px
tap_action:
@@ -230,7 +230,7 @@ elements:
type: icon
- icon: 'mdi:brightness-5'
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 0px
top: 100px
tap_action:
diff --git a/source/_integrations/facebook.markdown b/source/_integrations/facebook.markdown
index 36533b944ad..17dbaca1bbb 100644
--- a/source/_integrations/facebook.markdown
+++ b/source/_integrations/facebook.markdown
@@ -47,7 +47,7 @@ automation:
action:
service: notify.facebook
data:
- message: 'Good Evening'
+ message: "Good Evening"
target:
- '+919413017584'
- '+919784516314'
diff --git a/source/_integrations/facebox.markdown b/source/_integrations/facebox.markdown
index 8ebe2ee0af5..c4ea7fabee6 100644
--- a/source/_integrations/facebox.markdown
+++ b/source/_integrations/facebox.markdown
@@ -104,7 +104,7 @@ Use the `image_processing.detect_face` events to trigger automations, and breako
platform: event
event_type: image_processing.detect_face
event_data:
- name: 'Ringo_Starr'
+ name: "Ringo_Starr"
action:
service: notify.platform
data:
@@ -184,7 +184,7 @@ you can create an automation to receive notifications on Facebox errors:
action:
- service: notify.pushbullet
data_template:
- message: '{{ trigger.event.data.message }}'
+ message: "{{ trigger.event.data.message }}"
title: Facebox error
```
diff --git a/source/_integrations/familyhub.markdown b/source/_integrations/familyhub.markdown
index c3519fb3995..fba49362ef9 100644
--- a/source/_integrations/familyhub.markdown
+++ b/source/_integrations/familyhub.markdown
@@ -18,7 +18,7 @@ To enable your Family Hub camera in your installation, add the following to your
# Example configuration.yaml entry
camera:
- platform: familyhub
- ip_address: 'IP_ADDRESS'
+ ip_address: "IP_ADDRESS"
```
{% configuration %}
diff --git a/source/_integrations/file.markdown b/source/_integrations/file.markdown
index 4ed2f45425f..353866358b4 100644
--- a/source/_integrations/file.markdown
+++ b/source/_integrations/file.markdown
@@ -106,5 +106,5 @@ sensor:
name: Temperature
file_path: /home/user/.homeassistant/sensor.json
value_template: {% raw %}'{{ value_json.temperature }}'{% endraw %}
- unit_of_measurement: '°C'
+ unit_of_measurement: "°C"
```
diff --git a/source/_integrations/fireservicerota.markdown b/source/_integrations/fireservicerota.markdown
index 7cf918c4df9..9768ab4e2da 100644
--- a/source/_integrations/fireservicerota.markdown
+++ b/source/_integrations/fireservicerota.markdown
@@ -142,7 +142,7 @@ automation:
entity_id: media_player.nest_hub_bedroom
media_content_id: >
{{ state_attr('sensor.incidents','message_to_speech_url') }}
- media_content_type: 'audio/mp4'
+ media_content_type: "audio/mp4"
- alias: 'Send response acknowledgement when a button is pressed'
trigger:
diff --git a/source/_integrations/flux.markdown b/source/_integrations/flux.markdown
index 8a6a5a667bb..da28d284fb1 100644
--- a/source/_integrations/flux.markdown
+++ b/source/_integrations/flux.markdown
@@ -99,8 +99,8 @@ switch:
- light.desk
- light.lamp
name: Fluxer
- start_time: '7:00'
- stop_time: '23:00'
+ start_time: "7:00"
+ stop_time: "23:00"
start_colortemp: 4000
sunset_colortemp: 3000
stop_colortemp: 1900
diff --git a/source/_integrations/flux_led.markdown b/source/_integrations/flux_led.markdown
index 1d23964e219..ebfe1e9cc32 100644
--- a/source/_integrations/flux_led.markdown
+++ b/source/_integrations/flux_led.markdown
@@ -17,6 +17,7 @@ This integration will provide local control over your LED lights/strips and can
The `flux_led` integration is configured through the Configuration -> Integrations page. You can select either auto configuration or manual configuration. For auto configuration the integration will automatically scan your network for any supported devices.
If you select the manual flow you can specify the name and host address of the light controller. You can add multiple lights/strips by adding additional instances of the integration.
+
### Effects
The Flux LED light offers a number of effects which are not included in other lighting packages. These can be selected from the front-end, or sent in the effect field of the `light.turn_on` command.
diff --git a/source/_integrations/foscam.markdown b/source/_integrations/foscam.markdown
index 465b1d339d5..2062cef880d 100644
--- a/source/_integrations/foscam.markdown
+++ b/source/_integrations/foscam.markdown
@@ -61,9 +61,9 @@ camera_image: camera.bedroom
camera_view: live
elements:
- type: icon
- icon: 'mdi:arrow-up'
+ icon: "mdi:arrow-up"
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 25px
bottom: 50px
tap_action:
@@ -73,9 +73,9 @@ elements:
entity_id: camera.bedroom
movement: up
- type: icon
- icon: 'mdi:arrow-down'
+ icon: "mdi:arrow-down"
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 25px
bottom: 0px
tap_action:
@@ -85,9 +85,9 @@ elements:
entity_id: camera.bedroom
movement: down
- type: icon
- icon: 'mdi:arrow-left'
+ icon: "mdi:arrow-left"
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 50px
bottom: 25px
tap_action:
@@ -97,9 +97,9 @@ elements:
entity_id: camera.bedroom
movement: left
- type: icon
- icon: 'mdi:arrow-right'
+ icon: "mdi:arrow-right"
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 0px
bottom: 25px
tap_action:
@@ -109,9 +109,9 @@ elements:
entity_id: camera.bedroom
movement: right
- type: icon
- icon: 'mdi:arrow-top-left'
+ icon: "mdi:arrow-top-left"
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 50px
bottom: 50px
tap_action:
@@ -121,9 +121,9 @@ elements:
entity_id: camera.bedroom
movement: top_left
- type: icon
- icon: 'mdi:arrow-top-right'
+ icon: "mdi:arrow-top-right"
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 0px
bottom: 50px
tap_action:
@@ -133,9 +133,9 @@ elements:
entity_id: camera.bedroom
movement: top_right
- type: icon
- icon: 'mdi:arrow-bottom-left'
+ icon: "mdi:arrow-bottom-left"
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 50px
bottom: 0px
tap_action:
@@ -145,9 +145,9 @@ elements:
entity_id: camera.bedroom
movement: bottom_left
- type: icon
- icon: 'mdi:arrow-bottom-right'
+ icon: "mdi:arrow-bottom-right"
style:
- background: 'rgba(255, 255, 255, 0.5)'
+ background: "rgba(255, 255, 255, 0.5)"
right: 0px
bottom: 0px
tap_action:
diff --git a/source/_integrations/frontier_silicon.markdown b/source/_integrations/frontier_silicon.markdown
index ed5c2694321..3959070439a 100644
--- a/source/_integrations/frontier_silicon.markdown
+++ b/source/_integrations/frontier_silicon.markdown
@@ -67,8 +67,8 @@ alias: "Bathroom Motion Detected"
trigger:
platform: state
entity_id: binary_sensor.motion_sensor_166d0001171111
- from: 'off'
- to: 'on'
+ from: "off"
+ to: "on"
action:
service: media_player.turn_on
data:
diff --git a/source/_integrations/garadget.markdown b/source/_integrations/garadget.markdown
index 1c627804a19..0b145fafc52 100644
--- a/source/_integrations/garadget.markdown
+++ b/source/_integrations/garadget.markdown
@@ -83,15 +83,15 @@ sensor:
- platform: template
sensors:
garage_door_status:
- friendly_name: 'State of the door'
+ friendly_name: "State of the door"
value_template: "{{ states('cover.garage_door') }}"
garage_door_time_in_state:
- friendly_name: 'Since'
+ friendly_name: "Since"
value_template: "{{ state_attr('cover.garage_door', 'time_in_state') }}"
garage_door_wifi_signal_strength:
- friendly_name: 'WiFi strength'
+ friendly_name: "WiFi strength"
value_template: "{{ state_attr('cover.garage_door', 'wifi_signal_strength') }}"
- unit_of_measurement: 'dB'
+ unit_of_measurement: "dB"
group:
garage_door:
diff --git a/source/_integrations/generic.markdown b/source/_integrations/generic.markdown
index 77b930b2b7a..78d8b2e89ff 100644
--- a/source/_integrations/generic.markdown
+++ b/source/_integrations/generic.markdown
@@ -89,7 +89,7 @@ camera:
- platform: generic
name: Weather
still_image_url: https://www.yr.no/place/Norway/Oslo/Oslo/Oslo/meteogram.svg
- content_type: 'image/svg+xml'
+ content_type: "image/svg+xml"
```
### Local image
diff --git a/source/_integrations/geo_json_events.markdown b/source/_integrations/geo_json_events.markdown
index b4530d73327..f1714768254 100644
--- a/source/_integrations/geo_json_events.markdown
+++ b/source/_integrations/geo_json_events.markdown
@@ -70,5 +70,5 @@ geo_location:
- platform: geo_json_events
url: https://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_day.geojson
radius: 250
- entity_namespace: 'usgs_earthquakes'
+ entity_namespace: "usgs_earthquakes"
```
diff --git a/source/_integrations/geo_rss_events.markdown b/source/_integrations/geo_rss_events.markdown
index 9e512cd9b1f..58905bbeb94 100644
--- a/source/_integrations/geo_rss_events.markdown
+++ b/source/_integrations/geo_rss_events.markdown
@@ -34,7 +34,7 @@ sensor:
- platform: geo_rss_events
name: NSW Fire Service
url: https://www.rfs.nsw.gov.au/feeds/majorIncidents.xml
- unit_of_measurement: 'Incidents'
+ unit_of_measurement: "Incidents"
categories:
- 'Emergency Warning'
- 'Watch and Act'
@@ -87,11 +87,11 @@ sensor:
- platform: geo_rss_events
name: Qld Fire and Emergency Services
url: https://www.qfes.qld.gov.au/data/alerts/bushfireAlert.xml
- unit_of_measurement: 'Alerts'
+ unit_of_measurement: "Alerts"
- platform: geo_rss_events
name: Tas Fire Service
url: http://www.fire.tas.gov.au/Show?pageId=colBushfireSummariesRss
- unit_of_measurement: 'Alerts'
+ unit_of_measurement: "Alerts"
- platform: geo_rss_events
name: WA Department of Fire and Emergency Services
url: https://www.emergency.wa.gov.au/data/incident_FCAD.rss
diff --git a/source/_integrations/google_translate.markdown b/source/_integrations/google_translate.markdown
index a225fd433b1..f0e2b42a00e 100644
--- a/source/_integrations/google_translate.markdown
+++ b/source/_integrations/google_translate.markdown
@@ -39,5 +39,5 @@ A full configuration sample including optional variables:
# Example configuration.yaml entry
tts:
- platform: google_translate
- language: 'de'
+ language: "de"
```
diff --git a/source/_integrations/google_travel_time.markdown b/source/_integrations/google_travel_time.markdown
index 08b820ed433..c01ac567ddd 100644
--- a/source/_integrations/google_travel_time.markdown
+++ b/source/_integrations/google_travel_time.markdown
@@ -142,11 +142,11 @@ You can also use the `homeassistant.update_entity` service to update the sensor
initial_state: "on"
trigger:
- platform: time_pattern
- minutes: '/2'
+ minutes: "/2"
condition:
- condition: time
- after: '08:00:00'
- before: '11:00:00'
+ after: "08:00:00"
+ before: "11:00:00"
- condition: time
weekday:
- mon
diff --git a/source/_integrations/griddy.markdown b/source/_integrations/griddy.markdown
index dfc3da50d26..88abb01dbfe 100644
--- a/source/_integrations/griddy.markdown
+++ b/source/_integrations/griddy.markdown
@@ -50,7 +50,7 @@ The current price for the Load Zone will appear as a sensor:
```yaml
- id: '1572630019168'
alias: Stop Tesla Charging if Power Price Spikes
- description: ''
+ description: ""
trigger:
- above: '30'
entity_id: sensor.lz_houston_price_now
diff --git a/source/_integrations/growatt_server.markdown b/source/_integrations/growatt_server.markdown
index 24f57f8116c..c20a1695bfb 100644
--- a/source/_integrations/growatt_server.markdown
+++ b/source/_integrations/growatt_server.markdown
@@ -54,12 +54,12 @@ name:
# Example configuration.yaml entry
sensor:
- platform: growatt_server
- name: 'growatt home'
+ name: "growatt home"
plant_id: 12345678
username: username
password: password
- platform: growatt_server
- name: 'growatt work'
+ name: "growatt work"
plant_id: 87654321
username: username
password: password
diff --git a/source/_integrations/hangouts.markdown b/source/_integrations/hangouts.markdown
index 6ca273dc3ce..5a1ccfd199e 100644
--- a/source/_integrations/hangouts.markdown
+++ b/source/_integrations/hangouts.markdown
@@ -238,7 +238,7 @@ sensor:
- platform: rest
resource: https://api.ipify.org/?format=json
name: External IP
- value_template: '{{ value_json.ip }}'
+ value_template: "{{ value_json.ip }}"
scan_interval: 10
automation:
@@ -248,7 +248,7 @@ automation:
platform: state
condition:
- condition: template
- value_template: '{{ trigger.from_state.state != trigger.to_state.state }}'
+ value_template: "{{ trigger.from_state.state != trigger.to_state.state }}"
- condition: template
value_template: '{{ not is_state("sensor.external_ip", "unavailable") }}'
action:
diff --git a/source/_integrations/harmony.markdown b/source/_integrations/harmony.markdown
index 4447a492cad..d9394cf60c0 100644
--- a/source/_integrations/harmony.markdown
+++ b/source/_integrations/harmony.markdown
@@ -180,10 +180,10 @@ sensor:
sensors:
family_room:
value_template: '{{ state_attr("remote.family_room", "current_activity") }}'
- friendly_name: 'Family Room'
+ friendly_name: "Family Room"
bedroom:
value_template: '{{ state_attr("remote.bedroom", "current_activity") }}'
- friendly_name: 'bedroom'
+ friendly_name: "bedroom"
```
{% endraw %}
diff --git a/source/_integrations/here_travel_time.markdown b/source/_integrations/here_travel_time.markdown
index 8b505cf0119..72c07605685 100644
--- a/source/_integrations/here_travel_time.markdown
+++ b/source/_integrations/here_travel_time.markdown
@@ -160,11 +160,11 @@ automation:
initial_state: "on"
trigger:
- platform: time_pattern
- minutes: '/2'
+ minutes: "/2"
condition:
- condition: time
- after: '08:00:00'
- before: '11:00:00'
+ after: "08:00:00"
+ before: "11:00:00"
- condition: time
weekday:
- mon
diff --git a/source/_integrations/history_stats.markdown b/source/_integrations/history_stats.markdown
index 6388ee42abf..eba31dcf5e9 100644
--- a/source/_integrations/history_stats.markdown
+++ b/source/_integrations/history_stats.markdown
@@ -34,8 +34,8 @@ sensor:
entity_id: light.my_lamp
state: "on"
type: time
- start: '{{ now().replace(hour=0, minute=0, second=0) }}'
- end: '{{ now() }}'
+ start: "{{ now().replace(hour=0, minute=0, second=0) }}"
+ end: "{{ now() }}"
```
{% endraw %}
@@ -135,8 +135,8 @@ Here are some examples of periods you could work with, and what to write in your
{% raw %}
```yaml
- start: '{{ now().replace(hour=0, minute=0, second=0) }}'
- end: '{{ now() }}'
+ start: "{{ now().replace(hour=0, minute=0, second=0) }}"
+ end: "{{ now() }}"
```
{% endraw %}
@@ -146,7 +146,7 @@ Here are some examples of periods you could work with, and what to write in your
{% raw %}
```yaml
- end: '{{ now().replace(hour=0, minute=0, second=0) }}'
+ end: "{{ now().replace(hour=0, minute=0, second=0) }}"
duration:
hours: 24
```
@@ -158,7 +158,7 @@ Here are some examples of periods you could work with, and what to write in your
{% raw %}
```yaml
- start: '{{ now().replace(hour=6, minute=0, second=0) }}'
+ start: "{{ now().replace(hour=6, minute=0, second=0) }}"
duration:
hours: 5
```
@@ -172,8 +172,8 @@ Here, last Monday is _today_ as a timestamp, minus 86400 times the current weekd
{% raw %}
```yaml
- start: '{{ as_timestamp( now().replace(hour=0, minute=0, second=0) ) - now().weekday() * 86400 }}'
- end: '{{ now() }}'
+ start: "{{ as_timestamp( now().replace(hour=0, minute=0, second=0) ) - now().weekday() * 86400 }}"
+ end: "{{ now() }}"
```
{% endraw %}
@@ -183,7 +183,7 @@ Here, last Monday is _today_ as a timestamp, minus 86400 times the current weekd
{% raw %}
```yaml
- end: '{{ now().replace(hour=0, minute=0, second=0) }}'
+ end: "{{ now().replace(hour=0, minute=0, second=0) }}"
duration:
days: 30
```
@@ -195,8 +195,8 @@ Here, last Monday is _today_ as a timestamp, minus 86400 times the current weekd
{% raw %}
```yaml
- start: '{{ 0 }}'
- end: '{{ now() }}'
+ start: "{{ 0 }}"
+ end: "{{ now() }}"
```
{% endraw %}
diff --git a/source/_integrations/homematic.markdown b/source/_integrations/homematic.markdown
index 57d428ac8f2..e8e2e433891 100644
--- a/source/_integrations/homematic.markdown
+++ b/source/_integrations/homematic.markdown
@@ -212,7 +212,7 @@ sensor:
bedroom_valve:
value_template: "{% raw %}{{ state_attr('climate.leq123456', 'level') }}{% endraw %}"
entity_id: climate.leq123456
- friendly_name: 'Bedroom valve'
+ friendly_name: "Bedroom valve"
```
### Variables
diff --git a/source/_integrations/hp_ilo.markdown b/source/_integrations/hp_ilo.markdown
index 9da5cce69a7..52704ea4ecc 100644
--- a/source/_integrations/hp_ilo.markdown
+++ b/source/_integrations/hp_ilo.markdown
@@ -102,11 +102,11 @@ sensor:
monitored_variables:
- name: CPU fanspeed
sensor_type: server_health
- unit_of_measurement: '%'
+ unit_of_measurement: "%"
value_template: '{% raw %}{{ ilo_data.fans["Fan 1"].speed[0] }}{% endraw %}'
- name: Inlet temperature
sensor_type: server_health
- unit_of_measurement: '°C'
+ unit_of_measurement: "°C"
value_template: '{% raw %}{{ ilo_data.temperature["01-Inlet Ambient"].currentreading[0] }}{% endraw %}'
- name: Server Health
sensor_type: server_health
diff --git a/source/_integrations/html5.markdown b/source/_integrations/html5.markdown
index 361374b63b0..78886c1c16d 100644
--- a/source/_integrations/html5.markdown
+++ b/source/_integrations/html5.markdown
@@ -179,7 +179,7 @@ Example of adding a tag to your notification. This won't create new notification
message: "Last known sensor state is {{ states('sensor.sensor') }}."
data:
data:
- tag: 'notification-about-sensor'
+ tag: "notification-about-sensor"
```
{% endraw %}
diff --git a/source/_integrations/http.markdown b/source/_integrations/http.markdown
index 84b109577a2..81ad50380d9 100644
--- a/source/_integrations/http.markdown
+++ b/source/_integrations/http.markdown
@@ -125,7 +125,7 @@ If you want to apply additional IP filtering, and automatically ban brute force
```yaml
127.0.0.1:
- banned_at: '2016-11-16T19:20:03'
+ banned_at: "2016-11-16T19:20:03"
```
After a ban is added a Persistent Notification is populated to the Home Assistant frontend.
diff --git a/source/_integrations/humidifier.markdown b/source/_integrations/humidifier.markdown
index 2c4b20d0e3e..df25806fa53 100644
--- a/source/_integrations/humidifier.markdown
+++ b/source/_integrations/humidifier.markdown
@@ -46,7 +46,7 @@ automation:
- service: humidifier.set_mode
data:
entity_id: humidifier.bedroom
- preset_mode: 'eco'
+ preset_mode: "eco"
```
### Service `humidifier.set_humidity`
diff --git a/source/_integrations/hyperion.markdown b/source/_integrations/hyperion.markdown
index 5d300ba53a6..5363d1e7efb 100644
--- a/source/_integrations/hyperion.markdown
+++ b/source/_integrations/hyperion.markdown
@@ -93,7 +93,7 @@ automation:
trigger:
- platform: state
entity_id: light.hyperion
- to: 'on'
+ to: "on"
action:
- service: light.turn_on
data:
@@ -108,13 +108,13 @@ To have the lights playing an effect when pausing, idle or turn off a media play
trigger:
- platform: state
entity_id: media_player.plex
- to: 'off'
+ to: "off"
- platform: state
entity_id: media_player.plex.plex
- to: 'paused'
+ to: "paused"
- platform: state
entity_id: media_player.plex.plex
- to: 'idle'
+ to: "idle"
action:
- service: light.turn_on
data:
@@ -129,7 +129,7 @@ To capture the screen when playing something on a media_player you can use this
trigger:
- platform: state
entity_id: media_player.plex
- to: 'playing'
+ to: "playing"
action:
- service: light.turn_on
data:
diff --git a/source/_integrations/ifttt.markdown b/source/_integrations/ifttt.markdown
index 5a14221833b..6a03b18df5e 100644
--- a/source/_integrations/ifttt.markdown
+++ b/source/_integrations/ifttt.markdown
@@ -154,7 +154,7 @@ automation:
action:
service: script.ifttt_notify
data:
- value1: 'HA Status:'
+ value1: "HA Status:"
value2: "{{ trigger.event.data.entity_id.split('_')[1] }} is "
value3: "{{ trigger.event.data.to_state.state }}"
```
diff --git a/source/_integrations/ihc.markdown b/source/_integrations/ihc.markdown
index d89995039f9..d65766f0ca5 100644
--- a/source/_integrations/ihc.markdown
+++ b/source/_integrations/ihc.markdown
@@ -167,7 +167,7 @@ ihc:
sensor:
- id: 12345
name: Temperatur_living_room
- unit_of_measurement: '°C'
+ unit_of_measurement: "°C"
note: Floor and wall temp.
position: On wall between windows
- id: 23456
diff --git a/source/_integrations/image_processing.markdown b/source/_integrations/image_processing.markdown
index 3733c3fee47..257528d283d 100644
--- a/source/_integrations/image_processing.markdown
+++ b/source/_integrations/image_processing.markdown
@@ -46,7 +46,7 @@ automation:
event_type: image_processing.detect_face
event_data:
entity_id: image_processing.door
- name: 'Hans Maier'
+ name: "Hans Maier"
...
```
@@ -67,7 +67,7 @@ automation:
trigger:
- platform: state
entity_id: sensor.door_motion_sensor
- to: 'on'
+ to: "on"
action:
- service: image_processing.scan
data:
diff --git a/source/_integrations/influxdb.markdown b/source/_integrations/influxdb.markdown
index 0ada21fbecf..abc8a21fa24 100644
--- a/source/_integrations/influxdb.markdown
+++ b/source/_integrations/influxdb.markdown
@@ -520,7 +520,7 @@ username: home-assistant
field: value
database: db1
- name: Min for last hour
- unit_of_measurement: '%'
+ unit_of_measurement: "%"
value_template: '{% raw %}{{ value | round(1) }}{% endraw %}'
group_function: min
where: '"entity_id" = ''salon'' and time > now() - 1h'
diff --git a/source/_integrations/input_boolean.markdown b/source/_integrations/input_boolean.markdown
index 4fbfb6a2ce0..17fb74f5b66 100644
--- a/source/_integrations/input_boolean.markdown
+++ b/source/_integrations/input_boolean.markdown
@@ -75,7 +75,7 @@ automation:
trigger:
platform: state
entity_id: binary_sensor.motion_garage
- to: 'on'
+ to: "on"
condition:
condition: state
entity_id: input_boolean.notify_home
diff --git a/source/_integrations/input_datetime.markdown b/source/_integrations/input_datetime.markdown
index ea80a79142f..ff0bbdd700a 100644
--- a/source/_integrations/input_datetime.markdown
+++ b/source/_integrations/input_datetime.markdown
@@ -136,7 +136,7 @@ If you have a `datetime` object you can use its `timestamp` method. Of if you ha
target:
entity_id: input_datetime.XXX
data:
- time: '05:30:00'
+ time: "05:30:00"
# Sets time to time from datetime object
- service: input_datetime.set_datetime
target:
@@ -148,7 +148,7 @@ If you have a `datetime` object you can use its `timestamp` method. Of if you ha
target:
entity_id: input_datetime.XXX
data:
- date: '2020-08-24'
+ date: "2020-08-24"
# Sets date to date from datetime object
- service: input_datetime.set_datetime
target:
@@ -160,7 +160,7 @@ If you have a `datetime` object you can use its `timestamp` method. Of if you ha
target:
entity_id: input_datetime.XXX
data:
- datetime: '2020-08-25 05:30:00'
+ datetime: "2020-08-25 05:30:00"
# Sets date and time from datetime object
- service: input_datetime.set_datetime
target:
diff --git a/source/_integrations/input_number.markdown b/source/_integrations/input_number.markdown
index f02fbbcf74f..f1264939204 100644
--- a/source/_integrations/input_number.markdown
+++ b/source/_integrations/input_number.markdown
@@ -154,7 +154,7 @@ input_select:
- Reading
- Relax
- 'OFF'
- initial: 'Select'
+ initial: "Select"
input_number:
bedroom_brightness:
name: Brightness
@@ -198,7 +198,7 @@ automation:
- alias: Set temp slider
trigger:
platform: mqtt
- topic: 'setTemperature'
+ topic: "setTemperature"
action:
service: input_number.set_value
data:
@@ -214,7 +214,7 @@ automation:
action:
service: mqtt.publish
data:
- topic: 'setTemperature'
+ topic: "setTemperature"
retain: true
payload: "{{ states('input_number.target_temp') | int }}"
```
@@ -249,7 +249,7 @@ automation:
trigger:
platform: state
entity_id: switch.something
- to: 'on'
+ to: "on"
action:
- delay: "00:{{ states('input_number.minutes') | int }}:{{ states('input_number.seconds') | int }}"
- service: switch.turn_off
diff --git a/source/_integrations/input_text.markdown b/source/_integrations/input_text.markdown
index b6c55104860..7a6fb1b552e 100644
--- a/source/_integrations/input_text.markdown
+++ b/source/_integrations/input_text.markdown
@@ -32,7 +32,7 @@ input_text:
max: 40
text3:
name: Text 3
- pattern: '[a-fA-F0-9]*'
+ pattern: "[a-fA-F0-9]*"
text4:
name: Text 4
mode: password
@@ -121,7 +121,7 @@ input_select:
- Reading
- Relax
- 'OFF'
- initial: 'Select'
+ initial: "Select"
input_text:
bedroom:
name: Brightness
diff --git a/source/_integrations/islamic_prayer_times.markdown b/source/_integrations/islamic_prayer_times.markdown
index b6471ef17c5..2e4b1d5f312 100644
--- a/source/_integrations/islamic_prayer_times.markdown
+++ b/source/_integrations/islamic_prayer_times.markdown
@@ -33,7 +33,7 @@ islamic_prayer_times:
{% configuration %}
calculation_method:
required: false
- default: 'isna'
+ default: "isna"
type: string
description: "The calculation method used for prayer times. Must be one of: `karachi`, `isna`, `mwl`, `makkah`."
{% endconfiguration %}
diff --git a/source/_integrations/isy994.markdown b/source/_integrations/isy994.markdown
index d9230e4763d..bada843acba 100644
--- a/source/_integrations/isy994.markdown
+++ b/source/_integrations/isy994.markdown
@@ -113,7 +113,7 @@ automation:
event_type: isy994_control
event_data:
entity_id: light.lr_track_lights_front
- control: 'DFON'
+ control: "DFON"
value: 255
formatted: "On"
uom: "100"
diff --git a/source/_integrations/keyboard_remote.markdown b/source/_integrations/keyboard_remote.markdown
index 7dd54f8c307..323c4c65109 100644
--- a/source/_integrations/keyboard_remote.markdown
+++ b/source/_integrations/keyboard_remote.markdown
@@ -19,7 +19,7 @@ The `evdev` package is used to interface with the keyboard and thus this is Linu
```yaml
# Example configuration.yaml entry
keyboard_remote:
- type: 'key_up'
+ type: "key_up"
```
{% configuration %}
@@ -62,7 +62,7 @@ A full configuration for two Keyboard Remotes could look like the one below:
```yaml
keyboard_remote:
- device_descriptor: '/dev/input/by-id/bluetooth-keyboard'
- type: 'key_down'
+ type: "key_down"
emulate_key_hold: true
emulate_key_hold_delay: 250
emulate_key_hold_repeat: 33
@@ -76,8 +76,8 @@ Or like the following for one keyboard:
```yaml
keyboard_remote:
- device_name: 'Bluetooth Keyboard'
- type: 'key_down'
+ device_name: "Bluetooth Keyboard"
+ type: "key_down"
```
And an automation rule to breathe life into it:
diff --git a/source/_integrations/light.markdown b/source/_integrations/light.markdown
index 42c373b0ba0..e4c9f8d3356 100644
--- a/source/_integrations/light.markdown
+++ b/source/_integrations/light.markdown
@@ -56,7 +56,7 @@ automation:
trigger:
- platform: state
entity_id: binary_sensor.motion_1
- to: 'on'
+ to: "on"
action:
- service: light.turn_on
data:
diff --git a/source/_integrations/lock.mqtt.markdown b/source/_integrations/lock.mqtt.markdown
index a73f9159414..08beb2e43ae 100644
--- a/source/_integrations/lock.mqtt.markdown
+++ b/source/_integrations/lock.mqtt.markdown
@@ -195,7 +195,7 @@ lock:
optimistic: false
qos: 1
retain: true
- value_template: '{{ value.x }}'
+ value_template: "{{ value.x }}"
```
{% endraw %}
diff --git a/source/_integrations/london_air.markdown b/source/_integrations/london_air.markdown
index a658cd136df..4f93deb4fab 100644
--- a/source/_integrations/london_air.markdown
+++ b/source/_integrations/london_air.markdown
@@ -63,12 +63,12 @@ To explore the data available within the `data` attribute of a sensor use the `d
- platform: template
sensors:
updated:
- friendly_name: 'Updated'
+ friendly_name: "Updated"
value_template: {% raw %}'{{state_attr('sensor.merton', 'updated')}}'{% endraw %}
merton_pm10:
- friendly_name: 'Merton PM10'
+ friendly_name: "Merton PM10"
value_template: {% raw %}'{{state_attr('sensor.merton', 'data')[0].pollutants[0].summary}}'{% endraw %}
westminster_s02:
- friendly_name: 'Westminster S02'
+ friendly_name: "Westminster S02"
value_template: {% raw %}'{{state_attr('sensor.westminster', 'data')[0].pollutants[3].summary}}'{% endraw %}
```
diff --git a/source/_integrations/loopenergy.markdown b/source/_integrations/loopenergy.markdown
index 537b90f4a36..ec0807bab89 100644
--- a/source/_integrations/loopenergy.markdown
+++ b/source/_integrations/loopenergy.markdown
@@ -47,11 +47,11 @@ Now you have the keys, add the following lines to your `configuration.yaml`, rep
sensor:
- platform: loopenergy
electricity:
- electricity_serial: 'ELECTRICAL_SERIAL'
- electricity_secret: 'ELECTRICAL_SECRET'
+ electricity_serial: "ELECTRICAL_SERIAL"
+ electricity_secret: "ELECTRICAL_SECRET"
gas:
- gas_serial: 'GAS_SERIAL'
- gas_secret: 'GAS_SECRET'
+ gas_serial: "GAS_SERIAL"
+ gas_secret: "GAS_SECRET"
```
{% configuration %}
diff --git a/source/_integrations/manual.markdown b/source/_integrations/manual.markdown
index c3a0bd5effa..c1d7274232a 100644
--- a/source/_integrations/manual.markdown
+++ b/source/_integrations/manual.markdown
@@ -134,7 +134,7 @@ In the configuration example below:
alarm_control_panel:
- platform: manual
name: Home Alarm
- code: '1234'
+ code: "1234"
arming_time: 30
delay_time: 20
trigger_time: 4
@@ -157,16 +157,16 @@ automation:
trigger:
- platform: state
entity_id: sensor.pir1
- to: 'active'
+ to: "active"
- platform: state
entity_id: sensor.pir2
- to: 'active'
+ to: "active"
- platform: state
entity_id: sensor.door
- to: 'open'
+ to: "open"
- platform: state
entity_id: sensor.window
- to: 'open'
+ to: "open"
condition:
- condition: state
entity_id: alarm_control_panel.ha_alarm
@@ -184,7 +184,7 @@ automation:
trigger:
- platform: state
entity_id: alarm_control_panel.ha_alarm
- to: 'triggered'
+ to: "triggered"
action:
- service: notify.notify
data:
@@ -199,7 +199,7 @@ automation:
trigger:
- platform: state
entity_id: sensor.front_door_lock_alarm_type
- to: '19'
+ to: "19"
# many z-wave locks use Alarm Type 19 for 'Unlocked by Keypad'
action:
- service: alarm_control_panel.alarm_disarm
@@ -215,7 +215,7 @@ Sending a Notification when the Alarm is Armed (Away/Home), Disarmed and in Pend
trigger:
- platform: state
entity_id: alarm_control_panel.home_alarm
- to: 'disarmed'
+ to: "disarmed"
action:
- service: notify.notify
data:
@@ -227,7 +227,7 @@ Sending a Notification when the Alarm is Armed (Away/Home), Disarmed and in Pend
trigger:
- platform: state
entity_id: alarm_control_panel.home_alarm
- to: 'pending'
+ to: "pending"
action:
- service: notify.notify
data:
@@ -239,7 +239,7 @@ Sending a Notification when the Alarm is Armed (Away/Home), Disarmed and in Pend
trigger:
- platform: state
entity_id: alarm_control_panel.home_alarm
- to: 'armed_away'
+ to: "armed_away"
action:
- service: notify.notify
data:
@@ -251,7 +251,7 @@ Sending a Notification when the Alarm is Armed (Away/Home), Disarmed and in Pend
trigger:
- platform: state
entity_id: alarm_control_panel.home_alarm
- to: 'armed_home'
+ to: "armed_home"
action:
- service: notify.notify
data:
diff --git a/source/_integrations/marytts.markdown b/source/_integrations/marytts.markdown
index 03272640728..400a0a01216 100644
--- a/source/_integrations/marytts.markdown
+++ b/source/_integrations/marytts.markdown
@@ -68,11 +68,11 @@ A full configuration sample including optional variables:
# Example configuration.yaml entry
tts:
- platform: marytts
- host: 'localhost'
+ host: "localhost"
port: 59125
- codec: 'WAVE_FILE'
- voice: 'cmu-slt-hsmm'
- language: 'en_US'
+ codec: "WAVE_FILE"
+ voice: "cmu-slt-hsmm"
+ language: "en_US"
effect:
Volume: "amount:2.0;",
TractScaler: "amount:1.5;",
diff --git a/source/_integrations/matrix.markdown b/source/_integrations/matrix.markdown
index e8bf91af00a..8d62e4d82e6 100644
--- a/source/_integrations/matrix.markdown
+++ b/source/_integrations/matrix.markdown
@@ -124,7 +124,7 @@ automation:
action:
service: notify.matrix_notify
data:
- message: 'It looks like you wrote !testword'
+ message: "It looks like you wrote !testword"
- alias: 'React to an introduction'
trigger:
platform: event
diff --git a/source/_integrations/rest.markdown b/source/_integrations/rest.markdown
index e8297f6bc9d..bcd3bdc8100 100644
--- a/source/_integrations/rest.markdown
+++ b/source/_integrations/rest.markdown
@@ -261,10 +261,10 @@ sensor:
- platform: template
sensors:
date:
- friendly_name: 'Date'
- value_template: '{{ states.sensor.json_time.attributes["date"] }}'
+ friendly_name: "Date"
+ value_template: "{{ states.sensor.json_time.attributes["date"] }}"
milliseconds:
- friendly_name: 'milliseconds'
+ friendly_name: "milliseconds"
value_template: '{{ states.sensor.json_time.attributes["milliseconds_since_epoch"] }}'
```
@@ -310,17 +310,17 @@ sensor:
entity_picture_template: '{{ "https://openweathermap.org/img/w/"+state_attr('sensor.owm_report', 'weather')[0]["icon"].lower()+".png" }}'
entity_id: sensor.owm_report
owm_temp:
- friendly_name: 'Outside temp'
+ friendly_name: "Outside temp"
value_template: '{{ state_attr('sensor.owm_report', 'main')["temp"]-273.15 }}'
unit_of_measurement: "°C"
entity_id: sensor.owm_report
owm_pressure:
- friendly_name: 'Outside pressure'
+ friendly_name: "Outside pressure"
value_template: '{{ state_attr('sensor.owm_report', 'main')["pressure"] }}'
unit_of_measurement: "hP"
entity_id: sensor.owm_report
owm_humidity:
- friendly_name: 'Outside humidity'
+ friendly_name: "Outside humidity"
value_template: '{{ state_attr('sensor.owm_report', 'main')["humidity"] }}'
unit_of_measurement: "%"
entity_id: sensor.owm_report
@@ -368,25 +368,25 @@ sensor:
- bedroom1
- bedroom2
- bedroom3
- value_template: 'OK'
+ value_template: "OK"
- platform: template
sensors:
bedroom1_temperature:
value_template: '{{ states.sensor.room_sensors.attributes["bedroom1"]["temperature"] }}'
device_class: temperature
- unit_of_measurement: '°C'
+ unit_of_measurement: "°C"
bedroom1_humidity:
value_template: '{{ states.sensor.room_sensors.attributes["bedroom1"]["humidity"] }}'
device_class: humidity
- unit_of_measurement: '%'
+ unit_of_measurement: "%"
bedroom1_battery:
value_template: '{{ states.sensor.room_sensors.attributes["bedroom1"]["battery"] }}'
device_class: battery
- unit_of_measurement: 'V'
+ unit_of_measurement: "V"
bedroom2_temperature:
value_template: '{{ states.sensor.room_sensors.attributes["bedroom2"]["temperature"] }}'
device_class: temperature
- unit_of_measurement: '°C'
+ unit_of_measurement: "°C"
```
{% endraw %}
@@ -405,7 +405,7 @@ sensor:
resource: http://192.168.1.105/status.xml
json_attributes_path: "$.response"
scan_interval: 15
- value_template: 'OK'
+ value_template: "OK"
json_attributes:
- "usr0"
- "pot0"
diff --git a/source/_integrations/rfxtrx.markdown b/source/_integrations/rfxtrx.markdown
index 4227916136e..d364d02db23 100644
--- a/source/_integrations/rfxtrx.markdown
+++ b/source/_integrations/rfxtrx.markdown
@@ -240,7 +240,7 @@ type_string: 'ARC'
id_string': 'C3'
data: '0710010143030170'
values':
- Command: 'On'
+ Command: "On"
Rssi numeric': 7
```
diff --git a/source/_integrations/ring.markdown b/source/_integrations/ring.markdown
index f98d6589e7f..f6a4130d838 100644
--- a/source/_integrations/ring.markdown
+++ b/source/_integrations/ring.markdown
@@ -62,11 +62,11 @@ Then you can use the following automation, with the entities from your system, w
```yaml
automation:
- alias: 'Save the video when the doorbell is pushed'
+ alias: "Save the video when the doorbell is pushed"
trigger:
- platform: state
entity_id: binary_sensor.front_doorbell_ding
- to: 'on'
+ to: "on"
action:
- service: downloader.download_file
data:
diff --git a/source/_integrations/ripple.markdown b/source/_integrations/ripple.markdown
index 221bf8359a8..b3f6b5c863c 100644
--- a/source/_integrations/ripple.markdown
+++ b/source/_integrations/ripple.markdown
@@ -16,7 +16,7 @@ To add the Ripple sensor to your installation, specify a ripple address to watch
# Example configuration.yaml entry
sensor:
- platform: ripple
- address: 'r3kmLJN5D28dHuH8vZNUZpMC43pEHpaocV'
+ address: "r3kmLJN5D28dHuH8vZNUZpMC43pEHpaocV"
```
{% configuration %}
diff --git a/source/_integrations/rmvtransport.markdown b/source/_integrations/rmvtransport.markdown
index 67c97889e44..6839796eea0 100644
--- a/source/_integrations/rmvtransport.markdown
+++ b/source/_integrations/rmvtransport.markdown
@@ -101,13 +101,13 @@ sensor:
- 'Bus'
- 'S'
- station: 3006907
- products: 'Bus'
+ products: "Bus"
destinations: ['Wiesbaden Dernsches Gelände', 'Mainz Hauptbahnhof']
name: Destination
- station: 3006904
- lines: 'S8'
+ lines: "S8"
max_journeys: 5
- products: 'S'
+ products: "S"
```
The first sensor will return S-Bahn, bus, RB and RE trains departures from Frankfurt Hauptbahnhof to Frankfurt Airport or Stadium that are at least 5 minutes away.
diff --git a/source/_integrations/rova.markdown b/source/_integrations/rova.markdown
index 5b691ff87cd..723987dff4b 100644
--- a/source/_integrations/rova.markdown
+++ b/source/_integrations/rova.markdown
@@ -84,10 +84,10 @@ To have your Home Assistant installation remind you of upcoming waste collection
# Example configuration.yaml entry for Rova waste collection reminder
automation:
- id: rova-garbage-bio-reminder
- alias: 'Send Rova Bio waste collection reminder'
+ alias: "Send Rova Bio waste collection reminder"
trigger:
- platform: time
- at: '19:00:00'
+ at: "19:00:00"
condition:
- condition: template
value_template: "{% if (as_timestamp(states('sensor.rova_garbage_gft')) - as_timestamp(now())) < 43200 %}true{% endif %}"
@@ -96,7 +96,7 @@ automation:
action:
- service: NOTIFICATION_SERVICE
data:
- message: 'Reminder: put out biowaste bin'
+ message: "Reminder: put out biowaste bin"
```
{% endraw %}
diff --git a/source/_integrations/rpi_gpio.markdown b/source/_integrations/rpi_gpio.markdown
index 193021f2dd0..a5a798bed0b 100644
--- a/source/_integrations/rpi_gpio.markdown
+++ b/source/_integrations/rpi_gpio.markdown
@@ -133,14 +133,14 @@ cover:
- platform: rpi_gpio
relay_time: 0.2
invert_relay: false
- state_pull_mode: 'UP'
+ state_pull_mode: "UP"
invert_state: true
covers:
- relay_pin: 10
state_pin: 11
- relay_pin: 12
state_pin: 13
- name: 'Right door'
+ name: "Right door"
```
## Remote Raspberry Pi Cover
diff --git a/source/_integrations/rtorrent.markdown b/source/_integrations/rtorrent.markdown
index d95803cb5b3..a5fdcac17ab 100644
--- a/source/_integrations/rtorrent.markdown
+++ b/source/_integrations/rtorrent.markdown
@@ -16,7 +16,7 @@ To enable this sensor, add the following lines to your `configuration.yaml`:
# Example configuration.yaml entry
sensor:
- platform: rtorrent
- url: 'http://
:@:/RPC2'
+ url: "http://:@:/RPC2"
monitored_variables:
- 'current_status'
- 'download_speed'
diff --git a/source/_integrations/satel_integra.markdown b/source/_integrations/satel_integra.markdown
index 7a6ae977b30..d112c1a8d67 100644
--- a/source/_integrations/satel_integra.markdown
+++ b/source/_integrations/satel_integra.markdown
@@ -118,43 +118,43 @@ satel_integra:
port: 7094
partitions:
01:
- name: 'House'
+ name: "House"
arm_home_mode: 2
02:
- name: 'Garage'
+ name: "Garage"
zones:
01:
- name: 'Bedroom'
- type: 'motion'
+ name: "Bedroom"
+ type: "motion"
02:
- name: 'Hall'
- type: 'motion'
+ name: "Hall"
+ type: "motion"
30:
- name: 'Kitchen - smoke'
- type: 'smoke'
+ name: "Kitchen - smoke"
+ type: "smoke"
113:
- name: 'Entry door'
- type: 'opening'
+ name: "Entry door"
+ type: "opening"
outputs:
05:
- name: 'Garden lights trigger'
- type: 'light'
+ name: "Garden lights trigger"
+ type: "light"
09:
- name: 'Gate opening trigger'
- type: 'opening'
+ name: "Gate opening trigger"
+ type: "opening"
30:
- name: 'Alarm triggered'
- type: 'safety'
+ name: "Alarm triggered"
+ type: "safety"
32:
- name: 'Alarm power problem'
- type: 'safety'
+ name: "Alarm power problem"
+ type: "safety"
switchable_outputs:
05:
- name: 'Gate open'
+ name: "Gate open"
06:
- name: 'Gate close'
+ name: "Gate close"
14:
- name: 'Garden light'
+ name: "Garden light"
```
@@ -165,8 +165,8 @@ For example:
alias: Flick the input switch when movement in bedroom detected
trigger:
platform: state
- entity_id: 'binary_sensor.bedroom'
- to: 'on'
+ entity_id: "binary_sensor.bedroom"
+ to: "on"
action:
service: input_boolean.turn_on
data:
diff --git a/source/_integrations/scene.markdown b/source/_integrations/scene.markdown
index 84beea83966..8e1f34af395 100644
--- a/source/_integrations/scene.markdown
+++ b/source/_integrations/scene.markdown
@@ -164,8 +164,8 @@ The following example turns off some entities as soon as a window opens. The sta
trigger:
- platform: state
entity_id: binary_sensor.window
- from: 'off'
- to: 'on'
+ from: "off"
+ to: "on"
condition: []
action:
- service: scene.create
@@ -180,13 +180,13 @@ The following example turns off some entities as soon as a window opens. The sta
- service: climate.set_hvac_mode
data:
entity_id: climate.ecobee
- hvac_mode: 'off'
+ hvac_mode: "off"
- alias: Window closed
trigger:
- platform: state
entity_id: binary_sensor.window
- from: 'on'
- to: 'off'
+ from: "on"
+ to: "off"
condition: []
action:
- service: scene.turn_on
diff --git a/source/_integrations/scrape.markdown b/source/_integrations/scrape.markdown
index a643ead125f..cdd267b3722 100644
--- a/source/_integrations/scrape.markdown
+++ b/source/_integrations/scrape.markdown
@@ -126,9 +126,9 @@ sensor:
- platform: scrape
resource: http://www.bfs.de/DE/themen/opt/uv/uv-index/prognose/prognose_node.html
name: Coast Ostsee
- select: 'p'
+ select: "p"
index: 19
- unit_of_measurement: 'UV Index'
+ unit_of_measurement: "UV Index"
```
### IFTTT status
@@ -141,7 +141,7 @@ sensor:
- platform: scrape
resource: https://status.ifttt.com/
name: IFTTT status
- select: '.component-status'
+ select: ".component-status"
```
### Get the latest podcast episode file URL
@@ -154,7 +154,7 @@ sensor:
- platform: scrape
resource: https://hasspodcast.io/feed/podcast
name: Home Assistant Podcast
- select: 'enclosure'
+ select: "enclosure"
index: 1
attribute: url
```
@@ -191,7 +191,7 @@ sensor:
resource: http://www.bom.gov.au/vic/forecasts/melbourne.shtml
name: Melbourne Forecast Summary
select: ".main .forecast p"
- value_template: '{{ value | truncate(255) }}'
+ value_template: "{{ value | truncate(255) }}"
# Request every hour
scan_interval: 3600
headers:
diff --git a/source/_integrations/script.markdown b/source/_integrations/script.markdown
index 3a66e6d3a04..a2dfa5b5ff4 100644
--- a/source/_integrations/script.markdown
+++ b/source/_integrations/script.markdown
@@ -120,12 +120,12 @@ script:
wakeup:
alias: Wake Up
icon: "mdi:party-popper"
- description: 'Turns on the bedroom lights and then the living room lights after a delay'
+ description: "Turns on the bedroom lights and then the living room lights after a delay"
variables:
turn_on_entity: group.living_room
fields:
minutes:
- description: 'The amount of time to wait before turning on the living room lights'
+ description: "The amount of time to wait before turning on the living room lights"
example: 1
# If called again while still running (probably in delay step), start over.
mode: restart
@@ -165,15 +165,15 @@ automation:
trigger:
platform: state
entity_id: light.bedroom
- from: 'off'
- to: 'on'
+ from: "off"
+ to: "on"
action:
service: script.turn_on
entity_id: script.notify_pushover
data:
variables:
- title: 'State change'
- message: 'The light is on!'
+ title: "State change"
+ message: "The light is on!"
```
The other way is calling the script as a service directly. In this case, all service data will be made available as variables. If we apply this approach on the script above, it would look like this:
@@ -184,13 +184,13 @@ automation:
trigger:
platform: state
entity_id: light.bedroom
- from: 'off'
- to: 'on'
+ from: "off"
+ to: "on"
action:
service: script.notify_pushover
data:
- title: 'State change'
- message: 'The light is on!'
+ title: "State change"
+ message: "The light is on!"
```
Using the variables in the script requires the use of templates:
@@ -199,14 +199,14 @@ Using the variables in the script requires the use of templates:
# Example configuration.yaml entry
script:
notify_pushover:
- description: 'Send a pushover notification'
+ description: "Send a pushover notification"
fields:
title:
- description: 'The title of the notification'
- example: 'State change'
+ description: "The title of the notification"
+ example: "State change"
message:
- description: 'The message content'
- example: 'The light is on!'
+ description: "The message content"
+ example: "The light is on!"
sequence:
- condition: state
entity_id: switch.pushover_notifications
diff --git a/source/_integrations/sensehat.markdown b/source/_integrations/sensehat.markdown
index ce8b3661f5b..bef5936f50d 100644
--- a/source/_integrations/sensehat.markdown
+++ b/source/_integrations/sensehat.markdown
@@ -87,14 +87,14 @@ sensor:
- platform: template
sensors:
sensehat_temperature:
- value_template: '{{ states('sensor.temperature') | round(1) }}'
- unit_of_measurement: '°C'
+ value_template: "{{ states('sensor.temperature') | round(1) }}"
+ unit_of_measurement: "°C"
sensehat_pressure:
- value_template: '{{ states('sensor.pressure') | round(1) }}'
- unit_of_measurement: 'mb'
+ value_template: "{{ states('sensor.pressure') | round(1) }}"
+ unit_of_measurement: "mb"
sensehat_humidity:
- value_template: '{{ states('sensor.humidity') | round(1) }}'
- unit_of_measurement: '%'
+ value_template: "{{ states('sensor.humidity') | round(1) }}"
+ unit_of_measurement: "%"
```
{% endraw %}
diff --git a/source/_integrations/sensor.buienradar.markdown b/source/_integrations/sensor.buienradar.markdown
index 2b75385f290..c155cdfa0db 100644
--- a/source/_integrations/sensor.buienradar.markdown
+++ b/source/_integrations/sensor.buienradar.markdown
@@ -158,7 +158,7 @@ Full configuration example (excluding forecasted conditions) where location is m
```yaml
# Example configuration.yaml entry
- platform: buienradar
- name: 'volkel'
+ name: "volkel"
# Force 'Meetstation Volkel' to be used:
latitude: 51.65
longitude: 5.70
diff --git a/source/_integrations/sensor.command_line.markdown b/source/_integrations/sensor.command_line.markdown
index 6629495ca39..38843c89f09 100644
--- a/source/_integrations/sensor.command_line.markdown
+++ b/source/_integrations/sensor.command_line.markdown
@@ -74,7 +74,7 @@ sensor:
command: "cat /sys/class/thermal/thermal_zone0/temp"
# If errors occur, make sure configuration file is encoded as UTF-8
unit_of_measurement: "°C"
- value_template: '{{ value | multiply(0.001) | round(1) }}'
+ value_template: "{{ value | multiply(0.001) | round(1) }}"
```
{% endraw %}
@@ -184,8 +184,8 @@ sensor:
json_attributes:
- date
- milliseconds_since_epoch
- command: 'python3 /home/pi/.homeassistant/scripts/datetime.py'
- value_template: '{{ value_json.time }}'
+ command: "python3 /home/pi/.homeassistant/scripts/datetime.py"
+ value_template: "{{ value_json.time }}"
```
{% endraw %}
diff --git a/source/_integrations/sensor.mqtt.markdown b/source/_integrations/sensor.mqtt.markdown
index cbadd65b129..f0d2dc8391b 100644
--- a/source/_integrations/sensor.mqtt.markdown
+++ b/source/_integrations/sensor.mqtt.markdown
@@ -165,7 +165,7 @@ sensor:
- platform: mqtt
name: "RSSI"
state_topic: "home/sensor1/infojson"
- unit_of_measurement: 'dBm'
+ unit_of_measurement: "dBm"
value_template: "{{ value_json.RSSI }}"
availability:
- topic: "home/sensor1/status"
@@ -219,7 +219,7 @@ sensor:
- platform: mqtt
name: "Battery Tablet"
state_topic: "owntracks/tablet/tablet"
- unit_of_measurement: '%'
+ unit_of_measurement: "%"
value_template: "{{ value_json.batt }}"
```
{% endraw %}
@@ -245,12 +245,12 @@ sensor:
- platform: mqtt
name: "Temperature"
state_topic: "office/sensor1"
- unit_of_measurement: '°C'
+ unit_of_measurement: "°C"
value_template: "{{ value_json.temperature }}"
- platform: mqtt
name: "Humidity"
state_topic: "office/sensor1"
- unit_of_measurement: '%'
+ unit_of_measurement: "%"
value_template: "{{ value_json.humidity }}"
```
{% endraw %}
diff --git a/source/_integrations/seven_segments.markdown b/source/_integrations/seven_segments.markdown
index c081034c085..b70c2f2dfe3 100644
--- a/source/_integrations/seven_segments.markdown
+++ b/source/_integrations/seven_segments.markdown
@@ -142,9 +142,9 @@ sensor:
- platform: template
sensors:
power_meter:
- value_template: '{{ states('image_processing.sevensegment_ocr_seven_segments') }}'
- friendly_name: 'Ampere'
- unit_of_measurement: 'A'
+ value_template: "{{ states('image_processing.sevensegment_ocr_seven_segments') }}"
+ friendly_name: "Ampere"
+ unit_of_measurement: "A"
```
{% endraw %}
diff --git a/source/_integrations/shodan.markdown b/source/_integrations/shodan.markdown
index b9b78d89a1a..324dd707f76 100644
--- a/source/_integrations/shodan.markdown
+++ b/source/_integrations/shodan.markdown
@@ -24,7 +24,7 @@ file:
sensor:
- platform: shodan
api_key: SHODAN_API_KEY
- query: 'home-assistant'
+ query: "home-assistant"
```
{% configuration %}
diff --git a/source/_integrations/shopping_list.markdown b/source/_integrations/shopping_list.markdown
index be4bee97dc0..84f35f1d071 100644
--- a/source/_integrations/shopping_list.markdown
+++ b/source/_integrations/shopping_list.markdown
@@ -56,8 +56,8 @@ service: notify.notify
title: "Time to shop?"
message: 'Click to open the shopping list'
data:
- clickAction: '/shopping-list'
- url: '/shopping-list'
+ clickAction: "/shopping-list"
+ url: "/shopping-list"
```
{% endraw %}
diff --git a/source/_integrations/simulated.markdown b/source/_integrations/simulated.markdown
index b358417e6a3..e0becd4c5ee 100644
--- a/source/_integrations/simulated.markdown
+++ b/source/_integrations/simulated.markdown
@@ -92,8 +92,8 @@ To give an example of simulating real world data, a simulated relative humidity
```yaml
sensor:
- platform: simulated
- name: 'simulated relative humidity'
- unit: '%'
+ name: "simulated relative humidity"
+ unit: "%"
amplitude: 0 # Turns off the periodic contribution
mean: 50
spread: 10
diff --git a/source/_integrations/sisyphus.markdown b/source/_integrations/sisyphus.markdown
index a4b0a866f7d..d51a3338623 100644
--- a/source/_integrations/sisyphus.markdown
+++ b/source/_integrations/sisyphus.markdown
@@ -34,9 +34,9 @@ Auto-detection can be a little slow, so if your table has a fixed IP address or
# This will skip auto-detection and add only the listed tables
sisyphus:
- name: 'TABLE_NAME'
- host: 'TABLE_IP_OR_HOSTNAME'
+ host: "TABLE_IP_OR_HOSTNAME"
- name: 'ANOTHER_TABLE_NAME'
- host: 'ANOTHER_TABLE_IP_OR_HOSTNAME'
+ host: "ANOTHER_TABLE_IP_OR_HOSTNAME"
```
{% configuration %}
diff --git a/source/_integrations/slack.markdown b/source/_integrations/slack.markdown
index d560cc42e01..bfaa5d448ba 100644
--- a/source/_integrations/slack.markdown
+++ b/source/_integrations/slack.markdown
@@ -44,7 +44,7 @@ notify:
- name: NOTIFIER_NAME
platform: slack
api_key: YOUR_API_KEY
- default_channel: '#general'
+ default_channel: "#general"
```
{% configuration %}
diff --git a/source/_integrations/sma.markdown b/source/_integrations/sma.markdown
index d7299b9c562..97ec2a97c8a 100644
--- a/source/_integrations/sma.markdown
+++ b/source/_integrations/sma.markdown
@@ -127,7 +127,7 @@ Example:
```yaml
custom:
yesterday_consumption:
- key: '6400_00543A01'
+ key: "6400_00543A01"
unit: kWh
factor: 1000
```
diff --git a/source/_integrations/smtp.markdown b/source/_integrations/smtp.markdown
index 4cb747c2bbf..77a7dcb991c 100644
--- a/source/_integrations/smtp.markdown
+++ b/source/_integrations/smtp.markdown
@@ -109,8 +109,8 @@ To use the SMTP notification, refer to it in an automation or script like in thi
seconds: 1
- service: notify.NOTIFIER_NAME
data:
- title: 'Intruder alert'
- message: 'Intruder alert at apartment!!'
+ title: "Intruder alert"
+ message: "Intruder alert at apartment!!"
data:
images:
- /home/pi/snapshot1.jpg
@@ -130,7 +130,7 @@ The optional `html` field makes a custom text/HTML multi-part message, allowing
seconds: 1
- service: notify.NOTIFIER_NAME
data:
- message: 'Intruder alert at apartment!!'
+ message: "Intruder alert at apartment!!"
data:
images:
- /home/pi/snapshot1.jpg
diff --git a/source/_integrations/snips.markdown b/source/_integrations/snips.markdown
index 445fc66de4b..06fd876fbdd 100644
--- a/source/_integrations/snips.markdown
+++ b/source/_integrations/snips.markdown
@@ -155,7 +155,7 @@ intent_script:
- service: light.turn_on
data:
entity_id: 'light.{{ objectLocation | replace(" ","_") }}'
- color_name: '{{ objectColor }}'
+ color_name: "{{ objectColor }}"
```
{% endraw %}
@@ -176,7 +176,7 @@ In this example if we had an intent triggered with 'Set a timer for five minutes
SetTimer:
speech:
type: plain
- text: 'Set a timer'
+ text: "Set a timer"
action:
service: script.set_timer
data:
@@ -221,7 +221,7 @@ intent_script:
turn_on_light:
speech:
type: plain
- text: 'OK, turning on the light'
+ text: "OK, turning on the light"
action:
service: light.turn_on
```
@@ -233,7 +233,7 @@ intent_script:
OpenGarageDoor:
speech:
type: plain
- text: 'OK, opening the garage door'
+ text: "OK, opening the garage door"
action:
- service: cover.open_cover
data:
@@ -250,14 +250,14 @@ automation:
trigger:
- platform: state
entity_id: binary_sensor.my_garage_door_sensor
- from: 'off'
- to: 'on'
+ from: "off"
+ to: "on"
for:
minutes: 10
sequence:
service: snips.say_action
data:
- text: 'Garage door has been open 10 minutes, would you like me to close it?'
+ text: "Garage door has been open 10 minutes, would you like me to close it?"
intent_filter:
- closeGarageDoor
@@ -266,7 +266,7 @@ intent_script:
closeGarageDoor:
speech:
type: plain
- text: 'OK, closing the garage door'
+ text: "OK, closing the garage door"
action:
- service: script.garage_door_close
```
diff --git a/source/_integrations/snmp.markdown b/source/_integrations/snmp.markdown
index 3ae76681929..bea1a295cd5 100644
--- a/source/_integrations/snmp.markdown
+++ b/source/_integrations/snmp.markdown
@@ -230,12 +230,12 @@ To create a sensor that displays the uptime for your printer in minutes, you can
# Example configuration.yaml entry
sensor:
- platform: snmp
- name: 'Printer uptime'
+ name: "Printer uptime"
host: 192.168.2.21
baseoid: 1.3.6.1.2.1.1.3.0
accept_errors: true
- unit_of_measurement: 'minutes'
- value_template: '{{((value | int) / 6000) | int}}'
+ unit_of_measurement: "minutes"
+ value_template: "{{((value | int) / 6000) | int}}"
```
{% endraw %}
@@ -389,12 +389,12 @@ switch:
- platform: snmp
name: SNMP v3 switch
host: 192.168.0.3
- version: '3'
- username: 'myusername'
- auth_key: 'myauthkey'
- auth_protocol: 'hmac-sha'
- priv_key: 'myprivkey'
- priv_protocol: 'aes-cfb-128'
+ version: "3"
+ username: "myusername"
+ auth_key: "myauthkey"
+ auth_protocol: "hmac-sha"
+ priv_key: "myprivkey"
+ priv_protocol: "aes-cfb-128"
baseoid: 1.3.6.1.4.1.19865.1.2.1.4.0
payload_on: 1
payload_off: 0
@@ -402,12 +402,12 @@ switch:
- platform: snmp
name: Enable PoE on Netgear switch port 2 using SNMP v3
host: 192.168.0.4
- version: '3'
- username: 'myusername'
- auth_key: 'myauthkey'
- auth_protocol: 'hmac-sha'
- priv_key: 'myprivkey'
- priv_protocol: 'des'
+ version: "3"
+ username: "myusername"
+ auth_key: "myauthkey"
+ auth_protocol: "hmac-sha"
+ priv_key: "myprivkey"
+ priv_protocol: "des"
baseoid: 1.3.6.1.4.1.4526.11.15.1.1.1.1.1.2
payload_on: 15400
payload_off: 3000
diff --git a/source/_integrations/sochain.markdown b/source/_integrations/sochain.markdown
index 00812002046..1a4dcf7a527 100644
--- a/source/_integrations/sochain.markdown
+++ b/source/_integrations/sochain.markdown
@@ -17,7 +17,7 @@ To add the SoChain sensor to your installation, specify a network and address to
sensor:
- platform: sochain
network: LTC
- address: 'M9m37h3dVkLDS13wYK7vcs7ck6MMMX6yhK'
+ address: "M9m37h3dVkLDS13wYK7vcs7ck6MMMX6yhK"
```
{% configuration %}
diff --git a/source/_integrations/solaredge_local.markdown b/source/_integrations/solaredge_local.markdown
index e79e009e8f9..60a9deba65c 100644
--- a/source/_integrations/solaredge_local.markdown
+++ b/source/_integrations/solaredge_local.markdown
@@ -72,7 +72,7 @@ sensor:
sensors:
solaredge_energy_this_year_template:
value_template: "{{ (states('sensor.solaredge_energy_this_year') | float / 1000) | round(2) }}"
- unit_of_measurement: 'KWh'
+ unit_of_measurement: "KWh"
icon_template: "mdi:solar-power"
```
diff --git a/source/_integrations/solax.markdown b/source/_integrations/solax.markdown
index fb7d708b853..022fa774e01 100644
--- a/source/_integrations/solax.markdown
+++ b/source/_integrations/solax.markdown
@@ -49,11 +49,11 @@ sensors:
sensors:
total_pv_power:
friendly_name: "Total PV Power"
- unit_of_measurement: 'W'
+ unit_of_measurement: "W"
value_template: "{{ (states('sensor.pv1_power') | float) + (states('sensor.pv2_power') | float) }}"
load_power:
friendly_name: "Load Power"
- unit_of_measurement: 'W'
+ unit_of_measurement: "W"
value_template: "{{ (states('sensor.power_now') | float) - (states('sensor.exported_power') | float) }}"
```
diff --git a/source/_integrations/spotify.markdown b/source/_integrations/spotify.markdown
index 1ed7da9f5de..4daf9cc50a5 100644
--- a/source/_integrations/spotify.markdown
+++ b/source/_integrations/spotify.markdown
@@ -104,7 +104,7 @@ script:
- service: media_player.play_media
data:
entity_id: media_player.spotify
- media_content_id: 'https://open.spotify.com/playlist/5xddIVAtLrZKtt4YGLM1SQ?si=YcvRqaKNTxOi043Qn4LYkg'
+ media_content_id: "https://open.spotify.com/playlist/5xddIVAtLrZKtt4YGLM1SQ?si=YcvRqaKNTxOi043Qn4LYkg"
media_content_type: playlist
```
diff --git a/source/_integrations/sql.markdown b/source/_integrations/sql.markdown
index 4055ca93bf9..33a39b8fa9e 100644
--- a/source/_integrations/sql.markdown
+++ b/source/_integrations/sql.markdown
@@ -28,7 +28,7 @@ sensor:
queries:
- name: Sun state
query: "SELECT * FROM states WHERE entity_id = 'sun.sun' ORDER BY state_id DESC LIMIT 1;"
- column: 'state'
+ column: "state"
```
{% endraw %}
@@ -77,7 +77,7 @@ This example shows the previously *recorded* state of the sensor `sensor.tempera
sensor:
- platform: random
name: Temperature in
- unit_of_measurement: '°C'
+ unit_of_measurement: "°C"
```
The query will look like this:
@@ -93,7 +93,7 @@ sensor:
queries:
- name: Temperature in
query: "SELECT * FROM states WHERE entity_id = 'sensor.temperature_in' ORDER BY state_id DESC LIMIT 1;"
- column: 'state'
+ column: "state"
```
Note that the SQL sensor state corresponds to the last row of the SQL result set.
@@ -138,7 +138,7 @@ sensor:
queries:
- name: DB size
query: 'SELECT table_schema "database", Round(Sum(data_length + index_length) / 1024, 1) "value" FROM information_schema.tables WHERE table_schema="hass" GROUP BY table_schema;'
- column: 'value'
+ column: "value"
unit_of_measurement: kB
```
@@ -156,8 +156,8 @@ sensor:
queries:
- name: DB Size
query: 'SELECT ROUND(page_count * page_size / 1024 / 1024, 1) as size FROM pragma_page_count(), pragma_page_size();'
- column: 'size'
- unit_of_measurement: 'MiB'
+ column: "size"
+ unit_of_measurement: "MiB"
```
{% endraw %}
@@ -174,7 +174,7 @@ sensor:
queries:
- name: DB size
query: "SELECT TOP 1 SUM(m.size) * 8 / 1024 as size FROM sys.master_files m INNER JOIN sys.databases d ON d.database_id=m.database_id WHERE d.name='DB_NAME';"
- column: 'size'
+ column: "size"
unit_of_measurement: MiB
```
{% endraw %}
diff --git a/source/_integrations/stream.markdown b/source/_integrations/stream.markdown
index 921c67c5002..7ef44cf8802 100644
--- a/source/_integrations/stream.markdown
+++ b/source/_integrations/stream.markdown
@@ -49,7 +49,7 @@ action:
service: camera.record
data:
entity_id: camera.quintal
- filename: '/config/www/my_stream.mp4'
+ filename: "/config/www/my_stream.mp4"
duration: 30
```
diff --git a/source/_integrations/switch.mysensors.markdown b/source/_integrations/switch.mysensors.markdown
index 4c6240447b4..deedcba260d 100644
--- a/source/_integrations/switch.mysensors.markdown
+++ b/source/_integrations/switch.mysensors.markdown
@@ -64,22 +64,22 @@ automation:
- alias: Turn HVAC on
trigger:
platform: time
- at: '5:30:00'
+ at: "5:30:00"
action:
service: mysensors.send_ir_code
entity_id: switch.hvac_1_1
data:
- V_IR_SEND: '0xC284' # the IR code to send
+ V_IR_SEND: "0xC284" # the IR code to send
- alias: Turn HVAC off
trigger:
platform: time
- at: '0:30:00'
+ at: "0:30:00"
action:
service: mysensors.send_ir_code
entity_id: switch.hvac_1_1
data:
- V_IR_SEND: '0xC288' # the IR code to send
+ V_IR_SEND: "0xC288" # the IR code to send
```
## Example sketches
diff --git a/source/_integrations/switch.rest.markdown b/source/_integrations/switch.rest.markdown
index cfb3c631d63..a5eef91d9ab 100644
--- a/source/_integrations/switch.rest.markdown
+++ b/source/_integrations/switch.rest.markdown
@@ -99,7 +99,7 @@ switch:
resource: http://IP_ADDRESS/led_endpoint
body_on: '{"active": "true"}'
body_off: '{"active": "false"}'
- is_on_template: '{{ value_json.is_active }}'
+ is_on_template: "{{ value_json.is_active }}"
headers:
Content-Type: application/json
verify_ssl: true
diff --git a/source/_integrations/switchbot.markdown b/source/_integrations/switchbot.markdown
index 6457db41d20..b3f509131e4 100644
--- a/source/_integrations/switchbot.markdown
+++ b/source/_integrations/switchbot.markdown
@@ -19,7 +19,7 @@ To enable it, add the following lines to your `configuration.yaml`:
```yaml
switch:
- platform: switchbot
- mac: 'MAC_ADDRESS'
+ mac: "MAC_ADDRESS"
```
{% configuration %}
diff --git a/source/_integrations/switcher_kis.markdown b/source/_integrations/switcher_kis.markdown
index 182b073e538..dc89d3b817f 100644
--- a/source/_integrations/switcher_kis.markdown
+++ b/source/_integrations/switcher_kis.markdown
@@ -26,9 +26,9 @@ To retrieve your device's details, please follow the instructions [here](https:/
```yaml
switcher_kis:
- phone_id: 'REPLACE_WITH_PHONE_ID'
- device_id: 'REPLACE_WITH_DEVICE_ID'
- device_password: 'REPLACE_WITH_DEVICE_PASSWORD'
+ phone_id: "REPLACE_WITH_PHONE_ID"
+ device_id: "REPLACE_WITH_DEVICE_ID"
+ device_password: "REPLACE_WITH_DEVICE_PASSWORD"
```
{% configuration %}
diff --git a/source/_integrations/switchmate.markdown b/source/_integrations/switchmate.markdown
index 4030da9efa3..e5b686ce516 100644
--- a/source/_integrations/switchmate.markdown
+++ b/source/_integrations/switchmate.markdown
@@ -19,7 +19,7 @@ To enable it, add the following lines to your `configuration.yaml`:
```yaml
switch:
- platform: switchmate
- mac: 'cb:25:0b......'
+ mac: "cb:25:0b......"
```
{% configuration %}
diff --git a/source/_integrations/system_log.markdown b/source/_integrations/system_log.markdown
index 3c103af479e..e2a42155efe 100644
--- a/source/_integrations/system_log.markdown
+++ b/source/_integrations/system_log.markdown
@@ -118,7 +118,7 @@ automation:
service: persistent_notification.create
data:
title: Something bad happened
- message: '{{ trigger.event.data.message }}'
+ message: "{{ trigger.event.data.message }}"
```
{% endraw %}
@@ -133,11 +133,11 @@ automation:
trigger:
platform: state
entity_id: binary_sensor.door
- from: 'off'
- to: 'on'
+ from: "off"
+ to: "on"
action:
service: system_log.write
data:
- message: 'Door opened!'
+ message: "Door opened!"
level: info
```
diff --git a/source/_integrations/systemmonitor.markdown b/source/_integrations/systemmonitor.markdown
index a8add075c15..3160553fd36 100644
--- a/source/_integrations/systemmonitor.markdown
+++ b/source/_integrations/systemmonitor.markdown
@@ -112,7 +112,7 @@ sensor:
- platform: systemmonitor
resources:
- type: network_in
- arg: 'Local Area Connection'
+ arg: "Local Area Connection"
```
If you need to use some other interface, open a command line prompt and type `ipconfig` to list all interface names. For example a wireless connection output from `ipconfig` might look like:
diff --git a/source/_integrations/telegram.markdown b/source/_integrations/telegram.markdown
index 15bb3c56193..f6ecd131b3f 100644
--- a/source/_integrations/telegram.markdown
+++ b/source/_integrations/telegram.markdown
@@ -118,7 +118,7 @@ To use notifications, please see the [getting started with automation page](/get
action:
service: notify.NOTIFIER_NAME
data:
- title: '*Send a message*'
+ title: "*Send a message*"
message: "That's an example that _sends_ a *formatted* message with a custom inline keyboard."
data:
inline_keyboard:
diff --git a/source/_integrations/telegram_bot.markdown b/source/_integrations/telegram_bot.markdown
index bca5c1258fc..6623f72256d 100644
--- a/source/_integrations/telegram_bot.markdown
+++ b/source/_integrations/telegram_bot.markdown
@@ -297,11 +297,11 @@ trigger:
platform: event
event_type: telegram_command
event_data:
- command: '/ping'
+ command: "/ping"
action:
- service: notify.notify
data:
- message: 'pong'
+ message: "pong"
```
An example that shows keyboard interaction with `notify.telegram`
@@ -311,11 +311,11 @@ trigger:
platform: event
event_type: telegram_command
event_data:
- command: '/start'
+ command: "/start"
action:
- service: notify.telegram
data:
- message: 'commands'
+ message: "commands"
data:
keyboard:
- '/ping, /alarm'
@@ -329,7 +329,7 @@ trigger:
platform: event
event_type: telegram_command
event_data:
- command: '/siren'
+ command: "/siren"
action:
- service: homeassistant.turn_on
entity_id: switch.vision_zm1601eu5_battery_operated_siren_switch_9_0
@@ -349,7 +349,7 @@ An example to show the use of event_data in action:
platform: event
event_type: telegram_command
event_data:
- command: '/speak'
+ command: "/speak"
action:
- service: notify.kitchen_echo
data:
@@ -379,9 +379,9 @@ Text repeater:
action:
- service: telegram_bot.send_message
data:
- title: '*Dumb automation*'
- target: '{{ trigger.event.data.user_id }}'
- message: 'You said: {{ trigger.event.data.text }}'
+ title: "*Dumb automation*"
+ target: "{{ trigger.event.data.user_id }}"
+ message: "You said: {{ trigger.event.data.text }}"
disable_notification: true
inline_keyboard:
- "Edit message:/edit_msg, Don't:/do_nothing"
@@ -400,18 +400,18 @@ Message editor:
platform: event
event_type: telegram_callback
event_data:
- command: '/edit_msg'
+ command: "/edit_msg"
action:
- service: telegram_bot.answer_callback_query
data:
- callback_query_id: '{{ trigger.event.data.id }}'
- message: 'Editing the message!'
+ callback_query_id: "{{ trigger.event.data.id }}"
+ message: "Editing the message!"
show_alert: true
- service: telegram_bot.edit_message
data:
- message_id: '{{ trigger.event.data.message.message_id }}'
- chat_id: '{{ trigger.event.data.chat_id }}'
- title: '*Message edit*'
+ message_id: "{{ trigger.event.data.message.message_id }}"
+ chat_id: "{{ trigger.event.data.chat_id }}"
+ title: "*Message edit*"
inline_keyboard:
- "Edit message:/edit_msg, Don't:/do_nothing"
- "Remove this button:/remove_button"
@@ -433,16 +433,16 @@ Keyboard editor:
platform: event
event_type: telegram_callback
event_data:
- command: '/remove_button'
+ command: "/remove_button"
action:
- service: telegram_bot.answer_callback_query
data:
- callback_query_id: '{{ trigger.event.data.id }}'
- message: 'Callback received for editing the inline keyboard!'
+ callback_query_id: "{{ trigger.event.data.id }}"
+ message: "Callback received for editing the inline keyboard!"
- service: telegram_bot.edit_replymarkup
data:
- message_id: 'last'
- chat_id: '{{ trigger.event.data.chat_id }}'
+ message_id: "last"
+ chat_id: "{{ trigger.event.data.chat_id }}"
inline_keyboard:
- "Edit message:/edit_msg, Don't:/do_nothing"
```
@@ -459,12 +459,12 @@ Only acknowledges the 'NO' answer:
platform: event
event_type: telegram_callback
event_data:
- command: '/do_nothing'
+ command: "/do_nothing"
action:
- service: telegram_bot.answer_callback_query
data:
- callback_query_id: '{{ trigger.event.data.id }}'
- message: 'OK, you said no!'
+ callback_query_id: "{{ trigger.event.data.id }}"
+ message: "OK, you said no!"
```
{% endraw %}
@@ -479,13 +479,13 @@ Telegram callbacks also support arguments and commands the same way as normal me
platform: event
event_type: telegram_callback
event_data:
- command: '/repeat'
+ command: "/repeat"
action:
- service: telegram_bot.answer_callback_query
data:
show_alert: true
- callback_query_id: '{{ trigger.event.data.id }}'
- message: 'I repeat: {{trigger.event.data["args"]}}'
+ callback_query_id: "{{ trigger.event.data.id }}"
+ message: "I repeat: {{trigger.event.data["args"]}}"
```
{% endraw %}
@@ -507,11 +507,11 @@ Receiving `chat_id` and `message_id` identifiers of sent messages by the `telegr
- service: input_number.set_value
data_template:
entity_id: input_number.chat_id
- value: '{{ trigger.event.data.chat_id }}'
+ value: "{{ trigger.event.data.chat_id }}"
- service: input_number.set_value
data_template:
entity_id: input_number.message_id
- value: '{{ trigger.event.data.message_id }}'
+ value: "{{ trigger.event.data.message_id }}"
```
{% endraw %}
diff --git a/source/_integrations/template.markdown b/source/_integrations/template.markdown
index 34638fdebd9..3f02a1a9c4c 100644
--- a/source/_integrations/template.markdown
+++ b/source/_integrations/template.markdown
@@ -27,7 +27,7 @@ sensor:
sensors:
solar_angle:
friendly_name: "Sun angle"
- unit_of_measurement: 'degrees'
+ unit_of_measurement: "degrees"
value_template: "{{ state_attr('sun.sun', 'elevation') }}"
sunrise:
@@ -127,7 +127,7 @@ sensor:
sensors:
solar_angle:
friendly_name: "Sun Angle"
- unit_of_measurement: '°'
+ unit_of_measurement: "°"
value_template: "{{ '%+.1f'|format(state_attr('sun.sun', 'elevation')) }}"
```
@@ -194,12 +194,12 @@ sensor:
sensors:
transmission_down_speed_kbps:
friendly_name: "Transmission Down Speed"
- unit_of_measurement: 'kB/s'
+ unit_of_measurement: "kB/s"
value_template: "{{ states('sensor.transmission_down_speed')|float * 1024 }}"
transmission_up_speed_kbps:
friendly_name: "Transmission Up Speed"
- unit_of_measurement: 'kB/s'
+ unit_of_measurement: "kB/s"
value_template: "{{ states('sensor.transmission_up_speed')|float * 1024 }}"
```
@@ -279,7 +279,7 @@ sensor:
Power Production
{% endif %}
value_template: "{{ states('sensor.power_consumption') }}"
- unit_of_measurement: 'kW'
+ unit_of_measurement: "kW"
```
{% endraw %}
@@ -335,7 +335,7 @@ sensor:
sensors:
nonsmoker:
value_template: '{{ ( ( as_timestamp(now()) - as_timestamp(strptime("06.07.2018", "%d.%m.%Y")) ) / 86400 ) | round(2) }}'
- friendly_name: 'Not smoking'
+ friendly_name: "Not smoking"
unit_of_measurement: "Days"
```
diff --git a/source/_integrations/thermoworks_smoke.markdown b/source/_integrations/thermoworks_smoke.markdown
index 694110dfa59..268adb59b7d 100644
--- a/source/_integrations/thermoworks_smoke.markdown
+++ b/source/_integrations/thermoworks_smoke.markdown
@@ -99,7 +99,7 @@ input_number:
min: -40
max: 500
step: 0.5
- unit_of_measurement: '°F'
+ unit_of_measurement: "°F"
icon: mdi:thermometer
automation:
diff --git a/source/_integrations/timer.markdown b/source/_integrations/timer.markdown
index dd7cf7eb4a7..3d276826fc9 100644
--- a/source/_integrations/timer.markdown
+++ b/source/_integrations/timer.markdown
@@ -25,7 +25,7 @@ To add a timer to your installation, add the following to your `configuration.ya
# Example configuration.yaml entry
timer:
laundry:
- duration: '00:01:00'
+ duration: "00:01:00"
```
{% configuration %}
@@ -121,7 +121,7 @@ Set a timer called `test` to a duration of 30 seconds.
# Example configuration.yaml entry
timer:
test:
- duration: '00:00:30'
+ duration: "00:00:30"
```
### Control a timer from the frontend
@@ -129,19 +129,19 @@ timer:
```yaml
# Example automations.yaml entry
- alias: Timerswitch
- id: 'Timerstart'
+ id: "Timerstart"
# Timer is started when the switch pumprun is set to on.
trigger:
- platform: state
entity_id: switch.pumprun
- to: 'on'
+ to: "on"
action:
- service: timer.start
entity_id: timer.test
# When timer is stopped, the time run out, another message is sent
- alias: Timerstop
- id: 'Timerstop'
+ id: "Timerstop"
trigger:
- platform: event
event_type: timer.finished
diff --git a/source/_integrations/tod.markdown b/source/_integrations/tod.markdown
index 32a170f3857..a667f6a59ce 100644
--- a/source/_integrations/tod.markdown
+++ b/source/_integrations/tod.markdown
@@ -25,13 +25,13 @@ binary_sensor:
- platform: tod
name: Early Morning
after: sunrise
- after_offset: '-02:00'
- before: '07:00'
+ after_offset: "-02:00"
+ before: "07:00"
- platform: tod
name: Late Morning
- after: '10:00'
- before: '12:00'
+ after: "10:00"
+ before: "12:00"
```
{% configuration %}
diff --git a/source/_integrations/totalconnect.markdown b/source/_integrations/totalconnect.markdown
index 9727736c885..410a5156f6b 100644
--- a/source/_integrations/totalconnect.markdown
+++ b/source/_integrations/totalconnect.markdown
@@ -46,7 +46,7 @@ automation:
trigger:
platform: state
entity_id: alarm_control_panel.total_connect
- to: 'disarmed'
+ to: "disarmed"
condition:
condition: sun
before: sunset
@@ -57,7 +57,7 @@ automation:
trigger:
platform: state
entity_id: alarm_control_panel.total_connect
- to: 'armed_away'
+ to: "armed_away"
action:
service: scene.turn_on
entity_id: scene.OnArmedAway
diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown
index b7af997a3ad..0048ab96525 100644
--- a/source/_integrations/tplink.markdown
+++ b/source/_integrations/tplink.markdown
@@ -155,23 +155,23 @@ sensor:
my_tp_switch_amps:
friendly_name_template: "{{ state_attr('switch.my_tp_switch','friendly_name') }} Current"
value_template: "{{ state_attr('switch.my_tp_switch','current_a') | float }}"
- unit_of_measurement: 'A'
+ unit_of_measurement: "A"
my_tp_switch_watts:
friendly_name_template: "{{ state_attr('switch.my_tp_switch','friendly_name') }} Current Consumption"
value_template: "{{ state_attr('switch.my_tp_switch','current_power_w') | float }}"
- unit_of_measurement: 'W'
+ unit_of_measurement: "W"
my_tp_switch_total_kwh:
friendly_name_template: "{{ state_attr('switch.my_tp_switch','friendly_name') }} Total Consumption"
value_template: "{{ state_attr('switch.my_tp_switch','total_energy_kwh') | float }}"
- unit_of_measurement: 'kWh'
+ unit_of_measurement: "kWh"
my_tp_switch_volts:
friendly_name_template: "{{ state_attr('switch.my_tp_switch','friendly_name') }} Voltage"
value_template: "{{ state_attr('switch.my_tp_switch','voltage') | float }}"
- unit_of_measurement: 'V'
+ unit_of_measurement: "V"
my_tp_switch_today_kwh:
friendly_name_template: "{{ state_attr('switch.my_tp_switch','friendly_name') }} Today's Consumption"
value_template: "{{ state_attr('switch.my_tp_switch','today_energy_kwh') | float }}"
- unit_of_measurement: 'kWh'
+ unit_of_measurement: "kWh"
```
{% endraw %}
diff --git a/source/_integrations/transport_nsw.markdown b/source/_integrations/transport_nsw.markdown
index b6cdd039367..c7f9edb401d 100644
--- a/source/_integrations/transport_nsw.markdown
+++ b/source/_integrations/transport_nsw.markdown
@@ -28,8 +28,8 @@ To enable the sensor, add the following lines to your `configuration.yaml` file:
# Example configuration.yaml entry
sensor:
- platform: transport_nsw
- stop_id: '200024'
- api_key: 'YOUR API KEY'
+ stop_id: "200024"
+ api_key: "YOUR API KEY"
```
{% configuration %}
@@ -65,20 +65,20 @@ More example configurations for bus or ferry.
# Example bus route configuration.yaml entry
sensor:
- platform: transport_nsw
- name: 'Bus'
- stop_id: '209516'
+ name: "Bus"
+ stop_id: "209516"
route: '199'
- api_key: 'YOUR API KEY'
+ api_key: "YOUR API KEY"
```
```yaml
# Example ferry configuration.yaml entry
sensor:
- platform: transport_nsw
- name: 'Ferry'
- stop_id: '10102008'
- destination: 'Circular Quay'
- api_key: 'YOUR API KEY'
+ name: "Ferry"
+ stop_id: "10102008"
+ destination: "Circular Quay"
+ api_key: "YOUR API KEY"
```
The sensor returns n/a if no stop event is found within the next 24h. A `template` sensor can help building a more meaningful string.
diff --git a/source/_integrations/tts.markdown b/source/_integrations/tts.markdown
index e5da42d2522..f48ccf11c62 100644
--- a/source/_integrations/tts.markdown
+++ b/source/_integrations/tts.markdown
@@ -110,7 +110,7 @@ Say to all `media_player` device entities:
service: tts.google_translate_say
entity_id: "all"
data:
- message: 'May the Force be with you.'
+ message: "May the Force be with you."
```
Say to the `media_player.floor` device entity:
@@ -119,7 +119,7 @@ Say to the `media_player.floor` device entity:
service: tts.google_translate_say
entity_id: media_player.floor
data:
- message: 'May the Force be with you.'
+ message: "May the Force be with you."
```
Say to the `media_player.floor` device entity in French:
@@ -128,8 +128,8 @@ Say to the `media_player.floor` device entity in French:
service: tts.google_translate_say
entity_id: media_player.floor
data:
- message: 'Que la force soit avec toi.'
- language: 'fr'
+ message: "Que la force soit avec toi."
+ language: "fr"
```
With a template:
diff --git a/source/_integrations/twilio_call.markdown b/source/_integrations/twilio_call.markdown
index b97d0334c5e..d247f2db679 100644
--- a/source/_integrations/twilio_call.markdown
+++ b/source/_integrations/twilio_call.markdown
@@ -49,7 +49,7 @@ automation:
action:
service: notify.twilio_call
data:
- message: 'The sun has set'
+ message: "The sun has set"
target:
- +14151234567
- +15105555555
diff --git a/source/_integrations/twilio_sms.markdown b/source/_integrations/twilio_sms.markdown
index db1cad1683a..81876bfacb4 100644
--- a/source/_integrations/twilio_sms.markdown
+++ b/source/_integrations/twilio_sms.markdown
@@ -52,7 +52,7 @@ automation:
action:
service: notify.twilio_sms
data:
- message: 'The sun has set'
+ message: "The sun has set"
target:
- '+14151234567'
- '+15105555555'
diff --git a/source/_integrations/uk_transport.markdown b/source/_integrations/uk_transport.markdown
index b8eacf5b8e5..de6455acf5a 100644
--- a/source/_integrations/uk_transport.markdown
+++ b/source/_integrations/uk_transport.markdown
@@ -85,23 +85,23 @@ Attributes can be accessed using the [template sensor](/integrations/template) a
- platform: template
sensors:
next_train_status:
- friendly_name: 'Next train status'
+ friendly_name: "Next train status"
value_template: >-
{{state_attr('sensor.next_train_to_wat', 'next_trains')[0].status}}
next_trains_origin:
- friendly_name: 'Next train origin'
+ friendly_name: "Next train origin"
value_template: >-
{{state_attr('sensor.next_train_to_wat', 'next_trains')[0].origin_name}}
next_trains_estimated:
- friendly_name: 'Next train estimated'
+ friendly_name: "Next train estimated"
value_template: >-
{{state_attr('sensor.next_train_to_wat', 'next_trains')[0].estimated}}
next_trains_scheduled:
- friendly_name: 'Next train scheduled'
+ friendly_name: "Next train scheduled"
value_template: >-
{{state_attr('sensor.next_train_to_wat', 'next_trains')[0].scheduled}}
next_trains_platform:
- friendly_name: 'Next train platform'
+ friendly_name: "Next train platform"
value_template: >-
{{state_attr('sensor.next_train_to_wat', 'next_trains')[0].platform}}
```
@@ -140,16 +140,16 @@ And the template sensor for viewing the next bus attributes.
- platform: template
sensors:
next_bus_route:
- friendly_name: 'Next bus route'
+ friendly_name: "Next bus route"
value_template: {% raw %}"{{state_attr('sensor.next_bus_to_wantage', 'next_buses')[0].route}}"{% endraw %}
next_bus_direction:
- friendly_name: 'Next bus direction'
+ friendly_name: "Next bus direction"
value_template: {% raw %}"{{state_attr('sensor.next_bus_to_wantage', 'next_buses')[0].direction}}"{% endraw %}
next_bus_scheduled:
- friendly_name: 'Next bus scheduled'
+ friendly_name: "Next bus scheduled"
value_template: {% raw %}"{{state_attr('sensor.next_bus_to_wantage', 'next_buses')[0].scheduled}}"{% endraw %}
next_bus_estimated:
- friendly_name: 'Next bus estimated'
+ friendly_name: "Next bus estimated"
value_template: {% raw %}"{{state_attr('sensor.next_bus_to_wantage', 'next_buses')[0].estimated}}"{% endraw %}
```
diff --git a/source/_integrations/universal.markdown b/source/_integrations/universal.markdown
index 36696398265..910d15b933b 100644
--- a/source/_integrations/universal.markdown
+++ b/source/_integrations/universal.markdown
@@ -119,12 +119,12 @@ media_player:
service: media_player.select_source
data:
entity_id: media_player.receiver
- source: '{{ source }}'
+ source: "{{ source }}"
volume_set:
service: media_player.volume_set
data:
entity_id: media_player.receiver
- volume_level: '{{ volume_level }}'
+ volume_level: "{{ volume_level }}"
attributes:
state: switch.living_room_tv
@@ -215,8 +215,8 @@ automation:
trigger:
platform: state
entity_id: media_player.kodi_tv
- from: 'off'
- to: 'playing'
+ from: "off"
+ to: "playing"
action:
- service: media_player.turn_on
entity_id: media_player.kodi_tv
@@ -225,7 +225,7 @@ automation:
trigger:
platform: state
entity_id: media_player.kodi_tv
- to: 'idle'
+ to: "idle"
for:
minutes: 15
action:
@@ -272,7 +272,7 @@ media_player:
service: remote.turn_on
data:
entity_id: remote.alexander_down_guest
- activity: '{{ source }}'
+ activity: "{{ source }}"
```
{% endraw %}
diff --git a/source/_integrations/upb.markdown b/source/_integrations/upb.markdown
index 5301e239339..c9a1c158df8 100644
--- a/source/_integrations/upb.markdown
+++ b/source/_integrations/upb.markdown
@@ -172,17 +172,17 @@ Start a scene blinking.
#automation:
- alias: 'Specific scene activated'
- description: 'Trigger when scene 9 on network 42 is activated'
+ description: "Trigger when scene 9 on network 42 is activated"
trigger:
platform: event
event_type: upb.scene_changed
event_data:
command: activated
- address: '42_9'
+ address: "42_9"
action:
service: persistent_notification.create
data:
- title: 'Scene Activated'
+ title: "Scene Activated"
message: >
Activated scene 9 on network 42: {{trigger.event.data.command}}, {{trigger.event.data.address}}
@@ -192,8 +192,8 @@ Start a scene blinking.
#script:
all_lights_on:
- alias: 'All Lights On'
- description: 'Activate two UPB scenes named interior_lights and exterior_lights'
+ alias: "All Lights On"
+ description: "Activate two UPB scenes named interior_lights and exterior_lights"
sequence:
- service: scene.turn_on
entity_id:
@@ -201,8 +201,8 @@ all_lights_on:
- scene.exterior_lights
all_lights_off:
- alias: 'All Lights Off'
- description: 'Deactivate two UPB scenes named interior_lights and exterior_lights'
+ alias: "All Lights Off"
+ description: "Deactivate two UPB scenes named interior_lights and exterior_lights"
sequence:
- service: upb.scene_deactivate
entity_id:
@@ -210,8 +210,8 @@ all_lights_off:
- scene.exterior_lights
kitchen_fade_on:
- alias: 'Kitchen Fade to On'
- description: 'Turn on kitchen light to 75% over a period of 10 seconds'
+ alias: "Kitchen Fade to On"
+ description: "Turn on kitchen light to 75% over a period of 10 seconds"
sequence:
- service: upb.light_fade_start
data:
diff --git a/source/_integrations/updater.markdown b/source/_integrations/updater.markdown
index 5488a931e04..732cb975d44 100644
--- a/source/_integrations/updater.markdown
+++ b/source/_integrations/updater.markdown
@@ -68,8 +68,8 @@ automation:
trigger:
- platform: state
entity_id: binary_sensor.updater
- from: 'off'
- to: 'on'
+ from: "off"
+ to: "on"
action:
- service: notify.notify
data:
diff --git a/source/_integrations/usgs_earthquakes_feed.markdown b/source/_integrations/usgs_earthquakes_feed.markdown
index 115375269aa..5f3bddf3961 100644
--- a/source/_integrations/usgs_earthquakes_feed.markdown
+++ b/source/_integrations/usgs_earthquakes_feed.markdown
@@ -32,7 +32,7 @@ To integrate the U.S. Geological Survey Earthquake Hazards Program feed, add the
# Example configuration.yaml entry
geo_location:
- platform: usgs_earthquakes_feed
- feed_type: 'past_day_all_earthquakes'
+ feed_type: "past_day_all_earthquakes"
```
{% configuration %}
@@ -112,7 +112,7 @@ The following state attributes are available for each entity in addition to the
# Example configuration.yaml entry
geo_location:
- platform: usgs_earthquakes_feed
- feed_type: 'past_month_all_earthquakes'
+ feed_type: "past_month_all_earthquakes"
radius: 50
minimum_magnitude: 0.0
latitude: 35.899722
diff --git a/source/_integrations/utility_meter.markdown b/source/_integrations/utility_meter.markdown
index ddd52292143..a9c816ad506 100644
--- a/source/_integrations/utility_meter.markdown
+++ b/source/_integrations/utility_meter.markdown
@@ -146,9 +146,9 @@ a time based automation can be used:
automation:
trigger:
- platform: time
- at: '09:00:00'
+ at: "09:00:00"
- platform: time
- at: '21:00:00'
+ at: "21:00:00"
action:
- service: utility_meter.next_tariff
entity_id: utility_meter.daily_energy
diff --git a/source/_integrations/vacuum.mqtt.markdown b/source/_integrations/vacuum.mqtt.markdown
index 035905f1f45..7b57856f1f9 100644
--- a/source/_integrations/vacuum.mqtt.markdown
+++ b/source/_integrations/vacuum.mqtt.markdown
@@ -245,7 +245,7 @@ vacuum:
- medium
- high
- max
- send_command_topic: 'vacuum/send_command'
+ send_command_topic: "vacuum/send_command"
```
{% endraw %}
@@ -478,7 +478,7 @@ vacuum:
- medium
- high
- max
- send_command_topic: 'vacuum/send_command'
+ send_command_topic: "vacuum/send_command"
```
### State MQTT Protocol
@@ -527,8 +527,8 @@ Service trigger example:
action:
service: vacuum.send_command
data:
- entity_id: 'vacuum.vacuum_entity'
- command: 'custom_command'
+ entity_id: vacuum.vacuum_entity
+ command: "custom_command"
params:
- key: value
```
@@ -602,8 +602,8 @@ Service trigger example:
action:
service: vacuum.send_command
data:
- entity_id: 'vacuum.vacuum_entity'
- command: 'custom_command'
+ entity_id: vacuum.vacuum_entity
+ command: "custom_command"
params:
- key: value
```
diff --git a/source/_integrations/velbus.markdown b/source/_integrations/velbus.markdown
index 8fe3c7f0dbe..e7ddd25ae4a 100644
--- a/source/_integrations/velbus.markdown
+++ b/source/_integrations/velbus.markdown
@@ -40,7 +40,7 @@ There are 2 options in configuring the Velbus integration:
```yaml
# Example configuration.yaml entry for a USB or serial interface
velbus:
- port: 'PORT_STRING'
+ port: "PORT_STRING"
```
## Port String
@@ -101,7 +101,7 @@ The actual linking can be realized by two automation rules. One rule to control
trigger:
- entity_id: binary_sensor.push_button_10
platform: state
- to: 'on'
+ to: "on"
condition: []
action:
- entity_id: light.living
@@ -113,10 +113,10 @@ The actual linking can be realized by two automation rules. One rule to control
trigger:
- entity_id: light.living
platform: state
- to: 'on'
+ to: "on"
- entity_id: light.living
platform: state
- to: 'off'
+ to: "off"
condition: []
action:
- condition: or
diff --git a/source/_integrations/version.markdown b/source/_integrations/version.markdown
index 50bcc7be6df..9c9e5c4d0a9 100644
--- a/source/_integrations/version.markdown
+++ b/source/_integrations/version.markdown
@@ -95,7 +95,7 @@ sensor:
- platform: rest
resource: http://IP_ADDRESS:8123/api/config
name: Current Version
- value_template: '{{ value_json.version }}'
+ value_template: "{{ value_json.version }}"
```
{% endraw %}
diff --git a/source/_integrations/vesync.markdown b/source/_integrations/vesync.markdown
index eb5c5856ef4..f92fac78ebd 100644
--- a/source/_integrations/vesync.markdown
+++ b/source/_integrations/vesync.markdown
@@ -115,15 +115,15 @@ sensor:
vesync_switch_watts:
friendly_name_template: "{{ states.switch.vesync_switch.name}} Current Consumption"
value_template: '{{ states.switch.vesync_switch.attributes["current_power_w"] | float }}'
- unit_of_measurement: 'W'
+ unit_of_measurement: "W"
vesync_switch_total_kwh:
friendly_name_template: "{{ states.switch.vesync_switch.name}} Total Consumption"
value_template: '{{ states.switch.vesync_switch.attributes["today_energy_kwh"] | float }}'
- unit_of_measurement: 'kWh'
+ unit_of_measurement: "kWh"
vesync_switch_volts:
friendly_name_template: "{{ states.switch.vesync_switch.name}} Voltage"
value_template: '{{ states.switch.vesync_switch.attributes["voltage"] | float }}'
- unit_of_measurement: 'V'
+ unit_of_measurement: "V"
```
{% endraw %}
diff --git a/source/_integrations/vlc.markdown b/source/_integrations/vlc.markdown
index 7d650229650..4198d1adfab 100644
--- a/source/_integrations/vlc.markdown
+++ b/source/_integrations/vlc.markdown
@@ -50,7 +50,7 @@ A full configuration for VLC could look like the one below:
media_player:
- platform: vlc
name: speaker_1
- arguments: '--alsa-audio-device=hw:1,0'
+ arguments: "--alsa-audio-device=hw:1,0"
```
## Additional configuration on macOS
diff --git a/source/_integrations/voicerss.markdown b/source/_integrations/voicerss.markdown
index d48f4e62b24..7d5b23c50f0 100644
--- a/source/_integrations/voicerss.markdown
+++ b/source/_integrations/voicerss.markdown
@@ -54,9 +54,9 @@ The configuration sample below shows how an entry can look like:
tts:
- platform: voicerss
api_key: YOUR_API_KEY
- language: 'de-de'
+ language: "de-de"
codec: mp3
- format: '8khz_8bit_mono'
+ format: "8khz_8bit_mono"
```
Please note, some media_players require a certain format. For example the Sonos requires a format of '44khz_16bit_stereo'
diff --git a/source/_integrations/volkszaehler.markdown b/source/_integrations/volkszaehler.markdown
index b746b986cc4..cab0a9b40a9 100644
--- a/source/_integrations/volkszaehler.markdown
+++ b/source/_integrations/volkszaehler.markdown
@@ -66,7 +66,7 @@ monitored_conditions:
sensor:
- platform: volkszaehler
host: demo.volkszaehler.org
- uuid: '57acbef0-88a9-11e4-934f-6b0f9ecd95a8'
+ uuid: "57acbef0-88a9-11e4-934f-6b0f9ecd95a8"
monitored_conditions:
- average
- consumption
diff --git a/source/_integrations/volvooncall.markdown b/source/_integrations/volvooncall.markdown
index 379ba07b74b..deebd695e10 100644
--- a/source/_integrations/volvooncall.markdown
+++ b/source/_integrations/volvooncall.markdown
@@ -131,7 +131,7 @@ volvooncall:
username: YOUR_USERNAME
password: YOUR_PASSWORD
name:
- YOUR_VIN_NUMBER: 'NEW_NAME'
+ YOUR_VIN_NUMBER: "NEW_NAME"
resources:
- odometer
- lock
diff --git a/source/_integrations/wake_on_lan.markdown b/source/_integrations/wake_on_lan.markdown
index 908ac71a794..aca1946d9e2 100644
--- a/source/_integrations/wake_on_lan.markdown
+++ b/source/_integrations/wake_on_lan.markdown
@@ -126,5 +126,5 @@ switch:
service: shell_command.turn_off_TARGET
shell_command:
- turn_off_TARGET: 'ssh hass@TARGET sudo pm-suspend'
+ turn_off_TARGET: "ssh hass@TARGET sudo pm-suspend"
```
diff --git a/source/_integrations/watson_iot.markdown b/source/_integrations/watson_iot.markdown
index 760091fdda4..908dbe56425 100644
--- a/source/_integrations/watson_iot.markdown
+++ b/source/_integrations/watson_iot.markdown
@@ -29,10 +29,10 @@ With this basic information you can configure the component:
```yaml
# Example configuration.yaml entry:
watson_iot:
- organization: 'organization_id'
- type: 'device_type'
- id: 'device_id'
- token: 'auth_token'
+ organization: "organization_id"
+ type: "device_type"
+ id: "device_id"
+ token: "auth_token"
```
{% configuration %}
diff --git a/source/_integrations/watson_tts.markdown b/source/_integrations/watson_tts.markdown
index 34f87e30b85..21e470b0614 100644
--- a/source/_integrations/watson_tts.markdown
+++ b/source/_integrations/watson_tts.markdown
@@ -65,7 +65,7 @@ Say to all `media_player` device entities:
```yaml
- service: tts.watson_tts_say
data:
- message: 'Hello from Watson'
+ message: "Hello from Watson"
```
or
diff --git a/source/_integrations/waze_travel_time.markdown b/source/_integrations/waze_travel_time.markdown
index d86d8d7df25..fe919e6665c 100644
--- a/source/_integrations/waze_travel_time.markdown
+++ b/source/_integrations/waze_travel_time.markdown
@@ -22,7 +22,7 @@ sensor:
- platform: waze_travel_time
origin: Montréal, QC
destination: Québec, QC
- region: 'US'
+ region: "US"
```
{% configuration %}
@@ -120,20 +120,20 @@ sensor:
name: "Me to destination"
origin: device_tracker.myphone
destination: sensor.dest_address
- region: 'US'
+ region: "US"
# Tracking entity to zone friendly name
- platform: waze_travel_time
name: Home To Eddie's House
origin: zone.home
destination: Eddies House # Friendly name of a zone
- region: 'US'
+ region: "US"
# Tracking entity in imperial unit
- platform: waze_travel_time
origin: person.paulus
destination: "725 5th Ave, New York, NY 10022, USA"
- region: 'US'
+ region: "US"
units: imperial # 'metric' for Metric, 'imperial' for Imperial
vehicle_type: motorcycle # vehicle type used for routing
@@ -142,7 +142,7 @@ sensor:
name: Westerscheldetunnel
origin: 51.330436, 3.802043
destination: 51.445677, 3.749929
- region: 'EU'
+ region: "EU"
avoid_toll_roads: true
avoid_subscription_roads: true
```
diff --git a/source/_integrations/webostv.markdown b/source/_integrations/webostv.markdown
index fec592feb89..e2786bbb1c8 100644
--- a/source/_integrations/webostv.markdown
+++ b/source/_integrations/webostv.markdown
@@ -231,7 +231,7 @@ automation:
trigger:
platform: state
entity_id: binary_sensor.front_door_motion
- to: 'on'
+ to: "on"
action:
service: notify.livingroom_tv
data:
diff --git a/source/_integrations/wink.markdown b/source/_integrations/wink.markdown
index a964ec8239a..7288ad50c23 100644
--- a/source/_integrations/wink.markdown
+++ b/source/_integrations/wink.markdown
@@ -370,7 +370,7 @@ script:
- service: wink.set_nimbus_dial_state
data:
entity_id: wink.nimbus_dial_1
- rotation: 'ccw'
+ rotation: "ccw"
```
## Alarm Control Panel
diff --git a/source/_integrations/withings.markdown b/source/_integrations/withings.markdown
index bd1e92b784b..83f1956f5a2 100644
--- a/source/_integrations/withings.markdown
+++ b/source/_integrations/withings.markdown
@@ -129,7 +129,7 @@ sensor:
sensors:
withings_weight_lbs_USER_PROFILE_NAME:
friendly_name: "withings weight_lbs_USER_PROFILE_NAME"
- unit_of_measurement: 'lbs'
+ unit_of_measurement: "lbs"
value_template: "{{ (states('sensor.withings_weight_kg_USER_PROFILE_NAME') | float * 2.20462262185) | round(2) }}"
icon_template: mdi:weight-pound
@@ -137,7 +137,7 @@ sensor:
sensors:
withings_bone_mass_lbs_USER_PROFILE_NAME:
friendly_name: "withings bone_mass_lbs_USER_PROFILE_NAME"
- unit_of_measurement: 'lbs'
+ unit_of_measurement: "lbs"
value_template: "{{ (states('sensor.withings_bone_mass_kg_USER_PROFILE_NAME') | float * 2.20462262185) | round(2) }}"
icon_template: mdi:weight-pound
@@ -145,7 +145,7 @@ sensor:
sensors:
withings_fat_free_mass_lbs_USER_PROFILE_NAME:
friendly_name: "withings fat_free_mass_lbs_USER_PROFILE_NAME"
- unit_of_measurement: 'lbs'
+ unit_of_measurement: "lbs"
value_template: "{{ (states('sensor.withings_fat_free_mass_kg_USER_PROFILE_NAME') | float * 2.20462262185) | round(2) }}"
icon_template: mdi:weight-pound
@@ -153,7 +153,7 @@ sensor:
sensors:
withings_fat_mass_lbs_USER_PROFILE_NAME:
friendly_name: "withings fat_mass_lbs_USER_PROFILE_NAME"
- unit_of_measurement: 'lbs'
+ unit_of_measurement: "lbs"
value_template: "{{ (states('sensor.withings_fat_mass_kg_USER_PROFILE_NAME') | float * 2.20462262185) | round(2) }}"
icon_template: mdi:weight-pound
@@ -161,7 +161,7 @@ sensor:
sensors:
withings_muscle_mass_lbs_USER_PROFILE_NAME:
friendly_name: "withings muscle_mass_lbs_USER_PROFILE_NAME"
- unit_of_measurement: 'lbs'
+ unit_of_measurement: "lbs"
value_template: "{{ (states('sensor.withings_muscle_mass_kg_USER_PROFILE_NAME') | float * 2.20462262185) | round(2) }}"
icon_template: mdi:weight-pound
```
diff --git a/source/_integrations/workday.markdown b/source/_integrations/workday.markdown
index 239ce73dbda..4c3b259580f 100644
--- a/source/_integrations/workday.markdown
+++ b/source/_integrations/workday.markdown
@@ -134,10 +134,10 @@ automation:
alias: Turn on heater on workdays
trigger:
platform: time
- at: '08:00:00'
+ at: "08:00:00"
condition:
condition: state
- entity_id: 'binary_sensor.workday_sensor'
+ entity_id: binary_sensor.workday_sensor
state: "on"
action:
service: switch.turn_on
diff --git a/source/_integrations/xbox.markdown b/source/_integrations/xbox.markdown
index f2568e11cbd..9f400cd6bb9 100644
--- a/source/_integrations/xbox.markdown
+++ b/source/_integrations/xbox.markdown
@@ -166,7 +166,7 @@ elements:
service: remote.send_command
service_data:
entity_id: remote.xboxone_remote
- command: 'A'
+ command: "A"
style:
top: 82.5%
left: 80.05%
@@ -179,7 +179,7 @@ elements:
service: remote.send_command
service_data:
entity_id: remote.xboxone_remote
- command: 'X'
+ command: "X"
style:
top: 60.0%
left: 70.6%
@@ -192,7 +192,7 @@ elements:
service: remote.send_command
service_data:
entity_id: remote.xboxone_remote
- command: 'B'
+ command: "B"
style:
top: 60.0%
left: 89.5%
@@ -205,7 +205,7 @@ elements:
service: remote.send_command
service_data:
entity_id: remote.xboxone_remote
- command: 'Y'
+ command: "Y"
style:
top: 37.9%
left: 80.05%
@@ -230,8 +230,8 @@ elements:
service: media_player.play_media
service_data:
entity_id: media_player.xboxone
- media_content_type: ''
- media_content_id: 'Home'
+ media_content_type: ""
+ media_content_id: "Home"
style:
top: 22.2%
left: 47.2%
diff --git a/source/_integrations/xiaomi.markdown b/source/_integrations/xiaomi.markdown
index 4760dbf753a..bfeed006de3 100644
--- a/source/_integrations/xiaomi.markdown
+++ b/source/_integrations/xiaomi.markdown
@@ -51,8 +51,8 @@ To enable the platform, add the following lines to your`configuration.yaml` file
camera:
- platform: xiaomi
name: Camera
- host: '192.168.1.100'
- model: 'yi'
+ host: "192.168.1.100"
+ model: "yi"
password: YOUR_PASSWORD
```
@@ -105,11 +105,11 @@ One particularly useful adjustment deals with video size. Since Yi videos are fa
camera:
- platform: xiaomi
name: My Camera
- host: '192.168.1.100'
- model: 'xiaofang'
+ host: "192.168.1.100"
+ model: "xiaofang"
password: YOUR_PASSWORD
path: /home/camera/feed
- ffmpeg_arguments: '-vf scale=800:450'
+ ffmpeg_arguments: "-vf scale=800:450"
```
## Hostname template
@@ -120,7 +120,7 @@ camera:
- platform: xiaomi
name: Front Camera
host: "{{ states.device_tracker.front_camera.attributes.ip }}"
- model: 'yi'
+ model: "yi"
password: 1234
path: /tmp/sd/record
```
diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown
index 8b9c211951b..595338ee8bd 100644
--- a/source/_integrations/xiaomi_miio.markdown
+++ b/source/_integrations/xiaomi_miio.markdown
@@ -1083,14 +1083,14 @@ script:
towel_heater:
sequence:
- service: remote.send_command
- entity_id: 'remote.bathroom_remote'
+ entity_id: "remote.bathroom_remote"
data:
command:
- 'activate_towel_heater'
please_cover_your_ears:
sequence:
- service: remote.send_command
- entity_id: 'remote.bathroom_remote'
+ entity_id: "remote.bathroom_remote"
data:
command:
- 'read_bad_poem'
@@ -1288,7 +1288,7 @@ automation:
- service: xiaomi_miio.vacuum_clean_zone
data:
entity_id: vacuum.xiaomi_vacuum
- repeats: '{{states('input_number.vacuum_passes')|int}}'
+ repeats: "{{states('input_number.vacuum_passes')|int}}"
zone: [[30914,26007,35514,28807], [20232,22496,26032,26496]]
```
@@ -1308,7 +1308,7 @@ automation:
- service: xiaomi_miio.vacuum_clean_zone
data:
entity_id: vacuum.xiaomi_vacuum
- repeats: '{{states('input_number.vacuum_passes')|int}}'
+ repeats: "{{states('input_number.vacuum_passes')|int}}"
zone:
- [30914,26007,35514,28807]
- [20232,22496,26032,26496]
@@ -1494,7 +1494,7 @@ vacuum_kitchen:
sequence:
- service: vacuum.send_command
data:
- entity_id: 'vacuum.xiaomi_vacuum_cleaner'
+ entity_id: "vacuum.xiaomi_vacuum_cleaner"
command: app_zoned_clean
params: [[23084,26282,27628,29727,1]]
```
diff --git a/source/_integrations/yale_smart_alarm.markdown b/source/_integrations/yale_smart_alarm.markdown
index 63db9a507c6..32562e3207e 100644
--- a/source/_integrations/yale_smart_alarm.markdown
+++ b/source/_integrations/yale_smart_alarm.markdown
@@ -53,7 +53,7 @@ automation:
trigger:
platform: state
entity_id: alarm_control_panel.yale_smart_alarm
- to: 'disarmed'
+ to: "disarmed"
condition:
condition: sun
before: sunset
@@ -64,7 +64,7 @@ automation:
trigger:
platform: state
entity_id: alarm_control_panel.yale_smart_alarm
- to: 'armed_away'
+ to: "armed_away"
action:
service: scene.turn_on
entity_id: scene.OnArmedAway
diff --git a/source/_integrations/yandextts.markdown b/source/_integrations/yandextts.markdown
index f198a5324e6..d7d2c82b576 100644
--- a/source/_integrations/yandextts.markdown
+++ b/source/_integrations/yandextts.markdown
@@ -68,7 +68,7 @@ The configuration sample below shows how an entry can look like:
tts:
- platform: yandextts
api_key: YOUR_API_KEY
- language: 'ru-RU'
+ language: "ru-RU"
codec: mp3
voice: oksana
emotion: evil
diff --git a/source/_integrations/yi.markdown b/source/_integrations/yi.markdown
index 9cfd99c49e2..e0ff63ee2bc 100644
--- a/source/_integrations/yi.markdown
+++ b/source/_integrations/yi.markdown
@@ -69,7 +69,7 @@ To enable the platform, add the following lines to your`configuration.yaml` file
camera:
- platform: yi
name: Camera
- host: '192.168.1.100'
+ host: "192.168.1.100"
password: my_password_123
```
@@ -112,8 +112,8 @@ One particularly useful adjustment deals with video size. Since Yi videos are fa
camera:
- platform: yi
name: My Camera
- host: '192.168.1.100'
+ host: "192.168.1.100"
password: my_password_123
path: /home/camera/feed
- ffmpeg_arguments: '-vf scale=800:450'
+ ffmpeg_arguments: "-vf scale=800:450"
```
diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown
index 47ebbe0f9f9..c33f74a3532 100644
--- a/source/_integrations/zha.markdown
+++ b/source/_integrations/zha.markdown
@@ -200,7 +200,7 @@ To correct the device type, also called domain, add the following to your `confi
zha:
device_config:
84:71:27:ff:fe:93:17:24-1: # format: {ieee}-{endpoint_id}
- type: 'switch' # corrected device type
+ type: "switch" # corrected device type
```
`{ieee}` is the device hardware address which can be read from the Home Assistant UI when looking at *Device info*. From device info, you can find the `{endpoint_id}` by viewing the *Zigbee device signature*.
diff --git a/source/_integrations/zwave.markdown b/source/_integrations/zwave.markdown
index 9129079c2f3..f5a36f008f3 100644
--- a/source/_integrations/zwave.markdown
+++ b/source/_integrations/zwave.markdown
@@ -92,7 +92,7 @@ automation:
- service: climate.set_hvac_mode
data:
entity_id: climate.remotec_zxt120_heating_1_id
- hvac_mode: 'Off'
+ hvac_mode: "Off"
```
**Note:** In the example above, the word `Off` is encased in single quotes to be valid YAML.
diff --git a/source/_lovelace/entities.markdown b/source/_lovelace/entities.markdown
index 18fcf51e0bf..c71d7246bf1 100644
--- a/source/_lovelace/entities.markdown
+++ b/source/_lovelace/entities.markdown
@@ -367,7 +367,7 @@ type: entities
title: Entities card sample
show_header_toggle: true
header:
- image: 'https://www.home-assistant.io/images/lovelace/header-footer/balloons-header.png'
+ image: "https://www.home-assistant.io/images/lovelace/header-footer/balloons-header.png"
type: picture
entities:
- entity: alarm_control_panel.alarm
@@ -427,7 +427,7 @@ entities:
entity: sun.sun
attribute: elevation
name: Sun elevation
- prefix: '~'
+ prefix: "~"
suffix: Units
- type: conditional
conditions:
diff --git a/source/_lovelace/entity.markdown b/source/_lovelace/entity.markdown
index 528e24de78a..132347a1f32 100644
--- a/source/_lovelace/entity.markdown
+++ b/source/_lovelace/entity.markdown
@@ -60,11 +60,11 @@ Alternatively, the card can be configured using YAML:
- type: entity
entity: light.bedroom
attribute: brightness
- unit: '%'
+ unit: "%"
- type: entity
entity: vacuum.downstairs
name: Vacuum
- icon: 'mdi:battery'
+ icon: "mdi:battery"
attribute: battery_level
- unit: '%'
+ unit: "%"
```
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 aefaddf13c2..0aeb42fc900 100644
--- a/source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown
+++ b/source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown
@@ -56,7 +56,7 @@ automation:
trigger:
platform: mqtt
mqtt_topic: home/alarm/fire
- mqtt_payload: 'on'
+ mqtt_payload: "on"
action:
service: ifttt.trigger
diff --git a/source/_posts/2015-11-16-zwave-switches-lights-and-honeywell-thermostats-now-supported.markdown b/source/_posts/2015-11-16-zwave-switches-lights-and-honeywell-thermostats-now-supported.markdown
index cf40d59d40b..44dddf474ae 100644
--- a/source/_posts/2015-11-16-zwave-switches-lights-and-honeywell-thermostats-now-supported.markdown
+++ b/source/_posts/2015-11-16-zwave-switches-lights-and-honeywell-thermostats-now-supported.markdown
@@ -14,7 +14,7 @@ categories: Release-Notes
homeassistant:
customize:
switch.ac:
- icon: 'mdi:air-conditioner'
+ icon: "mdi:air-conditioner"
```
#### Breaking changes
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 38be3dbc1a0..8788212344d 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
@@ -64,12 +64,12 @@ automation:
trigger:
- platform: state
entity_id: device_tracker.beacon_car
- from: 'not_home'
- to: 'home'
+ from: "not_home"
+ to: "home"
condition:
- condition: state
entity_id: switch.gate
- state: 'off'
+ state: "off"
action:
service: switch.turn_on
entity_id: switch.gate
@@ -97,7 +97,7 @@ automation:
condition:
- condition: state
entity_id: script.send_key_alert
- state: 'on'
+ state: "on"
action:
service: script.turn_off
entity_id: script.send_key_alert
@@ -111,8 +111,8 @@ script:
minutes: 2
- service: notify.notify
data:
- message: 'You forgot your keys'
- target: 'device/gregs_iphone'
+ message: "You forgot your keys"
+ target: "device/gregs_iphone"
```