Merge remote-tracking branch 'origin/master' into next

Conflicts:
	source/_posts/2016-07-16-sqlalchemy-knx-join-simplisafe.markdown

source/_components/binary_sensor.http.markdown

@@ -32,6 +32,7 @@ For a quick test `curl` can be useful to "simulate" a device.
 
 ```bash
 $ curl -X POST -H "x-ha-access: YOUR_PASSWORD" \
+    -H "Content-Type: application/json" \
     -d '{"state": "off", "attributes": {"friendly_name": "Radio"}}' \
     http://localhost:8123/api/states/binary_sensor.radio
 ```

source/_components/camera.local_file.markdown

@@ -15,7 +15,7 @@ ha_release: 0.22
 
 The `local_file` camera platform allows you to integrate any readable image file from disk into Home Assistant as a camera. If the image is updated on the file system the image displayed in Home Assistant will also be updated.
 
-This can for example be used with various camera platforms that save a temporary images locally. It can also be used to display a graph that you render periodacally and will then be displayed in Home Assistant.
+This can for example be used with various camera platforms that save a temporary images locally. It can also be used to display a graph that you render periodically and will then be displayed in Home Assistant.
 
 To enable this camera in your installation, add the following to your `configuration.yaml` file:
 

source/_components/device_tracker.nmap_scanner.markdown

@@ -29,7 +29,7 @@ device_tracker:
 
 Configuration variables:
 
-- **hosts** (*Required*): Thenetwork range to scan in CIDR notation, eg. 192.168.1.1/24
+- **hosts** (*Required*): The network range to scan in CIDR notation, eg. 192.168.1.1/24
 - **home_interval** (*Optional*): The number of minutes nmap will not scan this device, assuming it is home, in order to preserve the device battery.
 
 See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.

source/_components/hdmi_cec.markdown

@@ -8,7 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Automation
-featured: false
+logo: hdmi.png
 ha_release: 0.23
 ha_iot_class: "Local Push"
 ---
@@ -23,11 +23,33 @@ The computer running Home Assistant must support CEC, and of course be connected
 
 ### {% linkable_title libcec %}
 
