Add 0.12 release blog post

source/_components/automation.markdown

@@ -161,22 +161,30 @@ automation:
 
 #### {% linkable_title Time trigger %}
 
-Time can be triggered in many ways. The most common is to specify `after` and trigger at a specific point in time each day. Alternatively, you can also match if the hour, minute or second of the current time has a specific value. For example, by only setting minutes in the config to 5 it will trigger every hour when it is 5 minutes past whole.  You cannot use `after` together with hour, minute or second.
+Time can be triggered in many ways. The most common is to specify `after` and trigger at a specific point in time each day. Alternatively, you can also match if the hour, minute or second of the current time has a specific value. You can prefix the value with a `/` to match whenever the value is divisible by that number. You cannot use `after` together with hour, minute or second.
 
 ```yaml
 automation:
   trigger:
     platform: time
-    # All following are optional.
-    # When 'after' is used, you cannot also match on hour, minute, seconds.
-    # Military time format.
-    # after: '15:32:00'
-    hours: 0
+    # Matches every hour at 5 minutes past whole
     minutes: 5
     seconds: 0
-```
 
-The above example will trigger every hour on the 5 (2:05, 3:05, 4:05, etc).
+automation 2:
+  trigger:
+    platform: time
+    # When 'after' is used, you cannot also match on hour, minute, seconds.
+    # Military time format.
+    after: '15:32:00'
+
+automation 3:
+  trigger:
+    platform: time
+    # You can also match on interval. This will match every 5 minutes
+    minutes: '/5'
+    seconds: 0
+```
 
 #### {% linkable_title Zone trigger %}
 

source/_components/binary_sensor.nest.markdown

@@ -1,7 +1,7 @@
 ---
 layout: component
-title: "Nest thermostat sensor"
-description: "Instructions how to integrate Nest thermostats sensors within Home Assistant."
+title: "Nest binary sensor"
+description: "Instructions how to integrate Nest binary sensors within Home Assistant."
 date: 2016-01-26 08:00
 sidebar: true
 comments: false
@@ -12,7 +12,7 @@ ha_category: Binary Sensor
 ---
 
 
-The `nest` binary sensor platform let you monitor various states of a thermostat from [Nest](https://nest.com).
+The Nest binary sensor platform let you monitor various states of a thermostat from [Nest](https://nest.com).
 
 To set it up, add the following information to your `configuration.yaml` file:
 
@@ -35,5 +35,4 @@ Configuration variables:
 
 - **monitored_conditions** array (*Required*): States to monitor.
 
-You must have the [Nest Thermostat](https://home-assistant.io/components/thermostat.nest/) entity configured to use this sensor.
-
+<p class='note'>You must have the [Nest component](https://home-assistant.io/components/nest/) configured to use this sensor.</p>

source/_components/device_tracker.owntracks.markdown

@@ -27,20 +27,20 @@ device_tracker:
 
 There is no further configuration needed for tracking Owntracks devices.
 
-#####Using Owntracks with other device trackers
+### {% linkable_title Using Owntracks with other device trackers %}
 Owntracks can also be used with other device trackers, such as [Nmap](/components/device_tracker.nmap_scanner/) or [Netgear](/components/device_tracker.netgear/). To do this, fill in the `mac` field to the Owntracks entry in `known_devices.yaml` with the MAC address of the device you want to track. This way the state of the device will be determined by the source that reported last.
 
-######Using Owntracks regions
-Owntracks can track regions, and send region entry and exit information to Home Assistant(HA). You set up a region in the Owntracks app which you should name the same as your HA Zone, and then make sure to turn on the `share` option for the region in the owntracks app. Please see the [owntracks documentation] (http://owntracks.org/booklet/guide/waypoints/)
+### {% linkable_title Using Owntracks regions %}
+Owntracks can track regions, and send region entry and exit information to Home Assistant(HA). You set up a region in the Owntracks app which you should name the same as your HA Zone, and then make sure to turn on the `share` option for the region in the owntracks app. Please see the [owntracks documentation](http://owntracks.org/booklet/guide/waypoints/)
 
 Home Assistant will use the enter and leave messages to set your zone location. Your location will be set to the center of zone when you enter. Location updates from OwnTracks will be ignored while you are inside a zone.
 
 When you exit a zone, Home Assistant will start using location updates to track you again. To make sure that Home Assistant correctly exits a zone (which it calculates based on your GPS co-ordinates), you may want to set your Zone radius in HA to be slightly smaller that the Owntracks region radius.
 
-#####Using Owntracks regions - forcing Owntracks to update using iBeacons
+### {% linkable_title Using Owntracks regions - forcing Owntracks to update using  %}iBeacons
 When run in the usual `significant changes mode` (which is kind to your phone battery), Owntracks sometimes doesn't update your location as quickly as you'd like when you arrive at a zone. This can be annoying if you want to trigger an automation when you get home. You can improve the situation using iBeacons.
 
-iBeacons are simple bluetooth devices that send out an 'I'm here' message. They are supported by IOS and some Android devices. Owntracks explain more [here] (http://owntracks.org/booklet/guide/beacons/)
+iBeacons are simple bluetooth devices that send out an "I'm here" message. They are supported by IOS and some Android devices. Owntracks explain more [here](http://owntracks.org/booklet/guide/beacons/)
 
 When you enter an iBeacon region, Owntracks will send a `region enter` message to HA as described above. So if you want to have an event triggered when you arrive home, you can put an iBeacon outside your front door. If you set up an OwnTracks iBeacon region called `home` then getting close to the beacon will trigger an update to HA that will set your zone to be `home`.
 
@@ -48,7 +48,7 @@ When you exit an iBeacon region HA will switch back to using GPS to determine yo
 
 Sometimes Owntracks will lose connection with an iBeacon for a few seconds. If you name your beacon starting with `-` Owntracks will wait longer before deciding it has exited the beacon zone. HA will ignore the `-` when it matches the Owntracks region with Zones. So if you call your Owntracks region `-home` then HA will recognise it as `home`, but you will have a more stable iBeacon connection.
 
-#####Using Owntracks iBeacons to track devices
+### {% linkable_title Using Owntracks iBeacons to track devices %}
 iBeacons don't need to be stationary. You could put one on your key ring, or in your car.
 
 When your phone sees a mobile iBeacon that it knows about, it will tell HA the location of that iBeacon. If your phone moves while you are connected to the iBeacon, HA will update the location of the iBeacon. But when your phone loses the connection, HA will stop updating the iBeacon location.
@@ -57,6 +57,6 @@ To use mobile iBeacons with HA, you just set up a region that doesn't match your
 
 This allows you to write zone automations for devices that can't track themselves (for example `alert me if I leave the house and my keys are still at home`). Another example would be `open the gates if my car arrives home`.
 
-#####Using mobile and fixed iBeacons together
-You can use iBeacons of both types together, so if you have a Zone `drive` with an iBeacon region called `-drive` and you arrive home with a mobile iBeacon called '-car', then `device_tracker.beacon_car' will be set to a state of 'drive'.
+### {% linkable_title Using mobile and fixed iBeacons together %}
+You can use iBeacons of both types together, so if you have a Zone `drive` with an iBeacon region called `-drive` and you arrive home with a mobile iBeacon called `-car`, then `device_tracker.beacon_car` will be set to a state of `drive`.
 

