Skip to content

Commit 203aac6

Browse files
fabafffabaff
authored
Merge pull request home-assistant#2317 from home-assistant/release-0-41
0.41
2 parents 8f1095f + 5a876d6 commit 203aac6

27 files changed

+896
-49
lines changed

‎_config.yml

Lines changed: 4 additions & 4 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: 40
142-
current_patch_version: 2
143-
date_released: 2017-03-22
141+
current_minor_version: 41
142+
current_patch_version: 0
143+
date_released: 2017-03-25
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-0402---march-22"
147+
#patch_version_notes: "#release-0411---march-xx"

‎source/_components/android_ip_webcam.markdown

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,17 @@ To set it up, download [the IP Webcam app][app] and add the following informatio
2121
```yaml
2222
# Example configuration.yaml entry
2323
android_ip_webcam:
24+
<<<<<<< HEAD
25+
<<<<<<< HEAD
26+
- host: 192.168.1.10
27+
=======
28+
# This should be the ip of your phone
29+
=======
2430
# This should be the IP Address of the phone
31+
>>>>>>> origin/current
2532
- host: 192.168.1.10
2633
name: Entrance
34+
>>>>>>> current
2735
```
2836

2937
Configuration variables:
@@ -62,5 +70,8 @@ Settings:
6270
- torch
6371
- whitebalance_lock
6472
- video_recording
73+
<<<<<<< HEAD
74+
=======
6575

6676
[app]: https://play.google.com/store/apps/details?id=com.pas.webcam
77+
>>>>>>> current