-[libcec](https://github.com/Pulse-Eight/libcec) must be installed for this component to work. Follow the installation instructions for your environment, provided at the link. `libcec` installs Python 3 bindings, by default as a system Python module. If you are running Home Assistant in a Python virtual environment, make sure it can access the system module, by either symlinking it or using the `--system-site-packages` flag.
+[libcec](https://github.com/Pulse-Eight/libcec) must be installed for this component to work. Follow the installation instructions for your environment, provided at the link. `libcec` installs Python 3 bindings by default as a system Python module. If you are running Home Assistant in a [Python virtual environment](/getting-started/installation-virtualenv/), make sure it can access the system module, by either symlinking it or using the `--system-site-packages` flag.
 
 #### {% linkable_title Symlinking into virtual environment %}
 
-`ln -s /usr/local/lib/python3.4/dist-packages/cec <your venv>/lib/python3.4/site-packages`
+Create a symlink to the `cec` installation.
+ 
+```bash
+$ ln -s /usr/local/lib/python3.4/dist-packages/cec /path/to/your/venv/lib/python3.4/site-packages
+```
+
+For the default virtual environment of a [Raspberry Pi AIO](/getting-started/installation-raspberry-pi-all-in-one/) the command would be as follows.
+
+```bash
+$ ln -s /usr/local/lib/python3.4/dist-packages/cec /srv/hass/hass_venv/lib/python3.4/site-packages
+```
+
+If after symlinking and adding `hdmi_cec:` to your configuration you are getting the following error in your logs, 
+
+```bash
+* failed to open vchiq instance
+```
+
+you will also need to add the user account Home Asssistant runs under, to the `video` group. To add the Home Assisitant's user account to the `video` group run the following command.
+
+```bash
+$ usermod -a -G video <hass_user_account>
+```
 
 ## {% linkable_title Configuration Example %}
 
@@ -54,7 +76,15 @@ Call the `hdmi_cec/select_device` service with the name of the device to select,
   "device": "Chromecast"
 }
 ```
+So an Automation action using the example above would look something like this.
 
+```yaml
+action:
+  service: hdmi_cec.select_device
+    data:
+      device: Chromecast
+```
+      
 ### {% linkable_title Power On %}
 
 Call the `hdmi_cec/power_on` service (no arguments) to power on any devices that support this function.

source/_components/http.markdown

@@ -13,6 +13,10 @@ ha_category: "Other"
 
 The `http` component serves all files and data required for the Home Assistant frontend. You only need to add this to your configuration file if you want to change any of the default settings.
 
+<p class='note warning'>
+It's HIGHLY recommended that you set the `api_password`, especially if you are planning to expose your installation to the internet.
+</p>
+
 ```yaml
 # Example configuration.yaml entry
 http:

source/_components/light.mqtt.markdown

@@ -79,3 +79,5 @@ Configuration variables:
   Make sure that your topics match exact. `some-topic/` and `some-topic` are different topics.
 </p>
 
+A basic example using a nodeMCU board (ESP8266) to control its built-in led (on/off) can be found [here](https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_light). [Here](https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_rgb_light) is another example to control a RGB led (on/off, brightness and colors).
+

source/_components/media_player.onkyo.markdown

@@ -31,7 +31,7 @@ media_player:
 ```
 Configuration variables:
 - **host** (*Optional*): IP address of the device. Example:`192.168.1.2` If not specified, the platform will load any discovered receivers.
-- **name** (*Optional, required if host is specified*): Name of the device
+- **name** (*Required if host is specified*): Name of the device
 - **sources** (*Optional*): A list of mappings from source to source name. Valid sources can be found below. A default list will be used if no source mapping is specified.
 
 List of source names:

source/_components/media_player.samsungtv.markdown

@@ -44,8 +44,12 @@ Currently known supported models:
 - F6500
 - EH5600
 - F6400AF
-
+ 
 If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io).
 The two letters at the beginning of the model number represent the region, UE is Europe, UN is North America and UA is Asia & Australia. The two numbers following that represent the screen size. If you add your model remember to remove these before adding them to the list.
 
 There's currently a [known issue](https://github.com/home-assistant/home-assistant/issues/2098) with some TV's receiving a *Key press UP* that can interrupt certain applications. 
+
+Currently tested but not working models:
+
+- KU6300 - Shows in GUI but unable to control.

source/_components/notify.aws_sns.markdown

@@ -40,3 +40,23 @@ Configuration variables:
 AWS SNS is a notify platform and thus can be controlled by calling the notify service [as described here](/components/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](http://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)). For more information, please see the [boto3 docs](http://boto3.readthedocs.io/en/latest/reference/services/sns.html#SNS.Client.publish).
 
 If one exists, the SNS Subject will be set to the title. All attributes from the payload except message will be sent as stringified message attributes.
+
+#### {% linkable_title Setting up SNS within AWS %}
+
+- Log into your AWS console and under "Security and Identity", select "Identity & Access Management".
+- On the left hand side, select "Users" then click "Create New Users". Enter a name here and then click "Create". 
+- You can either download the credentials or click the arrow to display them one time.
+
+<p class='note warning'>
+  If you do not download them you will lose them and will have to recreate a new user.
+</p>
+
+- Copy/Paste the two keys that you are provided here in your `configuration.yaml` file respectively.
+- On the left hand side of the screen go back to "Users" and select the user you just created. On the "Permissions" tab click the "Attach Policy" icon. Search for "SNS" and attach the policy "AmazonSNSFUullAccess".
+- Back to the AWS Console you now need to find "SNS" and click in to that service. It is under the Mobile Services group.
+- On the left hand side, select "Topics" then "Create new topic".
+- Choose a Topic Name and Display Name.
+- Now check the box next to the Topic you just created and under Actions, select "Subscribe to topic".
+- In the box that pops up, select the Protocol = SMS and enter in the phone number next to "Endpoint" you wish to SMS. Now click "Create".
+- Repeat for additional numbers.
+- Back in the "Users" section you will see a long alphanumeric line that starts with "arn:" and ends with the Topic Name you choose previously. This is what your "target" in Home Assistant will be.

source/_components/sensor.speedtest.markdown

@@ -74,3 +74,5 @@ Configuration variables:
 - **day** (*Optional*): Specify the day(s) of the month to schedule the speedtest. Use a list for multiple entries. Default is None.
 
 This component uses [speedtest-cli](https://github.com/sivel/speedtest-cli) to gather network performance data from Speedtest.net.  Please be aware of the potential [inconsistencies](https://github.com/sivel/speedtest-cli#inconsistency) that this component may display.
+
+When Home Assistant first starts up, the values of the speedtest will show as `Unknown`. You can use the service `sensor.update_speedtest` to run a manual speedtest and populate the data or just wait for the next regularly scheduled test.