Skip to content

Commit 9f18e9c

Browse files
balloobballoob
authored
Merge pull request home-assistant#2388 from home-assistant/release-0-42
0.42
2 parents 5455519 + f0b5f37 commit 9f18e9c

40 files changed

+1508
-67
lines changed

‎.gitignore

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,3 +11,5 @@ source/stylesheets/screen.css
1111
vendor
1212
node_modules
1313
source/.jekyll-metadata
14+
*.iml
15+
.idea/

‎_config.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -138,10 +138,10 @@ social:
138138

139139
# Home Assistant release details
140140
current_major_version: 0
141-
current_minor_version: 41
141+
current_minor_version: 42
142142
current_patch_version: 0
143-
date_released: 2017-03-25
143+
date_released: 2017-04-08
144144

145145
# Either # or the anchor link to latest release notes in the blog post.
146146
# Must be prefixed with a # and have double quotes around it.
147-
#patch_version_notes: "#release-0411---march-xx"
147+
patch_version_notes: "#"

‎source/_components/alarm_control_panel.totalconnect.markdown

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
layout: page
3+
title: "Honeywell TotalConnect Alarm Control Panel"
4+
description: "Instructions how to integrate TotalConnect alarms into Home Assistant."
5+
date: 2017-04-02 22:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: honeywell-tc.png
11+
ha_category: Alarm
12+
ha_release: 0.42
13+
---
14+
15+
The `totalconnect` platform provides connectivity with the Honeywell TotalConnect alarm systems used by many alarm companies
16+
17+
To enable this, add the following lines to your `configuration.yaml`:
18+
19+
```yaml
20+
# Example configuration.yaml entry
21+
alarm_control_panel:
22+
platform: totalconnect
23+
username: YOUR_USERNAME
24+
password: YOUR_PASSWORD
25+
```
26+
27+
Configuration variables:
28+
- **name** (*Optional*): Name of device in HomeAssistant
29+
- **username** (*Required*): Username used to sign into the TotalConnect app/web client.
30+
- **password** (*Required*): Password used to sign into the TotalConnect app/web client.
31+

‎source/_components/binary_sensor.hikvision.markdown

Lines changed: 33 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,9 @@ ha_release: 0.35
1313
ha_iot_class: "Local Push"
1414
---
1515

16-
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.
16+
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.
1717

18-
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.
18+
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.
1919

2020
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:
2121

@@ -24,7 +24,16 @@ binary_sensor.front_porch_motion
2424
binary_sensor.front_port_line_crossing
2525
```
2626

27-
This platform should work with all Hikvision cameras, and has been confirmed to work with the following models:
27+
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:
28+
29+
```
30+
binary_sensor.home_motion_1
31+
binary_sensor.home_motion_2
32+
binary_sensor.home_line_crossing_1
33+
binary_sensor.home_line_crossing_2
34+
```
35+
36+
This platform should work with all Hikvision cameras and nvrs, and has been confirmed to work with the following models:
2837
- DS-2CD3132-I
2938
- DS-2CD2232-I5
3039
- DS-2CD2032-I
@@ -55,7 +64,6 @@ Configuration options for a Hikvision Sensor:
5564
5665
Supported sensor/event types are:
5766
- Motion
58-
- IO Trigger
5967
- Line Crossing
6068
- Field Detection
6169
- Video Loss
@@ -70,9 +78,27 @@ Supported sensor/event types are:
7078
- Bad Video
7179
- PIR Alarm
7280
- Face Detection
81+
- Scene Change Detection
82+
7383
84+
Example of a configuration in your `configuration.yaml` that utilizes the customize options for a camera:
85+
86+
```yaml
87+
binary_sensor:
88+
platform: hikvision
89+
host: 192.168.X.X
90+
port: 80
91+
ssl: False
92+
username: user
93+
password: pass
94+
customize:
95+
motion:
96+
delay: 30
97+
line_crossing:
98+
ignored: True
99+
```
74100

75-
Example of a configuration in your `configuration.yaml` that utilizes the customize options:
101+
Example of a configuration in your `configuration.yaml` that utilizes the customize options for a nvr:
76102

77103
```yaml
78104
binary_sensor:
@@ -83,8 +109,8 @@ binary_sensor:
83109
username: user
84110
password: pass
85111
customize:
86-
sensor_name_1:
112+
motion_1:
87113
delay: 30
88-
sensor_name_2:
114+
field_detection_2:
89115
ignored: True
90116
```

‎source/_components/binary_sensor.ring.markdown

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
layout: page
3+
title: "Ring Binary Sensor"
4+
description: "Instructions on how to integrate your Ring.com devices within Home Assistant."
5+
date: 2017-04-01 10:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: ring.png
11+
ha_category: Binary Sensor
12+
ha_release: 0.42
13+
---
14+
15+
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).
16+
17+
Once you have enabled the [Ring component](/components/ring), add the following to your `configuration.yaml` file:
18+
19+
```yaml
20+
# Example configuration.yaml entry
21+
binary_sensor:
22+
- platform: ring
23+
monitored_conditions:
24+
- ding
25+
- motion
26+
```
27+
28+
Configuration variables:
29+
30+
- **monitored_conditions** array (*Required*): Conditions to display in the frontend. The following conditions can be monitored.
31+
- **ding**: Return a boolean value when the doorbell button was pressed.
32+
- **motion**: Return a boolean value when a moviment was detected by the Ring doorbell.
33+
34+
Currently only doorbells are supported by this sensor.

‎source/_components/binary_sensor.workday.markdown

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ ha_release: 0.41
1515

1616
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.
1717

18+
To enable the `workday` sensor in your installation, add the following to your `configuration.yaml` file:
19+
1820
```yaml
1921
# Example configuation.yaml entry
2022
binary_sensor:
@@ -32,8 +34,8 @@ Configuration variables:
3234
3335
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.
3436

