Skip to content

Commit c92f9e5

Browse files
balloobballoob
committed
Merge branch 'rc' into current
2 parents 432b4f1 + b4b7907 commit c92f9e5

40 files changed

+1143
-314
lines changed

‎_config.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -141,14 +141,14 @@ social:
141141

142142
# Home Assistant release details
143143
current_major_version: 0
144-
current_minor_version: 75
145-
current_patch_version: 3
146-
date_released: 2018-08-09
144+
current_minor_version: 76
145+
current_patch_version: 0
146+
date_released: 2018-08-17
147147

148148
# Either # or the anchor link to latest release notes in the blog post.
149149
# Must be prefixed with a # and have double quotes around it.
150150
# Major release:
151-
patch_version_notes: "#release-0753---august-9"
151+
patch_version_notes: "#"
152152
# Minor release (Example #release-0431---april-25):
153153

154154
# Date we moved to Discourse for comments

‎source/_components/amcrest.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Configuration variables:
4646
- **host** (*Required*): The IP address or hostname of your camera. If using a hostname, make sure the DNS works as expected.
4747
- **username** (*Required*): The username for accessing your camera.
4848
- **password** (*Required*): The password for accessing your camera.
49-
- **name** (*Optional*): This parameter allows you to override the name of your camera. The default is "Amcrest Camera".
49+
- **name** (*Optional*): This parameter allows you to override the name of your camera. The default is "Amcrest Camera". In the case of multi-camera setups, this is highly recommended as camera id number will be randomly changed at each reboot if a name is not allocated.
5050
- **port** (*Optional*): The port that the camera is running on. The default is 80.
5151
- **resolution** (*Optional*): This parameter allows you to specify the camera resolution. For a high resolution (1080/720p), specify the option `high`. For VGA resolution (640x480p), specify the option `low`. If omitted, it defaults to *high*.
5252
- **stream_source** (*Optional*): The data source for the live stream. `mjpeg` will use the camera's native MJPEG stream, whereas `snapshot` will use the camera's snapshot API to create a stream from still images. You can also set the `rtsp` option to generate the streaming via RTSP protocol. If omitted, it defaults to *snapshot*.

