Add blog post 0.21

source/_components/lirc.markdown

@@ -0,0 +1,95 @@
+---
+layout: page
+title: "LIRC"
+description: "Instructions how to integrate IR remotes with LIRC into Home Assistant."
+date: 2016-05-22 19:59
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: lirc.gif
+ha_category: Automation
+featured: false
+ha_release: 0.21
+ha_iot_class: "Local Push"
+---
+
+[LIRC](http://www.lirc.org/) integration for Home Assistant allows you to receive signals from an infrared remote control and control actions based on the buttons you press. You can use them to set scenes or trigger any other [automation](https://home-assistant.io/components/automation/).
+
+Sending IR commands is not supported in this component (yet), but can be accomplished using the [shell_command component](https://home-assistant.io/components/shell_command/) in conjunction with the `irsend` command.
+
+### {% linkable_title Installation %}
+
+To allow Home Assistant to talk to your IR receiver, you need to first make sure you have the correct dependencies installed:
+
+```bash
+$ sudo apt-get install lirc
+```
+
+<p class='note'>
+If you are configuring on a Raspberry Pi, there are excellent instructions with GPIO schematics and driver configurations [here](http://alexba.in/blog/2013/01/06/setting-up-lirc-on-the-raspberrypi/). Consider following these.
+</p>
+
+
+Now teach LIRC about your particular remote control by preparing a lircd configuration file (`/etc/lirc/lircd.conf`). Search the [LIRC remote database](http://lirc.sourceforge.net/remotes/) for your model. If you can't find it, then you can always use the `irrecord` program to learn your remote. This will create a valid configuration file. Add as many remotes as you want by pasting them into the file. If `irrecord` doesn't work (e.g. for some air conditioner remotes), then the `mode2` program is capable of reading the codes in raw mode, followed by `irrecord -a` to extract hex codes.
+
+Next, you have to make a `~/.lircrc` file that maps keypresses to system actions. [The configuration](http://www.lirc.org/html/configure.html) is a bit tedious but it must be done. Use the `prog = home-assistant` for all keys you want to be recognized by Home Assistant. The values you set for `button` must be the same as in the `lircd.conf` file and the values you put for `config` entry will be the sensor value in Home Assistant when you press the button. An example may look like this:
+
+```bash
+begin
+    remote = SONY
+    button = KEY_1
+    prog   = home-assistant
+    config = KEY_1
+end
+begin
+    remote = SONY
+    button = KEY_2
+    prog   = home-assistant
+    config = KEY_2
+end
+begin
+    remote = SONY
+    button = KEY_3
+    prog   = home-assistant
+    config = KEY_3
+end
+```
+
+Test your LIRC installation before proceeding by running:
+
+```bash
+$ irexec -n home-assistant
+```
+
+and pressing some buttons on the remote.
+
+
+### {% linkable_title Configuration %}
+
+```yaml
+# Example configuration.yaml entry
+lirc:
+```
+
+
+#### {% linkable_title Events %}
+
+The LIRC component fires `ir_command_received` events on the bus. You can capture the events and respond to them in automation scripts like this:
+
+```yaml
+# Example configuration.yaml automation entry
+automation:
+- alias: Off on Remote
+  trigger:
+    platform: event
+    event_type: ir_command_received
+    event_data:
+      button_name: KEY_0
+  action:
+    service: homeassistant.turn_off
+    entity_id: group.a_lights
+
+```
+
+The `button_name` data values (e.g. `KEY_0`) are set by you in the `.lircrc` file.

source/_components/sensor.dte_energy_bridge.markdown

@@ -0,0 +1,21 @@
+---
+layout: page
+title: "DTE Energy Bridge"
+description: "Instructions how to setup DTE Energy Bridge with Home Assistant."
+date: 2016-06-07 08:10
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category: Sensor
+ha_release: 0.21
+ha_iot_class: "Cloud Polling"
+---
+
+A sensor for the DTE Energy Bridge
+
+```yaml
+sensor:
+    platform: dte_energy_bridge
+    ip: 192.168.1.11
+```

source/_components/switch.flux.markdown

@@ -29,14 +29,14 @@ If you don't wish to have flux update on 30 second intervals, you can leave the
 switch turned off and use automation rules that call the service `switch.flux_update`
 whenever you want the lights updated.
 
-Example `configuration.yaml`:
 ```yaml
+# Example configuration.yaml entry
 switch:
   platform: flux
   lights:
     - light.desk
     - light.lamp
-  name: Fluxer		      # optional, default Flux
+  name: Fluxer            # optional, default Flux
   start_time: 7:00        # optional, default sunrise
   stop_time: 23:00        # optional, default 22:00
   start_colortemp: 4000   # optional, default 4000

source/_posts/2016-06-08-super-fast-web-enocean-lirc.markdown

@@ -0,0 +1,74 @@
+---
+layout: post
+title: "0.21: Improved Web and support for EnOcean, LIRC and Osram Lightify"
+description: "This new release of Home Assistant is lightning fast with the new web stack and progressive web application. On top of that a handful of new components and platforms for EnOcean, LIRC and Osram Lightify support."
+date: 2016-06-08 01:06:00 +0000
+date_formatted: "June 8, 2016"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+---
+
+It's time for release 0.21 and it contains massive core improvements: replacement of our home grown HTTP stack with a standardized WSGI stack. This will improve performance, speed, security and make future development of advanced HTTP features a breeze.
+
+This work was driven by the amazing Josh Wright. His knowledge, high standards and drive for security has helped improve Home Assistant a lot ever since he started helping out. Hip hip hurray for Josh!
+
+Alright, time for the changes:
+
+<img src='/images/supported_brands/enocean.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/osramlightify.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/lirc.gif' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
+
+ - New HTTP stack based on WSGI ([@JshWright], [@balloob])
+ - Frontend: lots of performance improvements ([@balloob])
+ - Initial support for EnOcean [lights][en-lights], [sensors][en-sensors] and [switches][en-switches] added ([@rubund])
+ - Light: [Osram Lightify] is now supported ([@olimpiurob])
+ - Light: [Insteon Hub] now supports brightness ([@wkonkel])
+ - Add support for adding HA as Windows 10 tile ([@fabaff])
+ - Condition: [time condition] can now cross midnight ([@jaharkes])
+ - Template based sensors should now throw less warnings ([@Bart247])
+ - New [LIRC component] allows receiving IR commands ([@partofthething])
+ - The [Feedreader] component will now persist data to disk to prevent duplicate events ([@shaftoe])
+ - Sun: azimuth attribute added ([@fabaff])
+ - New [Flux like switch platform] to change light intensity in the evening ([@nkgilley])
+ - We no longer crash if you live in a part of the world where the sun never sets ([@balloob])
+ - Rollershutter: [RFXTRX] now supported ([@jacobtomlinson])
+ - Switch: [Template switches] can now execute scripts ([@kellerza])
+ - Z-Wave: automatically heal the network at midnight ([@infamy])
+ - Sensor: [DTE Energy Bridge] now supported ([@kylehendricks])
+ - Media Player: [Kodi] now supports different turn off commands ([@armills])
+
+### Breaking Changes
+
+ - Our work in the WSGI stack is not fully done yet. We still have a minor issues where retrieving the error log in the about screen can raise an encoding error
+ - The API used to incorrectly accept a JSON body with form-url-encoded headers. Our cURL examples on the website used to be wrong and have [been updated].
+
+[@armills]: https://github.com/armills
+[@balloob]: https://github.com/balloob
+[@Bart247]: https://github.com/Bart247
+[@fabaff]: https://github.com/fabaff
+[@infamy]: https://github.com/infamy
+[@jacobtomlinson]: https://github.com/jacobtomlinson
+[@jaharkes]: https://github.com/jaharkes
+[@JshWright]: https://github.com/JshWright
+[@kellerza]: https://github.com/kellerza
+[@kylehendricks]: https://github.com/kylehendricks
+[@nkgilley]: https://github.com/nkgilley
+[@olimpiurob]: https://github.com/olimpiurob
+[@partofthething]: https://github.com/partofthething
+[@rubund]: https://github.com/rubund
+[@shaftoe]: https://github.com/shaftoe
+[@wkonkel]: https://github.com/wkonkel
+[DTE Energy Bridge]: /components/sensor.dte_energy_bridge/
+[en-lights]: /components/light.enocean/
+[en-sensors]: /components/sensor.enocean/
+[en-switches]: /components/switch.enocean/
+[Feedreader]: /components/feedreader/
+[Flux like switch platform]: /components/switch.flux/
+[Insteon Hub]: /components/insteon_hub/
+[Kodi]: /components/media_player.kodi/
+[LIRC component]: /components/lirc/
+[Osram Lightify]: /components/light.osramlightify/
+[RFXTRX]: /components/rfxtrx/
+[Template switches]: /components/switch.template/
+[time condition]: /getting-started/scripts-conditions/#time-condition
+[been updated]: /developers/rest_api/