Skip to content

Commit 2b0c3e8

Browse files
bdurrerbdurrer
committed
Merge 'home-assistant/current' into issue-2142
2 parents a4849b5 + 0e92aac commit 2b0c3e8

40 files changed

+425
-121
lines changed

‎_config.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -128,9 +128,9 @@ social:
128128
# Home Assistant release details
129129
current_major_version: 0
130130
current_minor_version: 40
131-
current_patch_version: 0
132-
date_released: 2017-03-11
131+
current_patch_version: 1
132+
date_released: 2017-03-16
133133

134134
# Either # or the anchor link to latest release notes in the blog post.
135135
# Must be prefixed with a # and have double quotes around it.
136-
patch_version_notes: "#"
136+
patch_version_notes: "#release-0401---march-16"

‎sass/custom/_paulus.scss

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -330,6 +330,21 @@ p.note {
330330
-moz-transition-property: -moz-transform, opacity;
331331
transition-property: transform, opacity;
332332
}
333+
334+
335+
.component-search{
336+
margin-bottom: 24px;
337+
338+
input{
339+
width: 100%;
340+
padding: 10px;
341+
342+
background-color: #fefefe;
343+
border-radius: 2px;
344+
border: 1px solid;
345+
border-color: #7c7c7c #c3c3c3 #ddd;
346+
}
347+
}
333348
}
334349