‎source/_components/binary_sensor.openuv.markdown

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
layout: page
3+
title: "OpenUV Binary Sensor"
4+
description: "Instructions on how to integrate OpenUV binary sensors within Home Assistant."
5+
date: 2018-07-31 22:01
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: openuv.jpg
11+
ha_category: Binary Sensor
12+
ha_release: 0.76
13+
ha_iot_class: "Cloud Polling"
14+
---
15+
16+
The `openuv` binary sensor platform allows you to view binary sensor data from
17+
[OpenUV](http://openuv.io).
18+
19+
<p class='note'>
20+
You must have the [OpenUV component](/components/openuv/) configured to use
21+
this platform. After configuring that component, binary sensors will
22+
automatically appear.
23+
</p>

‎source/_components/binary_sensor.velbus.markdown

Lines changed: 1 addition & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -13,49 +13,6 @@ ha_iot_class: "Local Push"
1313
ha_release: "0.50"
1414
---
1515

16-
The `velbus` binary_sensor allows you to control [Velbus](http://www.velbus.eu) connected wall switches.
17-
18-
## {% linkable_title Configuration %}
19-
20-
To use your Velbus wall switches in your installation, add the following to your `configuration.yaml` file:
21-
22-
```yaml
23-
# Example configuration.yaml entry
24-
binary_sensor:
25-
- platform: velbus
26-
devices:
27-
- name: Wall Switch 1
28-
module: 0xda
29-
channel: 4
30-
- name: Wall Switch 2
31-
module: 0xbc
32-
channel: 1
33-
is_pushbutton: true
34-
```
35-
36-
{% configuration %}
37-
devices:
38-
description: The list contains the binary sensors to configure.
39-
required: true
40-
type: map
41-
keys:
42-
name:
43-
description: Name to use in the frontend.
44-
required: true
45-
type: string
46-
module:
47-
description: The hexadecimal module address.
48-
required: true
49-
type: string
50-
channel:
51-
description: The channel number in the module.
52-
required: true
53-
type: string
54-
is_pushbutton:
55-
description: Set to indicate if a wall switch is a push button or not.
56-
required: false
57-
type: boolean
58-
default: false
59-
{% endconfiguration %}
16+
The `velbus` binary_sensor allows you to control [Velbus](http://www.velbus.eu) connected input devices.
6017

6118
For hub configuration, see [the Velbus component](/components/velbus/).

‎source/_components/device_tracker.bt_home_hub_5.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,6 @@ device_tracker:
2525
2626
Configuration variables:
2727
28-
- **host** (*Required*): The IP address of your router, e.g., 192.168.1.254.
28+
- **host** (*Optional*): The IP address of your router, Default: 192.168.1.254.
2929
3030
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.

‎source/_components/device_tracker.google_maps.markdown

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ha_category: Presence Detection
1313
ha_iot_class: "Cloud Polling"
1414
---
1515

16-
The `google_maps` platform allows you to detect presence using the unofficial API of [Google Maps Location Sharing](https://myaccount.google.com/locationsharing).
16+
The `google_maps` platform allows you to detect presence using the unofficial API of [Google Maps Location Sharing](https://myaccount.google.com/locationsharing).
1717

1818
## {% linkable_title Configuration %}
1919

@@ -45,4 +45,8 @@ password:
4545
description: The password for your given username.
4646
required: true
4747
type: string
48+
max_gps_accuracy:
49+
description: Sometimes Google Maps can report GPS locations with a very low accuracy (few kilometers). That can trigger false zoning. Using this parameter, you can filter these false GPS reports. The number has to be in meters. For example, if you put 200 only GPS reports with an accuracy under 200 will be taken into account - Defaults to 100km if not specified.
50+
required: false
51+
type: float
4852
{% endconfiguration %}

‎source/_components/device_tracker.keenetic_ndms2.markdown

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,8 @@ device_tracker:
2929
Configuration variables:
3030
3131
- **host** (*Required*): The IP address of your router, e.g., 192.168.1.1.
32-
- **username** (*Required*): The username to login into the router (user should have read access to web interface of the router).
32+
- **port** (*Optional*): The Telnet port of your router. Default is 23.
33+
- **username** (*Required*): The username to login into the router (user should have read access to telnet interface of the router).
3334
- **password** (*Required*): The password for the specified username.
3435
- **interface** (*Optional*): Ihe internal name of the interface to get devices connected to. Default is 'Home'. For expert users only.
3536

‎source/_components/device_tracker.ritassist.markdown

Lines changed: 82 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
---
2+
layout: page
3+
title: "RitAssist"
4+
description: "Instructions on how to use a RitAssist as a device tracker."
5+
date: 2018-06-15 22:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: ritassist.png
11+
ha_category: Presence Detection
12+
ha_iot_class: Cloud Polling
13+
ha_release: 0.76
14+
---
15+
16+
This platform allows you to integrate your vehicles equipped with [RitAssist](https://ritassist.nl/) or [FleetGO](https://fleetgo.com) hardware into Home Assistant. It allows you to see certain details about your vehicle, but also shows your vehicle on the map.
17+
18+
## API key
19+
To use this component, you need an **API key** and **API secret**, which can be requested by contacting [info@fleetgo.com](mailto:info@fleetgo.com?subject=API%20Key).
20+
21+
## Configuration
22+
To use this device tracker in your installation, add the following to your `configuration.yaml` file:
23+
24+
```yaml
25+
# Example configuration.yaml entry
26+
device_tracker:
27+
- platform: ritassist
28+
client_id: YOUR_CLIENT_ID
29+
client_secret: YOUR_CLIENT_SECRET
30+
username: YOUR_RITASSIST_USERNAME
31+
password: YOUR_RITASSIST_PASSWORD
32+
include:
33+
- LICENSE_PLATE
34+
```
35+
36+
{% configuration %}
37+
client_id:
38+
description: The client ID used to connect to the RitAssist API.
39+
required: true
40+
type: string
41+
client_secret:
42+
description: The client secret used to connect to the RitAssist API.
43+
required: true
44+
type: string
45+
username:
46+
description: Your RitAssist username.
47+
required: true
48+
type: string
49+
password:
50+
description: Your RitAssist password.
51+
required: true
52+
type: string
53+
include:
54+
description: A list of license plates to include, if this is not specified, all vehicles will be added.
55+
required: false
56+
type: strings
57+
{% endconfiguration %}
58+
59+
See the [device tracker component page](/components/device_tracker/) for instructions on how to configure the people to be tracked.
60+
61+
## Available Attributes
62+
63+
| Attribute | Description |
64+
|---|---|
65+
| latitude | The latitude of your vehicle |
66+
| longitude | The longitude of your vehicle |
67+
| altitude | Altitude of your vehicle |
68+
| id | Identifier used to identify your vehicle |
69+
| make | The make of the vehicle |
70+
| model | Model of your vehicle |
71+
| license_plate | License plate number |
72+
| active | If the engine is currently active or not |
73+
| odo | The odometer in kilometers |
74+
| speed | The current speed of your vehicle, in KM/h |
75+
| last_seen | The date and time when your vehicle last communicated with the API |
76+
| fuel_level | Fuel level of the vehicle [1] |
77+
| malfunction_light | Are any malfunction lights burning [1] |
78+
| coolant_temperature | Temperature of the coolant [1] |
79+
| power_voltage | Power voltage measured by the hardware [1] |
80+
| distance_from_home | How far is your vehicle located from your Home Assistant Home location |
81+
82+
[1] Only available on certain cars and hardware revisions.

‎source/_components/discovery.markdown

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
2121
* [Bose Soundtouch speakers](/components/media_player.soundtouch/)
2222
* [Denon network receivers](/components/media_player.denonavr/)
2323
* [DirecTV receivers](/components/media_player.directv/)
24+
* [DLNA DMR enabled devices](/components/media_player.dlna_dmr/)
2425
* [Frontier Silicon internet radios](/components/media_player.frontier_silicon/)
2526
* [Google Cast](/components/media_player.cast/)
2627
* [HomeKit](/components/homekit_controller/)
@@ -79,6 +80,7 @@ Valid values for ignore are:
7980
* `bose_soundtouch`: Bose Soundtouch speakers
8081
* `denonavr`: Denon network receivers
8182
* `directv`: DirecTV receivers
83+
* `dlna`: DLNA DMR enabled devices
8284
* `frontier_silicon`: Frontier Silicon internet radios
8385
* `google_cast`: Google Cast
8486
* `harmony`: Logitech Harmony Hub

‎source/_components/fan.dyson.markdown

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,3 +22,12 @@ You have first to setup the [Dyson component](/components/dyson/)
2222

2323
- Pure Cool link (desk and tower)
2424
- Pure Hot+cool link (but heating is not yet supported)
25+
26+
### {% linkable_title Attributes %}
27+
28+
The are several attributes that can be useful for automations and templates.
29+
30+
| Attribute | Description |
31+
| --------- | ----------- |
32+
| `is_night_mode` | A boolean that indicates if the night mode of the fan device is on.
33+
| `is_auto_mode` | A boolean that indicates if the auto mode of the fan device is on.

‎source/_components/fan.velbus.markdown

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

0 commit comments

Comments
 (0)