Merge branch 'current' into next

Gemfile.lock

@@ -19,7 +19,7 @@ GEM
       sass (>= 3.3.0, < 3.5)
     compass-import-once (1.0.5)
       sass (>= 3.2, < 3.5)
-    concurrent-ruby (1.1.6)
+    concurrent-ruby (1.1.7)
     em-websocket (0.5.1)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0.6.0)

source/.well-known/apple-app-site-association

@@ -6,6 +6,8 @@
         "appID": "UTQFCBPQRF.io.robbie.HomeAssistant.dev",
         "paths": [
           "/ios/*",
+          "NOT /ios/beta",
+          "NOT /ios/beta/*",
           "/tag/*"
         ]
       },
@@ -13,6 +15,8 @@
         "appID": "UTQFCBPQRF.io.robbie.HomeAssistant.beta",
         "paths": [
           "/ios/*",
+          "NOT /ios/beta",
+          "NOT /ios/beta/*",
           "/tag/*"
         ]
       },
@@ -20,6 +24,8 @@
         "appID": "UTQFCBPQRF.io.robbie.HomeAssistant",
         "paths": [
           "/ios/*",
+          "NOT /ios/beta",
+          "NOT /ios/beta/*",
           "/tag/*"
         ]
       },
@@ -27,6 +33,8 @@
         "appID": "QMQYCKL255.io.robbie.HomeAssistant.dev",
         "paths": [
           "/ios/*",
+          "NOT /ios/beta",
+          "NOT /ios/beta/*",
           "/tag/*"
         ]
       },
@@ -34,6 +42,8 @@
         "appID": "QMQYCKL255.io.robbie.HomeAssistant.beta",
         "paths": [
           "/ios/*",
+          "NOT /ios/beta",
+          "NOT /ios/beta/*",
           "/tag/*"
         ]
       },
@@ -41,6 +51,8 @@
         "appID": "QMQYCKL255.io.robbie.HomeAssistant",
         "paths": [
           "/ios/*",
+          "NOT /ios/beta",
+          "NOT /ios/beta/*",
           "/tag/*"
         ]
       }

source/.well-known/assetlinks.json

@@ -0,0 +1,38 @@
+[
+  {
+    "relation": ["delegate_permission/common.handle_all_urls"],
+    "target": {
+      "namespace": "android_app",
+      "package_name": "io.homeassistant.companion.android",
+      "sha256_cert_fingerprints":
+      ["11:19:4B:A8:09:B4:2D:DF:0E:1A:7D:EC:68:42:A5:9C:7F:F1:11:9C:54:82:E9:5F:EB:FF:D5:C6:01:4D:AA:5A"]
+    }
+  },
+  {
+    "relation": ["delegate_permission/common.handle_all_urls"],
+    "target": {
+      "namespace": "android_app",
+      "package_name": "io.homeassistant.companion.android.debug",
+      "sha256_cert_fingerprints":
+      ["11:19:4B:A8:09:B4:2D:DF:0E:1A:7D:EC:68:42:A5:9C:7F:F1:11:9C:54:82:E9:5F:EB:FF:D5:C6:01:4D:AA:5A"]
+    }
+  },
+  {
+    "relation": ["delegate_permission/common.handle_all_urls"],
+    "target": {
+      "namespace": "android_app",
+      "package_name": "io.homeassistant.companion.android.minimal",
+      "sha256_cert_fingerprints":
+      ["11:19:4B:A8:09:B4:2D:DF:0E:1A:7D:EC:68:42:A5:9C:7F:F1:11:9C:54:82:E9:5F:EB:FF:D5:C6:01:4D:AA:5A"]
+    }
+  },
+  {
+    "relation": ["delegate_permission/common.handle_all_urls"],
+    "target": {
+      "namespace": "android_app",
+      "package_name": "io.homeassistant.companion.android.minimal.debug",
+      "sha256_cert_fingerprints":
+      ["11:19:4B:A8:09:B4:2D:DF:0E:1A:7D:EC:68:42:A5:9C:7F:F1:11:9C:54:82:E9:5F:EB:FF:D5:C6:01:4D:AA:5A"]
+    }
+  }
+]

source/_docs/configuration/customizing-devices.markdown

@@ -40,7 +40,7 @@ entity_picture:
   required: false
   type: string
 icon:
-  description: "Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com) ([Cheatsheet](https://cdn.materialdesignicons.com/4.5.95/)). Prefix name with `mdi:`, ie `mdi:home`. Note: Newer icons may not yet be available in the current Home Assistant release. You can check when an icon was added to MaterialDesignIcons.com at [MDI History](https://materialdesignicons.com/history)."
+  description: "Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com) ([Cheatsheet](https://cdn.materialdesignicons.com/5.3.45/)). Prefix name with `mdi:`, ie `mdi:home`. Note: Newer icons may not yet be available in the current Home Assistant release. You can check when an icon was added to MaterialDesignIcons.com at [MDI History](https://materialdesignicons.com/history)."
   required: false
   type: string
 assumed_state:

source/_docs/mqtt/service.markdown

@@ -28,7 +28,7 @@ payload: on
 {% raw %}
 ```yaml
 topic: home-assistant/light/1/state
-payload_template: {{ states('device_tracker.paulus') }}
+payload_template: "{{ states('device_tracker.paulus') }}"
 ```
 {% endraw %}
 

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

