Skip to content

Commit 02d527d

Browse files
balloobballoob
committed
Merge remote-tracking branch 'origin/current' into next
2 parents 18e81c1 + 5ba6f9d commit 02d527d

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

56 files changed

+732
-173
lines changed

‎_config.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -142,12 +142,12 @@ social:
142142

143143
# Home Assistant release details
144144
current_major_version: 0
145-
current_minor_version: 50
146-
current_patch_version: 2
147-
date_released: 2017-07-31
145+
current_minor_version: 51
146+
current_patch_version: 0
147+
date_released: 2017-08-12
148148

149149
# Either # or the anchor link to latest release notes in the blog post.
150150
# Must be prefixed with a # and have double quotes around it.
151151
# Major release:
152-
patch_version_notes: "#release-0502---july-31"
152+
patch_version_notes: "#"
153153
# Minor release (Example #release-0431---april-25):

‎source/_addons/lets_encrypt.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,10 +10,10 @@ footer: true
1010
featured: true
1111
---
1212

13-
Setup and manage a [Let's Encrypt](https://letsencrypt.org/) certificate. This will create a certificate on the first run and renew it if the certificate is expiring in the next 30 days.
13+
Setup and manage a [Let's Encrypt](https://letsencrypt.org/) certificate. This will create a certificate on the first run and will auto-renew if the certificate is within 30 days of expiration.
1414

1515
<p class='note warning'>
16-
This add-on need port 80/443 to verify the certificate request, please stop all add-ons they use also this ports, otherwise you can not start this add-on.
16+
This add-on need port 80/443 to verify the certificate request, please stop all add-ons that also use these ports, or you may not be able to start this add-on.
1717
</p>
1818

1919
```json

‎source/_components/alarm_control_panel.woonveilg.markdown

Lines changed: 0 additions & 15 deletions
This file was deleted.

‎source/_components/apple_tv.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ then device authentication is required. Press the icon in the upper left corner
110110

111111
<img src='/images/screenshots/developer-tools.png' />
112112

113-
Select `apple_tv` as domain, `apple_tv_authenticate` as service and enter `{'entity_id': 'XXX'}` into "Service Data", but replace XXX with the entity id of your device (e.g. `media_player.apple_tv`). Press the button and hopefully you are presented with an input dialog asking for a pin code:
113+
Select `apple_tv` as domain, `apple_tv_authenticate` as service and enter `{"entity_id": "XXX"}` into "Service Data", but replace XXX with the entity id of your device (e.g. `media_player.apple_tv`). Press the button and hopefully you are presented with an input dialog asking for a pin code:
114114

115115
<img src='/images/components/apple_tv/auth_start.jpg' />
116116

‎source/_components/arlo.markdown

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,3 +32,17 @@ Configuration variables:
3232
It is recommended to create a dedicated user on Arlo website to be used within Home Assistant and then share your Arlo cameras.
3333
3434
Finish its configuration by visiting the [Arlo sensor page](/components/sensor.arlo/) or [Arlo camera page](/components/camera.arlo/).
35+
36+
The Arlo component also provides a service to enable/disable the motion detection sensor. The example below enables the motion detection every time the Home Assistant service starts.
37+
38+
```yaml
39+
#automation.yaml
40+
- alias: Enable Arlo upton HA start'
41+
initial_state: 'on'
42+
trigger:
43+
platform: homeassitant
44+
event: start
45+
action:
46+
service: camera.enable_motion_detection
47+
entity_id: camera.arlo_frontdoor
48+
```

‎source/_components/browser.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: home-assistant.png
11-
ha_category: Other
11+
ha_category: Utility
1212
---
1313

1414

‎source/_components/climate.markdown

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -222,3 +222,12 @@ automation:
222222
entity_id: climate.kitchen
223223
swing_mode: 1
224224
```
225+
#### {% linkable_title Customization %}
226+
227+
The step for the setpoint can be adjusted (default to 0,5 increments) by adding the following line into configuration
228+
229+
'''yaml
230+
customize:
231+
- entity_id
232+
target_temp_step: 1
233+
'''

‎source/_components/device_tracker.markdown

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -68,11 +68,11 @@ devicename:
6868

6969
| Parameter | Default | Description |
7070
|----------------|-------------------------------|---------------------------------------------------------------------------------------------------------|
71-
| `name` | Host name or "Unnamed Device" | The friendly name of the device |
72-
| `mac` | None | The MAC address of the device. Add this if you are using a network device tracker like Nmap or SNMP |
71+
| `name` | Host name or "Unnamed Device" | The friendly name of the device. |
72+
| `mac` | None | The MAC address of the device. Add this if you are using a network device tracker like Nmap or SNMP. |
7373
| `picture` | None | A picture that you can use to easily identify the person or device. You can also save the image file in a folder "www" in the same location (can be obtained from developer tools) where you have your configuration.yaml file and just use `picture: /local/favicon-192x192.png`. |
7474
| `icon` | mdi:account | An icon for this device (use as an alternative to `picture`). |
75-
| `gravatar` | None | An email address for the device's owner. If provided, it will override `picture` |
76-
| `track` | [uses platform setting] | If `yes`/`on`/`true` then the device will be tracked. Otherwise its location and state will not update |
77-
| `hide_if_away` | False | If `yes`/`on`/`true` then the device will be hidden if it is not at home |
78-
| `consider_home` | [uses platform setting] | Allows you to override the global `consider_home` setting from the platform configuration on a per device level |
75+
| `gravatar` | None | An email address for the device's owner. If provided, it will override `picture`. |
76+
| `track` | [uses platform setting] | If `yes`/`on`/`true` then the device will be tracked. Otherwise its location and state will not update. |
77+
| `hide_if_away` | False | If `yes`/`on`/`true` then the device will be hidden if it is not at home. |
78+
| `consider_home` | [uses platform setting] | Seconds to wait till marking someone as not home after not being seen. Allows you to override the global `consider_home` setting from the platform configuration on a per device level. |

‎source/_components/device_tracker.nmap_tracker.markdown

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,10 @@ As an alternative to the router-based device tracking, it is possible to directl
1717

1818
If you're on Debian or Ubuntu, you might have to install the packages for `arp` and `nmap`. Do so by running `$ sudo apt-get install net-tools nmap`. On a Fedora host run `$ sudo dnf -y install nmap`.
1919

20+
<p class='note'>
21+
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fullfilled.
22+
</p>
23+
2024
Host detection is done via Nmap's "fast scan" (`-F`) of the most frequently used 100 ports, with a host timeout of 5 seconds.
2125

2226
To use this device tracker in your installation, add the following to your `configuration.yaml` file:

‎source/_components/ffmpeg.markdown

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,16 @@ logo: ffmpeg.png
1111
ha_category: Hub
1212
---
1313

14-
The FFmpeg component allows other Home Assistant components to process video and audio streams. This component supports all FFmpeg versions since 3.0.0; if you have a older version, please update.
14+
The `ffmpeg` component allows other Home Assistant components to process video and audio streams. This component supports all FFmpeg versions since 3.0.0; if you have a older version, please update.
1515

1616
<p class='note'>
1717
You need the `ffmpeg` binary in your system path. On Debian 8 or Raspbian (Jessie) you can install it from [debian-backports](https://backports.debian.org/Instructions/). If you want [hardware acceleration](https://trac.ffmpeg.org/wiki/HWAccelIntro) support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are available on the [FFmpeg](http://www.ffmpeg.org/) website.
1818
</p>
1919

20+
<p class='note'>
21+
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fullfilled.
22+
</p>
23+
2024
To set it up, add the following information to your `configuration.yaml` file:
2125

2226
```yaml

‎source/_components/frontend.markdown

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,14 @@ This offers the official frontend to control Home Assistant.
1818
frontend:
1919
```
2020
21-
#### Themes
21+
### {% linkable_title Themes %}
22+
2223
Starting with version 0.49 you can define themes:
2324
2425
Example:
26+
2527
```yaml
28+
# Example configuration.yaml entry
2629
frontend:
2730
themes:
2831
happy:
@@ -31,13 +34,15 @@ frontend:
3134
primary-color: blue
3235
```
3336
34-
The example above defined two themes named `happy` and `sad`. For each theme you can set values for CSS variables. For a partial list of variables used by the main frontend see [ha-style.html](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/resources/ha-style.html)
37+
The example above defined two themes named `happy` and `sad`. For each theme you can set values for CSS variables. For a partial list of variables used by the main frontend see [ha-style.html](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/resources/ha-style.html).
3538

3639
There are 2 themes-related services:
37-
- `frontend.reload_themes` - reloads theme configuration from yaml.
38-
- `frontend.set_theme(name)` - sets backend-preferred theme name.
40+
41+
- `frontend.reload_themes`: reloads theme configuration from your `configuration.yaml` file.
42+
- `frontend.set_theme(name)`: sets backend-preferred theme name.
3943

4044
Example in automation:
45+
4146
```yaml
4247
automation:
4348
- alias: 'Set theme at startup'
@@ -48,5 +53,5 @@ automation:
4853
action:
4954
service: frontend.set_theme
5055
data:
51-
name: pink
56+
name: happy
5257
```

‎source/_components/hdmi_cec.markdown

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ha_release: 0.23
1313
ha_iot_class: "Local Push"
1414
---
1515

16-
The HDMI CEC component provides services that allow selecting the active device, powering on all devices, setting all devices to standby and creates switch entites for HDMI devices. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as Soundbars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use `cec-client` (part of the `libcec` package) to listen to traffic on the CEC bus and discover the correct numbers.
16+
The `hdmi_cec` component provides services that allow selecting the active device, powering on all devices, setting all devices to standby and creates switch entites for HDMI devices. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as Soundbars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use `cec-client` (part of the `libcec` package) to listen to traffic on the CEC bus and discover the correct numbers.
1717

1818
## {% linkable_title CEC Setup %}
1919

@@ -25,6 +25,10 @@ The computer running Home Assistant must support CEC, and of course be connected
2525

2626
[libcec](https://github.com/Pulse-Eight/libcec) must be installed for this component to work. Follow the installation instructions for your environment, provided at the link. `libcec` installs Python 3 bindings by default as a system Python module. If you are running Home Assistant in a [Python virtual environment](/getting-started/installation-virtualenv/), make sure it can access the system module, by either symlinking it or using the `--system-site-packages` flag.
2727

28+
<p class='note'>
29+
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fullfilled.
30+
</p>
31+
2832
#### {% linkable_title Symlinking into virtual environment %}
2933

3034
Create a symlink to the `cec` installation. Keep in mind different installation methods will result in different locations of cec.

‎source/_components/image_processing.openalpr_cloud.markdown

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,7 @@ image_processing:
2828
source:
2929
- entity_id: camera.garage
3030
```
31+
3132
Configuration variables:
3233
3334
- **region** (*Required*): Country or region. List of supported [values](https://github.com/openalpr/openalpr/tree/master/runtime_data/config).

‎source/_components/image_processing.opencv.markdown

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,6 @@ ha_release: 0.47
1717

1818
Some pre-defined classifiers can be found here: https://github.com/opencv/opencv/tree/master/data
1919

20-
### {% linkable_title Configuration %}
21-
2220
To setup OpenCV with Home Assistant, add the following section to your `configuration.yaml` file:
2321

2422
```yaml

‎source/_components/image_processing.seven_segments.markdown

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,10 @@ ha_iot_class: "Local Polling"
1717

1818
The `seven_segments` image processing platform allows you to read physical seven segments displays through Home Assistant. [`ssocr`](https://www.unix-ag.uni-kl.de/~auerswal/ssocr/) is used to extract the value shown on the display which is observed by a [camera](/components/camera/). `ssocr` need to be available on your system. Check the installation instruction for Fedora below or use `$ sudo apt-get install ssocr` on a Debian-based system:
1919

20+
<p class='note'>
21+
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fullfilled.
22+
</p>
23+
2024
```bash
2125
$ sudo dnf -y install imlib2-devel
2226
$ git clone https://github.com/auerswal/ssocr.git

0 commit comments

Comments
 (0)