Merge branch 'current' into next

_config.yml

@@ -138,10 +138,10 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 41
+current_minor_version: 42
 current_patch_version: 0
-date_released: 2017-03-25
+date_released: 2017-04-08
 
 # 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: "#release-0411---march-xx"
+patch_version_notes: "#"

source/_components/automation.markdown

@@ -11,7 +11,7 @@ logo: home-assistant.png
 ha_category: Automation
 ---
 
-Please see the [getting started section](/getting-started/automation/) for in-depth documentation on how to use the automation component.
+Please see the [docs section](/docs/automation/) for in-depth documentation on how to use the automation component.
 
 Starting with 0.28 your automation rules can be controlled with the frontend.
 

source/_components/binary_sensor.aurora.markdown

@@ -9,7 +9,9 @@ sharing: true
 footer: true
 ha_category: Binary Sensor
 ha_release: 0.39
+logo: noaa.png
 ---
+
 The `aurora` platform uses the [NOAA aurora forecast](http://www.swpc.noaa.gov/products/aurora-30-minute-forecast) service to let you know if an aurora might be visible at your home location in the next 30 minutes, based off of current solar flare activity.
 
 This service gives a number 0-100 representing the current likelihood of visible auroras at your latitude/longitude. By default this sensor is set up to trigger when the reported likelihood for your location is > 75. It updates every 5 minutes.
@@ -24,9 +26,10 @@ binary_sensor:
   - platform: aurora
 ```
 
-#### Configuration variables:
+Configuration variables:
 
 - **forecast_threshold** (*Optional*): Provide your own threshold number above which the sensor will trigger. Defaults to 75.
+- **name** (*Optional*): The name of the sensor. Default is 'Aurora Visibility'. 
 
 ```yaml
   binary_sensor:

source/_components/device_tracker.bluetooth_le_tracker.markdown

@@ -13,16 +13,24 @@ ha_iot_class: "Local Poll"
 ha_release: 0.27
 ---
 
-This tracker discovers new devices on boot and in regular intervals and tracks bluetooth low-energy devices periodically based on interval_seconds value. It is not required to pair the devices with each other! 
+<p class='note warning'>
+We have received <a href='https://github.com/home-assistant/home-assistant/issues/4442'>numerous reports</a> that this integration will have a big impact on the performance of the server.
+</p>
+
+This tracker discovers new devices on boot and in regular intervals and tracks bluetooth low-energy devices periodically based on interval_seconds value. It is not required to pair the devices with each other.
 
 Devices discovered are stored with 'BLE_' as the prefix for device mac addresses in `known_devices.yaml`.
 
-This platform requires pybluez to be installed. On Debian based installs, run `sudo apt install bluetooth libbluetooth-dev pkg-config libboost-python-dev libboost-thread-dev libglib2.0-dev python-dev`
+This platform requires pybluez to be installed. On Debian based installs, run
+
+```bash
+$ sudo apt install bluetooth libbluetooth-dev pkg-config libboost-python-dev libboost-thread-dev libglib2.0-dev python-dev
+```
 
 Before you get started with this platform, please note that:
+
  - This platform is incompatible with Windows
  - This platform requires root privileges
- - Don't use on a Raspberry Pi. It will become unusable slow when using this platform.
 
 To use the Bluetooth tracker in your installation, add the following to your `configuration.yaml` file:
 

source/_components/emulated_hue.markdown

@@ -25,21 +25,21 @@ The virtual bridge has the ability to turn entities on or off, or change the bri
 To enable the emulated Hue bridge, add one of the following configs to your `configuration.yaml` file:
 
 ```yaml
-# Amazon Echo example configuration.yaml entry
+# Google Home example configuration.yaml entry
 emulated_hue:
+  # Google Home does not work on different ports.
 ```
 
 ```yaml
-# Google Home example configuration.yaml entry
+# Amazon Echo example configuration.yaml entry
 emulated_hue:
-  type: google_home
-  # Google Home does not work on different ports.
+  type: alexa
   listen_port: 80
 ```
 
 Configuration variables:
 
-- **type** (*Optional*): The type of assistant who we are emulated for. Either `alexa` or `google_home`, defaults to `alexa`.
+- **type** (*Optional*): The type of assistant who we are emulated for. Either `alexa` or `google_home`, defaults to `google_home`.
 - **host_ip** (*Optional*): The IP address that your Home Assistant installation is running on. If you do not specify this option, the component will attempt to determine the IP address on its own.
 - **listen_port** (*Optional*): The port the Hue bridge API web server will run on. If not specified, this defaults to 8300. This can be any free port on your system.
 

source/_components/light.mqtt.markdown

@@ -11,9 +11,9 @@ logo: mqtt.png
 ha_category: Light
 ---
 
-The `mqtt` light platform lets you control your MQTT enabled light. It supports setting brightness, color temperature, effects, flashing, on/off, RGB colors, transitions, XY colors and white values.
+The `mqtt` light platform lets you control your MQTT enabled lights. It supports setting brightness, color temperature, effects, flashing, on/off, RGB colors, transitions, XY colors and white values.
 
-In an ideal scenario, the MQTT device will have a state topic to publish state changes. If these messages are published with RETAIN flag, the MQTT switch will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state of the switch will be false/off.
+In an ideal scenario, the MQTT device will have a state topic to publish state changes. If these messages are published with RETAIN flag, the MQTT light will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state of the switch will be false/off.
 
 When a state topic is not available, the light will work in optimistic mode. In this mode, the light will immediately change state after every command. Otherwise, the light will wait for state confirmation from device (message from `state_topic`).
 
@@ -45,6 +45,7 @@ Configuration variables:
 - **payload_off** (*Optional*): The payload that represents disabled state. Default is "OFF".
 - **payload_on** (*Optional*): The payload that represents enabled state. Default is "ON".
 - **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
+- **retain** (*Optional*): If the published message should have the retain flag on or not.
 - **rgb_command_topic** (*Optional*): The MQTT topic to publish commands to change the light's RGB state.
 - **rgb_state_topic** (*Optional*): The MQTT topic subscribed to receive RGB state updates.
 - **rgb_value_template** (*Optional*): Defines a [template](/topics/templating/) to extract the RGB value.
@@ -127,4 +128,5 @@ light:
 
 ### {% linkable_title Implementations %}
 
-A basic example using a nodeMCU board (ESP8266) to control its built-in led (on/off) can be found [here](https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_light). [Here](https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_rgb_light) is another example to control a RGB led (on/off, brightness and colors).
+- A [basic example](https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_light) using a nodeMCU board (ESP8266) to control its built-in LED (on/off).
+- Another [example](https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_rgb_light) to control a RGB LED (on/off, brightness, and colors).

source/_components/light.mqtt_json.markdown

@@ -121,6 +121,8 @@ light:
 
 ### {% linkable_title Implementations %}
 
-A full example of custom lighting using this platform and an ESP8266 microcontroller can be found [here](https://github.com/corbanmailloux/esp-mqtt-rgb-led). It supports on/off, brightness, transitions, RGB colors, and flashing.
+- A full example of custom lighting using this platform and an ESP8266 microcontroller can be found [here](https://github.com/corbanmailloux/esp-mqtt-rgb-led). It supports on/off, brightness, transitions, RGB colors, and flashing.
 
-There is also another implementation forked from the above repo, it supports all the same features but is made for addressable LED strips using FastLED on a NodeMCU V3 it can be found [here](https://github.com/JammyDodger231/nodemcu-mqtt-rgb-led)
+- There is also another implementation forked from the above repo, it supports all the same features but is made for addressable LED strips using FastLED on a NodeMCU V3 it can be found [here](https://github.com/JammyDodger231/nodemcu-mqtt-rgb-led).
+
+- [MQTT JSON Light](https://github.com/mertenats/Open-Home-Automation/tree/master/ha_mqtt_rgbw_light_with_discovery) is another implementation for ESP8266 including [MQTT discovery](/docs/mqtt/discovery/).

source/_components/light.rflink.markdown

@@ -47,10 +47,10 @@ Configuration variables:
 Device configuration variables:
 
 - **name** (*Optional*): Name for the device, defaults to Rflink ID.
-- **type** (*Optional*): Override automatically detected type of the light device, can be: switchable, dimmable, hybrid or toggle. See 'Light Types' below.
+- **type** (*Optional*): Override automatically detected type of the light device, can be: switchable, dimmable, hybrid or toggle. See 'Light Types' below. (default: Switchable)
 - **aliasses** (*Optional*): Alternative Rflink ID's this device is known by.
 - **fire_event** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False).
-- **signal_repetitions** (*Optional*): Repeat every Rflink command this number of times (default: 1)
+- **signal_repetitions** (*Optional*): Repeat every Rflink command this number of times (default: 1).
 - **fire_event_** (*Optional*): Set default `fire_event` for RFLink switch devices (see below).
 - **signal_repetitions** (*Optional*): Set default `signal_repetitions` for RFLink switch devices (see below).
 
@@ -71,6 +71,10 @@ light:
       aliasses:
         - newkaku_000000001_2
         - kaku_000001_a
+    Ansluta_ce30_0:
+      name: Kitchen Under Counter Lights
+    Maclean_0d82_01:
+      name: Bedroom Lamp
 ```
 
 Any on/off command from any allias ID updates the current state of the light. However when sending a command through the frontend only the primary ID is used.

source/_components/logger.markdown

@@ -67,3 +67,9 @@ data:
   homeassistant.components: warning
   homeassistant.components.media_player.yamaha: debug
 ```
+
+The log information are stored in the [configuration directory](/docs/configuration/) as `home-assistant.log` and you can read it with the command-line tool `cat` or follow it dynamicly with `tail -f`. If you are a Rasbian user then like the example below:
+
+```bash
+$ tail -f /home/pi/.homeassistant/home-assistant.log
+```

source/_components/lutron_caseta.markdown

@@ -0,0 +1,39 @@
+---
+layout: page
+title: "Lutron Caseta"
+description: "Instructions how to use Lutron Caseta devices with Home Assistant."
+date: 2017-01-28 13:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: lutron.png
+ha_category: Hub
+featured: False
+ha_release: 0.41
+---
+
+[Lutron](http://www.lutron.com/) is an American lighting control company.  They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc.  The `lutron_caseta` component in Home Assistant is responsible for communicating with the Lutron SmartBridge for these systems.
+
+This component only supports the Caseta line of products.  Current only supports Caseta dimmers as Home Assistant lights and caseta wall switches as Home Assistant switches.   
+
+When configured, the `lutron_caseta` component will automatically discover dimmers and switches as setup in the Lutron SmartBridge.
+
+To use Lutron Caseta devices in your installation, add the following to your configuration.yaml file using the IP of your lutron Smartbridge:
+
+``` yaml
+lutron_caseta:
+    host: <ip_address>
+    username: lutron
+    password: integration
+```
+
+Configuration variables:
+
+- **host** (*Required*): The IP address of the Lutron SmartBridge.
+- **username** (*Required*): The login name of the user.  The user `lutron` always exists.
+- **password** (*Required*): The password for the user specified above. `integration` is the password for the always-present `lutron` user.
+
+<p class='note'>
+  It is recommended to assign a static IP address to your Lutron SmartBridge.  This ensures that it won't change IP address, so you won't have to change the `host` if it reboots and comes up with a different IP address.
+</p>

source/_components/media_player.nad.markdown

@@ -23,12 +23,6 @@ To add an NAD receiver to your installation, add the following to your `configur
 media_player:
   - platform: nad
     serial_port: /dev/ttyUSB0
-    name: NAD Receiver
-    min_volume: -60
-    max_volume: -20
-    sources:
-      1: 'Kodi'
-      2: 'TV'
 ```
 
 Configuration variables:
@@ -39,8 +33,7 @@ Configuration variables:
 - **max_volume** (*optional*): Maximum volume in dB to use with the slider. Default is `-20`
 - **sources** (*Optional*): A list of mappings from source to source name. Valid sources are `1 to 10`.
 
-The min_volume and max_volume are there to protect you against misclicks on the slider so you will not blow up your speakers when you go from -92dB to +20dB.
-You can still force it to go higher or lower than the values set with the plus and minus buttons.
+The min_volume and max_volume are there to protect you against misclicks on the slider so you will not blow up your speakers when you go from -92dB to +20dB. You can still force it to go higher or lower than the values set with the plus and minus buttons.
 
 <p class='note warning'>
 On linux the user running home-assistant needs `dialout` permissions to access the serial port.
@@ -48,3 +41,17 @@ This can be added to the user by doing `sudo usermod -a -G dialout <username>`.
 Be aware that the user might need to logout and logon again to activate these permissions.
 </p>
 
+A full configuration example could look like this:
+
+```yaml
+# Example configuration.yaml entry
+media_player:
+  - platform: nad
+    serial_port: /dev/ttyUSB0
+    name: NAD Receiver
+    min_volume: -60
+    max_volume: -20
+    sources:
+      1: 'Kodi'
+      2: 'TV'
+```

source/_components/rflink.markdown

@@ -12,7 +12,7 @@ ha_category: Hub
 ha_release: 0.38
 ---
 
-The `rflink` component support devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
+The `rflink` component support devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino Mega firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
 
 The 433 Mhz spectrum is used by many manufacturers mostly using their own protocol/standard and includes devices like: light switches, blinds, weather stations, alarms and various other sensors.
 

source/_components/scene.wink.markdown

@@ -0,0 +1,19 @@
+---
+layout: page
+title: "Wink Scene"
+description: "Instructions how to setup the Wink scenes(shortcuts) within Home Assistant."
+date: 2017-04-01 16:45
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: wink.png
+ha_category: Scene
+ha_release: 0.41
+ha_iot_class: "Cloud Polling"
+---
+
+
+The Wink scene platform allows you to control your [Wink](http://www.wink.com/) shortcuts.
+
+The requirement is that you have setup [Wink](/components/wink/).

source/_components/sensor.crimereports.markdown

@@ -0,0 +1,101 @@
+---
+layout: page
+title: "Crime Reports"
+description: "Instructions on how to integrate CrimeReports.com into Home Assistant."
+date: 2017-02-16 11:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category: Sensor
+featured: false
+ha_release: 0.42
+ha_iot_class: "Cloud Polling"
+---
+
+The `crimereports` sensor allows one to track reported incidents occurring in a Home Assistant zone. Incidents include anything reported to [Crime Reports](http://crimereports.com). Your regional emergency services may or may not report data. The sensor only counts incidents from the current day.
+
+## Configuration
+
+To enable this sensor, add the following lines to your `configuration.yaml`. Your `zone` should be of sufficient size to capture incidents in your area. Your `home` zone is probably too small.
+
+```yaml
+zone:
+  - name: neighborhood
+    latitude: <your latitude>
+    longitude: <your longitude>
+    radius: <your neighborhood radius>
+
+sensor:
+  - platform: crimereports
+    zone: neighborhood
+```
+
+Configuration options for the Crime Reports Sensor:
+
+- **zone** (*Required*): The zone to monitor.
+- **include** (*Optional*): List of incident types to include.
+- **exclude** (*Optional*): List of incident types to exclude.
+- **update_inverval** (*Optional*): Minimum time interval between updates. Default is 30 minutes. Supported formats:
+  - `update_interval: 'HH:MM:SS'`
+  - `update_interval: 'HH:MM'`
+  - Time period dictionary, e.g.:
+    <pre>update_interval:
+        # At least one of these must be specified:
+        days: 0
+        hours: 0
+        minutes: 3
+        seconds: 30
+        milliseconds: 0
+    </pre>
+
+## Notes
+
+### Area
+
+Crime Reports captures all incidents in a region defined by a square shape. Home Assistant zones are circular. Therefore, the region defined by a Home Assistant zone in a Crime Reports context is a square that is big enough to fit the zone circle. Practically, this means some incidents may be captured that are outside your zone.
+
+### Incident Types
+
+You can explicitly include or exclude incident types. Specifying `include`s restricts the incidents to those types. Specifying `exclude`s will return all incident types except those specified.
+
+These incident types are available:
+
+- Alarm
+- Arson
+- Assault
+- Assault with Deadly Weapon
+- Breaking & Entering
+- Community Policing
+- Death
+- Disorder
+- Drugs
+- Emergency
+- Family Offense
+- Fire
+- Homicide
+- Kidnapping
+- Liquor
+- Missing Person
+- Other
+- Other Sexual Offense
+- Pedestrian Stop
+- Proactive Policing
+- Property Crime
+- Property Crime Commercial
+- Property Crime Residential
+- Quality of Life
+- Robbery
+- Sexual Assault
+- Sexual Offense
+- Theft
+- Theft from Vehicle
+- Theft of Vehicle
+- Traffic
+- Vehicle Recovery
+- Vehicle Stop
+- Weapons Offense
+
+### Events
+
+The `crimealerts` sensor fires a `crimealerts_incident` event when a new incident is detected, including the type, description, time, location, and coordinates of the incident.

source/_components/sensor.lyft.markdown

@@ -10,7 +10,7 @@ footer: true
 logo: lyft.png
 ha_category: Transport
 ha_iot_class: "Cloud Polling"
-ha_release: 0.42
+ha_release: 0.41
 ---
 
 

source/_components/sensor.min_max.markdown

@@ -39,7 +39,7 @@ sensor:
 
 Configuration variables:
 
-- **entity_ids** (*Required*): At least two entities to monitor
+- **entity_ids** (*Required*): At least two entities to monitor. The unit of measurement of the first entry will be the one that's used. All entities must use the same unit of measurement.
 - **type** (*Optional*): The type of sensor: `min`, `max` or `mean`. Defaults to `max`.
 - **name** (*Optional*): Name of the sensor to use in the frontend.
 - **round_digits** (*Optional*): Round mean value to specified number of digits. Defaults to 2.

source/_components/sensor.vera.markdown

@@ -17,3 +17,8 @@ The `vera` platform allows you to get data from your [Vera](http://getvera.com/)
   
 They will be automatically discovered if the vera component is loaded.
 
+Please note that some vera sensors (such as _motion_ and _flood_  sensors) are _armable_ which means that vera will send alerts (email messages ot txts) when they are _armed_ an change state.
+
+Home Assistant will display the state of these sensors regardless of the _armed_ state.
+
+To allow you to change the _armed state_ - Home Assistant will create a switch as well as a sensor for each _Armable_ sensor. You can hide these switches using customization if you wish.

source/_components/sensor.yweather.markdown

@@ -13,7 +13,7 @@ ha_release: 0.24
 ---
 
 
-The `yweather` platform uses [Yahoo Weather](https://www.yahoo.com/news/weather/) as an source for current meteorological data. The `forecast` will show you the condition for 5 days, 0 is the current day. You can use only `weather`, `temp_min`, and `temp_max` with forecast.
+The `yweather` platform uses [Yahoo Weather](https://www.yahoo.com/news/weather/) as an source for current meteorological data. The `forecast` will show you the condition for 5 days, 0 is the current day. You can use only `weather`, `temp_min`, and `temp_max` with forecast. It's important to note that a yweather sensor will only show ONE days forecast at a time so to show multiple days forecasts, you will need to use the 'name:' option and give each sensor a unique name.
 
 <p class='note warning'>
 Use of the Yahoo Weather API should not exceed reasonable request volume. Access is limited to 2,000 signed calls per day.
@@ -55,6 +55,37 @@ Configuration variables:
   - **pressure**: The sea-level air pressure in millibars.
   - **visibility**: The average visibility.
 
+Example of forecast using multiple days. In example, first sensor shows tomorrow's forecast, second sensor shows the next day and so on:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: yweather
+    forecast: 1
+    name: yw_day1
+    monitored_conditions:
+      - weather
+      - temp_min
+      - temp_max
+
+  - platform: yweather
+    forecast: 2
+    name: yw_day2
+    monitored_conditions:
+      - weather
+      - temp_min
+      - temp_max
+      
+  - platform: yweather
+    forecast: 3
+    name: yw_day3
+    monitored_conditions:
+      - weather
+      - temp_min
+      - temp_max
+
+```
+
 
 Details about the API are available in the [Yahoo! Developer Network](https://developer.yahoo.com/weather/).
 

source/_components/switch.rflink.markdown

@@ -43,14 +43,14 @@ Configuration variables:
 
 - **devices** (*Optional*): A list of devices with their name to use in the frontend.
 - **device_defaults**: (*Optional*)
-  - **fire_event_** (*Optional*): Set default `fire_event` for RFLink switch devices (see below).
+  - **fire_event** (*Optional*): Set default `fire_event` for RFLink switch devices (see below).
   - **signal_repetitions** (*Optional*): Set default `signal_repetitions` for RFLink switch devices (see below).
 
 Device configuration variables:
 
 - **name** (*Optional*): Name for the device, defaults to RFLink ID.
 - **aliasses** (*Optional*): Alternative RFLink ID's this device is known by.
-- **fire_event_** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False).
+- **fire_event** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False).
 - **signal_repetitions** (*Optional*): Repeat every RFLink command this number of times (default: 1)
 
 ### {% linkable_title Switch state %}

source/_docs/automation/trigger.markdown

@@ -15,6 +15,8 @@ Triggers are what starts the processing of an automation rule. It is possible to
 ### {% linkable_title Event trigger %}
 Triggers when an event is being processed. Events are the raw building blocks of Home Assistant. You can match events on just the event name or also require specific event data to be present.
 
+Events can be fired by components or via the API. There is no limitation to the types. A list of built-in events can be found [here](/docs/configuration/events/).
+
 ```yaml
 automation:
   trigger:
@@ -24,7 +26,22 @@ automation:
     event_data:
       mood: happy
 ```
-For example, to carry out actions when Home Assistant starts, you can use `event_type: homeassistant_start`. See other 'events' supported by Home Assistant [here](https://home-assistant.io/topics/events/).
+
+<p class='note warning'>
+  Starting 0.42, it is no longer possible to listen for event `homeassistant_start`. Use the 'homeassistant' platform below instead.
+</p>
+
+### {% linkable_title Home Assistant trigger %}
+
+Use this platform to trigger when Home Assistant starts up and shuts down.
+
+```yaml
+automation:
+  trigger:
+    platform: homeassistant
+    # Event can also be 'shutdown'
+    event: start
+```
 
 ### {% linkable_title MQTT trigger %}
 Triggers when a specific message is received on given topic. Optionally can match on the payload being sent over the topic.
@@ -62,7 +79,7 @@ automation:
   trigger:
     platform: state
     entity_id: device_tracker.paulus, device_tracker.anne_therese
-    # Optional 
+    # Optional
     from: 'not_home'
     to: 'home'
 
@@ -105,6 +122,8 @@ automation:
     value_template: "{% raw %}{% if is_state('device_tracker.paulus', 'home') %}true{% endif %}{% endraw %}"
 ```
 
+[template]: /docs/configuration/templating/
+
 ### {% 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. 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.

source/_docs/autostart/systemd.markdown

@@ -18,12 +18,12 @@ $ ps -p 1 -o comm=
 
 If the preceding command returns the string `systemd`, you are likely using `systemd`.
 
-If you want Home Assistant to be launched automatically, an extra step is needed to setup `systemd`. A service file is needed to control Home Assistant with `systemd`. The template below should be created using a text editor.  Note, root permissions via 'sudo' will likely be needed. The following should be noted to modify the template:
+If you want Home Assistant to be launched automatically, an extra step is needed to setup `systemd`. A service file is needed to control Home Assistant with `systemd`. The template below should be created using a text editor. Note, root permissions via `sudo` will likely be needed. The following should be noted to modify the template:
 
-+ `ExecStart` contains the path to `hass` and this may vary. Check with `whereis hass` for the location.
-+ If running Home Assistant in a python virtual environment or a docker, please skip to section below.
-+ For most systems, the file is `/etc/systemd/system/home-assistant@[your user].service` with [your user] replaced by the user account that Home Assistant will run as - normally `homeassistant`.  For Ubuntu 16.04, the file is `/lib/systemd/system/home-assistant.service` and requires running this command `sudo ln -s /lib/systemd/system/home-assistant.service /etc/systemd/system/home-assistant.service` after file is created.  
-+ If unfamiliar with command line text editors, `sudo nano -w [filename]` can be used with `[filename]` replaced with the full path to the file.  Ex. `sudo nano -w /etc/systemd/system/home-assistant@homeassistant.service`.  After text entered, press CTRL-X then press Y to save and exit.
+- `ExecStart` contains the path to `hass` and this may vary. Check with `whereis hass` for the location.
+- If running Home Assistant in a Python virtual environment or a Docker container, please skip to section below.
+- For most systems, the file is `/etc/systemd/system/home-assistant@[your user].service` with [your user] replaced by the user account that Home Assistant will run as - normally `homeassistant`.  For Ubuntu 16.04, the file is `/lib/systemd/system/home-assistant.service` and requires running this command `sudo ln -s /lib/systemd/system/home-assistant.service /etc/systemd/system/home-assistant.service` after file is created.
+- If unfamiliar with command-line text editors, `sudo nano -w [filename]` can be used with `[filename]` replaced with the full path to the file.  Ex. `sudo nano -w /etc/systemd/system/home-assistant@homeassistant.service`.  After text entered, press CTRL-X then press Y to save and exit.
 
 ```
 [Unit]
@@ -39,7 +39,9 @@ ExecStart=/usr/bin/hass
 WantedBy=multi-user.target
 ```
 
-If you've setup Home Assistant in `virtualenv` following our [python installation guide](https://home-assistant.io/getting-started/installation-virtualenv/) or [manual installation guide for raspberry pi](https://home-assistant.io/getting-started/installation-raspberry-pi/), the following template should work for you.  If Home Assistant install is not located at `/srv/homeassistant`, please modify the `ExecStart=` line appropriately.  
+### {% linkable_title Python virtual environment %}
+
+If you've setup Home Assistant in `virtualenv` following our [Python installation guide](https://home-assistant.io/getting-started/installation-virtualenv/) or [manual installation guide for Raspberry Pi](https://home-assistant.io/getting-started/installation-raspberry-pi/), the following template should work for you. If Home Assistant install is not located at `/srv/homeassistant`, please modify the `ExecStart=` line appropriately.
 
 ```
 [Unit]
@@ -55,7 +57,9 @@ ExecStart=/srv/homeassistant/bin/hass -c "/home/homeassistant/.homeassistant"
 WantedBy=multi-user.target
 ```
 
-If you want to use docker, the following template should work for you.
+### {% linkable_title Docker %}
+
+If you want to use Docker, the following template should work for you.
 
 ```
 [Unit]

source/_docs/configuration/templating.markdown

@@ -23,14 +23,14 @@ Templating is a powerful feature in Home Assistant that allows the user control
 
 - Formatting outgoing messages in, for example, the [notify] and [alexa] components.
 - Process incoming data from sources that provide raw data, like [MQTT], [REST sensor], or the [command line sensor].
-- [Advanced Automation templating]auto-template]
+- [Automation Templating].
 
 [notify]: /components/notify/
 [alexa]: /components/alexa/
 [MQTT]: /components/mqtt/
 [REST sensor]: /components/sensor.rest/
 [command line sensor]: /components/sensor.command_line/
-[auto-template]: /getting-started/automation-templating/
+[Automation Templating]: /docs/automation/templating/
 
 ## {% linkable_title Building templates %}
 
@@ -74,7 +74,7 @@ Home Assistant adds extensions to allow templates to access all of the current s
 - `is_state_attr('device_tracker.paulus', 'battery', 40)` will test if the given entity is specified state.
 - `now()` will be rendered as current time in your time zone.
 - `utcnow()` will be rendered as UTC time.
-- `as_timestamp` will convert datetime object or string to UNIX timestamp
+- `as_timestamp()` will convert datetime object or string to UNIX timestamp
 - `distance()` will measure the distance in meters between home, entity, coordinates.
 - `closest()` will find the closest entity.
 - `relative_time(timestamp)` will format the date time as relative time vs now (ie 7 seconds)

source/_docs/ecosystem/apache.markdown

@@ -55,7 +55,7 @@ If you don't want HTTPS, you can change `<VirtualHost *:443>` to `<VirtualHost *
 
 <p class='note'>
 In case you are getting occasional HTTP 504 error messages ("Gateway Timeout") when accessing the Web UI through your proxy, try adding disablereuse=on to both ProxyPass directives:
-
+</p>
 ```text
 <VirtualHost *:443>
   [...]
@@ -65,7 +65,6 @@ In case you are getting occasional HTTP 504 error messages ("Gateway Timeout") w
   [...]
 </VirtualHost>
 ```
-</p>
 
 #### {% linkable_title Multiple Instance %}
 

source/_docs/hassbian/common-tasks.markdown

@@ -93,7 +93,7 @@ This will in order do the following:
 - Change directory to the Home Assistant configuration directory.
 - Open the log file in the nano editor.
 
-Optionaly, you can also view the log with `journalctl`.
+Optionally, you can also view the log with `journalctl`.
 Log in as the `pi` account and execute the following commands:
 
 ```bash

source/_docs/hassbian/customization.markdown

@@ -14,7 +14,7 @@ To allow you to customize your installation further, we have included a set of H
 
   - Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and it's usage is not recommended if you share your network with others.
   - Install Libcec. Adds local [HDMI CEC support][cec].
-  - Install Mossquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects offical repository. Now includes websocket support.
+  - Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects offical repository. Now includes websocket support.
   - Install Open Z-Wave. Installs Open Z-Wave and prepares for using a USB or GPIO ZWave controller.
 
 All of these scripts are available in the directory `/home/pi/hassbian-scripts/`. For more information about these scripts have a look at the [hassbian-scripts repository][hassbian-repo].

source/_docs/installation/archlinux.markdown

@@ -24,7 +24,7 @@ and Home Assistant itself.
 $ pip3 install homeassistant
 ```
 
-Home Assistant is part of the [AUR](https://aur.archlinux.org/packages/home-assistant/). This meand that it can be installed directly with `pacman`:
+Home Assistant is part of the [AUR](https://aur.archlinux.org/packages/home-assistant/). This means that it can be installed directly with `pacman`:
 
 ```bash
 $ sudo pacman -S home-assistant

source/_docs/installation/fedora.markdown

@@ -23,3 +23,24 @@ and Home Assistant itself.
 $ pip3 install homeassistant
 ```
 
+To isolate the Home Assistant installation a [venv](https://docs.python.org/3/library/venv.html) is handy. First create a new directory to store the installation.
+
+```bash
+$ sudo mkdir -p /opt/homeassistant
+$ cd /opt/homeassistant
+```
+Now switch to the new directory, setup the venv, and activate it.
+
+```bash
+$ cd /opt/homeassistant
+$ pyvenv-3.5 .
+$ source bin/activate
+```
+
+Install Home Assistant itself.
+
+```bash
+$ pip3 install homeassistant
+```
+
+Check the [autostart](/docs/autostart/systemd/) section in the documentation for further details. 

source/_includes/asides/docs_navigation.html

@@ -6,7 +6,7 @@
         {% active_link /docs/installation/ Installation %}
         <ul>
           <li>{% active_link /docs/installation/virtualenv/ Python Virtual Env %}</li>
-          <li>{% active_link /docs/installation/raspberry-pi-all-in-one/ Raspberrry Pi All-in-One %}</li>
+          <li>{% active_link /docs/installation/raspberry-pi-all-in-one/ Raspberry Pi All-in-One %}</li>
           <li>{% active_link /docs/installation/updating/ Updating %}</li>
           <li>{% active_link /docs/installation/troubleshooting/ Troubleshooting %}</li>
         </ul>
@@ -41,9 +41,14 @@
           <li>{% active_link /docs/configuration/secrets/ Storing Secrets %}</li>
           <li>{% active_link /docs/configuration/templating/ Templating %}</li>
           <li>{% active_link /docs/configuration/group_visibility/ Group Visibility %}</li>
+          <li>{% active_link /docs/configuration/platform_options/ Entity component platform options %}</li>
+        </ul>
+      </li>
+      <li>
+        Core objects
+        <ul>
           <li>{% active_link /docs/configuration/events/ Events %}</li>
           <li>{% active_link /docs/configuration/state_object/ State Objects %}</li>
-          <li>{% active_link /docs/configuration/platform_options/ Entity component platform options %}</li>
         </ul>
       </li>
       <li>

source/_posts/2017-04-01-thomas-krenn-award.markdown

@@ -0,0 +1,40 @@
+---
+layout: post
+title: "Thomas Krenn award 2017"
+description: "Thomas Krenn award 2017"
+date: 2017-04-01 06:00:00 +0000
+date_formatted: "April 01, 2017"
+author: Fabian Affolter
+comments: true
+categories: Community
+og_image: /images/blog/2017-04-award/social.png
+---
+
+You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the [Thomas-Krenn-Award][award] put us on the 2nd place. This is an awesome achievment for an independent community project.
+
+I would like to thanks all contributors. Your endless effort made this possible.
+
+<img src='/images/blog/2017-04-award/award.jpg' style='border: 0;box-shadow: none;'>
+
+The prize beside the very nice trophy contains hardware and we want to give that hardware partically away. We won four [Low Energy Server v2 (LES)][LES] units with an Intel Celeron N2930, 8 GB of RAM, and a mSATA of 128 GB (one unit with 64 GB). We were thinking about to keep one of those units in Europe and one in North America for testing and to use during workshops and events. But the other two will go to interested parties.
+
+As a raffle would be to easy, we make a contest out of it. This means that we are looking for your application. Of course, we would like to see those systems goes to active or future developers who can justify their need for one of the systems to run CI, UI tests, public accessible Home Assistant demo instances, etc. At the other hand we would like to keep it open, to see with what people are coming up. Please participate as well if you are planning to automate the public school of your kids with 1000 switches or light, need a server to run it, and want to provide regular feedback about the user experience.
+
+Create an entry in our [Forum][forum]. Be creative and use your imagination.
+
+
+### {% linkable_title The details %}
+
+- Jury: The Home Assistant community
+- Dead line: April, 23 2017 - 23.59 UTC
+- Voting period: April, 24th till April, 30 2017 - 23.59 UTC
+
+The decision of the jury will be final. If there will be a dispute then the Top-5 commiter of the Home Assistant organisation on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the [Forum][forum] and on [Twitter][twitter].
+
+Keep in mind that you may have to pay the fee for customs handling and the import duty by yourself. The plan is to ship the hardware from Germany. If you are located in a country with import/export regulations, we may not be able to ship the hardware to you.
+
+[LES]: https://www.thomas-krenn.com/en/products/low-energy-systems/les-v2.html
+[award]: https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/
+[forum]: https://community.home-assistant.io/c/contest-2017
+[twitter]: https://twitter.com/home_assistant
+

source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown

@@ -0,0 +1,361 @@
+---
+layout: post
+title: "Home Assistant 0.42: Eddystone Beacons, Lockitron locks and Total Connect alarm systems"
+description: "Tons of bug fixes, performance increasements and some cool new integrations."
+date: 2017-04-08 08:04:05 +0000
+date_formatted: "April 8, 2017"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2017-04-0.42/social.png
+---
+
+<a href='/components/#added_in_current_version'><img src='/images/blog/2017-04-0.42/social.png' style='border: 0;box-shadow: none;'></a>
+
+It's time for Home Assistant 0.43. This release has been focused on refining the system and fixing a lot of bugs. We have also upgraded to the latest version of our HTTP library which should give us a significant boost serving files and API.
+
+On our social media front, we have crossed the 1000 likes on [our Facebook page][hass-fb]! Also on the social media front, the YouTube channel diyAutomate has been putting out a lot of great getting started videos about Home Assistant, [go check them out!][diyAutomate]
+
+Also want to take a moment to thank Austin Andrews aka [Templarian] for his [Material Design Icons][mli]. He is part of what makes Home Assistant so beautiful 🤗.
+
+[hass-fb]: https://www.facebook.com/homeassistantio
+[diyAutomate]: https://www.youtube.com/c/diyautomate
+[mli]: https://materialdesignicons.com/
+[Templarian]: https://github.com/templarian
+
+## New integrations
+
+- Lockitron locks ([@aarya123] - [#6805])
+- Met Office weather and sensor components ([@jacobtomlinson] - [#6742])
+- Total Connect alarm systems ([@wardcraigj] - [#6887])
+- Eddystone Beacon Temperature Sensor ([@citruz] - [#6789])
+- CrimeReports.com integration shows crimes around a location in the US ([@happyleavesaoc] - [#6966])
+- The Ring doorbell has been integrated further with the inclusion of binary sensors ([@tchellomello] - [#6520])
+
+<!--more-->
+## Breaking changes
+
+- We were incorrectly treating groups named `default_view` as default views. Make sure you set `view: true` in the config for these groups. [#251 (frontend)](https://github.com/home-assistant/home-assistant-polymer/pull/251)
+- The last release introduced a revamped LIFX platform. We only realised after deploy that this version does not work on Windows. We have added the old LIFX implementation back as `lifx_legacy`.
+- We added indexes to the database to speed up the history view. Initial boot can take a couple of minutes. Do not shut down while migration is occurring. [#6688]
+- Z-Wave cover workaround has been removed. Use device config instead. [#6832]
+
+```yaml
+zwave:
+  device_config:
+    cover.my_cover:
+      invert_openclose_buttons: true
+```
+
+- If you set an initial state for an automation, input_boolean, input_slider or input_select it will overrule over the previous state. [#6911] [#6924]
+- Z-Wave rename node service parameter `entity_id` has been replaced with `node_id` to align parameters [#6938]
+- Automations are now initialized when Home Assistant finishes starting up. This means that it is deprecated to listen for event `homeassistant_start`. Instead, use the new `homeassistant` automation platform. [#6936]
+
+```yaml
+automation:
+  trigger:
+    platform: homeassistant
+    event: start
+  action:
+    service: light.turn_on
+```
+
+- The Ring component has moved the authentication to a dedicated ring component. [#6520]
+
+```yaml
+ring:
+    username: !secret ring_username
+    password: !secret ring_password
+
+binary_sensor:
+  - platform: ring
+    monitored_conditions:
+      - ding
+      - motion
+
+sensor:
+  - platform: ring
+    monitored_conditions:
+      - battery
+      - last_activity
+      - last_ding
+      - last_motion
+      - volume
+```
+
+## All changes
+
+- Flux led update lib ([@danielhiversen] - [#6763])
+- Adding expire_after to mqtt sensor to expire outdated values ([@micw] - [#6708])
+- New indexes for states and recording_runs tables ([@m00dawg] - [#6688]) (breaking change)
+- Fix flaky template test ([@armills] - [#6768])
+- Repair zwave sensor coverage ([@armills] - [#6764])
+- Version bump to 0.42.0.dev0 ([@balloob])
+- current temp could be none ([@turbokongen] - [#6759])
+- Typing error and update test ([@turbokongen] - [#6757])
+- Wink Aros Fixes ([@geekofweek] - [#6726])
+- Upgrade pydroid-ipcam to 0.7 ([@fabaff] - [#6772])
+- Upgrade psutil to 5.2.1 ([@fabaff] - [#6771])
+- Upgrade sleekxmpp to 1.3.2 ([@fabaff] - [#6773])
+- Tests for zwave workaround detection ([@armills] - [#6761])
+- Bugfix automation fire on bootstrap ([@pvizeli] - [#6770])
+- Homematic Fixes ([@danielperna84] - [#6769])
+- Fix wink siren ([@w1ll1am23] - [#6775])
+- Fix bridge-led support in limitlessled.py ([@quadportnick] - [#6776])
+- Wrong info in discovery schema ([@turbokongen] - [#6779])
+- switch.tplink: upgrade to the newest upstream release which adds support for plugs using the newer communication protocol ([@rytilahti] - [#6790])
+- Add switch to MQTT discovery ([@fabaff] - [#6733])
+- Update docstrings ([@fabaff] - [#6795])
+- Add optional unit of measurement ([@fabaff] - [#6796])
+- Upgrade zeroconf to 0.19.0 ([@fabaff] - [#6792])
+- Upgrade pysnmp to 4.3.5 ([@fabaff] - [#6793])
+- Platform for Munich public transport departure times ([@DavidMStraub] - [#6704])
+- Use string formatting and remove already global disabled pylint issue ([@fabaff] - [#6801])
+- Fix typo and update name ([@fabaff] - [#6809])
+- Upgrade matrix-client to 0.0.6 ([@fabaff] - [#6808])
+- Make get_snmp_data more robust ([@tantecky] - [#6798])
+- Add NVR support to Hikvision Binary Sensors ([@mezz64] - [#6807])
+- Update Insight parameters using the subscription data. ([@pavoni] - [#6782])
+- fix WOL in docker/jail ([@goto100] - [#6810])
+- Allow to monitor Windows hosts ([@fabaff] - [#6803])
+- lights/hue: use device class for on/off devices like the osram lightify plug ([@jannau] - [#6817])
+- [switch.wemo] Fix mW to kW conversion. ([@lwis] - [#6826])
+- yeelight: adjust supported features on update() ([@rytilahti] - [#6799])
+- Updated pubnubsub-handler version ([@w1ll1am23] - [#6829])
+- Remove zwave cover invert workaround. Use config instead. ([@andrey-git] - [#6832]) (breaking change)
+- history_stats: Fix schema, as `state` can be arbitrary string ([@leppa] - [#6753])
+- Rflink group commands ([@aequitas] - [#5969])
+- Updating Alarm.com Component for async and no Selenium ([@Xorso] - [#6752])
+- Add voluptuous config validation to scenes ([@MartinHjelmare] - [#6830])
+- Integration with lockitron ([@aarya123] - [#6805]) (new-platform)
+- [switch.wemo] Fix today_energy_kwh calculation. ([@lwis] - [#6846])
+- Locative tests to use aiohttp test utils ([@balloob] - [#6838])
+- Convert Alexa tests to use aiohttp test utils ([@balloob] - [#6839])
+- Handle initial event after entity is instantiated. ([@aequitas] - [#6760])
+- Lifx legacy ([@amelchio] - [#6847]) (new-platform)
+- aiohttp 2 ([@balloob] - [#6835])
+- Fix configuration setup ([@bdurrer] - [#6853])
+- Add option to disable automatic add for lights and sensors. ([@aequitas] - [#6852])
+- Update aioHTTP to 2.0.5 ([@pvizeli] - [#6856])
+- use change light level to avoid variable ramp speeds ([@wardcraigj] - [#6860])
+- Handle aiohttp task cancellation better ([@balloob] - [#6862])
+- Introduced Ring binary sensors and refactored Ring component ([@tchellomello] - [#6520]) (breaking change) (new-platform)
+- Upgrade sendgrid to 3.6.5 ([@fabaff] - [#6866])
+- Upgrade sphinx-autodoc-typehints to 1.2.0 ([@fabaff] - [#6865])
+- Added Met Office weather and sensor components ([@jacobtomlinson] - [#6742]) (new-platform)
+- Upgrade speedtest-cli to 1.0.3 ([@fabaff] - [#6867])
+- Bumped amcrest module to 1.1.5 ([@tchellomello] - [#6872])
+- Upgrade pytz to 2017.02 ([@fabaff] - [#6875])
+- Upgrade aiohttp_cors to 0.5.2 ([@fabaff] - [#6874])
+- Upgrade sqlalchemy to 1.1.8 ([@fabaff] - [#6873])
+- added support for Fibaro FGR-222 (similar to FGRM-222) ([@ChristianKuehnel] - [#6890])
+- Fluxled ([@danielhiversen] - [#6892])
+- Fix Tado climate set off mode ([@wmalgadey] - [#6848])
+- Fox UMP volume set ([@danieljkemp] - [#6904])
+- Move examples out ([@balloob] - [#6908])
+- Update README.rst ([@balloob])
+- Makes amcrest.sensor to handle properly the scan_interval option. ([@tchellomello] - [#6885])
+- Make sensor.ring to handle scan_interval option as expected. ([@tchellomello] - [#6886])
+- Eliminate needless async_add_job invocation of async_add_devices ([@nugget] - [#6864])
+- Onkyo update ([@danieljkemp] - [#6906])
+- Fix for #6691 Neato Connection error handling ([@turbokongen] - [#6731])
+- Adds support for the PlugInDimmer hardware ([@gurumitts] - [#6915])
+- Support for zwave light transitions ([@armills] - [#6868])
+- Bump pyHik library version to support more cameras ([@mezz64] - [#6921])
+- Update vera cover refresh logic ([@pavoni] - [#6897])
+- Update frontend ([@balloob])
+- Automation: initial state > restore state ([@balloob] - [#6911]) (breaking change)
+- Upgrade flux_led to 0.17 ([@danielhiversen] - [#6929])
+- Upgrade paho-mqtt to 1.2.1 ([@fabaff] - [#6928])
+- Upgrade distro to 1.0.4 ([@fabaff] - [#6926])
+- Upgrade Sphinx to 1.5.4 ([@fabaff] - [#6927])
+- Allow token authentication for 'hook' switch component ([@KlaasH] - [#6922])
+- WIP - Fix bug in state handling in Vera Switch and Light ([@pavoni] - [#6931])
+- total connect alarm support ([@wardcraigj] - [#6887]) (new-platform)
+- Initial state over restore state ([@balloob] - [#6924]) (breaking change)
+- Eddystone Beacon Temperature Sensor ([@citruz] - [#6789]) (new-platform)
+- Add android ip webcam support for aiohttp2 ([@pvizeli] - [#6940])
+- Bump pywemo version. Fixes Osram/Sylvania Lightify tunable white bulbs. ([@pavoni] - [#6946])
+- Clean artifacts after running Ring tests. ([@tchellomello] - [#6944])
+- Rename zwave nodes by node ID instead of entity ID ([@armills] - [#6938]) (breaking change)
+- Report proper features in mqtt_json light ([@jawilson] - [#6941])
+- Add multi phone numbers support ([@titilambert] - [#6605])
+- Upgrade Sphinx to 1.5.5 ([@fabaff] - [#6947])
+- Upgrade py-cpuinfo to 3.0.0 ([@fabaff] - [#6948])
+- Fix automations listening to HOMEASSISTANT_START ([@balloob] - [#6936]) (breaking change)
+- Fix startup of sonos / snapshot handling / error handling ([@pvizeli] - [#6945])
+- Upgrade mysensors dep and callbacks ([@MartinHjelmare] - [#6950])
+- Added average temperature for the day before and the current period ([@diogos88] - [#6883])
+- Upgrade sqlalchemy to 1.1.9 ([@fabaff] - [#6955])
+- Update for 0.42 ([@fabaff])
+- Initial import for HassIO ([@pvizeli] - [#6935]) (new-platform)
+- light.yeelight: catch i/o related exceptions from the backend lib ([@rytilahti] - [#6952])
+- Fix current_temperature is rounded ([@aufano] - [#6960])
+- Preserve customize glob order. ([@andrey-git] - [#6963])
+- Foscam Camera: Adding exception handling when fetching the camera image to avoid python exception errors when host is not reachable or rather any url error to camera ([@viswa-swami] - [#6964])
+- Crime Reports sensor ([@happyleavesaoc] - [#6966]) (new-platform)
+- Update kodi for aiohttp2 ([@armills] - [#6967])
+- Bugfix time and task coro ([@pvizeli] - [#6968])
+- Fix control+c quitting HASS ([@balloob] - [#6974])
+- Update Emby for aiohttp v2 ([@mezz64] - [#6981])
+- switch.tplink: bump pyhs100 version requirement ([@rytilahti] - [#6986])
+- Warn if start takes a long time. ([@balloob] - [#6975])
+- Bump Amcrest module to 1.1.8 ([@tchellomello] - [#6990])
+
+[#5969]: https://github.com/home-assistant/home-assistant/pull/5969
+[#6520]: https://github.com/home-assistant/home-assistant/pull/6520
+[#6605]: https://github.com/home-assistant/home-assistant/pull/6605
+[#6688]: https://github.com/home-assistant/home-assistant/pull/6688
+[#6704]: https://github.com/home-assistant/home-assistant/pull/6704
+[#6708]: https://github.com/home-assistant/home-assistant/pull/6708
+[#6726]: https://github.com/home-assistant/home-assistant/pull/6726
+[#6731]: https://github.com/home-assistant/home-assistant/pull/6731
+[#6733]: https://github.com/home-assistant/home-assistant/pull/6733
+[#6742]: https://github.com/home-assistant/home-assistant/pull/6742
+[#6752]: https://github.com/home-assistant/home-assistant/pull/6752
+[#6753]: https://github.com/home-assistant/home-assistant/pull/6753
+[#6757]: https://github.com/home-assistant/home-assistant/pull/6757
+[#6759]: https://github.com/home-assistant/home-assistant/pull/6759
+[#6760]: https://github.com/home-assistant/home-assistant/pull/6760
+[#6761]: https://github.com/home-assistant/home-assistant/pull/6761
+[#6763]: https://github.com/home-assistant/home-assistant/pull/6763
+[#6764]: https://github.com/home-assistant/home-assistant/pull/6764
+[#6768]: https://github.com/home-assistant/home-assistant/pull/6768
+[#6769]: https://github.com/home-assistant/home-assistant/pull/6769
+[#6770]: https://github.com/home-assistant/home-assistant/pull/6770
+[#6771]: https://github.com/home-assistant/home-assistant/pull/6771
+[#6772]: https://github.com/home-assistant/home-assistant/pull/6772
+[#6773]: https://github.com/home-assistant/home-assistant/pull/6773
+[#6775]: https://github.com/home-assistant/home-assistant/pull/6775
+[#6776]: https://github.com/home-assistant/home-assistant/pull/6776
+[#6779]: https://github.com/home-assistant/home-assistant/pull/6779
+[#6782]: https://github.com/home-assistant/home-assistant/pull/6782
+[#6789]: https://github.com/home-assistant/home-assistant/pull/6789
+[#6790]: https://github.com/home-assistant/home-assistant/pull/6790
+[#6792]: https://github.com/home-assistant/home-assistant/pull/6792
+[#6793]: https://github.com/home-assistant/home-assistant/pull/6793
+[#6795]: https://github.com/home-assistant/home-assistant/pull/6795
+[#6796]: https://github.com/home-assistant/home-assistant/pull/6796
+[#6798]: https://github.com/home-assistant/home-assistant/pull/6798
+[#6799]: https://github.com/home-assistant/home-assistant/pull/6799
+[#6801]: https://github.com/home-assistant/home-assistant/pull/6801
+[#6803]: https://github.com/home-assistant/home-assistant/pull/6803
+[#6805]: https://github.com/home-assistant/home-assistant/pull/6805
+[#6807]: https://github.com/home-assistant/home-assistant/pull/6807
+[#6808]: https://github.com/home-assistant/home-assistant/pull/6808
+[#6809]: https://github.com/home-assistant/home-assistant/pull/6809
+[#6810]: https://github.com/home-assistant/home-assistant/pull/6810
+[#6817]: https://github.com/home-assistant/home-assistant/pull/6817
+[#6826]: https://github.com/home-assistant/home-assistant/pull/6826
+[#6829]: https://github.com/home-assistant/home-assistant/pull/6829
+[#6830]: https://github.com/home-assistant/home-assistant/pull/6830
+[#6832]: https://github.com/home-assistant/home-assistant/pull/6832
+[#6835]: https://github.com/home-assistant/home-assistant/pull/6835
+[#6838]: https://github.com/home-assistant/home-assistant/pull/6838
+[#6839]: https://github.com/home-assistant/home-assistant/pull/6839
+[#6846]: https://github.com/home-assistant/home-assistant/pull/6846
+[#6847]: https://github.com/home-assistant/home-assistant/pull/6847
+[#6848]: https://github.com/home-assistant/home-assistant/pull/6848
+[#6852]: https://github.com/home-assistant/home-assistant/pull/6852
+[#6853]: https://github.com/home-assistant/home-assistant/pull/6853
+[#6856]: https://github.com/home-assistant/home-assistant/pull/6856
+[#6860]: https://github.com/home-assistant/home-assistant/pull/6860
+[#6862]: https://github.com/home-assistant/home-assistant/pull/6862
+[#6864]: https://github.com/home-assistant/home-assistant/pull/6864
+[#6865]: https://github.com/home-assistant/home-assistant/pull/6865
+[#6866]: https://github.com/home-assistant/home-assistant/pull/6866
+[#6867]: https://github.com/home-assistant/home-assistant/pull/6867
+[#6868]: https://github.com/home-assistant/home-assistant/pull/6868
+[#6872]: https://github.com/home-assistant/home-assistant/pull/6872
+[#6873]: https://github.com/home-assistant/home-assistant/pull/6873
+[#6874]: https://github.com/home-assistant/home-assistant/pull/6874
+[#6875]: https://github.com/home-assistant/home-assistant/pull/6875
+[#6883]: https://github.com/home-assistant/home-assistant/pull/6883
+[#6885]: https://github.com/home-assistant/home-assistant/pull/6885
+[#6886]: https://github.com/home-assistant/home-assistant/pull/6886
+[#6887]: https://github.com/home-assistant/home-assistant/pull/6887
+[#6890]: https://github.com/home-assistant/home-assistant/pull/6890
+[#6892]: https://github.com/home-assistant/home-assistant/pull/6892
+[#6897]: https://github.com/home-assistant/home-assistant/pull/6897
+[#6904]: https://github.com/home-assistant/home-assistant/pull/6904
+[#6906]: https://github.com/home-assistant/home-assistant/pull/6906
+[#6908]: https://github.com/home-assistant/home-assistant/pull/6908
+[#6911]: https://github.com/home-assistant/home-assistant/pull/6911
+[#6915]: https://github.com/home-assistant/home-assistant/pull/6915
+[#6921]: https://github.com/home-assistant/home-assistant/pull/6921
+[#6922]: https://github.com/home-assistant/home-assistant/pull/6922
+[#6924]: https://github.com/home-assistant/home-assistant/pull/6924
+[#6926]: https://github.com/home-assistant/home-assistant/pull/6926
+[#6927]: https://github.com/home-assistant/home-assistant/pull/6927
+[#6928]: https://github.com/home-assistant/home-assistant/pull/6928
+[#6929]: https://github.com/home-assistant/home-assistant/pull/6929
+[#6931]: https://github.com/home-assistant/home-assistant/pull/6931
+[#6935]: https://github.com/home-assistant/home-assistant/pull/6935
+[#6936]: https://github.com/home-assistant/home-assistant/pull/6936
+[#6938]: https://github.com/home-assistant/home-assistant/pull/6938
+[#6940]: https://github.com/home-assistant/home-assistant/pull/6940
+[#6941]: https://github.com/home-assistant/home-assistant/pull/6941
+[#6944]: https://github.com/home-assistant/home-assistant/pull/6944
+[#6945]: https://github.com/home-assistant/home-assistant/pull/6945
+[#6946]: https://github.com/home-assistant/home-assistant/pull/6946
+[#6947]: https://github.com/home-assistant/home-assistant/pull/6947
+[#6948]: https://github.com/home-assistant/home-assistant/pull/6948
+[#6950]: https://github.com/home-assistant/home-assistant/pull/6950
+[#6952]: https://github.com/home-assistant/home-assistant/pull/6952
+[#6955]: https://github.com/home-assistant/home-assistant/pull/6955
+[#6960]: https://github.com/home-assistant/home-assistant/pull/6960
+[#6963]: https://github.com/home-assistant/home-assistant/pull/6963
+[#6964]: https://github.com/home-assistant/home-assistant/pull/6964
+[#6966]: https://github.com/home-assistant/home-assistant/pull/6966
+[#6967]: https://github.com/home-assistant/home-assistant/pull/6967
+[#6968]: https://github.com/home-assistant/home-assistant/pull/6968
+[#6974]: https://github.com/home-assistant/home-assistant/pull/6974
+[#6975]: https://github.com/home-assistant/home-assistant/pull/6975
+[#6981]: https://github.com/home-assistant/home-assistant/pull/6981
+[#6986]: https://github.com/home-assistant/home-assistant/pull/6986
+[#6990]: https://github.com/home-assistant/home-assistant/pull/6990
+[@ChristianKuehnel]: https://github.com/ChristianKuehnel
+[@DavidMStraub]: https://github.com/DavidMStraub
+[@KlaasH]: https://github.com/KlaasH
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@Xorso]: https://github.com/Xorso
+[@aarya123]: https://github.com/aarya123
+[@aequitas]: https://github.com/aequitas
+[@amelchio]: https://github.com/amelchio
+[@andrey-git]: https://github.com/andrey-git
+[@armills]: https://github.com/armills
+[@aufano]: https://github.com/aufano
+[@balloob]: https://github.com/balloob
+[@bdurrer]: https://github.com/bdurrer
+[@citruz]: https://github.com/citruz
+[@danielhiversen]: https://github.com/danielhiversen
+[@danieljkemp]: https://github.com/danieljkemp
+[@danielperna84]: https://github.com/danielperna84
+[@diogos88]: https://github.com/diogos88
+[@fabaff]: https://github.com/fabaff
+[@geekofweek]: https://github.com/geekofweek
+[@goto100]: https://github.com/goto100
+[@gurumitts]: https://github.com/gurumitts
+[@happyleavesaoc]: https://github.com/happyleavesaoc
+[@jacobtomlinson]: https://github.com/jacobtomlinson
+[@jannau]: https://github.com/jannau
+[@jawilson]: https://github.com/jawilson
+[@leppa]: https://github.com/leppa
+[@lwis]: https://github.com/lwis
+[@m00dawg]: https://github.com/m00dawg
+[@mezz64]: https://github.com/mezz64
+[@micw]: https://github.com/micw
+[@nugget]: https://github.com/nugget
+[@pavoni]: https://github.com/pavoni
+[@pvizeli]: https://github.com/pvizeli
+[@quadportnick]: https://github.com/quadportnick
+[@rytilahti]: https://github.com/rytilahti
+[@tantecky]: https://github.com/tantecky
+[@tchellomello]: https://github.com/tchellomello
+[@titilambert]: https://github.com/titilambert
+[@turbokongen]: https://github.com/turbokongen
+[@viswa-swami]: https://github.com/viswa-swami
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@wardcraigj]: https://github.com/wardcraigj
+[@wmalgadey]: https://github.com/wmalgadey

source/components/index.html

@@ -124,6 +124,11 @@ allComponents.pop(); // remove placeholder element at the end
       // set default value in search from URL
       jQuery('.component-search input').val(decodeURIComponent(location.hash).substring(8));
     }
+    
+    // add focus to the search field - even on IE
+    setTimeout(function () {
+      jQuery('.component-search input').focus();
+    }, 1);
   }
   init();
   
@@ -222,36 +227,6 @@ allComponents.pop(); // remove placeholder element at the end
 
     return false;
   });
-  
-    /**
-   * Simple debounce implementation, based on http://davidwalsh.name/javascript-debounce-function
-   */
-  function debounce(func, wait, immediate) {
-    var timeout;
-    return function() {
-      var context = this, args = arguments;
-      var later = function() {
-        timeout = null;
-        if (!immediate) {
-          func.apply(context, args);
-        }
-      };
-      var callNow = immediate && !timeout;
-      clearTimeout(timeout);
-      timeout = setTimeout(later, wait);
-      if (callNow) {
-        func.apply(context, args);
-      }
-    };
-  };
-  // update view by search text
-  $('.component-search input').keyup(debounce(function() {
-    var text = $(this).val();
-    // sanitize input
-    text = text.replace(/[(\?|\&\{\}\(\))]/gi, '');
-    updateHash('#search/' + text);
-    applyFilter();
-  }, 500));
 
   /**
    * Simple debounce implementation, based on http://davidwalsh.name/javascript-debounce-function
@@ -286,6 +261,5 @@ allComponents.pop(); // remove placeholder element at the end
 
   window.addEventListener('hashchange', applyFilter);
   applyFilter();
-
 })();
 </script>

source/getting-started/presence-detection.markdown

@@ -29,7 +29,7 @@ The device tracker component offers presence detection for Home Assistant. It su
 
 Scanning for connected devices is easy to setup. See the instructions for our [supported routers][routers] or [scan the network using nmap][nmap]. This approach does have its limitations, however: it will only be able to detect if a device is home, and iPhones may show as not home inaccurately (as iPhones disconnect from WiFi if idle).
 
-Home Assistant currently supports two third-party services for presence detection: [OwnTracks][ha-owntracks] and [Locative][ha-locative]. OwnTracks is an app that you install on your iPhone or Android phone that allows you to push the location of your device to Home Assistant using an MQTT broker. An MQTT broker is an Internet of Things communication platform that you can [freely host yourself][mqtt-self] or get [a private instance for free in the cloud](/components/mqtt/#run-your-own).
+Home Assistant currently supports multiple third-party services for presence detection: [OwnTracks][ha-owntracks], [GPSLogger][ha-gpslogger] and [Locative][ha-locative]. OwnTracks is an app that you install on your iPhone or Android phone that allows you to push the location of your device to Home Assistant using an MQTT broker. An MQTT broker is an Internet of Things communication platform that you can [freely host yourself][mqtt-self] or get [a private instance for free in the cloud](/components/mqtt/#run-your-own).
 
 <p class='note'>
 OwnTracks communicates directly with your MQTT broker; no data will pass through their servers.
@@ -45,6 +45,7 @@ Home Assistant will know the location of your device if you are using OwnTracks.
 [nmap]: /components/device_tracker.nmap_tracker/
 [ha-owntracks]: /components/device_tracker.owntracks/
 [ha-locative]: /components/device_tracker.locative/
+[gpslogger]: /components/device_tracker.gpslogger/
 [mqtt-self]: /components/mqtt/#run-your-own
 [mqtt-cloud]: /components/mqtt/#cloudmqtt
 [zone]: /components/zone/