@@ -1444,8 +1444,8 @@ The configuration parameters will have to be added to the `zwcfg` file. Replace
     <Item label="Disabled" value="0"/>
     <Item label="Enabled (default)" value="1"/>
   </Value>
-  <Value type="byte" genre="config" index="3" label="Motion Sensativity" size="1" min="1" max="10" value="10">
+  <Value type="byte" genre="config" index="3" label="Motion Sensitivity" size="1" min="1" max="10" value="10">
-    <Help>Adjust motion sensitivity where 10 is the most sensative setting.
+    <Help>Adjust motion sensitivity where 10 is the most sensitive setting.
     default: 10
     </Help>
   </Value>

source/_integrations/binary_sensor.mqtt.markdown

@@ -92,7 +92,7 @@ device_class:
   required: false
   type: string
 expire_after:
-  description: "Defines the number of seconds after the sensor's state expires if it's not updated. After expiry, the sensor's state becomes `unavailable` if any `availability` topic is defined and `unknown` otherwise."
+  description: Defines the number of seconds after the sensor's state expires, if it's not updated. After expiry, the sensor's state becomes `unavailable`.
   required: false
   type: integer
 force_update:
@@ -160,14 +160,17 @@ value_template:
 
 In this section, you will find some real-life examples of how to use this sensor.
 
-### Full configuration
+### Full configuration with JSON data
 
+This is an example of a configuration where the state is extracted from a JSON formatted MQTT message.
 To test, you can use the command line tool `mosquitto_pub` shipped with `mosquitto` or the `mosquitto-clients` package to send MQTT messages.
 
 To set the state of the binary sensor manually:
 
 ```bash
-mosquitto_pub -h 127.0.0.1 -t home-assistant/window/contact -m "OFF"
+mosquitto_pub -h 127.0.0.1 -t home-assistant/window/availability -m "online"
+mosquitto_pub -h 127.0.0.1 -t home-assistant/window/contact -m '{"state":"ON"}'
+mosquitto_pub -h 127.0.0.1 -t home-assistant/window/contact -m '{"state":"OFF"}'
 ```
 
 The example below shows a full configuration for a binary sensor:
@@ -181,14 +184,13 @@ binary_sensor:
     name: "Window Contact Sensor"
     state_topic: "home-assistant/window/contact"
     payload_on: "ON"
-    payload_off: "OFF"
     availability:
       - topic: "home-assistant/window/availability"
         payload_available: "online"
         payload_not_available: "offline"
     qos: 0
     device_class: opening
-    value_template: '{{ value.x }}'
+    value_template: '{{ value_json.state }}'
 ```
 
 {% endraw %}

source/_integrations/bom.markdown

@@ -206,8 +206,8 @@ sensor:
 To get the station ID for any BOM station:
 - Find your station on these maps: [NSW](http://www.bom.gov.au/nsw/observations/map.shtml), [QLD](http://www.bom.gov.au/qld/observations/map.shtml), [VIC](http://www.bom.gov.au/vic/observations/map.shtml), [WA](http://www.bom.gov.au/wa/observations/map.shtml), [SA](http://www.bom.gov.au/sa/observations/map.shtml), [TAS](http://www.bom.gov.au/tas/observations/map.shtml), [ACT](http://www.bom.gov.au/act/observations/canberramap.shtml), [NT](http://www.bom.gov.au/nt/observations/map.shtml).
  - alternatively, from the [BOM website](http://www.bom.gov.au/), navigate to State -> Observations -> Latest Observations -> Choose the station.
-- The URL will look like `http://www.bom.gov.au/products/IDx60801/[station].shtml`
+- The URL will look like `http://www.bom.gov.au/products/IDx60901/[station].shtml`
-- For Adelaide, the URL will look like `http://www.bom.gov.au/products/IDS60801/IDS60801.94675.shtml`; the station ID is `IDS60801.94675`.
+- For Adelaide, the URL will look like `http://www.bom.gov.au/products/IDS60901/IDS60901.94648.shtml`; the station ID is `IDS60901.94648`.
 
 {% configuration %}
 station:

source/_integrations/bond.markdown

