home-assistant · balloob · Jan 27, 2018 · Jan 13, 2018 · Jan 14, 2018 · Jan 14, 2018
diff --git a/.ruby-version b/.ruby-version
@@ -1 +1 @@
-2.4.1
+2.4.1
diff --git a/_config.yml b/_config.yml
@@ -139,12 +139,12 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 61
-current_patch_version: 1
-date_released: 2018-01-16
+current_minor_version: 62
+current_patch_version: 0
+date_released: 2018-01-27
 
 # 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-0611---january-16"
+patch_version_notes: "#"
 # Minor release (Example #release-0431---april-25):
diff --git a/source/_addons/git_pull.markdown b/source/_addons/git_pull.markdown
@@ -36,6 +36,8 @@ Load and update configuration files for Home Assistant from a GIT repository.
 - **auto_restart** (*Optional*): Make a restart of Home-Assistant if the config have change and is valid.
 - **repeat/active** (*Optional*): Pull periodic for GIT updates.
 - **repeat/interval** (*Optional*): Pull all x seconds and look for changes.
+- **deployment_user** (*Optional*): Username to use when authenticating to a repo with a username and password.
+- **deployment_password** (*Optional*): Password to use when authenticating to a repo.  Ignored if deployment_user is not set.
 - **deployment_key** (*Optional*): A private SSH key that will be used for communication during git operations. This key is mandatory for ssh-accessed repositories, which are the ones with the following pattern: `<user>@<host>:<repository path>`.
 - **deployment_key_protocol** (*Optional*): The key protocol. Default is "rsa". Valid protocols are:
 

