Merge branch 'current' into next

_config.yml

@@ -128,9 +128,9 @@ social:
 # Home Assistant release details
 current_major_version: 0
 current_minor_version: 39
-current_patch_version: 0
+current_patch_version: 2
-date_released: 2017-02-25
+date_released: 2017-03-01
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
-patch_version_notes: "#"
+patch_version_notes: "#release-0392---march-1"

source/_components/automation.markdown

@@ -19,12 +19,13 @@ Starting with 0.28 your automation rules can be controlled with the frontend.
   <img src='{{site_root}}/images/screenshots/automation-switches.png' />
 </p>
 
-This allows one to reload the automation without restarting Home Assistant itself. If you don't want to see the automation rule in your frontend use `hide_entity: True` to hide it.
+This allows one to reload the automation without restarting Home Assistant itself. If you don't want to see the automation rule in your frontend use `hide_entity: True` to hide it. You can also use `initial_state: 'off'` so that the automation is not automatically turned on after a Home assistant reboot.
 
 ```yaml
 automation:
   - alias: Door alarm
     hide_entity: True
+    initial_state: 'off'
     trigger:
       - platform: state
   ...

source/_components/binary_sensor.insteon_plm.markdown

@@ -0,0 +1,22 @@
+---
+layout: page
+title: "Insteon PLM Binary Sensor"
+description: "Instructions how to setup the Insteon PLM switches locally within Home Assistant."
+date: 2017-02-19 17:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: insteon.png
+ha_category: Binary Sensor
+ha_iot_class: "Local Push"
+ha_version: 0.39
+---
+
+The `insteon_plm` binary sensor platform lets you control your sensors through 
+an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a
+USB or serial port.  To add support, set up the primary [insteon_plm]
+component.
+
+[insteon_plm]: /components/insteon_plm/
+

source/_components/device_tracker.gpslogger.markdown

@@ -27,7 +27,7 @@ device_tracker:
 
 To configure GPSLogger, you must set up the app to send a `GET` request to your Home Assistant server at 
 ```yaml
-`http://<ha_server>/api/gpslogger?latitude=%LAT&longitude=%LON&device=%SER&accuracy=%ACC&battery=%BATT&speed=%SPD&direction=%DIR&altitude=%ALT&provider=%PROV&activity=%ACT`
+http://<ha_server>/api/gpslogger?latitude=%LAT&longitude=%LON&device=%SER&accuracy=%ACC&battery=%BATT&speed=%SPD&direction=%DIR&altitude=%ALT&provider=%PROV&activity=%ACT
 ```
 . Make sure to include the API password if you have configured a password in Home Assistant (add `&api_password=<password>` to the end of the URL). Configure that options under "General Options":
 
@@ -40,8 +40,9 @@ Set the URL under "General Options -> Logging details":
 - Log to KML: no
 - Log to custom URL: yes and set 
 ```yaml
-`http://<ha_server>/api/gpslogger?latitude=%LAT&longitude=%LON&device=%SER&accuracy=%ACC&battery=%BATT&speed=%SPD&direction=%DIR&altitude=%ALT&provider=%PROV&activity=%ACT` (be sure you include API password (`&api_password=<password>`) if needed, or you can also use HTTP Basic authentication `http://<username>:<password>@<ha_server>/api/gpslogger...`)
+http://<ha_server>/api/gpslogger?latitude=%LAT&longitude=%LON&device=%SER&accuracy=%ACC&battery=%BATT&speed=%SPD&direction=%DIR&altitude=%ALT&provider=%PROV&activity=%ACT
 ```
+(be sure you include API password (`&api_password=<password>`) if needed, or you can also use HTTP Basic authentication `http://<username>:<password>@<ha_server>/api/gpslogger...`)
 - Log to OpenGTS Server: no
 - Log to Plain Text: no
 - Log to NMEA: no

source/_components/hdmi_cec.markdown

@@ -133,10 +133,9 @@ hdmi_cec:
 Then you set individual platform for devices in customizations:
 
 ```yaml
-homeassistant:
+hdmi_cec:
-  customize:
+  types:
-    hdmi_cec.hdmi_5:
+    hdmi_cec.hdmi_5: media_player
-      platform: media_player
 ```
 
 And the last option is `host`. PyCEC supports bridging CEC commands over TCP. When you start pyCEC on machine with HDMI port (`python -m pycec`), you can then run homeassistant on another machine and connect to CEC over TCP. Specify TCP address of pyCEC server:

