home-assistant · balloob · Apr 8, 2017 · Mar 23, 2017 · Mar 24, 2017 · Mar 24, 2017
diff --git a/.gitignore b/.gitignore
@@ -11,3 +11,5 @@ source/stylesheets/screen.css
 vendor
 node_modules
 source/.jekyll-metadata
+*.iml
+.idea/
diff --git a/_config.yml b/_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: "#"
diff --git a/source/_components/alarm_control_panel.totalconnect.markdown b/source/_components/alarm_control_panel.totalconnect.markdown
@@ -0,0 +1,31 @@
+---
+layout: page
+title: "Honeywell TotalConnect Alarm Control Panel"
+description: "Instructions how to integrate TotalConnect alarms into Home Assistant."
+date: 2017-04-02 22:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: honeywell-tc.png
+ha_category: Alarm
+ha_release: 0.42
+---
+
+The `totalconnect` platform provides connectivity with the Honeywell TotalConnect alarm systems used by many alarm companies
+
+To enable this, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+alarm_control_panel:
+  platform: totalconnect
+  username: YOUR_USERNAME
+  password: YOUR_PASSWORD
+```
+
+Configuration variables:
+- **name** (*Optional*): Name of device in HomeAssistant
+- **username** (*Required*): Username used to sign into the TotalConnect app/web client.
+- **password** (*Required*): Password used to sign into the TotalConnect app/web client.
+
diff --git a/source/_components/binary_sensor.hikvision.markdown b/source/_components/binary_sensor.hikvision.markdown
@@ -13,9 +13,9 @@ ha_release: 0.35
 ha_iot_class: "Local Push"
 ---
 
-The Hikvision Binary Sensor is a platform that parses the event stream of a [Hikvision IP Camera](http://www.hikvision.com/) and presents the camera events to Home Assistant as binary sensors with either an "off" or "on" state.
+The Hikvision Binary Sensor is a platform that parses the event stream of a [Hikvision IP Camera or NVR](http://www.hikvision.com/) and presents the camera/nvr events to Home Assistant as binary sensors with either an "off" or "on" state.
 
-The platform will automatically add all sensors to Home Assistant that are configured within the camera interface to "Notify the surveillance center" as a trigger.  If you would like to hide a sensor type you can do so by either unchecking "Notify the surveillance center" in the camera configuration or by using the "ignored" customize option detailed below.
+The platform will automatically add all sensors to Home Assistant that are configured within the camera/nvr interface to "Notify the surveillance center" as a trigger.  If you would like to hide a sensor type you can do so by either unchecking "Notify the surveillance center" in the camera configuration or by using the "ignored" customize option detailed below.
 
 For example, if you configure a camera with the name "Front Porch" that has motion detection and line crossing events enabled to notify the surveillance center the following binary sensors will be added to Home Assistant:
 
@@ -24,7 +24,16 @@ binary_sensor.front_porch_motion
 binary_sensor.front_port_line_crossing
 ```
 
-This platform should work with all Hikvision cameras, and has been confirmed to work with the following models:
+When used with a NVR device the sensors will be appeneded with the channel number they represent.  For example, if you configure an NVR with the name "Home" that supports 2 cameras with motion detection and line crossing events enabled to notify the surveillance center the following binary sensors will be added to Home Assistant:
+
+```
+binary_sensor.home_motion_1
+binary_sensor.home_motion_2
+binary_sensor.home_line_crossing_1
+binary_sensor.home_line_crossing_2
+```
+
+This platform should work with all Hikvision cameras and nvrs, and has been confirmed to work with the following models:
 - DS-2CD3132-I
 - DS-2CD2232-I5
 - DS-2CD2032-I
@@ -55,7 +64,6 @@ Configuration options for a Hikvision Sensor:
 
 Supported sensor/event types are:
 - Motion
-- IO Trigger
 - Line Crossing
 - Field Detection
 - Video Loss
@@ -70,9 +78,27 @@ Supported sensor/event types are:
 - Bad Video
 - PIR Alarm
 - Face Detection
+- Scene Change Detection
+
 
+Example of a configuration in your `configuration.yaml` that utilizes the customize options for a camera:
+
+```yaml
+binary_sensor:
+  platform: hikvision
+  host: 192.168.X.X
+  port: 80
+  ssl: False
+  username: user
+  password: pass
+  customize:
+    motion:
+      delay: 30
+    line_crossing:
+      ignored: True
+```
 