‎source/_components/binary_sensor.workday.markdown

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
layout: page
3+
title: "Workday Binary Sensor"
4+
description: "Steps to configure the binary workday sensor."
5+
date: 2017-03-13 21:30
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: home-assistant.png
11+
ha_category: Binary Sensor
12+
ha_iot_class: "Local Polling"
13+
ha_release: 0.41
14+
---
15+
16+
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.
17+
18+
```yaml
19+
# Example configuation.yaml entry
20+
binary_sensor:
21+
- platform: workday
22+
country: DE
23+
province: BW
24+
```
25+
26+
Configuration variables:
27+
28+
- **country** (*Required*): Country code according to [holidays](https://pypi.python.org/pypi/holidays/0.8.1) notation.
29+
- **province** (*Optional*): Province code according to [holidays](https://pypi.python.org/pypi/holidays/0.8.1) notation (defaults to None).
30+
- **workdays** (*Optional*): List of workdays (defaults to mon, tue, wed, thu, fri).
31+
- **excludes** (*Optional*): List of workday excludes (defaults to sat, sun, holiday).
32+
33+
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.
34+
35+
36+
Example usage for automation:
37+
```yaml
38+
automation:
39+
alias: Turn on heater on workdays
40+
trigger:
41+
platform: time
42+
after: '08:00:00'
43+
condition:
44+
condition: state
45+
entity_id: 'binary_sensor.workday_sensor'
46+
state: 'off'
47+
action:
48+
service: switch.turn_on
49+
entity_id: switch.heater
50+
```

‎source/_components/camera.dispatcher.markdown

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
layout: page
3+
title: "Dispatcher IP Camera"
4+
description: "Instructions how to integrate internal dispatcher cameras within Home Assistant."
5+
date: 2017-03-08 00:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
ha_category: Camera
11+
logo: camcorder.png
12+
ha_release: 0.40
13+
ha_iot_class: "depends"
14+
---
15+
16+
<p class='note'>
17+
This platform is meant for developers only.
18+
</p>
19+
20+
The `dispatcher` camera platform allows developers to create virtual camera's.
21+
22+
You would normally not add this camera to your configuration directly but have it be discovered by one of the components that uses it.
23+
24+
```yaml
25+
# Example configuration.yaml entry
26+
camera:
27+
- platform: dispatcher
28+
signal: name_of_dispatcher_signal
29+
```
30+
31+
To update the image from another piece of code, run this from an async context:
32+
33+
```python
34+
from homeassistant.helpers.dispatcher import async_dispatcher_send
35+
36+
async_dispatcher_send(hass, 'name_of_dispatcher_signal', image_data)
37+
```
38+
39+
Configuration variables:
40+
- **signal** (*Required*): The signal name of dispatcher signal they send image data to this camera.
41+
- **name** (*Optional*): This parameter allows you to override the name of your camera.

‎source/_components/camera.synology.markdown

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ Configuration variables:
3131
- **url** (*Required*): The URL to your synology, including port.
3232
- **username** (*Required*): The username for accessing surveillance station.
3333
- **password** (*Required*): The password for accessing surveillance station.
34+
- **timeout** (*Optional*): The timeout in seconds used when connecting to the Surveillance Station. Defaults to 5.
3435
- **whitelist** (*Optional*): A list of which cameras you want to add, the names must be the same as in Surveillance Station. If omitted all cameras are added.
3536
- **verify_ssl** (*Optional*): True to require a valid certificate, False to disable certificate checking. Defaults to `True`.
3637

@@ -43,6 +44,7 @@ camera:
4344
url: https://192.168.1.120:5001
4445
username: USERNAME
4546
password: PASSWORD
47+
timeout: 15
4648
verify_ssl: False
4749
```
4850

‎source/_components/climate.tado.markdown

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
layout: page
3+
title: "Tado"
4+
description: "Instructions on how to integrate Tado thermostats with Home Assistant."
5+
date: 2017-03-20 12:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: tado.png
11+
ha_category: Climate
12+
ha_release: 0.41
13+
---
14+
15+
16+
The `tado` component platform is used as an interface to the my.tado.com website. It adds climate devices for every tado zone and sensors for some additional information of the zones.
17+
18+
To use your tado thermostats in your installation, add the following to your `configuration.yaml` file:
19+
20+
```yaml
21+
# Example configuration.yaml entry
22+
tado:
23+
username: YOUR_USERNAME
24+
password: YOUR_PASSWORD
25+
```
26+
27+
- **username** (*Required*): Username for my.tado.com.
28+
- **password** (*Required*): Password for my.tado.com.
29+
30+
The tado thermostats are internet connected thermostats. There exists an unofficial api at my.tado.com, which is used by theire website and now by this component.
31+
32+
It currently supports presenting the current temperature, the setting temperature and the current operation mode. Switching the mode is also supported. If no user is at home anymore, the devices are showing the away-state. Switching to away-mode is not supported.

‎source/_components/device_tracker.unifi.markdown

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ Configuration variables:
3131
- **port** (*Optional*): The port of your controller's web interface. Defaults to `8443`.
3232
- **username** (*Required*: The username of an user with administrative privileges, usually `admin`.
3333
- **password** (*Required*): The password for your given admin account.
34+
- **verify_ssl** (*Optional*): Verify the controllers SSL certificate. Defaults to True however can also be False or "path/to/custom_cert.pem".
3435
- **site_id** (*Optional*): Allows you to specify a `site_id` for device tracking. Defaults to `default`. Found in the URL of the controller (i.e. https://CONTROLLER:PORT/manage/site/SITE_ID/dashboard)
3536
- **verify_ssl** (*Optional*): Controls if the SSL certificate running on your Unifi webserver must be trusted by a known Certificate Authority on the server running Home Assistant. Defaults to 'True'.
3637

‎source/_components/device_tracker.volvooncall.markdown

Lines changed: 1 addition & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -13,21 +13,4 @@ ha_release: "0.30"
1313
---
1414

1515

16-
The `volvooncall` platform offers presence detection by retrieving your car's information from the [Volvo On Call](http://www.volvocars.com/intl/own/connectivity/volvo-on-call) cloud service.
17-
18-
To use Volvo On Call in your installation, add the following to your `configuration.yaml` file:
19-
20-
```yaml
21-
# Example configuration.yaml entry
22-
device_tracker:
23-
- platform: volvooncall
24-
username: username
25-
password: password
26-
```
27-
28-
Configuration variables:
29-
30-
- **username** (*Required*): The username associated with your Volvo On Call account.
31-
- **password** (*Required*): The password for your given Volvo On Call account.
32-
33-
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the cars to be tracked.
16+
Integrates Volvo on Call into Home Assistant. See the [main component](/components/volvooncall/) for configuration instructions.

‎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.39"
3+
title: "Home Assistant 0.41"
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.39
12+
ha_release: 0.41
1313
---
1414

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

‎source/_components/light.rflink.markdown

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -52,16 +52,19 @@ Configuration variables:
5252
- **devices** (*Optional*): A list of devices with their name to use in the frontend.
5353
- **new_devices_group** (*Optional*): Create group to add new/unknown devices to.
5454
- **device_defaults**: (*Optional*)
55-
- **fire_event_** (*Optional*): Set default `fire_event` for RFLink switch devices (see below).
56-
- **signal_repetitions** (*Optional*): Set default `signal_repetitions` for RFLink switch devices (see below).
55+
- **fire_event** (*Optional*): Set default `fire_event` for Rflink switch devices (see below).
56+
- **signal_repetitions** (*Optional*): Set default `signal_repetitions` for Rflink switch devices (see below).
5757

5858
Device configuration variables:
5959

60-
- **name** (*Optional*): Name for the device, defaults to RFLink ID.
61-
- **type** (*Optional*): Override automatically detected type of the light device, can be: switchable, dimmable or hybrid. See 'Light Types' below.
62-
- **aliasses** (*Optional*): Alternative RFLink ID's this device is known by.
63-
- **fire_event_** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False).
64-
- **signal_repetitions** (*Optional*): Repeat every RFLink command this number of times (default: 1)
60+
- **name** (*Optional*): Name for the device, defaults to Rflink ID.
61+
- **type** (*Optional*): Override automatically detected type of the light device, can be: switchable, dimmable, hybrid or toggle. See 'Light Types' below.
62+
- **aliasses** (*Optional*): Alternative Rflink ID's this device is known by.
63+
- **fire_event** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False).
64+
- **signal_repetitions** (*Optional*): Repeat every Rflink command this number of times (default: 1)
65+
- **fire_event_** (*Optional*): Set default `fire_event` for RFLink switch devices (see below).
66+
- **signal_repetitions** (*Optional*): Set default `signal_repetitions` for RFLink switch devices (see below).
67+
6568

6669
### {% linkable_title Light state %}
6770

@@ -90,6 +93,7 @@ Light devices can come in different forms. Some only switch on and off, other su
9093
- *Hybrid*: This type sends a `dim` followed by an a `on` command; and `off` commands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple `on` signals will cause dimmers to go into disco mode.
9194
- *Switchable*: Device type that sends only `on` and `off` commands. It work for both on/off and dimmable type switches. However dimmables might have issues with signal repetition (see above).
9295
- *Dimmable*: Sends only `dim` and `off` commands. This does not work on on/off type devices as they don't understand the `dim` command. For dimmers this does not cause issues with signal repetitions.
96+
- *Toggle*: Device type that sends only `on` commands to turn on or off the device. Some switches like for example Livolo light switches use the same 'on' command to switch on and switch off the lights. If the light is on and 'on' gets sent, the light will turn off and if the light is off and 'on' gets sent, the light will turn on. If the device has an unknown state, it will assume it is off by default.
9397

9498
By default new lights are assigned the `switchable` type. Protocol supporting dimming are assigned the `hybrid` type. Currently only `newkaku` protocol is detected as dimmable. Please refer to Device Support to get your dimmers supported.
9599

‎source/_components/media_player.kodi.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,11 +28,11 @@ media_player:
2828
2929
Configuration variables:
3030
31-
- **host** (*Required*): The host name or address of the device that is running XBMC/Kodi
31+
- **host** (*Required*): The host name or address of the device that is running XBMC/Kodi.
3232
- **port** (*Optional*): The HTTP port number. Defaults to 8080.
3333
- **tcp_port** (*Optional*): The TCP port number. Defaults to 9090. Used for websocket connections to Kodi.
3434
- **name** (*Optional*): The name of the device used in the frontend.
35-
- **ssl** (*Optional*): Connect to kodi with HTTPS and WSS. Defaults to `false`.
35+
- **proxy_ssl** (*Optional*): Connect to kodi with HTTPS and WSS. Defaults to `false`. Useful if Kodi is behind an SSL proxy.
3636
- **username** (*Optional*): The XBMC/Kodi HTTP username.
3737
- **password** (*Optional*): The XBMC/Kodi HTTP password.
3838
- **turn_off_action** (*Optional*): The desired turn off action. Options are `none`, `quit`, `hibernate`, `suspend`, `reboot`, or `shutdown`. Default `none`.

‎source/_components/media_player.mpd.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Configuration variables:
3131
3232
- **host** (*Required*): IP address of the Host where Music Player Daemon is running.
3333
- **port** (*Optional*): Port of the Music Player Daemon. Defaults to 6600.
34-
- **location** (*Optional*): Location of your Music Player Daemon. Defaults to "MPD".
34+
- **name** (*Optional*): Name of your Music Player Daemon. Defaults to "MPD".
3535
- **password** (*Optional*): Password for your Music Player Daemon.
3636
3737
Example script to load a saved playlist called "DeckMusic" and set the volume:

0 commit comments

Comments
 (0)