source/_components/group.markdown

@@ -11,31 +11,15 @@ logo: home-assistant.png
 ha_category: Organization
 ---
 
-Groups allow the user to combine multiple entities into one.
+Groups allow the user to combine multiple entities into one. A group can be promoted to a **view** by setting the `view` option to `yes`. This will make the group available as a new tab in the frontend.
 
 Check the **Set State** page from the **Developer Tools** and browse the **Current entities:** listing for all available entities.
 
-```yaml
-# Example configuration.yaml entry
-group:
-  information:
-    - sensor.time
-  living_room:
-    - binary_sensor.tv
-    - sensor.living_room_temperature
-  kitchen:
-    - switch.kitchen_pin_3
-    - sensor.oven_temperature
-```
-
-With Home Assistant 0.12.0 a new feature **view** was introduced.
-
 ```yaml
 # Example configuration.yaml entry
 group:
   kitchen:
     name: Kitchen
-    view: no
     entities:
       - switch.kitchen_pin_3
   upstairs:
@@ -54,7 +38,12 @@ Configuration variables:
 - **name** (*Optional*): Name of the group.
 - **icon** (*Optional*): An optional icon to show in the Frontend.
 - **view** (*Optional*): If yes then the entry will be shown as a view.
-- **entities** array (*Required*): List of entites to group.
+- **entities** array or comma delimited string (*Required*): List of entites to group.
+
+<p class='img'>
+<img src='/images/blog/2016-01-release-12/views.png'>
+Example of groups shown as views in the frontend.
+</p>
 
 If all entities are switches or lights they can be controlled as one with a switch at the top of the card. Grouped states should share the same type of states (ON/OFF or HOME/NOT_HOME).
 
@@ -65,8 +54,5 @@ group:
     - light.bowl
     - light.ceiling
     - light.tv_back_light
-  children:
-    - device_tracker.child_1
-    - device_tracker.child_2
+  children: device_tracker.child_1, device_tracker.child_2
 ```
-

source/_components/insteon_hub.markdown