35-
3637
Example usage for automation:
38+
3739
```yaml
3840
automation:
3941
alias: Turn on heater on workdays

‎source/_components/calendar.google.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ From this we will end up with the binary sensors `calendar.test_unimportant` and
9595

9696
But what if you only wanted it to toggle based on all events? Just leave out the *search* parameter.
9797

98-
**Note**: If you use a `#` sign for search then wrap it up. It's better to be safe!
98+
**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.
9999

100100

101101
### {% linkable_title Sensor attributes %}

‎source/_components/climate.honeywell.markdown

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,8 @@ Configuration variables:
3131
3232
- **username** (*Required*): The username of an user with access.
3333
- **password** (*Required*): The password for your given admin account.
34-
- **away_temperature** (*Optional*): Heating setpoint when away mode is on. If omitted it defaults to 16.0 deg C.
3534
- **region** (*Optional*): Region identifier (either 'eu' or 'us'). Defaults to 'eu' if not provided.
3635
- **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.
36+
- **away_temperature** (*Optional*) (*only for eu region*): Heating setpoint when away mode is on. If omitted it defaults to 16.0 deg C.
37+
- **cool_away_temperature** (*Optional*) (*only for us region*): Cooling setpoint when away mode is on. If omitted it defaults to 30.0 deg C.
38+
- **heat_away_temperature** (*Optional*) (*only for us region*): Heating setpoint when away mode is on. If omitted it defaults to 16.0 deg C.

‎source/_components/ha.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
layout: page
3-
title: "Home Assistant 0.41"
3+
title: "Home Assistant 0.42"
44
description: ""
55
date: 2016-12-16 17:00
66
sidebar: true
@@ -9,7 +9,7 @@ sharing: true
99
footer: true
1010
logo: home-assistant.png
1111
ha_category: Other
12-
ha_release: 0.41
12+
ha_release: 0.42
1313
---
1414

1515
Details about the latest release can always be found at:

