Merge branch 'master' into next

source/developers/credits.markdown

@@ -51,7 +51,7 @@ This page contains a list of people who have contributed in one way or another t
 - [Dale Higgs](https://github.com/dale3h)
 - [Dan Cinnamon](https://github.com/Cinntax)
 - [Daniel Perna](https://github.com/danielperna84)
-- [Daniel Iversen](https://github.com/danielhiversen)
+- [Daniel Høyer Iversen](https://github.com/danielhiversen)
 - [Daniel J. Kemp](https://github.com/danieljkemp/)
 - [Daniel Matuschek](https://github.com/usul27)
 - [Dan Smith](https://github.com/kk7ds)

source/developers/platform_example_light.markdown

@@ -11,6 +11,20 @@ footer: true
 
 This example is for adding support for the imaginary Awesome Lights. It shows the different best practices for developing a platform.
 
+Similar to Example Sensor Platform, Copy the code below and create it as a file in `<config_dir>/custom_components/light/awesomelights.py`.
+
+Add the following to your configuration.yaml:
+
+```yaml
+light:
+  - platform: awesomelights
+    host: HOST_HERE
+    username: USERNAME_HERE
+    password: PASSWORD_HERE_OR_secrets.yaml
+```
+
+Note the `platform` name matches the filename for the source code.
+
 ```python
 import logging
 

source/developers/platform_example_sensor.markdown

@@ -37,7 +37,7 @@ def setup_platform(hass, config, add_devices, discovery_info=None):
 class ExampleSensor(Entity):
     @property
     def name(self):
-        return 'Temperature'
+        return 'Example Temperature'
 
     @property
     def state(self):

source/developers/releasing.markdown

@@ -15,8 +15,10 @@ This page describes the steps for publishing a new Home Assistant release.
 
 1. Create a pull request from `dev` to `master` with the upcoming release number as title.
 2. Merge `master` into `dev` to make the PR mergable. PR message contains intro, highlighting major changes, and an overview of all changes tagging each author.
-3. Merge pull request.
-4. Go to [releases](https://github.com/home-assistant/home-assistant/releases) and tag a new release on the `master` branch. Tag name and title name are version number. Release description is text from PR.
+3. Update `homeassistant/const.py` with the correct version number (remove the the `dev` tag) and push that commit.
+4. Merge pull request.
+5. Then, after merged, push another update to `dev` of `homeassistant/const.py` that includes the next version with the `dev` tag. Add a meaningful commit message like "Version bump to X". This commit acts as marker for the next release.
+6. Go to [releases](https://github.com/home-assistant/home-assistant/releases) and tag a new release on the `master` branch. "Tag version" and "Release title" are the version number (`O.x` for major version, `0.x.y` for minor and bug fix releases). Release description is the text from PR. Press "Publish release" to finish the process.
 
 ### {% linkable_title Website %}
 
@@ -29,7 +31,7 @@ This page describes the steps for publishing a new Home Assistant release.
 
 ### {% linkable_title Python Package Index %}
 
-Checkout `master` branch and run `script/release` to publish the new release on [Python Package Index](https://pypi.python.org)
+Checkout the `master` branch and run `script/release` to publish the new release on [Python Package Index](https://pypi.python.org).
 
 ### {% linkable_title Social media %}
 

source/developers/server_sent_events.markdown

@@ -44,6 +44,12 @@ Visit [http://localhost:8123/local/sse.html](http://localhost:8123/local/sse.htm
 
 ## {% linkable_title Examples %}
 
+The simplest way to consume server-sent events is `curl`.
+
+```bash
+$ curl http://localhost:8123/api/stream?api_password=MYPASS
+```
+
 ### {% linkable_title Website %}
 
 The [home-assistant-sse](https://github.com/fabaff/home-assistant-sse) repository contains an more advanced example.