@@ -26,4 +26,3 @@ Configuration variables:
 
 - **username** (*Required*): The username that used to access the Insteon interface.
 - **password** (*Required*): The password that used to access the Insteon interface.
-

source/_components/nest.markdown

@@ -0,0 +1,27 @@
+---
+layout: component
+title: "Nest"
+description: "Instructions how to integrate Nest into Home Assistant."
+date: 2016-01-29 21:57
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: nest_thermostat.png
+ha_category: Hub
+featured: false
+---
+
+The Nest component is the main component to integrate all Nest related platforms. It will setup your thermostats and any connected sensors.
+
+```yaml
+# Example configurayion.yaml entry
+nest:
+  username: USERNAME
+  password: PASSWORD
+```
+
+Configuration variables:
+
+- **username** (*Required*): Your Nest username.
+- **password** (*Required*): Your Nest password.

source/_components/notify.google_voice.markdown

@@ -0,0 +1,37 @@
+---
+layout: component
+title: "Google Voice SMS"
+description: "Instructions how to add user notifications to Home Assistant."
+date: 2016-01-29
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: google_voice.png
+ha_category: Notifications
+featured: true
+---
+
+[Google Voice](https://www.google.com/voice) is a free service, that allows sending of SMS messages to mobile phones.
+
+### Configuration
+
+```yaml
+# Example configuration.yaml entry
+notify:
+  platform: googlevoice
+  username: YOUR_GOOGLE_EMAIL
+  password: YOUR_GOOGLE_PASSWORD
+  # Optional
+  name: NOTIFIER_NAME
+```
+
+Configuration variables:
+
+- **username** (*Required*): Enter your the Google email address you have signed up for Google Voice with. Go to https://www.google.com/voice to setup your Google Voice account.
+- **password** (*Required*): Enter the password associated with the above email. Go to https://www.pushbullet.com/ to retrieve your API key.
+- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
+
+### Usage
+
+Google Voice is a notify platform and thus can be controlled by calling the notify service [as described here](/components/notify/). It will send a notification to all devices listed in the notification **target**.

source/_components/sensor.nest.markdown

@@ -1,7 +1,7 @@
 ---
 layout: component
-title: "Nest thermostat sensor"
-description: "Instructions how to integrate Nest thermostats sensors within Home Assistant."
+title: "Nest sensor"
+description: "Instructions how to integrate Nest sensors within Home Assistant."
 date: 2016-01-13 19:59
 sidebar: true
 comments: false
@@ -12,7 +12,7 @@ ha_category: Sensor
 ---
 
 
-The `nest` sensor platform let you monitor a thermostat from [Nest](https://nest.com). It also includes the ability to monitor things like the state of our HVAC system and the current humidity and temperature.
+The Nest sensor platform let you monitor sensors connected to your [Nest](https://nest.com) thermostat.
 
 To set it up, add the following information to your `configuration.yaml` file:
 
@@ -36,8 +36,4 @@ Configuration variables:
 
 - **monitored_conditions** array (*Required*): States to monitor.
 
-You must have the [Nest Thermostat](https://home-assistant.io/components/thermostat.nest/) entity configured to use this sensor.
-
-<p class='img'>
-  <img src='{{site_root}}/images/screenshots/nest-thermostat-card.png' />
-</p>
+<p class='note'>You must have the [Nest component](https://home-assistant.io/components/nest/) configured to use this sensor.</p>

source/_components/thermostat.nest.markdown

@@ -13,22 +13,17 @@ featured: true
 ---
 
 
-The nest thermostat platform let you control a thermostat from [Nest](https://nest.com).
+The Nest thermostat platform let you control a thermostat from [Nest](https://nest.com).
 
 To set it up, add the following information to your `configuration.yaml` file:
 
 ```yaml
 thermostat:
   platform: nest
-  username: USERNAME
-  password: PASSWORD
 ```
 
-Configuration variables:
-
-- **username** (*Required*): Your Nest username.
-- **password** (*Required*): Your Nest password.
-
 <p class='img'>
   <img src='{{site_root}}/images/screenshots/nest-thermostat-card.png' />
 </p>
+
+<p class='note'>You must have the [Nest component](https://home-assistant.io/components/nest/) configured to use this sensor.</p>

source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown

@@ -63,7 +63,7 @@ First release of 2016 and we are on 🔥! The [main repository][github-ha] has p
 [MySensors sensor platform]: /components/sensor.mysensors/
 [Amazon Echo]: /components/alexa/
 
-### Deprecations
+### Backwards incompatible changes
  - The [RPi.GPIO sensor platform][rpi-bs] has been moved to the `binary_sensor` component.
  - [MySensors sensor platform] now requires the [MySensors] component to be configured.
  - Geofancy platform has been renamed to [Locative].

source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown

@@ -0,0 +1,91 @@
+---
+layout: post
+title: "0.12: Insteon, LIFX, Twitter and ZigBee"
+description: "Home Assistant 0.12 brings improved organizational tools and makes writing automation in Python easier."
+date: 2016-01-30 00:22:00 -0800
+date_formatted: "January 30, 2016"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2016-01-release-12/social.png
+---
+
+Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.
+
+I would like to give a shout out to [Greg Dowling (@pavoni)][@pavoni] as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!
+
+This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See [the demo] to see this in action and read more in the [group documentation][group] how to get started.
+
+<p class='img'>
+<a href='/demo/'><img src='/images/blog/2016-01-release-12/views.png'></a>
+Example of the new views in the frontend. <a href='/components/group/'>Learn more.</a>
+</p>
+
+<img src='/images/supported_brands/insteon.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/lifx.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/twitter.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/zigbee.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/google_voice.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
+
+ - Binary sensor: [command sensor] added ([@Bart274])
+ - [Nest] support extended to include sensors and binary sensors ([@joshughes])
+ - Light: [LIFX] platform added ([@TangoAlpha])
+ - Notify: [Twitter] platform added ([@HydrelioxGitHub])
+ - Sensor: [Template] platform added ([@pavoni])
+ - Switch: [Wink] platform now supports sirens ([@w1ll1am23])
+ - [Insteon hub] support added ([@FreekingDean])
+ - [Statsd] component added ([@michaelkuty])
+ - Light: [Rfxtrx] platform now supports dimming ([@turbokongen])
+ - Time scheduling (including [time automation]) now works with intervals (ie. `/5`) ([@kennedyshead])
+ - Sensor: [onewire] support added ([@deisi])
+ - [Zigbee] support added ([@flyte])
+ - Device Tracker: [OwnTracks] can now track iBeacons ([@pavoni])
+ - Notify: [Google Voice SMS] platform added ([@w1ll1am23])
+ - Toggle service added to `homeassistant`, `switch`, `light` and `media_player` ([@rmkraus])
+ - [Thermostat] services added to control fans ([@auchter])
+ - Improved Python automation: Event helpers are now also available as decorators for custom components ([@rmkraus])
+ - Frontend: support added for tabs to show [different views][group] of your house ([@balloob])
+ - Bugfixes by [@molobrakos], [@MartinHjelmare], [@pavoni], [@trollkarlen], [@zmrow], [@maddox], [@persandstrom], [@happyleavesaoc], [@balloob], [@fabaff], [@stefan-jonasson], [@haraldnagel].
+
+[the demo]: /demo/
+[command sensor]: /components/binary_sensor.command/
+[Google Voice SMS]: /components/notify.google_voice/
+[Insteon hub]: /components/insteon_hub/
+[LIFX]: /components/light.lifx/
+[Nest]: /components/nest/
+[onewire]: /components/sensor.onewire/
+[OwnTracks]: /components/device_tracker.owntracks/
+[Rfxtrx]: /components/light.rfxtrx/
+[Statsd]: /components/statsd/
+[Template]: /components/sensor.template/
+[Thermostat]: /components/thermostat/
+[time automation]: /components/automation/#time-trigger
+[Twitter]: /components/notify.twitter/
+[Wink]: /components/wink/
+[Zigbee]: /components/zigbee/
+[group]: /components/group/
+[@auchter]: https://github.com/auchter
+[@balloob]: https://github.com/balloob
+[@Bart274]: https://github.com/Bart274
+[@deisi]: https://github.com/deisi
+[@fabaff]: https://github.com/fabaff
+[@flyte]: https://github.com/flyte
+[@FreekingDean]: https://github.com/FreekingDean
+[@happyleavesaoc]: https://github.com/happyleavesaoc
+[@haraldnagel]: https://github.com/haraldnagel
+[@HydrelioxGitHub]: https://github.com/HydrelioxGitHub
+[@joshughes]: https://github.com/joshughes
+[@kennedyshead]: https://github.com/kennedyshead
+[@maddox]: https://github.com/maddox
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@michaelkuty]: https://github.com/michaelkuty
+[@molobrakos]: https://github.com/molobrakos
+[@pavoni]: https://github.com/pavoni
+[@persandstrom]: https://github.com/persandstrom
+[@rmkraus]: https://github.com/rmkraus
+[@stefan-jonasson]: https://github.com/stefan-jonasson
+[@TangoAlpha]: https://github.com/TangoAlpha
+[@trollkarlen]: https://github.com/trollkarlen
+[@turbokongen]: https://github.com/turbokongen
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@zmrow]: https://github.com/zmrow
+
+### Backwards incompatible changes
+ - Nest config has moved from thermostat to the [Nest component][Nest].