From 3f1fd2a25137fb97bfffa7d64cabc2fdd4cfccad Mon Sep 17 00:00:00 2001
From: Erik Montnemery
Date: Thu, 9 May 2019 16:43:41 +0200
Subject: [PATCH 001/123] Update trigger.markdown
---
source/_docs/automation/trigger.markdown | 22 ++++++++++++++--------
1 file changed, 14 insertions(+), 8 deletions(-)
diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown
index b892651b895..bd42db25035 100644
--- a/source/_docs/automation/trigger.markdown
+++ b/source/_docs/automation/trigger.markdown
@@ -130,9 +130,10 @@ automation:
### {% linkable_title Sun trigger %}
-Triggers when the sun is setting or rising. An optional time offset can be given to have it trigger a set time before or after the sun event (i.e. 45 minutes before sunset, when dusk is setting in).
+#### Sunset / Sunrise trigger
+Triggers when the sun is setting or rising, i.e. when the sun elevation reaches 0°.
-Sunrise as a trigger may need special attention as explained in time triggers below. This is due to the date changing at midnight and sunrise is at an earlier time on the following day.
+An optional time offset can be given to have it trigger a set time before or after the sun event (e.g. 45 minutes before sunset). Since the duration of twilight is different throughout the year, it is recommended to use sun elevation triggers instead of `sunset` or `sunrise` with a time offset to trigger automations at the start of dusk or dawn.
```yaml
automation:
@@ -140,11 +141,12 @@ automation:
platform: sun
# Possible values: sunset, sunrise
event: sunset
- # Optional time offset. This example is 45 minutes.
+ # Optional time offset. This example will trigger 45 minutes before sunrise.
offset: '-00:45:00'
```
-Sometimes you may want more granular control over an automation based on the elevation of the sun. This can be used to layer automations to occur as the sun lowers on the horizon or even after it is below the horizon. This is also useful when the "sunset" event is not dark enough outside and you would like the automation to run later at a precise solar angle instead of the time offset such as turning on exterior lighting. For most things, a general number like -4 degrees is suitable and is used in this example:
+#### Sun elevation trigger
+Sometimes you may want more granular control over an automation than simply sunset or sunrise and specify an exact elevation of the sun. This can be used to layer automations to occur as the sun lowers on the horizon or even after it is below the horizon. This is also useful when the "sunset" event is not dark enough outside and you would like the automation to run later at a precise solar angle instead of the time offset such as turning on exterior lighting. For most things intended to trigger during dusk or dawn, a number between 0° and -6° is suitable; -4° is used in this example:
{% raw %}
```yaml
@@ -162,11 +164,15 @@ automation:
```
{% endraw %}
-If you want to get more precise, start with the US Naval Observatory [tool](http://aa.usno.navy.mil/data/docs/AltAz.php) that will help you estimate what the solar angle will be at any specific time. Then from this, you can select from the defined twilight numbers. Although the actual amount of light depends on weather, topography and land cover, they are defined as:
+If you want to get more precise, start with the US Naval Observatory [tool](http://aa.usno.navy.mil/data/docs/AltAz.php) which will help you estimate what the solar elevation will be at any specific time. Then from this, you can select from the defined twilight numbers.
-- Civil twilight: Solar angle > -6°
-- Nautical twilight: Solar angle > -12°
-- Astronomical twilight: Solar angle > -18°
+Although the actual amount of light depends on weather, topography and land cover, they are defined as:
+
+- Civil twilight: 0° > Solar angle > -6°
+
+ This is what is meant by twilight for the average person: Under clear weather conditions, civil twilight approximates the limit at which solar illumination suffices for the human eye to clearly distinguish terrestrial objects. Enough illumination renders artificial sources unnecessary for most outdoor activities.
+- Nautical twilight: 6° > Solar angle > -12°
+- Astronomical twilight: 12° > Solar angle > -18°
A very thorough explanation of this is available in the Wikipedia article about the [Twilight](https://en.wikipedia.org/wiki/Twilight).
From ab4e93af8b0322a142412642302c1da137600e47 Mon Sep 17 00:00:00 2001
From: Erik Montnemery
Date: Thu, 9 May 2019 17:17:22 +0200
Subject: [PATCH 002/123] Update conditions.markdown
---
source/_docs/scripts/conditions.markdown | 44 +++++++++++++++++++++++-
1 file changed, 43 insertions(+), 1 deletion(-)
diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown
index ed261f6c874..c34a5b9ba62 100644
--- a/source/_docs/scripts/conditions.markdown
+++ b/source/_docs/scripts/conditions.markdown
@@ -119,11 +119,53 @@ condition:
```
### {% linkable_title Sun condition %}
+#### Sun state condition
+The sun state can be used to test if the sun has set or risen.
-The sun condition can test if the sun has already set or risen when a trigger occurs. The `before` and `after` keys can only be set to `sunset` or `sunrise`. They have a corresponding optional offset value (`before_offset`, `after_offset`) that can be added, similar to the [sun trigger][sun_trigger].
+```yaml
+condition:
+ condition: state # 'day' condition: from sunrise until sunset
+ entity_id: sun.sun
+ state: 'above_horizon'
+```
+```yaml
+condition:
+ condition: state # from sunset until sunrise
+ entity_id: sun.sun
+ state: 'below_horizon'
+```
+
+#### Sun elevation condition
+The sun elevation can be used to test if the sun has set or risen, it is dusk, it is night etc. when a trigger occurs.
+For an in depth explanation of sun elevation see [sun trigger][sun_trigger].
+
+```yaml
+condition:
+ condition: and # 'twilight' condition: dusk and dawn, in typical locations
+ conditions:
+ - condition: template
+ value_template: '{{ states.sun.sun.attributes.elevation < 0 }}'
+ - condition: template
+ value_template: '{{ states.sun.sun.attributes.elevation > -6 }}'
+```
+
+```yaml
+condition:
+ condition: template # 'night' condition: from dusk to dawn, in typical locations
+ value_template: '{{ states.sun.sun.attributes.elevation < -6 }}'
+```
+
+#### Sunset/sunrise condition
+The sun condition can also test if the sun has already set or risen when a trigger occurs. The `before` and `after` keys can only be set to `sunset` or `sunrise`. They have a corresponding optional offset value (`before_offset`, `after_offset`) that can be added, similar to the [sun trigger][sun_trigger].
[sun_trigger]: /docs/automation/trigger/#sun-trigger
+
+The sunset/sunrise conditions do not work in locations inside the polar circles, and also not in locations with highly skewed local time zone.
+
+It is advised to use conditions evaluating the solar elevation instead of the before/after sunset/sunrise conditions.
+
+
```yaml
condition:
condition: sun
From 3c2026d68362600219dff15cf1b15c09c082aba4 Mon Sep 17 00:00:00 2001
From: Erik Montnemery
Date: Thu, 9 May 2019 19:03:32 +0200
Subject: [PATCH 003/123] Update conditions.markdown
---
source/_docs/scripts/conditions.markdown | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown
index c34a5b9ba62..db552067b5d 100644
--- a/source/_docs/scripts/conditions.markdown
+++ b/source/_docs/scripts/conditions.markdown
@@ -145,15 +145,15 @@ condition:
condition: and # 'twilight' condition: dusk and dawn, in typical locations
conditions:
- condition: template
- value_template: '{{ states.sun.sun.attributes.elevation < 0 }}'
+ value_template: {% raw %}'{{ states.sun.sun.attributes.elevation < 0 }}'{% endraw %}
- condition: template
- value_template: '{{ states.sun.sun.attributes.elevation > -6 }}'
+ value_template: {% raw %}'{{ states.sun.sun.attributes.elevation > -6 }}'{% endraw %}
```
```yaml
condition:
condition: template # 'night' condition: from dusk to dawn, in typical locations
- value_template: '{{ states.sun.sun.attributes.elevation < -6 }}'
+ value_template: {% raw %}'{{ states.sun.sun.attributes.elevation < -6 }}'{% endraw %}
```
#### Sunset/sunrise condition
From 4ae0644122c4bca89670e4daace4d0c6c2d6ba5f Mon Sep 17 00:00:00 2001
From: Erik Montnemery
Date: Fri, 10 May 2019 15:10:13 +0200
Subject: [PATCH 004/123] Update trigger.markdown
---
source/_docs/automation/trigger.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown
index bd42db25035..7fa85f880d7 100644
--- a/source/_docs/automation/trigger.markdown
+++ b/source/_docs/automation/trigger.markdown
@@ -130,7 +130,7 @@ automation:
### {% linkable_title Sun trigger %}
-#### Sunset / Sunrise trigger
+#### {% linkable_title Sunset / Sunrise trigger %}
Triggers when the sun is setting or rising, i.e. when the sun elevation reaches 0°.
An optional time offset can be given to have it trigger a set time before or after the sun event (e.g. 45 minutes before sunset). Since the duration of twilight is different throughout the year, it is recommended to use sun elevation triggers instead of `sunset` or `sunrise` with a time offset to trigger automations at the start of dusk or dawn.
@@ -145,7 +145,7 @@ automation:
offset: '-00:45:00'
```
-#### Sun elevation trigger
+#### {% linkable_title Sun elevation trigger %}
Sometimes you may want more granular control over an automation than simply sunset or sunrise and specify an exact elevation of the sun. This can be used to layer automations to occur as the sun lowers on the horizon or even after it is below the horizon. This is also useful when the "sunset" event is not dark enough outside and you would like the automation to run later at a precise solar angle instead of the time offset such as turning on exterior lighting. For most things intended to trigger during dusk or dawn, a number between 0° and -6° is suitable; -4° is used in this example:
{% raw %}
From 147513b7c7c947ddb543af01dc4821fedcb48129 Mon Sep 17 00:00:00 2001
From: Erik Montnemery
Date: Fri, 10 May 2019 15:13:02 +0200
Subject: [PATCH 005/123] Update conditions.markdown
---
source/_docs/scripts/conditions.markdown | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown
index db552067b5d..5f9848af2de 100644
--- a/source/_docs/scripts/conditions.markdown
+++ b/source/_docs/scripts/conditions.markdown
@@ -119,7 +119,7 @@ condition:
```
### {% linkable_title Sun condition %}
-#### Sun state condition
+#### {% linkable_title Sun state condition %}
The sun state can be used to test if the sun has set or risen.
```yaml
@@ -136,9 +136,10 @@ condition:
state: 'below_horizon'
```
-#### Sun elevation condition
+#### {% linkable_title Sun elevation condition %}
The sun elevation can be used to test if the sun has set or risen, it is dusk, it is night etc. when a trigger occurs.
-For an in depth explanation of sun elevation see [sun trigger][sun_trigger].
+For an in depth explanation of sun elevation see [sun elevation trigger][sun_elevation_trigger].
+[sun_elevation_trigger]: /docs/automation/trigger/#sun-elevation-trigger
```yaml
condition:
@@ -156,7 +157,7 @@ condition:
value_template: {% raw %}'{{ states.sun.sun.attributes.elevation < -6 }}'{% endraw %}
```
-#### Sunset/sunrise condition
+#### {% linkable_title Sunset/sunrise condition %}
The sun condition can also test if the sun has already set or risen when a trigger occurs. The `before` and `after` keys can only be set to `sunset` or `sunrise`. They have a corresponding optional offset value (`before_offset`, `after_offset`) that can be added, similar to the [sun trigger][sun_trigger].
[sun_trigger]: /docs/automation/trigger/#sun-trigger
From 60a7ead71a5a05807601dd15e00b93b2ba132224 Mon Sep 17 00:00:00 2001
From: Erik Montnemery
Date: Fri, 10 May 2019 17:21:23 +0200
Subject: [PATCH 006/123] Fix links.
---
source/_docs/scripts/conditions.markdown | 2 ++
1 file changed, 2 insertions(+)
diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown
index 5f9848af2de..f44b97ebebf 100644
--- a/source/_docs/scripts/conditions.markdown
+++ b/source/_docs/scripts/conditions.markdown
@@ -139,6 +139,7 @@ condition:
#### {% linkable_title Sun elevation condition %}
The sun elevation can be used to test if the sun has set or risen, it is dusk, it is night etc. when a trigger occurs.
For an in depth explanation of sun elevation see [sun elevation trigger][sun_elevation_trigger].
+
[sun_elevation_trigger]: /docs/automation/trigger/#sun-elevation-trigger
```yaml
@@ -159,6 +160,7 @@ condition:
#### {% linkable_title Sunset/sunrise condition %}
The sun condition can also test if the sun has already set or risen when a trigger occurs. The `before` and `after` keys can only be set to `sunset` or `sunrise`. They have a corresponding optional offset value (`before_offset`, `after_offset`) that can be added, similar to the [sun trigger][sun_trigger].
+
[sun_trigger]: /docs/automation/trigger/#sun-trigger
From 29f5b7f94775345512aefd511658a079e0fc8aa7 Mon Sep 17 00:00:00 2001
From: Erik Montnemery
Date: Fri, 10 May 2019 17:36:49 +0200
Subject: [PATCH 007/123] Update trigger.markdown
---
source/_docs/automation/trigger.markdown | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown
index 7fa85f880d7..b75ee3db9c5 100644
--- a/source/_docs/automation/trigger.markdown
+++ b/source/_docs/automation/trigger.markdown
@@ -133,7 +133,13 @@ automation:
#### {% linkable_title Sunset / Sunrise trigger %}
Triggers when the sun is setting or rising, i.e. when the sun elevation reaches 0°.
-An optional time offset can be given to have it trigger a set time before or after the sun event (e.g. 45 minutes before sunset). Since the duration of twilight is different throughout the year, it is recommended to use sun elevation triggers instead of `sunset` or `sunrise` with a time offset to trigger automations at the start of dusk or dawn.
+An optional time offset can be given to have it trigger a set time before or after the sun event (e.g. 45 minutes before sunset).
+
+
+Since the duration of twilight is different throughout the year, it is recommended to use [sun elevation triggers][sun_elevation_trigger] instead of `sunset` or `sunrise` with a time offset to trigger automations during dusk or dawn.
+
+
+[sun_elevation_trigger]: /docs/automation/trigger/#sun-elevation-trigger
```yaml
automation:
From fc34628a3b1386263615b1cc830240ff790f2911 Mon Sep 17 00:00:00 2001
From: tube0013
Date: Mon, 20 May 2019 11:05:52 -0400
Subject: [PATCH 008/123] Add Host ModemManager fix
---
source/_components/zha.markdown | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/source/_components/zha.markdown b/source/_components/zha.markdown
index 79df7194824..2b2d6019ebe 100644
--- a/source/_components/zha.markdown
+++ b/source/_components/zha.markdown
@@ -102,3 +102,8 @@ enable_quirks:
To add new devices to the network, call the `permit` service on the `zha` domain. Do this by clicking the Service icon in Developer tools and typing `zha.permit` in the **Service** dropdown box. Next, follow the device instructions for adding, scanning or factory reset.
In case you want to add Philips Hue bulbs that have previously been added to another bridge, have a look at: [https://github.com/vanviegen/hue-thief/](https://github.com/vanviegen/hue-thief/)
+
+
+## {% linkable_title ZHA Start up issue with Home-Assistant Docker/Hass.io installs on linux hosts %}
+
+On Linux hosts ZHA can fail to start during HA startup or restarts because the HUSBZB-1 device is being claimed by the host's modemmanager service. To fix this disable the modemmanger on the host system.
From 59bc6f1777af8326bdb6577ad6fb9f46b6af26e0 Mon Sep 17 00:00:00 2001
From: Klaas Schoute
Date: Mon, 20 May 2019 17:29:34 +0200
Subject: [PATCH 009/123] :pencil2: Tweak
---
source/_components/zha.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_components/zha.markdown b/source/_components/zha.markdown
index 2b2d6019ebe..2ef214ad062 100644
--- a/source/_components/zha.markdown
+++ b/source/_components/zha.markdown
@@ -106,4 +106,4 @@ In case you want to add Philips Hue bulbs that have previously been added to ano
## {% linkable_title ZHA Start up issue with Home-Assistant Docker/Hass.io installs on linux hosts %}
-On Linux hosts ZHA can fail to start during HA startup or restarts because the HUSBZB-1 device is being claimed by the host's modemmanager service. To fix this disable the modemmanger on the host system.
+On Linux hosts ZHA can fail to start during HA startup or restarts because the HUSBZB-1 device is being claimed by the host's modemmanager service. To fix this disable the modemmanger on the host system.
From 161194978442f9f00fc67b5f6e3ed87cf6536433 Mon Sep 17 00:00:00 2001
From: tube0013
Date: Tue, 21 May 2019 09:19:44 -0400
Subject: [PATCH 010/123] Add @newlund suggested changes
---
source/_components/zha.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_components/zha.markdown b/source/_components/zha.markdown
index 2ef214ad062..7835c397cee 100644
--- a/source/_components/zha.markdown
+++ b/source/_components/zha.markdown
@@ -106,4 +106,4 @@ In case you want to add Philips Hue bulbs that have previously been added to ano
## {% linkable_title ZHA Start up issue with Home-Assistant Docker/Hass.io installs on linux hosts %}
-On Linux hosts ZHA can fail to start during HA startup or restarts because the HUSBZB-1 device is being claimed by the host's modemmanager service. To fix this disable the modemmanger on the host system.
+On Linux hosts ZHA can fail to start during HA startup or restarts because the zigbee USB device is being claimed by the host's modemmanager service. To fix this disable the modemmanger on the host system.
From cbf66444fa0acde7781f6c7954b661548ae081aa Mon Sep 17 00:00:00 2001
From: tube0013
Date: Thu, 23 May 2019 13:02:47 -0400
Subject: [PATCH 011/123] Add command to remove modemmanger from host
---
source/_components/zha.markdown | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/source/_components/zha.markdown b/source/_components/zha.markdown
index 7835c397cee..9f7a3e08441 100644
--- a/source/_components/zha.markdown
+++ b/source/_components/zha.markdown
@@ -107,3 +107,8 @@ In case you want to add Philips Hue bulbs that have previously been added to ano
## {% linkable_title ZHA Start up issue with Home-Assistant Docker/Hass.io installs on linux hosts %}
On Linux hosts ZHA can fail to start during HA startup or restarts because the zigbee USB device is being claimed by the host's modemmanager service. To fix this disable the modemmanger on the host system.
+
+To remove modemmanager from an Debian/Ubuntu host run this command:
+```
+sudo apt-get purge modemmanager
+```
From e0ca456f9ad0bc1f0757c029891653218497ce97 Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Wed, 29 May 2019 14:29:34 -0700
Subject: [PATCH 012/123] Add stub release notes 94
---
_config.yml | 6 +++---
source/_posts/2019-06-05-release-94.markdown | 20 ++++++++++++++++++++
2 files changed, 23 insertions(+), 3 deletions(-)
create mode 100644 source/_posts/2019-06-05-release-94.markdown
diff --git a/_config.yml b/_config.yml
index d5aa5c751ed..7cfd2697f1a 100644
--- a/_config.yml
+++ b/_config.yml
@@ -138,9 +138,9 @@ social:
# Home Assistant release details
current_major_version: 0
-current_minor_version: 93
-current_patch_version: 2
-date_released: 2019-05-22
+current_minor_version: 94
+current_patch_version: 0
+date_released: 2019-06-05
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.
diff --git a/source/_posts/2019-06-05-release-94.markdown b/source/_posts/2019-06-05-release-94.markdown
new file mode 100644
index 00000000000..01afef59b73
--- /dev/null
+++ b/source/_posts/2019-06-05-release-94.markdown
@@ -0,0 +1,20 @@
+---
+layout: post
+title: "0.94: TBD - update date"
+description: "TO DO."
+date: 2019-05-29 04:11:03
+date_formatted: "June 5, 2019"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2019-06-release-94/components.png
+---
+
+
+
+New:
+ - Possible to store core config in storage. Configuration.yaml will override storage.
+ - Onboarding updated to set core config
+ - Python 3.5.3 deprecated, support will be dropped in the first release after August 1.
+ - More cool stuff?
From aec551668fe6ec52c136d0d8562e6c490e45cb91 Mon Sep 17 00:00:00 2001
From: Klaas Schoute
Date: Thu, 30 May 2019 00:09:16 +0200
Subject: [PATCH 013/123] :pencil2: Tweak
---
source/_docs/automation/trigger.markdown | 2 ++
1 file changed, 2 insertions(+)
diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown
index b75ee3db9c5..0fc3d9991d6 100644
--- a/source/_docs/automation/trigger.markdown
+++ b/source/_docs/automation/trigger.markdown
@@ -131,6 +131,7 @@ automation:
### {% linkable_title Sun trigger %}
#### {% linkable_title Sunset / Sunrise trigger %}
+
Triggers when the sun is setting or rising, i.e. when the sun elevation reaches 0°.
An optional time offset can be given to have it trigger a set time before or after the sun event (e.g. 45 minutes before sunset).
@@ -152,6 +153,7 @@ automation:
```
#### {% linkable_title Sun elevation trigger %}
+
Sometimes you may want more granular control over an automation than simply sunset or sunrise and specify an exact elevation of the sun. This can be used to layer automations to occur as the sun lowers on the horizon or even after it is below the horizon. This is also useful when the "sunset" event is not dark enough outside and you would like the automation to run later at a precise solar angle instead of the time offset such as turning on exterior lighting. For most things intended to trigger during dusk or dawn, a number between 0° and -6° is suitable; -4° is used in this example:
{% raw %}
From a3b76fb3ed47f29217b46942bb8ef74ebe71611d Mon Sep 17 00:00:00 2001
From: Klaas Schoute
Date: Thu, 30 May 2019 00:10:30 +0200
Subject: [PATCH 014/123] :pencil2: Tweak
---
source/_docs/scripts/conditions.markdown | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown
index f44b97ebebf..26968f97601 100644
--- a/source/_docs/scripts/conditions.markdown
+++ b/source/_docs/scripts/conditions.markdown
@@ -119,7 +119,9 @@ condition:
```
### {% linkable_title Sun condition %}
+
#### {% linkable_title Sun state condition %}
+
The sun state can be used to test if the sun has set or risen.
```yaml
@@ -137,6 +139,7 @@ condition:
```
#### {% linkable_title Sun elevation condition %}
+
The sun elevation can be used to test if the sun has set or risen, it is dusk, it is night etc. when a trigger occurs.
For an in depth explanation of sun elevation see [sun elevation trigger][sun_elevation_trigger].
@@ -159,6 +162,7 @@ condition:
```
#### {% linkable_title Sunset/sunrise condition %}
+
The sun condition can also test if the sun has already set or risen when a trigger occurs. The `before` and `after` keys can only be set to `sunset` or `sunrise`. They have a corresponding optional offset value (`before_offset`, `after_offset`) that can be added, similar to the [sun trigger][sun_trigger].
[sun_trigger]: /docs/automation/trigger/#sun-trigger
From c66f2ee4b5c9eb2da23c74cfb8114332be2fef73 Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Wed, 29 May 2019 15:15:35 -0700
Subject: [PATCH 015/123] Add some more notes
---
source/_posts/2019-06-05-release-94.markdown | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/source/_posts/2019-06-05-release-94.markdown b/source/_posts/2019-06-05-release-94.markdown
index 01afef59b73..001bcee87d1 100644
--- a/source/_posts/2019-06-05-release-94.markdown
+++ b/source/_posts/2019-06-05-release-94.markdown
@@ -14,7 +14,9 @@ og_image: /images/blog/2019-06-release-94/components.png
New:
- - Possible to store core config in storage. Configuration.yaml will override storage.
- - Onboarding updated to set core config
+ - Possible to store core config in storage. If set in configuration.yaml, it will override storage. Note that configuration.yaml will no longer contain any automatic detected values when writing initial configuration. This feature is available via the UI during onboarding.
+ - Step added to onboarding to allow configuring name, location, timezone and unit system.
- Python 3.5.3 deprecated, support will be dropped in the first release after August 1.
+ - Add UI to manage Google Entities exposed via Home Assistant Cloud. To use, remove filters from configuration.yaml. Also allows disabling 2 factor authentication on a per device basis.
+ - Discovery has been redone. Integrations can now specify how they are discoverable via Zeroconf or SSDP in their manifest, this will be picked up by the zeroconf and ssdp integrations.
- More cool stuff?
From 07fa2b4128fe2fb1ab2c920af357e6e8253e9f77 Mon Sep 17 00:00:00 2001
From: Klaas Schoute
Date: Thu, 30 May 2019 00:16:44 +0200
Subject: [PATCH 016/123] :pencil2: Tweak
---
source/_components/zha.markdown | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/source/_components/zha.markdown b/source/_components/zha.markdown
index 9f7a3e08441..2355771d4bc 100644
--- a/source/_components/zha.markdown
+++ b/source/_components/zha.markdown
@@ -103,12 +103,14 @@ To add new devices to the network, call the `permit` service on the `zha` domain
In case you want to add Philips Hue bulbs that have previously been added to another bridge, have a look at: [https://github.com/vanviegen/hue-thief/](https://github.com/vanviegen/hue-thief/)
+## {% linkable_title Troubleshooting %}
-## {% linkable_title ZHA Start up issue with Home-Assistant Docker/Hass.io installs on linux hosts %}
+### {% linkable_title ZHA Start up issue with Home-Assistant Docker/Hass.io installs on linux hosts %}
On Linux hosts ZHA can fail to start during HA startup or restarts because the zigbee USB device is being claimed by the host's modemmanager service. To fix this disable the modemmanger on the host system.
To remove modemmanager from an Debian/Ubuntu host run this command:
-```
+
+```bash
sudo apt-get purge modemmanager
```
From 5383bce4d6e2a785a48057355bd409aba7477c5e Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Wed, 29 May 2019 19:52:54 -0700
Subject: [PATCH 017/123] Update release notes
---
source/_posts/2019-06-05-release-94.markdown | 460 +++++++++++++++++++
1 file changed, 460 insertions(+)
diff --git a/source/_posts/2019-06-05-release-94.markdown b/source/_posts/2019-06-05-release-94.markdown
index 001bcee87d1..697bfb67c0b 100644
--- a/source/_posts/2019-06-05-release-94.markdown
+++ b/source/_posts/2019-06-05-release-94.markdown
@@ -20,3 +20,463 @@ New:
- Add UI to manage Google Entities exposed via Home Assistant Cloud. To use, remove filters from configuration.yaml. Also allows disabling 2 factor authentication on a per device basis.
- Discovery has been redone. Integrations can now specify how they are discoverable via Zeroconf or SSDP in their manifest, this will be picked up by the zeroconf and ssdp integrations.
- More cool stuff?
+
+## {% linkable_title New Integrations %}
+
+- Adding Watson TTS (IBM Cloud) ([@rutkai] - [#23299]) ([watson_tts docs]) (new-integration) (new-platform)
+- MCP23017 ([@jardiamj] - [#23127]) ([mcp23017 docs]) (new-integration) (new-platform)
+- Solax Inverter Sensor Component ([@squishykid] - [#22579]) ([solax docs]) (new-integration) (new-platform)
+- Add Remote RPi Component ([@jgriff2] - [#23518]) ([remote_rpi_gpio docs]) (new-integration) (new-platform)
+- Azure Event Hub history component ([@eavanvalkenburg] - [#23878]) ([azure_event_hub docs]) (new-integration)
+- Add SSDP integration ([@balloob] - [#24090]) ([default_config docs]) ([discovery docs]) ([hue docs]) ([ssdp docs]) ([zeroconf docs]) (new-integration)
+
+## {% linkable_title New Platforms %}
+
+- Add LCN climate platform ([@alengwenus] - [#22542]) ([lcn docs]) (new-platform)
+- Add incomfort climate and bump client ([@zxdavb] - [#23830]) ([incomfort docs]) (new-platform)
+- Add new SmartHab light and cover platform ([@outadoc] - [#21225]) ([smarthab docs]) (new-platform)
+- Add geniushub sensor and binary_sensor ([@zxdavb] - [#23811]) ([geniushub docs]) (new-platform)
+- Adding Watson TTS (IBM Cloud) ([@rutkai] - [#23299]) ([watson_tts docs]) (new-integration) (new-platform)
+- MCP23017 ([@jardiamj] - [#23127]) ([mcp23017 docs]) (new-integration) (new-platform)
+- Solax Inverter Sensor Component ([@squishykid] - [#22579]) ([solax docs]) (new-integration) (new-platform)
+- Add Remote RPi Component ([@jgriff2] - [#23518]) ([remote_rpi_gpio docs]) (new-integration) (new-platform)
+- Add Repetier-Server Component ([@MTrab] - [#21658]) ([repetier docs]) (new-platform)
+
+## {% linkable_title If you need help... %}
+
+...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+## {% linkable_title Reporting Issues %}
+
+Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
+
+
+
+## {% linkable_title Breaking Changes %}
+
+- Quiet the chatty sun.sun ([@Swamp-Ig] - [#23832]) ([sun docs]) (breaking change)
+- Doorbird Refactor ([@oblogic7] - [#23892]) ([doorbird docs]) (breaking change)
+- ESPHome component to use zeroconf discovery ([@Kane610] - [#24043]) ([esphome docs]) (breaking change)
+- Always update all Plex client types ([@jjlawren] - [#24038]) ([plex docs]) (breaking change)
+- Fix entity id naming when not using first install ([@tkjacobsen] - [#23606]) ([verisure docs]) (breaking change)
+- Update the name of Zestimate sensors ([@dreed47] - [#23770]) ([zestimate docs]) (breaking change)
+- Remove custom entity_id naming ([@jjlawren] - [#24072]) ([plex docs]) (breaking change)
+- Trådfri component to use new zeroconf discovery ([@Kane610] - [#24041]) ([discovery docs]) ([tradfri docs]) (breaking change)
+- Move Homekit controller component to user zeroconf discovery ([@Kane610] - [#24042]) ([discovery docs]) ([homekit_controller docs]) (breaking change)
+- Deprecate Python 3.5.3 ([@balloob] - [#24177]) (breaking change)
+
+## {% linkable_title All changes %}
+
+- Add Presence Detector Indoor to Homematic IP ([@SukramJ] - [#23755]) ([homematicip_cloud docs])
+- Split up yaml loaders into multiple files ([@ties] - [#23774])
+- Add config entry for IQVIA ([@bachya] - [#23765]) ([iqvia docs])
+- Add stepped volume to demo ([@elupus] - [#23759]) ([demo docs])
+- Add battery binary sensor to homematic ([@sander76] - [#23067]) ([homematic docs])
+- fix two times creating JWT headers. ([@pszafer] - [#23777]) ([html5 docs])
+- Bumped keenetic NDMS2 client version ([@foxel] - [#23786]) ([keenetic_ndms2 docs])
+- Add support for an external step in config flow ([@balloob] - [#23782])
+- Centralize geniushub updates ([@zxdavb] - [#23764]) ([geniushub docs])
+- Move tests to right folder ([@balloob] - [#23790])
+- Add LCN climate platform ([@alengwenus] - [#22542]) ([lcn docs]) (new-platform)
+- Bump venstarcolortouch to v0.7 ([@stbenjam] - [#23806]) ([venstar docs])
+- Upgrade youtube_dl to 2019.05.11 ([@fabaff] - [#23808]) ([media_extractor docs])
+- Bump pyotgw to 0.4b4, fix Opentherm Gateway name in manifest.json ([@mvn23] - [#23810]) ([opentherm_gw docs])
+- Fix patching right import ([@balloob] - [#23816])
+- Add incomfort climate and bump client ([@zxdavb] - [#23830]) ([incomfort docs]) (new-platform)
+- Make broadlink switch restore its state ([@akloeckner] - [#23829]) ([broadlink docs])
+- Catch import error when processing config ([@balloob] - [#23833])
+- Remove badges from README [skipci] ([@balloob] - [#23815])
+- HomeKit Controller: Adopt config entries for pairing with homekit accessories ([@Jc2k] - [#23825]) ([discovery docs]) ([homekit_controller docs])
+- Automatically generate config flow list ([@balloob] - [#23802])
+- Add new SmartHab light and cover platform ([@outadoc] - [#21225]) ([smarthab docs]) (new-platform)
+- Daikin adaptions for AirBase units ([@fredrike] - [#23734]) ([daikin docs])
+- Fix for battery device: new_device referenced before assignment. ([@sander76] - [#23793]) ([homematic docs])
+- Better handle large amounts of data being sent over WS ([@balloob] - [#23842]) ([camera docs]) ([lovelace docs]) ([media_player docs]) ([websocket_api docs])
+- Zeroconf - replace library ([@Kane610] - [#23835]) ([zeroconf docs])
+- WS: Improve service calling errors ([@balloob] - [#23840]) ([script docs]) ([websocket_api docs])
+- Allow deletion of automations and scripts ([@balloob] - [#23845]) ([config docs])
+- Use Cloudhooks for OwnTracks ([@balloob] - [#23847]) ([owntracks docs])
+- Fix aiohttp response serialize ([@balloob] - [#23858]) ([cloud docs])
+- Add geniushub sensor and binary_sensor ([@zxdavb] - [#23811]) ([geniushub docs]) (new-platform)
+- Quiet the chatty sun.sun ([@Swamp-Ig] - [#23832]) ([sun docs]) (breaking change)
+- Take code owner for sun.sun ([@Swamp-Ig] - [#23877]) ([sun docs])
+- Fix homekit test assert no messages ([@scop] - [#23856])
+- Restructure device tracker ([@balloob] - [#23862]) ([device_tracker docs])
+- Update Pynetgear to v0.6.1 ([@starkillerOG] - [#23886]) ([netgear docs])
+- Fix ecobee 3 homekit pairing ([@Jc2k] - [#23882]) ([homekit_controller docs])
+- Enable Homematic IP cloud climate device with HeatingThermostat only ([@SukramJ] - [#23776]) ([homematicip_cloud docs])
+- Load HA core config from storage ([@emontnemery] - [#23872])
+- Netatmo, handle offline device ([@Danielhiversen] - [#23907]) ([netatmo docs])
+- [WIP] Simplify zeroconf ([@robbiet480] - [#23890]) ([zeroconf docs])
+- Version bump insteonplm to 0.15.4 ([@nugget] - [#23918])
+- Fix bug when IQVIA API fails to return data ([@bachya] - [#23916]) ([iqvia docs])
+- Fix icons for homekit_controller sensors ([@Jc2k] - [#23921]) ([homekit_controller docs])
+- Fix additional IQVIA data bug ([@bachya] - [#23931]) ([iqvia docs])
+- Have homekit_controller use device registry ([@Jc2k] - [#23874]) ([homekit_controller docs])
+- Fix for non existing Daikin zones ([@fredrike] - [#23792]) ([daikin docs])
+- Fix fan rates for Daikin ([@fredrike] - [#23860]) ([daikin docs])
+- Added support for sensor other than temperature and humidity ([@Bouni] - [#23863]) ([spaceapi docs])
+- Add unit of measurement to Tautulli sensor ([@SiliconAvatar] - [#23873]) ([tautulli docs])
+- Update requests to 2.22.0 ([@BKPepe] - [#23958])
+- show battery level also when vacuum has no map support ([@adrianschroeter] - [#23947]) ([neato docs])
+- Upate xiaomi voltage parser, fix #23898 ([@Danielhiversen] - [#23962]) ([xiaomi_aqara docs])
+- Doorbird Refactor ([@oblogic7] - [#23892]) ([doorbird docs]) (breaking change)
+- Update russound_rio dependency to version 0.1.7 ([@wickerwaka] - [#23973]) ([russound_rio docs])
+- Adding Watson TTS (IBM Cloud) ([@rutkai] - [#23299]) ([watson_tts docs]) (new-integration) (new-platform)
+- Entity Cleanup on Z-Wave node removal ([@cgarwood] - [#23633]) ([zwave docs])
+- Use the timezone defined in Home Assistant when making the API call ([@ludeeus] - [#23284]) ([vasttrafik docs])
+- Updated non-blocking timout to 10 seconds for fixing timeout issues. ([@TomerFi] - [#23930]) ([switcher_kis docs])
+- Delete devices / entities when we remove a config entry. ([@Swamp-Ig] - [#23983])
+- Better handle file not found when loading YAML ([@balloob] - [#23908]) ([apns docs]) ([http docs])
+- daikin version bump ([@fredrike] - [#23991]) ([daikin docs])
+- Bump loopenergy library version - catches runtime exception. ([@pavoni] - [#23989]) ([loopenergy docs])
+- Update owner frontend integrations [skip ci] ([@balloob] - [#24001]) ([frontend docs]) ([lovelace docs]) ([panel_custom docs]) ([panel_iframe docs])
+- Axis IO-port support ([@Kane610] - [#23312]) ([axis docs])
+- Fire event when core config is updated ([@emontnemery] - [#23922])
+- Update CODEOWNERS ([@emontnemery] - [#24015])
+- Add websocket API for updating core config ([@emontnemery] - [#24009]) ([config docs])
+- Add geniushub sensors for issues ([@zxdavb] - [#23976]) ([geniushub docs])
+- Fix iterating over NoneType exception ([@iamtpage] - [#23648]) ([darksky docs])
+- bump geniushub-client to 0.4.9 ([@zxdavb] - [#24022]) ([geniushub docs])
+- Zeroconf discovery for config entries ([@Kane610] - [#23919]) ([axis docs]) ([zeroconf docs])
+- Improve yeelight imports ([@zewelor] - [#24020]) ([yeelight docs])
+- Downgrade Hue warning ([@balloob] - [#24033]) ([hue docs])
+- Ambiclimate test, mock ([@Danielhiversen] - [#24034])
+- Upgrade Mastodon.py to 1.4.2 ([@fabaff] - [#24004]) ([mastodon docs])
+- Require core config detection to be triggerd manually ([@balloob] - [#24019]) ([config docs]) ([onboarding docs])
+- Don't pass in loop ([@balloob] - [#23984])
+- Update ambiclimate library ([@Danielhiversen] - [#24049]) ([ambiclimate docs])
+- ESPHome component to use zeroconf discovery ([@Kane610] - [#24043]) ([esphome docs]) (breaking change)
+- Add support for available property for broadlink ([@Danielhiversen] - [#23981]) ([broadlink docs])
+- Always update all Plex client types ([@jjlawren] - [#24038]) ([plex docs]) (breaking change)
+- Convert stream source to method ([@balloob] - [#23905])
+- Fix entity id naming when not using first install ([@tkjacobsen] - [#23606]) ([verisure docs]) (breaking change)
+- Daikin airbase beta fixes ([@fredrike] - [#24050]) ([daikin docs])
+- Better logging of method used for ADB connection ([@JeffLIrion] - [#24037]) ([androidtv docs])
+- Fix zeroconf sorting ([@balloob] - [#24068])
+- Rfxtrx, add data types ([@Danielhiversen] - [#24066]) ([rfxtrx docs])
+- Update the name of Zestimate sensors ([@dreed47] - [#23770]) ([zestimate docs]) (breaking change)
+- Added possibility to define the data type of Homematic ([@p0l0] - [#24078]) ([homematic docs])
+- Add 'adb_response' attribute to Android TV / Fire TV ([@JeffLIrion] - [#23960]) ([androidtv docs])
+- Adjust logging ([@elupus] - [#24082])
+- Fix Hue bridge timeout ([@terual] - [#24084]) ([hue docs])
+- MCP23017 ([@jardiamj] - [#23127]) ([mcp23017 docs]) (new-integration) (new-platform)
+- Remove device tracker unnecessary separate except clause ([@elupus] - [#24081]) ([device_tracker docs])
+- Refactoring of LCN component ([@alengwenus] - [#23824]) ([lcn docs])
+- Update code owner for Xiaomi TV ([@simse] - [#24102]) ([xiaomi_tv docs])
+- Issue #23514 - fix invalid hue response ([@techfreek] - [#23909]) ([emulated_hue docs])
+- Config entry device tracker ([@balloob] - [#24040]) ([device_tracker docs]) ([geofency docs]) ([gpslogger docs]) ([icloud docs]) ([locative docs]) ([owntracks docs]) ([zone docs])
+- Solax Inverter Sensor Component ([@squishykid] - [#22579]) ([solax docs]) (new-integration) (new-platform)
+- Set assumed_state property to True. ([@jardiamj] - [#24118]) ([mcp23017 docs])
+- Remove custom entity_id naming ([@jjlawren] - [#24072]) ([plex docs]) (breaking change)
+- Move imports to top ([@andrewsayre] - [#24108]) ([heos docs])
+- Use name in ESPHome discovery title ([@OttoWinter] - [#24100])
+- Add Remote RPi Component ([@jgriff2] - [#23518]) ([remote_rpi_gpio docs]) (new-integration) (new-platform)
+- Azure Event Hub history component ([@eavanvalkenburg] - [#23878]) ([azure_event_hub docs]) (new-integration)
+- geniushub: fix sensor battery level, and bump client ([@zxdavb] - [#24123]) ([geniushub docs])
+- Use importlib metadata to check installed packages ([@balloob] - [#24114])
+- Avoid useless Sonos state updates ([@amelchio] - [#24135]) ([sonos docs])
+- Add SSDP integration ([@balloob] - [#24090]) ([default_config docs]) ([discovery docs]) ([hue docs]) ([ssdp docs]) ([zeroconf docs]) (new-integration)
+- Lovelace: Fire event on save ([@bramkragten] - [#24104]) ([lovelace docs])
+- Use central polling to update entities ([@jjlawren] - [#24059]) ([plex docs])
+- Library refactorization of deCONZ ([@Kane610] - [#23725]) ([deconz docs])
+- Retrieve wire and wireless devices with the SRM device tracker ([@aerialls] - [#24117]) ([synology_srm docs])
+- bump dependency envoy_reader to 0.4 ([@jesserizzo] - [#24145]) ([enphase_envoy docs])
+- Debug log when polling ZHA light. ([@Adminiuga] - [#24167]) ([zha docs])
+- Upgrade huawei-lte-api to 1.2.0 ([@chmielowiec] - [#24165]) ([huawei_lte docs])
+- Use device name for device_tracker entry ([@robbiet480] - [#24155]) ([mobile_app docs])
+- Use global imports for ESPHome ([@OttoWinter] - [#24158]) ([esphome docs])
+- Add Repetier-Server Component ([@MTrab] - [#21658]) ([repetier docs]) (new-platform)
+- Cloud: Websocket API to manage Google assistant entity config ([@balloob] - [#24153]) ([cloud docs]) ([google_assistant docs])
+- Fix calling notify.notify with mobile_app targets in play. Fixes #24064 ([@robbiet480] - [#24156]) ([mobile_app docs])
+- Remove unused Sonos turn on/off methods ([@amelchio] - [#24174]) ([sonos docs])
+- Reinstate passing loop to DSMR ([@balloob] - [#24127]) ([dsmr docs])
+- Trådfri component to use new zeroconf discovery ([@Kane610] - [#24041]) ([discovery docs]) ([tradfri docs]) (breaking change)
+- Move Homekit controller component to user zeroconf discovery ([@Kane610] - [#24042]) ([discovery docs]) ([homekit_controller docs]) (breaking change)
+- Revert Zeroconf back to previously used library ([@Kane610] - [#24139]) ([zeroconf docs])
+- Deprecate Python 3.5.3 ([@balloob] - [#24177]) (breaking change)
+- Keep integrations in discovery ([@Kane610] - [#24179]) ([discovery docs])
+- Avoid slow updates with unavailable Sonos devices ([@amelchio] - [#24180]) ([sonos docs])
+- Support Hass.io wheels / docker env ([@pvizeli] - [#24175])
+- Remove discovery from initial config ([@balloob] - [#24183])
+- Fix duplicated discovered homekit devices ([@Jc2k] - [#24178]) ([homekit_controller docs])
+- Add service calls for LCN component ([@alengwenus] - [#24105]) ([lcn docs])
+
+[#21225]: https://github.com/home-assistant/home-assistant/pull/21225
+[#21658]: https://github.com/home-assistant/home-assistant/pull/21658
+[#22542]: https://github.com/home-assistant/home-assistant/pull/22542
+[#22579]: https://github.com/home-assistant/home-assistant/pull/22579
+[#23067]: https://github.com/home-assistant/home-assistant/pull/23067
+[#23127]: https://github.com/home-assistant/home-assistant/pull/23127
+[#23284]: https://github.com/home-assistant/home-assistant/pull/23284
+[#23299]: https://github.com/home-assistant/home-assistant/pull/23299
+[#23312]: https://github.com/home-assistant/home-assistant/pull/23312
+[#23518]: https://github.com/home-assistant/home-assistant/pull/23518
+[#23606]: https://github.com/home-assistant/home-assistant/pull/23606
+[#23633]: https://github.com/home-assistant/home-assistant/pull/23633
+[#23648]: https://github.com/home-assistant/home-assistant/pull/23648
+[#23725]: https://github.com/home-assistant/home-assistant/pull/23725
+[#23734]: https://github.com/home-assistant/home-assistant/pull/23734
+[#23755]: https://github.com/home-assistant/home-assistant/pull/23755
+[#23759]: https://github.com/home-assistant/home-assistant/pull/23759
+[#23764]: https://github.com/home-assistant/home-assistant/pull/23764
+[#23765]: https://github.com/home-assistant/home-assistant/pull/23765
+[#23770]: https://github.com/home-assistant/home-assistant/pull/23770
+[#23774]: https://github.com/home-assistant/home-assistant/pull/23774
+[#23776]: https://github.com/home-assistant/home-assistant/pull/23776
+[#23777]: https://github.com/home-assistant/home-assistant/pull/23777
+[#23782]: https://github.com/home-assistant/home-assistant/pull/23782
+[#23786]: https://github.com/home-assistant/home-assistant/pull/23786
+[#23790]: https://github.com/home-assistant/home-assistant/pull/23790
+[#23792]: https://github.com/home-assistant/home-assistant/pull/23792
+[#23793]: https://github.com/home-assistant/home-assistant/pull/23793
+[#23802]: https://github.com/home-assistant/home-assistant/pull/23802
+[#23806]: https://github.com/home-assistant/home-assistant/pull/23806
+[#23808]: https://github.com/home-assistant/home-assistant/pull/23808
+[#23810]: https://github.com/home-assistant/home-assistant/pull/23810
+[#23811]: https://github.com/home-assistant/home-assistant/pull/23811
+[#23815]: https://github.com/home-assistant/home-assistant/pull/23815
+[#23816]: https://github.com/home-assistant/home-assistant/pull/23816
+[#23824]: https://github.com/home-assistant/home-assistant/pull/23824
+[#23825]: https://github.com/home-assistant/home-assistant/pull/23825
+[#23829]: https://github.com/home-assistant/home-assistant/pull/23829
+[#23830]: https://github.com/home-assistant/home-assistant/pull/23830
+[#23832]: https://github.com/home-assistant/home-assistant/pull/23832
+[#23833]: https://github.com/home-assistant/home-assistant/pull/23833
+[#23835]: https://github.com/home-assistant/home-assistant/pull/23835
+[#23840]: https://github.com/home-assistant/home-assistant/pull/23840
+[#23842]: https://github.com/home-assistant/home-assistant/pull/23842
+[#23845]: https://github.com/home-assistant/home-assistant/pull/23845
+[#23847]: https://github.com/home-assistant/home-assistant/pull/23847
+[#23856]: https://github.com/home-assistant/home-assistant/pull/23856
+[#23858]: https://github.com/home-assistant/home-assistant/pull/23858
+[#23860]: https://github.com/home-assistant/home-assistant/pull/23860
+[#23862]: https://github.com/home-assistant/home-assistant/pull/23862
+[#23863]: https://github.com/home-assistant/home-assistant/pull/23863
+[#23872]: https://github.com/home-assistant/home-assistant/pull/23872
+[#23873]: https://github.com/home-assistant/home-assistant/pull/23873
+[#23874]: https://github.com/home-assistant/home-assistant/pull/23874
+[#23877]: https://github.com/home-assistant/home-assistant/pull/23877
+[#23878]: https://github.com/home-assistant/home-assistant/pull/23878
+[#23882]: https://github.com/home-assistant/home-assistant/pull/23882
+[#23886]: https://github.com/home-assistant/home-assistant/pull/23886
+[#23890]: https://github.com/home-assistant/home-assistant/pull/23890
+[#23892]: https://github.com/home-assistant/home-assistant/pull/23892
+[#23905]: https://github.com/home-assistant/home-assistant/pull/23905
+[#23907]: https://github.com/home-assistant/home-assistant/pull/23907
+[#23908]: https://github.com/home-assistant/home-assistant/pull/23908
+[#23909]: https://github.com/home-assistant/home-assistant/pull/23909
+[#23916]: https://github.com/home-assistant/home-assistant/pull/23916
+[#23918]: https://github.com/home-assistant/home-assistant/pull/23918
+[#23919]: https://github.com/home-assistant/home-assistant/pull/23919
+[#23921]: https://github.com/home-assistant/home-assistant/pull/23921
+[#23922]: https://github.com/home-assistant/home-assistant/pull/23922
+[#23930]: https://github.com/home-assistant/home-assistant/pull/23930
+[#23931]: https://github.com/home-assistant/home-assistant/pull/23931
+[#23947]: https://github.com/home-assistant/home-assistant/pull/23947
+[#23958]: https://github.com/home-assistant/home-assistant/pull/23958
+[#23960]: https://github.com/home-assistant/home-assistant/pull/23960
+[#23962]: https://github.com/home-assistant/home-assistant/pull/23962
+[#23973]: https://github.com/home-assistant/home-assistant/pull/23973
+[#23976]: https://github.com/home-assistant/home-assistant/pull/23976
+[#23981]: https://github.com/home-assistant/home-assistant/pull/23981
+[#23983]: https://github.com/home-assistant/home-assistant/pull/23983
+[#23984]: https://github.com/home-assistant/home-assistant/pull/23984
+[#23989]: https://github.com/home-assistant/home-assistant/pull/23989
+[#23991]: https://github.com/home-assistant/home-assistant/pull/23991
+[#24001]: https://github.com/home-assistant/home-assistant/pull/24001
+[#24004]: https://github.com/home-assistant/home-assistant/pull/24004
+[#24009]: https://github.com/home-assistant/home-assistant/pull/24009
+[#24015]: https://github.com/home-assistant/home-assistant/pull/24015
+[#24019]: https://github.com/home-assistant/home-assistant/pull/24019
+[#24020]: https://github.com/home-assistant/home-assistant/pull/24020
+[#24022]: https://github.com/home-assistant/home-assistant/pull/24022
+[#24033]: https://github.com/home-assistant/home-assistant/pull/24033
+[#24034]: https://github.com/home-assistant/home-assistant/pull/24034
+[#24037]: https://github.com/home-assistant/home-assistant/pull/24037
+[#24038]: https://github.com/home-assistant/home-assistant/pull/24038
+[#24040]: https://github.com/home-assistant/home-assistant/pull/24040
+[#24041]: https://github.com/home-assistant/home-assistant/pull/24041
+[#24042]: https://github.com/home-assistant/home-assistant/pull/24042
+[#24043]: https://github.com/home-assistant/home-assistant/pull/24043
+[#24049]: https://github.com/home-assistant/home-assistant/pull/24049
+[#24050]: https://github.com/home-assistant/home-assistant/pull/24050
+[#24059]: https://github.com/home-assistant/home-assistant/pull/24059
+[#24066]: https://github.com/home-assistant/home-assistant/pull/24066
+[#24068]: https://github.com/home-assistant/home-assistant/pull/24068
+[#24072]: https://github.com/home-assistant/home-assistant/pull/24072
+[#24078]: https://github.com/home-assistant/home-assistant/pull/24078
+[#24081]: https://github.com/home-assistant/home-assistant/pull/24081
+[#24082]: https://github.com/home-assistant/home-assistant/pull/24082
+[#24084]: https://github.com/home-assistant/home-assistant/pull/24084
+[#24090]: https://github.com/home-assistant/home-assistant/pull/24090
+[#24100]: https://github.com/home-assistant/home-assistant/pull/24100
+[#24102]: https://github.com/home-assistant/home-assistant/pull/24102
+[#24104]: https://github.com/home-assistant/home-assistant/pull/24104
+[#24105]: https://github.com/home-assistant/home-assistant/pull/24105
+[#24108]: https://github.com/home-assistant/home-assistant/pull/24108
+[#24114]: https://github.com/home-assistant/home-assistant/pull/24114
+[#24117]: https://github.com/home-assistant/home-assistant/pull/24117
+[#24118]: https://github.com/home-assistant/home-assistant/pull/24118
+[#24123]: https://github.com/home-assistant/home-assistant/pull/24123
+[#24127]: https://github.com/home-assistant/home-assistant/pull/24127
+[#24135]: https://github.com/home-assistant/home-assistant/pull/24135
+[#24139]: https://github.com/home-assistant/home-assistant/pull/24139
+[#24145]: https://github.com/home-assistant/home-assistant/pull/24145
+[#24153]: https://github.com/home-assistant/home-assistant/pull/24153
+[#24155]: https://github.com/home-assistant/home-assistant/pull/24155
+[#24156]: https://github.com/home-assistant/home-assistant/pull/24156
+[#24158]: https://github.com/home-assistant/home-assistant/pull/24158
+[#24165]: https://github.com/home-assistant/home-assistant/pull/24165
+[#24167]: https://github.com/home-assistant/home-assistant/pull/24167
+[#24174]: https://github.com/home-assistant/home-assistant/pull/24174
+[#24175]: https://github.com/home-assistant/home-assistant/pull/24175
+[#24177]: https://github.com/home-assistant/home-assistant/pull/24177
+[#24178]: https://github.com/home-assistant/home-assistant/pull/24178
+[#24179]: https://github.com/home-assistant/home-assistant/pull/24179
+[#24180]: https://github.com/home-assistant/home-assistant/pull/24180
+[#24183]: https://github.com/home-assistant/home-assistant/pull/24183
+[@Adminiuga]: https://github.com/Adminiuga
+[@BKPepe]: https://github.com/BKPepe
+[@Bouni]: https://github.com/Bouni
+[@Danielhiversen]: https://github.com/Danielhiversen
+[@Jc2k]: https://github.com/Jc2k
+[@JeffLIrion]: https://github.com/JeffLIrion
+[@Kane610]: https://github.com/Kane610
+[@MTrab]: https://github.com/MTrab
+[@OttoWinter]: https://github.com/OttoWinter
+[@SiliconAvatar]: https://github.com/SiliconAvatar
+[@SukramJ]: https://github.com/SukramJ
+[@Swamp-Ig]: https://github.com/Swamp-Ig
+[@TomerFi]: https://github.com/TomerFi
+[@adrianschroeter]: https://github.com/adrianschroeter
+[@aerialls]: https://github.com/aerialls
+[@akloeckner]: https://github.com/akloeckner
+[@alengwenus]: https://github.com/alengwenus
+[@amelchio]: https://github.com/amelchio
+[@andrewsayre]: https://github.com/andrewsayre
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bramkragten]: https://github.com/bramkragten
+[@cgarwood]: https://github.com/cgarwood
+[@chmielowiec]: https://github.com/chmielowiec
+[@dreed47]: https://github.com/dreed47
+[@eavanvalkenburg]: https://github.com/eavanvalkenburg
+[@elupus]: https://github.com/elupus
+[@emontnemery]: https://github.com/emontnemery
+[@fabaff]: https://github.com/fabaff
+[@foxel]: https://github.com/foxel
+[@fredrike]: https://github.com/fredrike
+[@iamtpage]: https://github.com/iamtpage
+[@jardiamj]: https://github.com/jardiamj
+[@jesserizzo]: https://github.com/jesserizzo
+[@jgriff2]: https://github.com/jgriff2
+[@jjlawren]: https://github.com/jjlawren
+[@ludeeus]: https://github.com/ludeeus
+[@mvn23]: https://github.com/mvn23
+[@nugget]: https://github.com/nugget
+[@oblogic7]: https://github.com/oblogic7
+[@outadoc]: https://github.com/outadoc
+[@p0l0]: https://github.com/p0l0
+[@pavoni]: https://github.com/pavoni
+[@pszafer]: https://github.com/pszafer
+[@pvizeli]: https://github.com/pvizeli
+[@robbiet480]: https://github.com/robbiet480
+[@rutkai]: https://github.com/rutkai
+[@sander76]: https://github.com/sander76
+[@scop]: https://github.com/scop
+[@simse]: https://github.com/simse
+[@squishykid]: https://github.com/squishykid
+[@starkillerOG]: https://github.com/starkillerOG
+[@stbenjam]: https://github.com/stbenjam
+[@techfreek]: https://github.com/techfreek
+[@terual]: https://github.com/terual
+[@ties]: https://github.com/ties
+[@tkjacobsen]: https://github.com/tkjacobsen
+[@wickerwaka]: https://github.com/wickerwaka
+[@zewelor]: https://github.com/zewelor
+[@zxdavb]: https://github.com/zxdavb
+[ambiclimate docs]: /components/ambiclimate/
+[androidtv docs]: /components/androidtv/
+[apns docs]: /components/apns/
+[axis docs]: /components/axis/
+[azure_event_hub docs]: /components/azure_event_hub/
+[broadlink docs]: /components/broadlink/
+[camera docs]: /components/camera/
+[cloud docs]: /components/cloud/
+[config docs]: /components/config/
+[daikin docs]: /components/daikin/
+[darksky docs]: /components/darksky/
+[deconz docs]: /components/deconz/
+[default_config docs]: /components/default_config/
+[demo docs]: /components/demo/
+[device_tracker docs]: /components/device_tracker/
+[discovery docs]: /components/discovery/
+[doorbird docs]: /components/doorbird/
+[dsmr docs]: /components/dsmr/
+[emulated_hue docs]: /components/emulated_hue/
+[enphase_envoy docs]: /components/enphase_envoy/
+[esphome docs]: /components/esphome/
+[frontend docs]: /components/frontend/
+[geniushub docs]: /components/geniushub/
+[geofency docs]: /components/geofency/
+[google_assistant docs]: /components/google_assistant/
+[gpslogger docs]: /components/gpslogger/
+[heos docs]: /components/heos/
+[homekit_controller docs]: /components/homekit_controller/
+[homematic docs]: /components/homematic/
+[homematicip_cloud docs]: /components/homematicip_cloud/
+[html5 docs]: /components/html5/
+[http docs]: /components/http/
+[huawei_lte docs]: /components/huawei_lte/
+[hue docs]: /components/hue/
+[icloud docs]: /components/icloud/
+[incomfort docs]: /components/incomfort/
+[iqvia docs]: /components/iqvia/
+[keenetic_ndms2 docs]: /components/keenetic_ndms2/
+[lcn docs]: /components/lcn/
+[locative docs]: /components/locative/
+[loopenergy docs]: /components/loopenergy/
+[lovelace docs]: /components/lovelace/
+[mastodon docs]: /components/mastodon/
+[mcp23017 docs]: /components/mcp23017/
+[media_extractor docs]: /components/media_extractor/
+[media_player docs]: /components/media_player/
+[mobile_app docs]: /components/mobile_app/
+[neato docs]: /components/neato/
+[netatmo docs]: /components/netatmo/
+[netgear docs]: /components/netgear/
+[onboarding docs]: /components/onboarding/
+[opentherm_gw docs]: /components/opentherm_gw/
+[owntracks docs]: /components/owntracks/
+[panel_custom docs]: /components/panel_custom/
+[panel_iframe docs]: /components/panel_iframe/
+[plex docs]: /components/plex/
+[remote_rpi_gpio docs]: /components/remote_rpi_gpio/
+[repetier docs]: /components/repetier/
+[rfxtrx docs]: /components/rfxtrx/
+[russound_rio docs]: /components/russound_rio/
+[script docs]: /components/script/
+[smarthab docs]: /components/smarthab/
+[solax docs]: /components/solax/
+[sonos docs]: /components/sonos/
+[spaceapi docs]: /components/spaceapi/
+[ssdp docs]: /components/ssdp/
+[sun docs]: /components/sun/
+[switcher_kis docs]: /components/switcher_kis/
+[synology_srm docs]: /components/synology_srm/
+[tautulli docs]: /components/tautulli/
+[tradfri docs]: /components/tradfri/
+[vasttrafik docs]: /components/vasttrafik/
+[venstar docs]: /components/venstar/
+[verisure docs]: /components/verisure/
+[watson_tts docs]: /components/watson_tts/
+[websocket_api docs]: /components/websocket_api/
+[xiaomi_aqara docs]: /components/xiaomi_aqara/
+[xiaomi_tv docs]: /components/xiaomi_tv/
+[yeelight docs]: /components/yeelight/
+[zeroconf docs]: /components/zeroconf/
+[zestimate docs]: /components/zestimate/
+[zha docs]: /components/zha/
+[zone docs]: /components/zone/
+[zwave docs]: /components/zwave/
From 4516a0940ea26745dec61b422a030bda94907627 Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Wed, 29 May 2019 20:06:10 -0700
Subject: [PATCH 018/123] Add some more notes
---
source/_posts/2019-06-05-release-94.markdown | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/source/_posts/2019-06-05-release-94.markdown b/source/_posts/2019-06-05-release-94.markdown
index 697bfb67c0b..4a4c50917ae 100644
--- a/source/_posts/2019-06-05-release-94.markdown
+++ b/source/_posts/2019-06-05-release-94.markdown
@@ -14,12 +14,13 @@ og_image: /images/blog/2019-06-release-94/components.png
New:
- - Possible to store core config in storage. If set in configuration.yaml, it will override storage. Note that configuration.yaml will no longer contain any automatic detected values when writing initial configuration. This feature is available via the UI during onboarding.
+ - Possible to store core config in storage. If set in configuration.yaml, it will override storage (this is what anyone coming from 0.93 has). Note that configuration.yaml will no longer contain any automatic detected values when writing initial configuration. This feature is available via the UI during onboarding.
+ - Allow deletion of scripts/automations via the UI editor.
+ - This is the first release where a user can use a subset of Home Assistant without using configuration.yaml.
- Step added to onboarding to allow configuring name, location, timezone and unit system.
- Python 3.5.3 deprecated, support will be dropped in the first release after August 1.
- Add UI to manage Google Entities exposed via Home Assistant Cloud. To use, remove filters from configuration.yaml. Also allows disabling 2 factor authentication on a per device basis.
- - Discovery has been redone. Integrations can now specify how they are discoverable via Zeroconf or SSDP in their manifest, this will be picked up by the zeroconf and ssdp integrations.
- - More cool stuff?
+ - Discovery has been redone. Integrations can now specify how they are discoverable via Zeroconf or SSDP in their manifest, this will be picked up by the zeroconf and ssdp integrations. The new discovery is non-obtrusive: nothing is added to your configuration without approval by the user. You can find integrations pending approval in the discovered section of the integrations page in the config.
## {% linkable_title New Integrations %}
From c93d94dd1d58b64a76a52ca0e0e7d9457898deda Mon Sep 17 00:00:00 2001
From: Otto Winter
Date: Fri, 31 May 2019 00:36:54 +0200
Subject: [PATCH 019/123] Remove esphome breaking change (#9537)
---
source/_posts/2019-06-05-release-94.markdown | 1 -
1 file changed, 1 deletion(-)
diff --git a/source/_posts/2019-06-05-release-94.markdown b/source/_posts/2019-06-05-release-94.markdown
index 4a4c50917ae..40167c84061 100644
--- a/source/_posts/2019-06-05-release-94.markdown
+++ b/source/_posts/2019-06-05-release-94.markdown
@@ -57,7 +57,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Quiet the chatty sun.sun ([@Swamp-Ig] - [#23832]) ([sun docs]) (breaking change)
- Doorbird Refactor ([@oblogic7] - [#23892]) ([doorbird docs]) (breaking change)
-- ESPHome component to use zeroconf discovery ([@Kane610] - [#24043]) ([esphome docs]) (breaking change)
- Always update all Plex client types ([@jjlawren] - [#24038]) ([plex docs]) (breaking change)
- Fix entity id naming when not using first install ([@tkjacobsen] - [#23606]) ([verisure docs]) (breaking change)
- Update the name of Zestimate sensors ([@dreed47] - [#23770]) ([zestimate docs]) (breaking change)
From 1744091219521a8c7d1b11c85f77931fbe66606e Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Fri, 31 May 2019 13:56:02 -0700
Subject: [PATCH 020/123] Update notes
---
source/_posts/2019-06-05-release-94.markdown | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/source/_posts/2019-06-05-release-94.markdown b/source/_posts/2019-06-05-release-94.markdown
index 40167c84061..a5d8b8fda62 100644
--- a/source/_posts/2019-06-05-release-94.markdown
+++ b/source/_posts/2019-06-05-release-94.markdown
@@ -14,13 +14,14 @@ og_image: /images/blog/2019-06-release-94/components.png
New:
- - Possible to store core config in storage. If set in configuration.yaml, it will override storage (this is what anyone coming from 0.93 has). Note that configuration.yaml will no longer contain any automatic detected values when writing initial configuration. This feature is available via the UI during onboarding.
+ - Possible to store core config in storage. If set in configuration.yaml, it will override storage (this is what anyone coming from 0.93 has). Note that configuration.yaml will no longer contain any automatic detected values when writing initial configuration. This feature is available via the UI during onboarding. Big thanks to [@emontnemery] for this contribution.
- Allow deletion of scripts/automations via the UI editor.
- This is the first release where a user can use a subset of Home Assistant without using configuration.yaml.
- Step added to onboarding to allow configuring name, location, timezone and unit system.
- Python 3.5.3 deprecated, support will be dropped in the first release after August 1.
- Add UI to manage Google Entities exposed via Home Assistant Cloud. To use, remove filters from configuration.yaml. Also allows disabling 2 factor authentication on a per device basis.
- - Discovery has been redone. Integrations can now specify how they are discoverable via Zeroconf or SSDP in their manifest, this will be picked up by the zeroconf and ssdp integrations. The new discovery is non-obtrusive: nothing is added to your configuration without approval by the user. You can find integrations pending approval in the discovered section of the integrations page in the config.
+ - Discovery has been redone. Integrations can now specify how they are discoverable via Zeroconf, SSDP or HomeKit in their manifest, this will be picked up by the zeroconf and ssdp integrations. The new discovery is non-obtrusive: nothing is added to your configuration without approval by the user. You can find integrations pending approval in the discovered section of the integrations page in the config. Only a handful of integrations have been migrated to the new approach in this release. Thanks to [@Kane610], [@Jc2k]
+
## {% linkable_title New Integrations %}
From d174c6c55e1ac2d1bbaffa992bcef45af76e9eba Mon Sep 17 00:00:00 2001
From: Kyle Niewiada
Date: Fri, 31 May 2019 17:54:42 -0400
Subject: [PATCH 021/123] Add device model and bold shutdown directions
Added a device model for the Hank Z-Wave button: https://products.z-wavealliance.org/products/1918
I just bought one and used the same directions to get it working.
I also wanted to bold the directions telling the user to shutdown because I missed that paragraph and lost quite a bit of time trying to figure out why it wouldn't persist.
---
source/_docs/z-wave/device-specific.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/source/_docs/z-wave/device-specific.markdown b/source/_docs/z-wave/device-specific.markdown
index aacb9b3da27..da14dc69af9 100644
--- a/source/_docs/z-wave/device-specific.markdown
+++ b/source/_docs/z-wave/device-specific.markdown
@@ -167,7 +167,7 @@ Some models of the Zooz Toggle switches ship with an instruction manual with inc
## {% linkable_title Central Scene configuration %}
-To provide Central Scene support you need to shut Home Assistant down and modify your `zwcfg_*.xml` file according to the following guides.
+To provide Central Scene support you need to **shut Home Assistant down** and modify your `zwcfg_*.xml` file according to the following guides.
### {% linkable_title Inovelli Scene Capable On/Off and Dimmer Wall Switches %}
@@ -386,7 +386,7 @@ Button four release|4|1
Use the same configuration as for the Aeotec Wallmote.
-### {% linkable_title HANK One-key Scene Controller HKZN-SCN01 %}
+### {% linkable_title HANK One-key Scene Controller HKZN-SCN01/HKZW-SCN01 %}
For the HANK One-key Scene Controller, you may need to update the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following:
From 0f89c201dcdae21984c4dd09b9abfa6a02da2eb4 Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Fri, 31 May 2019 15:17:10 -0700
Subject: [PATCH 022/123] More notes
---
source/_posts/2019-06-05-release-94.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/source/_posts/2019-06-05-release-94.markdown b/source/_posts/2019-06-05-release-94.markdown
index a5d8b8fda62..b773f6691e0 100644
--- a/source/_posts/2019-06-05-release-94.markdown
+++ b/source/_posts/2019-06-05-release-94.markdown
@@ -20,8 +20,8 @@ New:
- Step added to onboarding to allow configuring name, location, timezone and unit system.
- Python 3.5.3 deprecated, support will be dropped in the first release after August 1.
- Add UI to manage Google Entities exposed via Home Assistant Cloud. To use, remove filters from configuration.yaml. Also allows disabling 2 factor authentication on a per device basis.
- - Discovery has been redone. Integrations can now specify how they are discoverable via Zeroconf, SSDP or HomeKit in their manifest, this will be picked up by the zeroconf and ssdp integrations. The new discovery is non-obtrusive: nothing is added to your configuration without approval by the user. You can find integrations pending approval in the discovered section of the integrations page in the config. Only a handful of integrations have been migrated to the new approach in this release. Thanks to [@Kane610], [@Jc2k]
-
+ - Discovery has been redone. Integrations can now specify how they are discoverable via Zeroconf, SSDP or HomeKit in their manifest, this will be picked up by the zeroconf and ssdp integrations, which are part of the default config. The new discovery is non-obtrusive: nothing is added to your configuration without approval by the user. You can find integrations pending approval in the discovered section of the integrations page in the config. Only a handful of integrations have been migrated to the new approach in this release. Thanks to [@Kane610], [@Jc2k]. If you are not using the `default_config` integration, add `ssdp:` and `zeroconf:` to your configuration.yaml.
+ - We are bringing the device tracker integration into the age of modern integrations. The first step has been to migrating the platforms that use config entries like OwnTracks and GPSLogger. This means that for these integrations, you will now be able to use things like entity registry to change entity ID and name.
## {% linkable_title New Integrations %}
From b90fcfe5385790e4a690a61185696cb30ab9cf2a Mon Sep 17 00:00:00 2001
From: Klaas Schoute
Date: Sat, 1 Jun 2019 00:41:16 +0200
Subject: [PATCH 023/123] :pencil2: Tweak
---
source/_docs/z-wave/device-specific.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_docs/z-wave/device-specific.markdown b/source/_docs/z-wave/device-specific.markdown
index da14dc69af9..94f6edb9c40 100644
--- a/source/_docs/z-wave/device-specific.markdown
+++ b/source/_docs/z-wave/device-specific.markdown
@@ -167,7 +167,7 @@ Some models of the Zooz Toggle switches ship with an instruction manual with inc
## {% linkable_title Central Scene configuration %}
-To provide Central Scene support you need to **shut Home Assistant down** and modify your `zwcfg_*.xml` file according to the following guides.
+To provide Central Scene support you need to **shutdown Home Assistant** and modify your `zwcfg_*.xml` file according to the following guides.
### {% linkable_title Inovelli Scene Capable On/Off and Dimmer Wall Switches %}
From db243d7fb6f871e019c9539784c6a04d2f48b136 Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Fri, 31 May 2019 15:50:05 -0700
Subject: [PATCH 024/123] Update geofency, GPSLogger and owntracks docs
---
source/_components/geofency.markdown | 8 +++----
source/_components/gpslogger.markdown | 4 +---
source/_components/locative.md | 4 +---
source/_components/owntracks.markdown | 30 +++------------------------
4 files changed, 8 insertions(+), 38 deletions(-)
diff --git a/source/_components/geofency.markdown b/source/_components/geofency.markdown
index 86d38f99d84..70abf05f026 100644
--- a/source/_components/geofency.markdown
+++ b/source/_components/geofency.markdown
@@ -16,15 +16,13 @@ redirect_from:
- /components/device_tracker.geofency/
---
-This component sets up integration with [Geofency](http://www.geofency.com/). Geofency is a [paid app](https://itunes.apple.com/app/id615538630) for iOS that lets users to configure a request that will be sent when a geofence or iBeacon region is entered or exited. This can be configured with Home Assistant to update your location.
-
-Enabling this component will automatically enable the Geofency Device Tracker.
+This component sets up integration with [Geofency](http://www.geofency.com/). Geofency is a paid app for iOS that lets users to configure a request that will be sent when a geofence or iBeacon region is entered or exited. This can be configured with Home Assistant to update your location.
## {% linkable_title Configuration %}
To configure Geofency, you must set it up via the integrations panel in the configuration screen. You must then configure the iOS app (via the Webhook feature) to send a POST request to your Home Assistant server at the webhook URL provided by the integration during setup. Use the default POST format. Make sure to enable the 'Update Geo-Position' functionality for mobile beacons.
-Geofency will automatically generate the device tracker name used for geofences, and you will find it in `known_devices.yaml` after the first request. For beacons, the device name will be `beacon_`, e.g., `device_tracker.beacon_car`.
+Geofency will automatically generate the device tracker name used for geofences, and you will find it in the integrations section after the first request. For beacons, the device name will be `beacon_`, e.g., `device_tracker.beacon_car`.
When using mobile beacons (optional) an entry in `configuration.yaml` is still needed as this can't be added via the integrations panel.
@@ -49,4 +47,4 @@ geofency:
When you enter a geofence or stationary beacon, your location name in Home Assistant will be set to the name of the geofence or beacon location in Geofency. When you exit a geofence or stationary beacon, your location name in Home Assistant will be set to `not home`. For mobile beacons, the location name will be `not_home` whenever the beacon is entered or exited outside of a [zone](/components/zone/), otherwise, it will be set to the name of the zone.
-To make Geofency work better with the [proximity](/components/proximity/) component, you should enable the 'Send Current Location' feature in the Webhook configuration screen. This ensures that the _current_ GPS coordinates are included in exit events instead of the coordinates of the (center of) the zone that was exited.
\ No newline at end of file
+To make Geofency work better with the [proximity](/components/proximity/) component, you should enable the 'Send Current Location' feature in the Webhook configuration screen. This ensures that the _current_ GPS coordinates are included in exit events instead of the coordinates of the (center of) the zone that was exited.
diff --git a/source/_components/gpslogger.markdown b/source/_components/gpslogger.markdown
index 8f4e5549ac0..eb4e00ceb77 100644
--- a/source/_components/gpslogger.markdown
+++ b/source/_components/gpslogger.markdown
@@ -16,9 +16,7 @@ redirect_from:
- /components/device_tracker.gpslogger/
---
-This component sets up integration with [GPSLogger](http://code.mendhak.com/gpslogger/). GPSLogger is an open source app for [Android](https://play.google.com/store/apps/details?id=com.mendhak.gpslogger) that allows users to set up a `POST` request to update GPS coordinates. This can be configured with Home Assistant to update your location.
-
-Enabling this component will automatically enable the GPSLogger Device Tracker.
+This component sets up integration with [GPSLogger](https://gpslogger.app/). GPSLogger is an open source app for Android that allows users to update your location in Home Assistant.
## {% linkable_title Configuration %}
diff --git a/source/_components/locative.md b/source/_components/locative.md
index 7aeecdfa8a3..b704054ff02 100644
--- a/source/_components/locative.md
+++ b/source/_components/locative.md
@@ -17,7 +17,7 @@ redirect_from:
---
-Locative is no longer under active development. Read more here
+Locative is no longer under active development.
This platform allows you to detect presence using [Locative](https://my.locative.io/). Locative is an open source app for [iOS](https://github.com/LocativeHQ/ios-app) and [Android](https://github.com/LocativeHQ/Locative-Android) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location.
@@ -34,5 +34,3 @@ To configure Locative, you must set it up via the integrations panel in the conf
When you enter a geofence, your location name in Home Assistant will be set to the name of the geofence in Locative. When you exit a geofence, your location name in Home Assistant will be set to "not home".
-
-To use Locative in combination with another device tracker, such as [Nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/), fill in the `mac` field to the Locative entry in `known_devices.yaml` with the MAC address of the device you want to track. The state of the device will be determined by the source that reported last.
diff --git a/source/_components/owntracks.markdown b/source/_components/owntracks.markdown
index 7dc33ac5b0e..fafb7ab9573 100644
--- a/source/_components/owntracks.markdown
+++ b/source/_components/owntracks.markdown
@@ -24,17 +24,9 @@ By default the integration will listen for incoming messages from OwnTracks via
-### {% linkable_title Configuring the component %}
+## {% linkable_title Configuration %}
-1. Open the Home Assistant frontend
-1. Open Settings -> integrations
-1. If you see an Owntracks component under 'Configured', delete it.
- - Click on it.
- - Click on the trashcan icon in the upper right corner.
-1. Now, look for Owntracks in 'Setup new integration' and click on CONFIGURE.
-1. The login credentials and configuration for owntracks will be presented to you.
- in a popup window. You will need these in the configuration for the app as mentioned below.
-1. Save these credentials somewhere, as there is no way to get it back at a later point in time if it is lost, besides repeating step 1-5
+To configure OwnTracks, you must set it up via the integrations panel in the configuration screen. This will give you the webhook URL to use during mobile device configuration (below).
### {% linkable_title Configuring the app - Android %}
@@ -43,7 +35,7 @@ By default the integration will listen for incoming messages from OwnTracks via
In the OwnTracks app, open sidebar and click on preferences, then on connection. Change the following settings:
- Mode: Private HTTP
- - Host: ``
+ - Host: ``
- Identification:
- Username: ``
- Password: Can be left blank.
@@ -167,19 +159,3 @@ By default, any Owntracks user connected to Home Assistant can export their wayp
1. The configuration variable `waypoints` can be set to `false` which will disable importing waypoints for all users.
2. The configuration variable `waypoint_whitelist` can contain a list of users who are allowed to import waypoints.
-
-## {% linkable_title Using Owntracks with other device trackers %}
-
-Owntracks can also be used with other device trackers, such as [Nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/). To do this, fill in the `mac` field to the Owntracks entry in `known_devices.yaml` with the MAC address of the device you want to track. This way the state of the device will be determined by the source that reported last. The naming convention for known device list is `_` and could be set in app configuration. More details about this config can found in [device tracker](/components/device_tracker/).
-
-An example showing the inclusion of the `mac` field for multiple component tracking. The `mac` field will need to be added to the `owntracks` device and will enable tracking by all components that track via the `mac` address.
-
-```yaml
-USERNAME_DEVICE_ID:
- name: Friendly Name
- mac: EA:AA:55:E7:C6:94
- picture: https://www.home-assistant.io/images/favicon-192x192.png
- gravatar: test@example.com
- track: true
- hide_if_away: false
-```
From 2d752bcab07e612064fe44918d7db6b57c368746 Mon Sep 17 00:00:00 2001
From: Klaas Schoute
Date: Sat, 1 Jun 2019 01:46:57 +0200
Subject: [PATCH 025/123] :hammer: Restructure platform pages (#9541)
---
.../_components/alarm_control_panel.markdown | 9 +--
source/_components/binary_sensor.markdown | 34 +---------
source/_components/camera.markdown | 67 ++++++++++---------
source/_components/climate.markdown | 21 +-----
source/_components/cover.markdown | 24 +------
source/_components/device_tracker.markdown | 34 ++--------
source/_components/fan.markdown | 14 +---
source/_components/light.markdown | 10 ++-
source/_components/lock.markdown | 2 +
source/_components/media_player.markdown | 4 +-
source/_components/notify.markdown | 16 +----
source/_components/sensor.markdown | 19 +-----
source/_components/switch.markdown | 2 +
13 files changed, 72 insertions(+), 184 deletions(-)
diff --git a/source/_components/alarm_control_panel.markdown b/source/_components/alarm_control_panel.markdown
index 8ae3f922130..12df0d474a5 100644
--- a/source/_components/alarm_control_panel.markdown
+++ b/source/_components/alarm_control_panel.markdown
@@ -7,12 +7,9 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Alarm
ha_release: 0.7.3
---
-Home Assistant can give you an interface with is similar to a classic alarm system. There are several panels supported:
-
-- [Alarm.com](/components/alarm_control_panel.alarmdotcom/)
-- [Manual](/components/alarm_control_panel.manual/)
-- [MQTT](/components/alarm_control_panel.mqtt/)
-- [Verisure](/components/verisure/)
+Home Assistant can give you an interface with is similar to a classic alarm system.
diff --git a/source/_components/binary_sensor.markdown b/source/_components/binary_sensor.markdown
index 41193b16c9a..f8e61cbd429 100644
--- a/source/_components/binary_sensor.markdown
+++ b/source/_components/binary_sensor.markdown
@@ -7,43 +7,13 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Binary Sensor
ha_release: 0.9
---
Binary sensors gather information about the state of devices which have a "digital" return value (either 1 or 0). These can be switches, contacts, pins, etc. These sensors only have two states: **0/off/low/closed/false** and **1/on/high/open/true**. Knowing that there are only two states allows Home Assistant to represent these sensors in a better way in the frontend according to their functionality.
-### {% linkable_title Device Class %}
-
-The way these sensors are displayed in the frontend can be modified in the [customize section](/getting-started/customizing-devices/). The following device classes are supported for binary sensors:
-
-- **None**: Generic on/off. This is the default and doesn't need to be set.
-- **battery**: `On` means low, `Off` means normal
-- **cold**: `On` means cold, `Off` means normal
-- **connectivity**: `On` means connected, `Off` means disconnected
-- **door**: `On` means open, `Off` means closed
-- **garage_door**: `On` means open, `Off` means closed
-- **gas**: `On` means gas detected, `Off` means no gas (clear)
-- **heat**: `On` means hot, `Off` means normal
-- **light**: `On` means light detected, `Off` means no light
-- **lock**: `On` means open (unlocked), `Off` means closed (locked)
-- **moisture**: `On` means moisture detected (wet), `Off` means no moisture (dry)
-- **motion**: `On` means motion detected, `Off` means no motion (clear)
-- **moving**: `On` means moving, `Off` means not moving (stopped)
-- **occupancy**: `On` means occupied, `Off` means not occupied (clear)
-- **opening**: `On` means open, `Off` means closed
-- **plug**: `On` means device is plugged in, `Off` means device is unplugged
-- **power**: `On` means power detected, `Off` means no power
-- **presence**: `On` means home, `Off` means away
-- **problem**: `On` means problem detected, `Off` means no problem (OK)
-- **safety**: `On` means unsafe, `Off` means safe
-- **smoke**: `On` means smoke detected, `Off` means no smoke (clear)
-- **sound**: `On` means sound detected, `Off` means no sound (clear)
-- **vibration**: `On` means vibration detected, `Off` means no vibration (clear)
-- **window**: `On` means open, `Off` means closed
-
-For analog sensors please check the [component overview](/components/#sensor).
-
-Example of various device classes icons in `On` and `Off` state.
diff --git a/source/_components/camera.markdown b/source/_components/camera.markdown
index bde3c074194..706ce094b9b 100644
--- a/source/_components/camera.markdown
+++ b/source/_components/camera.markdown
@@ -7,10 +7,24 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Camera
ha_release: 0.7
---
-The camera component allows you to use IP cameras with Home Assistant. With a little additional work you could use [USB cameras](/blog/2016/06/23/usb-webcams-and-home-assistant/) as well.
+The camera component allows you to use IP cameras with Home Assistant.
+
+### {% linkable_title Streaming Video %}
+
+If your camera supports it, and the [`stream`](/components/stream) component is setup, you will be able to stream your cameras in the frontend and on supported media players.
+
+This option will keep the stream alive, and preload the feed on Home Assistant startup. This will result in reduced latency when opening the stream in the frontend, as well as when using the `play_stream` service or Google Assistant integration. It does, however, utilize more resources on your machine, so it is recommended to check CPU usage if you plan to use this feature.
+
+
+
+ Example showing the Preload Stream option in the camera dialog.
+
+
### {% linkable_title Services %}
@@ -18,6 +32,26 @@ Once loaded, the `camera` platform will expose services that can be called to pe
Available services: `turn_on`, `turn_off`, `enable_motion_detection`, `disable_motion_detection`, `snapshot`, and `play_stream`.
+#### {% linkable_title Service `play_stream` %}
+
+Play a live stream from a camera to selected media player(s). Requires [`stream`](/components/stream) component to be set up.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | no | Name of entity to fetch stream from, e.g., `camera.living_room_camera`. |
+| `media_player` | no | Name of media player to play stream on, e.g., `media_player.living_room_tv`. |
+| `format` | yes | Stream format supported by `stream` component and selected `media_player`. Default: `hls` |
+
+For example, the following action in an automation would send an `hls` live stream to your chromecast.
+
+```yaml
+action:
+ service: camera.play_stream
+ data:
+ entity_id: camera.yourcamera
+ media_player: media_player.chromecast
+```
+
#### {% linkable_title Service `turn_on` %}
Turn on camera. Not all camera models support this service, please consult individual camera page.
@@ -100,26 +134,6 @@ action:
```
{% endraw %}
-#### {% linkable_title Service `play_stream` %}
-
-Play a live stream from a camera to selected media player(s). Requires [`stream`](/components/stream) component to be set up.
-
-| Service data attribute | Optional | Description |
-| ---------------------- | -------- | ----------- |
-| `entity_id` | no | Name of entity to fetch stream from, e.g., `camera.living_room_camera`. |
-| `media_player` | no | Name of media player to play stream on, e.g., `media_player.living_room_tv`. |
-| `format` | yes | Stream format supported by `stream` component and selected `media_player`. Default: `hls` |
-
-For example, the following action in an automation would send an `hls` live stream to your chromecast.
-
-```yaml
-action:
- service: camera.play_stream
- data:
- entity_id: camera.yourcamera
- media_player: media_player.chromecast
-```
-
### {% linkable_title Test if it works %}
A simple way to test if you have set up your `camera` platform correctly, is to use **Services** from the **Developer Tools**. Choose your service from the dropdown menu **Service**, enter something like the sample below into the **Service Data** field, and hit **CALL SERVICE**.
@@ -128,13 +142,4 @@ A simple way to test if you have set up your `camera` platform correctly, is to
{
"entity_id": "camera.living_room_camera"
}
-```
-
-### {% linkable_title Preload Stream %}
-
-If your camera supports it, and the [`stream`](/components/stream) component is setup, You will notice a "Preload Stream" option in the top right of the dialog when clicking to view the camera stream. This option will keep the stream alive, and preload the feed on Home Assistant startup. This will result in reduced latency when opening the stream in the frontend, as well as when using the `play_stream` service or Google Assistant integration. It does, however, utilize more resources on your machine, so it is recommended to check CPU usage if you plan to use this feature.
-
-
-
- Example showing the Preload Stream option in the camera dialog.
-
\ No newline at end of file
+```
\ No newline at end of file
diff --git a/source/_components/climate.markdown b/source/_components/climate.markdown
index 86b2d5e7ce9..40796752f8a 100644
--- a/source/_components/climate.markdown
+++ b/source/_components/climate.markdown
@@ -7,19 +7,12 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Climate
ha_release: 0.19
---
-
The `climate` component is built for the controlling and monitoring of HVAC (heating, ventilating, and air conditioning) and thermostat devices.
-
-To enable this component, pick one of the platforms, and add it to your `configuration.yaml`:
-
-```yaml
-# Example configuration.yaml entry
-climate:
- platform: demo
-```
## {% linkable_title Services %}
@@ -238,13 +231,3 @@ Turn climate device off
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Targets all when omitted.
-
-#### {% linkable_title Customization %}
-
-The step for the setpoint can be adjusted (default to 0,5 increments) by adding the following line into configuration
-
-```yaml
-customize:
- - entity_id
- target_temp_step: 1
-```
diff --git a/source/_components/cover.markdown b/source/_components/cover.markdown
index 34674ff60dc..b0842663293 100644
--- a/source/_components/cover.markdown
+++ b/source/_components/cover.markdown
@@ -7,33 +7,13 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Cover
ha_release: 0.27
---
Home Assistant can give you an interface to control covers such as rollershutters, blinds, and garage doors.
-The display style of each entity can be modified in the [customize section](/getting-started/customizing-devices/). Besides the basic ones like `friendly_name` or `hidden`, the following attributes are supported for covers:
-
-| Attribute | Default | Description |
-| --------- | ------- | ----------- |
-| `device_class` | | see below
-| `assumed_state` | `false` | If set to `true`, cover buttons will always be enabled
-
-### {% linkable_title Device Class %}
-
-The way these sensors are displayed in the frontend can be modified in the [customize section](/docs/configuration/customizing-devices/). The following device classes are supported for covers:
-
-- **None**: Generic cover. This is the default and doesn't need to be set.
-- **awning**: Control of an awning, such as an exterior retractable window, door, or patio cover.
-- **blind**: Control of blinds, which are linked slats that expand or collapse to cover an opening or may be tilted to partially covering an opening, such as window blinds.
-- **curtain**: Control of curtains or drapes, which is often fabric hung above a window or door that can be drawn open.
-- **damper**: Control of a mechanical damper that reduces airflow, sound, or light.
-- **door**: Control of a door or gate that provides access to an area.
-- **garage**: Control of a garage door that provides access to a garage.
-- **shade**: Control of shades, which are a continuous plane of material or connected cells that expanded or collapsed over an opening, such as window shades.
-- **shutter**: Control of shutters, which are linked slats that swing out/in to covering an opening or may be tilted to partially cover an opening, such as indoor or exterior window shutters.
-- **window**: Control of a physical window that opens and closes or may tilt.
-
## {% linkable_title Services %}
### {% linkable_title Cover control services %}
diff --git a/source/_components/device_tracker.markdown b/source/_components/device_tracker.markdown
index d4f699982b4..c2b958a1db2 100644
--- a/source/_components/device_tracker.markdown
+++ b/source/_components/device_tracker.markdown
@@ -7,14 +7,12 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Presence Detection
ha_release: 0.7
---
-Home Assistant can get information from your wireless router or third party services like iCloud or OwnTracks to track which devices are connected and considered "in home". Please check the sidebar for a list of brands of supported wireless routers and services.
-
-There are also trackers available which use different technologies like [MQTT](/components/mqtt/) or [Nmap](/components/nmap_tracker/) to scan the network for devices.
-
-An [event](/getting-started/automation-trigger/#event-trigger) (`device_tracker_new_device`) will be fired when a device is discovered for the first time.
+The device tracker allows you to track devices in Home Assistant. This can happen by querying your wireless router or by having applications push location info.
## {% linkable_title Configuring a `device_tracker` platform %}
@@ -24,8 +22,8 @@ To get started add the following lines to your `configuration.yaml` (example for
# Example configuration.yaml entry for Netgear device
device_tracker:
- platform: netgear
- host: 192.168.1.1
- username: admin
+ host: IP_ADDRESS
+ username: YOUR_USERNAME
password: YOUR_PASSWORD
new_device_defaults:
track_new_devices: true
@@ -54,8 +52,8 @@ The extended example from above would look like the following sample:
# Example configuration.yaml entry for Netgear device
device_tracker:
- platform: netgear
- host: 192.168.1.1
- username: admin
+ host: IP_ADDRESS
+ username: YOUR_USERNAME
interval_seconds: 10
consider_home: 180
new_device_defaults:
@@ -94,24 +92,6 @@ devicename:
| `hide_if_away` | false | If `yes`/`on`/`true` then the device will be hidden if it is not at home. |
| `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. |
-## {% linkable_title Using GPS device trackers with local network device trackers %}
-
-GPS based device trackers (like [OwnTracks](/components/owntracks/), [GPSLogger](/components/gpslogger) and others) can also be used with local network device trackers, such as [Nmap](/components/nmap_tracker/) or [Netgear](/components/netgear/). To do this, fill in the `mac` field to the entry in `known_devices.yaml` with the MAC address of the device you want to track. This way the state of the device will be determined by *the source that reported last*. The naming convention for known device list is `_` and could be set in the app configuration.
-
-An example showing the inclusion of the `mac` field for multiple platform tracking. The `mac` field was added to the GPS based device tracker entry and will enable tracking by all platforms that track via the `mac` address.
-
-```yaml
-USERNAME_DEVICE_ID:
- name: Friendly Name
- mac: EA:AA:55:E7:C6:94
- picture: https://www.home-assistant.io/images/favicon-192x192.png
- gravatar: test@example.com
- track: true
- hide_if_away: false
-```
-
-If you want to track whether either your GPS based tracker or your local network tracker, identify you as being at home, use [a group](/components/group/) instead.
-
## {% linkable_title Device states %}
The state of your tracked device will be `'home'` if it is in the [home zone](/components/zone#home-zone), detected by your network or Bluetooth based presence detection. If you're using a presence detection method that includes coordinates then when it's in a zone the state will be the name of the zone (case sensitive). When a device isn't at home and isn't in any zone, the state will be `'not_home'`.
diff --git a/source/_components/fan.markdown b/source/_components/fan.markdown
index 4b306d1ef68..fcb577171d7 100644
--- a/source/_components/fan.markdown
+++ b/source/_components/fan.markdown
@@ -7,17 +7,9 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Fan
ha_release: 0.27
---
-
-The `fan` component is built for the controlling of fan devices. It can be called the little brother of the [climate](/components/climate/) component.
-
-To enable this component, pick one of the platforms, and add it to your `configuration.yaml`:
-
-```yaml
-# Example configuration.yaml entry
-climate:
- platform: fan
-```
-
+The `fan` component is built for the controlling of fan devices.
diff --git a/source/_components/light.markdown b/source/_components/light.markdown
index 45c0bd022b9..a1fd6ec5f51 100644
--- a/source/_components/light.markdown
+++ b/source/_components/light.markdown
@@ -7,14 +7,12 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Light
ha_release: pre 0.7
---
-This component allows you to track and control various light bulbs. Read the platform documentation for your particular light hardware to learn how to enable it.
-
-
-The light component supports multiple entries in configuration.yaml by appending a sequential number to the section: light 2:, light 3: etc.
-
+This component allows you to track and control various light bulbs. Read the integration documentation for your particular light hardware to learn how to enable it.
### {% linkable_title Default turn-on values %}
@@ -26,7 +24,7 @@ The `.default` suffix should be added to the entity identifier of each light to
Turns one light on or multiple lights on using [groups]({{site_root}}/components/group/).
-Most lights do not support all attributes. You can check the platform documentation of your particular light for hints, but in general, you will have to try things out and see what works.
+Most lights do not support all attributes. You can check the integration documentation of your particular light for hints, but in general, you will have to try things out and see what works.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
diff --git a/source/_components/lock.markdown b/source/_components/lock.markdown
index f57fa53b0bb..17066c9fddd 100644
--- a/source/_components/lock.markdown
+++ b/source/_components/lock.markdown
@@ -7,6 +7,8 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Lock
ha_release: 0.9
---
diff --git a/source/_components/media_player.markdown b/source/_components/media_player.markdown
index 5bfb1c3fd08..f00ec9b13b7 100644
--- a/source/_components/media_player.markdown
+++ b/source/_components/media_player.markdown
@@ -7,10 +7,12 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Media Player
ha_release: 0.7
---
-Interacts with media players on your network. Please check the right sidebar for a full list of supported devices.
+Interacts with media players on your network.
## {% linkable_title Services %}
diff --git a/source/_components/notify.markdown b/source/_components/notify.markdown
index bab55206cc5..444c59c441e 100644
--- a/source/_components/notify.markdown
+++ b/source/_components/notify.markdown
@@ -7,6 +7,8 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Notifications
ha_release: 0.7
---
@@ -14,19 +16,7 @@ The `notify` component makes it possible to send notifications to a wide variety
If you want to send notifications to the Home Assistant Web Interface you may use the [Persistent Notification Component](/components/persistent_notification/).
-## {% linkable_title Configuration %}
-
-```yaml
-# Example configuration.yaml entry
-notify:
- - platform: pushbullet
- name: NOTIFY_NAME
- api_key: YOUR_API_KEY
-```
-
-The **name** parameter is optional but needed if you want to use multiple platforms. The platform will be exposed as service `notify.`. The name will default to `notify` if not supplied.
-
-### {% linkable_title Service %}
+## {% linkable_title Service %}
Once loaded, the `notify` platform will expose a service that can be called to send notifications.
diff --git a/source/_components/sensor.markdown b/source/_components/sensor.markdown
index 3e021d1d06a..5d7613f0834 100644
--- a/source/_components/sensor.markdown
+++ b/source/_components/sensor.markdown
@@ -7,28 +7,15 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Sensor
ha_release: 0.7
---
Sensors are gathering information about states and conditions.
-Home Assistant currently supports a wide range of sensors. They are able to display information which are provides by Home Assistant directly, are gathered from web services, and, of course, physical devices. Please check the sidebar for a full list of supported sensor platforms.
-
-## {% linkable_title Device Class %}
-
-The way these sensors are displayed in the frontend can be modified in the [customize section](/docs/configuration/customizing-devices/). The following device classes are supported for sensors:
-
-- **None**: Generic sensor. This is the default and doesn't need to be set.
-- **battery**: Percentage of battery that is left.
-- **humidity**: Percentage of humidity in the air.
-- **illuminance**: The current light level in lx or lm.
-- **signal_strength**: Signal strength in dB or dBm.
-- **temperature**: Temperature in °C or °F.
-- **power**: Power in W or kW.
-- **pressure**: Pressure in hPa or mbar.
-- **timestamp**: Datetime object or timestamp string.
+Home Assistant currently supports a wide range of sensors. They are able to display information which are provides by Home Assistant directly, are gathered from web services, and, of course, physical devices.
-Example of various device class icons for sensors.
diff --git a/source/_components/switch.markdown b/source/_components/switch.markdown
index 097a394df9b..f8996d801ed 100644
--- a/source/_components/switch.markdown
+++ b/source/_components/switch.markdown
@@ -7,6 +7,8 @@ sidebar: true
comments: false
sharing: true
footer: true
+ha_category:
+ - Switch
ha_release: 0.7
---
From 7fca29f878fb6b38381283bca3b4e0c53aeac81b Mon Sep 17 00:00:00 2001
From: Colin Frei
Date: Sat, 1 Jun 2019 10:01:55 +0200
Subject: [PATCH 026/123] Clarify that the free tier is limited (#9542)
* Clarify that the free tier is limited
* :pencil2: Tweak
---
source/_components/pushbullet.markdown | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/source/_components/pushbullet.markdown b/source/_components/pushbullet.markdown
index ecab9b1caca..98f67c88305 100644
--- a/source/_components/pushbullet.markdown
+++ b/source/_components/pushbullet.markdown
@@ -23,6 +23,10 @@ There is currently support for the following device types within Home Assistant:
- [Sensor](#sensor)
- [Notifications](#notifications)
+
+The free tier is [limited](https://docs.pushbullet.com/#push-limit) to 500 pushes per month.
+
+
### {% linkable_title Sensor %}
The `pushbullet` sensor platform reads messages from [Pushbullet](https://www.pushbullet.com/), a free service to send information between your phones, browsers, and friends. This sensor platform provides sensors that show the properties of the latest received Pushbullet notification mirror.
@@ -83,7 +87,7 @@ All properties will be displayed as attributes. The properties array are just fo
## {% linkable_title Notifications %}
-The `pushbullet` notification platform sends messages to [Pushbullet](https://www.pushbullet.com/), a free service to send information between your phones, browsers, and friends.
+The `pushbullet` notification platform sends messages to [Pushbullet](https://www.pushbullet.com/), a free service to send information between your phones, browsers, and friends. The free tier is [limited](https://docs.pushbullet.com/#push-limit) to 500 pushes per month.
To enable Pushbullet notifications in your installation, add the following to your `configuration.yaml` file:
@@ -191,4 +195,4 @@ action:
Don't forget to [whitelist external directories](/docs/configuration/basic/), so Home Assistant has access to them.
-
\ No newline at end of file
+
From b0e07fab9812e52725e6c0da30e5ec2fc572530d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?M=C3=A5rten=20Seiplax?=
Date: Sat, 1 Jun 2019 21:04:29 +0300
Subject: [PATCH 027/123] Fix 404 link for react example (#9546)
The link for the react example returns a 404
Seems it has been moved to https://github.com/home-assistant/custom-panel-starter-kit-react
Updated the link description for better accessibility (when used with text-to-speech software used by visually impaired users).
---
source/_cookbook/custom_panel_using_react.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_cookbook/custom_panel_using_react.markdown b/source/_cookbook/custom_panel_using_react.markdown
index e526487b0c5..f63db13c591 100644
--- a/source/_cookbook/custom_panel_using_react.markdown
+++ b/source/_cookbook/custom_panel_using_react.markdown
@@ -18,7 +18,7 @@ This is a [React](https://facebook.github.io/react/) implementation of [TodoMVC]
- It uses the user configuration for the component in the `configuration.yaml` file for rendering.
- It allows toggling the sidebar.
-Download the source [here](https://github.com/home-assistant/example-custom-config/blob/master/panels/react.html). Copy the file to `/panels/` (you might have to create the directory if it doesn't exist).
+[Download the source for React Starter Kit here](https://github.com/home-assistant/custom-panel-starter-kit-react). Copy the file to `/panels/` (you might have to create the directory if it doesn't exist).
Create an entry for the panel in your `configuration.yaml` file to enable it.
From 11497d8d82141dbf19e25dae77f32453168f9b53 Mon Sep 17 00:00:00 2001
From: Klaas Schoute
Date: Sat, 1 Jun 2019 21:37:40 +0200
Subject: [PATCH 028/123] :hammer: Add logo and quality scale (#9543)
---
source/_components/alarm_control_panel.markdown | 2 ++
source/_components/binary_sensor.markdown | 2 ++
source/_components/camera.markdown | 2 ++
source/_components/climate.markdown | 2 ++
source/_components/cover.markdown | 2 ++
source/_components/device_tracker.markdown | 2 ++
source/_components/fan.markdown | 2 ++
source/_components/light.markdown | 2 ++
source/_components/lock.markdown | 2 ++
source/_components/media_player.markdown | 2 ++
source/_components/notify.markdown | 2 ++
source/_components/sensor.markdown | 2 ++
source/_components/switch.markdown | 2 ++
13 files changed, 26 insertions(+)
diff --git a/source/_components/alarm_control_panel.markdown b/source/_components/alarm_control_panel.markdown
index 12df0d474a5..3c39b71b480 100644
--- a/source/_components/alarm_control_panel.markdown
+++ b/source/_components/alarm_control_panel.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Alarm
+ha_qa_scale: internal
ha_release: 0.7.3
---
diff --git a/source/_components/binary_sensor.markdown b/source/_components/binary_sensor.markdown
index f8e61cbd429..6206478e09c 100644
--- a/source/_components/binary_sensor.markdown
+++ b/source/_components/binary_sensor.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Binary Sensor
+ha_qa_scale: internal
ha_release: 0.9
---
diff --git a/source/_components/camera.markdown b/source/_components/camera.markdown
index 706ce094b9b..a8a4b967042 100644
--- a/source/_components/camera.markdown
+++ b/source/_components/camera.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Camera
+ha_qa_scale: internal
ha_release: 0.7
---
diff --git a/source/_components/climate.markdown b/source/_components/climate.markdown
index 40796752f8a..131d13309b4 100644
--- a/source/_components/climate.markdown
+++ b/source/_components/climate.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Climate
+ha_qa_scale: internal
ha_release: 0.19
---
diff --git a/source/_components/cover.markdown b/source/_components/cover.markdown
index b0842663293..81b753f4314 100644
--- a/source/_components/cover.markdown
+++ b/source/_components/cover.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Cover
+ha_qa_scale: internal
ha_release: 0.27
---
diff --git a/source/_components/device_tracker.markdown b/source/_components/device_tracker.markdown
index c2b958a1db2..c6b6292ef28 100644
--- a/source/_components/device_tracker.markdown
+++ b/source/_components/device_tracker.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Presence Detection
+ha_qa_scale: internal
ha_release: 0.7
---
diff --git a/source/_components/fan.markdown b/source/_components/fan.markdown
index fcb577171d7..37631338b93 100644
--- a/source/_components/fan.markdown
+++ b/source/_components/fan.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Fan
+ha_qa_scale: internal
ha_release: 0.27
---
diff --git a/source/_components/light.markdown b/source/_components/light.markdown
index a1fd6ec5f51..cc0563c73c6 100644
--- a/source/_components/light.markdown
+++ b/source/_components/light.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Light
+ha_qa_scale: internal
ha_release: pre 0.7
---
diff --git a/source/_components/lock.markdown b/source/_components/lock.markdown
index 17066c9fddd..065cf915907 100644
--- a/source/_components/lock.markdown
+++ b/source/_components/lock.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Lock
+ha_qa_scale: internal
ha_release: 0.9
---
diff --git a/source/_components/media_player.markdown b/source/_components/media_player.markdown
index f00ec9b13b7..7a0bbe6d858 100644
--- a/source/_components/media_player.markdown
+++ b/source/_components/media_player.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Media Player
+ha_qa_scale: internal
ha_release: 0.7
---
diff --git a/source/_components/notify.markdown b/source/_components/notify.markdown
index 444c59c441e..87df0e81f63 100644
--- a/source/_components/notify.markdown
+++ b/source/_components/notify.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Notifications
+ha_qa_scale: internal
ha_release: 0.7
---
diff --git a/source/_components/sensor.markdown b/source/_components/sensor.markdown
index 5d7613f0834..d28f8a51528 100644
--- a/source/_components/sensor.markdown
+++ b/source/_components/sensor.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Sensor
+ha_qa_scale: internal
ha_release: 0.7
---
diff --git a/source/_components/switch.markdown b/source/_components/switch.markdown
index f8996d801ed..acf851afdf6 100644
--- a/source/_components/switch.markdown
+++ b/source/_components/switch.markdown
@@ -7,8 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
+logo: home-assistant.png
ha_category:
- Switch
+ha_qa_scale: internal
ha_release: 0.7
---
From b346a03336258021fabf96b501b904ecb8ec15fc Mon Sep 17 00:00:00 2001
From: Klaas Schoute
Date: Sun, 2 Jun 2019 22:36:08 +0200
Subject: [PATCH 029/123] =?UTF-8?q?=E2=9C=8F=EF=B8=8F=20Fix=20broken=20lin?=
=?UTF-8?q?k=20in=20configurator=20component=20(#9553)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
source/_components/configurator.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/source/_components/configurator.markdown b/source/_components/configurator.markdown
index bb862023a4c..1778daa4ee7 100644
--- a/source/_components/configurator.markdown
+++ b/source/_components/configurator.markdown
@@ -24,6 +24,6 @@ The configurator component allows components to request information from the use
- Input fields can be defined with a description, and optional type
- It will trigger a callback when the button is pressed
-The Hue component in [the demo](/demo) and Plex are implemented using the configurator. See [the source of the demo component](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/demo.py#L132) for a simple example.
+The Hue component in [the demo](/demo) and Plex are implemented using the configurator. See [the source of the demo component](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/demo) for a simple example.
-See [the source](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/configurator.py#L39) for more details on how to use the configurator component.
+See [the source](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/configurator) for more details on how to use the configurator component.
From 7aad455bbf60d0d976bfcb71a38454b6d9d175c9 Mon Sep 17 00:00:00 2001
From: Klaas Schoute
Date: Mon, 3 Jun 2019 20:16:01 +0200
Subject: [PATCH 030/123] =?UTF-8?q?=F0=9F=94=A8=20Change=20the=20device=20?=
=?UTF-8?q?class=20description=20(#9544)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
* :hammer: Change URLs to device classes on dev page
* :hammer: The other url's
* :pencil2: Improve the description
* :hammer: Revert the suggested urls
---
source/_components/ads.markdown | 4 ++--
source/_components/binary_sensor.knx.markdown | 2 +-
source/_components/binary_sensor.mqtt.markdown | 2 +-
source/_components/binary_sensor.rest.markdown | 4 +---
source/_components/binary_sensor.rflink.markdown | 2 +-
source/_components/binary_sensor.rfxtrx.markdown | 2 +-
source/_components/binary_sensor.template.markdown | 2 +-
source/_components/command_line.markdown | 3 ++-
source/_components/cover.mqtt.markdown | 2 +-
source/_components/cover.template.markdown | 2 +-
source/_components/enocean.markdown | 4 ++--
source/_components/raspihats.markdown | 2 +-
source/_components/rest.markdown | 4 +---
source/_components/trend.markdown | 4 +---
source/_components/w800rf32.markdown | 2 +-
15 files changed, 18 insertions(+), 23 deletions(-)
diff --git a/source/_components/ads.markdown b/source/_components/ads.markdown
index 2c285b2ebbc..96adb3de43d 100644
--- a/source/_components/ads.markdown
+++ b/source/_components/ads.markdown
@@ -102,7 +102,7 @@ name:
required: false
type: string
device_class:
- description: The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: string
{% endconfiguration %}
@@ -250,6 +250,6 @@ name:
type: string
device_class:
required: false
- description: Sets the class of the device, changing the device state and icon that is displayed on the UI (awning, blind, curtain, damper, door, garage, shade, shutter, window)
+ description: Sets the [class of the device](/components/cover/), changing the device state and icon that is displayed on the frontend.
type: device_class
{% endconfiguration %}
diff --git a/source/_components/binary_sensor.knx.markdown b/source/_components/binary_sensor.knx.markdown
index f144ff47952..c0351d17788 100644
--- a/source/_components/binary_sensor.knx.markdown
+++ b/source/_components/binary_sensor.knx.markdown
@@ -37,7 +37,7 @@ name:
required: false
type: string
device_class:
- description: HASS device class e.g., "motion".
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: string
significant_bit:
diff --git a/source/_components/binary_sensor.mqtt.markdown b/source/_components/binary_sensor.mqtt.markdown
index 7cccd22aa10..3aec89fc491 100644
--- a/source/_components/binary_sensor.mqtt.markdown
+++ b/source/_components/binary_sensor.mqtt.markdown
@@ -87,7 +87,7 @@ unique_id:
required: false
type: string
device_class:
- description: The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: string
value_template:
diff --git a/source/_components/binary_sensor.rest.markdown b/source/_components/binary_sensor.rest.markdown
index 46ece211e90..b35c6ba008a 100644
--- a/source/_components/binary_sensor.rest.markdown
+++ b/source/_components/binary_sensor.rest.markdown
@@ -73,9 +73,7 @@ name:
type: string
default: REST Binary Sensor
device_class:
- description: >
- The [type/class](/components/binary_sensor/) of
- the sensor to set the icon in the frontend.
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: string
value_template:
diff --git a/source/_components/binary_sensor.rflink.markdown b/source/_components/binary_sensor.rflink.markdown
index bfc0979f0a8..11426bff5e6 100644
--- a/source/_components/binary_sensor.rflink.markdown
+++ b/source/_components/binary_sensor.rflink.markdown
@@ -55,7 +55,7 @@ devices:
required: false
type: list
device_class:
- description: The [type or class of the sensor](/components/binary_sensor/#device-class) to set the icon in the frontend.
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: string
off_delay:
diff --git a/source/_components/binary_sensor.rfxtrx.markdown b/source/_components/binary_sensor.rfxtrx.markdown
index 571af036e8d..1049752bb7c 100644
--- a/source/_components/binary_sensor.rfxtrx.markdown
+++ b/source/_components/binary_sensor.rfxtrx.markdown
@@ -63,7 +63,7 @@ devices:
required: false
type: string
device_class:
- description: "The [type or class of the sensor](/components/binary_sensor/) to set the icon in the frontend."
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: device_class
fire_event:
diff --git a/source/_components/binary_sensor.template.markdown b/source/_components/binary_sensor.template.markdown
index 71cb01894b7..521757fbb1e 100644
--- a/source/_components/binary_sensor.template.markdown
+++ b/source/_components/binary_sensor.template.markdown
@@ -56,7 +56,7 @@ sensors:
required: false
type: string, list
device_class:
- description: The type/class of the sensor to set the icon in the frontend.
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: device_class
default: None
diff --git a/source/_components/command_line.markdown b/source/_components/command_line.markdown
index 3fe4193a592..76fd3b8e9c4 100644
--- a/source/_components/command_line.markdown
+++ b/source/_components/command_line.markdown
@@ -31,6 +31,7 @@ binary_sensor:
It's highly recommended to enclose the command in single quotes `'` as it ensures all characters can be used in the command and reduces the risk of unintentional escaping. To include a single quote in a command enclosed in single quotes, double it: `''`.
+
{% configuration %}
command:
description: The action to take to get the value.
@@ -42,7 +43,7 @@ name:
type: string
default: "*name* from the device"
device_class:
- description: The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: string
payload_on:
diff --git a/source/_components/cover.mqtt.markdown b/source/_components/cover.mqtt.markdown
index acf37e99e42..45454e6eae9 100644
--- a/source/_components/cover.mqtt.markdown
+++ b/source/_components/cover.mqtt.markdown
@@ -175,7 +175,7 @@ tilt_invert_state:
type: boolean
default: false
device_class:
- description: The [type/class](/components/cover/#device-class) of the cover to set the icon in the frontend.
+ description: Sets the [class of the device](/components/cover/), changing the device state and icon that is displayed on the frontend.
required: false
type: string
json_attributes_topic:
diff --git a/source/_components/cover.template.markdown b/source/_components/cover.template.markdown
index e4813769784..5f1188e5493 100644
--- a/source/_components/cover.template.markdown
+++ b/source/_components/cover.template.markdown
@@ -69,7 +69,7 @@ cover:
required: false
type: template
device_class:
- description: The [type/class](/components/cover/#device-class) of the cover to set the icon in the frontend.
+ description: Sets the [class of the device](/components/cover/), changing the device state and icon that is displayed on the frontend.
required: false
type: string
open_cover:
diff --git a/source/_components/enocean.markdown b/source/_components/enocean.markdown
index 5cbce8bce6b..ada39a33b6e 100644
--- a/source/_components/enocean.markdown
+++ b/source/_components/enocean.markdown
@@ -102,7 +102,7 @@ name:
type: string
default: EnOcean binary sensor
device_class:
- description: The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: device_class
{% endconfiguration %}
@@ -193,7 +193,7 @@ name:
type: string
default: EnOcean sensor
device_class:
- description: The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: device_class
default: powersensor
diff --git a/source/_components/raspihats.markdown b/source/_components/raspihats.markdown
index fc266f4975c..bf229a3eb14 100644
--- a/source/_components/raspihats.markdown
+++ b/source/_components/raspihats.markdown
@@ -78,7 +78,7 @@ i2c_hats:
default: false
type: boolean
device_class:
- description: See device classes in [binary_sensor component](/components/binary_sensor/).
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
default: "None"
type: string
diff --git a/source/_components/rest.markdown b/source/_components/rest.markdown
index 835a7b98218..5536b035395 100644
--- a/source/_components/rest.markdown
+++ b/source/_components/rest.markdown
@@ -55,9 +55,7 @@ name:
type: string
default: REST Sensor
device_class:
- description: >
- The [type/class](/components/sensor/) of
- the sensor to set the icon in the frontend.
+ description: Sets the [class of the device](/components/sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: string
value_template:
diff --git a/source/_components/trend.markdown b/source/_components/trend.markdown
index 78c22c87c7b..1d9637e8319 100644
--- a/source/_components/trend.markdown
+++ b/source/_components/trend.markdown
@@ -54,9 +54,7 @@ sensors:
required: false
type: string
device_class:
- description: >
- The [type/class](/components/binary_sensor/#device-class) of
- the sensor to set the icon in the frontend.
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: string
friendly_name:
diff --git a/source/_components/w800rf32.markdown b/source/_components/w800rf32.markdown
index f2b7cece328..0012c015039 100644
--- a/source/_components/w800rf32.markdown
+++ b/source/_components/w800rf32.markdown
@@ -68,7 +68,7 @@ devices:
required: false
type: string
device_class:
- description: "The [type or class of the sensor](/components/binary_sensor/) to set the icon in the frontend."
+ description: Sets the [class of the device](/components/binary_sensor/), changing the device state and icon that is displayed on the frontend.
required: false
type: device_class
off_delay:
From e599084f8efb3c75e1b0444b05359b5dac9b6de5 Mon Sep 17 00:00:00 2001
From: klaasnicolaas
Date: Mon, 3 Jun 2019 20:19:46 +0200
Subject: [PATCH 031/123] :rewind: Put the device classes back
---
source/_components/binary_sensor.markdown | 34 ++++++++++++++++++++++-
source/_components/cover.markdown | 15 ++++++++++
source/_components/sensor.markdown | 15 ++++++++++
3 files changed, 63 insertions(+), 1 deletion(-)
diff --git a/source/_components/binary_sensor.markdown b/source/_components/binary_sensor.markdown
index 6206478e09c..2d83527eed8 100644
--- a/source/_components/binary_sensor.markdown
+++ b/source/_components/binary_sensor.markdown
@@ -14,8 +14,40 @@ ha_qa_scale: internal
ha_release: 0.9
---
-Binary sensors gather information about the state of devices which have a "digital" return value (either 1 or 0). These can be switches, contacts, pins, etc. These sensors only have two states: **0/off/low/closed/false** and **1/on/high/open/true**. Knowing that there are only two states allows Home Assistant to represent these sensors in a better way in the frontend according to their functionality.
+Binary sensors gather information about the state of devices which have a "digital" return value (either 1 or 0). These can be switches, contacts, pins, etc. These sensors only have two states: **0/off/low/closed/false** and **1/on/high/open/true**. Knowing that there are only two states allows Home Assistant to represent these sensors in a better way in the frontend according to their functionality.
+
+### {% linkable_title Device Class %}
+
+The way these sensors are displayed in the frontend can be modified in the [customize section](/getting-started/customizing-devices/). The following device classes are supported for binary sensors:
+
+- **None**: Generic on/off. This is the default and doesn't need to be set.
+- **battery**: `On` means low, `Off` means normal
+- **cold**: `On` means cold, `Off` means normal
+- **connectivity**: `On` means connected, `Off` means disconnected
+- **door**: `On` means open, `Off` means closed
+- **garage_door**: `On` means open, `Off` means closed
+- **gas**: `On` means gas detected, `Off` means no gas (clear)
+- **heat**: `On` means hot, `Off` means normal
+- **light**: `On` means light detected, `Off` means no light
+- **lock**: `On` means open (unlocked), `Off` means closed (locked)
+- **moisture**: `On` means moisture detected (wet), `Off` means no moisture (dry)
+- **motion**: `On` means motion detected, `Off` means no motion (clear)
+- **moving**: `On` means moving, `Off` means not moving (stopped)
+- **occupancy**: `On` means occupied, `Off` means not occupied (clear)
+- **opening**: `On` means open, `Off` means closed
+- **plug**: `On` means device is plugged in, `Off` means device is unplugged
+- **power**: `On` means power detected, `Off` means no power
+- **presence**: `On` means home, `Off` means away
+- **problem**: `On` means problem detected, `Off` means no problem (OK)
+- **safety**: `On` means unsafe, `Off` means safe
+- **smoke**: `On` means smoke detected, `Off` means no smoke (clear)
+- **sound**: `On` means sound detected, `Off` means no sound (clear)
+- **vibration**: `On` means vibration detected, `Off` means no vibration (clear)
+- **window**: `On` means open, `Off` means closed
+
+For analog sensors please check the [component overview](/components/#sensor).
+Example of various device classes icons in `On` and `Off` state.
diff --git a/source/_components/cover.markdown b/source/_components/cover.markdown
index 81b753f4314..90172534114 100644
--- a/source/_components/cover.markdown
+++ b/source/_components/cover.markdown
@@ -16,6 +16,21 @@ ha_release: 0.27
Home Assistant can give you an interface to control covers such as rollershutters, blinds, and garage doors.
+## {% linkable_title Device Class %}
+
+The way these sensors are displayed in the frontend can be modified in the [customize section](/docs/configuration/customizing-devices/). The following device classes are supported for covers:
+
+- **None**: Generic cover. This is the default and doesn't need to be set.
+- **awning**: Control of an awning, such as an exterior retractable window, door, or patio cover.
+- **blind**: Control of blinds, which are linked slats that expand or collapse to cover an opening or may be tilted to partially covering an opening, such as window blinds.
+- **curtain**: Control of curtains or drapes, which is often fabric hung above a window or door that can be drawn open.
+- **damper**: Control of a mechanical damper that reduces airflow, sound, or light.
+- **door**: Control of a door or gate that provides access to an area.
+- **garage**: Control of a garage door that provides access to a garage.
+- **shade**: Control of shades, which are a continuous plane of material or connected cells that expanded or collapsed over an opening, such as window shades.
+- **shutter**: Control of shutters, which are linked slats that swing out/in to covering an opening or may be tilted to partially cover an opening, such as indoor or exterior window shutters.
+- **window**: Control of a physical window that opens and closes or may tilt.
+
## {% linkable_title Services %}
### {% linkable_title Cover control services %}
diff --git a/source/_components/sensor.markdown b/source/_components/sensor.markdown
index d28f8a51528..e7b677297c3 100644
--- a/source/_components/sensor.markdown
+++ b/source/_components/sensor.markdown
@@ -18,6 +18,21 @@ Sensors are gathering information about states and conditions.
Home Assistant currently supports a wide range of sensors. They are able to display information which are provides by Home Assistant directly, are gathered from web services, and, of course, physical devices.
+## {% linkable_title Device Class %}
+
+The way these sensors are displayed in the frontend can be modified in the [customize section](/docs/configuration/customizing-devices/). The following device classes are supported for sensors:
+
+- **None**: Generic sensor. This is the default and doesn't need to be set.
+- **battery**: Percentage of battery that is left.
+- **humidity**: Percentage of humidity in the air.
+- **illuminance**: The current light level in lx or lm.
+- **signal_strength**: Signal strength in dB or dBm.
+- **temperature**: Temperature in °C or °F.
+- **power**: Power in W or kW.
+- **pressure**: Pressure in hPa or mbar.
+- **timestamp**: Datetime object or timestamp string.
+
+Example of various device class icons for sensors.
From b4cae19d564393f5a22ee173727fdf31b62453c7 Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Mon, 3 Jun 2019 14:03:20 -0700
Subject: [PATCH 032/123] Update blog post 94
---
source/_posts/2019-06-05-release-94.markdown | 50 ++++++++++++++----
.../blog/2019-06-release-94/google-ui.png | Bin 0 -> 81847 bytes
2 files changed, 41 insertions(+), 9 deletions(-)
create mode 100644 source/images/blog/2019-06-release-94/google-ui.png
diff --git a/source/_posts/2019-06-05-release-94.markdown b/source/_posts/2019-06-05-release-94.markdown
index b773f6691e0..8d67dd662e7 100644
--- a/source/_posts/2019-06-05-release-94.markdown
+++ b/source/_posts/2019-06-05-release-94.markdown
@@ -13,15 +13,47 @@ og_image: /images/blog/2019-06-release-94/components.png
-New:
- - Possible to store core config in storage. If set in configuration.yaml, it will override storage (this is what anyone coming from 0.93 has). Note that configuration.yaml will no longer contain any automatic detected values when writing initial configuration. This feature is available via the UI during onboarding. Big thanks to [@emontnemery] for this contribution.
- - Allow deletion of scripts/automations via the UI editor.
- - This is the first release where a user can use a subset of Home Assistant without using configuration.yaml.
- - Step added to onboarding to allow configuring name, location, timezone and unit system.
- - Python 3.5.3 deprecated, support will be dropped in the first release after August 1.
- - Add UI to manage Google Entities exposed via Home Assistant Cloud. To use, remove filters from configuration.yaml. Also allows disabling 2 factor authentication on a per device basis.
- - Discovery has been redone. Integrations can now specify how they are discoverable via Zeroconf, SSDP or HomeKit in their manifest, this will be picked up by the zeroconf and ssdp integrations, which are part of the default config. The new discovery is non-obtrusive: nothing is added to your configuration without approval by the user. You can find integrations pending approval in the discovered section of the integrations page in the config. Only a handful of integrations have been migrated to the new approach in this release. Thanks to [@Kane610], [@Jc2k]. If you are not using the `default_config` integration, add `ssdp:` and `zeroconf:` to your configuration.yaml.
- - We are bringing the device tracker integration into the age of modern integrations. The first step has been to migrating the platforms that use config entries like OwnTracks and GPSLogger. This means that for these integrations, you will now be able to use things like entity registry to change entity ID and name.
+It is time for the 0.94 release and there is some seriously good stuff in this release. We're working hard on polishing everything and getting ready for the big Home Assistant 1.0 release. And we're getting closer. So close actually, that this is the first release that can be installed and configured without touching any `configuration.yaml`! Onboard, configure integrations, manage automations and scripts all from the UI.
+
+
The 0.94 release of @home_assistant will be the first release where you can onboard, configure integrations (not all) and set up automations without touching configuration.yaml. pic.twitter.com/AZNG1VWhF1
+
+This milestone has been achieved thanks to the hard work by [@emontnemery] who contributed the ability to store the core config in storage: name, location, unit system, time zone. We still allow users to store their core configuration in `configuration.yaml`, which will take precedent when defined. This means that it is a non-breaking change. Core config is now set during onboarding and can be edited in the general page of the config panel.
+
+Another cool new feature is the total revamp of how you manage which entities are exposed to Google Assistant via Home Assistant Cloud. From the cloud UI you can now click "Manage Entities" and you are brought to the Google Assistant entity manager. From here you can enable which entities are exposed and, if you deem appropriate, choose to disable the two factor authentication on your garage door (the asking for a pin).
+
+
+
+Screenshot of the new user interface to manage which entities are exposed to Google Assistant.
+