Finalize release 0.10 blogpost

source/_components/alexa.markdown

@@ -14,19 +14,27 @@ featured: false
 
 The Alexa component allows you to integrate Home Assistant into Alexa/Amazon Echo. This component will allow you to query information within Home Assistant by using your voice. There are no supported sentences out of the box as of now, you will have to define them all yourself. This component does not yet allow the control of devices connected to Home Assistant.
 
+<p style='text-align: center;'>
+<iframe width="560" height="315" src="https://www.youtube.com/embed/1Ke3mtWd_cQ" frameborder="0" allowfullscreen></iframe>
+</p>
+
+
 ### Requirements before using
 Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are ok because our skills will only run in development mode. Read more on [our blog][blog-lets-encrypt] about how to set up encryption for Home Assistant. If you are unable to get https up and running, consider using [this AWS Lambda proxy for Alexa skills](https://forums.developer.amazon.com/forums/thread.jspa?messageID=18604).
 
 [blog-lets-encrypt]: https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/
 
 To get started with Alexa skills:
- - log in to [Amazon developer console](https://developer.amazon.com)
+
+ - Log in to [Amazon developer console](https://developer.amazon.com)
  - Go to Apps & Services => Alexa => Alexa Skill Kit - Get Started
  - Add a new skill
    - Name: Home Assistant
    - Invocation name: home assistant (or be creative, up to you)
    - Version: 1.0
-   - Endpoint: https / https://YOUR_HOST/api/alexa?api_password=YOUR_API_PASSWORD
+   - Endpoint:
+     - https
+     - https://YOUR_HOST/api/alexa?api_password=YOUR_API_PASSWORD
 
 ### Configuring your Amazon Alexa skill
 
@@ -69,9 +77,11 @@ This means that we can now ask Alexa things like:
 
 ### Configuring Home Assistant
 
-Out of the box, the component will do nothing. You have to teach it about all intents you want it to answer to. The way it works is that the answer for each intent is based on a templates that you define. Each template will have access to the existing state as per the `states` variable but will also have access to all variables defined in the intent.
+Out of the box, the component will do nothing. You have to teach it about all intents you want it to answer to. The way it works is that the answer for each intent is based on [templates] that you define. Each template will have access to the existing states via the `states` variable but will also have access to all variables defined in the intent.
 
-The values of `speech/text`, `card/title` and `card/content` will be parsed as a template.
+You can use [templates] for the values of `speech/text`, `card/title` and `card/content`.
+
+[templates]: /getting-started/templating/
 
 Configuring the Alexa component for the above intents would look like this:
 
@@ -88,8 +98,8 @@ alexa:
                  is_state('device_tracker.anne_therese', 'home') -%}
             You are both home, you silly
           {%- else -%}
-           Anne Therese is at {{ states("device_tracker.anne_therese") }} and
-           Paulus is at {{ states("device_tracker.paulus") }}
+            Anne Therese is at {{ states("device_tracker.anne_therese") }} and
+            Paulus is at {{ states("device_tracker.paulus") }}
           {% endif %}
 
     LocateIntent:
@@ -97,7 +107,7 @@ alexa:
         type: plaintext
         text: >
           {%- for state in states.device_tracker -%}
-            {%- if state.name[:4].lower() == User.lower() -%}
+            {%- if state.name.lower() == User.lower() -%}
               {{ state.name }} is at {{ state.state }}
             {%- endif -%}
           {%- else -%}

source/_posts/2015-12-20-amazon-echo-icloud-and-templates.markdown

@@ -0,0 +1,92 @@
+---
+layout: post
+title: "0.10: Amazon Echo, iCloud, Dweet.io, Twitch and templating support!"
+description: "Home Assistant 0.10 has been released with a bunch of added components and brand new templating support."
+date: 2015-12-22 01:30:00 -0800
+date_formatted: "December 22, 2015"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+# og_image:
+---
+
+Alrighty, it's time for Home Assistant 0.10. A lot amazing things have changed and sadly we also had to introduce a bunch of backwards incompatible changes. I would like to give a big shoutout to Philip Lundrigan ([@philipbl]) who put a lot in effort in helping the migration to move towards using templates for a wide variety of platforms.
+
+<center><iframe width="560" height="315" src="https://www.youtube.com/embed/1Ke3mtWd_cQ" frameborder="0" allowfullscreen></iframe></center>
+
+<img src='/images/supported_brands/icloud.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/heatmiser.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/dweet.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/amazon-echo.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/eliq.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
+
+ - Device tracker: [iCloud] platform added ([@xorso], [@kevinpanaro])
+ - Frontend: Improved caching using service workers if served over SSL ([@balloob])
+ - Sensor: [Twitch] platform added ([@happyleavesaoc])
+ - [Template] support ([@balloob], [@philipbl], [@fabaff])
+ - Thermostat: [Heatmiser] platform added ([@andylockran])
+ - Sensor: [Dweet.io] platform added ([@fabaff])
+ - [Alexa/Amazon echo] component added ([@balloob])
+ - Device Tracker: [FritzBox] platform added ([@deisi], [@caiuspb])
+ - Sensor: [Wink] now supports the Egg minders ([@w1ll1am23])
+ - Sensor: [ELIQ Online] platform added ([@molobrakos])
+ - Binary sensor: [REST] platform added ([@fabaff])
+ - Sensor: [Torque (OBD2)] platform added ([@happyleavesaoc])
+
+[iCloud]: /components/device_tracker.icloud/
+[Twitch]: /components/sensor.twitch/
+[Template]: /getting-started/templating/
+[Heatmiser]: /components/thermostat.heatmiser/
+[Dweet.io]: /components/sensor.dweet/
+[Alexa/Amazon echo]: /components/alexa/
+[FritzBox]: /components/device_tracker.fritzbox/
+[Wink]: /components/sensor.wink/
+[ELIQ Online]: /components/sensor.eliqonline/
+[REST]: /components/binary_sensor.rest/
+[Torque (OBD2)]: /components/sensor.torque/
+[@andylockran]: https://github.com/andylockran
+[@balloob]: https://github.com/balloob
+[@caiuspb]: https://github.com/caiuspb
+[@deisi]: https://github.com/deisi
+[@fabaff]: https://github.com/fabaff
+[@happyleavesaoc]: https://github.com/happyleavesaoc
+[@kevinpanaro]: https://github.com/kevinpanaro
+[@molobrakos]: https://github.com/molobrakos
+[@philipbl]: https://github.com/philipbl
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@xorso]: https://github.com/xorso
+
+<!--more-->
+
+### Templates
+
+This release introduces templates. This will allow you to parse data before it gets processed or create messages for notifications on the fly based on data within Home Assistant. The notification component and the new Alexa/Amazon Echo component are both using the new template functionality to render responses. A template editor has been added to the developer tool section in the app so you can get instant feedback if your templates are working or not.
+
+```jinja2
+The temperature at home is {% raw %}{{ states('sensor.temperature') }}{% endraw %}.
+```
+
+More information and examples can be found in the [template documentation][Template].
+
+### Breaking changes
+
+Templates will now be the only way to extract data from 'raw' sources like REST, CommandSensor or MQTT. This will replace any specific option that used to do this before. This means that `precision`, `factor`, `attribute` or `json_path` etc will no longer work.
+
+Affected components and platforms:
+
+ - sensor: [arest][sensor.arest]
+ - sensor: [command_sensor][sensor.command]
+ - sensor: [rest][sensor.rest]
+ - sensor: [MQTT][sensor.mqtt]
+ - switch: [MQTT][switch.mqtt]
+ - rollershutter: [MQTT][rollershutter.mqtt]
+ - light: [MQTT][light.mqtt]
+ - binary_sensor: [MQTT][binary_sensor.mqtt]
+ - automation: [numeric_state][automation-numeric-state]
+
+[sensor.arest]: /components/sensor.arest/
+[sensor.command]: /components/sensor.command_sensor/
+[sensor.rest]: /components/sensor.rest/
+[sensor.mqtt]: /components/sensor.mqtt/
+[switch.mqtt]: /components/switch.mqtt/
+[rollershutter.mqtt]: /components/rollershutter.mqtt/
+[light.mqtt]: /components/light.mqtt/
+[binary_sensor.mqtt]: /components/binary_sensor.mqtt/
+[automation-numeric-state]: /components/automation/#numeric-state-trigger

source/getting-started/templating.markdown

@@ -91,7 +91,11 @@ Home Assistant adds extensions to allow templates to access all of the current s
   Paulus is at {{ states('device_tracker.paulus')) }}.
 {% endif %}
 
-{{ states.sensor.temperature | multiply(10) | round(2) }}{% endraw %}
+{{ states.sensor.temperature | multiply(10) | round(2) }}
+
+{% if states('sensor.temperature') | float > 20 %}
+  It is warm!
+{%endif %}{% endraw %}
 ```
 
 ## {% linkable_title Processing incoming data %}