source/_components/insteon_plm.markdown

@@ -0,0 +1,89 @@
+---
+layout: page
+title: "Insteon PLM"
+description: "Instructions how to setup an Insteon USB PLM locally within Home Assistant."
+date:  2017-02-19 16:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: insteon.png
+ha_category: Hub
+ha_iot_class: "Local Push"
+ha_version: 0.39
+---
+
+This component adds "local push" support for INSTEON PowerLinc Modems allowing
+linked INSTEON devices to be used within Home Assistant as lights, switches,
+and binary sensors.  Device support is provided by the underlying [insteonplm]
+package.  It is known to work with both the [2413U] USB and [2412S]
+RS242 flavors of PLM.  This component does not work with the IP-based hub
+products.  For that, you'll want the "Insteon (Local)" component instead.
+
+[insteonplm]: https://github.com/nugget/python-insteonplm
+[2413U]: https://www.insteon.com/powerlinc-modem-usb
+[2412S]: https://www.insteon.com/powerlinc-modem-serial
+
+
+```yaml
+# insteon_plm supported configuration variables
+insteon_plm:
+  port: SERIAL_PORT
+  device_override:
+     - address: INSTEON_ADDRESS
+       platform: DEVICE_PLATFORM
+```
+
+Configuration variables:
+- **port** (*Required*): The port for your device, e.g. `/dev/ttyUSB0`
+- **device_override** (*Optional*): Override the default device platform
+  
+
+### {% linkable_title Customization %} 
+
+The only configuration item that is absolutely necessary is the port so that
+Home Assistant can connect to the PLM.  This will expose all the supported INSTEON
+devices which exist in the modem's ALL-Link database.  However, devices will
+only be shown by their INSTEON hex address (e.g. "1A.2B.3C") which can be a bit
+unwieldy.  As you link and unlink devices using the 'Set' buttons, they'll be
+added and removed from Home Assistant automatically.
+
+You can use the normal Home Assistant [device customization] section of your
+configuration to assign friendly names and special icons to your devices.  This
+is especially useful for setting device_class on your binary_sensor INSTEON
+devices.
+
+[device customization]: /getting-started/customizing-devices/
+
+### {% linkable_title Device Overrides %} 
+
+INSTEON devices are added to Home Assistant using the platform(s) that make the
+most sense given the model and features of the hardware.  In most cases this is
+unambiguous, but sometimes the component will not be able to guess the actual
+usage of the device.  For example, there might be a table lamp plugged into an
+INSTEON appliance relay module.  By default, this will show as a 'switch'
+device in Home Assistant, but it really should be a 'light' device.  For
+exceptions like this, the component supports a device plaform override.  You
+can set any device (by address) to explicitly use a specific platform if the
+default is not correct.
+
+### {% linkable_title Example Configuration with Options%} 
+
+```yaml
+# Full example of insteon_plm configuration with customizations and overrides
+
+homeassistant:
+  customize:
+    light.a1b2c3:
+      friendly_name: Bedside Lamp
+    binary_sensor.a2b3c4:
+      friendly_name: Garage Door
+      device_class: opening
+
+insteon_plm:
+  port: /dev/ttyUSB0
+  device_override:
+    - address: a1b2c3  # Icon Appliance Module for bedside lamp
+      platform: light  # make it a light instead of a switch
+```
+

source/_components/light.insteon_plm.markdown

@@ -0,0 +1,22 @@
+---
+layout: page
+title: "Insteon PLM Light"
+description: "Instructions how to setup Insteon PLM lights locally within Home Assistant."
+date: 2017-02-19 17:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: insteon.png
+ha_category: Light
+ha_iot_class: "Local Push"
+ha_version: 0.39
+---
+
+The `insteon_plm` light platform lets you control your sensors through 
+an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a
+USB or serial port.  To add support, set up the primary [insteon_plm]
+component.
+
+[insteon_plm]: /components/insteon_plm/
+

source/_components/media_player.gstreamer.markdown

@@ -52,10 +52,10 @@ sudo yum install -y python-gstreamer1 gstreamer1-plugins-good \
 
 For Fedora replace `yum` with `dnf`.
 
