Merge branch 'current' into next

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.