Merge branch 'current' into next

source/_integrations/alexa.smart_home.markdown

@@ -173,6 +173,7 @@ Alexa can link your Amazon account to your Home Assistant account. Therefore Hom
 - Input all information required. Assuming your Home Assistant can be accessed by https://[YOUR HOME ASSISTANT URL:PORT]
   * `Authorization URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize
   * `Access Token URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/token
+    - Note: you must use a valid/trusted SSL Certificate and port 443 for account linking to work
   * `Client ID`:
     - https://pitangui.amazon.com/ if you are in US
     - https://layla.amazon.com/ if you are in EU

source/_integrations/deconz.markdown

@@ -393,6 +393,8 @@ The `entity_id` names will be `light.device_name`, where `device_name` is define
 - IKEA Trådfri Bulb E27 WS & RGB Opal 600lm
 - IKEA Trådfri Bulb GU10 W 400lm
 - IKEA Trådfri FLOALT LED light panel
+- Innr BY-265, BY-245
+- OSRAM Classic A60 W clear - LIGHTIFY
 - OSRAM Flex RGBW
 - OSRAM Gardenpole RGBW
 - Philips Hue White A19
@@ -436,6 +438,8 @@ The `entity_id` name will be `sensor.device_name`, where `device_name` is define
   - Xiaomi Smart Home Wireless Switch
 - Temperature Sensor
   - Xiaomi Temperature/Humidity Sensor
+- OpenClose Sensor
+  - Xiaomi Window / Door Sensor with Temperature
 
 ### deCONZ Daylight Sensor
 

source/_integrations/emulated_hue.markdown

@@ -145,14 +145,24 @@ These attributes used to be found under the `customize` section of `homeassistan
 
 You can verify that the `emulated_hue` integration has been loaded and is responding by pointing a local browser to the following URL:
 
-- `http://<HA IP Address>:8300/description.xml` - This URL should return a descriptor file in the form of an XML file.
+- `http://<HA IP Address>:80/description.xml` - This URL should return a descriptor file in the form of an XML file.
-- `http://<HA IP Address>:8300/api/pi/lights` - This will return a list of devices, lights, scenes, groups, etc.. that `emulated_hue` is exposing to Alexa.
+- `http://<HA IP Address>:80/api/pi/lights` - This will return a list of devices, lights, scenes, groups, etc.. that `emulated_hue` is exposing to Alexa.
 
-For Google Home, verify that the URLs above are using port 80, rather than port 8300 (i.e. `http://<HA IP Address>:80/description.xml`).
+Verify that the URLs above are using port 80, rather than port 8300 (i.e. `http://<HA IP Address>:80/description.xml`). Both Google Home and Amazon Alexa/Echo (as of the 2019-08 firmware) require port 80.
 
-For Amazon Alexa/Echo, verify that the URLs above are using port 80, rather than port 8300 (i.e. `http://<HA IP Address>:80/description.xml`). Since 2019-08 Amazon Echo firmware, Alexa no longer works with port 8300.
+### Platform specific instructions
 
