home-assistant · niklaswa · Jul 16, 2018 · Jul 16, 2018 · Jul 16, 2018 · Jul 16, 2018
diff --git a/_config.yml b/_config.yml
@@ -141,14 +141,14 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 73
+current_minor_version: 74
 current_patch_version: 1
-date_released: 2018-07-08
+date_released: 2018-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-0741---july-24"
 # Minor release (Example #release-0431---april-25):
 
 # Date we moved to Discourse for comments

diff --git a/plugins/active_link.rb b/plugins/active_link.rb
@@ -10,7 +10,7 @@ def initialize(tag_name, text, token)
     def render(context)
       href = Liquid::Template.parse(@href).render context
       title = Liquid::Template.parse(@title).render context
-      cls = @href == context.registers[:page]["url"] ? "class='active'" : ''
+      cls = href == context.registers[:page]["url"] ? "class='active'" : ''
       "<a #{cls} href='#{href}'>#{title}</a>"
     end
   end

diff --git a/source/_components/asterisk_mbox.markdown b/source/_components/asterisk_mbox.markdown
@@ -9,11 +9,11 @@ sharing: true
 footer: true
 logo: asterisk.png
 ha_category: Other
-ha_version: 0.51
 ha_iot_class: "Local Push"
+ha_release: 0.51
 ---
 