@@ -17,7 +17,7 @@ ha_config_flow: true
 
 The Bond integration allows you to control appliances through your [Bond Bridge](https://bondhome.io/). Duplicates your RF remote control.
 
-Supported devices:
+Supported devices (see Requirements section below):
 
 - Ceiling fans
 - Shades
@@ -31,3 +31,9 @@ Menu: **Configuration** -> **Integrations**.
 
 Click on the `+` sign to add an integration and click on **Bond** (use typeahead if necessary).
 After completing the configuration flow, the Bond integration will be available.
+
+## Requirements
+
+This integration supports Bond bridges with firmware v2.10.x and up.
+Bond bridges with firmware v2.9.x and lower will **not** work correctly. Please
+upgrade your firmware from Bond app before adding this integration.

source/_integrations/emulated_hue.markdown

@@ -41,6 +41,12 @@ If you added or upgraded to a newer Alexa device and devices are not found, you
 
 </div>
 
+<div class='note'>
+  
+Logitech Harmony remotes cannot connect to this emulator via Android and iOS mobile applications because they require the physical button on the hub to be pressed. The [MyHarmony desktop software](https://support.myharmony.com/en-us/download) must be used with the original cable to connect it.
+  
+</div>
+
 ### Configuration
 
 To enable the emulated Hue bridge, add one of the following configs to your `configuration.yaml` file:

source/_integrations/http.markdown

@@ -43,7 +43,7 @@ server_port:
   type: integer
   default: 8123
 ssl_certificate:
-  description: Path to your TLS/SSL certificate to serve Home Assistant over a secure connection.
+  description: Path to your TLS/SSL certificate to serve Home Assistant over a secure connection. If using the [Let's Encrypt add-on](https://github.com/home-assistant/hassio-addons/tree/master/letsencrypt) this will be at `/ssl/fullchain.pem`.
   required: false
   type: string
 ssl_peer_certificate:
@@ -51,7 +51,7 @@ ssl_peer_certificate:
   required: false
   type: string
 ssl_key:
-  description: Path to your TLS/SSL key to serve Home Assistant over a secure connection.
+  description: Path to your TLS/SSL key to serve Home Assistant over a secure connection. If using the [Let's Encrypt add-on](https://github.com/home-assistant/hassio-addons/tree/master/letsencrypt) this will be at `/ssl/privkey.pem`.
   required: false
   type: string
 cors_allowed_origins:

source/_integrations/mitemp_bt.markdown

@@ -8,7 +8,7 @@ ha_iot_class: Local Polling
 ha_domain: mitemp_bt
 ---
 
-The `mitemp_bt` sensor platform allows one to monitor room temperature and humidity. The [Xiaomi Mijia BLE Temperature and Humidity sensor with LCD](https://www.amazon.com/Temperature-Humidity-Xiaomi-Bluetooth-Screen-Remote/dp/B079L6N6PC) is a small Bluetooth Low Energy device that monitors the room temperature and humidity. As only a single BLE device can be polled at the same time, the library employs locking to make sure this is the case.
+The `mitemp_bt` sensor platform allows one to monitor room temperature and humidity. The [Xiaomi Mijia BLE Temperature and Humidity sensor with LCD](https://www.banggood.com/Xiaomi-Mijia-Bluetooth-Thermometer-Hygrometer-with-LCD-Screen-Magnetic-Suction-Wall-Stickers-p-1232396.html) is a small Bluetooth Low Energy device that monitors the room temperature and humidity. As only a single BLE device can be polled at the same time, the library employs locking to make sure this is the case.
 
 ## Installation
 

source/_integrations/person.markdown

@@ -8,23 +8,23 @@ ha_quality_scale: internal
 ha_domain: person
 ---
 
-The person integration allows connecting [device tracker](/integrations/device_tracker/) entities to one or more person entities. The state updates of a connected device tracker will set the state of the person. When multiple device trackers are used, the state of person will be determined in this order:
+The `person` integration allows connecting [device tracker](/integrations/device_tracker/) entities to one or more person entities. The state updates of a connected device tracker will set the state of the person. When multiple device trackers are used, the state of person will be determined in this order:
 
-1. If there are stationary trackers (non-GPS trackers, i.e., a router or Bluetooth 'device_trackers') presenting the status 'home', the tracker most recently updated will be used.
+1. If there are stationary trackers (non-GPS trackers, e.g., a router or Bluetooth device tracker) presenting the status `home`, the tracker most recently updated will be used.
-2. If there are trackers of type 'gps', then the most recently updated tracker will be used.
+2. If there are trackers of type `gps`, then the most recently updated tracker will be used.
-3. Otherwise, the latest tracker with status 'not_home' will be used.
+3. Otherwise, the latest tracker with status `not_home` will be used.
 
-Let's say, for example, that you have 3 trackers: 'tracker_gps', 'tracker_router' and 'tracker_ble'.
+Let's say, for example, that you have three trackers: `tracker_gps`, `tracker_router` and `tracker_ble`.
 
-1. You're at home, all 3 devices show status 'home' - status of your Person entity will be 'home' with source 'tracker_router' or 'tracker_ble', whichever was most recently updated.
+1. You're at home, all three devices show status `home` - status of your Person entity will be `home` with source `tracker_router` or `tracker_ble`, whichever was most recently updated.
-2. You just left home. 'tracker_gps' shows status 'not_home', but the other two trackers show status 'home' (they may not have yet updated due to their 'consider_home' setting see [device_tracker](/integrations/device_tracker/#configuring-a-device_tracker-platform)). Since the stationary trackers have priority, you are considered 'home'.
+2. You just left home. `tracker_gps` shows status `not_home`, but the other two trackers show status `home` (they may not have yet updated due to their `consider_home` setting see [device_tracker](/integrations/device_tracker/#configuring-a-device_tracker-platform)). Since the stationary trackers have priority, you are considered `home`.
-3. After some time, both stationary trackers show status 'not_home'. Now your Person entity has status 'not_home' with source 'tracker_gps'.
+3. After some time, both stationary trackers show status `not_home`. Now your Person entity has status 'not_home' with source `tracker_gps`.
-4. While you are away from home, your Home Assistant is restarted. Until 'tracker_gps' receives an update, your status will be determined by the stationary trackers, since they will have the most recent update after a restart. Obviously, the status will be 'not_home'.
+4. While you are away from home, your Home Assistant instance is restarted. Until the `tracker_gps` receives an update, your status will be determined by the stationary trackers, since they will have the most recent update after a restart. Obviously, the status will be `not_home`.
-5. Then you're going into a zone you have defined as 'zone1', 'tracker_gps' sends an update, and now your status is 'zone1' with source 'tracker_gps'.
+5. Then you're going into a zone you have defined as `zone1`, `tracker_gps` sends an update, and now your status is `zone1` with source `tracker_gps`.
-6. You've returned home and your mobile device has connected to the router, but 'tracker_gps' hasn't updated yet. Your status will be 'home' with source 'tracker_router'.
+6. You've returned home and your mobile device has connected to the router, but `tracker_gps` hasn't updated yet. Your status will be `home` with source `tracker_router`.
-7. After the 'tracker_gps' update occurs, your status will still be 'home' with source 'tracker_router' or 'tracker_ble', whichever has the most recent update.
+7. After the `tracker_gps` update occurs, your status will still be `home` with source `tracker_router` or `tracker_ble`, whichever has the most recent update.
 
-TL;DR: When you're at home, your position is determined first by stationary trackers (if any) and then by GPS. When you're outside your home, your position is determined firstly by GPS and then by stationary trackers.
+In short, when you're at home, your position is determined first by stationary trackers (if any) and then by GPS. When you're outside your home, your position is determined firstly by GPS and then by stationary trackers.
 
 **Hint**: When you use multiple device trackers together, especially stationary and GPS trackers, it's advisable to set `consider_home` for stationary trackers as low as possible see [device_tracker](/integrations/device_tracker/#configuring-a-device_tracker-platform)).
 
@@ -40,7 +40,7 @@ person:
 
 ## Configuring the `person` integration via YAML
 
-If you prefer YAML, you can also configure your persons via `configuration.yaml`:
+If you prefer YAML, you can also configure your persons via the `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -61,11 +61,11 @@ person:
     required: true
     type: string
   user_id:
-    description: The user id of the Home Assistant user account for the person. *`user_id` (aka `ID`) of users can be inspected in the "Users"/"Manage users" screen in the configuration panel.*
+    description: The user ID of the Home Assistant user account for the person. `user_id` (aka `ID`) of users can be inspected in the "Users"/"Manage users" screen in the configuration panel.
     required: false
     type: string
   device_trackers:
-    description: A list of device tracker entity ids to track. These will represent the state of the person.
+    description: A list of device tracker entity IDs to track. These will represent the state of the person.
     required: false
     type: [string, list]
 {% endconfiguration %}

source/_integrations/sensor.mqtt.markdown

@@ -65,7 +65,7 @@ device_class:
   type: device_class
   default: None
 expire_after:
-  description: Defines the number of seconds after the value expires if it's not updated.
+  description: Defines the number of seconds after the sensor's state expires, if it's not updated. After expiry, the sensor's state becomes `unavailable`.
   required: false
   type: integer
   default: 0

source/_integrations/zha.markdown

@@ -71,11 +71,10 @@ ZHA integration uses a hardware independent Zigbee stack implementation with mod
 
 - Texas Instruments CC253x, CC26x2R, and CC13x2 based radios (via the [zigpy-cc](https://github.com/zigpy/zigpy-cc) library for zigpy)
   - [CC2531 USB stick hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
-  - [CC2530 + CC2591 USB stick hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
+  - [CC2530 + CC2591/CC2592 USB stick hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
-  - [CC2530 + CC2592 dev board hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
-  - [CC2652R dev board hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
-  - [CC1352P-2 dev board hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
   - [CC2538 + CC2592 dev board hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
+  - [CC2652P/CC2652R/CC2652RB USB stick or dev board hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/information/supported_adapters)
+  - [CC1352P/CC1352R USB stick or dev board hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/information/supported_adapters)
 - ZiGate based radios (via the [zigpy-zigate](https://github.com/zigpy/zigpy-zigate) library for zigpy and require firmware 3.1a or later)
   - [ZiGate USB-TTL](https://zigate.fr/produit/zigate-ttl/)
   - [ZiGate USB-DIN](https://zigate.fr/produit/zigate-usb-din/)

source/_posts/2020-08-05-mobile-apps-new-features.markdown

@@ -0,0 +1,141 @@
+---
+title: "Home Assistant Companion Apps: New and Upcoming Features"
+description: "What's new and what's in the works with the companion apps"
+date: 2020-08-05 00:00:00
+date_formatted: "August 5, 2020"
+comments: true
+author: Daniel Shokouhi & Tom Brien
+author_twitter: tbrien88
+categories: Release-Notes
+og_image: /images/blog/2020-08-05-mobile-apps-new-features/Companion-new-upcoming.png
+---
+
+Hi, it's been a while since we let you know about all the great things you can do with the Home Assistant Companion Apps for Android and iOS, so let's rectify that now as there are so many exciting updates. Before we get started on that though, iOS users should take a moment to read [this blog post](/blog/2020/07/28/ios-app-migration) which has some important information about a small change coming up.
+
+## A note on privacy
+
+Currently we use Google's Firebase notification service for sending notifications to your device and also for tracking crashes. We did this because of simplicity, due to how notifications work on iOS we can't use just any server to send notifications, in fact there is a pretty narrow choice. Using Firebase allowed us to keep costs low, which Nabu Casa then covered so people are able to use it at no cost. However, many people were uncomfortable about this and would prefer an app that did not rely on Google's servers. Well we hear you and we are actively looking at moving to other providers. While we have not completed this work yet, we just wanted to let you know it is something that is being actively developed and hopefully we will have more news very soon.
+
+## Android minimal app
+
+On a related note, we are delighted to say we now offer a way to install a minimal version of the Android app that is completely free of any reliance on Google. This version of the app does not have location tracking or notifications. We hope that by providing this version of the app more developers will be excited about contributing to the app in general. You can find the APK on the [release](https://github.com/home-assistant/android/releases) page up on GitHub starting from version 2.1.0.
+
+## What's New(ish)
+
+The short answer is lots! The Android and iOS apps are developed by separate teams so while the features are similar, they are not identical and do not follow a common road map. Android changes are up next, [click here to jump to the iOS update](#ios)
+
+### Android
+
+#### Notification Improvements
+
+Throughout the past few releases Android notifications were greatly improved with new features and fixes.
+
+Starting in 1.8.0 we enhanced our image notifications to allow for not only a relative path (i.e. storing in your [`www`](/integrations/http#hosting-files) folder) but you can also request a snapshot using the [Camera Proxy API](https://developers.home-assistant.io/docs/api/rest/#get-apicamera_proxycameraentity_id). All authentication is handled via the app so you don't need to worry about it. You can also use [click action](https://companion.home-assistant.io/docs/notifications/notifications-basic/#notification-click-actio) and [actionable notifications](https://companion.home-assistant.io/docs/notifications/actionable-notifications#building-automations-for-notification-actions) to navigate to a specific lovelace view.
+
+From 1.9.0 you can now create and remove [notification channels](https://companion.home-assistant.io/docs/notifications/notifications-basic#notification-channels) on the fly. This is helpful so you can create channels that can override your do not disturb settings, specifically for notifications like the alarm while notifications for your laundry can continue to let you be undisturbed.
+
+In 1.10.0 we further enhanced our notifications to allow for many new options. Users can now change the [LED Color](https://companion.home-assistant.io/docs/notifications/notifications-basic#notification-led-color), [vibration pattern](https://companion.home-assistant.io/docs/notifications/notifications-basic#notification-vibration-pattern) and [importance](https://companion.home-assistant.io/docs/notifications/notifications-basic#notification-channel-importance) of a message. These options can also be used with a channel to help set defaults to allow you to further distinguish between notifications. You can now [group](https://companion.home-assistant.io/docs/notifications/notifications-basic#thread-id-grouping-notifications) your notifications to help declutter the notification pull down. [Persistent notifications](https://companion.home-assistant.io/docs/notifications/notifications-basic#persistent-notification) were also introduced so you can't simply swipe away those important notifications, you can pair this with the [`sticky`](https://companion.home-assistant.io/docs/notifications/notifications-basic#sticky-notification) property so the notification does not disappear. The `message` now allows for [HTML formatting](https://companion.home-assistant.io/docs/notifications/notifications-basic#notification-message-html-formatting) so you can highlight the important parts. Users can also supply an [icon](https://companion.home-assistant.io/docs/notifications/notifications-basic#notification-icon) much like they can with an image.  For the unimportant notifications you can set a [timeout](https://companion.home-assistant.io/docs/notifications/notifications-basic#notification-timeout) so after x amount of seconds the notification is automatically dismissed.
+
+```yaml
+automation:
+  - alias: Alarm triggered
+    trigger:
+      platform: state
+      entity_id: alarm_control_panel.home
+      to: triggered
+    action:
+      service: notify.mobile_app_pixel_4_xl
+      data:
+        message: "Front alarm <b>triggered</b>"     # some HTML formatting to highlight the alert
+        data:
+          channel: Alarm             # creates a new channel called Alarm that you can manage from your device
+          importance: high           # set the channel importance to high
+          ledColor: red              # make the LED flash red for this notification
+          vibrationPattern: "100,30,100,30,100,30,200,30,200,30,200,30,100,30,100,30,100"     # SOS vibration pattern
+          persistent: true           # set to persistent
+          sticky: true               # make sure it doesn't dismiss if selected
+          clickAction: /lovelace/alarm    # navigate user to the lovelace alarm view
+          icon: /local/alarm.jpg     # relative path to the icon
+          color: red                 # set the color of the notification to red
+          group: alarm               # the group name to group together notifications
+          tag: alarm                 # tag is required in order to remove the persistent notification
+```
+
+
+In the above automation example a new channel with the name `Alarm` will be created with a default setting for vibration, LED and importance. This notification will also be persistent and part of a group and tag along with an icon amongst other changes.
+
+
+#### Sensors
+
+Starting with 1.8.0 we have introduced a new [Geocoded sensor](https://companion.home-assistant.io/docs/core/sensors#geocoded-location-sensor) that helps translate your GPS location to an actual street address.
+
+<p class='img'>
+<img src='/images/blog/2020-08-05-mobile-apps-new-features/geocoded_sensor.png' alt='Screenshot of the Geocoded Sensor'></a>
+Screenshot of the Geocoded Sensor.
+</p>
+
+The battery level sensor was split in 1.9.0 to include a [battery state sensor](https://companion.home-assistant.io/docs/core/sensors#battery-sensors) so you can see when your device is actively `charging`, `not_charging`, `discharging` and `full`. You can also distinguish whether its `wireless`, `ac` or `usb`. The state now updates immediately upon being plugged in and unplugged to allow for quicker automations.
+
+
+#### Biometrics
+
+Biometrics were introduced in 1.9.0 to allow the user to lock down the app when they are not using it. Upon launching the app you will see a lockscreen like below requesting for either your fingerprint or face to unlock the app. You can set this feature up by visiting the App Configuration screen inside the app.
+
+<p class='img'>
+<img src='/images/blog/2020-08-05-mobile-apps-new-features/biometric_unlock.png' alt='Screenshot of Biometric Unlock'></a>
+Screenshot of Biometric Unlock.
+</p>
+
+
+#### Additional Improvements
+
+We have also been hard at working making improvements in other areas of the app:
+
+* There are now 2 [widgets](https://companion.home-assistant.io/docs/core/android-widgets) that you can set up, with Entity State being the latest addition. The Entity State widget will display the state and any attribute of the selected entity. It will update once every 30 minutes or when tapped. The Service Call widget was also enhanced to allow you to select from a list of valid and available services along with the ability to add additional data fields that the service may require.
+* In App Configuration the Home Network WiFi SSID option now allows the user to select multiple SSIDs.
+* A Cookie Manager was added to our WebView that will allow you to save cookies from sites that you may use in the [webpage card](/lovelace/iframe/).
+* More descriptive SSL error messages were added to help users resolve local issues they may encounter while setting up the app.
+* Device ID is now sent with the event data for actionable notifications.
+
+### iOS
+
+Firstly, we should say a hello to Zac ([@zacwest](https://github.com/zacwest)) who has joined the iOS team and contributed a huge amount of code in the last couple of months. In fact, Zac has rewritten much of the underlying code of the app in that time, so while it may look much the same, behind the scenes it's almost a new app! Some features that are now in the iOS app are:
+
+#### Stability
+
+Making the app reliable and eliminating bugs was a big focus. You won’t have to pull-to-refresh as often, sensors update more reliably, and editing things like actions and notifications won’t accidentally delete them.
+
+Whether it is to turn on the lights when you get home at night, or send a someone a notification that you're leaving work and how long the journey should take, we know that this is what a lot of people use the app for the most and we also know the performance has not been 100 % and that changes in recent versions of iOS seem to have made this work. There have been a huge number of changes to work around these issues (unfortunately Apple's CoreLocation framework is something of a black box), we now sanity check the location data before sending it to Home Assistant, checking if the accuracy is acceptable or if an update from a minute ago has better accuracy. We also try and get a new update when accuracy is bad. While we still use significant location changes (such as changing cell tower) to wake the app up from the background, we now automatically discard the data they provide and attempt to get a higher accuracy GPS location.
+
+#### Empowering Notifications
+
+Notifications are some of the more powerful ways you can interact with the app, and they are now even more powerful. [Camera notifications](https://companion.home-assistant.io/docs/notifications/dynamic-content) will now stream via HTTP Live Streaming (HLS) instead of the older MJPEG standard when you have the `stream` integration enabled, giving you a more live experience; camera notifications also show up in the right aspect ratio; you can add per-action URLs that should be launched for each action of a notification; relative URLs (like `/lovelace-tacos/0`) will now open within the app without kicking you out to Safari.
+
+<p class='img'>
+<img src='/images/blog/2020-08-05-mobile-apps-new-features/ios-notification-examples.png' alt='Screenshot of new notification example triggers and service calls'></a>
+Screenshot of example triggers and service calls for notifications.
+</p>
+
+#### More frequent sensor updates while using the app
+
+A lot of people have asked for the sensors to be updated more frequently. The problem we have is while the app is in the background it is asleep as part of iOS's efforts to preserve battery. However, while you're using the app it should be able to send data frequently. You can now set a desired frequency of sensor updates while you have the app open. This can be as slow as every hour or as fast as every 20 seconds! Hopefully this will be a huge improvement for people using iPads as wall-mounted kiosks.
+
+#### No more duplicate integrations
+
+Previously when you removed and reinstalled the app you would get a new `..._2` integration in Home Assistant along with a new set of sensors like `sensor.freds_iphone_2`. This was a pain! Especially for our amazing beta testers who often went through the app's onboarding process several times in a day to check for bugs (THANK YOU!). Now the app registers its unique ID with Home Assistant, this means in most cases when you reinstall or reset up the app it should just pick and use the old integration and entities.
+
+#### Usability
+
+Another avenue of improvement is making things a bit easier. You’ll now find example triggers and service calls when configuring notification categories and actions within the app; theme color choices should always come through; you can adjust things like the zoom factor of the pages or how often sensors update if the app remains open; and more! You will definitely want to dig into the [releases](https://github.com/home-assistant/iOS/releases) or play around in the app’s settings.
+
+#### A look ahead at iOS 14
+
+Coming to iOS 14 is Widgets, and no doubt there’s some huge potential here. A good analogy for what they can do is to think of them as Apple Watch complications; relatively static displays that can be updated with a multitude of data. One thing we’d love is to get an idea of the information and displays you’re interested in seeing here as Widgets get built out over the next few months. Please let us know any ideas you have on [this thread](https://community.home-assistant.io/t/what-kind-of-ios-14-widgets-would-you-like-to-see).
+
+iOS 14 is also introducing [Local Push Connectivity](https://developer.apple.com/documentation/networkextension/local_push_connectivity), which adds support for push notifications on your local network that do not require a trip to the cloud. This, like Critical Alerts, requires explicit approval from Apple, but we’re hopeful about improving the experience with your boats and RVs!
+
+## That's it, almost
+
+Wow, thanks for reading all the way down here! Everything you've read about wouldn't be possible without a very dedicated team of volunteers. In addition to the highlights above, we’ve also fixed a good amount of bugs and made other improvements across the board. Thanks goes to [JBassett](https://github.com/JBassett), [KBerstene](https://github.com/KBerstene), [chriss158](https://github.com/chriss158), [timmmeeeh](https://github.com/timmmeeeh), [timmoo001](https://github.com/timmoo001), [craftykoala](https://github.com/craftykoala), [jeroenseegers](https://github.com/jeroenseegers), [yoxjames](https://github.com/yoxjames), and [neopilou](https://github.com/neopilou) on the Android side and [robbiet480](https://www.github.com/robbiet480) and [zacwest](https://www.github.com/zacwest) on iOS.
+
+Two last things, firstly a reminder that you can find our complete docs for the apps on [their own site](https://companion.home-assistant.io). Secondly, as you're the kind of person that reads whole blog posts (well done again!) you might be the perfect beta tester for our apps, if you think you could help out, you can sign up for the Android app [here](https://play.google.com/apps/testing/io.homeassistant.companion.android) or the iOS app [here](https://companion.home-assistant.io/app/ios/beta).

source/addons/index.html

@@ -22,9 +22,9 @@ regenerate: false
 
 <p>
   To install add-ons, navigate to the Supervisor panel in your Home Assistant
-    frontend, and click on the "ADD-ON STORE" tab. All add-ons, including their documentation, are available right from the store.
+    frontend, and click on the "Add-on store" tab. All add-ons, including their documentation, are available right from the store.
     Some advanced add-ons will only be visible after you opt-in to "Advanced Mode" which can be changed on your user profile page.
-    Click on a add-on you are interested in, to read the documentation or to install the add-on.
+    Click on an add-on you are interested in, to read the documentation or to install the add-on.
 </p>
 
 <p class="note">

source/hassio/enable_i2c.markdown

@@ -1,12 +1,11 @@
 ---
-title: "Enable i2c on the Home Assistant Operating System"
+title: "Enable I2C on the Home Assistant Operating System"
 description: "Instructions on how to enable I2C on a Raspberry PI"
 ---
 
-Home Assistant using the Home Assistant Operating System, is a managed environment.
+Home Assistant using the Home Assistant Operating System is a managed environment, which means you can't use existing methods to enable the I2C bus on a Raspberry Pi.
-Which means you can't use existing methods to enable the I2C bus on a Raspberry Pi.
 
-If you're attempting to add an external sensor, you will have to [enable the I2C interface in the Home Assistant configuration](https://github.com/home-assistant/hassos/blob/dev/Documentation/boards/raspberrypi.md#i2c) using a USB stick.
+If you're attempting to add an external sensor you will have to [enable the I2C interface in the Home Assistant configuration](https://github.com/home-assistant/hassos/blob/dev/Documentation/boards/raspberrypi.md#i2c) using a USB stick.
 
 ## Step by step instructions
 

source/hassio/hassos_faq.markdown

@@ -6,7 +6,7 @@ description: "Frequently Asked Questions for Home Assistant OS"
 
 The bootloader for Home Assistant OS (uboot) does not yet support Pi4 booting from USB. Support is likely a month or two away as of July 2020.
 
-The Pi4, with 8GB RAM, is similarly waiting for support from upstream.
+The Pi4 with 8GB RAM is similarly waiting for support from upstream.
 
 ## How do I run a specific version of Home Assistant?
 
@@ -37,12 +37,12 @@ No. The USB "CONFIG" stick is only used to import a network profile to `/etc/Net
 
 This error indicates the image, whether for updating to Home Assistant or installing or updating an add-on, was not able to be pulled to your system. This is usually a situation where there is not enough space for the image to be downloaded. The first thing to check for is the available space on your system.
 
-Please note, if you are running the operating system as a virtual machine; the default VM image is only about 6GB. Many VM users run into this as they have not allocated enough storage. 32 GB is the minimum recommended size.
+Please note, if you are running the operating system as a virtual machine; the default VM image is only about 6GB. Many VM users run into this as they have not allocated enough storage. 32GB is the minimum recommended size.
 
-You'll need to explore your own system to determine where space has gone.
+You will need to explore your own system to determine where space has gone.
 Using `df -h` in the SSH add-on console to you can quickly check to see if you have space available.
 
-If there is plenty of space available then you might check to see if you are having network issues that are preventing images being downloaded.
+If there is plenty of space available then you might check to see if you are having network issues that are preventing images from being downloaded.
 
 ## Why does the start button for an add-on flash red when I click it?
 
@@ -53,6 +53,6 @@ The logs on this page are the same you would see using `ha logs` in the custom C
 ## I'm trying to find my files on the host or SD card. Where are they?
 
 On a Home Assistant OS install, your files are on the data partition within `/mnt/data/supervisor/`.
-On the SD itself, this is an EXT4 partition labeled `hassos-data`
+On the SD itself, this is an EXT4 partition labeled `hassos-data`.
 
 On a Supervised install, they are in `/usr/share/hassio/`.

source/hassio/installation.markdown

@@ -33,10 +33,10 @@ The following will take you through the steps required to install Home Assistant
 
    - Flash the downloaded image to an SD card using [balenaEtcher][balenaEtcher]. If using a Pi, we recommend at least a 32 GB SD card to avoid running out of space.
    - Load the appliance image into your virtual machine software. (Note: You are free to assign as much resources as you wish to the VM, please assign enough based on your add-on needs)
-     - For VirtualBox create a new virtual machine, select "Other Linux (64Bit), assign it atleast 2 GB of memory and "Use an existing virtual hard disk file", select the VDI file from above, afterwards edit the "Settings" of the VM and go "System" then Motherboard and Enable EFI, then "Network" "Adapter 1" Bridged and your adapter
+     - For VirtualBox create a new virtual machine, select "Other Linux (64Bit), assign it at least 2 GB of memory and "Use an existing virtual hard disk file", select the VDI file from above, afterwards edit the "Settings" of the VM and go "System" then Motherboard and Enable EFI, then "Network" "Adapter 1" Bridged and your adapter.
-     - For Hyper-V create a new virtual machine, select "Generation 2", assign it at least 2 GB of memory and select "Connection -> "Your Virtual Switch that is bridged", then "Use an existing virtual hard disk" and select the VHDX file from above, after creation go to "Settings" -> "Security" and deselect "Enable Secure Boot"
+     - For Hyper-V create a new virtual machine, select "Generation 2", assign it at least 2 GB of memory and select "Connection -> "Your Virtual Switch that is bridged", then "Use an existing virtual hard disk" and select the VHDX file from above, after creation go to "Settings" -> "Security" and deselect "Enable Secure Boot".
      - For KVM create a new virtual machine in `virt-manager`, select "Import existing disk image", provide the path to the QCOW2 image above, choose "Generic Default" for the operating system, assign at least 2 GB memory and 1 vCPU, check the box for "Customize configuration before install" and select your bridge under "Network Selection", then under customization select "Overview" -> "Firmware" -> "UEFI x86_64: ...".
-     - For Vmware Workstation create a new virtual machine, select "Custom", make it compatible with the default of Workstation and ESX, Choose "I will install the operating system later", select "Linux" -> "Other Linux 5.x or later kernel 64-bit", give it atleast 2GB RAM and 1vCPU, select "Use Bridged Networking" then "Use an existing virtual disk" and select the VMDK file above, after creation of VM go to "Settings" and "Options" then "Advanced" and select "Firmware type" to "UEFI"
+     - For Vmware Workstation create a new virtual machine, select "Custom", make it compatible with the default of Workstation and ESX, Choose "I will install the operating system later", select "Linux" -> "Other Linux 5.x or later kernel 64-bit", give it at least 2 GB RAM and 1vCPU, select "Use Bridged Networking" then "Use an existing virtual disk" and select the VMDK file above, after creation of VM go to "Settings" and "Options" then "Advanced" and select "Firmware type" to "UEFI".
 
 3. Optional - set up the Wi-Fi or a static IP address. There are two possible places for that:
    - on a blank USB stick with a FAT32 partition having partition label `CONFIG`, while in its root directory, create the `network/my-network` file, or
@@ -107,23 +107,23 @@ If you would like to test next release before anyone else, you can install the b
 
 [balenaEtcher]: https://www.balena.io/etcher
 [hassos-network]: https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md
-[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi0-w-4.11.img.gz
+[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_rpi0-w-4.12.img.gz
-[pi1]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi-4.11.img.gz
+[pi1]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_rpi-4.12.img.gz
-[pi2]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi2-4.11.img.gz
+[pi2]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_rpi2-4.12.img.gz
-[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi3-4.11.img.gz
+[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_rpi3-4.12.img.gz
-[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi3-64-4.11.img.gz
+[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_rpi3-64-4.12.img.gz
-[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi4-4.11.img.gz
+[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_rpi4-4.12.img.gz
-[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi4-64-4.11.img.gz
+[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_rpi4-64-4.12.img.gz
-[tinker]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_tinker-4.11.img.gz
+[tinker]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_tinker-4.12.img.gz
-[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_odroid-c2-4.11.img.gz
+[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_odroid-c2-4.12.img.gz
-[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_odroid-n2-4.11.img.gz
+[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_odroid-n2-4.12.img.gz
-[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_odroid-xu4-4.11.img.gz
+[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_odroid-xu4-4.12.img.gz
-[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_intel-nuc-4.11.img.gz
+[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_intel-nuc-4.12.img.gz
-[vmdk]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vmdk.gz
+[vmdk]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_ova-4.12.vmdk.gz
-[vhdx]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vhdx.gz
+[vhdx]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_ova-4.12.vhdx.gz
-[vdi]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vdi.gz
+[vdi]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_ova-4.12.vdi.gz
-[qcow2]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.qcow2.gz
+[qcow2]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_ova-4.12.qcow2.gz
-[Virtual Appliance]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.ova
+[Virtual Appliance]: https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_ova-4.12.ova
 [local]: http://homeassistant.local:8123
 [samba]: /addons/samba/
 [ssh]: /addons/ssh/

source/hassio/zwave.markdown

@@ -13,7 +13,7 @@ zwave:
 ## RAZBERRY BOARD
 
 If you need GPIO on Raspberry Pi 3 for your Z-Wave module, add the following line into `config.txt` (you have to access that on the SD card directly. Simply plug it into your PC and edit it there.
-The `config.txt` is not accessible from the Home Assistant Operating System, you may need to open the SD card on a Windows or Linux system.:
+The `config.txt` is not accessible from the Home Assistant Operating System, you may need to open the SD card on a Windows or Linux system:
 
 ```txt
 dtoverlay=pi3-miniuart-bt
@@ -39,7 +39,7 @@ zha:
 
 ## Ubuntu and Debian based host system
 
-If your instance is running on a Debian based system, e.g., Ubuntu, the ModemManager may cause unexpected issues.
+If your instance is running on a Debian-based system, e.g., Ubuntu, the ModemManager may cause unexpected issues.
 
 The ModemManager might be claiming or interfering with a USB Z-Wave stick, like the much used Aeotec ones. If you experience issues where the stick stops responding, needs to be re-plugged or Home Assistant needs a restart to get Z-Wave back, chances are high that the ModemManager is causing the issue.