Merge branch 'current' into next

_config.yml

@@ -5,10 +5,10 @@
 
 url: https://www.home-assistant.io
 title: Home Assistant
-subtitle: Open-source home automation platform running on Python 3
+subtitle: Open source home automation that puts local control and privacy first.
 author: Home Assistant
 simple_search: https://www.google.com/search
-description: Home Assistant is an open-source home automation platform running on Python 3.
+description: Open source home automation that puts local control and privacy first.
 
 # Default date format is "ordinal" (resulting in "July 22nd 2007")
 # You can customize the format as defined in
@@ -141,14 +141,14 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 78
-current_patch_version: 3
-date_released: 2018-09-22
+current_minor_version: 79
+current_patch_version: 0
+date_released: 2018-09-28
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
 # Major release:
-patch_version_notes: "#release-0783---september-22"
+patch_version_notes: ""
 # Minor release (Example #release-0431---april-25):
 
 # Date we moved to Discourse for comments

source/_components/demo.markdown

@@ -26,13 +26,15 @@ Available demo platforms:
 - [Image Processing](/components/image_processing/) (`image_processing`)
 - [Light](/components/light/) (`light`)
 - [Lock](/components/lock/) (`lock`)
+- [Mailbox](/components/mailbox/) (`mailbox`)
+- [Media Player](/components/media_player/) (`media_player`)
 - [Notification](/components/notify/) (`notify`)
 - [Remote](/components/remote/) (`remote`)
 - [Sensor](/components/sensor/) (`sensor`)
 - [Switch](/components/switch/) (`switch`)
 - [Text-to-speech](/components/tts/) (`tts`)
 - [Weather](/components/weather/) (`weather`)
-- [Mailbox](/components/mailbox/) (`mailbox`)
+
 
 To integrate a demo platform in Home Assistant, add the following section to your `configuration.yaml` file:
 

source/_components/device_tracker.locative.markdown

@@ -38,4 +38,4 @@ To configure Locative, you must set up the app to send a `GET` request to your H
 
 When you enter a geofence, your location name in Home Assistant will be set to the name of the geofence in Locative. When you exit a geofence, your location name in Home Assistant will be set to "not home".
 
-To use Locative in combination with another device tracker, such as [nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/), fill in the `mac` field to the Locative entry in `known_devices.yaml` with the MAC address of the device you want to track. The state of the device will be determined by the source that reported last.
+To use Locative in combination with another device tracker, such as [Nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/), fill in the `mac` field to the Locative entry in `known_devices.yaml` with the MAC address of the device you want to track. The state of the device will be determined by the source that reported last.

source/_components/device_tracker.nmap_tracker.markdown

@@ -38,17 +38,17 @@ device_tracker:
 
 Configuration variables:
 
-- **hosts** (*Required*): The network address to scan (in any supported NMap format). Mixing subnets and IPs is possible.
-- **home_interval** (*Optional*): The number of minutes nmap will not scan this device, assuming it is home, in order to preserve the device battery.
-- **exclude** (*Optional*): Hosts not to include in nmap scanning. Scanning the host where Home Assistant is running can cause problems (websocket error), so excluding that host is a good idea.
-- **scan_options** (*Optional*): Configurable scan options for nmap. Default to `-F --host-timeout 5s`
+- **hosts** (*Required*): The network address to scan (in any supported Nmap format). Mixing subnets and IPs is possible.
+- **home_interval** (*Optional*): The number of minutes Nmap will not scan this device, assuming it is home, in order to preserve the device battery.
+- **exclude** (*Optional*): Hosts not to include in Nmap scanning. Scanning the host where Home Assistant is running can cause problems (websocket error), so excluding that host is a good idea.
+- **scan_options** (*Optional*): Configurable scan options for Nmap. Default to `-F --host-timeout 5s`
 
 ## {% linkable_title Examples %}
 
 A full example for the `nmap` tracker could look like the following sample:
 
 ```yaml
-# Example configuration.yaml entry for nmap
+# Example configuration.yaml entry for Nmap
 # One whole subnet, and skipping two specific IPs.
 device_tracker:
   - platform: nmap_tracker
@@ -60,7 +60,7 @@ device_tracker:
 ```
 
 ```yaml
-# Example configuration.yaml for nmap
+# Example configuration.yaml for Nmap
 # One subnet, and two specific IPs in another subnet.
 device_tracker:
   - platform: nmap_tracker

source/_components/device_tracker.snmp.markdown

@@ -19,7 +19,7 @@ A lot of WiFi access points and WiFi routers support the Simple Network Manageme
 This device tracker needs SNMP to be enabled on the router. It could be that you need to install the SNMP support manually.
 </p>
 
-The following OID examples pull the current MAC Address table from a router. This reflects all recent devices seen on the network. However, since devices are not removed until they time out, this is less effective for [device tracker component page](/components/device_tracker/) than desirable. It is recommended to use [Ping](/components/device_tracker.ping/) or [NMAP](/components/device_tracker.nmap_tracker/) instead.
+The following OID examples pull the current MAC Address table from a router. This reflects all recent devices seen on the network. However, since devices are not removed until they time out, this is less effective for [device tracker component page](/components/device_tracker/) than desirable. It is recommended to use [Ping](/components/device_tracker.ping/) or [Nmap](/components/device_tracker.nmap_tracker/) instead.
 
 | Brand | Device/Firmware | OID |
 |---|---|---|---|

source/_components/device_tracker.tomato.markdown

@@ -15,7 +15,7 @@ ha_release: pre 0.7
 
 The `tomato` platform requires an extra config variable called `http_id`. The value can be obtained by logging in to the Tomato admin interface and search for `http_id` in the page source code.
 
-Because of a limitation in Tomato's API, this platform will only track wireless devices. If tracking wired devices like a Philips Hue Hub is necessary, it is possible to use another platform like [NMAP](/components/device_tracker.nmap_tracker/).
+Because of a limitation in Tomato's API, this platform will only track wireless devices. If tracking wired devices like a Philips Hue Hub is necessary, it is possible to use another platform like [Nmap](/components/device_tracker.nmap_tracker/).
 
 To use this device tracker in your installation, add the following to your `configuration.yaml` file:
 

source/_components/google_assistant.markdown

@@ -29,34 +29,34 @@ To use Google Assistant, your Home Assistant configuration has to be externally
 
 You need to create an API Key with the [Google Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) which allows you to update devices without unlinking and relinking an account (see [below](/#troubleshooting-the-request_sync-service)). If you don't provided it the `google_assistant.request_sync` service is not exposed. It is recommended to set up this configuration key as it also allows the usage of the following command, "Ok Google, sync my devices". Once you have setup this component you will need to call this service (or command) each time you add a new device that you wish to control via the Google Assistant integration.
 
-1. Create a new project in the [developer console](https://console.actions.google.com/).  
-  a. Add/Import project, give it a name    
+1. Create a new project in the [Actions on Google console](https://console.actions.google.com/).
+  a. Add/Import project, give it a name
   b. Click on `Home Control` card, select the `Smart home` recommendation.
-  c. Create an Action, under the build section. Add in your Home Assistant URL: `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant`, replace the `[YOUR HOME ASSISTANT URL:PORT]` with the domain / ip address and the port under which your Home Assistant is reachable.  
-  d. Click `Done`. Then click on `Overview`, which will lead you back to the app details screen.  
+  c. Create an Action, under the build section. Add in your Home Assistant URL: `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant`, replace the `[YOUR HOME ASSISTANT URL:PORT]` with the domain / ip address and the port under which your Home Assistant is reachable.
+  d. Click `Done`. Then click on `Overview`, which will lead you back to the app details screen.
 2. `Account linking` is required for your app to interact with Home Assistant. Set this up under the `Quick Setup` section
-	a. Leave it at the default `No, I only want to allow account creation on my website` and select Next  
-	b. For the `Linking type` select `OAuth` and `Authorization Code`  
+	a. Leave it at the default `No, I only want to allow account creation on my website` and select Next
+	b. For the `Linking type` select `OAuth` and `Authorization Code`
 	c. Client ID: `https://oauth-redirect.googleusercontent.com/`, the trailing slash is important
 	d. Client Secret: Anything you like, Home Assistant don't need this field
 	e. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize`.
 	f. Token URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/auth/token`.
-	g. Configure your client. Add scopes for `email` and `name`.  
+	g. Configure your client. Add scopes for `email` and `name`.
 	h. Do NOT check `Google to transmit clientID and secret via HTTP basic auth header`
 	i. Testing instructions: Enter anything. It doesn't matter since you won't submit this app.
 3. Back on the overview page. Click `Simulator` under `TEST`. It will create a new draft version Test App. You don't have to actually test.
 4. If you haven't already added the component configuration to `configuration.yaml` file and restarted Home Assistant, you'll be unable to continue until you have.
 5. Open the Google Assistant app and go into `Settings > Home Control`
 6. Click the `+` sign, and near the bottom, you should have `[test] your app name`. Selecting that should lead you to a browser to login your Home Assistant instance, then redirect back to a screen where you can set rooms for your devices or nicknames for your devices.
