diff --git a/_config.yml b/_config.yml
index 10e1ef759d7..7d840828153 100644
--- a/_config.yml
+++ b/_config.yml
@@ -143,11 +143,11 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 49
-current_patch_version: 0
-date_released: 2017-07-16
+current_patch_version: 1
+date_released: 2017-07-24
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.
# Major release:
-patch_version_notes: "#"
+patch_version_notes: "#release-0491---july-24"
# Minor release (Example #release-0431---april-25):
diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss
index d428797a7f3..56d86c93af2 100644
--- a/sass/custom/_paulus.scss
+++ b/sass/custom/_paulus.scss
@@ -118,16 +118,21 @@ $primary-color: #049cdb;
}
}
- .founder-vision {
+ .highlight-blog-post {
+ font-size: 2.0rem;
+ line-height: 1.15;
+ padding: 15px;
display: block;
text-decoration: none;
color: white;
- padding: 15px;
- font-size: 2.25rem;
- line-height: 1.33333;
transition: background-color .5s;
background-color: #038FC7;
+ &.large {
+ font-size: 2.25rem;
+ line-height: 1.33333;
+ }
+
&:hover {
background-color: lighten(#038FC7, 10%);
}
@@ -184,6 +189,8 @@ $primary-color: #049cdb;
border: 0;
box-shadow: none;
margin: 15px;
+ width: 200px;
+ max-width: 40%;
}
}
}
@@ -406,7 +413,8 @@ p.note {
}
.edit-github {
- text-align: right;
+ float: right;
+ margin-left: 8px;
margin-bottom: 8px;
font-size: .8em;
}
diff --git a/source/_addons/check_config.markdown b/source/_addons/check_config.markdown
index 932f4d50547..0b00f1b147e 100644
--- a/source/_addons/check_config.markdown
+++ b/source/_addons/check_config.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Check Home Assistant configuration"
-description: "Check your current Home Assistant configuration against a new version"
+description: "Check your current Home Assistant configuration against a new version."
date: 2017-04-30 13:28
sidebar: true
comments: false
@@ -9,7 +9,7 @@ sharing: true
footer: true
---
-You can use this addon to check whether your configuration files are valid against the new version of Home Assistant before you actually update your Home Assistant. This will help you avoid errors due to breaking changes, resulting in smooth update.
+You can use this addon to check whether your configuration files are valid against the new version of Home Assistant before you actually update your Home Assistant installation. This will help you avoid errors due to breaking changes, resulting in an smooth update.
```json
{
diff --git a/source/_addons/mosquitto.markdown b/source/_addons/mosquitto.markdown
index 397b7b8f95c..ef75d1f1db7 100644
--- a/source/_addons/mosquitto.markdown
+++ b/source/_addons/mosquitto.markdown
@@ -10,7 +10,7 @@ footer: true
featured: true
---
-Set up a [mosquitto](https://mosquitto.org/) MQTT broker.
+Set up [Mosquitto](https://mosquitto.org/) as MQTT broker.
```json
{
@@ -22,12 +22,14 @@ Set up a [mosquitto](https://mosquitto.org/) MQTT broker.
],
"customize": {
"active": false,
- "folder": "mosquitto
+ "folder": "mosquitto",
}
}
```
-
Make sure you use logins and disable anonymous access if you want to secure the system.
+
+Make sure you use logins and disable anonymous access if you want to secure the system.
+
Configuration variables:
@@ -35,10 +37,12 @@ Configuration variables:
- **ssl** (*Optional*): Listen to broker on port 8883 with SSL/TLS. This requires certificates. Defaults to `false`.
- **anonymous** (*Optional*): Allow anonymous connection. If *logins* is set, anonymous user can only read data. Defaults to `true`.
- **logins** (*Optional*): A list of user that will be created with *username* and *password*.
-- **customize** (*Optional*): If you enable it, it read additional config files (`*.conf`) from `/share/mosquitto`.
+- **customize** (*Optional*): If you enable it, it reads additional configuration files (`*.conf`) from `/share/mosquitto`.
### {% linkable_title Home Assistant configuration %}
+To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own) add the following entry to the `configuration.yaml` file.
+
```yaml
# Example configuration.yaml entry
mqtt:
diff --git a/source/_addons/nginx_proxy.markdown b/source/_addons/nginx_proxy.markdown
index defb16a3847..fab4ac9842d 100644
--- a/source/_addons/nginx_proxy.markdown
+++ b/source/_addons/nginx_proxy.markdown
@@ -1,7 +1,7 @@
---
layout: page
-title: "Nginx SSL proxy"
-description: "Nginx Home Assistant SSL proxy"
+title: "NGINX SSL proxy"
+description: "NGINX Home Assistant SSL proxy."
date: 2017-04-30 13:28
sidebar: true
comments: false
@@ -9,8 +9,7 @@ sharing: true
footer: true
---
-Setup a SSL proxy with nginx and redirect port 80 to 443. Make sure you have generate certificate before you start this add-on.
-
+Setup a SSL proxy with NGINX and redirect port 80 to 443. Make sure you have generate certificate before you start this add-on.
```json
@@ -24,6 +23,6 @@ Configuration variables:
- **domain** (*Required*): Domain they will proxy run with it.
-It is possible to deactive port 80 if you need this for things like `emulate_hue`. It exists a the moment no UI function for that, so you need call hass.io API with ssh addon:
+It is possible to deactive port 80 if you need this for things like `emulate_hue`. It exists a the moment no UI function for that, so you need call Hass.io API with SSH addon:
`curl -d '{"network": {"443/tcp": 443}}' http://172.17.0.2/addons/core_nginx_proxy/options`
diff --git a/source/_addons/samba.markdown b/source/_addons/samba.markdown
index c755b8abbb6..e434e6f15ee 100644
--- a/source/_addons/samba.markdown
+++ b/source/_addons/samba.markdown
@@ -35,7 +35,7 @@ Configuration variables:
- **name** (*Optional*): default `hassio`. Set netbios name of hassio device.
- **workgroup** (*Optional*): default `WORKGROUP`. Set network workgroup.
- **guest** (*Optional*): Allow login without a username or password. Defaults to `true`.
-- **map** (*Optional*): Control whitch folder will be expose. `config` is for Home Assistant configuration folder. `addons` for local custom repositiory. `share` is a folder that can access from add-ons and Home Assistant too. `backup` for access to snapshot files. `ssl` for certificate storage, be careful with this option! Defaults to `true`.
+- **map** (*Optional*): Control which folder will be expose. `config` is for Home Assistant configuration folder. `addons` for local custom repositiory. `share` is a folder that can access from add-ons and Home Assistant too. `backup` for access to snapshot files. `ssl` for certificate storage, be careful with this option! Defaults all to `true`, except for `ssl`.
- **username** (*Optional*): The username for logging in if guest login is not used.
- **password** (*Optional*): Password for `username`. An empty password is not supported.
- **interface** (*Optional*): Interface on that will start the share. Normaly is `eth0` for ethernet wired connection and `wlan0` for wireless connection.
diff --git a/source/_addons/ssh.markdown b/source/_addons/ssh.markdown
index 44cdbe6c8f4..64ab8e54cb1 100644
--- a/source/_addons/ssh.markdown
+++ b/source/_addons/ssh.markdown
@@ -10,28 +10,39 @@ footer: true
featured: true
---
-Setting up an [SSH](https://openssh.org/) server allows access to your Hass.io folders with any SSH client. It include also a cli to access into Hass.IO api. Try it out:
+Setting up an [SSH](https://openssh.org/) server allows access to your Hass.io folders with any SSH client. It include also a command-line tool to access the [Hass.io API](https://github.com/home-assistant/hassio/blob/dev/API.md). Try it out:
```bash
$ hassio help
```
-
This add-on will not enable you to install packages or do anything as root. This is not allowed with Hass.io.
+
+This add-on will not enable you to install packages or do anything as root. This is not allowed with Hass.io.
+
-To use this add-on, you must have a private/public key to log in. To generate them, follow the [instructions for Windows][win] and [these for other platforms][other].
+To use this add-on, you must have a private/public key to log in. To generate them, follow the [instructions for Windows][win] and [these for other platforms][other]. It is possible to set a password for login since version 2.0 but for hight security use private/public keys. You can not run both variant at same time.
```json
{
"authorized_keys": [
"ssh-rsa AKDJD3839...== my-key"
- ]
+ ],
+ "password": ""
}
```
+The username for login over ssh is `root`.
+
Configuration variables:
-- **authorized_keys** (*Required*): Your public-keys for authorized keyfile. Every element will be a line inside that file.
+- **authorized_keys** (*Optional*): Your public-keys for authorized keyfile. Every element will be a line inside that file.
+- **password** (*Optional*): Set a password for login. We do not recommend this variant.
+
+
+
This add-on is not compatible when you installed Hass.io via the generic Linux installer.
+
This add-on is not compatible if Hass.io was installed via the generic Linux installer.
diff --git a/source/_components/binary_sensor.flic.markdown b/source/_components/binary_sensor.flic.markdown
index 126eb15c020..c6a5b19e92b 100644
--- a/source/_components/binary_sensor.flic.markdown
+++ b/source/_components/binary_sensor.flic.markdown
@@ -30,7 +30,7 @@ Configuration variables:
- **host** (*Optional*): The IP or hostname of the flic service server. Defaults to `localhost`.
- **port** (*Optional*): The port of the flic service. Defaults to `5551`.
- **discovery** (*Optional*): If `true` then the component is configured to constantly scan for new buttons. Defaults to `true`.
-- **ignored_click_types**: List of click types whose occurrence should not trigger and `flic_click` event.
+- **ignored_click_types**: List of click types whose occurrence should not trigger a `flic_click` event. Click types are `single`, `double`, and `hold`.
- **timeout** (*Optional*): Maximum time in seconds an event can be queued locally on a button before discarding the event. Defaults to 3.
#### {% linkable_title Discovery %}
@@ -38,7 +38,7 @@ Configuration variables:
If discovery is enabled, you can add a new button by pressing it for at least 7 seconds. The button will be paired with the flic service and added to Home Assistant. Otherwise, you have to manually pair it with the flic service. The Home Assistant platform will not scan for new buttons and will only connect to buttons already paired.
#### {% linkable_title Timeout %}
- +When the flic button is triggered while disconnected from flic service, it will queue all events and try to connect and transmit them as soon as possible. The timeout variable can be used to stop events from triggering if too much time passed between the action and the notification in Home Assistant.
+ When the flic button is triggered while disconnected from flic service, it will queue all events and try to connect and transmit them as soon as possible. The timeout variable can be used to stop events from triggering if too much time passed between the action and the notification in Home Assistant.
#### {% linkable_title Events %}
diff --git a/source/_components/binary_sensor.markdown b/source/_components/binary_sensor.markdown
index a2cc7ee8518..43b66dd453e 100644
--- a/source/_components/binary_sensor.markdown
+++ b/source/_components/binary_sensor.markdown
@@ -15,7 +15,7 @@ Knowing that there are only two states allows Home Assistant to represent these
The way these sensors are displayed in the frontend can be modified in the [customize section](/getting-started/customizing-devices/). The following device classes are supported for binary sensors:
-- **None**: Generic on/off
+- **None**: Generic on/off. This is the default and doesn't need to be set.
- **cold**: `On` means cold
- **connectivity**: `On` means connection present, `Off` means no connection
- **gas**: `On` means gas detected
diff --git a/source/_components/binary_sensor.wink.markdown b/source/_components/binary_sensor.wink.markdown
index aaff7d4e451..9c975eff79b 100644
--- a/source/_components/binary_sensor.wink.markdown
+++ b/source/_components/binary_sensor.wink.markdown
@@ -28,7 +28,7 @@ The requirement is that you have setup [Wink](/components/wink/).
- Liquid presense sensors
- Z-wave lock key codes
- Lutron connected bulb remote buttons
-- Wink Relay buttons and presense detection
+- Wink Relay buttons and presence detection
- Wink spotter loudness and vibration (No Wink hub required)
- Wink hub devices connection status. This includes any paired hubs like Hue, Wink v1, Wink v2, Wink Relay...
- Dropcam sensors
diff --git a/source/_components/media_extractor.markdown b/source/_components/media_extractor.markdown
index 05f197f079d..3875579d3c0 100644
--- a/source/_components/media_extractor.markdown
+++ b/source/_components/media_extractor.markdown
@@ -53,7 +53,7 @@ More info about queries [here](https://github.com/rg3/youtube-dl#format-selectio
### {% linkable_title Use the service %}
-Go to the "Developer Tools", then to "Call Service", and choose `media_extractor/play_media` from the list of available services. Fill the "Service Data" field as shown in the example below and hit "CALL SERVICE".
+Go to the "Developer Tools," then to "Call Service," and choose `media_extractor/play_media` from the list of available services. Fill the "Service Data" field as shown in the example below and hit "CALL SERVICE."
This will download the file from the given URL.
diff --git a/source/_components/media_player.onkyo.markdown b/source/_components/media_player.onkyo.markdown
index f0fb1580963..e78075c01a5 100644
--- a/source/_components/media_player.onkyo.markdown
+++ b/source/_components/media_player.onkyo.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Onkyo"
-description: "Instructions how to integrate Onkyo receivers into Home Assistant."
+description: "Instructions how to integrate Onkyo and some Pioneer receivers into Home Assistant."
date: 2016-03-30 08:00
sidebar: true
comments: false
@@ -14,9 +14,9 @@ ha_iot_class: "Local Polling"
---
-The `onkyo` platform allows you to control a [Onkyo receiver](http://www.onkyo.com/) from Home Assistant. Please be aware that you need to enable "Network Standby" for this component to work in your Hardware.
+The `onkyo` platform allows you to control a [Onkyo](http://www.onkyo.com/) and some recent [Pioneer](http://www.pioneerelectronics.com) receivers from Home Assistant. Please be aware that you need to enable "Network Standby" for this component to work in your Hardware.
-To add an Onkyo receiver to your installation, add the following to your `configuration.yaml` file:
+To add an Onkyo or Pioneer receiver to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
diff --git a/source/_components/media_player.pioneer.markdown b/source/_components/media_player.pioneer.markdown
index 720241193d9..66086c5ded3 100644
--- a/source/_components/media_player.pioneer.markdown
+++ b/source/_components/media_player.pioneer.markdown
@@ -14,7 +14,7 @@ ha_release: 0.19
ha_iot_class: "Local Polling"
---
-The `pioneer` platform allows you to control Pioneer Network Receivers.
+The `pioneer` platform allows you to control Pioneer Network Receivers. Please note, however, that the more recent Pioneer models work with [Onkyo](/components/media_player.onkyo/) platform instead.
To add a Pioneer receiver to your installation, add the following to your `configuration.yaml` file:
diff --git a/source/_components/recorder.markdown b/source/_components/recorder.markdown
index ecf4a2003c2..7c8c16d2bd5 100644
--- a/source/_components/recorder.markdown
+++ b/source/_components/recorder.markdown
@@ -120,6 +120,10 @@ homeassistant@homeassistant:/srv/homeassistant/homeassistant_venv$ source bin/ac
(homeassistant_venv) homeassistant@homeassistant:/srv/homeassistant/homeassistant_venv$ pip3 install mysqlclient
```
+After installing the dependencies, it is required to create the database manually. During the startup, Home Assistant will look for the database specified in the `db_url`. If the database doesn't exist, it will not automatically create it for you.
+
+Once Home Assistant finds the database, with right level of permissions, all the required tables will then be automatically created and the data will be populated accordingly.
+
### {% linkable_title PostgreSQL %}
For PostgreSQL you may have to install a few dependencies:
diff --git a/source/_components/sensor.buienradar.markdown b/source/_components/sensor.buienradar.markdown
index b7a4b8714a9..b42e120eddf 100644
--- a/source/_components/sensor.buienradar.markdown
+++ b/source/_components/sensor.buienradar.markdown
@@ -14,8 +14,9 @@ ha_iot_class: "Cloud Polling"
---
-The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands.
-The relevant weatherstation used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). The selected weatherstation will provide all weather data, with the exception of the forecasted precipitaion. The forecasted precipitation data will be retrieved from buienradar using your actual gps-location (and not the location of the nearest weatherstation).
+The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands. The relevant weatherstation used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). A map of all available weatherstations can be found [here](https://www.google.com/maps/d/embed?mid=1NivHkTGQUOs0dwQTnTMZi8Uatj0).
+
+The selected weatherstation will provide all weather data, with the exception of the forecasted precipitation. The forecasted precipitation data will be retrieved from buienradar using your actual gps-location (and not the location of the nearest weatherstation).
To integrate `buienradar` with Home Assistant, add the following section to your `configuration.yaml` file:
@@ -42,7 +43,7 @@ Configuration variables:
- `sensor.br_ground_temperature`, since no name has been set for the sensor and the default display name for monitored condition `groundtemperature` is `Ground Temperature`
- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.nl.
- **longitude** (*Optional*): Longitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.nl.
-- **timeframe** (*Optional*): Minutes to look ahead for precipitation (5..120) [default: 60].
+- **timeframe** (*Optional*): Minutes to look ahead for precipitation forecast (5..120) [default: 60].
- **monitored_conditions** array (*Required*): One or more conditions to display in the frontend.
- **stationname**: The name of the selected meteo-station.
- **symbol**: A symbol for the current weather.
@@ -66,6 +67,8 @@ Full configuration example where location is manually specified:
```yaml
# Example configuration.yaml entry
- platform: buienradar
+ name: 'volkel'
+ # Force 'Meetstation Volkel' to be used:
latitude: 51.65
longitude: 5.70
monitored_conditions:
@@ -86,4 +89,6 @@ Full configuration example where location is manually specified:
- precipitation_forecast_average
- precipitation_forecast_total
```
-
+
+[Usage statement:](https://www.buienradar.nl/overbuienradar/gratis-weerdata)
+> Buienradar makes free weatherdata available for use by individuals and businesses (website/intranet). The use of the weatherdata is allowed for **non-commercial purposes**. Please refer to the full usage statement linked above to confirm your usage or to request permission.
diff --git a/source/_components/sensor.random.markdown b/source/_components/sensor.random.markdown
index 44bdfad4fa8..ac61331913b 100644
--- a/source/_components/sensor.random.markdown
+++ b/source/_components/sensor.random.markdown
@@ -14,7 +14,7 @@ ha_release: 0.32
---
-The `random` sensor platform is creating random sensor values (integers) out of a given range. This can be useful if you want to test automation rules.
+The `random` sensor platform is creating random sensor values (integers) out of a given range. This can be useful if you want to test automation rules. It generates a new value every time it is polled.
To enable the random sensor, add the following lines to your `configuration.yaml`:
@@ -31,3 +31,6 @@ Configuration variables:
- **maximum** (*Optional*): Upper limit for the values. Defaults to `20`.
- **unit_of_measurement** (*Optional*): Defines the units of measurement of the sensor, if any.
+See the [entity component options][entity-docs] to control how often the main component polls the random sensor. The default is 30 seconds.
+
+[entity-docs]: https://home-assistant.io/docs/configuration/platform_options/
diff --git a/source/_components/switch.mqtt.markdown b/source/_components/switch.mqtt.markdown
index 546ad7fc78f..a31e4bc4301 100644
--- a/source/_components/switch.mqtt.markdown
+++ b/source/_components/switch.mqtt.markdown
@@ -35,6 +35,7 @@ Configuration variables:
- **name** (*Optional*): The name of the switch. Default is 'MQTT Switch'.
- **state_topic** (*Optional*): The MQTT topic subscribed to receive state updates.
- **command_topic** (*Required*): The MQTT topic to publish commands to change the switch state.
+- **availability_topic** (*Optional*): The MQTT topic subscribed to receive availability (online/offline) updates. The payload is the same for the command_topic.
- **payload_on** (*Optional*): The payload that represents enabled state. Default is "ON".
- **payload_off** (*Optional*): The payload that represents disabled state. Default is "OFF".
- **optimistic** (*Optional*): Flag that defines if switch works in optimistic mode. Default is `true` if no `state_topic` defined, else `false`.
@@ -61,6 +62,7 @@ switch:
name: "Bedroom Switch"
state_topic: "home/bedroom/switch1"
command_topic: "home/bedroom/switch1/set"
+ availability_topic: "home/bedroom/switch1/available"
payload_on: "ON"
payload_off: "OFF"
optimistic: false
diff --git a/source/_components/telegram_bot.webhooks.markdown b/source/_components/telegram_bot.webhooks.markdown
index 491b292879b..aacbdffe549 100644
--- a/source/_components/telegram_bot.webhooks.markdown
+++ b/source/_components/telegram_bot.webhooks.markdown
@@ -14,6 +14,8 @@ ha_release: 0.42
Telegram chatbot webhooks implementation as described in the Telegram [documentation](https://core.telegram.org/bots/webhooks).
+Using Telegrams `setWebhook` method your bot's webhook URL should be set to `https://:/api/telegram_webhooks`.
+
This is one of two bot implementations supported by Telegram. Described by Telegram as the preferred implementation but requires your Home Assistant instance to be exposed to the internet.
To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:
diff --git a/source/_components/tradfri.markdown b/source/_components/tradfri.markdown
index 8bd6a2af081..7145cedc4f3 100644
--- a/source/_components/tradfri.markdown
+++ b/source/_components/tradfri.markdown
@@ -35,15 +35,15 @@ $ sudo make install
macOS:
```bash
-$ sudo brew install libtool
-$ sudo brew install autoconf
-$ sudo brew install automake
+$ brew install libtool
+$ brew install autoconf
+$ brew install automake
$ git clone --depth 1 --recursive -b dtls https://github.com/home-assistant/libcoap.git
$ cd libcoap
$ ./autogen.sh
$ ./configure --disable-documentation --disable-shared --without-debug CFLAGS="-D COAP_DEBUG_FD=stderr"
$ make
-$ sudo make install
+$ make install
```
You will be prompted to configure the gateway through the Home Assistant interface, Enter the security key when prompted and click configure
diff --git a/source/_components/weather.buienradar.markdown b/source/_components/weather.buienradar.markdown
index 07da95af18c..682e85c2827 100644
--- a/source/_components/weather.buienradar.markdown
+++ b/source/_components/weather.buienradar.markdown
@@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling"
---
The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands.
-The relevant weatherstation used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component).
+The relevant weatherstation used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). A map of all available weatherstations can be found [here](https://www.google.com/maps/d/embed?mid=1NivHkTGQUOs0dwQTnTMZi8Uatj0).
To add the buienradar weather to your installation, add the following to your `configuration.yaml` file:
@@ -38,7 +38,8 @@ A full configuration example:
# Example configuration.yaml entry
weather:
- platform: buienradar
- name: buienradar
+ name: 'volkel'
+ # Force 'Meetstation Volkel' to be used:
latitude: 51.65
longitude: 5.70
forecast: True
@@ -48,3 +49,6 @@ weather:
This platform is an alternative to the [`buienradar`](/components/sensor.buienradar/) sensor.
The weather platform is easier to configure but less customisable.
+
+[Usage statement:](https://www.buienradar.nl/overbuienradar/gratis-weerdata)
+> Buienradar makes free weatherdata available for use by individuals and businesses (website/intranet). The use of the weatherdata is allowed for **non-commercial purposes**. Please refer to the full usage statement linked above to confirm your usage or to request permission.
diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown
index 8da78ab7a68..23411246de3 100644
--- a/source/_docs/configuration/customizing-devices.markdown
+++ b/source/_docs/configuration/customizing-devices.markdown
@@ -67,6 +67,7 @@ homeassistant:
| `assumed_state` | For switches with an assumed state two buttons are shown (turn off, turn on) instead of a switch. By setting `assumed_state` to `false` you will get the default switch icon.
| `device_class` | Sets the class of the device, changing the device state and icon that is displayed on the UI (see below).
| `initial_state` | Sets the initial state for automations. `on` or `off`.
+| `unit_of_measurement` | Defines the units of measurement, if any.
### {% linkable_title Device Class %}
diff --git a/source/_docs/hassbian.markdown b/source/_docs/installation/hassbian.markdown
similarity index 100%
rename from source/_docs/hassbian.markdown
rename to source/_docs/installation/hassbian.markdown
diff --git a/source/_docs/hassbian/common-tasks.markdown b/source/_docs/installation/hassbian/common-tasks.markdown
similarity index 98%
rename from source/_docs/hassbian/common-tasks.markdown
rename to source/_docs/installation/hassbian/common-tasks.markdown
index 262770e8d20..ce294b5c1b9 100644
--- a/source/_docs/hassbian/common-tasks.markdown
+++ b/source/_docs/installation/hassbian/common-tasks.markdown
@@ -7,13 +7,13 @@ sidebar: true
comments: false
sharing: true
footer: true
-redirect_from: /getting-started/hassbian-common-tasks/
+redirect_from: /docs/hassbian/common-tasks/
---
### {% linkable_title Login to the Raspberry Pi %}
To login to your Raspberry Pi running HASSbian you're going to be using a ssh client. Depending on your platform there are several alternatives for doing this. Linux and Max OS generally have a ssh client installed. Windows users are recommended to download and install the ssh client [Putty][ssh-putty].
-Connect to the Raspberry Pi over ssh. Default user name is `pi` and password is `raspberry`.
+Connect to the Raspberry Pi over ssh. Default user name is `pi` and password is `raspberry`.
Linux and Mac OS users execute the following command in a terminal.
```bash
diff --git a/source/_docs/hassbian/customization.markdown b/source/_docs/installation/hassbian/customization.markdown
similarity index 97%
rename from source/_docs/hassbian/customization.markdown
rename to source/_docs/installation/hassbian/customization.markdown
index dfc566f1ff8..1b295b83efe 100644
--- a/source/_docs/hassbian/customization.markdown
+++ b/source/_docs/installation/hassbian/customization.markdown
@@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
-redirect_from: /getting-started/hassbian-customization/
+redirect_from: /docs/hassbian/customization/
---
To allow you to customize your installation further, we have included a tool called `hassbian-config`. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation.
diff --git a/source/_docs/hassbian/installation.markdown b/source/_docs/installation/hassbian/installation.markdown
similarity index 97%
rename from source/_docs/hassbian/installation.markdown
rename to source/_docs/installation/hassbian/installation.markdown
index e1e2cd5516b..df50d186801 100644
--- a/source/_docs/hassbian/installation.markdown
+++ b/source/_docs/installation/hassbian/installation.markdown
@@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
-redirect_from: /getting-started/installation-raspberry-pi-image/
+redirect_from: /docs/hassbian/installation/
---
The easiest way to install Home Assistant on your Raspberry Pi is by using HASSbian: a Raspberry Pi image with Home Assistant built-in. The image will install the latest version of Home Assistant on initial boot (~10 minutes).
diff --git a/source/_docs/hassbian/integrations.markdown b/source/_docs/installation/hassbian/integrations.markdown
similarity index 98%
rename from source/_docs/hassbian/integrations.markdown
rename to source/_docs/installation/hassbian/integrations.markdown
index fe1cebcf400..e48f9e35367 100644
--- a/source/_docs/hassbian/integrations.markdown
+++ b/source/_docs/installation/hassbian/integrations.markdown
@@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
-redirect_from: /getting-started/hassbian-installation/
+redirect_from: /docs/hassbian/integrations/
---
Some components that are specific for the Raspberry Pi can require some further configuration outside of Home Assistant. All commands below are assumed to be executed with the `pi` account. For full documentation of these components refer to the [components](/components) page.
diff --git a/source/_docs/hassbian/upgrading.markdown b/source/_docs/installation/hassbian/upgrading.markdown
similarity index 94%
rename from source/_docs/hassbian/upgrading.markdown
rename to source/_docs/installation/hassbian/upgrading.markdown
index 0af3dc90c83..0ac77e21b12 100644
--- a/source/_docs/hassbian/upgrading.markdown
+++ b/source/_docs/installation/hassbian/upgrading.markdown
@@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
-redirect_from: /getting-started/hassbian-upgrading/
+redirect_from: /docs/hassbian/upgrading/
---
HASSbian is based on Raspbian and uses the same repositories. Any changes to Raspbian will be reflected in HASSbian. To update and upgrade system packages and installed software (excluding Home Assistant) do the following.
diff --git a/source/_includes/asides/docs_navigation.html b/source/_includes/asides/docs_navigation.html
index 24d52934717..25b6afd3a58 100644
--- a/source/_includes/asides/docs_navigation.html
+++ b/source/_includes/asides/docs_navigation.html
@@ -8,22 +8,14 @@
diff --git a/source/_posts/2017-07-16-release-49.markdown b/source/_posts/2017-07-16-release-49.markdown
index 10ab8ca15e9..81aaab898ad 100644
--- a/source/_posts/2017-07-16-release-49.markdown
+++ b/source/_posts/2017-07-16-release-49.markdown
@@ -57,6 +57,25 @@ This feature has also been brought to you by [@Andrey-git]! Big shout out to him
- Added media_extractor service ([@minchik] - [#8369]) ([media_extractor docs]) (new-platform)
- Vizio SmartCast support ([@vkorn] - [#8260]) ([media_player.vizio docs]) (new-platform)
+## {% linkable_title Release 0.49.1 - July 24 %}
+
+- Fix TP-Link device tracker regression since 0.49 ([@maikelwever] - [#8497]) ([device_tracker.tplink docs])
+- prometheus: Convert fahrenheit to celsius ([@rcloran] - [#8511]) ([prometheus docs])
+- Update dlib_face_detect.py ([@pvizeli] - [#8516]) ([image_processing.dlib_face_detect docs])
+- Realfix for dlib ([@pvizeli] - [#8517]) ([image_processing.dlib_face_detect docs])
+- Attach the `chat_id` for a callback query from a chat group (fixes #8461) ([@azogue] - [#8523]) ([telegram_bot docs])
+- Fix support for multiple Apple TVs ([@postlund] - [#8539])
+- LIFX: assume default features for unknown products ([@amelchio] - [#8553]) ([light.lifx docs])
+- Fix broken status update for lighting4 devices ([@ypollart] - [#8543]) ([rfxtrx docs]) ([binary_sensor.rfxtrx docs])
+- zha: Update to bellows 0.3.4 ([@rcloran] - [#8594]) ([zha docs])
+- Fix STATION_SCHEMA validation on longitude ([@clkao] - [#8610]) ([sensor.citybikes docs])
+- Bumped Amcrest version ([@tchellomello] - [#8624]) ([amcrest docs])
+- Check if /dev/input/by-id exists ([@schaal] - [#8601]) ([keyboard_remote docs])
+- Tado Fix #8606 ([@filcole] - [#8621]) ([climate.tado docs])
+- prometheus: Fix zwave battery level ([@rcloran] - [#8615]) ([prometheus docs])
+- ubus: Make multiple instances work again ([@glance-] - [#8571]) ([device_tracker.ubus docs])
+- Properly slugify switch.flux update service name ([@jawilson] - [#8545]) ([switch.flux docs])
+
## {% linkable_title If you need help... %}
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
@@ -395,7 +414,6 @@ amcrest:
[light.zha docs]: https://home-assistant.io/components/light.zha/
[lutron docs]: https://home-assistant.io/components/lutron/
[media_extractor docs]: https://home-assistant.io/components/media_extractor/
-[media_extractor docs]: https://home-assistant.io/components/media_extractor/
[media_player.apple_tv docs]: https://home-assistant.io/components/media_player.apple_tv/
[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/
[media_player.emby docs]: https://home-assistant.io/components/media_player.emby/
@@ -432,7 +450,6 @@ amcrest:
[sensor.openweathermap docs]: https://home-assistant.io/components/sensor.openweathermap/
[sensor.otp docs]: https://home-assistant.io/components/sensor.otp/
[sensor.rflink docs]: https://home-assistant.io/components/sensor.rflink/
-[sensor.london_underground docs]: https://home-assistant.io/components/sensor.london_underground/
[sensor.uber docs]: https://home-assistant.io/components/sensor.uber/
[sensor.waqi docs]: https://home-assistant.io/components/sensor.waqi/
[sensor.yweather docs]: https://home-assistant.io/components/sensor.yweather/
@@ -460,3 +477,31 @@ amcrest:
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
[discord]: https://discord.gg/c5DvZ4e
+[#8497]: https://github.com/home-assistant/home-assistant/pull/8497
+[#8511]: https://github.com/home-assistant/home-assistant/pull/8511
+[#8516]: https://github.com/home-assistant/home-assistant/pull/8516
+[#8517]: https://github.com/home-assistant/home-assistant/pull/8517
+[#8523]: https://github.com/home-assistant/home-assistant/pull/8523
+[#8539]: https://github.com/home-assistant/home-assistant/pull/8539
+[#8543]: https://github.com/home-assistant/home-assistant/pull/8543
+[#8553]: https://github.com/home-assistant/home-assistant/pull/8553
+[#8594]: https://github.com/home-assistant/home-assistant/pull/8594
+[#8610]: https://github.com/home-assistant/home-assistant/pull/8610
+[@clkao]: https://github.com/clkao
+[@maikelwever]: https://github.com/maikelwever
+[@ypollart]: https://github.com/ypollart
+[binary_sensor.rfxtrx docs]: https://home-assistant.io/components/binary_sensor.rfxtrx/
+[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
+[#8545]: https://github.com/home-assistant/home-assistant/pull/8545
+[#8571]: https://github.com/home-assistant/home-assistant/pull/8571
+[#8601]: https://github.com/home-assistant/home-assistant/pull/8601
+[#8615]: https://github.com/home-assistant/home-assistant/pull/8615
+[#8621]: https://github.com/home-assistant/home-assistant/pull/8621
+[#8624]: https://github.com/home-assistant/home-assistant/pull/8624
+[@filcole]: https://github.com/filcole
+[@glance-]: https://github.com/glance-
+[@jawilson]: https://github.com/jawilson
+[@schaal]: https://github.com/schaal
+[device_tracker.ubus docs]: https://home-assistant.io/components/device_tracker.ubus/
+[keyboard_remote docs]: https://home-assistant.io/components/keyboard_remote/
+[switch.flux docs]: https://home-assistant.io/components/switch.flux/
diff --git a/source/_posts/2017-07-25-introducing-hassio.markdown b/source/_posts/2017-07-25-introducing-hassio.markdown
new file mode 100644
index 00000000000..3a181997f61
--- /dev/null
+++ b/source/_posts/2017-07-25-introducing-hassio.markdown
@@ -0,0 +1,97 @@
+---
+layout: post
+title: "Introducing Hass.io"
+description: "The ultimate home automation hub has arrived."
+date: 2017-07-25 00:02:05 +0000
+date_formatted: "July 25, 2017"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Announcements
+og_image: /images/hassio/screenshots/dashboard.png
+---
+
+**TL;DR:** Today we're introducing [Hass.io]. Hass.io is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration and can easily be extended using [Hass.io add-ons][addons] including [Google Assistant] and [Let's Encrypt].
+
+----
+
+Home Assistant is 2 months away from being 4 years old. In that time the Internet of Things has really taken off and we've seen many new devices and services. We saw the introduction of voice assistants like Google Home and new standards like Apple HomeKit.
+
+Some things have been supported natively in Home Assistant, others have been integrated into Home Assistant via third party applications. All these moving parts caused our users to spend a lot of time maintaining their systems and applications instead of automating their homes.
+
+So we decided to take a step back from day-to-day Home Assistant development and see if we could offer a solution that makes updating a breeze for our users. A solution that you can flash to your Raspberry Pi and no longer worry about. A solution that would still be local first and respect the user's privacy.
+
+And this is how [Pascal Vizeli] came up with Hass.io, an operating system based on [ResinOS] and [Docker]. Hass.io will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows taking/restoring snapshots of your configuration and can easily be extended using [Hass.io add-ons][addons].
+
+
+
+Hass.io dashboard
+
+
+To install add-ons, a user can browse the built-in add-on store and install, configure and update any available application. Want to turn your device into a Google Assistant or make your configuration accessible via Samba/Windows networking? Both are a couple of clicks away! ([Video demo - 38s, no audio][install-demo])
+
+At launch we have included a couple of [built-in add-ons][addons] like [Google Assistant], [Let's Encrypt] and [Duck DNS]. Besides our internal add-ons, it is also possible to create and share your own add-on repositories. During our beta period we've already seen some great add-ons being shared: [Homebridge][olivierg], [InfluxDB][bestlibre], [HASS Configurator][danielperna] and [AppDaemon][vkorn].
+
+As we strongly believe in the openness of technology, we are releasing Hass.io as [open source] under the Apache 2.0 license. That way any user can make sure that the code that runs in their homes is secure and safe.
+
+- [Learn more about Hass.io][Hass.io]
+- [Install Hass.io][install]
+- [Available add-ons][addons]
+
+_Some frequently asked questions are answered below in the read more section._
+
+
+
+
+
+Hass.io has been built by [Pascal Vizeli], the UI has been made by [Paulus Schoutsen] and [BRUHAutomation] made the introduction video. Big thanks to [Resin.io] for building ResinOS and helping us get started with it. Also a big thanks to the community for early feedback, helping out with the documentation and add-on development ❤️
+
+
+
+#### {% linkable_title Will Hass.io be the only way to run Home Assistant? %}
+
+Hass.io is and will always be optional. You can still run Home Assistant wherever you can run Python.
+
+#### {% linkable_title Which devices are supported at launch? %}
+
+Initially we support the Raspberry Pi 1, 2, 3 and Intel NUC. Advanced users can also [install Hass.io on a Linux server][advanced-install].
+
+#### {% linkable_title Can I install packages or scripts on the machine? %}
+
+No, this is not possible as we're using stateless Docker containers. To install a package you'll have to write a local add-on that interacts with Home Assistant. See [our tutorial][run-local].
+
+#### {% linkable_title Can I restore a snapshot on a different device? %}
+
+Yes, any Hass.io snapshot can be restored on any device.
+
+#### {% linkable_title The Hass.io configuration panel contains powerful tools. Why is there no extra security besides the Home Assistant login? %}
+
+This is in the works. We have already implemented [the backend](https://github.com/home-assistant/hassio/pull/41) and plan to release the UI soon.
+
+#### {% linkable_title Is there a roadmap? %}
+
+We use [Pivotal Tracker] to track things that are in progress and what we might work on.
+
+[Hass.io]: /hassio
+[install]: /hassio/installation
+[Homebridge]: https://github.com/nfarina/homebridge
+[hb-hass]: https://github.com/home-assistant/homebridge-homeassistant
+[Pascal Vizeli]: https://github.com/pvizeli/
+[Paulus Schoutsen]: https://github.com/balloob/
+[ResinOS]: https://resinos.io/
+[Docker]: https://www.docker.com/
+[addons]: /addons/
+[bestlibre]: https://community.home-assistant.io/t/repository-bestlibre-addons-repository/18037
+[danielperna]: https://community.home-assistant.io/t/repository-hass-configurator/17838
+[olivierg]: https://community.home-assistant.io/t/repository-homebridge-add-on/18569
+[vkorn]: https://community.home-assistant.io/t/repository-few-addons/20659
+[install-demo]: https://youtu.be/NfyavpAg4as
+[BRUHAutomation]: https://www.youtube.com/channel/UCLecVrux63S6aYiErxdiy4w
+[open source]: https://github.com/home-assistant/hassio
+[Google Assistant]: /addons/google_assistant/
+[Let's Encrypt]: /addons/lets_encrypt/
+[Duck DNS]: /addons/duckdns/
+[advanced-install]: /hassio/installation/#alternative-install-on-generic-linux-server
+[Pivotal Tracker]: https://www.pivotaltracker.com/n/projects/2020851
+[run-local]: /hassio/run_local/
+[Resin.io]: https://resin.io
diff --git a/source/_posts/2017-07-27-talk-python-podcast.markdown b/source/_posts/2017-07-27-talk-python-podcast.markdown
new file mode 100644
index 00000000000..9b364cb1ed6
--- /dev/null
+++ b/source/_posts/2017-07-27-talk-python-podcast.markdown
@@ -0,0 +1,22 @@
+---
+layout: post
+title: "Talk Python interview with Paulus Schoutsen"
+description: "In this episode of Talk Python, Michael Kennedy interviews Paulus Schoutsen about Hass.io and the perfect home automation."
+date: 2017-07-27 02:00:00
+date_formatted: "July 27, 2017"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Media
+og_image: /images/blog/2017-07-talk-python/logo.png
+---
+
+
+
+Join Michael Kennedy at the Talk Python podcast for an hour long interview with Paulus Schoutsen, the founder of Home Assistant, as they discuss the release of Hass.io and the vision for the perfect home automation.
+
+
+ Visit the episode page on Talk Python
+
diff --git a/source/developers/architecture.markdown b/source/developers/architecture.markdown
index 2e967a087c5..422777573b4 100644
--- a/source/developers/architecture.markdown
+++ b/source/developers/architecture.markdown
@@ -7,6 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
+og_image: /images/architecture/ha_architecture.png
---
Before we dive into the Home Assistant architecture, let's get a clear overview of the home automation landscape as a whole. This way, we can show how the different parts of Home Assistant fit into the picture.
diff --git a/source/developers/architecture_components.markdown b/source/developers/architecture_components.markdown
index eff2ff1f2e6..095a4f73781 100644
--- a/source/developers/architecture_components.markdown
+++ b/source/developers/architecture_components.markdown
@@ -7,6 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
+og_image: /images/architecture/component_interaction.png
---
Home Assistant can be extended with **components**. Each component is responsible for a specific domain within Home Assistant. Components can listen for or trigger events, offer services, and maintain states. Components are written in Python and can do all the goodness that Python has to offer. Out of the box, Home Assistant offers a bunch of [built-in components]({{site_root}}/components/).
diff --git a/source/developers/hassio/addon_config.markdown b/source/developers/hassio/addon_config.markdown
index 426d3808ec2..c77fb780df1 100644
--- a/source/developers/hassio/addon_config.markdown
+++ b/source/developers/hassio/addon_config.markdown
@@ -102,7 +102,7 @@ The config for an add-on is stored in `config.json`.
| ports | no | Network ports to expose from the container. Format is `"container-port/type": host-port`.
| host_network | no | If that is True, the add-on run on host network.
| devices | no | Device list to map into add-on. Format is: `::`. i.e. `/dev/ttyAMA0:/dev/ttyAMA0:rwm`
-| privileged | no | Privilege for access to hardware/system. Available access: `NET_ADMIN`
+| privileged | no | Privilege for access to hardware/system. Available access: `NET_ADMIN`, `SYS_ADMIN`
| map | no | List of maps for additional hass.io folders. Possible values: `config`, `ssl`, `addons`, `backup`, `share`. Default it map it `ro`, you can change that if you add a ":rw" at the end of name.
| environment | no | A dict of environment variable to run add-on.
| options | yes | Default options value of the add-on
diff --git a/source/developers/hassio/debugging.markdown b/source/developers/hassio/debugging.markdown
index 6b47eb12440..4f557178286 100644
--- a/source/developers/hassio/debugging.markdown
+++ b/source/developers/hassio/debugging.markdown
@@ -31,7 +31,7 @@ Follow steps 1-4 under 'Generating a new SSH key' (The other sections are not ap
Step 3 in the link above, shows the path to the private key file `id_rsa` for your chosen operating system. Your public key, `id_rsa.pub`, is saved in the same folder. Next, copy your public key file to the root of your SD card.
-Make sure when you are copying the public key to the root of the SD card that you rename the file correctly with no `.pub` file extension.
+Make sure when you are copying the public key to the root of the /boot partition of the SD card that you rename the file correctly with no `.pub` file extension.
## {% linkable_title Checking the logs %}
diff --git a/source/developers/index.markdown b/source/developers/index.markdown
index f1fb27273db..c801866e6aa 100644
--- a/source/developers/index.markdown
+++ b/source/developers/index.markdown
@@ -7,6 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
+og_image: /images/architecture/component_interaction.png
---
Welcome to the Home Assistant development documentation. This is the place to learn all about how Home Assistant works and how you can extend it with support for your devices and services!
diff --git a/source/docs/index.markdown b/source/docs/index.markdown
index 4c743e1b121..65a6e87c6b9 100644
--- a/source/docs/index.markdown
+++ b/source/docs/index.markdown
@@ -12,11 +12,11 @@ footer: true
The documentation covers from beginner to advanced topic around the installation, the setup, the configuration, and the usage of Home Assistant.
+Hass.io dashboard
+
+ 
-Add the urls of repositories (one per line) and then press "Save". A new card for the repository will appear.
+Add the URLs of repositories (one per line) and then press "Save". A new card for the repository will appear.