home-assistant · balloob · Feb 10, 2018 · Nov 7, 2017 · Nov 9, 2017 · Jan 21, 2018
diff --git a/_config.yml b/_config.yml
@@ -139,14 +139,14 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 62
-current_patch_version: 1
-date_released: 2018-01-30
+current_minor_version: 63
+current_patch_version: 0
+date_released: 2018-02-10
 
 # 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: "#release-0621---january-30"
+patch_version_notes: "#"
 # Minor release (Example #release-0431---april-25):
 
 # Date we moved to Discourse for comments

diff --git a/source/_components/binary_sensor.knx.markdown b/source/_components/binary_sensor.knx.markdown
@@ -25,6 +25,7 @@ binary_sensor:
     address: '6/0/2'
     device_class: 'motion'
     #significant_bit: 2
+    #reset_after: 100
 ```
 
 Configuration variables:
@@ -33,6 +34,7 @@ Configuration variables:
 - **address**: KNX group address of the binary sensor.
 - **device_class** (Optional): HASS device class e.g. "motion".
 - **significant_bit** (Optional): Specify which significant bit of the KNX value should be used. Default is 1.
+- **reset_after** (Optional): Reset back to OFF state after specified milliseconds.
 
 You can also attach actions to binary sensors (e.g., to switch on a light when a switch was pressed). In this example, one light is switched on when the button was pressed once and two others when the button was pressed a second time.
 

diff --git a/source/_components/binary_sensor.mercedesme.markdown b/source/_components/binary_sensor.mercedesme.markdown
@@ -0,0 +1,20 @@
+---
+layout: page
+title: "Mercedes me Binary Sensor"
+description: "Instructions on how to integrate Mercedes me binary sensors into Home Assistant."
+date: 2018-01-27 17:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: mercedesme.png
+ha_category: Binary Sensor
+ha_iot_class: "Cloud polling"
+ha_release: 0.63
+---
+
+The `Mercedes me` platform allows you to get data from your [Mercedes me connected car](https://www.mercedes-benz.com/en/mercedes-me/) sensors like windows, doors, lock, tire warnings from within Home Assistant.
+
+They will be automatically discovered if the Mercedes me component is loaded.
+
+For more configuration information see the [Mercedes me component](/components/mercedes me/) documentation.
diff --git a/source/_components/binary_sensor.mqtt.markdown b/source/_components/binary_sensor.mqtt.markdown
@@ -75,6 +75,11 @@ value_template:
   description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload."
   required: false
   type: string
+force_update:
+  description: Sends update events even if the value hasn't changed. Useful if you want to have meaningful value graphs in history.
+  reqired: false
+  type: boolean
+  default: False 
 {% endconfiguration %}
 
 

diff --git a/source/_components/binary_sensor.template.markdown b/source/_components/binary_sensor.template.markdown
@@ -48,6 +48,10 @@ binary_sensor:
             description: Name to use in the frontend.
             required: false
             type: string
+          entity_id:
+            description: A list of entity IDs so the sensor only reacts to state changes of these entities. This can be used if the automatic analysis fails to find all relevant entities.
+            required: false
+            type: string, list
           device_class:
             description: The type/class of the sensor to set the icon in the frontend.
             required: false
@@ -57,6 +61,14 @@ binary_sensor:
             description: Defines a template to set the state of the sensor.
             required: true
             type: template
+          icon_template:
+            description: Defines a template for the icon of the sensor.
+            required: false
+            type: template
+          entity_picture_template:
+            description: Defines a template for the entity picture of the sensor.
+            required: false
+            type: template
           delay_on:
             description: The amount of time the template state must be ***met*** before this sensor will switch to `on`.
             required: false

diff --git a/source/_components/camera.canary.markdown b/source/_components/camera.canary.markdown
@@ -13,6 +13,20 @@ ha_release: "0.60"
 ha_iot_class: "Cloud Polling"
 ---
 
-The `canary` camera platform allows you to view the latest camera image (triggered by motion) by your [Canary](https://canary.is) device in Home Assistant.
+The `canary` camera platform allows you to watch the live stream of your [Canary](https://canary.is) camera in Home Assistant. This requires the [`ffmpeg` component](/components/ffmpeg/) to be already configured.
 
-To add `canary` camera to your installation, follow instructions in [Canary component](/components/canary/).
+To add `canary` camera to your installation, follow instructions in [Canary component](/components/canary/). Once you have [Canary component](/components/canary/) setup, your [Canary](https://canary.is) camera(s) should show up automatically.
+
+You can add the following to your `configuration.yaml` file to configure `canary` camera with optional settings:
+
+```yaml
+camera:
+  - platform: canary
+```
+
+{% configuration %}
+  ffmpeg_arguments:
+    description: Extra options to pass to `ffmpeg`, e.g. image quality or video filter options. More details in [FFmpeg component](/components/ffmpeg).
+    required: false
+    type: string
+{% endconfiguration %}
diff --git a/source/_components/climate.melissa.markdown b/source/_components/climate.melissa.markdown
@@ -0,0 +1,20 @@
+---
+layout: page
+title: "Melissa Climate"
+description: "Instructions on how to integrate Melissa climate system (HVAC) into Home Assistant."
+date: 2018-01-08 20:21
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: mclimate.png
+ha_category: Climate
+ha_iot_class: "Cloud Polling"
+ha_release: 0.63
+---
+
+The `Melissa` climate platform allows you to control your [Melissa Climate](http://seemelissa.com/) from within Home Assistant.
+
+The climate platform will be automatically configured if Melissa component is configured.
+
+For more configuration information see the [Melissa component](/components/melissa/) documentation.
diff --git a/source/_components/cover.template.markdown b/source/_components/cover.template.markdown
@@ -48,6 +48,10 @@ cover:
         description: Name to use in the frontend.
         required: false
         type: string
+      entity_id:
+        description: A list of entity IDs so the cover only reacts to state changes of these entities. This can be used if the automatic analysis fails to find all relevant entities.
+        required: false
+        type: [string, list]
       value_template:
         description: Defines a template to get the state of the cover. Valid values are `open`/`true` or `closed`/`false`. [`value_template`](#value_template) and [`position_template`](#position_template) cannot be specified concurrently.
         required: exclusive
@@ -197,6 +201,9 @@ cover:
           {% else %}
             mdi:window-closed
           {% endif %}
+        entity_id:
+          - cover.bedroom
+          - cover.livingroom
 
 sensor:
   - platform: template

diff --git a/source/_components/device_tracker.mercedesme.markdown b/source/_components/device_tracker.mercedesme.markdown
@@ -0,0 +1,19 @@
+---
+layout: page
+title: "Mercedes me"
+description: "Instructions on for how to integrate Mercedes me into Home Assistant."
+date: 2018-01-27 10:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: mercedesme.png
+ha_category: Presence Detection
+ha_release: 0.63
+---
+
+The `Mercedes me` platform allows you to get data about the location of your [Mercedes me connected car](https://www.mercedes-benz.com/en/mercedes-me/) car within Home Assistant.
+
+The device tracker platform will be automatically configured if Mercedes me component is configured.
+
+For more configuration information see the [Mercedes me component](/components/mercedesme/) documentation.
diff --git a/source/_components/emulated_hue.markdown b/source/_components/emulated_hue.markdown
@@ -17,9 +17,9 @@ ha_iot_class: "Local Push"
 Be aware that `emulated_hue` doesn't work for new **Google Home** users. If you're a new user of Google Home, use the [Google Assistant component](https://home-assistant.io/components/google_assistant/).
 </p>
 
-The `emulated_hue` component provides a virtual Philips Hue bridge, written entirely in software, that allows services that work with the Hue API to interact with Home Assistant
-entities. The driving use case behind this functionality is to allow Home Assistant to work with an Amazon Echo or Google Home with no set up cost outside of configuration changes.
-The virtual bridge has the ability to turn entities on or off, or change the brightness of dimmable lights. The volume level of media players can be controlled as brightness.
+The `emulated_hue` component provides a virtual Philips Hue bridge, written entirely in software, which allows services that work with the Hue API to interact with Home Assistant
+entities. The driving use case behind for functionality is to allow Home Assistant to work with an Amazon Echo or Google Home with no setup cost outside of configuration changes.
+The virtual bridge can turn entities on/off or change the brightness of dimmable lights. The volume level of media players can be controlled as brightness.
 
 <p class='note'>
 A physical Hue Bridge is required for Philips Hue lights to function - this virtual bridge will not replace a physical bridge. Instead, it allows Home Assistant to represent non-Philips Hue devices to Amazon Echo as Philips Hue devices, which Amazon Echo can control with built-in support.
@@ -47,14 +47,14 @@ emulated_hue:
 
 Configuration variables:
 
-- **type** (*Optional*): The type of assistant who we are emulated for. Either `alexa` or `google_home`, defaults to `google_home`. **This configuration option is deprecated and will be removed in a future release. It is no longer necessary to define type.**
+- **type** (*Optional*): The type of assistant which we are emulating. Either `alexa` or `google_home`, defaults to `google_home`. **This configuration option is deprecated and will be removed in a future release. It is no longer necessary to define type.**
 - **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.
 
-- **advertise_ip** (*Optional*): If you need to override the IP address used for UPNP discovery. (For example, using network isolation in Docker)
-- **advertise_port** (*Optional*): If you need to specifically override the advertised UPNP port.
+- **advertise_ip** (*Optional*): If you need to override the IP address used for UPnP discovery. (For example, using network isolation in Docker)
+- **advertise_port** (*Optional*): If you need to specifically override the advertised UPnP port.
 
-- **upnp_bind_multicast** (*Optional*): Whether or not to bind the UPNP (SSDP) listener to the multicast address (239.255.255.250) or instead to the (unicast) host_ip address specified above (or automatically determined). The default is true, which will work for most situations.  In special circumstances, like running in a FreeBSD or FreeNAS jail, you may need to disable this.
+- **upnp_bind_multicast** (*Optional*): Whether or not to bind the UPnP (SSDP) listener to the multicast address (239.255.255.250) or instead to the (unicast) host_ip address specified above (or automatically determined). The default is true, which will work for most situations.  In special circumstances, like running in a FreeBSD or FreeNAS jail, you may need to disable this.
 
 - **off_maps_to_on_domains** (*Optional*): The domains that maps an "off" command to an "on" command.
 
@@ -75,6 +75,8 @@ Configuration variables:
   - `media_player`
   - `fan`
 
+- **entities** (*Optional*): Customization for entities.
+
 A full configuration sample looks like the one below.
 
 ```yaml
