Merge branch 'current' into next

_config.yml

@@ -101,8 +101,8 @@ social:
 # Home Assistant release details
 current_major_version: 0
 current_minor_version: 114
-current_patch_version: 2
-date_released: 2020-08-17
+current_patch_version: 4
+date_released: 2020-08-26
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

source/_docs/frontend/browsers.markdown

@@ -25,7 +25,7 @@ We would appreciate if you help to keep this page up-to-date and add feedback.
 
 | Browser               | Release        | State      | Comments                 |
 | :-------------------- |:---------------|:-----------|:-------------------------|
-| [Safari]              |                | works      | Map is fixed since 0.51. |
+| [Safari]              |                | works      | Not working with Safari Technology Preview 112 beta |
 
 ## Linux
 
@@ -59,10 +59,10 @@ We would appreciate if you help to keep this page up-to-date and add feedback.
 
 | Browser               | Release        | State      | Comments                 |
 | :-------------------- |:---------------|:-----------|:-------------------------|
-| [Safari]              |                | works      | Can also be added to desktop. Map is fixed since 0.51. |
-| [Chrome]              |                | works      |                          |
+| [Safari]              |                | works      | Can also be added to desktop. Not working in iOS 14 beta 5. |
+| [Chrome]              |                | works      | Not working in iOS 14 beta 5.               |
 
-There are reports that devices running with iOS prior to iOS 10, especially old iPads, are having trouble.
+There are reports that devices running with iOS prior to iOS 10, especially old iPads, are having trouble. Devices running iOS 14 beta 5, you will not be able to interact with Home Assistant controls.
 
 ## webOS
 

source/_docs/installation.markdown

@@ -64,6 +64,7 @@ If you use these install methods, we assume that you know how to manage and admi
 :-----|:-----|:-----
 [venv<BR>(as another user)](/docs/installation/raspberry-pi/)|Any Linux, Python 3.7 or later|Those familiar with their operating system
 [venv<BR>(as your user)](/docs/installation/virtualenv/)|Any Python 3.7 or later|Developers