335350
@media only screen and (max-width: $lap-end) {

‎source/_components/binary_sensor.apcupsd.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ comments: false
88
sharing: true
99
footer: true
1010
logo: apcupsd.png
11-
ha_category: Binary Sensor
11+
ha_category: System Monitor
1212
ha_release: 0.13
1313
ha_iot_class: "Local Polling"
1414
---

‎source/_components/binary_sensor.bbb_gpio.markdown

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,12 +19,12 @@ To use your BeagleBone Black's GPIO in your installation, add the following to y
1919
```yaml
2020
# Example configuration.yaml entry
2121
binary_sensor:
22-
- platform: bbb_gpio
23-
pins:
24-
P8_12:
25-
name: Door
26-
GPIO0_26:
27-
name: Window
22+
- platform: bbb_gpio
23+
pins:
24+
P8_12:
25+
name: Door
26+
GPIO0_26:
27+
name: Window
2828
```
2929
3030
Configuration variables:

‎source/_components/device_tracker.unifi.markdown

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,5 +32,6 @@ Configuration variables:
3232
- **username** (*Required*: The username of an user with administrative privileges, usually `admin`.
3333
- **password** (*Required*): The password for your given admin account.
3434
- **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)
35+
- **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'.
3536

3637
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.

‎source/_components/discovery.markdown

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,10 @@ Home Assistant can discover and automatically configure zeroconf/mDNS and uPnP d
2626
* Logitech media server (Squeezebox)
2727
* DirecTV
2828
* Apple TV
29+
* Yeelight Sunflower Bulb
30+
* Flux Led/MagicLight
31+
* Linn / Openhome
32+
* Denon Network Receivers
2933

3034
It will be able to add Google Chromecasts and Belkin WeMo switches automatically, for Philips Hue it will require some configuration from the user.
3135

@@ -43,6 +47,24 @@ Configuration variables:
4347
4448
- **ignore** (*Optional*): A list of platforms that never will be automatically configured by `discovery`.
4549

50+
Valid values for ignore are:
51+
* philips_hue: (Philips Hue)
52+
* google_cast: (Google Chromecast)
53+
* panasonic_viera: (Panasonic Viera)
54+
* plex_mediaserver: (Plex media server)
55+
* roku: (Roku media player)
56+
* sonos: (Sonos Speakers)
57+
* yamaha: (Yamaha media player)
58+
* logitech_mediaserver: (Logitech media server - Squeezebox player)
59+
* directv: (DirecTV)
60+
* denonavr: (Denon Network Receivers)
61+
* samsung_tv: (Samsung TV)
62+
* yeelight: (Yeelight Sunflower Bulb)
63+
* flux_led: (Flux Led/MagicLight)
64+
* apple_tv: (Apple TV)
65+
* openhome: (Linn / Openhome)
66+
67+
4668
<p class='note'>
4769
Home Assistant must be on the same network as the devices for uPnP discovery to work.
4870
If running Home Assistant in a Docker container use switch `--net=host` to put it on the host's network.

‎source/_components/influxdb.markdown

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
layout: page
33
title: "InfluxDB"
44
description: "Record events in InfluxDB."
5-
date: 2015-12-06 13:08
5+
date: 2017-03-13 22:09
66
sidebar: true
77
comments: false
88
sharing: true
@@ -27,40 +27,40 @@ You will still need to create a database named `home_assistant` via InfluxDB's w
2727

2828
Configuration variables:
2929

30-
- **host** (*Optional*): IP address of your database host, eg. 192.168.1.10. Defaults to `localhost`.
30+
- **host** (*Optional*): IP address of your database host, e.g. 192.168.1.10. Defaults to `localhost`.
3131
- **port** (*Optional*): Port to use. Defaults to 8086.
3232
- **username** (*Optional*): The username of the database user.
3333
- **password** (*Optional*): The password for the database user account.
3434
- **database** (*Optional*): Name of the database to use. Defaults to `home_assistant`. The database must already exist.
3535
- **ssl** (*Optional*): Use https instead of http to connect. Defaults to false.
3636
- **verify_ssl** (*Optional*): Verify SSL certificate for https request. Defaults to false.
3737
- **default_measurement** (*Optional*): Measurement name to use when an entity doesn't have a unit. Defaults to entity id.
38-
- **override_measurement** (*Optional*): Measurement name to use instead of unit or default measurement. This will store all data points in the singel same measurement.
39-
- **blacklist** (*Optional*): List of entities not logged to InfluxDB.
38+
- **override_measurement** (*Optional*): Measurement name to use instead of unit or default measurement. This will store all data points in a single measurement.
39+
- **blacklist** (*Optional*): List of entities that should not be logged to InfluxDB.
4040
- **whitelist** (*Optional*): List of the entities (only) that will be logged to InfluxDB. If not set, all entities will be logged. Values set by the **blacklist** option will prevail.
4141
- **tags** (*Optional*): Tags to mark the data.
4242

4343
## {% linkable_title Data migration %}
4444

4545
Starting with 0.36 the InfluxDB component has a new schema to store values in the InfluxDB databases.
4646

47-
- There will not be any tags/fields named time anymore.
47+
- There will no longer be any tags/fields named `time`.
4848
- All numeric fields (int/float/bool) will be stored as float inside InfluxDB database.
4949
- All string fields corresponding to state attributes will be renamed as `FIELDNAME_str`, where `FIELDNAME` is the state attribute, to avoid type conflicts.
50-
- All string fields corresponding to a state will be renamed as state (former value).
51-
- Fields named value will always be stored as float.
52-
- Fields named state will always be stored as string.
50+
- All string fields corresponding to a state will be renamed as `state` (former value).
51+
- Fields named `value` will always be stored as float.
52+
- Fields named `state` will always be stored as string.
5353

5454
### {% linkable_title Migration script %}
5555

56-
If you need to migrate your database, you may require to run the `influxdb_migrator` script. Run the script after upgrade to 0.36 but before first regular start of `hass` version 0.36.
56+
If you need to migrate your database, you may require to run the `influxdb_migrator` script. Run the script after upgrade to 0.36 but before the first regular start of `hass` version 0.36.
5757

5858
These are the steps the script will perform:
5959
1. Create a new database (called `DBNAME__old`) to store old data.
6060
2. Copy data from `DBNAME` database to `DBNAME__old` database.
6161
3. Empty `DBNAME` database (using `drop` then `create`). `DBNAME` database is now considered as the new database.
6262
4. For each measurement of `DBNAME__old` database:
63-
1. Read all points from the current measuremnt (by group of `1000` points by default) and convert them.
63+
1. Read all points from the current measurement (in groups of 1000 points by default) and convert them.
6464
2. Send group of points to `DBNAME` database.
6565
5. Delete the `DBNAME__old` database if needed.
6666

@@ -94,7 +94,7 @@ optional arguments:
9494
- If you run the script with only the `-h` option, you will get a help printout with a short explanation of the different options.
9595
- The host option defaults to `'127.0.0.1'`.
9696
- The port option defaults to `8086`.
97-
- You should be able to omit username and password, if InfluxDB authentication is disabled, which it is by default.
97+
- You should be able to omit username and password if InfluxDB authentication is disabled, which it is by default.
9898
- The step option defaults to `1000`.
9999

100100

‎source/_components/joaoapps_join.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Configuration variables:
3737
- **device_id** (*Required*): The Id of your device.
3838
- **api_key** (*Required*): The API key for Join.
3939
40-
The notify service has a few optional parameters such as icon and small icon. You can use them like so:
40+
The notify service has two optional parameters: `icon` and `small icon`. You can use them like so:
4141

4242
```json
4343
{"message":"Hello!","title":"From Hass","data":{"icon":"https://goo.gl/KVqcYi","smallicon":"http://goo.gl/AU4Wf1"}}

‎source/_components/light.lifx.markdown

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -19,12 +19,8 @@ The `lifx` platform allows you to integrate your [LIFX](http://www.lifx.com) int
1919
# Example configuration.yaml entry
2020
light:
2121
- platform: lifx
22-
broadcast: 192.168.1.255
22+
server: 192.168.1.10
2323
```
2424
Configuration variables:
2525
2626
- **server** (*Optional*): Your server address. Only needed if using more than one network interface. Omit if you are unsure.
27-
- **broadcast** (*Optional*): The broadcast address, set to reach all LIFX bulbs.
28-
29-
If there is an issue with lights not showing up when Home Assistant is restarted, add broadcast to your configuration.
30-

‎source/_components/light.yeelightsunflower.markdown

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,11 @@ ha_category: Light
1111
ha_release: 0.39
1212
---
1313

14-
The `yeelightsunflower` light platform allows you to control your Yeelight Sunflower light bulbs with Home Assistant.
15-
Note that the "Yeelight Sunflower" bulbs are not the same as the "Yeelight WiFi" bulbs.
14+
The `yeelightsunflower` light platform allows you to control your Yeelight Sunflower light bulbs with Home Assistant.
1615

17-
### {% linkable_title Example configuration %}
16+
<p class='note warning'>
17+
The "Yeelight Sunflower" bulbs are not the same as the "Yeelight WiFi" bulbs.
18+
</p>
1819

1920
To enable your lights, add the following lines to your `configuration.yaml` file:
2021

@@ -37,4 +38,3 @@ When the hub is loaded, your lights will appear as devices with their Zigbee IDs
3738
The Yeelight Sunflower hub supports SSDP discovery, but that has not been built into the platform. Let the developer know if that would be helpful to you.
3839
</p>
3940
40-

‎source/_components/media_player.firetv.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Steps to configure your Amazon Fire TV stick with Home Assistant:
2828
- From the main (Launcher) screen, select Settings.
2929
- Select System > About > Network.
3030
- The following commands must be run in a Python 2.x environment. They will allow the component to function in an Ubuntu 16.04/Hassbian environment.
31-
- `apt-get install swig libssl-dev python-dev libusb-1.0-0`
31+
- `apt-get install swig libssl-dev python-dev libusb-1.0-0 python-yaml`
3232
- `pip install flask`
3333
- `pip install https://pypi.python.org/packages/source/M/M2Crypto/M2Crypto-0.24.0.tar.gz`
3434
- `pip install firetv[firetv-server]`

‎source/_components/media_player.gstreamer.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ And then install the following system dependencies:
3737
Debian/Ubuntu/Rasbian:
3838

3939
```bash
40-
sudo apt-get install python-gst-1.0 \
40+
sudo apt-get install python3-gst-1.0 \
4141
gir1.2-gstreamer-1.0 gir1.2-gst-plugins-base-1.0 \
4242
gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly \
4343
gstreamer1.0-tools

‎source/_components/media_player.samsungtv.markdown

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Configuration variables:
3232
- **host** (*Required*): The IP of the Samsung Smart TV, eg. `192.168.0.10`.
3333
- **port** (*Optional*): The port of the Samsung Smart TV. Defaults to 55000. If set to 8001, the new websocket connection will be used (required for 2016+ TVs).
3434
- **name** (*Optional*): The name you would like to give to the Samsung Smart TV.
35-
- **timeout** (*Optional*): The time-out for the communication with the TV. Defaults to 0.
35+
- **timeout** (*Optional*): The time-out in seconds for the communication with the TV. Defaults to 0 (no timeout).
3636
- **mac** (*Optional*): The MAC address of the Samsung Smart TV, eg. `00:11:22:33:44:55:66`. Required for power on support via wake on lan.
3737

3838
Currently known supported models:
@@ -44,6 +44,7 @@ Currently known supported models:
4444
- ES6800
4545
- F6300
4646
- F6500
47+
- EH5300
4748
- EH5600
4849
- F6400AF
4950
- D6505

‎source/_components/notify.twilio_call.markdown

Lines changed: 3 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,18 +9,13 @@ sharing: true
99
footer: true
1010
logo: twilio.png
1111
ha_category: Notifications
12-
ha_release: "0.37"
12+
ha_release: 0.37
1313
---
1414

15-
The `twilio` notification platform enables sending notifications via Voice, powered by [Twilio](https://twilio.com).
15+
The `twilio_call` notification platform enables sending notifications via Voice, powered by [Twilio](https://twilio.com).
1616
Passed message will be read by Text-To-Speech service.
1717

18-
This component is just an adaptation from the Twilio SMS notification platform and won't exist without it.
19-
20-
Free trial account is available at [Twilio](https://twilio.com) website providing free calls to verified phone numbers.
21-
Calls are limited to 10 minutes and will play a short trial message before your message runs.
22-
23-
Upgraded accounts have no limitation.
18+
The requirement is that you have setup [Twilio](/components/twilio/).
2419

2520
To use this notification platform in your installation, add the following to your `configuration.yaml` file:
2621

@@ -29,15 +24,11 @@ To use this notification platform in your installation, add the following to you
2924
notify:
3025
- name: NOTIFIER_NAME
3126
platform: twilio_call
32-
account_sid: ACCOUNT_SID_FROM_TWILIO
33-
auth_token: AUTH_TOKEN_FROM_TWILIO
3427
from_number: E164_PHONE_NUMBER
3528
```
3629
3730
Configuration variables:
3831
39-
- **account_sid** (*Required*): Your Twilio Account SID which can be found in your [console](https://www.twilio.com/console). It starts with the letters `AC`.
40-
- **auth_token** (*Required*): Your Twilio Account SID which can be found in your [console](https://www.twilio.com/console). It should be directly under where you found the `account_sid`.
4132
- **from_number** (*Required*): An [E.164](https://en.wikipedia.org/wiki/E.164) formatted phone number, like +14151234567. See [Twilio's guide to formatting phone numbers](https://www.twilio.com/help/faq/phone-numbers/how-do-i-format-phone-numbers-to-work-internationally) for more information.
4233
- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
4334

‎source/_components/notify.twilio_sms.markdown

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,22 +14,20 @@ ha_release: "0.20"
1414

1515
The `twilio` notification platform enables sending notifications via SMS, powered by [Twilio](https://twilio.com).
1616

17+
The requirement is that you have setup [Twilio](/components/twilio/).
18+
1719
To use this notification platform in your installation, add the following to your `configuration.yaml` file:
1820

1921
```yaml
2022
# Example configuration.yaml entry
2123
notify:
2224
- name: NOTIFIER_NAME
2325
platform: twilio_sms
24-
account_sid: ACCOUNT_SID_FROM_TWILIO
25-
auth_token: AUTH_TOKEN_FROM_TWILIO
2626
from_number: E164_PHONE_NUMBER
2727
```
2828
2929
Configuration variables:
3030
31-
- **account_sid** (*Required*): Your Twilio Account SID which can be found in your [console](https://www.twilio.com/console). It starts with the letters `AC`.
32-
- **auth_token** (*Required*): Your Twilio Account SID which can be found in your [console](https://www.twilio.com/console). It should be directly under where you found the `account_sid`.
3331
- **from_number** (*Required*): An [E.164](https://en.wikipedia.org/wiki/E.164) formatted phone number, like +14151234567. See [Twilio's guide to formatting phone numbers](https://www.twilio.com/help/faq/phone-numbers/how-do-i-format-phone-numbers-to-work-internationally) for more information.
3432
- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
3533

‎source/_components/notify.webostv.markdown

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,7 @@ Configuration variables:
3333
- **host** (*Required*): The IP of the LG WebOS Smart TV, e.g. 192.168.0.10
3434
- **name** (*Required*): The name you would like to give to the LG WebOS Smart TV.
3535
- **filename** (*Optional*): The filename where the pairing key with the TV should be stored. This path is relative to Home Assistant's config directory. It defaults to `webostv.conf`.
36+
- **icon** (*Optional*): The path to an image file to use as the icon in notifications. If provided, this image will override the Home Assistant logo.
3637

3738
A possible automation could be:
3839

@@ -49,3 +50,20 @@ automation:
4950
data:
5051
message: "You should open a window! (Livingroom Co2: {{ states.sensor.netatmo_livingroom_co2.state }}ppm)"
5152
```
53+
54+
The icon can be overridden for individual notifications by providing a path to an alternative icon image to use:
55+
56+
```yaml
57+
automation:
58+
- alias: Front door motion
59+
trigger:
60+
platform: state
61+
entity_id: binary_sensor.front_door_motion
62+
state: 'on'
63+
action:
64+
service: notify.livingroom_tv
65+
data:
66+
message: "Movement detected: Front Door"
67+
data:
68+
icon: "/home/homeassistant/images/doorbell.png"
69+
```

‎source/_components/rflink.markdown

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,9 @@ Wildcards only work at the end of the ID, not in the middle of front!
9494

9595
Even though a lot of devices are supported by Rflink, not all have been tested/implemented. If you have a device supported by Rflink but not by this component please consider testing and adding support yourself or [create an issue](https://github.com/home-assistant/home-assistant/issues/new) and mention `@aequitas` in the description.
9696

97+
### {% linkable_title Device Incorrectly Identified %}
98+
99+
If you find a device is recognized differently, with different protocols or the ON OFF is swapped or detected as two ON commands, it can be overcome with the RFlink 'RF Signal Learning' mechanism from RFLink Rev 46 (11 March 2017). http://www.nemcon.nl/blog2/faq#RFFind.
97100

98101
### {% linkable_title Technical overview %}
99102

‎source/_components/sensor.apcupsd.markdown

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,8 @@ comments: false
88
sharing: true
99
footer: true
1010
logo: apcupsd.png
11-
ha_category: Sensor
11+
ha_release: 0.13
12+
ha_category: System Monitor
1213
---
1314

1415
The `apcupsd` sensor platform allows you to monitor a UPS (battery backup) by using data from the [apcaccess](http://linux.die.net/man/8/apcaccess) command.

‎source/_components/sensor.comed_hourly_pricing.markdown

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,12 @@ ha_release: "0.40"
1313
ha_iot_class: "Cloud Polling"
1414
---
1515

16-
The ComEd Hourly Pricing program is an optional program available to ComEd electric subscribers which charges customers a variable rate for electricity supply based on current demand rather than a traditional fixed rate. Live prices are published [here](https://hourlypricing.comed.com/live-prices/) and also via an [API](https://hourlypricing.comed.com/hp-api/) which we can integrate as a sensor in Home Assistant.
16+
The ComEd Hourly Pricing program is an optional program available to ComEd electric subscribers which charges customers a variable rate for electricity supply based on current demand rather than a traditional fixed rate. Live prices are published [here](https://hourlypricing.comed.com/live-prices/) and also via an [API](https://hourlypricing.comed.com/hp-api/) which we can integrate as a sensor in Home Assistant.
1717

1818
There are two price feeds available: the 5-minute price and current hour average price.
1919

20+
To use this sensor in your installation, add the following to your `configuration.yaml` file:
21+
2022
```yaml
2123
# Example configuration.yaml entry
2224
sensor:
@@ -33,5 +35,5 @@ Configuration variables:
3335
- **five_minute**: The latest 5-minute price in cents.
3436
- **current_hour_average**: The latest current hour average price in cents.
3537
- **name** (*Optional*): Custom name for the sensor.
36-
- **offset** (*Optional*): The pricing feeds provide only the *supply* cost of the electricity. The offset parameter allows you to provide a fixed constant that will be added to the pricing data to provide a more accurate representation of the total electricity cost per kWh.
38+
- **offset** (*Optional*): The pricing feeds provide only the *supply* cost of the electricity. The offset parameter allows you to provide a fixed constant that will be added to the pricing data to provide a more accurate representation of the total electricity cost per kWh.
3739

0 commit comments

Comments
 (0)