@@ -90,26 +92,21 @@ emulated_hue:
   expose_by_default: true
   exposed_domains:
     - light
-```
-
-With additional customization you will be able to specify the behavior of the existing entities.
-
-```yaml
-# Example customization
-homeassistant:
-  customize:
+  entities:
     light.bedroom_light:
-      # Don't allow light.bedroom_light to be controlled by the emulated Hue bridge
-      emulated_hue_hidden: true
-    light.office_light:
-      # Address light.office_light as "back office light"
-      emulated_hue_name: "back office light"
+      name: "Bedside Lamp"
+    light.ceiling_lights:
+      hidden: true
 ```
 
-The following are attributes that can be applied in the `customize` section:
+The following are attributes that can be applied in the `entities` section:
+
+- **name** (*Optional*): The name that the emulated Hue will use. The default for this is the entity's friendly name.
+- **hidden** (*Optional*): Whether or not the emulated Hue bridge should expose the entity. Adding `hidden: false` will expose the entity to Alexa. The default value for this attribute is controlled by the `expose_by_default` option.
 
-- **emulated_hue_hidden** (*Optional*): Whether or not the entity should be exposed by the emulated Hue bridge. Adding `emulated_hue_hidden: false` will expose the entity to Alexa. The default value for this attribute is controlled by the `expose_by_default` option.
-- **emulated_hue_name** (*Optional*): The name that the emulated Hue will use. The default for this is the entity's friendly name.
+<p class='note'>
+These attributes used to be found under the `customize` section of `homeassistant`, however, they have now been moved to `entities`. Emulated Hue configuration under `homeassistant.customize` will be deprecated in the near future.
+</p>
 
 ### {% linkable_title Troubleshooting %}
 
@@ -118,9 +115,9 @@ You can verify that the `emulated_hue` component has been loaded and is respondi
  - `http://<HA IP Address>:8300/description.xml` - This URL should return a descriptor file in the form of an XML file.
  - `http://<HA IP Address>:8300/api/pi/lights` - This will return a list of devices, lights, scenes, groups, etc.. that `emulated_hue` is exposing to Alexa.
 
