Skip to content

Commit ebcfa2b

Browse files
fabafffabaff
committed
Merge branch 'current' into next
2 parents 8c18f6a + 9cdfdc8 commit ebcfa2b

File tree

11 files changed

+717
-11
lines changed

11 files changed

+717
-11
lines changed

‎_config.yml

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

139139
# Home Assistant release details
140140
current_major_version: 0
141-
current_minor_version: 87
142-
current_patch_version: 1
143-
date_released: 2019-02-10
141+
current_minor_version: 88
142+
current_patch_version: 0
143+
date_released: 2019-02-20
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.

‎source/_components/default_config.markdown

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
layout: page
3+
title: "Default Config"
4+
description: "The default config component will initate a default configuration for Home Assistant."
5+
date: 2019-02-15 20:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: home-assistant.png
11+
ha_category: Other
12+
ha_release: 0.88
13+
featured: false
14+
---
15+
16+
This component is a meta-component and configures a default set of components for Home Assistant to load. The components that will be loaded can be found [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/default_config/__init__.py).

‎source/_components/ebusd.markdown

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,11 @@ sidebar: true
77
comments: false
88
sharing: true
99
footer: true
10-
logo: ebusd.png
1110
ha_category: Sensor
1211
ha_iot_class: "Local Polling"
1312
ha_release: "0.88"
13+
redirect_from:
14+
- /components/sensor.ebusd/
1415
---
1516

1617
Integration between [ebusd](https://github.com/john30/ebusd/) daemon for communication with eBUS heating systems, and Home Assistant using sensor component.
@@ -31,7 +32,7 @@ host:
3132
description: This is the IP address of your ebus daemon, e.g., `127.0.0.1`.
3233
required: true
3334
type: string
34-
circuit:
35+
circuit:
3536
description: The heating circuit name to monitor, e.g., 700.
3637
required: true
3738
type: string
@@ -40,7 +41,7 @@ port:
4041
type: integer
4142
required: false
4243
default: 8888
43-
name:
44+
name:
4445
description: The name to use when displaying this ebusd instance.
4546
type: string
4647
required: false

‎source/_components/remote.harmony.markdown renamed to ‎source/_components/harmony.markdown

File renamed without changes.

‎source/_components/weather.ipma.markdown renamed to ‎source/_components/ipma.markdown

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ logo: ipma.png
1111
ha_category: Weather
1212
ha_release: 0.72
1313
ha_iot_class: "Cloud Polling"
14+
redirect_from:
15+
- /components/weather.ipma/
1416
---
1517

1618
The `ipma` weather platform uses the [Instituto Português do Mar e Atmosfera](http://www.ipma.pt) as a source for current and forecast meteorological data.

‎source/_components/person.markdown

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,11 @@ ha_release: 0.88
1515

1616
The person component allows to connect device tracker entities to one or more person entities. The last state update of a connected device tracker will set the state of the person. Eg if you connect your router and your owntracks device as trackers to your person, the last state update from either the router or your owntracks device will set the state of your person.
1717

18-
## {% linkable_title Configuring the `person` component %}
18+
You can manage persons via the UI from the person page inside the configuration panel.
1919

20-
To get started add the following lines to your `configuration.yaml`:
20+
## {% linkable_title Configuring the `person` component via YAML %}
21+
22+
If you prefer YAML, you can also configure your persons via `configuration.yaml`:
2123

2224
```yaml
2325
# Example configuration.yaml entry

‎source/_components/velux.markdown

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ ha_release: 0.49
1515
ha_iot_class: "Local Polling"
1616
redirect_from:
1717
- /components/scene.velux/
18+
- /components/cover.velux/
1819
---
1920

2021
[Velux](http://www.velux.com) integration for Home Assistant allows you to connect to a Velux KLF 200 interface, to control [io-homecontrol](http://www.io-homecontrol.com) devices like windows and blinds. The module allows you to start scenes configured within KLF 200.

‎source/_components/xs1.markdown

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,18 @@ comments: false
88
sharing: true
99
footer: true
1010
logo: xs1.jpg
11-
ha_category:
11+
ha_category:
1212
- Hub
1313
- Climate
1414
- Sensor
1515
- Switch
1616
ha_release: 0.88
1717
featured: false
1818
ha_iot_class: "Local Polling"
19+
redirect_from:
20+
- /components/climate.xs1/
21+
- /components/sensor.xs1/
22+
- /components/switch.xs1/
1923
---
2024

2125
The [EZcontrol XS1](http://www.ezcontrol.de/content/view/36/28/) integration for Home Assistant allows you to observe and control devices configured on the XS1 Gateway. Please have a look at the official docs for using this gateway [Bedienungsanleitung v3.0.0.0](http://www.ezcontrol.de/support/downloads/XS1/xs1manual/Bedienungsanleitung_EZcontrol_XS1_3.0.0.0-2.pdf).
@@ -78,8 +82,8 @@ If you are using climate devices the "current temp" sensor will be automatically
7882
| `switch` | Yes | |
7983
| `dimmer` | Partly | Dimmers are currently handled like switches so actual dimming is not supported :(|
8084
| `temperature` | Yes | |
81-
82-
85+
86+
8387
### {% linkable_title Climate Actuator/Sensor%}
8488

8589
Home Assistant can combine temperature sensors and climate actuators into a single device. The XS1 gateway does not allow this, but a sensor and actuator can be configured separately. To make Home Assistant register them in the same climate device just prefix the **sensor** name with the actuator name on the XS1 gateway configuration, f.ex:

0 commit comments

Comments
 (0)