-If you're running Home Assistant in a virtual environment, you'll need to symlink the system Python's `gst` module into your virtual environment:
+If you're running Home Assistant in a virtual environment, you'll need to symlink the system Python's `gi` module into your virtual environment:
 
 ```bash
-ln -s /path/to/your/installation/of/gst /path/to/your/venv/lib/python3.4/site-packages
+ln -s /path/to/your/installation/of/gi /path/to/your/venv/lib/python3.4/site-packages
 ``` 
 
 On a Raspberry PI, you may need to add the Home Assistant user to the `audio` group:

source/_components/notify.matrix.markdown

@@ -13,7 +13,7 @@ ha_release: 0.32
 ---
 
 
-The `matrix` platform allows you to deliver notifications from Home Assistant to a Matrix room. Rooms can be both direct as well as group chats.
+The `matrix` platform allows you to deliver notifications from Home Assistant to a [Matrix](http://matrix.org) room. Rooms can be both direct as well as group chats.
 
 To enable Matrix notifications in your installation, add the following to your `configuration.yaml` file:
 

source/_components/notify.pushover.markdown

@@ -53,3 +53,23 @@ This is a quote from the Pushover website regarding free/open source apps:
 When setting up the application you can use this [icon](https://home-assistant.io/images/favicon-192x192.png).
 
 To use notifications, please see the [getting started with automation page](/getting-started/automation/).
+
+When sending a notification, optional parameters can also be set as per the pushover [API documentation](https://pushover.net/api). 
+
+Example notification triggered from the Alexa component for an intents is shown below which also uses [Automation Templating](/getting-started/automation-templating/) for the message:
+
+```yaml
+# Example configuration.yaml entries
+alexa:
+  intents:
+    LocateIntent:
+      action:
+        service: notify.notify
+        data_template:
+          message: "The location of {% raw %}{{ User }}{% endraw %} has been queried via Alexa."
+          data:
+            title: "Home Assistant"
+            sound: falling
+            device: pixel
+            url: "https://home-assistant.io/"
+```

source/_components/sensor.fido.markdown

@@ -0,0 +1,57 @@
+---
+layout: page
+title: "Fido"
+description: "Instructions how to integrate Fido data usage within Home Assistant."
+date: 2017-01-01 17:17
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: fido.png
+ha_category: Sensor
+ha_release: 0.39
+ha_iot_class: "Cloud Polling"
+---
+
+
+Integrate your [Fido](https://www.fido.ca/) account information into Home Assistant.
+
+To enable this sensor, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: fido
+    username: MYUSERNAME
+    password: MYPASSWORD
+    monitored_variables:
+     - fido_dollar
+     - balance
+     - data_used
+```
+
+Configuration variables:
+
+- **username** (*Required*): You Fido username (your Fido phone number).
+- **password** (*Required*): Your Fido password.
+- **monitored_variables** array (*Required*): Variables to monitor.
+  - **fido_dollar**: Your Fido dollar balance
+  - **balance**: Your account balance
+  - **data_used**: Current data used
+  - **data_limit**: Current data limit
+  - **data_remaining**: Current data remaining
+  - **text_used**: SMS sent
+  - **text_limit**: SMS limit
+  - **text_remaining**: SMS remaining
+  - **mms_used**: MMS sent
+  - **mms_limit**: MMS limit
+  - **mms_remaining**: MMS remaining
+  - **text_int_used**: International SMS sent
+  - **text_int_limit**: International SMS limit
+  - **text_int_remaining**: International SMS remaining
+  - **talk_used**: Talk time used
+  - **talk_limit**: Talk time limit
+  - **talt_remaining**: Talk time remaining
+  - **other_talk_used**: Other talk time used (It could be internation calls)
+  - **other_talk_limit**: Other talk time limit
+  - **other_talt_remaining**: Other talk time remaining

source/_components/sensor.pocketcasts.markdown

@@ -0,0 +1,27 @@
+---
+layout: page
+title: PocketCasts
+description: "Instructions on how to set up PocketCasts sensors within Home Assistant."
+date: 2017-02-14 08:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category: Sensor
+ha_release: 0.39
+---
+
+To enable this sensor, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: pocketcasts
+    username: YOUR_USERNAME
+    password: YOUR_PASSWORD
+```
+
+Configuration options for the PocketCasts Sensor:
+
+- **username** (*Required*): The username to access the PocketCasts service.
+- **password** (*Required*): The password for the given username.

source/_components/sensor.waqi.markdown

@@ -32,7 +32,7 @@ Configuration variables:
 
 - **locations** (*Required*): a list of location names to look for air quality data. In case a specific location has multiple registered stations all of them will be added to Home Assistant
 
-- **token** (*Required*): a token for the AQICN public API. Please obtain one at (AQICN API token)[http://aqicn.org/data-platform/token/#/]
+- **token** (*Required*): a token for the AQICN public API. Please obtain one at [AQICN API token](http://aqicn.org/data-platform/token/#/)
 
 - **stations** (*Optional*): a list of station names to look for air quality data. Station should be within locations specified above.
 

source/_components/sensor.wunderground.markdown

@@ -17,7 +17,7 @@ ha_iot_class: "Cloud Polling"
 The `wunderground` platform uses [Weather Underground](http://www.wunderground.com) as a source for current weather information. 
 
 <p class='note warning'>
-Obtain a WUnderground API key [here](https://www.wunderground.com/weather/api). A free account allows 500 requests per day or 10 per minute.
+Obtain a WUnderground API key [here](https://www.wunderground.com/weather/api). A free account allows 500 requests per day and also a maximum of 10 per minute. See details [here](https://www.wunderground.com/weather/api/d/pricing.html).
 </p>
 
 To add Wunderground to your installation, add the following to your `configuration.yaml` file:

source/_components/switch.insteon_plm.markdown

@@ -0,0 +1,22 @@
+---
+layout: page
+title: "Insteon PLM Switch"
+description: "Instructions how to setup the Insteon PLM switches locally within Home Assistant."
+date: 2017-02-19 17:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: insteon.png
+ha_category: Switch
+ha_iot_class: "Local Push"
+ha_version: 0.39
+---
+
+The `insteon_plm` switch platform lets you control your switches through 
+an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a
+USB or serial port.  To add support, set up the primary [insteon_plm]
+component.
+
+[insteon_plm]: /components/insteon_plm/
+

source/_components/zabbix.markdown

@@ -35,7 +35,7 @@ Configuration variables:
 
 ```yaml
 # Example configuration.yaml entry
-zoneminder:
+zabbix:
   host: ZABBIX_HOST
   path: ZABBIX_PATH
   ssl: False

source/_cookbook/githubbackup.markdown

@@ -147,7 +147,7 @@ Every time you run this script, you will be prompted for a comment to describe t
 
 ### {% linkable_title Step 7: Configuration file testing %}
 
-[Travis CI](https://travis-ci.org) is a continuous intigration testing system that runs every time the code in your repository is updated and allows you to validate that your code works on a fresh install.
+[Travis CI](https://travis-ci.org) is a continuous integration testing system that runs every time the code in your repository is updated and allows you to validate that your code works on a fresh install.
 
 - [Authorise Travis CI](https://travis-ci.org/auth) to have access to your github repos.  
 - Create the build script that travis will run to test your repo.

source/_docs/backend/database.markdown

@@ -122,5 +122,5 @@ The `VACUUM` command cleans the your database.
 sqlite> VACUUM;
 ```
 
-For a more interactive way to work with the database or the create statistics, checkout our [Jupyther notebooks](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/).
+For a more interactive way to work with the database or the create statistics, checkout our [Jupyther notebooks](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/tree/master/).
 

source/_docs/configuration/customizing-devices.markdown

@@ -38,7 +38,7 @@ homeassistant:
       icon: mdi:home
   customize_glob:
     "light.kitchen_*":
-      icon: mid:description
+      icon: mdi:description
 
 ```
 
@@ -60,13 +60,6 @@ Device class is currently supported by the following platforms:
 * [Binary Sensor](/components/binary_sensor/)
 * [Cover](/components/cover/)
 
-### {% linkable_title Device Class %}
-
-Device class is currently supported by the following platforms:
-
-* [Binary Sensor](/components/binary_sensor/)
-* [Cover](/components/cover/)
-
 ### {% linkable_title Reloading customize %}
 
 Home Assistant offers a service to reload the core configuration while Home Assistant is running called `homeassistant/reload_core_config`. This allows you to change your customize section and see it being applied without having to restart Home Assistant. To call this service, go to the <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> service developer tools, select the service `homeassistant/reload_core_config` and click "Call Service".

source/_docs/ecosystem/hadashboard/installation.markdown

@@ -60,7 +60,7 @@ By default, the docker instance should pick up your timezone but if you want to
 Raspberry pi needs to use a different docker build file so the build command is slightly different:
 
 ```bash
-$ docker build -f Docker-raspi/Dockerfile -t hadashboard .
+$ sudo docker build -f Docker-raspi/Dockerfile -t hadashboard .
 ```
 
 Apart from that the other steps are identical.

source/_docs/hassbian/upgrading.markdown

@@ -15,16 +15,28 @@ Log in as the `pi` account and execute the following commands:
 
 ```bash
 $ sudo apt-get update
-$ sudo apt-get upgrade
+$ sudo apt-get -y upgrade
 ```
 
-Press `Y` to confirm that you would like to continue.
+
+#### {% linkable_title Updating Home Assistant %}
+
+To update the Home Assistant installation execute the following command as the `pi` user.
+
+```bash
+$ sudo systemctl stop homeassistant@homeassistant.service
+$ sudo su -s /bin/bash homeassistant
+$ source /srv/homeassistant/bin/activate
+$ pip3 install --upgrade homeassistant
+$ exit
+$ sudo systemctl start homeassistant@homeassistant.service
+```
 
 #### {% linkable_title Upgrading the hassbian-scripts %}
 
 To update the hassbian-scripts directory execute the following command as the `pi` user.
 
 ```bash
-$ cd hassbian-scripts
+$ cd /home/pi/hassbian-scripts
 $ git pull
 ```

source/_docs/installation/windows.markdown

@@ -0,0 +1,27 @@
+---
+layout: page
+title: "Installation on a Windoes system"
+description: "Instructions to install Home Assistant on a Microsoft Windows system."
+date: 2017-02-23 11:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+To run Home Assistant on Microsoft Windows installation you need to install Python first. Download Python for https://www.python.org/downloads/windows/ and follow the instructions of the installer.
+
+Start 
+
+```bash
+C:\...\> pip3 install homeassistant
+C:\...\> py -m homeassistant --open-ui
+```
+
+For autostarting Home Assistant please refer to this [guide](https://community.home-assistant.io/t/autostart-on-windows/3504).
+
+Check this [video](https://www.youtube.com/watch?v=X27eVvuqwnY) for the installation on Windows 10.
+
+<p class='note warning'>
+The Microsoft Windows platform is not a primary target to install home Assistant. Also, not all tools and third-party modules will work.
+</p>

source/_docs/z-wave.markdown

@@ -80,7 +80,7 @@ Configuration variables:
 - **config_path** (*Optional*): The path to the Python OpenZWave configuration files. Defaults to the folder `config` in your Python OpenZWave install directory.
 - **autoheal** (*Optional*): Allows disabling auto Z-Wave heal at midnight. Defaults to True.
 - **polling_interval** (*Optional*): The time period in milliseconds between polls of a nodes value. Be careful about using polling values below 30000 (30 seconds) as polling can flood the zwave network and cause problems.
-- **customize** (*Optional*): This attribute contains node-specific override values. See [Customizing devices and services](https://home-assistant.io/getting-started/customizing-devices/) for format:
+- **device_config** (*Optional*): This attribute contains node-specific override values. (For releases prior to 0.39 this variable is called **customize**) See [Customizing devices and services](https://home-assistant.io/getting-started/customizing-devices/) for format:
   - **polling_intensity** (*Optional*): Enables polling of a value and sets the frequency of polling (0=none, 1=every time through the list, 2=every other time, etc). If not specified then your device will not be polled.
   - **ignored** (*Optional*): Ignore this entitiy completely. It won't be shown in the Web Interface and no events are generated for it.
   - **refresh_value** (*Optional*): Enable refreshing of the node value. Only the light component uses this. Defaults to False.

source/_posts/2017-02-22-home-assistant-tshirts-have-arrived.markdown

@@ -12,11 +12,14 @@ og_image: /images/blog/2017-02-shirts/social.png
 ---
 
 <p class='img'>
-  <a href='https://teespring.com/stores/home-assistant-us-store'><img src='/images/blog/2017-02-shirts/beard.png' /></a>
+  <img src='/images/blog/2017-02-shirts/beard.png' />
-  Cool dude with beard and tattoo wearing [the new blue Home Assistant shirt][blue].
+  Cool dude with beard and tattoo wearing [the new blue Home Assistant shirt][blue-us].
 </p>
 
-What time is it? Yep, t-shirt time. Today we're launching the first two Home Assistant designs. We have a [blue t-shirt][blue] as pictured above and [a design for on black/gray shirts][black] as pictured below. [Go to the store!][store]
+What time is it? Yep, t-shirt time. Today we're launching the first two Home Assistant designs. We have a blue t-shirt ([🇪🇺 EU][blue-eu] – [🇺🇸 US][blue-us]) as pictured above and a design for on black/gray shirts ([🇪🇺 EU][black-eu] – [🇺🇸 US][black-us]) as pictured below.
+
+ - [Visit the 🇺🇸 US store][store-us]
+ - [Visit the 🇪🇺 EU store][store-eu]
 
 <a href='https://www.eff.org'><img src='/images/supported_brands/eff.png' style='width: 150px; float: right; box-shadow: none; border: 0; margin-left: 15px;' /></a>
 
@@ -24,48 +27,49 @@ And because we love the internet and all the things that it has brought us, **we
 
 The EFF is a nonprofit organization that aims to protect the rights of technology users. You might however be more familiar with one of their projects: [Let's Encrypt][le]. [Read more about what the EFF does.][eff-issues]
 
-[So, what are you waiting for? Buy a shirt!][store]
+So, what are you waiting for? Get yourself a shirt! [🇪🇺 EU store][store-eu] – [🇺🇸 US store][store-us]
 
 <p class='img'>
-  <a href='https://teespring.com/stores/home-assistant-us-store'><img src='/images/blog/2017-02-shirts/family.png' /></a>
+  <img src='/images/blog/2017-02-shirts/family.png' />
-  Family of 4 on a bench wearing [the new black Home Assistant shirt][black].
+  Family of 4 on a bench wearing the new black Home Assistant shirt. [🇪🇺 EU][black-eu] – [🇺🇸 US][black-us]
 </p>
 
 We are using [Teespring.com][ts] to manage all the sales, production and distribution of the shirts and they will also donate our profits to the EFF. It's also how we got all these amazing stockphotos. Some extra things to note about our teespring shop:
 
- - For now we are only launching a US-based store and are working on an EU-based store. We will keep you updated when that is ready. An EU-based store would bring ([according to Teespring][ts-eu]) 65% cheaper shipping and 30% faster delivery if you are in Europe compared to the US store.
  - Teespring shows that there is a number of days left until the end of the campaign for the shirts. Don't worry about that, it should automatically relaunch.
- - Right now [the blue shirt][blue] does not show that 100% of the proceedings will go to charity but their support confirmed to me that it will and that the badge should show up soon.
 
 More photos after the click.
 <!--more-->
 
 <p class='img'>
-  <a href='https://teespring.com/stores/home-assistant-us-store'><img src='/images/blog/2017-02-shirts/pull-finger.png' /></a>
+  <img src='/images/blog/2017-02-shirts/pull-finger.png' />
-  Moment suprême of a solo pull-my-finger joke while wearing [the new blue Home Assistant shirt][blue].
+  Moment suprême of a solo pull-my-finger joke while wearing the new blue Home Assistant shirt. – [🇪🇺 EU][blue-eu] – [🇺🇸 US][blue-us]
 </p>
 <p class='img'>
-  <a href='https://teespring.com/stores/home-assistant-us-store'><img src='/images/blog/2017-02-shirts/group.png' /></a>
+  <img src='/images/blog/2017-02-shirts/group.png' />
-   Two men carrying two women and [the new blue Home Assistant shirt][blue].
+   Two men carrying two women and the new blue Home Assistant shirt. – [🇪🇺 EU][blue-eu] – [🇺🇸 US][blue-us]
 </p>
 <p class='img'>
-  <a href='https://teespring.com/stores/home-assistant-us-store'><img src='/images/blog/2017-02-shirts/lollipop.png' /></a>
+  <img src='/images/blog/2017-02-shirts/lollipop.png' />
-  Cute girl with gigantic lollipop rocking [the new black Home Assistant shirt][black].
+  Cute girl with gigantic lollipop rocking the new black Home Assistant shirt. – [🇪🇺 EU][black-eu] – [🇺🇸 US][black-us]
 </p>
 <p class='img'>
-  <a href='https://teespring.com/stores/home-assistant-us-store'><img src='/images/blog/2017-02-shirts/shout.png' /></a>
+  <img src='/images/blog/2017-02-shirts/shout.png' />
-  Frustrated user wearing [the new blue Home Assistant shirt][blue].
+  Frustrated user wearing the new blue Home Assistant shirt. – [🇪🇺 EU][blue-eu] – [🇺🇸 US][blue-us]
 </p>
 <p class='img'>
-  <a href='https://teespring.com/stores/home-assistant-us-store'><img src='/images/blog/2017-02-shirts/kids.png' /></a>
+  <img src='/images/blog/2017-02-shirts/kids.png' />
-  Cool kid listening to music + sidekick. Both wearing [the new blue Home Assistant shirt][blue].
+  Cool kid listening to music + sidekick. Both wearing the new blue Home Assistant shirt.  – [🇪🇺 EU][blue-eu] – [🇺🇸 US][blue-us]
 </p>
 
 [eff]: https://www.eff.org
 [le]: https://letsencrypt.org
 [ts]: https://teespring.com
 [ts-eu]: https://teespring.com/teespring-europe
-[store]: https://teespring.com/stores/home-assistant-us-store
+[store-us]: https://teespring.com/stores/home-assistant-us-store
+[store-eu]: https://teespring.com/stores/home-assistant-eu-store
 [eff-issues]: https://www.eff.org/issues
-[blue]: https://teespring.com/home-assistant-shirt
+[blue-us]: https://teespring.com/home-assistant-shirt
-[black]: https://teespring.com/hass-shirt-black
+[black-us]: https://teespring.com/hass-shirt-black
+[blue-eu]: https://teespring.com/hass-blue-shirt-eu-2
+[black-eu]: https://teespring.com/hass-shirt-black-eu-2

source/_posts/2017-02-25-config-panel-and-state-restoration.markdown

@@ -69,6 +69,8 @@ We realized that this was leading into a rabbit hole that we had to get out off.
 
 So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.
 
+[**Update: the online tool can be found here.**](https://jsfiddle.net/balloob/d2e56q6f/74/)
+
 #### Customize has been reverted to it's original config
 
 The old customize is back. The options to match by domain or using glob have been moved to it's own options. It will now look like this:
@@ -132,15 +134,15 @@ And a final shout out to [Pascal][@pvizeli]. He keeps improving the performance
 - Add [Ebox][ebox] sensor platform ([@titilambert])
 - Mediaplayer [clementine][clementine] remote ([@jjmontesl])
 - Add [Fido][fido] sensor ([@titilambert])
+- Add [History Statistics][history_stats] sensor platform ([@bokub])
 
 #### Improvements
 
-- Tellduslive: Don't thow exception if connection to server is lost ([@molobrakos])
+- Tellduslive: Don't throw exception if connection to server is lost ([@molobrakos])
 - Core: Convert config.components to a set ([@balloob])
 - Media Player - Apple TV: Handle connection errors when connecting to Apple TVs, re-use aiohttp session , add fake support for turn on/off ([@postlund])
 - Zoneminder: Refactoring and JSON decode error handling ([@pschmitt])
 - Recorder: Add tests for full schema migration, limit to session scope ([@armills])
-- Tests: Add history_stats sensor ([@bokub])
 - Device tracker - Tado: Add support for multiple devices to Tado device tracker ([@markoudev])
 - Z-Wave: Fix zwave helper getter not to fail on some None results. ([@andrey-git])
 - Core: `sensor_class` migrate to `device_class` ([@armills])
@@ -191,7 +193,18 @@ And a final shout out to [Pascal][@pvizeli]. He keeps improving the performance
 - Discovery: Make it possible to ignore platforms in discovery ([@postlund])
 - Image processing: Add `device_class` ([@pvizeli])
 
+### {% linkable_title Release 0.39.1 - February 27 %}
+
+ - Add workaround for Paho out of memory issues ([@pvizeli])
+ - When an error occurs while storing group config, fail instead of wiping config. ([@balloob])
+
+### {% linkable_title Release 0.39.2 - March 1 %}
+
+ - Move Zigbee from eventbus to dispatcher ([@pvizeli])
+ - Fix discovery taking up all memory and cpu ([@balloob] + [@tomusher])
+
 #### Breaking changes
+
  - VolvoOnCall has been extended with more features and had to be converted to a component
  - Limitlessled support for Bridge v6 and RGBWW bulbs require users to specify `version` and `port
  - hdmi_cec config now requires users to set the types in the hdmi_cec config instead of using `customize`:
@@ -203,6 +216,7 @@ hdmi_cec:
 ```
 
 #### Bugfixes:
+
 [@pvizeli], [@LinuxChristian], [@molobrakos], [@balloob], [@rytilahti], [@fabaff], [@andrey-git], [@aequitas], [@konikvranik], [@Danielhiversen], [@colinodell], [@pschmitt], [@bachp], [@bachp],[@w1ll1am23], [@valentinalexeev], [@robbiet480], [@MartinHjelmare], [@happyleavesaoc], [@tdickman], [@arraylabs], [@lwis], [@titilambert]
 
 ### If you need help...
@@ -211,6 +225,7 @@ hdmi_cec:
 ### Reporting Issues
 Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
 
+[@tomusher]: https://github.com/tomusher
 [@turbokongen]: https://github.com/turbokongen
 [@w1ll1am23]: https://github.com/w1ll1am23
 [@nugget]: https://github.com/nugget
@@ -266,7 +281,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [@kitcorey]: https://github.com/kitcorey
 [@andersonshatch]: https://github.com/andersonshatch
 
-[telegram]: https://home-assistant.io/componet/telegram_webhook/
+[telegram]: https://home-assistant.io/componet/telegram_webhooks/
 [pushsafer]: https://home-assistant.io/components/notify.pushsafer/
 [openhome]: https://home-assistant.io/components/media_player.openhome/
 [ups]: https://home-assistant.io/components/sensor.ups/
@@ -285,6 +300,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [volvo]: https://home-assistant.io/components/volvooncall/
 [pocket]: https://home-assistant.io/components/sensor.pocketcasts/
 [config]: https://home-assistant.io/components/config/
+[history_stats]: https://home-assistant.io/components/sensor.history_stats/
 
 
 [docs]: https://home-assistant.io/docs/

source/developers/api.markdown

@@ -9,7 +9,7 @@ sharing: true
 footer: true
 ---
 
-Home Assistant prvides various APIs. For detail please refer to [Home Assistant API](https://dev-docs.home-assistant.io/en/dev/) documentation.
+Home Assistant provides various APIs. For detail please refer to [Home Assistant API](https://dev-docs.home-assistant.io/en/dev/) documentation.
 
   * [Websocket API](/developers/websocket_api/)
   * [RESTful API](/developers/rest_api/)

source/developers/component_generic_discovery.markdown

@@ -43,14 +43,12 @@ In the hub component `myflashyhub.py` you can call your light and switch compone
 from homeassistant.helpers.discovery import load_platform
 DOMAIN = 'myflashyhub'
 
-MFH_GLOBAL = None
+DATA_MFH = 'MFH'
 
 def setup(hass, config):
     """Your controller/hub specific code."""
+    hass.data[DATA_MFH] = SomeObjectToInitialiseGlobal()
 
-    global MFH_GLOBAL
-    if MFH_GLOBAL is None:
-        MFH_GLOBAL = SomeObjectToInitialiseGlobal
     #--- snip ---
     load_platform(hass, 'light', DOMAIN)
     load_platform(hass, 'switch', DOMAIN, {'optional': 'arguments'})
@@ -65,7 +63,7 @@ import custom_components.myflashyhub as myflashyhub
 # as passed in above. 'light' will receive discovery_info=None
 def setup_platform(hass, config, add_devices, discovery_info=None):
     """Your switch/light specific code."""
-    # You can now use myflashyhub.MFH_GLOBAL
+    # You can now use hass.data[myflashyhub.DATA_MFH]
 ```
 
 

source/getting-started/use.markdown

@@ -11,7 +11,7 @@ footer: true
 
 If you are using Hassbian, browse to [http://hassbian.local:8123](http://hassbian.local:8123) to open the Home Assistant frontend.
 
-To reload your configuration, go to **Configuration** in your side panel, and choose:
+To reload your configuration, go to **Configuration** in your side panel, and choose "CHECK CONFIG" and "RELOAD CORE":
 
 <p class='img'>
 <img src='/images/screenshots/configuration-validation.png' />