From 91bf714e891efd8d893ae6863ab6b327af916f50 Mon Sep 17 00:00:00 2001
From: ochlocracy <5885236+ochlocracy@users.noreply.github.com>
Date: Thu, 12 Mar 2020 15:03:01 -0400
Subject: [PATCH 06/12] =?UTF-8?q?Update=20Alexa=20Smart=20Home=20Light=20t?=
=?UTF-8?q?o=20include=20brightness,=20color,=20te=E2=80=A6=20(#12345)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
and color.
---
.../_integrations/alexa.smart_home.markdown | 54 ++++++++++++++++++-
1 file changed, 53 insertions(+), 1 deletion(-)
diff --git a/source/_integrations/alexa.smart_home.markdown b/source/_integrations/alexa.smart_home.markdown
index 13935cca955..9724bc298df 100644
--- a/source/_integrations/alexa.smart_home.markdown
+++ b/source/_integrations/alexa.smart_home.markdown
@@ -424,6 +424,9 @@ The following integrations are currently supported:
- [Input Number](#input-number)
- [Image Processing](#image-processing)
- [Light](#light)
+ - [Brightness](#brightness)
+ - [Color Temperature](#color-temperature)
+ - [Color](#color)
- [Lock](#lock)
- [Media Player](#media-player)
- [Channels](#change-channel)
@@ -760,8 +763,57 @@ The following table lists the possible friendly name synonyms available for a In
### Light
-- _"Alexa, dim the bathroom light."_
+Control lights with _"turn on"_ and _"turn off"_ utterances, adjust brightness, color, and temperature.
+
+- _"Alexa, turn on the bathroom light."_
+- _"Alexa, turn off the patio light."_
+
+#### Brightness
+
+Lights that support brightness can be adjusted with percentages ranging from 0 to 100 percent.
+
- _"Alexa, set the bedroom light to fifty percent."_
+- _"Alexa, living room lights to one hundred percent."_
+
+The _"dim"_ utterance will decrease the brightness of a light 25 percentage points.
+
+- _"Alexa, dim the bathroom light."_
+
+#### Color Temperature
+
+Adjust lights that support color temperature using the following friendly names:
+
+- _"Alexa, set the dining room softer."_
+- _"Alexa, make the living room warmer."_
+- _"Alexa, set the dining room cooler."_
+- _"Alexa, make the living room light whiter."_
+- _"Alexa, make the living room warm white."_
+- _"Alexa, set the kitchen to daylight."_
+
+The following table lists the possible friendly name synonyms available to lights that support color temperature.
+
+| Color Temperature in Kelvin | Friendly Name Synonyms |
+| -----| ---------------------------------------------- |
+| 2200 | _"warm"_, _"warm white"_ |
+| 2700 | _"incandescent"_, _"soft white"_ |
+| 4000 | _"white"_ |
+| 5500 | _"daylight"_, _"daylight white"_ |
+| 7000 | _"cool"_, _"cool white"_ |
+
+Use _"warmer"_, _"softer"_, _"cooler_, _"whiter"_ utterances to adjust color temperature by 50 `mired` (approximately 300-500 degree kelvin change).
+
+- _"Alexa, set the dining room softer."_
+- _"Alexa, make the living room warmer."_
+- _"Alexa, set the dining room cooler."_
+- _"Alexa, make the living room light whiter."_
+
+#### Color
+
+Set the light color using the CSS [basic color keywords](https://drafts.csswg.org/css-color-3/#html4) or [extended color keywords](https://drafts.csswg.org/css-color-3/#svg-color) as the friendly color name.
+
+- _"Alexa, set the front porch light to blue."_
+- _"Alexa, set the bedroom light to red."_
+- _"Alexa, change the kitchen to the color crimson."_
### Lock
From c35be8f422a9ae9b249e18ac400ab0957f028a31 Mon Sep 17 00:00:00 2001
From: Paul Sinclair <24625998+sinclairpaul@users.noreply.github.com>
Date: Fri, 13 Mar 2020 08:29:55 -0400
Subject: [PATCH 07/12] =?UTF-8?q?=F0=9F=93=9A=20Remove=20Hass.io=20referen?=
=?UTF-8?q?ces=20(#12348)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
* 📚 Remove Hass.io references
* Update recorder.markdown
* Update recorder.markdown
* Update recorder.markdown
---
source/_integrations/recorder.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown
index 267e54e57c4..8ad38a1688c 100644
--- a/source/_integrations/recorder.markdown
+++ b/source/_integrations/recorder.markdown
@@ -18,7 +18,7 @@ This integration constantly saves data. If you use the default configuration, th
Home Assistant uses [SQLAlchemy](https://www.sqlalchemy.org/), which is an Object Relational Mapper (ORM). This means that you can use **any** SQL backend for the recorder that is supported by SQLAlchemy, like [MySQL](https://www.mysql.com/), [MariaDB](https://mariadb.org/), [PostgreSQL](https://www.postgresql.org/), or [MS SQL Server](https://www.microsoft.com/en-us/sql-server/).
-The default database engine is [SQLite](https://www.sqlite.org/) which doesn't require any configuration. The database is stored in your Home Assistant configuration directory (`.homeassistant` or '/config/' in Hass.io) and called `home-assistant_v2.db`.
+The default database engine is [SQLite](https://www.sqlite.org/) which does not require any configuration. The database is stored in your Home Assistant configuration directory ('/config/') and is named `home-assistant_v2.db`.
To change the defaults for the `recorder` integration in your installation, add the following to your `configuration.yaml` file:
From ea76e1eab1a675facf72ad93337b2a520291f4a4 Mon Sep 17 00:00:00 2001
From: Paul Sinclair <24625998+sinclairpaul@users.noreply.github.com>
Date: Fri, 13 Mar 2020 08:31:22 -0400
Subject: [PATCH 08/12] =?UTF-8?q?=F0=9F=93=9A=20Remove=20Hass.io=20referen?=
=?UTF-8?q?ce=20-=20tradfri=20(#12351)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
source/_integrations/tradfri.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/tradfri.markdown b/source/_integrations/tradfri.markdown
index c4658b64ff3..464ba64bff5 100644
--- a/source/_integrations/tradfri.markdown
+++ b/source/_integrations/tradfri.markdown
@@ -58,7 +58,7 @@ Then restart Home Assistant. When prompted, enter the security key and click *co
### Compilation issues
- This does not apply to Hass.io or Docker.
+ This does not apply to Home Assistant running in Docker Containers, including the default Home Assistant install.
Please make sure you have `autoconf` installed (`$ sudo apt-get install autoconf`) if you want to use this component. Also, installing some dependencies might take considerable time (more than one hour) on slow devices.
From dfdf7fe21f603cf4804662ba03ff1662432ed013 Mon Sep 17 00:00:00 2001
From: Paul Sinclair <24625998+sinclairpaul@users.noreply.github.com>
Date: Fri, 13 Mar 2020 08:32:32 -0400
Subject: [PATCH 09/12] =?UTF-8?q?=F0=9F=93=9A=20Remove=20Hass.io=20referen?=
=?UTF-8?q?ces=20for=20http=20page=20(#12350)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
source/_integrations/http.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/http.markdown b/source/_integrations/http.markdown
index fb15340d193..fae6ab3e9e5 100644
--- a/source/_integrations/http.markdown
+++ b/source/_integrations/http.markdown
@@ -154,7 +154,7 @@ Please note, that sources from `trusted_networks` won't be banned automatically.
## Hosting files
-If you want to use Home Assistant to host or serve static files then create a directory called `www` under the configuration path (`/config` on Hass.io, `.homeassistant` elsewhere). The static files in `www/` can be accessed by the following URL `http://your.domain:8123/local/`, for example `audio.mp3` would be accessed as `http://your.domain:8123/local/audio.mp3`.
+If you want to use Home Assistant to host or serve static files then create a directory called `www` under the configuration path (`/config`). The static files in `www/` can be accessed by the following URL `http://your.domain:8123/local/`, for example `audio.mp3` would be accessed as `http://your.domain:8123/local/audio.mp3`.
From 1544511a7967df7caafc7b55ced22287ad8ed970 Mon Sep 17 00:00:00 2001
From: Jay
Date: Fri, 13 Mar 2020 13:01:44 -0500
Subject: [PATCH 10/12] Cosmetic improvements and correction (#12355)
Per #31713, Hue groups are no longer imported by default. Also made some cosmetic improvements to the documentation.
---
source/_integrations/hue.markdown | 22 ++++++++++------------
1 file changed, 10 insertions(+), 12 deletions(-)
diff --git a/source/_integrations/hue.markdown b/source/_integrations/hue.markdown
index f0d49984b4c..764620f7a22 100644
--- a/source/_integrations/hue.markdown
+++ b/source/_integrations/hue.markdown
@@ -14,20 +14,20 @@ ha_codeowners:
ha_domain: hue
---
-Philips Hue support is integrated into Home Assistant as a hub that can drive the light and sensor platforms. The preferred way to set up the Philips Hue platform is by enabling the [discovery component](/integrations/discovery/).
+The Philips Hue integration allows you to control and monitor the lights and motion sensors connected to your Hue bridge. The preferred way to set up the Philips Hue integration is by enabling [discovery](/integrations/discovery/).
There is currently support for the following device types within Home Assistant:
- Lights
- Motion sensors (including temperature and light level sensors)
-The hub can be set up by navigating to the Configuration tab in the sidebar and selecting Integrations. You will see "Philips Hue" in the discovered section. Click configure and you will be presented with the initiation dialog. This will prompt you to press the Hue button on your bridge to register the hub in Home Assistant. After you click submit, you will have the opportunity to select the area that your bridge is located.
+To set up this integration, click Configuration in the sidebar and then click Integrations. You should see "Philips Hue" in the discovered section (if you do not, click the + icon in the lower right and find Philips Hue). Click configure and you will be presented with the initiation dialog. This will prompt you to press the button on your Hue bridge to register the hub with Home Assistant. After you click submit, you will have the opportunity to select the area that your bridge is located.
When you configure the Hue bridge from Home Assistant, it writes a token to a file in your Home Assistant [configuration directory](/docs/configuration/). That token authenticates the communication with the Hue bridge. This token uses the IP address of the bridge. If the IP address for the bridge changes, you will need to register it with Home Assistant again. To avoid this, you may set up a DHCP reservation on your router for your Hue bridge so that it always has the same IP address.
Once registration is complete you should see the Hue lights listed as `light` entities, the Hue motion sensors listed as `binary_sensor` entities, and the Hue temperature and light level sensors (which are built in to the motion sensors) listed as `sensor` entities. If you don't, you may have to restart Home Assistant once more.
-If you want to enable the integration without relying on the [discovery component](/integrations/discovery/), add the following lines to your `configuration.yaml` file:
+If you want to enable the integration without relying on [discovery](/integrations/discovery/), add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
@@ -50,7 +50,7 @@ allow_hue_groups:
description: Disable this to stop Home Assistant from importing the groups defined on the Hue bridge.
required: false
type: boolean
- default: true
+ default: false
{% endconfiguration %}
## Examples
@@ -92,7 +92,7 @@ To create a `LightGroup` named `Ceiling lights` that contains the lights 1, 2, a
$ curl -XPOST -d '{"name": "Ceiling lights", "lights": ["1", "2", "3"]}' http:///api//groups
```
-The `` is the string that is used to register Home Assistant on the bridge. You can find it in the `core.config_entries` file in your configuration\.storage path. `` is the IP address or hostname of your Hue bridge.
+The `` is the string that is used to register Home Assistant with the bridge. You can find it in the `core.config_entries` file in `/PATH-TO-YOUR-CONFIGURATION/.storage/`. `` is the IP address or hostname of your Hue bridge.
You can find the IDs of your lights by executing the following command:
@@ -110,9 +110,9 @@ More information can be found on the [Philips Hue API documentation](https://www
### Using Hue Scenes in Home Assistant
-The Hue platform has its own concept of scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them—many that you've never used, and almost all very poorly named.
+The Hue platform has its own concept of scenes for setting the colors of a group of lights simultaneously. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them—many that you've never used, and almost all very poorly named.
-To avoid user interface overload, we don't expose scenes directly. Instead there is a hue.hue_activate_scene service which can be used by `automation` or `script` components.
+To avoid user interface overload, we don't expose scenes directly. Instead there is a `hue.hue_activate_scene` service which can be used in an automation or script.
This will have all the bulbs transitioned at once, instead of one at a time like when using standard scenes in Home Assistant.
For instance:
@@ -136,15 +136,13 @@ _Note_: `group_name` is not a reference to a Home Assistant group name. It can o
### Finding Group and Scene Names
-How do you find these names?
+The easiest way to find Hue scene names is to only use the scenes from the 2nd generation Hue app, which are organized by room (group) and scene name. Use the room name and scene name that you see in the app. You can test that these work at Developer Tools > Services in your Home Assistant instance.
-The easiest way to do this is to only use the scenes from the 2nd generation Hue app, which is organized by room (group) and scene name. Use the values of room name and scene name that you see in the app. You can test that these work by using the `dev-service` console of your Home Assistant instance.
-
-Alternatively, you can dump all rooms and scene names using this [gist](https://gist.github.com/sdague/5479b632e0fce931951c0636c39a9578). This does **not** tell you which groups and scenes work together, but it is sufficient to get values that you can test in the `dev-service` console.
+Alternatively, you can dump all rooms and scene names using this [gist](https://gist.github.com/sdague/5479b632e0fce931951c0636c39a9578). This does **not** tell you which groups and scenes work together, but it is sufficient to get values that you can test at Developer Tools > Services.
### Caveats
-The Hue API doesn't activate scenes directly; rather, they must be associated with a Hue group (typically rooms, especially if using the 2nd gen app). But Hue scenes don't actually reference their group. So heuristic matching is used.
+The Hue API doesn't activate scenes directly; rather, they must be associated with a Hue group (typically rooms, especially if using the 2nd generation Hue app). But Hue scenes don't actually reference their group, so heuristic matching is used.
Neither group names nor scene names are guaranteed unique in Hue. If you are observing unexpected behavior from calling Hue scenes in Home Assistant, make the names of your Hue scenes more specific in the Hue app.
From 677123da13a92844ad10f18cbd10d633c13339a5 Mon Sep 17 00:00:00 2001
From: Paul Sinclair <24625998+sinclairpaul@users.noreply.github.com>
Date: Fri, 13 Mar 2020 16:19:56 -0400
Subject: [PATCH 11/12] =?UTF-8?q?=F0=9F=93=9A=20Remove=20Hass.io=20referen?=
=?UTF-8?q?ce=20-=20Deconz=20(#12358)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
source/_integrations/deconz.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/deconz.markdown b/source/_integrations/deconz.markdown
index bc8398dde9a..e35dcbdd4b2 100644
--- a/source/_integrations/deconz.markdown
+++ b/source/_integrations/deconz.markdown
@@ -34,7 +34,7 @@ There is currently support for the following device types within Home Assistant:
## Recommended way of running deCONZ
-If you are running Hass.io, an official add-on for deCONZ is available in the add-on store.
+An official add-on for deCONZ is available in the Home Assistant add-on store.
Otherwise, use [community container](https://hub.docker.com/r/marthoc/deconz/) by Marthoc for your deCONZ needs.
### Supported devices
From 4d0b3e3d558922e064dc738512a3a4ca0ef8f0ca Mon Sep 17 00:00:00 2001
From: Paul Sinclair <24625998+sinclairpaul@users.noreply.github.com>
Date: Fri, 13 Mar 2020 16:21:18 -0400
Subject: [PATCH 12/12] =?UTF-8?q?=F0=9F=93=9A=20Remove=20Hass.io=20Referen?=
=?UTF-8?q?ce=20-=20Glossary=20(#12356)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
source/_data/glossary.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_data/glossary.yml b/source/_data/glossary.yml
index b0388379976..9bb3f81f014 100644
--- a/source/_data/glossary.yml
+++ b/source/_data/glossary.yml
@@ -1,7 +1,7 @@
- topic: Action
description: "An [Action](/docs/automation/action/) is an event that can be fired as a response to a trigger, once all conditions have been met."
- topic: Add-on
- description: "Hass.io add-ons provide additional, standalone, applications that can run beside Home Assistant on a Hass.io installation. Most of these, add-on provided, applications can be integrated into Home Assistant using integrations. Examples of add-ons are: an MQTT broker, database service or a file server."
+ description: "Add-ons provide additional, standalone, applications that can run beside Home Assistant. Most of these, add-on provided, applications can be integrated into Home Assistant using integrations. Examples of add-ons are: an MQTT broker, database service or a file server."
- topic: Automation
description: "[Automations](/docs/automation/) offer the capability to call a service based on a simple or complex trigger. Automation allows a condition such as a sunset to cause an event, such as a light turning on."
- topic: Binary sensor