-An additional step is required to run Home Assistant as a non-root user and use port 80 when using the AiO script.  Execute the following command to allow `emulated_hue` to use port 80 as a non-root user.
+#### Hass.io and Docker
+
+No further actions are required
+
+#### Python venv
+
+An additional step is required to run Home Assistant as a non-root user and use port 80. 
+
+##### Linux
+
+On Linux systems (Ubuntu, Debian, etc) execute the following command to allow `emulated_hue` to use port 80 as a non-root user:
 
 ```bash
 sudo setcap 'cap_net_bind_service=+ep' /srv/homeassistant/homeassistant_venv/bin/python3
@@ -160,6 +170,20 @@ sudo setcap 'cap_net_bind_service=+ep' /srv/homeassistant/homeassistant_venv/bin
 
 Please note that your path may be different depending on your installation method. For example, if you followed the [Virtualenv instructions](/docs/installation/virtualenv/), your path will be `/srv/homeassistant/bin/python3`.
 
+##### FreeBSD and FreeNAS
+
+On FreeBSD based systems, including FreeNAS, execute the following to allow `emulated_hue` to use port 80 as a non-root user:
+
+```bash
+sysctl net.inet.ip.portrange.reservedhigh=0
+```
+
+You can make this persist by adding the following to `/etc/sysctl.conf`:
+
+```bash
+net.inet.ip.portrange.reservedhigh=0
+```
+
 ### License
 
 Much of this code is based on work done by Bruce Locke on his [ha-local-echo](https://github.com/blocke/ha-local-echo) project, originally released under the MIT License. The license is located [here](https://github.com/blocke/ha-local-echo/blob/b9bf5dcaae6d8e305e2283179ffba64bde9ed29e/LICENSE).

source/_integrations/mcp23017.markdown

@@ -14,6 +14,8 @@ The `mcp23017` integration is the base for all related mcp23017 platforms in Hom
 
 For more details about the MCP23017 I2C I/O port expander you can find its datasheet here: [MCP23017](https://www.microchip.com/wwwproducts/en/MCP23017).
 
+If you are using Hass.io on HassOS you can’t use existing methods to enable the I2C bus on a Raspberry Pi, you will have to [enable the I2C interface in the Hass.io configuration](https://github.com/home-assistant/hassos/blob/dev/Documentation/boards/raspberrypi.md#i2c) using a USB stick. To accomplish that, follow this step by step instructions: [Enable HassOS i2c](https://www.home-assistant.io/hassio/enable_i2c).
+
 ## Binary Sensor
 
 The `mcp23017` binary sensor platform allows you to read sensor values from the I/O pins of your [MCP23017 I2C I/O expander](https://www.adafruit.com/product/732).

source/_integrations/sesame.markdown

@@ -12,7 +12,7 @@ The `sesame` platform allows you to control your [Sesame](https://candyhouse.co/
 
 ## Configuration
 
-Your Sesame needs to be paired with a mobile device running the app in *virtual station* mode, or a standalone [Wi-Fi Access Point](https://candyhouse.co/collections/frontpage/products/wi-fi-access-point).
+Your Sesame needs to be paired with a standalone [Wi-Fi Access Point](https://candyhouse.co/collections/frontpage/products/wi-fi-access-point) purchased separately.
 
 You will also need to generate an API key from [my.candyhouse.co](https://my.candyhouse.co/#/credentials).
 

source/_integrations/spotify.markdown

@@ -28,10 +28,10 @@ To create the required Spotify application:
 - Add a **Redirect URI** in one of the following forms:
 
  If you are not using SSL:
-  `http://<your_home_assistant_url_or_local_ip>:<port>/api/spotify`
+  `http://<your_home_assistant_url_or_local_ip>/api/spotify`
 
  If you are using SSL:
-  `https://<your_home_assistant_url_or_local_ip>:<port>/api/spotify`
+  `https://<your_home_assistant_url_or_local_ip>/api/spotify`
 
 - Click **Save** after adding the URI.
 

source/_integrations/webostv.markdown

@@ -149,7 +149,7 @@ data:
 
 ### Next/Previous buttons
 
-The behaviour of the next and previsous buttons is different depending on the active source:
+The behaviour of the next and previous buttons is different depending on the active source:
 
  - if the source is 'LiveTV' (television): next/previous buttons act as channel up/down
  - otherwise: next/previous buttons act as next/previous track

source/lovelace/views.markdown

@@ -85,7 +85,7 @@ View config:
 
 ## Paths
 
-You can link to one view from another view by its path. For this use cards that support navigation (`navigation_path`). Do not use special characters in paths.
+You can link to one view from another view by its path. For this use cards that support navigation (`navigation_path`). Do not use special characters in paths. Do not begin a path with a number. This will cause the parser to read your path as a view index.
 
 ### Example