‎source/_components/light.limitlessled.markdown

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -35,10 +35,12 @@ light:
3535
type: rgbw
3636
name: Bathroom
3737
- host: 192.168.1.11
38-
bridge_led: True
3938
groups:
4039
- number: 1
4140
name: Living Room & Hall
41+
- number: 1
42+
type: bridge-led
43+
name: Bridge Light
4244
```
4345
4446
Configuration variables:
@@ -47,11 +49,10 @@ Configuration variables:
4749
- **host** (*Required*): IP address of the device, eg. `192.168.1.32`
4850
- **version** (*Optional*): Bridge version (default is `6`). Don't use if you aren't sure.
4951
- **port** (*Optional*): Bridge port. Defaults to 5987.
50-
- **bridge_led** (*Optional*): If True, the bridge led can be controlled. (Only supported for newer bridges with integrated led)
5152
- **groups** array (*Required*): The list of available groups.
52-
- **number** (*Required*): Group number (`1`-`4`). Corresponds to the group number on the remote.
53+
- **number** (*Required*): Group number (`1`-`4`). Corresponds to the group number on the remote. These numbers may overlap only if the type is different.
5354
- **name** (*Required*): Any name you'd like. Must be unique among all configured groups.
54-
- **type** (*Optional*): Type of group. Choose either `rgbww`, `rgbw` or `white`. `rgbw` is the default if you don't specify this entry.
55+
- **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.
5556

5657
### {% linkable_title Properties %}
5758

‎source/_components/light.rflink.markdown

Lines changed: 2 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -18,17 +18,6 @@ First you have to set up your [rflink hub](/components/rflink/).
1818

1919
After configuring the RFLink hub lights will be automatically discovered and added.
2020

21-
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.
22-
23-
For example:
24-
25-
```yaml
26-
# Example configuration.yaml entry
27-
sensor:
28-
platform: rflink
29-
new_devices_group: "New Rflink Lights"
30-
```
31-
3221
RFLink switch/light ID's are composed of: protocol, id, switch. For example: `newkaku_0000c6c2_1`.
3322

3423
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:
4938
5039
Configuration variables:
5140
41+
- **automatic_add** (*Optional*): Automatically add new/unconfigured devices to HA if detected (default: True).
5242
- **devices** (*Optional*): A list of devices with their name to use in the frontend.
53-
- **new_devices_group** (*Optional*): Create group to add new/unknown devices to.
5443
- **device_defaults**: (*Optional*)
5544
- **fire_event** (*Optional*): Set default `fire_event` for Rflink switch devices (see below).
5645
- **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
10594

10695
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:
10796

108-
- Configure a `new_devices_group` for lights and optionally add it to a different `view`.
97+
- Disable automatically adding of unconfigured new sensors (set `automatic_add` to `false`).
10998
- Hide unwanted devices using [customizations](/getting-started/customizing-devices/)
11099
- [Ignore devices on a platform level](/components/rflink/#ignoring-devices)
111100

‎source/_components/lock.lockitron.markdown

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
layout: page
3+
title: "Lockitron Lock"
4+
description: "Instructions how to integrate Lockitron locks into Home Assistant."
5+
date: 2017-03-24 00:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: lockitron.png
11+
ha_category: Lock
12+
ha_iot_class: "Cloud Polling"
13+
ha_release: "0.42"
14+
---
15+
16+
The `lockitron` platform allows you to control your [Lockitron](https://lockitron.com/) lock from within Home Assistant.
17+
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.
18+
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).
19+
20+
```yaml
21+
lock:
22+
- platform: lockitron
23+
access_token: asdf
24+
id: fdsa
25+
```
26+
27+
Configuration variables:
28+
29+
- **access_token** (*Required*): The usernThe security token provided by Lockitron to lock and unlock your lock.
30+
- **id** (*Required*): The lock id given by Lockitron (should be a GUID).
31+

‎source/_components/media_player.emby.markdown

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ footer: true
1010
logo: emby.png
1111
ha_category: Media Player
1212
ha_release: "0.32"
13-
ha_iot_class: "Local Polling"
13+
ha_iot_class: "Local Push"
1414
---
1515

1616

@@ -28,7 +28,8 @@ media_player:
2828
2929
Configuration variables:
3030
31-
- **host** (*Required*): The host name or address of the device that is running Emby.
31+
- **host** (*Optional*): The host name or address of the device that is running Emby. Defaults to ```localhost```.
3232
- **api_key** (*Required*): The api-key you would like home-assistant to use to authenticate.
33-
- **ssl** (*Optional*): True if you want to connect with https. Be sure to set the port also.
34-
- **port** (*Optional*): The port number. Defaults to 8096.
33+
- **ssl** (*Optional*): True if you want to connect with https/wss. Your SSL certificate must be valid. Default is False.
34+
- **port** (*Optional*): The port number. Defaults to 8096 with SSL set to False and 8920 with SSL set to True.
35+
- **auto_hide** (*Optional*): True if you want to automatically hide devices that are unavailable from the Home Assistant Interface. Defaults to False.

‎source/_components/media_player.markdown

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,15 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`,
3434
| `entity_id` | yes | Target a specific media player. Defaults to all. |
3535
| `volume_level` | no | Float for volume level |
3636

37+
#### {% linkable_title Service `media_player/volume_transition` %}
38+
39+
| Service data attribute | Optional | Description |
40+
|------------------------|----------|--------------------------------------------------|
41+
| `entity_id` | yes | Target a specific media player. Defaults to all. |
42+
| `volume_level` | no | Float for volume level |
43+
| `transition` | no | Integer for transition time in seconds |
44+
45+
3746
#### {% linkable_title Service `media_player/media_seek` %}
3847

3948
| Service data attribute | Optional | Description |

‎source/_components/rflink.markdown

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -121,3 +121,27 @@ If you find a device is recognized differently, with different protocols or the
121121
- The platform implementions take care of creating new devices (if enabled) for unsees incoming packet id's.
122122
- 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.
123123

124+
### {% linkable_title Debug logging %}
125+
126+
For debugging purposes or context when investigating issues you can enable debug logging for Rflink with the following config snippet:
127+
128+
```yaml
129+
logger:
130+
default: error
131+
logs:
132+
rflink: debug
133+
homeassistant.components.rflink: debug
134+
```
135+
136+
This will give you output looking like this:
137+
138+
```
139+
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: 20;00;Nod
140+
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: o RadioFrequencyLink - R
141+
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: FLink Gateway V1.1 - R45
142+
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: ;
143+
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] got packet: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R45;
144+
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'}
145+
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'}
146+
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'}
147+
```

0 commit comments

Comments
 (0)