-The `asterisk_mbox `Asterisk Voicemail integration for Home Assistant allows you to view, listen to, and delete voicemails from an Asterisk voicemail mailbox. The component includes a panel on the frontend that provides caller-id and speech-to-text transcription (using Google's API) of messages in addition to playback and message deletion. There is also an included sensor that indicates of the number of available messages. There is no requirement that the Asterisk PBX and Home Assistant are running on the same machine.
+The `asterisk_mbox` Asterisk Voicemail integration for Home Assistant allows you to view, listen to, and delete voicemails from an Asterisk voicemail mailbox. The component includes a panel on the frontend that provides caller-id and speech-to-text transcription (using Google's API) of messages in addition to playback and message deletion. There is also an included sensor that indicates of the number of available messages. There is no requirement that the Asterisk PBX and Home Assistant are running on the same machine.
 
 To enable the component, a configuration is required in both Home Assistant as well as on the Asterisk server.
 
@@ -31,13 +31,21 @@ asterisk_mbox:
 
 This will add a new 'Mailbox' side-panel, as well as a sensor to indicate # of messages available.
 
-Configuration variables:
-
-- **password** (*Required*): The password that was set during Asterisk PBX configuration
-- **host** (*Required*): The ip-address of the server that is running the Asterisk PBX
-- **port** (*Required*): The port on the Asterisk PBX server that was configured during Asterisk PBX configuration
+{% configuration %}
+password:
+  description: The password that was set during Asterisk PBX configuration
+  required: true
+  type: string
+host:
+  description: The ip-address of the server that is running the Asterisk PBX
+  required: true
+  type: string
+port:
+  description: The port on the Asterisk PBX server that was configured during Asterisk PBX configuration
+  required: true
+  type: string
+{% endconfiguration %}
 
 <p class='note warning'>
 Communication between the Asterisk PBX server and the Home Assistant server is password-protected, but the data transmission is not encrypted. It is recommended to only use this component when communication is contained within a local area network.
 </p>
-
diff --git a/source/_components/auth.markdown b/source/_components/auth.markdown
@@ -0,0 +1,15 @@
+---
+layout: page
+title: "Auth"
+description: "This component is responsible for providing the authentication endpoints."
+date: 2018-03-19 21:04
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: home-assistant.png
+ha_category: Other
+ha_release: 0.73
+---
+
+This component creates the endpoints for the authentication system that is built into Home Assistant. There are no configuration options for this component directly as it relies on the auth system in the core.
diff --git a/source/_components/binary_sensor.insteon_plm.markdown b/source/_components/binary_sensor.insteon_plm.markdown
@@ -10,12 +10,12 @@ footer: true
 logo: insteon.png
 ha_category: Binary Sensor
 ha_iot_class: "Local Push"
-ha_version: 0.39
+ha_release: 0.39
 ---
 
 The `insteon_plm` binary sensor platform lets you control your sensors through 
 an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a
 USB or serial port.  To add support, set up the primary [insteon_plm]
 component.
 
-[insteon_plm]: /components/insteon_plm/
+[insteon_plm]: /components/insteon_plm/
diff --git a/source/_components/climate.generic_thermostat.markdown b/source/_components/climate.generic_thermostat.markdown
@@ -43,7 +43,7 @@ Configuration variables:
 
 A full configuration example looks like the one below. `min_cycle_duration` and `keep_alive` must contain at least one of the following entries: `days:`, `hours:`, `minutes:`, `seconds:` or `milliseconds:`.
 
-Currently the `generic_thermostat` climate platform supports 'heat', 'cool' and 'off' operation modes. You can force your `generic_thermstat` to avoid starting by setting Operation to 'off'. 
+Currently the `generic_thermostat` climate platform supports 'auto', 'heat', 'cool' and 'off' operation modes. If you set the operation mode to 'auto' it will switch to the matching mode 'heat' or 'cool' (`ac_mode`) automatically. You can force your `generic_thermostat` to avoid starting by setting `initial_operation_mode` to 'off'. 
 
 Please note that changing Away Mode you will force a target temperature change as well that will get restored once the Away Mode is turned off. 
 

diff --git a/source/_components/climate.oem.markdown b/source/_components/climate.oem.markdown
@@ -13,7 +13,7 @@ ha_release: 0.39
 ha_iot_class: "Local Polling"
 ---
 
-This platform supports the ESP82666 based "WiFi MQTT Relay / Thermostat" sold by [OpenEnergyMonitor](https://shop.openenergymonitor.com/wifi-mqtt-relay-thermostat/). The underlying [library](http://oemthermostat.readthedocs.io/) only supports this single relay variant of the [original device](https://harizanov.com/2014/12/wifi-iot-3-channel-relay-board-with-mqtt-and-http-api-using-esp8266/).
+This platform supports the ESP8266 based "WiFi MQTT Relay / Thermostat" sold by [OpenEnergyMonitor](https://shop.openenergymonitor.com/wifi-mqtt-relay-thermostat/). The underlying [library](http://oemthermostat.readthedocs.io/) only supports this single relay variant of the [original device](https://harizanov.com/2014/12/wifi-iot-3-channel-relay-board-with-mqtt-and-http-api-using-esp8266/).
 
 This platform controls the setpoint of the thermostat in its "manual" mode, therefore there is a configuration option the away setpoint.
 

diff --git a/source/_components/device_tracker.mqtt_json.markdown b/source/_components/device_tracker.mqtt_json.markdown
@@ -9,11 +9,10 @@ sharing: true
 footer: true
 logo: mqtt.png
 ha_category: Presence Detection
-ha_version: 0.44
 ha_iot_class: depends
+ha_release: 0.44
 ---
 
-
 The `mqtt_json` device tracker platform allows you to detect presence by monitoring an MQTT topic for new locations. To use this platform, you specify a unique topic for each device.
 
 To use this device tracker in your installation, add the following to your `configuration.yaml` file:
@@ -27,10 +26,16 @@ device_tracker:
       annetherese_n4: location/annetherese
 ```
 
-Configuration variables:
-
-- **devices** (*Required*): List of devices with their topic.
-- **qos** (*Optional*): The QoS level of the topic.
+{% configuration %}
+devices:
+  description: List of devices with their topic.
+  required: true
+  type: list
+qos:
+  description: The QoS level of the topic.
+  required: false
+  type: string
+{% endconfiguration %}
 
 This platform receives JSON formatted payloads containing GPS information, for example:
 

diff --git a/source/_components/device_tracker.xiaomi_miio.markdown b/source/_components/device_tracker.xiaomi_miio.markdown
@@ -9,8 +9,8 @@ sharing: true
 footer: true
 logo: xiaomi.png
 ha_category: Presence Detection
-ha_version: 0.67
 ha_iot_class: "Local Polling"
+ha_release: 0.67
 ---
 
 The `xiaomi_miio` device tracker platform is observing your Xiaomi Mi WiFi Repeater 2 and reporting all associated WiFi clients.

diff --git a/source/_components/dominos.markdown b/source/_components/dominos.markdown
@@ -9,8 +9,8 @@ sharing: true
 footer: true
 logo: dominos.png
 ha_category: Other
-ha_version: 0.59
 ha_iot_class: "Cloud Polling"
+ha_release: 0.59
 ---
 
 The `dominos` component allows you to order Dominos Pizza from within your Home Assistant scripts and automations.

diff --git a/source/_components/fan.insteon_hub.markdown b/source/_components/fan.insteon_hub.markdown
diff --git a/source/_components/fan.insteon_local.markdown b/source/_components/fan.insteon_local.markdown
@@ -1,6 +1,6 @@
 ---
 layout: page
-title: "Insteon (Local) Fan"
+title: "Insteon (local) Fan"
 description: "Instructions on how to setup the Insteon Hub Fans locally within Home Assistant."
 date:  2017-04-06 11:00
 sidebar: true
@@ -9,9 +9,10 @@ sharing: true
 footer: true
 logo: insteon.png
 ha_category: Fan
-ha_version: 0.48
+ha_release: 0.48
+redirect_from: /components/fan.insteon_hub/
 ---
 
-The `insteon_local` fan component lets you control your fan connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
+The `insteon_local` fan component lets you control your fans connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
 
-To get your insteon fans working with Home Assistant, follow the instructions for the general [Insteon local component](/components/insteon_local/). The fans will be automatically disovered and added to Home Assistant. The device names will be the Insteon address of the fans.
+To get your Insteon fans working with Home Assistant, follow the instructions for the general [Insteon local component](/components/insteon_local/). The fans will be automatically discovered and added to Home Assistant. The device names will be the Insteon address of the fans.
diff --git a/source/_components/fan.insteon_plm.markdown b/source/_components/fan.insteon_plm.markdown
@@ -1,7 +1,7 @@
 ---
 layout: page
 title: "Insteon PLM Fan"
-description: "Instructions on how to setup the Insteon PLM fan locally within Home Assistant."
+description: "Instructions on how to setup the Insteon PLM Fans locally within Home Assistant."
 date: 2017-02-19 17:00
 sidebar: true
 comments: false
@@ -10,15 +10,7 @@ footer: true
 logo: insteon.png
 ha_category: Fan
 ha_iot_class: "Local Push"
-ha_version: 0.65
+ha_release: 0.65
 ---
 
-The `insteon_plm` fan platform lets you control your [FanLinc] through 
-an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a
-USB or serial port.  To add support, set up the primary [insteon_plm]
-component.
-
-[insteon_plm]: /components/insteon_plm/
-[FanLinc]: https://www.smarthome.com/fanlinc-insteon-2475f-ceiling-fan-and-light-controller-fixture-module-dual-band.html
-
-
+The `insteon_plm` fan platform lets you control your [FanLinc](https://www.smarthome.com/fanlinc-insteon-2475f-ceiling-fan-and-light-controller-fixture-module-dual-band.html) through an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a USB or serial port. To add support, set up the primary [insteon_plm](/components/insteon_plm/) component.
diff --git a/source/_components/fan.xiaomi_miio.markdown b/source/_components/fan.xiaomi_miio.markdown
@@ -9,8 +9,8 @@ sharing: true
 footer: true
 logo: xiaomi.png
 ha_category: Fan
-ha_version: 0.57
 ha_iot_class: "Local Polling"
+ha_release: 0.57
 ---
 
 The `xiaomi_miio` fan platform allows you to control the Xiaomi Air Purifier and Xiaomi Air Humidifier.
@@ -181,20 +181,20 @@ fan:
 
 {% configuration %}
 host:
-  description: The IP address of your fan.
+  description: The IP address of your miio fan.
   required: true
   type: string
 token:
-  description: The API token of your fan.
+  description: The API token of your miio fan.
   required: true
   type: string
 name:
-  description: The name of your fan.
+  description: The name of your miio fan.
   required: false
   type: string
   default: Xiaomi Air Purifier
 model:
-  description: The model of your device.
+  description: The model of your miio fan. Valid values are `zhimi.airpurifier.v6`, `zhimi.airpurifier.v3`, `zhimi.humidifier.v1` and `zhimi.humidifier.ca1`. This setting can be used to bypass the device model detection and is recommended if your device isn't always available.
   required: false
   type: string
 {% endconfiguration %}

diff --git a/source/_components/goalfeed.markdown b/source/_components/goalfeed.markdown
@@ -9,7 +9,7 @@ sharing: true
 footer: true
 logo: goalfeed.png
 ha_category: Other
-ha_version: 0.63
+ha_release: 0.63
 ---
 
 The `goalfeed` component lets you use your Goalfeed account to trigger events in Home Assistant whenever a NHL or MLB team scores. 

diff --git a/source/_components/image_processing.microsoft_face_identify.markdown b/source/_components/image_processing.microsoft_face_identify.markdown
@@ -24,10 +24,10 @@ For using the result inside an automation rule, take a look at the [component](/
 ```yaml
 # Example configuration.yaml entry
 image_processing:
- - platform: microsoft_face_identify
-   group: family
-   source:
-    - entity_id: camera.door
+  - platform: microsoft_face_identify
+    group: family
+    source:
+      - entity_id: camera.door
 ```
 
 Configuration variables:

diff --git a/source/_components/input_number.markdown b/source/_components/input_number.markdown
@@ -194,3 +194,38 @@ automation:
         payload: "{{ states('input_number.target_temp') | int }}"
 ```
 {% endraw %}
+
+Here's an example of `input_number` being used as a delay in an automation.
+
+{% raw %}
+```yaml
+# Example configuration.yaml entry using 'input_number' as a delay in an automation
+input_number:
+  minutes:
+    name: minutes
+    icon: mdi:clock-start
+    initial: 3
+    min: 0
+    max: 6
+    step: 1
+
+  seconds:
+    name: seconds
+    icon: mdi:clock-start
+    initial: 30
+    min: 0
+    max: 60
+    step: 10
+
+automation:
+ - alias: turn something off after x time after turning it on
+   trigger:
+     platform: state
+     entity_id: switch.something
+     to: 'on'
+   action:
+     - delay: '00:{{ states.input_number.minutes.state | int }}:{{ states.input_number.seconds.state | int }}'
+     - service: switch.turn_off
+       entity_id: switch.something
+```
+{% endraw %}
diff --git a/source/_components/insteon_hub.markdown b/source/_components/insteon_hub.markdown