diff --git a/source/_components/alexa.markdown b/source/_components/alexa.markdown
@@ -21,6 +21,7 @@ There are a few ways that you can use Amazon Echo and Home Assistant together.
 
 - [Build custom commands to use](#i-want-to-build-custom-commands-to-use-with-echo)
 - [Create a new Flash Briefing source](#flash-briefing-skills)
+- [Use the Smart Home API to control lights, etc](#smart-home)
 - Alternative: use the [Emulated Hue component][emulated-hue-component] to trick Alexa to thinking Home Assistant is a Philips Hue hub.
 
 Amazon has released [Echosim], a website that simulates the Alexa service in your browser. That way it is easy to test your skills without having access to a physical Amazon Echo.
@@ -332,6 +333,50 @@ Please refer to the [Amazon documentation][flash-briefing-api-docs] for more inf
       - Having passed all validations to reach this screen, you can now click on "< Back to All Skills" as your flash briefing is now available as in "Development" service.
 - To invoke your flash briefing, open the Alexa app on your phone or go to the [Alexa Settings Site][alexa-settings-site], open the "Skills" configuration section, select "Your Skills", scroll to the bottom, tap on the Flash Briefing Skill you just created, enable it, then manage Flash Briefing and adjust ordering as necessary.  Finally ask your Echo for your "news","flash briefing", or "briefing".
 
+
+## {% linkable_title Smart Home %}
+
+While the Skills API described above allows for arbitrary intents, all
+utterances must begin with "Alexa, tell $invocation_name ..."
+
+The [Emulated Hue component][emulated-hue-component] provides a simpler
+interface such as, "Alexa, turn on the kitchen light". However it has some
+limitations since everything looks like a light bulb.
+
+Amazon provides a Smart Home API for richer home automation control. It takes
+considerable effort to configure. The easy solution is to use
+[Home Assistant Cloud](/components/cloud/).
+
+If you don't want to use Home Assistant Cloud and are willing to do the
+integration work yourself, Home Assistant can expose an HTTP API which makes
+the integration work easier. Example configuration:
+
+```yaml
+alexa:
+  smart_home:
+    filter:
+      include_entities:
+        - light.kitchen
+        - light.kitchen_left
+      include_domains:
+        - switch
+      exclude_entities:
+        - switch.outside
+    entity_config:
+      light.kitchen:
+        name: Custom Name for Alexa
+        description: The light in the kitchen
+      switch.stairs:
+        display_categories: LIGHT
+```
+
+This exposes an HTTP POST endpoint at `http://your_hass_ip/api/alexa/smart_home`
+which accepts and returns messages conforming to the
+[Smart Home v3 payload](https://developer.amazon.com/docs/smarthome/smart-home-skill-api-message-reference.html).
+You must then create an Amazon developer account with an Alexa skill and Lambda
+function to integrate this endpoint. See
+[Haaska](https://github.com/auchter/haaska) for an example.
+
 [amazon-dev-console]: https://developer.amazon.com
 [flash-briefing-api]: https://developer.amazon.com/alexa-skills-kit/flash-briefing
 [flash-briefing-api-docs]: https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/flash-briefing-skill-api-feed-reference

diff --git a/source/_components/api.markdown b/source/_components/api.markdown
@@ -0,0 +1,25 @@
+---
+layout: page
+title: "API"
+description: "Instructions how to setup the RESTful API within Home Assistant."
+date: 2018-01-21 08:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: home-assistant.png
+ha_category: "Other"
+---
+
+The `api` component exposes a RESTful API and allows one to interact with a Home Assistant instance that is running headless. This component depends on the [`http` component](/components/http/).
+
+<p class='note warning'>
+It is HIGHLY recommended that you set the `api_password`, especially if you are planning to expose your installation to the internet.
+</p>
+
+```yaml
+# Example configuration.yaml entry
+api:
+```
+
+For details to use the API, please refer to the [REST API](/developers/rest_api/) or the [Python REST API documentation](/developers/python_api/) in the "Developer" section. 
diff --git a/source/_components/binary_sensor.ihc.markdown b/source/_components/binary_sensor.ihc.markdown
@@ -0,0 +1,69 @@
+---
+layout: page
+title: "IHC Binary Sensor"
+description: "Instructions how to integrate IHC Binary Sensors within Home Assistant."
+date: 2017-11-27 13:35
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: ihc.png
+ha_category: Binary Sensor
+ha_release: 0.62
+ha_iot_class: "Local Push"
+---
+
+Before you can use the IHC Binary Sensor platform, you must setup the [IHC Component](/components/ihc/)
+
+When auto setup is enabled the following products will be found in the IHC project and setup as binary sensors:
+
+* Dataline magnet contacts
+* Dataline Pir sensors
+* Dataline Pir sensors with twilight detection
+* Dataline Pir alarm sensor
+* Dataline smoke detector
+* Dataline gas detector
+* Dataline light sensor
+
+To manually configure IHC Binary Sensors insert this section in your configuration:
+
+```yaml
+binary_sensor:
+  - platform: ihc
+    binary_sensors:
+      - id: 12345
+        name: mysensor
+        type: opening
+        inverting: True
+      - id: 12346
+           ...
+```
+
+{% configuration %}
+binary_sensors:
+  description: List of binary sensors to setup manually.
+  required: false
+  type: map
+  keys:
+    id:
+      description: The IHC resource id.
+      required: true
+      type: int
+    inverting:
+      description: If True the sensor will be inverted.
+      required: false
+      type: bool
+      default: false
+    name:
+      description: The name of the component
+      required: false
+      type: string
+    type:
+      description: The binary sensor type. See [Home Assistant binary sensor](/components/binary_sensor/) for available types.
+      required: false
+      type: string
+{% endconfiguration %}
+
+The resource id should be an id of a boolean IHC resource.
+For more information about IHC resource ids see [Manual Setup](/components/ihc/#manual-setup)
+
diff --git a/source/_components/binary_sensor.workday.markdown b/source/_components/binary_sensor.workday.markdown
@@ -28,8 +28,8 @@ binary_sensor:
 Configuration variables:
 
 - **name** (*Optional*): A name for this sensor. Defaults to *Workday Sensor*
-- **country** (*Required*): Country code according to [holidays](https://pypi.python.org/pypi/holidays/0.8.1) notation.
-- **province** (*Optional*): Province code according to [holidays](https://pypi.python.org/pypi/holidays/0.8.1) notation. Defaults to None.
+- **country** (*Required*): Country code according to [holidays](https://pypi.python.org/pypi/holidays/0.9.3) notation.
+- **province** (*Optional*): Province code according to [holidays](https://pypi.python.org/pypi/holidays/0.9.3) notation. Defaults to None.
 - **workdays** (*Optional*): List of workdays. Defaults to `mon`, `tue`, `wed`, `thu`, `fri`.
 - **excludes** (*Optional*): List of workday excludes. Defaults to `sat`, `sun`, `holiday`.
 - **days_offset** (*Optional*): Set days offset. Defaults to `0`.

diff --git a/source/_components/camera.onvif.markdown b/source/_components/camera.onvif.markdown
@@ -31,6 +31,6 @@ Configuration variables:
 - **username** (*Optional*): The username for the camera.
 - **password** (*Optional*): The password for the camera.
 - **port** (*Optional*): The port for the camera. This defaults to 5000
-
+- **extra_arguments** (*Optional*): Extra options to pass to `ffmpeg`, e.g. image quality or video filter options. More details in [FFmpeg component](/components/ffmpeg).
 
 If you are running into trouble with this sensor, please refer to the [Troubleshooting section](/components/ffmpeg/#troubleshooting).
diff --git a/source/_components/camera.xeoma.markdown b/source/_components/camera.xeoma.markdown
@@ -0,0 +1,89 @@
+---
+layout: page
+title: "Xeoma Camera"
+description: "Instructions on how to integrate camera video feeds from a Xeoma server in Home Assistant"
+date: 2018-01-12 20:05
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: xeoma.png
+ha_category: Camera
+ha_iot_class: "Local Polling"
+ha_release: 0.62
+---
+
+
+The `Xeoma` camera platform allows you to view the video feeds from a [Xeoma](http://felenasoft.com/xeoma) video surveillance server.
+
+To enable Xeoma camera feeds, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+camera:
+  - platform: xeoma
+    host: http://localhost:10090
+```
+
+{% configuration %}
+host:
+  description: The URL of the Xeoma server's web interface.
+  required: true
+  type: string
+username:
+  description: The username used to access the Xeoma server's web interface.
+  required: false
+  type: string
+password:
+  description: The password used to access the Xeoma server's web interface.
+  required: false
+  type: string
+new_version:
+  description: Set to false if the Xeoma server version is 17.5 or earlier.
+  required: false
+  default: true
+  type: boolean
+cameras:
+  description: List of customizations for individual Xeoma cameras.
+  required: false
+  type: list
+  keys:
+    image_name: 
+      description: The name of the JPEG image for this camera as configured in Xeoma (without .jpg extension).
+      required: true
+      type: string
+    name:
+      description: The name to display in the frontend for this camera.
+      required: false
+      default: The `image_name` for this camera.
+      type: string
+    hide:
+      description: Don't show this camera in Home Assistant.
+      required: false
+      default: false
+      type: boolean
+{% endconfiguration %}
+
+## {% linkable_title Full examples %}
+
+```yaml
+# Example configuration.yaml entry
+camera:
+  - platform: xeoma
+    host: http://localhost:10090
+    username: user
+    password: secretpassword
+    new_version: false
+    cameras:
+      - image_name: front_porch
+        name: Front Porch
+      - image_name: back_patio
+        hide: true
+```
+
+To use this platform, you must have the Xeoma Web Server module enabled in at least one of your camera chains.
+
+This platform will parse the Xeoma web interface to find all enabled cameras and add them all to Home Assistant. You can 
+hide individual cameras using the platform configuration.
+
+The `image_name` configuration value for each camera should match the name supplied to the Xeoma Web Server configuration (under _Path to access images_) with the _.jpg_ extension removed.
diff --git a/source/_components/climate.daikin.markdown b/source/_components/climate.daikin.markdown
@@ -17,16 +17,18 @@ ha_iot_class: "Local Polling"
 The `daikin` climate platform integrates Daikin air conditioning systems into Home Assistant, enabling control of setting the following parameters:
 
 - **mode** (cool, heat, dry, fan only or auto)
-- **fan speed**
+- **fan speed** (on supported models)
 - **target temperature**
 - **swing mode** (on supported models)
 
 Current temperature is displayed.
 
 <p class='note warning'>
-Please note, the `daikin` platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant
+Please note, the `daikin` platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant. BRP069A42 does not support setting of fan speed or fan swing mode.
 </p>
 
+The platform has been integrated with discovery so all your Daikin AC's climate devices can be automatically discovered.
+
 To enable the platform, add the following lines to your `configuration.yaml` file:
 
 ```yaml

diff --git a/source/_components/climate.generic_thermostat.markdown b/source/_components/climate.generic_thermostat.markdown
@@ -39,7 +39,7 @@ Configuration variables:
 - **hot_tolerance** (*Optional*): Set a minimum amount of difference between the temperature read by the sensor specified in the *target_sensor* option and the target temperature that must change prior to being switched off. For example, if the target temperature is 25 and the tolerance is 0.5 the heater will stop when the sensor equals or goes above 25.5.
 - **keep_alive** (*Optional*): Set a keep-alive interval. If set, the switch specified in the *heater* option will be triggered every time the interval elapses. Use with heaters and A/C units that shut off if they don't receive a signal from their remote for a while. Use also with switches that might lose state. The keep-alive call is done with the current valid climate component state (either on or off).
 - **initial_operation_mode** (*Optional*): Set the initial operation mode. Valid values are `off` or `auto`. Value has to be double quoted. If this parameter is not set, it is preferable to set a *keep_alive* value. This is helpful to align any discrepancies between *generic_thermostat* and *heater* state.
-- **away_temp** (*Optional*): Set the temperature used by "away_mode" (default: 16). Please specify when using `ac_mode: True` to a higher value.
+- **away_temp** (*Optional*): Set the temperature used by "away_mode". If this is not specified, away_mode feature will not get activated.
 
 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:`.