-7. If you want to allow other household users to control the devices:  
-	a. Go to the settings for the project you created in point 1 in the developer console.  
-	b. Under the gear icon, click `Permissions`  
-	c. Click `Add`, type the new user's e-mail address and choose `Project -> Editor` role  
+7. If you want to allow other household users to control the devices:
+	a. Go to the settings for the project you created in point 1 in the developer console.
+	b. Under the gear icon, click `Permissions`
+	c. Click `Add`, type the new user's e-mail address and choose `Project -> Editor` role
 	d. Have the new user go to [developer console](https://console.actions.google.com/) and repeat steps starting from point 3
-8. If you want to use the `google_assistant.request_sync` service, to update devices without unlinking and relinking, in Home Assistant, then enable Homegraph API for your project:  
-	a. Go to the [cloud console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview)  
-	b. Select your project and click Enable Homegraph API  
-	c. Go to Credentials, which you can find on the left navigation bar under the key icon, and select API Key from Create Credentials  
+8. If you want to use the `google_assistant.request_sync` service, to update devices without unlinking and relinking, in Home Assistant, then enable Homegraph API for your project:
+	a. Go to the [cloud console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview)
+	b. Select your project and click Enable Homegraph API
+	c. Go to Credentials, which you can find on the left navigation bar under the key icon, and select API Key from Create Credentials
 	d. Note down the generated API Key and use this in the configuration
 
 ## {% linkable_title Configuration %}

source/_components/hue.markdown

@@ -12,6 +12,7 @@ ha_category: Hub
 ha_iot_class: "Local Polling"
 featured: true
 ha_release: "0.60"
+ha_qa_scale: platinum
 ---
 
 Philips Hue support is integrated into Home Assistant as a Hub that can drive the light platform. The preferred way to setup the Philips Hue platform is by enabling the [discovery component](/components/discovery/).

source/_components/media_player.kodi.markdown

@@ -196,7 +196,7 @@ media_player:
 ```
 
 <p class='note'>
-This example and the following requires to have the [script.json-cec](https://github.com/joshjowen/script.json-cec) plugin installed on your kodi player. It'll also expose th endpoints standy, toggle and activate without authentication on your kodi player. Use this with caution.
+This example and the following requires to have the [script.json-cec](https://github.com/joshjowen/script.json-cec) plugin installed on your kodi player. It'll also expose the endpoints standby, toggle and activate without authentication on your kodi player. Use this with caution.
 </p>
 
 ### {% linkable_title Kodi services samples %}

source/_components/notify.html5.markdown

@@ -52,7 +52,7 @@ Follow these steps to verify domain ownership with Google Webmaster Central / Se
 2. Create a directory named "www" in your Home Assistant configuration directory (/config share from Samba add-on).
 3. Place the downloaded google*.html file in the "www" directory.
 4. RESTART Home Assistant - this is important!
-5. Verify the file can be accessed in the browser, ie. **https://example.com:8123/local/google123456789.html** (change filename) - you should a plain text message saying "google-site-verification: ..." - if you see "404: Not Found" or something else, retry the above steps.
+5. Verify the file can be accessed in the browser, ie. **https://example.com:8123/local/google123456789.html** (change filename) - you should see a plain text message saying "google-site-verification: ..." - if you see "404: Not Found" or something else, retry the above steps.
 6. Go back to Google Webmaster Central / Search Console and proceed with the verification.
 
 ### {% linkable_title Requirements %}

source/_components/sensor.dnsip.markdown

@@ -33,13 +33,14 @@ sensor:
 
 Configuration variables:
 
-- **hostname** (*Optional*): The hostname for which to perform the DNS query. Default: `myip.opendns.com` (special hostname that resolves to your public IP)
-- **resolver** (*Optional*): The DNS server to target the query at. Default: `208.67.222.222` (OpenDNS)
+- **hostname** (*Optional*): The hostname for which to perform the DNS query. Defaults to `myip.opendns.com` (special hostname that resolves to your public IP).
+- **name** (*Optional*): Name of the sensor. Defaults to `myip` or hostname without dots if specified.
+- **resolver** (*Optional*): The DNS server to target the query at. Defaults to `208.67.222.222` (OpenDNS).
 - **ipv6** (*Optional*): Set this to `true` or `false` if IPv6 should be used. When resolving the public IP, this will be the IP of the machine where Home Assistant is running on.
-- **resolver_ipv6** (*Optional*): The IPv6 DNS server to target the query at. Default: `2620:0:ccc::2` (OpenDNS)
-- **scan_interval** (*Optional*): Defines number of seconds for polling interval. Default: `120` seconds.
+- **resolver_ipv6** (*Optional*): The IPv6 DNS server to target the query at. Defaults to `2620:0:ccc::2` (OpenDNS).
+- **scan_interval** (*Optional*): Defines number of seconds for polling interval. Defaults to `120` seconds.
 
-#### {% linkable_title Extended example %}
+## {% linkable_title Extended example %}
 
 ```yaml
 # Example configuration.yaml entry
@@ -49,5 +50,6 @@ sensor:
   # Resolve IP address of home-assistant.io via Google DNS
   - platform: dnsip
     hostname: home-assistant.io
+    name: hass
     resolver: 8.8.8.8
 ```

source/_components/sensor.ios.markdown

@@ -0,0 +1,17 @@
+---
+layout: page
+title: "iOS"
+description: "Instructions on how to use the iOS sensors with Home Assistant."
+date: 2018-04-06 08:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: apple.png
+ha_category: Sensor
+featured: false
+ha_release: 0.31
+ha_iot_class: push
+---
+
+The `ios` component is the Home Assistant part for using the iOS companion app. For further details please check the [iOS section](/docs/ecosystem/ios/) in the documentation for further details.

source/_components/sensor.jewish_calendar.markdown

@@ -7,10 +7,9 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
-logo: home-assistant.png
 ha_category: Calendar
-ha_iot_class: "Local Push"
-ha_release: "0.80"
+ha_iot_class: "Local Poll"
+ha_release: "0.79"
 ---
 
 The Jewish Calendar (`jewish_calendar`) sensor platform displays a variety of information related to the Jewish Calendar as a variety of sensors.

source/_components/sensor.nest.markdown

@@ -59,7 +59,7 @@ The following conditions are available by device:
 ## {% linkable_title Security State %}
 
 <p class='note warning'>
-This feature is not designed to transfer your Home Assitant to a secruity system, neither Home Assistant nor Nest be liable to You for damages,
+This feature is not designed to transfer your Home Assitant to a security system, neither Home Assistant nor Nest be liable to You for damages,
 or consequential damages of any character arising as a result of use this feature.
   
 This feature does not depend on the [Nest Secure alarm system](https://nest.com/alarm-system/overview/) and is not a reflection of the status of that system,
@@ -67,9 +67,9 @@ nor does it react to state changes in that system.
 </p>
 
 <p class='note'>
-This feautre use a new [Nest Secruity API](https://developers.nest.com/documentation/cloud/security-guide),
-you may need to change your ["Product"](https://developers.nest.com/products) permission setting to include `Secruity State Read`.
-After permission change, you may need to re-authorize your client.
+This feature uses a new [Nest Security API](https://developers.nest.com/documentation/cloud/security-guide).
+You may need to change your ["Product"](https://developers.nest.com/products) permission setting to include `Security State Read`.
+After this permission change, you may need to re-authorize your client.
 </p>
 
 If a Nest Cam detects the presence of a person (see `person_detected` in [binary_sensor.nest](/components/binary_sensor.nest/)) while the structure is in `away` mode (see `away` in [binary_sensor.nest](/components/binary_sensor.nest/)), the structure enters `deter` mode.

source/_components/sensor.tibber.markdown

@@ -14,6 +14,7 @@ ha_iot_class: "Cloud Polling"
 ---
 
 The `tibber` sensor provides the current electricity price if you are a [Tibber](https://tibber.com/) customer.
+If you have a Tibber Pulse it will also show the electricity consumption in real time.
 
 To add Tibber to your installation, add the following to your `configuration.yaml` file:
 

source/_cookbook/automation_telegram_presence_alert.markdown

@@ -10,7 +10,7 @@ footer: true
 ha_category: Automation Examples
 ---
 
-This will send a message when someone in your known devices list connects to your local network. In other words, when someone arrives home. It will only work if you are using the [nmap](/components/device_tracker.nmap_tracker/) device tracker or a similar component. 
+This will send a message when someone in your known devices list connects to your local network. In other words, when someone arrives home. It will only work if you are using the [Nmap](/components/device_tracker.nmap_tracker/) device tracker or a similar component. 
 
 This example uses [Telegram](/components/notify.telegram/) to send the notification.
 

source/_docs/authentication/multi-factor-auth.markdown

@@ -66,7 +66,7 @@ homeassistant:
 
 Notify MFA module using [notify component](https://www.home-assistant.io/components/notify/) to delivery a [HMAC-based One-Time Password](https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_algorithm) to user configured target.
 
-User need first set up the MFA module by select one of the aviliable notify service. A 8 digit one-time password will be sent by this notify service, user need to input it to verify the setup.
+User need first set up the MFA module by select one of the aviliable notify service. A 6 digit one-time password will be sent by this notify service, user need to input it to verify the setup.
 
 During the login process, an 8 digit one-time password will be sent again, user need to input it to verify his/her identity. If the validation failed, a new one-time password will be sent again.
 

source/_docs/authentication/providers.markdown

@@ -10,10 +10,6 @@ sharing: true
 footer: true
 ---
 
-<p class='note warning'>
-This page only apply to release 0.77 and above.
-</p>
-
 <p class='note warning'>
 This is an advanced feature. If misconfigured, you will not be able to access Home Assistant anymore!
 </p>

source/_docs/configuration/devices.markdown

@@ -14,9 +14,14 @@ Home Assistant will be able to automatically discover many devices and services
 
 See the [components overview page](/components/) to find installation instructions for your devices and services. If you can't find support for your favorite device or service, [consider adding support](/developers/add_new_platform/).
 
+Classification for the available integrations:
+
+- [IoT class(/blog/2016/02/12/classifying-the-internet-of-things): Classifier for the device's behavior.
+- [Quality scale](/docs/quality_scale/): Representation of the integration's quality.
+
 Usually every entity needs its own entry in the `configuration.yaml` file. There are two styles for multiple entries:
 
-#### {% linkable_title Style 1: Collect every entity under the "parent" %}
+## {% linkable_title Style 1: Collect every entity under the "parent" %}
 
 ```yaml
 sensor:
@@ -33,7 +38,7 @@ switch:
   - platform: vera
 ```
 
-#### {% linkable_title Style 2: List each device separately %}
+## {% linkable_title Style 2: List each device separately %}
 
 You need to append numbers or strings to differentiate the entries, as in the example below. The appended number or string must be unique.
 
@@ -52,7 +57,7 @@ camera 2:
   platform: mjpeg
 ```
 
-### {% linkable_title Grouping devices %}
+## {% linkable_title Grouping devices %}
 
 Once you have several devices set up, it is time to organize them into groups.
 Each group consists of a name and a list of entity IDs. Entity IDs can be retrieved from the web interface by using the Set State page in the Developer Tools (<img src='/images/screenshots/developer-tool-states-icon.png' alt='service developer tool icon' class="no-shadow" height="38" />).

source/_docs/ecosystem/appdaemon/api.markdown

@@ -1596,7 +1596,7 @@ for tracker in trackers:
 
 ### {% linkable_title get_tracker_state() %}
 
-Get the state of a tracker. The values returned depend in part on the configuration and type of device trackers in the system. Simpler tracker types like `Locative` or `NMAP` will return one of 2 states:
+Get the state of a tracker. The values returned depend in part on the configuration and type of device trackers in the system. Simpler tracker types like `Locative` or `Nmap` will return one of 2 states:
 
 - `home`
 - `not_home`

source/_docs/installation/hassbian/installation.markdown

@@ -17,8 +17,8 @@ One of the easiest ways to install Home Assistant on your Raspberry Pi Zero, 2,
  3. Ensure your Raspberry Pi has wired access to the internet for the entire process or configure your [wireless network settings](#wireless-network) **before proceeding to step 4**.
  4. Insert SD card to Raspberry Pi and turn it on. Initial installation of Home Assistant will take about 10 minutes.
 
-<p class='note'>
-Please remember to ensure you're using an [appropriate power supply](https://www.raspberrypi.org/help/faqs/#powerReqs) with your Pi. Mobile chargers may not be suitable, since some are designed to only provide the full power with that manufacturer's handsets.
+<p class='note warning'>
+Please remember to ensure you're using an [appropriate power supply](https://www.raspberrypi.org/help/faqs/#powerReqs) with your Pi. Mobile chargers may not be suitable since some were only designed to provide just enough power to the device it was designed for by the manufacturer. **Do not** try to power the Pi from the USB port on a TV, computer, or similar.
 </p>
 
 These instructions are also available as a [video](https://www.youtube.com/watch?v=iIz6XqDwHEk).  

source/_docs/quality_scale.markdown

@@ -0,0 +1,31 @@
+---
+layout: page
+title: "Quality Scale"
+description: "Details about the classification of integrations."
+date: 2018-09-26 23:50
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+The Integration Quality Scale scores each integration based on the code quality and user experience. Each level of the quality scale consists of a list of requirements. If an integration matches all requirements, it's considered to have reached that level.
+
+[Integration Quality Scale](https://developers.home-assistant.io/docs/en/integration_quality_scale_index.html) for developers.
+
+## {% linkable_title No score %}
+
+This integration passes the bare minimum requirements. That's the level of most integrations when they are introduced into Home Assistant. It doesn't mean that they are bad or buggy, just that you need to configure them with an entry in your `configuration.yaml` file.
+
+## {% linkable_title Silver 🥈 %}
+
+This integration is able to cope when things go wrong. It will not print any exceptions nor will it fill the log with retry attempts. Also, it will show you if a device is offline or not ready when you start Home Assistant.
+
+## {% linkable_title Gold 🥇 %}
+
+This is a solid integration that is able to survive poor conditions and can be configured via the user interface.
+
+## {% linkable_title Platinum 🏆 %}
+
+Best of the best. The integration is completely async, meaning it's super fast and gives you an excellent user experience.
+

source/_docs/security/webserver.markdown

@@ -12,7 +12,7 @@ redirect_from: /docs/frontend/webserver/
 
 It was only a matter of time until the first queries for tools like [https://www.shodan.io](https://www.shodan.io/search?query=Home+Assistant) to search for Home Assistant instances showed up.
 
-To get an idea about how your Home Assistant instance looks to a network scanner, you can use `nmap`. The `nmap` tool is already available if you are using the [nmap device tracker](/components/device_tracker/). 
+To get an idea about how your Home Assistant instance looks to a network scanner, you can use `nmap`. The `nmap` tool is already available if you are using the [Nmap device tracker](/components/device_tracker/). 
 
 ```bash
 $ nmap -sV -p 8123 --script=http-title,http-headers 192.168.0.3

source/_docs/z-wave/adding.markdown

@@ -80,7 +80,18 @@ To remove (exclude) a Z-Wave device from your system:
 1. Go to the Z-Wave control panel in the Home Assistant frontend
 2. Click the **Remove Node** button in the *Z-Wave Network Management* card - this will place the controller in exclusion mode
 3. Activate your device to be excluded by following the instructions provided with the device
-4. Run a *Heal Network* so all the other nodes learn about its removal
+4. The device will now be removed, but that won't show until you restart Home Assistant 
+5. Run a *Heal Network* so all the other nodes learn about its removal
+
+If your device isn't responding to this process, possibly because you've factory reset it or it has failed, you can remove it using **Remove Failed Node**. This only works for devices marked as `"is_failed": true`, but you can trick the system into thinking that this the case:
+
+1. Go to the *States* menu under *Developer tools* in the Home Assistant frontend
+2. Click on the name of the `zwave.` entity you want to remove
+3. At the top, edit the JSON attributes to replace `false` with `true` for `"is_failed": false,` so that it reads `"is_failed": true,`
+4. Click **Set State**
+5. Go to the Z-Wave control panel in the Home Assistant frontend
+6. Click the **Remove Failed Node** button in the *Z-Wave Network Management* card
+7. The device will now be removed, but that won't show until you restart Home Assistant 
 
 ## {% linkable_title Troubleshooting %}
 

source/_docs/z-wave/control-panel.markdown

@@ -33,7 +33,7 @@ Here is where you [include and exclude](/docs/z-wave/adding/) Z-Wave devices fro
 ## {% linkable_title Z-Wave Node Management %}
 
 * **Refresh Node** refreshes the information on the node and its entities. If used on a battery powered device, the device will first need to wake for this to work.
-* **Remove Failed Node** will remove a failed node from the network. The node needs to be on the controller's Failed Node List (marked as `is_failed: true`), otherwise this command will fail.
+* **Remove Failed Node** will remove a failed node from the network. The node needs to be on the controller's Failed Node List (marked as `is_failed: true`), otherwise this command will fail. You can trick OpenZWave into thinking the node is failed by selecting the `zwave` entity in the *States* menu, under *Developer tools*, and changing `"is_failed": false,` to `"is_failed": true,` then selecting *Set State*.
 * **Replace Failed Node** will replace a failed device with another. If the node is not in the controller's Failed Node List, or the node responds, this command will fail.
 * **Print Node** prints all state of Z-Wave node to the console log
 

source/_includes/asides/component_navigation.html

@@ -28,6 +28,20 @@
     </div>
   {% endif %}
 
+  {% if page.ha_qa_scale %}
+    <div class='section'>
+      Quality Scale: <a href='/docs/quality_scale/'>
+        {% if page.ha_qa_scale == 'platinum' %}
+          🏆 (platinum)
+        {% elsif page.ha_qa_scale == 'gold' %}
+          🥇 (gold)
+        {% elsif page.ha_qa_scale == 'silver' %}
+          🥈 (silver)
+        {% endif %}
+      </a>
+    </div>
+  {% endif %}
+
   {% if page.ha_release %}
     <div class='section'>
       Introduced in release: {{ page.ha_release }}

source/_lovelace/iframe.markdown

@@ -12,7 +12,9 @@ footer: true
 
 Embed data from other webservices in your dashboard. You can also embed files stored in your `<config-directory>/www` folder and reference them using `/local/<file>`.
 
+<p class='note warning'>
 You can't embed sites using HTTP if you are using HTTPS for your Home Assistant.
+</p>
 
 <p class='img'>
   <img width="500" src='/images/lovelace/lovelace_iframe.png' alt='Windy weather radar as iframe'>

source/_posts/2018-09-15-release-78.markdown

@@ -81,6 +81,7 @@ The configuration value type should no longer be used. ([@endor-force] - [#15935
 - Fix Mi Flora median calculation. Removed `retries` and `timeout` config parameters, they were not used for several months. Replaced `cache_value` config with `scan_interval` to fix a bug in the PR. ([@PaulAnnekov] - [#16085]) ([sensor.miflora docs]) (breaking change)
 - Twitch now requires a `client_id` and so the platform got updated. ([@ioangogo] - [#16428]) ([sensor.twitch docs]) (breaking change)
 - The radiotherm `fan` and `mode` state attributes were updated to reflect the real-time fan and mode states of the thermostat, rather than the overall selected state (automatic, mostly). The mode attributes still contain the selected modes (fan on/auto, heat/cool/auto). ([@cpw] - [#15031]) ([climate.radiotherm docs]) (breaking change)
+- The `dnsip` sensor now uses `myip` as default name. ([@grea09] - [#16205]) ([sensor.dnsip docs]) (breaking change)
 
 ## {% linkable_title Beta Fixes %}
 

source/_posts/2018-10-01-release-79.markdown

@@ -0,0 +1,534 @@
+---
+layout: post
+title: "0.79: Device Registry, Logi Circle, Huawei LTE routers, GeoJSON"
+description: "Home Assistant is now able to show the devices and entities that belong to an integration."
+date: 2018-09-28 00:01:00
+date_formatted: "September 28, 2018"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2018-09-release-0.79/components.png
+---
+
+<p class='note'>
+In case you missed it two weeks ago, check [our plans for the future](/blog/2018/09/17/thinking-big/).
+</p>
+
+<a href='/components/#version/0.79'><img src='/images/blog/2018-09-release-0.79/components.png' style='border: 0;box-shadow: none;'></a>
+
+It's time for another great release and we're introducing a brand new feature: device registry. This allows integrations to tell Home Assistant not only about entities, but also which devices the entities represent. It also allows integrations to tell Home Assistant how a device is connected to Home Assistant. For example, a Hue light bulb is connected to Home Assistant via the Hue hub.
+
+<p class='img'>
+<img src='/images/blog/2018-09-release-0.79/integrations.png' alt='Screenshot showing several configured integrations'>
+Screenshot showing several configured integrations in the configuration panel.
+</p>
+
+Adding devices to the mix allows us to do a lot of cool things. It allows us to group entities and show how they relate to one another. It will also allow us to inform the user if data leaves the home network and shows the firmware version that the device is running on.
+
+<p class='img'>
+<img src='/images/blog/2018-09-release-0.79/config_entry.png' alt='Screenshot showing the devices of a config entry'>
+Screenshot showing the devices of the iOS integration.
+</p>
+
+Devices can only be added by integrations that are configured via the integrations panel in the config panel. So we've also been expanding the integrations that support that. This release brings support to iOS, MQTT and Tradfri.
+
+<p class='img'>
+<img src='/images/blog/2018-09-release-0.79/mqtt.png' alt='Screenshot showing how to configure MQTT via UI'>
+Screenshot showing how to configure MQTT via UI
+</p>
+
+And this is not all! There is so much more. In an effort to make the quality of an integration more clear, we've added an [Integration Quality Scale](/docs/quality_scale/). With this scale we'll be able to clearly communicate to the user how good an integration is and it gives developers a list on how to improve it. Expect these levels to pop up in the integration list soon.
+
+And did you think we forgot about auth? We did not. [@awarecan] has added a new multi-factor auth module that will send you a one-time authentication code to finish your login, **with a notification service of your choice**. PushBullet, Hangouts, iOS app, some obscure custom notification service using a shell script? It's possible.
+
+Oh, and yes, there is also some cool new integrations. Support has been added for Logi Circle camera's, GeoJSON events and even a bank. More below 👇
+
+## {% linkable_title New Platforms %}
+
+- Add Huawei LTE router platform, device tracker, and sensor ([@scop] - [#16498]) ([device_tracker docs]) ([huawei_lte docs]) ([sensor.huawei_lte docs]) (new-platform)
+- New EDP re:dy component ([@abmantis] - [#16426]) ([edp_redy docs]) ([sensor.edp_redy docs]) ([switch.edp_redy docs]) (new-platform)
+- Jewish calendar sensor ([@tsvi] - [#16393]) ([sensor.jewish_calendar docs]) (new-platform)
+- Added support for Starling Bank ([@Dullage] - [#16522]) ([sensor.starlingbank docs]) (new-platform)
+- Add Call Data Log platform. Mailboxes no longer require media ([@PhracturedBlue] - [#16579]) ([asterisk_mbox docs]) ([mailbox docs]) ([mailbox.asterisk_cdr docs]) ([mailbox.asterisk_mbox docs]) (new-platform)
+- Add Logi Circle component, camera and sensor platform ([@evanjd] - [#16540]) ([logi_circle docs]) ([camera.logi_circle docs]) ([sensor.logi_circle docs]) (new-platform)
+- deCONZ cover support ([@Kane610] - [#16759]) ([cover docs]) ([deconz docs]) ([cover.deconz docs]) (new-platform)
+- GeoJSON platform ([@exxamalte] - [#16610]) ([geo_location docs]) (new-platform)
+- Add linky sensor ([@tiste] - [#16468]) ([sensor.linky docs]) (new-platform)
+
+## {% linkable_title If you need help... %}
+
+...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+## {% linkable_title Reporting Issues %}
+
+Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
+
+<!--more-->
+
+## {% linkable_title Breaking Changes %}
+
+- Netdata configuration change: Allows multiple elements per group. Specify the `data_group` as part of the sensor description. See docs for details. ([@reefab] - [#16656]) ([sensor.netdata docs]) (breaking change)
+- The Dyson sensor Air Quality Index is now named AQI following Dyson's mobile app ([@glpatcern] - [#14550]) ([sensor.dyson docs]) (breaking change)
+
+## {% linkable_title Beta Fixes %}
+
+- Don't warn but info when on dev mode ([@balloob] - [#16831]) ([updater docs]) (beta fix)
+- Bump zm-py to 0.0.3 ([@rohankapoorcom] - [#16835]) ([zoneminder docs]) (beta fix)
+- Support old tradfri config format ([@balloob] - [#16841]) ([tradfri docs]) (beta fix)
+- Allow MQTT discovery ([@balloob] - [#16842]) ([mqtt docs]) (beta fix)
+- Add unique ID and device info to Nest camera ([@balloob] - [#16846]) ([camera.nest docs]) (beta fix)
+- Device Registry Support for iOS Sensors ([@cgarwood] - [#16862]) ([sensor.ios docs]) (beta fix)
+- Fix MQTT discovery ([@balloob] - [#16864]) ([mqtt docs]) (beta fix)
+- Make ring sync again ([@balloob] - [#16866]) ([camera.ring docs]) (beta fix)
+- Add unique_id to Nest Sensors ([@cgarwood] - [#16869]) ([binary_sensor.nest docs]) ([sensor.nest docs]) (beta fix)
+- Prevent discovered Tradfri while already configured ([@balloob] - [#16891]) ([tradfri docs]) (beta fix)
+- Handle exception handling websocket command ([@balloob] - [#16927]) ([websocket_api docs]) (beta fix)
+
+## {% linkable_title All changes %}
+
+- Upgrade wakeonlan to 1.1.6 ([@fabaff] - [#16512]) ([wake_on_lan docs]) ([media_player.panasonic_viera docs]) ([media_player.samsungtv docs]) ([switch.wake_on_lan docs])
+- Make the Qnap sensor more resilient if server is not reachable ([@mrosseel] - [#16445]) ([sensor.qnap docs])
+- Update PyRMVtransport version ([@cgtobi] - [#16547]) ([sensor.rmvtransport docs])
+- Isort preparations ([@scop] - [#16555]) ([apple_tv docs]) ([geo_location docs]) ([google_assistant docs]) ([rachio docs]) ([media_player.cast docs]) ([media_player.webostv docs])
+- Store notifications in component. Add ws endpoint for fetching. ([@jeradM] - [#16503]) ([http docs]) ([persistent_notification docs])
+- Fixes an OpenUV bug with the scan interval ([@bachya] - [#16570]) ([openuv docs])
+- Bump pyeconet ([@w1ll1am23] - [#16571]) ([climate.econet docs])
+- yr: use async syntax ([@Danielhiversen] - [#16563]) ([sensor.yr docs])
+- Notifications for Android TV: Add fontsize and sending images ([@danielperna84] - [#16565]) ([notify docs])
+- Upgrade pytest to 3.8.0 and pytest-timeout to 1.3.2 ([@scop] - [#16489])
+- Refactor zha/async_device_initialized(). ([@Adminiuga] - [#16485]) ([zha docs])
+- Update fan.zha platform. ([@Adminiuga] - [#16551]) ([fan.zha docs])
+- Hangouts help "page" and little bugfix ([@hobbypunk90] - [#16464]) ([hangouts docs])
+- Konnected component feature updates ([@heythisisnate] - [#16479]) ([konnected docs])
+- Add config entry to iOS ([@balloob] - [#16580]) ([ios docs]) ([notify docs])
+- Switchmate ([@Danielhiversen] - [#16395]) ([switch.switchmate docs])
+- Update pyhomematic to 0.1.48 ([@danielperna84] - [#16588]) ([homematic docs])
+- Add configure_reporting() method to zha component ([@Adminiuga] - [#16487]) ([zha docs]) ([binary_sensor.zha docs]) ([sensor.zha docs])
+- Allow only_cache parameter in zha.safe_read() ([@Adminiuga] - [#16553]) ([zha docs])
+- Update tibber lib version ([@Danielhiversen] - [#16590]) ([sensor.tibber docs])
+- xiaomi lib 0.10.0 ([@Danielhiversen] - [#16591]) ([xiaomi_aqara docs])
+- Support for the Quirky Nimbus ([@w1ll1am23] - [#16520]) ([wink docs]) ([climate.wink docs])
+- Multiple tag managers for Wireless Sensor Tags. ([@sergeymaysak] - [#16353]) ([wirelesstag docs]) ([binary_sensor.wirelesstag docs]) ([sensor.wirelesstag docs]) ([switch.wirelesstag docs])
+- Add Huawei LTE router platform, device tracker, and sensor ([@scop] - [#16498]) ([device_tracker docs]) ([huawei_lte docs]) ([sensor.huawei_lte docs]) (new-platform)
+- Changing z-wave brightness calculation to respect 0x01 and 0x02 byte values ([@Harvtronix] - [#16420]) ([light.zwave docs])
+- Add myself to CODEOWNERS for upcloud ([@scop] - [#16599])
+- Add websocket list APIs for the registries ([@balloob] - [#16597]) ([config docs])
+- MQTT config entry ([@balloob] - [#16594]) ([hangouts docs]) ([homematicip_cloud docs]) ([mqtt docs])
+- Upgrade python-twitch-client to 0.6.0 ([@fabaff] - [#16602]) ([sensor.twitch docs])
+- Improve precision of timer ticks ([@amelchio] - [#16598])
+- Switch components.sensor.zha to await syntax. ([@Adminiuga] - [#16619]) ([sensor.zha docs])
+- Adding support for RTDSContactSensor and RTDSMotionSensor in Tahoma … (RTS Alarms sensors and contacts for Somfy Protexiom alarms) ([@christopheBfr] - [#16609]) ([tahoma docs]) ([sensor.tahoma docs])
+- fix bug where momentary switch with activation low does not reset ([@heythisisnate] - [#16603]) ([switch.konnected docs])
+- Extracting zoneminder to a new library ([@rohankapoorcom] - [#16527]) ([zoneminder docs]) ([camera.zoneminder docs])
+- Add @rohankapoorcom to CODEOWNERS for the zoneminder platform ([@rohankapoorcom] - [#16627])
+- Small huawei_lte improvements ([@scop] - [#16626]) ([huawei_lte docs]) ([sensor.huawei_lte docs])
+- Upgrade pwmled to 1.3.0 ([@soldag] - [#16624]) ([light.rpi_gpio_pwm docs])
+- Clean up MjpegCamera by removing unnused hass object in __init__ ([@rohankapoorcom] - [#16628]) ([camera.axis docs]) ([camera.mjpeg docs]) ([camera.zoneminder docs])
+- Update developer doc links to developers.home-assistant.io ([@scop] - [#16622]) ([websocket_api docs])
+- Add valid_window=1 to TOTP verify ([@awarecan] - [#16625])
+- Add new devices to HomematicIP Cloud ([@mxworm] - [#16636]) ([binary_sensor.homematicip_cloud docs]) ([sensor.homematicip_cloud docs])
+- New EDP re:dy component ([@abmantis] - [#16426]) ([edp_redy docs]) ([sensor.edp_redy docs]) ([switch.edp_redy docs]) (new-platform)
+- Upgrade Switchmate lib ([@Danielhiversen] - [#16637]) ([switch.switchmate docs])
+- Update pyhomematic to 0.1.49 ([@danielperna84] - [#16649]) ([homematic docs])
+- Upgrade holidays to 0.9.7 ([@fabaff] - [#16651]) ([binary_sensor.workday docs])
+- Fix link to docs ([@fabaff] - [#16652]) ([vacuum.ecovacs docs])
+- Log raw result of configure_reporting() command. ([@Adminiuga] - [#16655]) ([zha docs])
+- Rework timer delays ([@amelchio] - [#16650])
+- Add config entries to connection class ([@balloob] - [#16618])
+- Add zha device entity ([@damarco] - [#14579]) ([zha docs])
+- Clean up device update, add via-hub ([@balloob] - [#16659])
+- Jewish calendar sensor ([@tsvi] - [#16393]) ([sensor.jewish_calendar docs]) (new-platform)
+- Fixes an AirVisual bug where response data is missing ([@bachya] - [#16673]) ([sensor.airvisual docs])
+- Suppress traceback and log error ([@fabaff] - [#16669]) ([sensor.scrape docs])
+- Fix Ecovacs vacuums showing "None" for name ([@OverloadUT] - [#16654]) ([ecovacs docs]) ([vacuum.ecovacs docs])
+- Upgrade paho-mqtt to 1.4.0 ([@fabaff] - [#16688]) ([mqtt docs]) ([shiftr docs])
+- Streamline log messages ([@gwww] - [#16243])
+- Added velbus counter sensors, updated to py-velbus 2.0.20 ([@Cereal2nd] - [#16683]) ([velbus docs]) ([sensor.velbus docs])
+- Added support for Starling Bank ([@Dullage] - [#16522]) ([sensor.starlingbank docs]) (new-platform)
+- Netdata configuration change: Allows multiple elements per group ([@reefab] - [#16656]) ([sensor.netdata docs]) (breaking change)
+- Upgrade mypy to 0.630 ([@scop] - [#16674])
+- Use one regex for Hass.io URL check ([@pvizeli] - [#16710]) ([hassio docs])
+- Remove usage of "run_until_complete" ([@smurfix] - [#16617])
+- More isort preparations ([@scop] - [#16633])
+- Use posargs in tox lint env ([@scop] - [#16646])
+- Make pylint report non-LF linefeeds per the style guidelines ([@scop] - [#16601])
+- Config flow tradfri ([@balloob] - [#16665])
+- MyQ Open State Fix ([@geekofweek] - [#16681]) ([cover.myq docs])
+- Save disabled_by in entity registry ([@cgarwood] - [#16699])
+- Upgrading librouteros version ([@kunago] - [#16718]) ([device_tracker docs])
+- Add unique_id to mqtt_json light ([@nikolaykasyanov] - [#16721])
+- On-demand update of swiss public transport sensor ([@vikramgorla] - [#16723]) ([sensor.swiss_public_transport docs])
+- Upgrade youtube_dl to 2018.09.18 ([@fabaff] - [#16729]) ([media_extractor docs])
+- Met.no weather platform ([@Danielhiversen] - [#16582])
+- Upgrade keyring to 15.1.0 ([@fabaff] - [#16734])
+- Avoid calling yr update every second for a minute ones every hour ([@Danielhiversen] - [#16731]) ([sensor.yr docs])
+- Upgrade shodan to 1.10.2 ([@fabaff] - [#16736]) ([sensor.shodan docs])
+- Add subscription info endpoint ([@balloob] - [#16727]) ([cloud docs]) ([websocket_api docs])
+- Small cleanup for slack ([@pvizeli] - [#16743]) ([notify docs])
+- light.zha: Catch exceptions for all commands. ([@Adminiuga] - [#16752]) ([light.zha docs])
+- Changed save_on_change to default to False ([@zoe1337] - [#16744]) ([light.yeelight docs])
+- Add option to disable specific integrations ([@balloob] - [#16757]) ([alexa docs]) ([cloud docs]) ([google_assistant docs])
+- Use pysonos for Sonos media player ([@amelchio] - [#16753]) ([sonos docs]) ([media_player.sonos docs])
+- deCONZ add via_hub attribute for device registry ([@Kane610] - [#16760]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([sensor.deconz docs]) ([switch.deconz docs])
+- Upgrade pysonos to 0.0.2 ([@amelchio] - [#16761])
+- Fix faulty color temp crashing google ([@balloob] - [#16758]) ([google_assistant docs])
+- Add Call Data Log platform. Mailboxes no longer require media ([@PhracturedBlue] - [#16579]) ([asterisk_mbox docs]) ([mailbox docs]) ([mailbox.asterisk_cdr docs]) ([mailbox.asterisk_mbox docs]) (new-platform)
+- Implement support for complex templates in script delays ([@rohankapoorcom] - [#16442])
+- Add Logi Circle component, camera and sensor platform ([@evanjd] - [#16540]) ([logi_circle docs]) ([camera.logi_circle docs]) ([sensor.logi_circle docs]) (new-platform)
+- Zha switch schedule update state ([@Adminiuga] - [#16621]) ([switch.zha docs])
+- Add Carbon Monoxide HomeKit Sensor ([@cdce8p] - [#16664]) ([homekit docs])
+- Add unique_id to mqtt camera ([@bieniu] - [#16569]) ([camera.mqtt docs])
+- Add tradfri device info ([@balloob] - [#16768])
+- Make rest sensor and binary sensor more efficient ([@exxamalte] - [#14484]) ([binary_sensor.rest docs]) ([sensor.rest docs])
+- Refactored units and icons for the Dyson sensors ([@glpatcern] - [#14550]) ([sensor.dyson docs]) (breaking change)
+- Add confirmation to Cast/Sonos/iOS config entries ([@balloob] - [#16769])
+- deCONZ cover support ([@Kane610] - [#16759]) ([cover docs]) ([deconz docs]) ([cover.deconz docs]) (new-platform)
+- GeoJSON platform ([@exxamalte] - [#16610]) ([geo_location docs]) (new-platform)
+- Upgrade restrictedpython to 4.0b5 ([@fabaff] - [#16779]) ([python_script docs])
+- Upgrade bimmer_connected to 0.5.2 ([@gerard33] - [#16780]) ([bmw_connected_drive docs])
+- Fix Windows loop ([@balloob] - [#16737])
+- Fix return to base logic for neato ([@dshokouhi] - [#16776]) ([vacuum.neato docs])
+- Update Tibber lib ([@Danielhiversen] - [#16795])
+- Bump pybotvac to 0.0.10 ([@dshokouhi] - [#16799]) ([neato docs])
+- Bump zm-py up to 0.0.2 ([@rohankapoorcom] - [#16800]) ([zoneminder docs])
+- Bump sucks (Ecovacs) lib to 0.9.3 ([@OverloadUT] - [#16803]) ([ecovacs docs]) ([vacuum.ecovacs docs])
+- Upgrade zeroconf to 0.21.3 ([@tadly] - [#16789])
+- Add Tuya cover state ([@huangyupeng] - [#16709]) ([cover.tuya docs])
+- Add configurable host for bbox routers ([@isonet] - [#16778])
+- Set botvac state when offline ([@dshokouhi] - [#16805]) ([vacuum.neato docs])
+- Handle netgear_lte connection errors ([@amelchio] - [#16806]) ([netgear_lte docs]) ([notify docs]) ([sensor.netgear_lte docs])
+- Improve opentherm_gw state detection ([@mvn23] - [#16809]) ([climate.opentherm_gw docs])
+- Rework chromecast fix ([@awarecan] - [#16804]) ([media_player.cast docs])
+- Add linky sensor ([@tiste] - [#16468]) ([sensor.linky docs]) (new-platform)
+- Use pyspcwebgw for SPC component ([@mbrrg] - [#16214]) ([spc docs]) ([alarm_control_panel.spc docs]) ([binary_sensor.spc docs])
+- Remove discovered MQTT Switch device when discovery topic is cleared ([@emontnemery] - [#16605]) ([mqtt docs]) ([switch.mqtt docs])
+- Allow split component definitions in packages ([@thomasloven] - [#16177])
+- Add Notify MFA module ([@awarecan] - [#16314])
+- Broadlink service name ([@Danielhiversen] - [#16345]) ([switch.broadlink docs])
+- Add Python 3.7 classifier ([@scop] - [#16645])
+- Allow soundtouch to play https content too ([@robin13] - [#16713]) ([media_player.soundtouch docs])
+- Fix some unhandled exceptions due to missing null checks ([@OverloadUT] - [#16812]) ([cover.isy994 docs]) ([light.isy994 docs])
+- Don't warn but info when on dev mode ([@balloob] - [#16831]) ([updater docs]) (beta fix)
+- Bump zm-py to 0.0.3 ([@rohankapoorcom] - [#16835]) ([zoneminder docs]) (beta fix)
+- Support old tradfri config format ([@balloob] - [#16841]) ([tradfri docs]) (beta fix)
+- Allow MQTT discovery ([@balloob] - [#16842]) ([mqtt docs]) (beta fix)
+- Add unique ID and device info to Nest camera ([@balloob] - [#16846]) ([camera.nest docs]) (beta fix)
+- Device Registry Support for iOS Sensors ([@cgarwood] - [#16862]) ([sensor.ios docs]) (beta fix)
+- Fix MQTT discovery ([@balloob] - [#16864]) ([mqtt docs]) (beta fix)
+- Make ring sync again ([@balloob] - [#16866]) ([camera.ring docs]) (beta fix)
+- Add unique_id to Nest Sensors ([@cgarwood] - [#16869]) ([binary_sensor.nest docs]) ([sensor.nest docs]) (beta fix)
+- Prevent discovered Tradfri while already configured ([@balloob] - [#16891]) ([tradfri docs]) (beta fix)
+- Handle exception handling websocket command ([@balloob] - [#16927]) ([websocket_api docs]) (beta fix)
+
+[#14484]: https://github.com/home-assistant/home-assistant/pull/14484
+[#14550]: https://github.com/home-assistant/home-assistant/pull/14550
+[#14579]: https://github.com/home-assistant/home-assistant/pull/14579
+[#16177]: https://github.com/home-assistant/home-assistant/pull/16177
+[#16214]: https://github.com/home-assistant/home-assistant/pull/16214
+[#16243]: https://github.com/home-assistant/home-assistant/pull/16243
+[#16314]: https://github.com/home-assistant/home-assistant/pull/16314
+[#16345]: https://github.com/home-assistant/home-assistant/pull/16345
+[#16353]: https://github.com/home-assistant/home-assistant/pull/16353
+[#16393]: https://github.com/home-assistant/home-assistant/pull/16393
+[#16395]: https://github.com/home-assistant/home-assistant/pull/16395
+[#16420]: https://github.com/home-assistant/home-assistant/pull/16420
+[#16426]: https://github.com/home-assistant/home-assistant/pull/16426
+[#16442]: https://github.com/home-assistant/home-assistant/pull/16442
+[#16445]: https://github.com/home-assistant/home-assistant/pull/16445
+[#16464]: https://github.com/home-assistant/home-assistant/pull/16464
+[#16468]: https://github.com/home-assistant/home-assistant/pull/16468
+[#16479]: https://github.com/home-assistant/home-assistant/pull/16479
+[#16485]: https://github.com/home-assistant/home-assistant/pull/16485
+[#16487]: https://github.com/home-assistant/home-assistant/pull/16487
+[#16489]: https://github.com/home-assistant/home-assistant/pull/16489
+[#16498]: https://github.com/home-assistant/home-assistant/pull/16498
+[#16503]: https://github.com/home-assistant/home-assistant/pull/16503
+[#16512]: https://github.com/home-assistant/home-assistant/pull/16512
+[#16520]: https://github.com/home-assistant/home-assistant/pull/16520
+[#16522]: https://github.com/home-assistant/home-assistant/pull/16522
+[#16527]: https://github.com/home-assistant/home-assistant/pull/16527
+[#16540]: https://github.com/home-assistant/home-assistant/pull/16540
+[#16547]: https://github.com/home-assistant/home-assistant/pull/16547
+[#16551]: https://github.com/home-assistant/home-assistant/pull/16551
+[#16553]: https://github.com/home-assistant/home-assistant/pull/16553
+[#16555]: https://github.com/home-assistant/home-assistant/pull/16555
+[#16563]: https://github.com/home-assistant/home-assistant/pull/16563
+[#16565]: https://github.com/home-assistant/home-assistant/pull/16565
+[#16569]: https://github.com/home-assistant/home-assistant/pull/16569
+[#16570]: https://github.com/home-assistant/home-assistant/pull/16570
+[#16571]: https://github.com/home-assistant/home-assistant/pull/16571
+[#16579]: https://github.com/home-assistant/home-assistant/pull/16579
+[#16580]: https://github.com/home-assistant/home-assistant/pull/16580
+[#16582]: https://github.com/home-assistant/home-assistant/pull/16582
+[#16588]: https://github.com/home-assistant/home-assistant/pull/16588
+[#16590]: https://github.com/home-assistant/home-assistant/pull/16590
+[#16591]: https://github.com/home-assistant/home-assistant/pull/16591
+[#16594]: https://github.com/home-assistant/home-assistant/pull/16594
+[#16597]: https://github.com/home-assistant/home-assistant/pull/16597
+[#16598]: https://github.com/home-assistant/home-assistant/pull/16598
+[#16599]: https://github.com/home-assistant/home-assistant/pull/16599
+[#16601]: https://github.com/home-assistant/home-assistant/pull/16601
+[#16602]: https://github.com/home-assistant/home-assistant/pull/16602
+[#16603]: https://github.com/home-assistant/home-assistant/pull/16603
+[#16605]: https://github.com/home-assistant/home-assistant/pull/16605
+[#16609]: https://github.com/home-assistant/home-assistant/pull/16609
+[#16610]: https://github.com/home-assistant/home-assistant/pull/16610
+[#16617]: https://github.com/home-assistant/home-assistant/pull/16617
+[#16618]: https://github.com/home-assistant/home-assistant/pull/16618
+[#16619]: https://github.com/home-assistant/home-assistant/pull/16619
+[#16621]: https://github.com/home-assistant/home-assistant/pull/16621
+[#16622]: https://github.com/home-assistant/home-assistant/pull/16622
+[#16624]: https://github.com/home-assistant/home-assistant/pull/16624
+[#16625]: https://github.com/home-assistant/home-assistant/pull/16625
+[#16626]: https://github.com/home-assistant/home-assistant/pull/16626
+[#16627]: https://github.com/home-assistant/home-assistant/pull/16627
+[#16628]: https://github.com/home-assistant/home-assistant/pull/16628
+[#16633]: https://github.com/home-assistant/home-assistant/pull/16633
+[#16636]: https://github.com/home-assistant/home-assistant/pull/16636
+[#16637]: https://github.com/home-assistant/home-assistant/pull/16637
+[#16645]: https://github.com/home-assistant/home-assistant/pull/16645
+[#16646]: https://github.com/home-assistant/home-assistant/pull/16646
+[#16649]: https://github.com/home-assistant/home-assistant/pull/16649
+[#16650]: https://github.com/home-assistant/home-assistant/pull/16650
+[#16651]: https://github.com/home-assistant/home-assistant/pull/16651
+[#16652]: https://github.com/home-assistant/home-assistant/pull/16652
+[#16654]: https://github.com/home-assistant/home-assistant/pull/16654
+[#16655]: https://github.com/home-assistant/home-assistant/pull/16655
+[#16656]: https://github.com/home-assistant/home-assistant/pull/16656
+[#16659]: https://github.com/home-assistant/home-assistant/pull/16659
+[#16664]: https://github.com/home-assistant/home-assistant/pull/16664
+[#16665]: https://github.com/home-assistant/home-assistant/pull/16665
+[#16669]: https://github.com/home-assistant/home-assistant/pull/16669
+[#16673]: https://github.com/home-assistant/home-assistant/pull/16673
+[#16674]: https://github.com/home-assistant/home-assistant/pull/16674
+[#16681]: https://github.com/home-assistant/home-assistant/pull/16681
+[#16683]: https://github.com/home-assistant/home-assistant/pull/16683
+[#16688]: https://github.com/home-assistant/home-assistant/pull/16688
+[#16699]: https://github.com/home-assistant/home-assistant/pull/16699
+[#16709]: https://github.com/home-assistant/home-assistant/pull/16709
+[#16710]: https://github.com/home-assistant/home-assistant/pull/16710
+[#16713]: https://github.com/home-assistant/home-assistant/pull/16713
+[#16718]: https://github.com/home-assistant/home-assistant/pull/16718
+[#16721]: https://github.com/home-assistant/home-assistant/pull/16721
+[#16723]: https://github.com/home-assistant/home-assistant/pull/16723
+[#16727]: https://github.com/home-assistant/home-assistant/pull/16727
+[#16729]: https://github.com/home-assistant/home-assistant/pull/16729
+[#16731]: https://github.com/home-assistant/home-assistant/pull/16731
+[#16734]: https://github.com/home-assistant/home-assistant/pull/16734
+[#16736]: https://github.com/home-assistant/home-assistant/pull/16736
+[#16737]: https://github.com/home-assistant/home-assistant/pull/16737
+[#16743]: https://github.com/home-assistant/home-assistant/pull/16743
+[#16744]: https://github.com/home-assistant/home-assistant/pull/16744
+[#16752]: https://github.com/home-assistant/home-assistant/pull/16752
+[#16753]: https://github.com/home-assistant/home-assistant/pull/16753
+[#16757]: https://github.com/home-assistant/home-assistant/pull/16757
+[#16758]: https://github.com/home-assistant/home-assistant/pull/16758
+[#16759]: https://github.com/home-assistant/home-assistant/pull/16759
+[#16760]: https://github.com/home-assistant/home-assistant/pull/16760
+[#16761]: https://github.com/home-assistant/home-assistant/pull/16761
+[#16768]: https://github.com/home-assistant/home-assistant/pull/16768
+[#16769]: https://github.com/home-assistant/home-assistant/pull/16769
+[#16776]: https://github.com/home-assistant/home-assistant/pull/16776
+[#16778]: https://github.com/home-assistant/home-assistant/pull/16778
+[#16779]: https://github.com/home-assistant/home-assistant/pull/16779
+[#16780]: https://github.com/home-assistant/home-assistant/pull/16780
+[#16789]: https://github.com/home-assistant/home-assistant/pull/16789
+[#16795]: https://github.com/home-assistant/home-assistant/pull/16795
+[#16799]: https://github.com/home-assistant/home-assistant/pull/16799
+[#16800]: https://github.com/home-assistant/home-assistant/pull/16800
+[#16803]: https://github.com/home-assistant/home-assistant/pull/16803
+[#16804]: https://github.com/home-assistant/home-assistant/pull/16804
+[#16805]: https://github.com/home-assistant/home-assistant/pull/16805
+[#16806]: https://github.com/home-assistant/home-assistant/pull/16806
+[#16809]: https://github.com/home-assistant/home-assistant/pull/16809
+[#16812]: https://github.com/home-assistant/home-assistant/pull/16812
+[#16831]: https://github.com/home-assistant/home-assistant/pull/16831
+[#16835]: https://github.com/home-assistant/home-assistant/pull/16835
+[#16841]: https://github.com/home-assistant/home-assistant/pull/16841
+[#16842]: https://github.com/home-assistant/home-assistant/pull/16842
+[#16846]: https://github.com/home-assistant/home-assistant/pull/16846
+[#16862]: https://github.com/home-assistant/home-assistant/pull/16862
+[#16864]: https://github.com/home-assistant/home-assistant/pull/16864
+[#16866]: https://github.com/home-assistant/home-assistant/pull/16866
+[#16869]: https://github.com/home-assistant/home-assistant/pull/16869
+[#16891]: https://github.com/home-assistant/home-assistant/pull/16891
+[#16927]: https://github.com/home-assistant/home-assistant/pull/16927
+[@Adminiuga]: https://github.com/Adminiuga
+[@Cereal2nd]: https://github.com/Cereal2nd
+[@Danielhiversen]: https://github.com/Danielhiversen
+[@Dullage]: https://github.com/Dullage
+[@Harvtronix]: https://github.com/Harvtronix
+[@Kane610]: https://github.com/Kane610
+[@OverloadUT]: https://github.com/OverloadUT
+[@PhracturedBlue]: https://github.com/PhracturedBlue
+[@abmantis]: https://github.com/abmantis
+[@amelchio]: https://github.com/amelchio
+[@awarecan]: https://github.com/awarecan
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bieniu]: https://github.com/bieniu
+[@cdce8p]: https://github.com/cdce8p
+[@cgarwood]: https://github.com/cgarwood
+[@cgtobi]: https://github.com/cgtobi
+[@christopheBfr]: https://github.com/christopheBfr
+[@damarco]: https://github.com/damarco
+[@danielperna84]: https://github.com/danielperna84
+[@dshokouhi]: https://github.com/dshokouhi
+[@emontnemery]: https://github.com/emontnemery
+[@evanjd]: https://github.com/evanjd
+[@exxamalte]: https://github.com/exxamalte
+[@fabaff]: https://github.com/fabaff
+[@geekofweek]: https://github.com/geekofweek
+[@gerard33]: https://github.com/gerard33
+[@glpatcern]: https://github.com/glpatcern
+[@gwww]: https://github.com/gwww
+[@heythisisnate]: https://github.com/heythisisnate
+[@hobbypunk90]: https://github.com/hobbypunk90
+[@huangyupeng]: https://github.com/huangyupeng
+[@isonet]: https://github.com/isonet
+[@jeradM]: https://github.com/jeradM
+[@kunago]: https://github.com/kunago
+[@mbrrg]: https://github.com/mbrrg
+[@mrosseel]: https://github.com/mrosseel
+[@mvn23]: https://github.com/mvn23
+[@mxworm]: https://github.com/mxworm
+[@nikolaykasyanov]: https://github.com/nikolaykasyanov
+[@pvizeli]: https://github.com/pvizeli
+[@reefab]: https://github.com/reefab
+[@robin13]: https://github.com/robin13
+[@rohankapoorcom]: https://github.com/rohankapoorcom
+[@scop]: https://github.com/scop
+[@sergeymaysak]: https://github.com/sergeymaysak
+[@smurfix]: https://github.com/smurfix
+[@soldag]: https://github.com/soldag
+[@tadly]: https://github.com/tadly
+[@thomasloven]: https://github.com/thomasloven
+[@tiste]: https://github.com/tiste
+[@tsvi]: https://github.com/tsvi
+[@vikramgorla]: https://github.com/vikramgorla
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@zoe1337]: https://github.com/zoe1337
+[alarm_control_panel.spc docs]: /components/alarm_control_panel.spc/
+[alexa docs]: /components/alexa/
+[apple_tv docs]: /components/apple_tv/
+[asterisk_mbox docs]: /components/asterisk_mbox/
+[binary_sensor.deconz docs]: /components/binary_sensor.deconz/
+[binary_sensor.homematicip_cloud docs]: /components/binary_sensor.homematicip_cloud/
+[binary_sensor.nest docs]: /components/binary_sensor.nest/
+[binary_sensor.rest docs]: /components/binary_sensor.rest/
+[binary_sensor.spc docs]: /components/binary_sensor.spc/
+[binary_sensor.wirelesstag docs]: /components/binary_sensor.wirelesstag/
+[binary_sensor.workday docs]: /components/binary_sensor.workday/
+[binary_sensor.zha docs]: /components/binary_sensor.zha/
+[bmw_connected_drive docs]: /components/bmw_connected_drive/
+[camera.axis docs]: /components/camera.axis/
+[camera.logi_circle docs]: /components/camera.logi_circle/
+[camera.mjpeg docs]: /components/camera.mjpeg/
+[camera.mqtt docs]: /components/camera.mqtt/
+[camera.nest docs]: /components/camera.nest/
+[camera.ring docs]: /components/camera.ring/
+[camera.zoneminder docs]: /components/camera.zoneminder/
+[climate.econet docs]: /components/climate.econet/
+[climate.opentherm_gw docs]: /components/climate.opentherm_gw/
+[climate.wink docs]: /components/climate.wink/
+[cloud docs]: /components/cloud/
+[config docs]: /components/config/
+[cover docs]: /components/cover/
+[cover.deconz docs]: /components/cover.deconz/
+[cover.isy994 docs]: /components/cover.isy994/
+[cover.myq docs]: /components/cover.myq/
+[cover.tuya docs]: /components/cover.tuya/
+[deconz docs]: /components/deconz/
+[device_tracker docs]: /components/device_tracker/
+[ecovacs docs]: /components/ecovacs/
+[edp_redy docs]: /components/edp_redy/
+[fan.zha docs]: /components/fan.zha/
+[geo_location docs]: /components/geo_location/
+[google_assistant docs]: /components/google_assistant/
+[hangouts docs]: /components/hangouts/
+[hassio docs]: /components/hassio/
+[homekit docs]: /components/homekit/
+[homematic docs]: /components/homematic/
+[homematicip_cloud docs]: /components/homematicip_cloud/
+[http docs]: /components/http/
+[huawei_lte docs]: /components/huawei_lte/
+[ios docs]: /components/ios/
+[konnected docs]: /components/konnected/
+[light.deconz docs]: /components/light.deconz/
+[light.isy994 docs]: /components/light.isy994/
+[light.rpi_gpio_pwm docs]: /components/light.rpi_gpio_pwm/
+[light.yeelight docs]: /components/light.yeelight/
+[light.zha docs]: /components/light.zha/
+[light.zwave docs]: /components/light.zwave/
+[logi_circle docs]: /components/logi_circle/
+[mailbox docs]: /components/mailbox/
+[mailbox.asterisk_cdr docs]: /components/mailbox.asterisk_cdr/
+[mailbox.asterisk_mbox docs]: /components/mailbox.asterisk_mbox/
+[media_extractor docs]: /components/media_extractor/
+[media_player.cast docs]: /components/media_player.cast/
+[media_player.panasonic_viera docs]: /components/media_player.panasonic_viera/
+[media_player.samsungtv docs]: /components/media_player.samsungtv/
+[media_player.sonos docs]: /components/media_player.sonos/
+[media_player.soundtouch docs]: /components/media_player.soundtouch/
+[media_player.webostv docs]: /components/media_player.webostv/
+[mqtt docs]: /components/mqtt/
+[neato docs]: /components/neato/
+[netgear_lte docs]: /components/netgear_lte/
+[notify docs]: /components/notify/
+[openuv docs]: /components/openuv/
+[persistent_notification docs]: /components/persistent_notification/
+[python_script docs]: /components/python_script/
+[rachio docs]: /components/rachio/
+[sensor.airvisual docs]: /components/sensor.airvisual/
+[sensor.deconz docs]: /components/sensor.deconz/
+[sensor.dyson docs]: /components/sensor.dyson/
+[sensor.edp_redy docs]: /components/sensor.edp_redy/
+[sensor.homematicip_cloud docs]: /components/sensor.homematicip_cloud/
+[sensor.huawei_lte docs]: /components/sensor.huawei_lte/
+[sensor.ios docs]: /components/sensor.ios/
+[sensor.jewish_calendar docs]: /components/sensor.jewish_calendar/
+[sensor.linky docs]: /components/sensor.linky/
+[sensor.logi_circle docs]: /components/sensor.logi_circle/
+[sensor.nest docs]: /components/sensor.nest/
+[sensor.netdata docs]: /components/sensor.netdata/
+[sensor.netgear_lte docs]: /components/sensor.netgear_lte/
+[sensor.qnap docs]: /components/sensor.qnap/
+[sensor.rest docs]: /components/sensor.rest/
+[sensor.rmvtransport docs]: /components/sensor.rmvtransport/
+[sensor.scrape docs]: /components/sensor.scrape/
+[sensor.shodan docs]: /components/sensor.shodan/
+[sensor.starlingbank docs]: /components/sensor.starlingbank/
+[sensor.swiss_public_transport docs]: /components/sensor.swiss_public_transport/
+[sensor.tahoma docs]: /components/sensor.tahoma/
+[sensor.tibber docs]: /components/sensor.tibber/
+[sensor.twitch docs]: /components/sensor.twitch/
+[sensor.velbus docs]: /components/sensor.velbus/
+[sensor.wirelesstag docs]: /components/sensor.wirelesstag/
+[sensor.yr docs]: /components/sensor.yr/
+[sensor.zha docs]: /components/sensor.zha/
+[shiftr docs]: /components/shiftr/
+[sonos docs]: /components/sonos/
+[spc docs]: /components/spc/
+[switch.broadlink docs]: /components/switch.broadlink/
+[switch.deconz docs]: /components/switch.deconz/
+[switch.edp_redy docs]: /components/switch.edp_redy/
+[switch.konnected docs]: /components/switch.konnected/
+[switch.mqtt docs]: /components/switch.mqtt/
+[switch.switchmate docs]: /components/switch.switchmate/
+[switch.wake_on_lan docs]: /components/switch.wake_on_lan/
+[switch.wirelesstag docs]: /components/switch.wirelesstag/
+[switch.zha docs]: /components/switch.zha/
+[tahoma docs]: /components/tahoma/
+[tradfri docs]: /components/tradfri/
+[updater docs]: /components/updater/
+[vacuum.ecovacs docs]: /components/vacuum.ecovacs/
+[vacuum.neato docs]: /components/vacuum.neato/
+[velbus docs]: /components/velbus/
+[wake_on_lan docs]: /components/wake_on_lan/
+[websocket_api docs]: /components/websocket_api/
+[wink docs]: /components/wink/
+[wirelesstag docs]: /components/wirelesstag/
+[xiaomi_aqara docs]: /components/xiaomi_aqara/
+[zha docs]: /components/zha/
+[zoneminder docs]: /components/zoneminder/

source/getting-started/configuration.markdown

@@ -36,9 +36,9 @@ From the Hass.io main panel open the add-on store.
 
 ### {% linkable_title Editing config via HASS Configurator %}
 
-The first add-on we should install is the HASS Configurator. With the HASS Configurator you'll be able to edit your Home Assistant configuration from the web interface.
+The first add-on we should install is the HASS Configurator. With the HASS Configurator, you'll be able to edit your Home Assistant configuration from the web interface.
 
-Go to the add-on store (see previous step), click on Configurator and click on "INSTALL". When installation is complete, the UI will go to the add-on details page for the configurator. Here you will be able to change settings, start and stop the add-on. Follow the steps below to setup the add-on.
+Go to the add-on store (see the previous step), click on Configurator and click on "INSTALL". When installation is complete, the UI will go to the add-on details page for the configurator. Here you will be able to change settings, start and stop the add-on. Follow the steps below to setup the add-on.
 
  - Set a password on the Config box, don't forget to use quotes on your password
  

source/getting-started/index.markdown

@@ -9,7 +9,7 @@ sharing: true
 footer: true
 ---
 
-The goal of this getting started guide is to install [Hass.io](/hassio/) on a Raspberry Pi. Hass.io is our own all in one solution that turns your Raspberry Pi or other device into the ultimate home automation hub.
+The goal of this getting started guide is to install [Hass.io](/hassio/) on a Raspberry Pi. Hass.io is our own all in one solution that turns your Raspberry Pi or another device into the ultimate home automation hub.
 
 Follow this guide if you want to get started with Home Assistant easily, or if you have no or little Linux experience. For advanced users or if you have no Raspberry Pi at hand, check our [alternative installation methods](/docs/installation/). The [FAQ](/faq/#home-assistant-vs-hassio) explains more about the differences.
 

source/getting-started/presence-detection.markdown

@@ -27,13 +27,13 @@ Screenshot of Home Assistant showing a school, work and home zone and two people
 
 The device tracker component offers presence detection for Home Assistant. It supports three different methods for presence detection: scan for connected devices on the local network, scan for Bluetooth devices within range, and connect to third-party service.
 
-Scanning for connected devices is easy to setup; options include [supported routers][routers] and [scanning the network using nmap][nmap]. This approach does have its limitations, however: it will only be able to detect if a device is at home, and modern smartphones may show as not home inaccurately (as they disconnect from WiFi if idle).
+Scanning for connected devices is easy to setup; options include [supported routers][routers] and [scanning the network using Nmap][nmap]. This approach does have its limitations, however: it will only be able to detect if a device is at home, and modern smartphones may show as not home inaccurately (as they disconnect from WiFi if idle).
 
 You can scan for [Bluetooth][ha-bluetooth] and [Bluetooth LE][ha-bluetooth-le] devices. Unlike with WiFi, modern smartphones don't turn off Bluetooth automatically, though the range is lower.
 
 Home Assistant currently supports multiple third-party services for presence detection, such as [OwnTracks over MQTT][ha-owntracks-mqtt], [OwnTracks over HTTP][ha-owntracks-http] [GPSLogger][ha-gpslogger] and [Locative][ha-locative].
 
-There are a wide [range of options][ha-presence] available, both for scanning your local network and third-party services.
+There is a wide [range of options][ha-presence] available, both for scanning your local network and third-party services.
 
 ### {% linkable_title Zones %}
 

source/hassio/installation.markdown

@@ -23,8 +23,8 @@ Hass.io images are available for:
 - As [Virtual Appliance]:
   - [VMDK][vmdk]
 
-<p class='note'>
-Please remember to ensure you're using an [appropriate power supply](https://www.raspberrypi.org/help/faqs/#powerReqs) with your Pi. Mobile chargers may not be suitable since some were only designed to provide just enough power to the device it was designed for by the manufacturer.
+<p class='note warning'>
+Please remember to ensure you're using an [appropriate power supply](https://www.raspberrypi.org/help/faqs/#powerReqs) with your Pi. Mobile chargers may not be suitable since some were only designed to provide just enough power to the device it was designed for by the manufacturer. **Do not** try to power the Pi from the USB port on a TV, computer, or similar.
 </p>
 
 - Flash the downloaded image to an SD card using [Etcher][etcher]. We recommend at least a 32 GB SD card to avoid running out of space.
@@ -77,14 +77,14 @@ A detailed guide about running Hass.io as a virtual machine is available in the
 [etcher]: https://etcher.io/
 [Virtual Appliance]: https://github.com/home-assistant/hassos/blob/dev/Documentation/boards/ova.md
 [hassos-network]: https://github.com/home-assistant/hassos/blob/dev/Documentation/network.md
-[pi0-w]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi0-w-1.10.img.gz
-[pi1]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi-1.10.img.gz
-[pi2]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi2-1.10.img.gz
-[pi3-32]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi3-1.10.img.gz
-[pi3-64]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi3-64-1.10.img.gz
+[pi0-w]: https://github.com/home-assistant/hassos/releases/download/1.11/hassos_rpi0-w-1.11.img.gz
+[pi1]: https://github.com/home-assistant/hassos/releases/download/1.11/hassos_rpi-1.11.img.gz
+[pi2]: https://github.com/home-assistant/hassos/releases/download/1.11/hassos_rpi2-1.11.img.gz
+[pi3-32]: https://github.com/home-assistant/hassos/releases/download/1.11/hassos_rpi3-1.11.img.gz
+[pi3-64]: https://github.com/home-assistant/hassos/releases/download/1.11/hassos_rpi3-64-1.11.img.gz
 [tinker]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_tinker-2.2.img.gz
 [odroid-c2]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_odroid-c2-2.2.img.gz
-[vmdk]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_ova-1.10.vmdk
+[vmdk]: https://github.com/home-assistant/hassos/releases/download/1.11/hassos_ova-1.11.vmdk
 [linux]: https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio
 [local]: http://hassio.local:8123
 [samba]: /addons/samba/

source/hassio/zwave.markdown

@@ -42,6 +42,16 @@ zha:
   database_path: /config/zigbee.db
 ```
 
+### {% linkable_title Finding the path %}
+
+If the above defaults don't work, you can check what hardware has been found using the [hassio command](/hassio/commandline/#hardware):
+
+```bash
+$ hassio hardware info
+```
+
+Or you can use the UI and look in the *System* section of the *Hass.io* menu. There you'll find a *Hardware* button which will list all the hardware found.
+
 ## {% linkable_title Further reading %}
 
 For more information on using Z-Wave, see the [main documentation](/docs/z-wave/).

source/index.html

@@ -8,7 +8,7 @@ hero_unit: true
 is_homepage: true
 regenerate: true
 hide_github_edit: true
-description: Open-source home automation platform running on Python 3. Track and control all devices at home and automate control. Installation in less than a minute.
+description: Open source home automation that puts local control and privacy first.
 ---
 
 <div class="frontpage">
@@ -24,7 +24,7 @@ description: Open-source home automation platform running on Python 3. Track and
       </div>
       <div class='join-community material-card text'>
         <h1>Join The Community</h1>
-        We love to help &amp; talk home automation.
+        We love to help with &amp; talk about home automation.
 
         <div class='links'>
           <a href='https://community.home-assistant.io'>Forums</a>

source/ios/beta.markdown

@@ -0,0 +1,12 @@
+---
+layout: page
+title: "Join Home Assistant iOS beta"
+description: "Invititation to join the Home Assistant iOS beta."
+release_date: 2016-10-24 15:00:00 -0700
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+<script>document.location.href = 'https://testflight.apple.com/join/XCUga7ko';</script>