-Example of a configuration in your `configuration.yaml` that utilizes the customize options:
+Example of a configuration in your `configuration.yaml` that utilizes the customize options for a nvr:
 
 ```yaml
 binary_sensor:
@@ -83,8 +109,8 @@ binary_sensor:
   username: user
   password: pass
   customize:
-    sensor_name_1:
+    motion_1:
       delay: 30
-    sensor_name_2:
+    field_detection_2:
       ignored: True
 ```
diff --git a/source/_components/binary_sensor.ring.markdown b/source/_components/binary_sensor.ring.markdown
@@ -0,0 +1,34 @@
+---
+layout: page
+title: "Ring Binary Sensor"
+description: "Instructions on how to integrate your Ring.com devices within Home Assistant."
+date: 2017-04-01 10:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: ring.png
+ha_category: Binary Sensor
+ha_release: 0.42
+---
+
+To get your [Ring.com](https://ring.com/) binary sensors working within Home Assistant, please follow the instructions for the general [Ring component](/components/ring).
+
+Once you have enabled the [Ring component](/components/ring), add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+binary_sensor:
+  - platform: ring
+    monitored_conditions:
+      - ding
+      - motion
+```
+
+Configuration variables:
+
+- **monitored_conditions** array (*Required*): Conditions to display in the frontend. The following conditions can be monitored.
+  - **ding**: Return a boolean value when the doorbell button was pressed.
+  - **motion**: Return a boolean value when a moviment was detected by the Ring doorbell.
+
+Currently only doorbells are supported by this sensor.
diff --git a/source/_components/binary_sensor.workday.markdown b/source/_components/binary_sensor.workday.markdown
@@ -15,6 +15,8 @@ ha_release: 0.41
 
 The `workday` binary sensor indicates, whether the current day is a workday or not. It allows specifying, which days of the week counts as workdays and also uses the python module [holidays](https://pypi.python.org/pypi/holidays) to incorporate information about region-specific public holidays.
 
+To enable the `workday` sensor in your installation, add the following to your `configuration.yaml` file:
+
 ```yaml
 # Example configuation.yaml entry
 binary_sensor:
@@ -32,8 +34,8 @@ Configuration variables:
 
 Days are specified as follows: `mon`, `tue`, `wed`, `thu`, `fri`, `sat`, `sun`. The keyword `holiday` is used for public holidays identified by the holidays module.
 
-
 Example usage for automation:
+
 ```yaml
 automation:
   alias: Turn on heater on workdays

diff --git a/source/_components/calendar.google.markdown b/source/_components/calendar.google.markdown
@@ -95,7 +95,7 @@ From this we will end up with the binary sensors `calendar.test_unimportant` and
 
 But what if you only wanted it to toggle based on all events? Just leave out the *search* parameter.
 
-**Note**: If you use a `#` sign for search then wrap it up. It's better to be safe!
+**Note**: If you use a `#` sign for `search` then wrap the whole search term in quotes. Otherwise everything following the hash sign would be considered a YAML comment.
 
 
 ### {% linkable_title Sensor attributes %}

diff --git a/source/_components/climate.honeywell.markdown b/source/_components/climate.honeywell.markdown
@@ -31,6 +31,8 @@ Configuration variables:
 
 - **username** (*Required*): The username of an user with access.
 - **password** (*Required*): The password for your given admin account.
-- **away_temperature** (*Optional*): Heating setpoint when away mode is on. If omitted it defaults to 16.0 deg C.
 - **region** (*Optional*): Region identifier (either 'eu' or 'us'). Defaults to 'eu' if not provided.
 - **scan_interval**(*Optional*): Scan interval is expressed in seconds. Recommended value of 600 seconds. Default value is 120 seconds. Omitting scan_interval may result in too-frequent polling and cause you to rate-limited by Honeywell.
+- **away_temperature** (*Optional*) (*only for eu region*): Heating setpoint when away mode is on. If omitted it defaults to 16.0 deg C.
+- **cool_away_temperature** (*Optional*) (*only for us region*): Cooling setpoint when away mode is on. If omitted it defaults to 30.0 deg C.
+- **heat_away_temperature** (*Optional*) (*only for us region*): Heating setpoint when away mode is on. If omitted it defaults to 16.0 deg C.
diff --git a/source/_components/ha.markdown b/source/_components/ha.markdown
@@ -1,6 +1,6 @@
 ---
 layout: page
-title: "Home Assistant 0.41"
+title: "Home Assistant 0.42"
 description: ""
 date: 2016-12-16 17:00
 sidebar: true
@@ -9,7 +9,7 @@ sharing: true
 footer: true
 logo: home-assistant.png
 ha_category: Other
-ha_release: 0.41
+ha_release: 0.42
 ---
 
 Details about the latest release can always be found at:

diff --git a/source/_components/light.limitlessled.markdown b/source/_components/light.limitlessled.markdown
@@ -35,10 +35,12 @@ light:
         type: rgbw
         name: Bathroom
     - host: 192.168.1.11
-      bridge_led: True
       groups:
       - number: 1
         name: Living Room & Hall
+      - number: 1
+        type: bridge-led
+        name: Bridge Light
 ```
 
 Configuration variables:
@@ -47,11 +49,10 @@ Configuration variables:
   - **host** (*Required*): IP address of the device, eg. `192.168.1.32`
   - **version** (*Optional*): Bridge version (default is `6`). Don't use if you aren't sure.
   - **port** (*Optional*): Bridge port. Defaults to 5987.
-  - **bridge_led** (*Optional*): If True, the bridge led can be controlled. (Only supported for newer bridges with integrated led)
   - **groups** array (*Required*): The list of available groups.
-    - **number** (*Required*): Group number (`1`-`4`). Corresponds to the group number on the remote.
+    - **number** (*Required*): Group number (`1`-`4`). Corresponds to the group number on the remote. These numbers may overlap only if the type is different.
     - **name** (*Required*): Any name you'd like. Must be unique among all configured groups.
-    - **type** (*Optional*): Type of group. Choose either `rgbww`, `rgbw` or `white`. `rgbw` is the default if you don't specify this entry.
+    - **type** (*Optional*): Type of group. Choose either `rgbww`, `rgbw`, `white`, or `bridge-led`. `rgbw` is the default if you don't specify this entry. Use `bridge-led` to control the built-in LED of newer WiFi bridges.
 
 ### {% linkable_title Properties %}
 

diff --git a/source/_components/light.rflink.markdown b/source/_components/light.rflink.markdown
@@ -18,17 +18,6 @@ First you have to set up your [rflink hub](/components/rflink/).
 
 After configuring the RFLink hub lights will be automatically discovered and added.
 
-New/unknown lights can be assigned to a default group automatically by specifying the `new_devices_group` option with a group name. If the group doesn't exist it will be created.
-
-For example:
-
-```yaml
-# Example configuration.yaml entry
-sensor:
-  platform: rflink
-  new_devices_group: "New Rflink Lights"
-```
-
 RFLink switch/light ID's are composed of: protocol, id, switch. For example: `newkaku_0000c6c2_1`.
 
 Once the ID of a light is known it can be used to configure the light in HA, for example to add it to a different group, hide it or configure a nice name.
@@ -49,8 +38,8 @@ light:
 
 Configuration variables:
 
+- **automatic_add** (*Optional*): Automatically add new/unconfigured devices to HA if detected (default: True).
 - **devices**  (*Optional*): A list of devices with their name to use in the frontend.
-- **new_devices_group** (*Optional*): Create group to add new/unknown devices to.
 - **device_defaults**: (*Optional*)
   - **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).
@@ -105,7 +94,7 @@ By default new lights are assigned the `switchable` type. Protocol supporting di
 
 Lights are added automatically when the RFLink gateway intercepts a wireless command in the ether. To prevent cluttering the frontend use any of these methods:
 
-- Configure a `new_devices_group` for lights and optionally add it to a different `view`.
+- Disable automatically adding of unconfigured new sensors (set `automatic_add` to `false`).
 - Hide unwanted devices using [customizations](/getting-started/customizing-devices/)
 - [Ignore devices on a platform level](/components/rflink/#ignoring-devices)
 

diff --git a/source/_components/lock.lockitron.markdown b/source/_components/lock.lockitron.markdown
@@ -0,0 +1,31 @@
+---
+layout: page
+title: "Lockitron Lock"
+description: "Instructions how to integrate Lockitron locks into Home Assistant."
+date: 2017-03-24 00:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: lockitron.png
+ha_category: Lock
+ha_iot_class: "Cloud Polling"
+ha_release: "0.42"
+---
+
+The `lockitron` platform allows you to control your [Lockitron](https://lockitron.com/) lock from within Home Assistant.
+In order to get the correct `access_token` and `id`, log on to their [developer page](https://api.lockitron.com/), create a new app, and get the access_token they give you.
+Then, call the retrieve all locks function on the page and get the id of your lock (make sure you get your lock's id and not the virtual lock they create for you).
+
+```yaml
+lock:
+  - platform: lockitron
+    access_token: asdf
+    id: fdsa
+```
+
+Configuration variables:
+
+- **access_token** (*Required*): The usernThe security token provided by Lockitron to lock and unlock your lock.
+- **id** (*Required*): The lock id given by Lockitron (should be a GUID).
+
diff --git a/source/_components/media_player.emby.markdown b/source/_components/media_player.emby.markdown
@@ -10,7 +10,7 @@ footer: true
 logo: emby.png
 ha_category: Media Player
 ha_release: "0.32"
-ha_iot_class: "Local Polling"
+ha_iot_class: "Local Push"
 ---
 
 
@@ -28,7 +28,8 @@ media_player:
 
 Configuration variables:
 
-- **host** (*Required*): The host name or address of the device that is running Emby.
+- **host** (*Optional*): The host name or address of the device that is running Emby. Defaults to ```localhost```.
 - **api_key** (*Required*): The api-key you would like home-assistant to use to authenticate.
-- **ssl** (*Optional*): True if you want to connect with https. Be sure to set the port also.
-- **port** (*Optional*): The port number. Defaults to 8096.
+- **ssl** (*Optional*): True if you want to connect with https/wss. Your SSL certificate must be valid. Default is False.
+- **port** (*Optional*): The port number. Defaults to 8096 with SSL set to False and 8920 with SSL set to True.
+- **auto_hide** (*Optional*): True if you want to automatically hide devices that are unavailable from the Home Assistant Interface. Defaults to False.
diff --git a/source/_components/media_player.markdown b/source/_components/media_player.markdown
@@ -34,6 +34,15 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`,
 | `entity_id`            |      yes | Target a specific media player. Defaults to all. |
 | `volume_level`         |       no | Float for volume level                         |
 
+#### {% linkable_title Service `media_player/volume_transition` %}
+
+| Service data attribute | Optional | Description                                      |
+|------------------------|----------|--------------------------------------------------|
+| `entity_id`            |      yes | Target a specific media player. Defaults to all. |
+| `volume_level`         |       no | Float for volume level                         |
+| `transition`           |       no | Integer for transition time in seconds           |
+
+
 #### {% linkable_title Service `media_player/media_seek` %}
 
 | Service data attribute | Optional | Description                                            |

diff --git a/source/_components/rflink.markdown b/source/_components/rflink.markdown
@@ -121,3 +121,27 @@ If you find a device is recognized differently, with different protocols or the
 - The platform implementions take care of creating new devices (if enabled) for unsees incoming packet id's.
 - Device entities take care of matching to the packet ID, interpreting and performing actions based on the packet contents. Common entitiy logic is maintained in this main component.
 
+### {% linkable_title Debug logging %}
+
+For debugging purposes or context when investigating issues you can enable debug logging for Rflink with the following config snippet:
+
+```yaml
+logger:
+  default: error
+  logs:
+    rflink: debug
+    homeassistant.components.rflink: debug
+```
+
+This will give you output looking like this:
+
+```
+17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: 20;00;Nod
+17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: o RadioFrequencyLink - R
+17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: FLink Gateway V1.1 - R45
+17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: ;
+17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] got packet: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R45;
+17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] decoded packet: {'firmware': 'RFLink Gateway', 'revision': '45', 'node': 'gateway', 'protocol': 'unknown', 'hardware': 'Nodo RadioFrequencyLink', 'version': '1.1'}
+17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] got event: {'version': '1.1', 'firmware': 'RFLink Gateway', 'revision': '45', 'hardware': 'Nodo RadioFrequencyLink', 'id': 'rflink'}
+17-03-07 20:12:05 DEBUG (MainThread) [homeassistant.components.rflink] event of type unknown: {'version': '1.1', 'firmware': 'RFLink Gateway', 'revision': '45', 'hardware': 'Nodo RadioFrequencyLink', 'id': 'rflink'}
+```
-Original file line number
+Diff line change
@@ Expand Up / @@ -11,3 +11,5 @@ source/stylesheets/screen.css @@
     vendor
     node_modules
     source/.jekyll-metadata
+    *.iml
+    .idea/