-For Google Home, verify that the URLs above are using  port 80, rather than port 8300 (i.e. `http://<HA IP Address>:80/description.xml`).
+For Google Home, verify that the URLs above are using port 80, rather than port 8300 (i.e. `http://<HA IP Address>:80/description.xml`).
 
-An additional step is required to run Home Assistant as non-root user and use port 80 when using the AiO script.  Execute the following command to allow `emulated_hue` to use port 80 as non-root user.
+An additional step is required to run Home Assistant as a non-root user and use port 80 when using the AiO script.  Execute the following command to allow `emulated_hue` to use port 80 as a non-root user.
 
 ```bash
 sudo setcap 'cap_net_bind_service=+ep' /srv/homeassistant/homeassistant_venv/bin/python3

diff --git a/source/_components/goalfeed.markdown b/source/_components/goalfeed.markdown
@@ -0,0 +1,54 @@
+---
+layout: page
+title: "Goalfeed"
+description: "Instructions on how to setup Goalfeed events within Home Assistant."
+date: 2017-12-13 17:30
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: goalfeed.png
+ha_category: Other
+ha_version: 0.63
+---
+
+The `goalfeed` component lets you use your Goalfeed account to trigger events in Home Assistant whenever a NHL or MLB team scores. 
+
+To use this component, enter your email address and password from your goalfeed.ca account in your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+goalfeed:
+  username: your_email@gmail.com
+  password: goalfeed_password
+```
+
+{% configuration %}
+username:
+  required: true
+  description: The email address on your goalfeed.ca account.
+  type: string
+password:
+  required: true
+  description: The password on your goalfeed.ca account.
+  type: string
+{% endconfiguration %}
+
+Now you can use the goal event type in your automations:
+
+```yaml
+- alias: 'Jets Goal'
+  trigger:
+    platform: event
+    event_type: goal
+    event_data:
+      team_name: "Winnipeg Jets"
+```
+
+Goal events have the following event data:
+
+- **team**: Three letter code representing the team. This is unique within the leagues, but not unique across the leagues (i.e. 'WPG' or 'TOR').
+- **team_name**: The team that scored (i.e. 'Winnipeg Jets' or 'Toronto Blue Jays').
+- **team_hash**: A unique hash for the team (you can find these values on https://goalfeed.ca/get-teams).
+- **league_id**: A unique number for the league.
+- **league_name**: A the short name of the league (i.e. 'NHL' or 'MLB').
diff --git a/source/_components/influxdb.markdown b/source/_components/influxdb.markdown
@@ -35,7 +35,6 @@ Configuration variables:
 - **ssl** (*Optional*): Use https instead of http to connect. Defaults to false.
 - **verify_ssl** (*Optional*): Verify SSL certificate for https request. Defaults to false.
 - **max_retries** (*Optional*): Allow the component to retry if there was a network error when transmitting data
-- **retry_queue_limit** (*Optional*): If retry enabled, specify how much calls are allowed to be queued for retry.
 - **default_measurement** (*Optional*): Measurement name to use when an entity doesn't have a unit. Defaults to entity id.
 - **override_measurement** (*Optional*): Measurement name to use instead of unit or default measurement. This will store all data points in a single measurement.
 - **component_config**, **component_config_domain**, **component_config_glob** (*Optional*): These attributes contains component-specific override values. See [Customizing devices and services](https://home-assistant.io/getting-started/customizing-devices/) for format.

diff --git a/source/_components/knx.markdown b/source/_components/knx.markdown
@@ -31,6 +31,7 @@ There is currently support for the following device types within Home Assistant:
 - [Light](/components/light.knx)
 - [Thermostat](/components/climate.knx)
 - [Notify](/components/notify.knx)
+- [Scene](/components/scene.knx)
 
 ### {% linkable_title Configuration %}
 
@@ -83,7 +84,6 @@ knx:
 - **fire_event** (*Optional*): If set to True, platform will write all received KNX messages to event bus
 - **fire_event_filter** (*Optional*): If `fire_event` is set `fire_event_filter` has to be specified. `fire_event_filter` defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HOme Assistant event bus. 
 - **state_updater** (*Optional*): The component will collect the current state of each configured device from the KNX bus to display it correctly within Home-Assistant. Set this option to False to prevent this behavior.
-- **time_address** (*Optional*): Broadcast current local time to KNX bus with configured group address.
 
 ### {% linkable_title Services %}
 
@@ -98,6 +98,27 @@ Service Data: {"address": "1/0/15", "payload": 0}
 * **address**: KNX group address
 * **payload**: Payload, either an integer or an array of integers
 
+### {% linkable_title Exposing sensor values or time to knx bus %}
+
+KNX component is able to expose time or sensor values to KNX bus. The component will broadcast any change of the exposed value to the KNX bus and answer read requests to the specified group address:
+
+```yaml
+# Example configuration.yaml entry
+knx:
+    expose::
+        - type: 'temperature'
+          entity_id: 'sensor.owm_temperature'
+          address: '0/0/2'
+        - type: 'time'
+          address: '0/0/1'
+        - type: 'datetime'
+          address: '0/0/23'
+```
+
+* **type**: Type of the exposed value. Either time or datetime or any supported type of [KNX Sensor](/components/sensor.knx/) (e.g. "temperature" or "humidity").
+* **entity_id**: Entity id of the HASS component to be exposed. Not necessarry for types time and datetime.
+* **address**: KNX group address.
+
 
 ### {% linkable_title Known issues %}
 

diff --git a/source/_components/light.template.markdown b/source/_components/light.template.markdown
@@ -51,6 +51,10 @@ light:
         description: Name to use in the frontend.
         required: false
         type: string
+      entity_id:
+        description: A list of entity IDs so the light only reacts to state changes of these entities. This can be used if the automatic analysis fails to find all relevant entities.
+        required: false
+        type: [string, list]
       value_template:
         description: Defines a template to get the state of the light.
         required: false