+[Supervised](https://github.com/home-assistant/supervised-installer) | [Requirements](https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md#supported-operating-system-system-dependencies-and-versions) | Those very familiar with their operating system
 
 ## Community provided guides
 

source/_docs/mqtt/discovery.markdown

@@ -73,6 +73,7 @@ Supported abbreviations:
     'aux_cmd_t':           'aux_command_topic',
     'aux_stat_tpl':        'aux_state_template',
     'aux_stat_t':          'aux_state_topic',
+    'avty'                 'availability',
     'avty_t':              'availability_topic',
     'away_mode_cmd_t':     'away_mode_command_topic',
     'away_mode_stat_tpl':  'away_mode_state_template',
@@ -135,6 +136,8 @@ Supported abbreviations:
     'json_attr':           'json_attributes',
     'json_attr_t':         'json_attributes_topic',
     'json_attr_tpl':       'json_attributes_template',
+    'max_mirs':            'max_mireds',
+    'min_mirs':            'min_mireds',
     'max_temp':            'max_temp',
     'min_temp':            'min_temp',
     'mode_cmd_t':          'mode_command_topic',

source/_docs/scripts.markdown

@@ -22,6 +22,16 @@ script:
           message: 'Turned on the ceiling light!'
 ```
 
+## Types of Actions
+
+- [Call a Service](#call-a-service)
+- [Test a Condition](#test-a-condition)
+- [Delay](#delay)
+- [Wait](#wait)
+- [Fire an Event](#fire-an-event)
+- [Repeat a Group of Actions](#repeat-a-group-of-actions)
+- [Choose a Group of Actions](#choose-a-group-of-actions)
+
 ### Call a Service
 
 The most important one is the action to call a service. This can be done in various ways. For all the different possibilities, have a look at the [service calls page].
@@ -214,7 +224,7 @@ an event trigger.
 ```
 {% endraw %}
 
-### Raise and Consume Custom Events
+#### Raise and Consume Custom Events
 
 The following automation shows how to raise a custom event called `event_light_state_changed` with `entity_id` as the event data. The action part could be inside a script or an automation.
 
@@ -357,11 +367,36 @@ field | description
 
 This action allows you to select a sequence of other actions from a list of sequences.
 Nesting is fully supported.
-Each sequence is paired with a list of conditions (see [conditions page] for available options.) The first sequence whose conditions are all true will be run.
-An optional `default` sequence can be included which will be run if none of the sequences from the list are run.
+
+Each sequence is paired with a list of conditions. (See the [conditions page] for available options and how multiple conditions are handled.) The first sequence whose conditions are all true will be run.
+An _optional_ `default` sequence can be included which will be run only if none of the sequences from the list are run.
+
+The `choose` action can be used like an "if" statement. The first `conditions`/`sequence` pair is like the "if/then", and can be used just by itself. Or additional pairs can be added, each of which is like an "elif/then". And lastly, a `default` can be added, which would be like the "else."
 
 {% raw %}
 ```yaml
+# Example with just an "if"
+automation:
+  - trigger:
+      - platform: state
+        entity_id: binary_sensor.motion
+        to: 'on'
+    action:
+      - choose:
+          # IF nobody home, sound the alarm!
+          - conditions:
+              - condition: state
+                entity_id: group.family
+                state: not_home
+            sequence:
+              - service: script.siren
+                data:
+                  duration: 60
+      - service: light.turn_on
+        entity_id: all
+```
+```yaml
+# Example with "if" and "else"
 automation:
   - trigger:
       - platform: state
@@ -383,6 +418,39 @@ automation:
           - service: light.turn_off
             entity_id: light.front_lights
 ```
+```yaml
+# Example with "if", "elif" and "else"
+automation:
+  - trigger:
+      - platform: state
+        entity_id: input_boolean.simulate
+        to: 'on'
+    mode: restart
+    action:
+      - choose:
+          # IF morning
+          - conditions:
+              - condition: template
+                value_template: "{{ now().hour < 9 }}"
+            sequence:
+              - service: script.sim_morning
+          # ELIF day
+          - conditions:
+              - condition: template
+                value_template: "{{ now().hour < 18 }}"
+            sequence:
+              - service: light.turn_off
+                entity_id: light.living_room
+              - service: script.sim_day
+        # ELSE night
+        default:
+          - service: light.turn_off
+            entity_id: light.kitchen
+          - delay:
+              minutes: "{{ range(1, 11)|random }}"
+          - service: light.turn_off
+            entity_id: all
+```
 {% endraw %}
 
 [Script component]: /integrations/script/

source/_docs/z-wave/device-specific.markdown

@@ -1227,7 +1227,19 @@ To get the Z-Push Button 2 or the Z-Push Button 8 working in Home Assistant, you
         </CommandClass>
     ```
 
-    - 5.2 For the Z-Push Button 8:
+    - 5.2 For the Z-Push Button 4:
+
+    ```xml
+        <CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0">				<Instance index="1" />
+      <Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+      <Value type="int" genre="user" instance="1" index="1" label="Button 1" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+      <Value type="int" genre="user" instance="1" index="2" label="Button 2" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+      <Value type="int" genre="user" instance="1" index="3" label="Button 3" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+      <Value type="int" genre="user" instance="1" index="4" label="Button 4" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+        </CommandClass>
+    ```
+    
+    - 5.3 For the Z-Push Button 8:
 
     ```xml
         <CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0">				<Instance index="1" />

source/_docs/z-wave/installation.markdown

@@ -93,7 +93,7 @@ An easy script to generate a random key:
 cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//'
 ```
 
-You can also use sites like [this one](https://www.random.org/cgi-bin/randbyte?nbytes=16&format=h) to generate the required data, just remember to put `0x` before each pair of characters:
+You can also use sites like [this one](https://www.random.org/cgi-bin/randbyte?nbytes=16&format=h) to generate the required data, just remember to put `0x` before each pair of characters and a `,` between them:
 
 ```yaml
 # Example configuration.yaml entry for network_key

source/_integrations/bayesian.markdown

@@ -3,6 +3,7 @@ title: Bayesian
 description: Instructions on how to integrate threshold Bayesian sensors into Home Assistant.
 ha_category:
   - Utility
+  - Binary Sensor
 ha_iot_class: Local Polling
 ha_release: 0.53
 ha_quality_scale: internal

source/_integrations/binary_sensor.template.markdown

@@ -52,7 +52,7 @@ sensors:
           required: false
           type: [string, list]
         unique_id:
-          description: An ID that uniquely identifies this binary sensor. Set this to an unique value to allow customisation trough the UI.
+          description: An ID that uniquely identifies this binary sensor. Set this to an unique value to allow customisation through the UI.
           required: false
           type: string
         device_class:

source/_integrations/caldav.markdown

@@ -107,6 +107,11 @@ days:
   description: Number of days for the search for upcoming appointments.
   default: 1
   type: integer
+verify_ssl:
+  description: Verify the SSL certificate or not. If using self-signed certificates, this usually needs to be set to "False".
+  required: false
+  type: boolean
+  default: true
 {% endconfiguration %}
 
 ## Sensor attributes

source/_integrations/cast.markdown

@@ -23,7 +23,7 @@ Support for mDNS discovery in your local network is mandatory. Make sure that yo
 Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device.  You can use it by adding the [Cast entity row](/lovelace/entities/#cast) to your Lovelace UI, or by calling the `cast.show_lovelace_view` service. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your Lovelace YAML for each view, as outlined in the [views documentation](/lovelace/views/#path). The `dashboard_path` is the part of the Lovelace UI URL that follows the defined `base_url` Typically "lovelace". The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call):
 
 ```yaml
-'cast_downstairs_on_kitchen':
+cast_downstairs_on_kitchen:
   alias: Show Downstairs on kitchen
   sequence:
   - data:

source/_integrations/denonavr.markdown

@@ -50,6 +50,7 @@ Known supported devices:
 - Marantz SR5008
 - Marantz SR5011
 - Marantz SR6007 - SR6012
+- Marantz SR8015
 - Marantz NR1504
 - Marantz NR1506
 - Marantz NR1602

source/_integrations/derivative.markdown

@@ -4,6 +4,7 @@ description: Instructions on how to integrate Derivative Sensor into Home Assist
 ha_category:
   - Utility
   - Energy
+  - Sensor
 ha_release: 0.105
 ha_iot_class: Local Push
 logo: derivative.png

source/_integrations/envisalink.markdown

@@ -29,7 +29,7 @@ An `envisalink` section must be present in the `configuration.yaml` file and con
 ```yaml
 # Example configuration.yaml entry
 envisalink:
-  host: <envisalink IP address>
+  host: <envisalink IP address or hostname>
   panel_type: HONEYWELL or DSC
   user_name: YOUR_USERNAME
   password: YOUR_PASSWORD
@@ -54,7 +54,7 @@ envisalink:
 
 {% configuration %}
 host:
-  description: The IP address of the Envisalink device on your home network.
+  description: The IP address or hostname (host.fqdn.tld) of the Envisalink device on your home network.
   required: true
   type: string
 panel_type:

source/_integrations/filesize.markdown

@@ -3,6 +3,7 @@ title: File Size
 description: Component for monitoring the size of a file.
 ha_category:
   - Utility
+  - Sensor
 ha_iot_class: Local Polling
 ha_release: 0.64
 ha_domain: filesize

source/_integrations/filter.markdown

@@ -3,6 +3,7 @@ title: Filter
 description: Instructions on how to integrate Data Filter Sensors into Home Assistant.
 ha_category:
   - Utility
+  - Sensor
 ha_release: 0.65
 ha_iot_class: Local Push
 ha_quality_scale: internal

source/_integrations/folder.markdown

@@ -3,6 +3,7 @@ title: Folder
 description: Sensor for monitoring the contents of a folder.
 ha_category:
   - Utility
+  - Sensor
 ha_iot_class: Local Polling
 ha_release: 0.64
 ha_domain: folder

source/_integrations/hangouts.markdown

@@ -212,9 +212,9 @@ Sends a message to the given conversations.
 
 | Service data attribute | Optional | Description                                      |
 |------------------------|----------|--------------------------------------------------|
-| target                 | List of targets with id or name. [Required] | [{"id": "UgxrXzVrARmjx_C6AZx4AaABAagBo-6UCw"}, {"name": "Test Conversation"}] |
-| message                | List of message segments, only the "text" field is required in every segment. [Required] | [{"text":"test", "is_bold": false, "is_italic": false, "is_strikethrough": false, "is_underline": false, "parse_str": false, "link_target": "http://google.com"}, ...] |
-| data                   | Extra options | {"image_file": "path"} / {"image_url": "url"} |
+| target                 | No | List of targets with id or name. |
+| message                | No | List of message segments, only the "text" field is required in every segment. |
+| data                   | Yes | Either a path to an image file or a URL to an image. |
 
 ### Service `hangouts.reconnect`
 

source/_integrations/history_stats.markdown

@@ -3,6 +3,7 @@ title: History Stats
 description: Instructions about how to integrate historical statistics into Home Assistant.
 ha_category:
   - Utility
+  - Sensor
 ha_iot_class: Local Polling
 ha_release: 0.39
 ha_quality_scale: internal

source/_integrations/homeassistant.markdown

@@ -24,7 +24,9 @@ Loads the main configuration file (`configuration.yaml`) and all linked files. O
 
 ### Service `homeassistant.restart`
 
-Restarts the Home Assistant instance (also reloading the configuration on start).
+Restarts the Home Assistant instance (also reloading the configuration on start). 
+
+This will also do a configuration check before doing a restart. If the configuration check fails then Home Assistant will not be restarted, instead a persistent notification with the ID `persistent_notification.homeassistant_check_config` will be created. The logs will show details on what failed the configuration check.
 
 ### Service `homeassistant.stop`
 

source/_integrations/influxdb.markdown

@@ -343,7 +343,7 @@ sensor:
         name: "Mean humidity reported from past day"
         query: >
           filter(fn: (r) => r._field == "value" and r.domain == "sensor" and strings.containsStr(v: r.entity_id, substr: "humidity"))
-          |> keep(columns: ["_value"])\n"
+          |> keep(columns: ["_value"])
         range_start: "-1d"
 ```
 

source/_integrations/integration.markdown

@@ -4,6 +4,7 @@ description: Instructions on how to integrate Integration Sensor into Home Assis
 ha_category:
   - Utility
   - Energy
+  - Sensor
 ha_release: 0.87
 ha_iot_class: Local Push
 ha_quality_scale: internal
@@ -55,7 +56,7 @@ unit:
   required: false
   type: string
 method:
-  description: Riemann sum method to be used. Available methods are `trapezoidal`, `left` and `right`."
+  description: "Riemann sum method to be used. Available methods are `trapezoidal`, `left` and `right`."
   required: false
   type: string
   default: trapezoidal

source/_integrations/linksys_smart.markdown

@@ -13,6 +13,7 @@ Tested routers:
 
 - Linksys WRT3200ACM MU-MIMO Gigabit Wi-Fi Wireless Router
 - Linksys WRT1900ACS Dual-band Wi-Fi Router
+- Linksys EA6900 AC1900 Dual-Band Wi-Fi Router
 - Linksys EA8300 Max-Stream AC2200 Tri-Band Wi-Fi Router
 
 ## Setup

source/_integrations/min_max.markdown

@@ -3,6 +3,7 @@ title: Min/Max
 description: Instructions on how to integrate min/max sensors into Home Assistant.
 ha_category:
   - Utility
+  - Sensor
 ha_iot_class: Local Polling
 ha_release: 0.31
 ha_quality_scale: internal

source/_integrations/netatmo.markdown

@@ -57,7 +57,7 @@ Menu: **Configuration** -> **Integrations**.
 
 Configuration of Netatmo public weather stations is offered from the front end. Enter the Netatmo integration and press the cogwheel.
 
-In the dialogue, it is possible to create, edit and remove public weather sensors. For each area a unique name has to be set along with an area to be covered and whether to display average or maximum values.
+In the dialog, it is possible to create, edit and remove public weather sensors. For each area a unique name has to be set along with an area to be covered and whether to display average or maximum values.
 
 To edit an existing area simply enter its name and follow the dialog. 
 

source/_integrations/opengarage.markdown

@@ -79,6 +79,8 @@ covers:
   <img src='{{site_root}}/images/integrations/opengarage/cover_opengarage_details.jpg' />
 </p>
 
+{% raw %}
+
 ```yaml
 # Related configuration.yaml entry
 cover:
@@ -94,7 +96,7 @@ sensor:
   sensors:
     garage_status:
       friendly_name: 'Honda Door Status'
-      value_template: {% raw %}'{% if states.cover.honda %}
+      value_template: '{% if states.cover.honda %}
           {% if states.cover.honda.attributes["door_state"] == "open" %}
             Open
           {% elif states.cover.honda.attributes["door_state"] == "closed" %}
@@ -108,21 +110,30 @@ sensor:
           {% endif %}
           {% else %}
           n/a
-          {% endif %}'{% endraw %}
-    garage_car_present:
-      friendly_name: 'Honda in Garage'
-      value_template: {% raw %}'{% if states.cover.honda %}
-          {% if is_state("cover.honda", "open") %}
-            n/a
-          {% elif ((states.cover.honda.attributes["distance_sensor"] > 40) and (states.cover.honda.attributes["distance_sensor"] < 100)) %}
-            Yes
-          {% else %}
-            No
-          {% endif %}
-          {% else %}
-          n/a
           {% endif %}'
 
+binary_sensor:
+  platform: template
+  sensors:
+    honda_in_garage:
+      friendly_name: "Honda In Garage"
+      value_template: "{{ state_attr('cover.honda', 'distance_sensor') < 100 }}"
+      availability_template: >-
+        {% if is_state('cover.honda','closed') %}
+          true
+        {% else %}
+          unavailable
+        {% endif %}
+      icon_template: >-
+        {% if is_state('binary_sensor.honda_in_garage','on') %}
+          mdi:car
+        {% else %}
+          mdi:car-arrow-right
+        {% endif %}
+      unique_id: binary_sensor.honda_in_garage
+      delay_on: 5
+      delay_off: 5
+
 group:
   garage:
     name: Garage
@@ -135,8 +146,6 @@ customize:
   cover.honda:
     friendly_name: Honda
     entity_picture: /local/honda.gif
-  sensor.garage_car_present:
-    icon: mdi:car
 ```
 
 {% endraw %}

source/_integrations/otp.markdown

@@ -3,6 +3,7 @@ title: One-Time Password (OTP)
 description: Instructions on how to add One-Time Password (OTP) sensors into Home Assistant.
 ha_category:
   - Utility
+  - Sensor
 ha_iot_class: Local Polling
 ha_release: 0.49
 ha_quality_scale: internal

source/_integrations/panasonic_viera.markdown

@@ -98,6 +98,7 @@ script:
 
 - TC-P50ST50
 - TC-P55ST50
+- TC-P60ST50 (can't power on)
 - TC-P60S60
 - TC-P65VT30
 - TX-32AS520E

source/_integrations/season.markdown

@@ -3,6 +3,7 @@ title: Season
 description: Instructions on how to add season sensors into Home Assistant.
 ha_category:
   - Utility
+  - Sensor
 ha_iot_class: Local Polling
 ha_release: 0.53
 ha_quality_scale: internal

source/_integrations/sensor.command_line.markdown

@@ -3,6 +3,7 @@ title: "Command line Sensor"
 description: "Instructions on how to integrate command line sensors into Home Assistant."
 ha_category:
   - Utility
+  - Sensor
 ha_release: pre 0.7
 ha_iot_class: Local Polling
 ha_domain: command_line

source/_integrations/sensor.websocket_api.markdown

@@ -4,6 +4,7 @@ description: "Instructions on how to count connected clients within Home Assista
 logo: home-assistant.png
 ha_category:
   - Utility
+  - Sensor
 ha_release: 0.33
 ha_iot_class: Local Push
 ha_quality_scale: internal

source/_integrations/simulated.markdown

@@ -3,6 +3,7 @@ title: Simulated
 description: Component for simulating a numerical sensor.
 ha_category:
   - Utility
+  - Sensor
 ha_iot_class: Local Polling
 ha_release: 0.65
 ha_quality_scale: internal

source/_integrations/sms.markdown

@@ -77,6 +77,7 @@ You will need a USB GSM stick modem.
 - [Huawei E3372-510](https://www.amazon.com/gp/product/B01N6P3HI2/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1)(
 Need to unlock it using [this guide](http://blog.asiantuntijakaveri.fi/2015/07/convert-huawei-e3372h-153-from.html))
 - [Huawei E3531](https://www.amazon.com/Modem-Huawei-Unlocked-Caribbean-Desbloqueado/dp/B011YZZ6Q2/ref=sr_1_1?keywords=Huawei+E3531&qid=1581447800&sr=8-1)
+- [Huawei E3272](https://www.amazon.com/Huawei-E3272s-506-Unlocked-Americas-Europe/dp/B00HBL51OQ)
 
 [List of modems that may work](https://www.asus.com/event/networks_3G4G_support/)
 
@@ -84,6 +85,8 @@ Need to unlock it using [this guide](http://blog.asiantuntijakaveri.fi/2015/07/c
 
 For some unknown reason, the rule that converts these modems from storage devices into serial devices does not run automatically. To work around this problem, follow the procedure to create `udev` rule on a configuration USB stick for the device to switch to serial mode.
 
+0. Try disable virtual cd-rom and change work mode "only modem". After this modem correct work on Raspberry Pi without 'udev' rule.
+
 1. Run `lsusb`, its output looks like this:
 
 ```bash

source/_integrations/snmp.markdown

@@ -11,7 +11,7 @@ ha_release: 0.57
 ha_domain: snmp
 ---
 
-A lot of Wi-Fi access points and Wi-Fi routers support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/manageing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of instances and metrics, like network interfaces, disks and Wi-Fi registrations.
+A lot of Wi-Fi access points and Wi-Fi routers support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/managing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of instances and metrics, like network interfaces, disks and Wi-Fi registrations.
 
 There is currently support for the following device types within Home Assistant:
 

source/_integrations/spaceapi.markdown

@@ -9,7 +9,7 @@ ha_codeowners:
 ha_domain: spaceapi
 ---
 
-The `spaceapi` integration allow Hackerspaces to expose information to web apps or any other application with the [SpaceAPI](http://spaceapi.net/).
+The `spaceapi` integration allow Hackerspaces to expose information to web apps or any other application with the [SpaceAPI](https://spaceapi.io/).
 
 ## Configuration
 

source/_integrations/sql.markdown

@@ -3,6 +3,7 @@ title: SQL
 description: Instructions how to integrate SQL sensors into Home Assistant.
 ha_category:
   - Utility
+  - Sensor
 ha_release: 0.63
 ha_codeowners:
   - '@dgomes'
@@ -16,7 +17,7 @@ This can be used to present statistics about Home Assistant sensors if used with
 
 To configure this sensor, you need to define the sensor connection variables and a list of queries to your `configuration.yaml` file. A sensor will be created for each query:
 
-To enable it, add the following lines to your `configuration.yaml`:
+To enable it, add the following lines to your `configuration.yaml` file:
 
 {% raw %}
 ```yaml
@@ -108,7 +109,7 @@ SELECT * FROM states WHERE entity_id = 'binary_sensor.xyz789' GROUP BY state ORD
 
 ### Database size
 
-#### Database size in Postgres
+#### Postgres
 
 {% raw %}
 ```yaml
@@ -139,3 +140,19 @@ sensor:
         unit_of_measurement: kB
 ```
 {% endraw %}
+
+#### SQLite
+
+If you are using the `recorder` integration then you don't need to specify the location of the database. For all other cases, add `db_url: sqlite:////path/to/database.db`.
+
+{% raw %}
+```yaml
+sensor:
+  - platform: sql
+    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'
+```
+{% endraw %}

source/_integrations/statistics.markdown

@@ -3,6 +3,7 @@ title: Statistics
 description: Instructions on how to integrate statistical sensors into Home Assistant.
 ha_category:
   - Utility
+  - Sensor
 ha_iot_class: Local Polling
 ha_release: '0.30'
 ha_quality_scale: internal

source/_integrations/threshold.markdown

@@ -3,6 +3,7 @@ title: Threshold
 description: Instructions on how to integrate threshold binary sensors into Home Assistant.
 ha_category:
   - Utility
+  - Binary Sensor
 ha_iot_class: Local Polling
 ha_release: 0.34
 ha_quality_scale: internal

source/_integrations/travisci.markdown

@@ -33,7 +33,7 @@ sensor:
 
 {% configuration %}
 api_key:
-  description: The acces token for GitHub.
+  description: The access token for GitHub.
   required: true
   type: string
 branch:

source/_integrations/trend.markdown

@@ -3,6 +3,7 @@ title: Trend
 description: Instructions on how to integrate Trend binary sensors into Home Assistant.
 ha_category:
   - Utility
+  - Binary Sensor
 ha_release: 0.28
 ha_iot_class: Local Push
 ha_quality_scale: internal

source/_integrations/uptime.markdown

@@ -3,6 +3,7 @@ title: Uptime
 description: Instructions on how to integrate an uptime sensor into Home Assistant.
 ha_category:
   - Utility
+  - Sensor
 ha_iot_class: Local Push
 ha_release: 0.56
 ha_quality_scale: internal

source/_integrations/version.markdown

@@ -3,6 +3,7 @@ title: Version
 description: Instructions on how to integrate a version sensor into Home Assistant.
 ha_category:
   - Utility
+  - Sensor
 ha_iot_class: Local Push
 ha_release: 0.52
 ha_quality_scale: internal

source/_integrations/vlc_telnet.markdown

@@ -48,6 +48,10 @@ Only the "music" media type is supported for now.
 This service will control any instance of VLC player on the network with the telnet interface activated. 
 To activate the telnet interface on your VLC Player please read the [official VLC documentation](https://wiki.videolan.org/Documentation:Modules/telnet/). Also remember to add a firewall rule allowing inbound connections for the port used in the device running VLC.
 
+In case the VLC is running on a host with a locale other than English, you may get some errors during the volume change.
+This is related to the different use of the decimal separator in other countries.
+Consider to set the locale to `en_US` before starting VLC.
+
 ## Full configuration
 
 A full configuration for VLC could look like the one below:

source/_integrations/workday.markdown

@@ -3,6 +3,7 @@ title: Workday
 description: Steps to configure the binary workday sensor.
 ha_category:
   - Utility
+  - Binary Sensor
 ha_iot_class: Local Polling
 ha_release: 0.41
 ha_quality_scale: internal

source/_integrations/yeelight.markdown

@@ -137,6 +137,7 @@ This integration is tested to work with the following models. If you have a diff
 | `color1`   | YLDP02YL     | LED Bulb (Color)                                 |
 | `color1`   | YLDP03YL     | LED Bulb (Color) - E26                           |
 | `color2`   | YLDP06YL     | LED Bulb (Color) - 2nd generation                |
+| `color4`   | YLDP13YL     | LED Bulb 1S (Color)                              |
 | `strip1`   | YLDD01YL     | Lightstrip (Color)                               |
 | `strip1`   | YLDD02YL     | Lightstrip (Color)                               |
 | ?          | YLDD04YL     | Lightstrip (Color)                               |

source/_integrations/zha.markdown

@@ -59,6 +59,7 @@ ZHA integration uses a hardware independent Zigbee stack implementation with mod
   - [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/)
   - [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs_usb_adapter.html)
   - [Elelabs Zigbee Raspberry Pi Shield](https://elelabs.com/products/elelabs_zigbee_shield.html)
+  - Bitron Video/Smabit BV AV2010/10 USB-Stick with Silicon Labs Ember 3587 (no flashing necessary)
   - Telegesis ETRX357USB (Note! This first have to be flashed with other EmberZNet firmware)
   - Telegesis ETRX357USB-LRS (Note! This first have to be flashed with other EmberZNet firmware)
   - Telegesis ETRX357USB-LRS+8M (Note! This first have to be flashed with other EmberZNet firmware)

source/_lovelace/entities.markdown

@@ -223,8 +223,8 @@ type:
 style:
   required: false
   description: Style the element using CSS.
-  type: string
-  default: "height: 1px, background-color: var(--secondary-text-color)"
+  type: map
+  default: "height: 1px, background-color: var(--divider-color)"
 {% endconfiguration %}
 
 ### Section

source/_posts/2020-08-12-release-114.markdown

@@ -610,6 +610,45 @@ the automation is turned off.
 [recorder docs]: /integrations/recorder/
 [samsungtv docs]: /integrations/samsungtv/
 
+## Release 0.114.3 - August 20
+
+- Update zeroconf to fix ServiceBrowser leak on cancelation ([@bdraco] - [#38933]) ([zeroconf docs])
+- Bump netdisco to 2.8.2 to accomodate new zeroconf exception ([@bdraco] - [#38949]) ([discovery docs]) ([ssdp docs])
+- Fix Control4 light setup issues ([@lawtancool] - [#38952]) ([control4 docs])
+- Bump pychromecast to 7.2.1 ([@emontnemery] - [#39018]) ([cast docs])
+- Fix emulated hue on/off devices compatibility with alexa ([@bdraco] - [#39063]) ([emulated_hue docs])
+- Update met.no library ([@Danielhiversen] - [#39076]) ([met docs]) ([norway_air docs])
+
+[#38933]: https://github.com/home-assistant/core/pull/38933
+[#38949]: https://github.com/home-assistant/core/pull/38949
+[#38952]: https://github.com/home-assistant/core/pull/38952
+[#39018]: https://github.com/home-assistant/core/pull/39018
+[#39063]: https://github.com/home-assistant/core/pull/39063
+[#39076]: https://github.com/home-assistant/core/pull/39076
+[@danielhiversen]: https://github.com/Danielhiversen
+[@bdraco]: https://github.com/bdraco
+[@emontnemery]: https://github.com/emontnemery
+[@lawtancool]: https://github.com/lawtancool
+[cast docs]: /integrations/cast/
+[control4 docs]: /integrations/control4/
+[discovery docs]: /integrations/discovery/
+[emulated_hue docs]: /integrations/emulated_hue/
+[met docs]: /integrations/met/
+[norway_air docs]: /integrations/norway_air/
+[ssdp docs]: /integrations/ssdp/
+[zeroconf docs]: /integrations/zeroconf/
+
+## Release 0.114.4 - August 26
+
+- Fix TTS languange characters ([@pvizeli] - [#39211]) ([tts docs])
+- Fix time pattern listener firing a few microseconds early ([@bdraco] - [#39281])
+
+[#39211]: https://github.com/home-assistant/core/pull/39211
+[#39281]: https://github.com/home-assistant/core/pull/39281
+[@bdraco]: https://github.com/bdraco
+[@pvizeli]: https://github.com/pvizeli
+[tts docs]: /integrations/tts/
+
 ## All changes
 
 <details>

source/_posts/2020-08-28-android-230-release.markdown

@@ -0,0 +1,91 @@
+---
+title: "Home Assistant Companion Android App: New Features"
+description: "What's new with the Home Assistant Companion Android App in 2.3.0"
+date: 2020-08-28 00:00:00
+date_formatted: "August 28, 2020"
+comments: true
+author: Daniel Shokouhi
+categories: Release-Notes
+og_image: /images/blog/2020-08-28-android-230-release/Companion.png
+---
+
+Hey there, its been so long since we last gave an update on our mobile apps we thought it would be time to give you more updates! This time around we will focus on whats new in the Android app. There have been a few releases so were going to cover everything new up until version 2.3.0 which was just released to the Google Play Store.
+
+## Manage Sensors
+
+Starting from version 2.2.0 there is a new Manage Sensors screen that you can find under App Configuration. Users can now disable sensors they don't want while continuing to receive updates from the sensors they do care about. This includes turning off the Geocoded sensor while keeping location tracking on. Speaking of which the 2 location toggles that used to be found in App Configuration are now located in this new screen. You can expect to see the live data that was recently sent over to your Home Assistant server as well as the attributes and other sensor details.
+
+<p class='img'>
+<img src='/images/blog/2020-08-28-android-230-release/manage_sensors.png' alt='Screenshot of Manage Sensors'></a>
+Screenshot of the Manage Sensors.
+</p>
+
+<p class='img'>
+<img src='/images/blog/2020-08-28-android-230-release/sensor_management.png' alt='Screenshot of Sensor Management'></a>
+Screenshot of Sensor Management.
+</p>
+
+## New Sensors
+
+We have had quite a bit of sensors get added since we last spoke so here's whats new. Some of these sensors will update their state in your Home Assistant server upon certain state changes. All of the sensors listed below will also update during the normal 15 minute update interval. To get more details about what to expect from each sensor check out the [docs](https://companion.home-assistant.io/docs/core/sensors).
+
+Available for Google Play Store version only:
+
+* Activity
+
+Available for all users:
+
+* Audio
+* Bluetooth
+* Do Not Disturb
+* Last Reboot
+* Light
+* Phone
+* Pressure
+* Proximity
+* Next Alarm
+* Sim 1 & 2
+* Steps
+* Storage
+
+## Sensor Enhancements
+
+In addition to all the new sensors mentioned above we also had some improvements to our existing set of sensors. The battery state sensor now includes the battery health as a attribute and will also issue a second update call a few seconds after being plugged in so the state can update faster. The WiFi connection sensor was also updated so the state and certain attributes will update upon any network detected change. This state change also means that if you have multiple access points you will be able to see the device switching in real time.
+
+## NFC
+
+The app now supports reading and writing to NFC tags so you can build automations off scanning the tag. Home Assistant Core 0.114+ is required for this feature. Keep in mind that certain phones will require you to have your phone unlocked before it can read the tag. More details about how it works in the [docs](https://companion.home-assistant.io/docs/integrations/universal-links).
+
+<p class='img'>
+<img src='/images/blog/2020-08-28-android-230-release/nfc.png' alt='Screenshot of NFC'></a>
+Screenshot of NFC.
+</p>
+
+## Template Widget
+
+A new widget was added to give the user full control over creating a template widget with just about any data they want! Users will see the template rendering in real time as they build it. I personally recommend to start building your templates on a desktop as it can feel a bit cumbersome on a phone or tablet. This widget will update every 15 minutes or when it is tapped.
+
+<p class='img'>
+<img src='/images/blog/2020-08-28-android-230-release/template_widget.png' alt='Screenshot of the Template Widget'></a>
+Screenshot of the Template Widget.
+</p>
+
+
+## Theming
+
+You can now set the theme of the app independently from the device theme. This is useful for users who like a dark theme on their device but use a light theme for Home Assistant. In addition to this change we also had a few more fixes around themes.
+
+<p class='img'>
+<img src='/images/blog/2020-08-28-android-230-release/app_theme.png' alt='Screenshot of App Theme selection'></a>
+Screenshot of App Theme selection.
+</p>
+
+## Additional Improvements
+
+* Support for H265 videos was added
+* Entity state widget was enhanced to allow for multiple attributes and a custom separator
+* Widgets were enhanced overall to allow material icons
+* Notifications can now use `:smiley:` like you can in Discord
+* Lots of fixes across the board
+
+Special thanks to [chriss158](https://github.com/chriss158), [colincachia](https://github.com/colincachia), [David-Development](https://github.com/David-Development), [JBassett](https://github.com/JBassett), [klejejs](https://github.com/klejejs), [noam148](https://github.com/noam148), [skynetua](https://github.com/skynetua) and [uvjustin](https://github.com/uvjustin) for all of your contributions. So keep them bug reports and feature requests [coming](https://github.com/home-assistant/android/issues/new/choose), we'll chat again soon!

source/getting-started/index.markdown

@@ -42,8 +42,8 @@ We will need a few things to get started with installing Home Assistant. The Ras
 
 ### Software requirements
 
-- Download and extract the Home Assistant image for [your device](/hassio/installation/)
-- Download [balenaEtcher] to write the image to an SD card
+- Download and extract the Home Assistant image for [your device](/hassio/installation/).
+- Download [balenaEtcher] to write the image to an SD card.
 
 [balenaEtcher]: https://www.balena.io/etcher