mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-25 02:07:15 +00:00
Merge branch 'current' into next
This commit is contained in:
Fabian Affolter
commit
665db64fe7
2
.github/PULL_REQUEST_TEMPLATE.md
vendored
2
.github/PULL_REQUEST_TEMPLATE.md
vendored
@ -5,7 +5,7 @@
|
||||
|
||||
## Checklist:
|
||||
|
||||
- [ ] Branch: Fixes, changes and adjustments should be created against `current`. New documentation for platforms/components and features should go to `next`.
|
||||
- [ ] Branch: `next` is for changes and new documentation that will go public with the next [home-assistant](https://github.com/home-assistant/home-assistant) release. Fixes, changes and adjustments for the current release should be created against `current`.
|
||||
- [ ] The documentation follow the [standards][standards].
|
||||
|
||||
[standards]: https://home-assistant.io/developers/documentation/standards/
|
||||
|
||||
@ -142,13 +142,13 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 77
|
||||
current_patch_version: 2
|
||||
date_released: 2018-08-31
|
||||
current_patch_version: 3
|
||||
date_released: 2018-09-03
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
# Major release:
|
||||
patch_version_notes: "#release-0772---august-31"
|
||||
patch_version_notes: "#release-0773---september-3"
|
||||
# Minor release (Example #release-0431---april-25):
|
||||
|
||||
# Date we moved to Discourse for comments
|
||||
|
||||
@ -89,10 +89,11 @@ See the following links for more information:
|
||||
|
||||
Add the following configuration to enable ACLs:
|
||||
|
||||
1. Set `customize` flag to `true` in your configuration.
|
||||
1. Set the `active` flag within the `customize` section to `true` in your configuration.
|
||||
2. Create a file in `/share/mosquitto` named `acl.conf` with the following contents:
|
||||
|
||||
```text
|
||||
acl_file /share/mosquitto/accesscontrollist
|
||||
```
|
||||
3. Create a file in `/share/mosquitto` named `accesscontrollist` and add contents according to your requirements.
|
||||
|
||||
The `/share` folder can be found on the host filesystem under `/usr/share/hassio/share`, or via the `Share` folder through SMB (Samba).
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: apcupsd.png
|
||||
ha_category: Hub
|
||||
ha_category: System Monitor
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: apple.png
|
||||
ha_category: Hub
|
||||
ha_category: Multimedia
|
||||
ha_iot_class: "Local Push"
|
||||
ha_release: 0.49
|
||||
---
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: august.png
|
||||
ha_category: Door bell
|
||||
ha_category: Doorbell
|
||||
ha_release: "0.64"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: axis.png
|
||||
ha_category: Hub
|
||||
ha_category: Camera
|
||||
ha_release: "0.45"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
@ -17,6 +17,8 @@ ha_iot_class: "Local Polling"
|
||||
|
||||
Home Assistant will automatically discover their presence on your network.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
You can also manually configure your devices by adding the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
@ -28,8 +30,6 @@ axis:
|
||||
- camera
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
## {% linkable_title Configuration variables %}
|
||||
|
||||
- **device** (*Required*): Unique name
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: august.png
|
||||
ha_category: Door bell
|
||||
ha_category: Doorbell
|
||||
ha_release: "0.64"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
@ -20,3 +20,4 @@ If you have August Doorbell, once you have enabled the [August component](/compo
|
||||
* Doorbell ding sensor
|
||||
* Doorbell motion sensor
|
||||
* Doorbell online sensor
|
||||
|
||||
|
||||
0
source/_components/binary_sensor.bmw_connected_drive.markdown
Executable file → Normal file
0
source/_components/binary_sensor.bmw_connected_drive.markdown
Executable file → Normal file
@ -15,6 +15,8 @@ ha_iot_class: Cloud Polling
|
||||
|
||||
The `upcloud` binary sensor platform allows you to monitor your UpCloud servers.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your UpCloud servers, you first have to set up your [UpCloud hub](/components/upcloud/) and then add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -8,15 +8,19 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: bloomsky.png
|
||||
ha_category: Hub
|
||||
ha_category: Environment
|
||||
ha_release: 0.14
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `bloomsky` component allows you to access your [BloomSky](https://www.bloomsky.com/) weather station's [sensors](/components/sensor.bloomsky), [binary sensors](/components/binary_sensor.bloomsky), and [camera](/components/camera.bloomsky) from Home Assistant.
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
Obtain your API key from your [BloomSky dashboard](https://dashboard.bloomsky.com). Click `developers` in the bottom left of the screen.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To integrate your BloomSky hub with Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
@ -25,6 +29,9 @@ bloomsky:
|
||||
api_key: YOUR_API_KEY
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **api_key** (*Required*): Your BloomSky API key.
|
||||
{% configuration %}
|
||||
api_key:
|
||||
description: Your BloomSky API key.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -16,6 +16,8 @@ ha_iot_class: "Local Polling"
|
||||
|
||||
The `bloomsky` camera component allows you to view the current photo created by the camera in the [BloomSky](https://www.bloomsky.com) weather station. This can work in concert with [BloomSky sensors](/components/sensor.bloomsky).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable this camera in your installation, set up the [BloomSky component](/components/bloomsky) with your API key and add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -23,11 +23,7 @@ The `daikin` climate platform integrates Daikin air conditioning systems into Ho
|
||||
|
||||
Current temperature is displayed.
|
||||
|
||||
<p class='note warning'>
|
||||
Please note, the `daikin` platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant. BRP069A42 does not support setting of fan speed or fan swing mode.
|
||||
</p>
|
||||
|
||||
The platform has been integrated with discovery so all your Daikin AC's climate devices can be automatically discovered.
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable the platform, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
|
||||
0
source/_components/cover.mqtt.markdown
Executable file → Normal file
0
source/_components/cover.mqtt.markdown
Executable file → Normal file
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: daikin.png
|
||||
ha_category: Hub
|
||||
ha_category: Climate
|
||||
ha_release: 0.59
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
@ -16,11 +16,15 @@ ha_iot_class: "Local Polling"
|
||||
|
||||
The `daikin` component integrates Daikin air conditioning systems into Home Assistant.
|
||||
|
||||
To automatically add all your Daikin devices (ACs and associated sensors) into your Home Assistant installation, add the following to your 'configuration.yaml' file:
|
||||
## {% linkable_title Supported hardware %}
|
||||
|
||||
<p class='note warning'>
|
||||
Please note, the Daikin platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant.
|
||||
</p>
|
||||
**Only** the european versions of Daikin ACs (models BRP069A41, 42, 43, 45).
|
||||
|
||||
The model BRP069A42 does not support setting of fan speed or fan swing mode.
|
||||
|
||||
Please note that some AC devices may report outside temperature only when they are turned on.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To automatically add all your Daikin devices (ACs and associated sensors) into your Home Assistant installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -52,7 +56,3 @@ monitored_conditions:
|
||||
description: The current temperature measured outside the house.
|
||||
{% endconfiguration %}
|
||||
|
||||
<p class='note warning'>
|
||||
Please note that some AC devices may report outside temperature only when they are turned on.
|
||||
</p>
|
||||
|
||||
|
||||
@ -16,11 +16,11 @@ ha_iot_class: "Local Polling"
|
||||
|
||||
The `digital_ocean` component allows you to access the information about your [Digital Ocean](https://www.digitalocean.com/) droplets from Home Assistant.
|
||||
|
||||
### {% linkable_title Setup %}
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
Obtain your API key from your [Digital Ocean dashboard](https://cloud.digitalocean.com/settings/api/tokens).
|
||||
|
||||
### {% linkable_title Configuration %}
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To integrate your Digital Ocean droplets with Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -8,13 +8,15 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: doorbird.png
|
||||
ha_category: Hub
|
||||
ha_category: Doorbell
|
||||
ha_release: "0.54"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `doorbird` implementation allows you to integrate your [DoorBird](http://www.doorbird.com/) device in Home Assistant.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To connect your device, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
@ -94,4 +96,4 @@ Enabling any monitored condition will delete all registered notification service
|
||||
action:
|
||||
service: light.turn_on
|
||||
entity_id: light.side_entry_porch
|
||||
```
|
||||
```
|
||||
|
||||
@ -38,17 +38,21 @@ eufy:
|
||||
name: Smart Switch
|
||||
```
|
||||
|
||||
access_token can be obtained by running:
|
||||
`access_token can be obtained by running:
|
||||
|
||||
```
|
||||
curl -H "Content-Type: application/json" -d '{"client_id":"eufyhome-app", "client_Secret":"GQCpr9dSp3uQpsOMgJ4xQ", "email":"USERNAME", "password":"PASSWORD"}' https://home-api.eufylife.com/v1/user/email/login | jq
|
||||
```bash
|
||||
$ curl -H "Content-Type: application/json" \
|
||||
-d '{"client_id":"eufyhome-app", "client_Secret":"GQCpr9dSp3uQpsOMgJ4xQ", "email":"USERNAME", "password":"PASSWORD"}' \
|
||||
https://home-api.eufylife.com/v1/user/email/login \
|
||||
| jq
|
||||
```
|
||||
|
||||
replacing USERNAME and PASSWORD with the Eufy username and password. This will give an access_token. Then run:
|
||||
replacing USERNAME and PASSWORD with the Eufy username and password. This will give an `access_token`. Then run:
|
||||
|
||||
```
|
||||
curl -H token:TOKEN -H category:Home https://home-api.eufylife.com/v1/device/list/devices-and-groups | jq
|
||||
```bash
|
||||
$ curl -H token:TOKEN -H category:Home \
|
||||
https://home-api.eufylife.com/v1/device/list/devices-and-groups | jq
|
||||
```
|
||||
|
||||
replacing TOKEN with the access_token from the previous command. This will provide the local_code for each device.
|
||||
replacing TOKEN with the `access_token` from the previous command. This will provide the local_code for each device.
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- [Notify](/components/notify.knx)
|
||||
- [Scene](/components/scene.knx)
|
||||
|
||||
### {% linkable_title Configuration %}
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your KNX in your installation, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
@ -77,8 +77,8 @@ knx:
|
||||
|
||||
```yaml
|
||||
knx:
|
||||
fire_event: True
|
||||
fire_event_filter: ["1/0/*", "6/2,3,4-6/*"]
|
||||
fire_event: True
|
||||
fire_event_filter: ["1/0/*", "6/2,3,4-6/*"]
|
||||
```
|
||||
|
||||
- **fire_event** (*Optional*): If set to True, platform will write all received KNX messages to event bus
|
||||
@ -105,21 +105,20 @@ KNX component is able to expose time or sensor values to KNX bus. The component
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
knx:
|
||||
expose:
|
||||
- type: 'temperature'
|
||||
entity_id: 'sensor.owm_temperature'
|
||||
address: '0/0/2'
|
||||
- type: 'time'
|
||||
address: '0/0/1'
|
||||
- type: 'datetime'
|
||||
address: '0/0/23'
|
||||
expose:
|
||||
- type: 'temperature'
|
||||
entity_id: 'sensor.owm_temperature'
|
||||
address: '0/0/2'
|
||||
- type: 'time'
|
||||
address: '0/0/1'
|
||||
- type: 'datetime'
|
||||
address: '0/0/23'
|
||||
```
|
||||
|
||||
* **type**: Type of the exposed value. Either time or datetime or any supported type of [KNX Sensor](/components/sensor.knx/) (e.g., "temperature" or "humidity").
|
||||
* **entity_id**: Entity id of the HASS component to be exposed. Not necessary for types time and datetime.
|
||||
* **address**: KNX group address.
|
||||
|
||||
|
||||
### {% linkable_title Known issues %}
|
||||
|
||||
Due to lame multicast support the routing abstraction and the gateway scanner only work with Python >=3.5.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Blinkstick"
|
||||
title: "Blinkstick Light"
|
||||
description: "Instructions on how to setup Blinkstick lights within Home Assistant."
|
||||
date: 2015-10-08 10:00
|
||||
sidebar: true
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Blinkt!"
|
||||
title: "Blinkt! Light"
|
||||
description: "Instructions on how to setup Blinkt! RGB LED lights within Home Assistant."
|
||||
date: 2017-04-30 9:00
|
||||
sidebar: true
|
||||
|
||||
@ -18,6 +18,8 @@ The `knx` light component is used as in interface to switching/light actuators.
|
||||
|
||||
The `knx` component must be configured correctly, see [KNX Component](/components/knx).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your KNX light in your installation, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
@ -31,12 +33,14 @@ light:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **address** (*Required*): KNX group address for switching the light on and off.
|
||||
- **name** (*Optional*): A name for this device used within Home Assistant.
|
||||
- **address**: KNX group address for switching the light on and off.
|
||||
- **brightness_address** (Optional): KNX group address for dimming light.
|
||||
- **state_address** (*Optional*): separate KNX group address for retrieving the switch state of the light.
|
||||
- **brightness_state_address** (*Optional*): separate KNX group address for retrieving the dimmed state of the light.
|
||||
- **color_address** (*Optional*): separate KNX group address for setting the color of the light.
|
||||
- **color_state_address** (*Optional*): separate KNX group address for retrieving the color of the light.
|
||||
|
||||
Some KNX devices can change their state internally without any messages on the KNX bus, e.g., if you configure a timer on a channel. The optional `state_address` can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given state address, this will overwrite the state of the switch object.
|
||||
For switching/light actuators that are only controlled by a single group address and can't change their state internally, you don't have to configure the state address.
|
||||
|
||||
|
||||
0
source/_components/light.template.markdown
Executable file → Normal file
0
source/_components/light.template.markdown
Executable file → Normal file
0
source/_components/lock.bmw_connected_drive.markdown
Executable file → Normal file
0
source/_components/lock.bmw_connected_drive.markdown
Executable file → Normal file
0
source/_components/map.markdown
Executable file → Normal file
0
source/_components/map.markdown
Executable file → Normal file
@ -8,14 +8,18 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: microsoft.png
|
||||
ha_category: Hub
|
||||
ha_category: Image Processing
|
||||
ha_release: "0.37"
|
||||
---
|
||||
|
||||
The `microsoft_face` component platform is the main component for Microsoft Azure Cognitive service [Face](https://www.microsoft.com/cognitive-services/en-us/face-api). All data are stored in your own private instance in the Azure cloud.
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
You need an API key, which is free, but requires an [Azure registration](https://azure.microsoft.com/de-de/free/) using your Microsoft ID. The free resource (*F0*) is limited to 20 requests per minute and 30k requests in a month. If you don't want to use the Azure cloud, you can also get an API key by registering with [cognitive-services](https://www.microsoft.com/cognitive-services/en-us/subscriptions). Please note that all keys on cognitive services must be recreated every 90 days.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable the Microsoft Face component, add the following to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -17,6 +17,8 @@ The `knx` notify platform allows you to send notifications to [KNX](http://www.k
|
||||
|
||||
The `knx` component must be configured correctly, see [KNX Component](/components/knx).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your KNX switch in your installation, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
@ -26,5 +28,8 @@ notify:
|
||||
address: '5/1/10'
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
* **address** (*Required*): KNX group address of the notification.
|
||||
* **name** (*Optional*): A name for this device used within Home Assistant.
|
||||
* **address**: KNX group address of the notification
|
||||
|
||||
|
||||
@ -8,12 +8,14 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Other
|
||||
ha_category: Environment
|
||||
ha_release: 0.44
|
||||
---
|
||||
|
||||
This`plant`component lets you merge moisture, conductivity, light intensity, temperature and battery level for a plant into a single UI element. It also supports setting minimum and maximum values for each measurement and will change its state to "problem" if it is not within those limits.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your `plant` sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
0
source/_components/remote.harmony.markdown
Executable file → Normal file
0
source/_components/remote.harmony.markdown
Executable file → Normal file
0
source/_components/remote.itach.markdown
Executable file → Normal file
0
source/_components/remote.itach.markdown
Executable file → Normal file
0
source/_components/remote.markdown
Executable file → Normal file
0
source/_components/remote.markdown
Executable file → Normal file
@ -16,6 +16,10 @@ The `knx` scenes platform allows you to trigger [KNX](http://www.knx.org) scenes
|
||||
|
||||
The `knx` component must be configured correctly, see [KNX Component](/components/knx).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your KNX scence in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
scene:
|
||||
@ -27,8 +31,7 @@ scene:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **address** (*Required*): KNX group address of the binary sensor.
|
||||
- **scene_number** (*Required*): KNX scene number to be activated.
|
||||
- **name** (*Optional*): A name for this device used within Home Assistant.
|
||||
- **address**: KNX group address of the binary sensor.
|
||||
- **scene_number** KNX scene number to be activated.
|
||||
|
||||
|
||||
|
||||
@ -16,6 +16,8 @@ ha_iot_class: "Cloud Polling"
|
||||
|
||||
The `bloomsky` sensor component allows you to view the measurements made by sensors in the [BloomSky](https://www.bloomsky.com) weather station. This can work in concert with the [BloomSky camera](/components/camera.bloomsky).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable these sensors in your installation, set up the [BloomSky component](/components/bloomsky) with your API key add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -8,13 +8,15 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: System Monitor
|
||||
ha_category: Network
|
||||
ha_release: 0.44
|
||||
ha_iot_class: "depends"
|
||||
---
|
||||
|
||||
The `cert_expiry` sensor fetches information from a configured URL and displays the certificate expiry in days.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To add the Certificate Expiry sensor to your installation, add these options to `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -16,12 +16,8 @@ ha_iot_class: "Local Polling"
|
||||
|
||||
The `daikin` sensor platform integrates Daikin air conditioning systems into Home Assistant, enabling displaying the following parameters:
|
||||
|
||||
- **inside temperature**
|
||||
- **outside temperature**
|
||||
|
||||
<p class='note warning'>
|
||||
Please note, the `daikin` platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant.
|
||||
</p>
|
||||
- Inside temperature
|
||||
- Outside temperature
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
@ -54,6 +50,3 @@ monitored_conditions:
|
||||
description: The current temperature measured outside the house.
|
||||
{% endconfiguration %}
|
||||
|
||||
<p class='note warning'>
|
||||
Please note that some AC devices may report outside temperature only when they are turned on.
|
||||
</p>
|
||||
|
||||
@ -17,8 +17,26 @@ The `knx` sensor platform allows you to monitor [KNX](http://www.knx.org) sensor
|
||||
|
||||
The `knx` component must be configured correctly, see [KNX Component](/components/knx).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your KNX sensor in your installation, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: knx
|
||||
name: Heating.Valve1
|
||||
address: '2/0/0'
|
||||
```
|
||||
|
||||
|
||||
|
||||
- **address** (*Required*): KNX group address of the sensor.
|
||||
- **name** (*Optional*): A name for this device used within Home Assistant.
|
||||
- **type** (*Optional*): "percent", "temperature", "humidity", "illuminance", "brightness", "speed_ms", "current", "power", "electric_current", "electric_potential", "energy", "frequency", "heatflowrate", "phaseanglerad", "phaseangledeg", "powerfactor" or "speed".
|
||||
|
||||
## {% linkable_title Full example %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
@ -31,8 +49,3 @@ sensor:
|
||||
address: '6/2/1'
|
||||
type: 'temperature'
|
||||
```
|
||||
|
||||
- **name** (*Optional*): A name for this device used within Home Assistant.
|
||||
- **address**: KNX group address of the sensor.
|
||||
- **type** (Optional): "percent", "temperature", "humidity", "illuminance", "brightness", "speed_ms", "current", "power", "electric_current", "electric_potential", "energy", "frequency", "heatflowrate", "phaseanglerad", "phaseangledeg", "powerfactor" or "speed".
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: miflora.png
|
||||
ha_category: DIY
|
||||
ha_category: Environment
|
||||
ha_release: 0.29
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Climate
|
||||
ha_category: Environment
|
||||
ha_release: '0.20'
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: swiss-hydrological-data.png
|
||||
ha_category: Weather
|
||||
ha_category: Environment
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_release: 0.22
|
||||
---
|
||||
@ -19,33 +19,49 @@ ha_release: 0.22
|
||||
|
||||
The `swiss_hydrological_data` sensor will show you details (temperature, level, and discharge) of rivers and lakes in Switzerland.
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
The [station overview](http://www.hydrodaten.admin.ch/en/danger-levels-table.html) contains a list of all available measuring points and will help to determine the ID of station which is needed for the configuration.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: swiss_hydrological_data
|
||||
station: STATION_ID
|
||||
- platform: swiss_hydrological_data
|
||||
station: STATION_ID
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **name** (*Optional*): Name to use in the frontend.
|
||||
- **station** (*Required*): The ID of the measurement point.
|
||||
{% configuration %}
|
||||
station:
|
||||
description: The ID of the measurement point.
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: Name to use in the frontend.
|
||||
required: false
|
||||
type: string
|
||||
default:
|
||||
{% endconfiguration %}
|
||||
|
||||
The hydrological measurings are coming from the [Swiss Federal Office for the Environment (Bundesamt für Umwelt - Abt. Hydrologie)](http://www.hydrodaten.admin.ch) and are updated almost in real-time.
|
||||
|
||||
## {% linkable_title Example %}
|
||||
|
||||
This sensor contains additional information which an easily accessed by a [template sensor](/components/sensor.template/).
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: template
|
||||
sensors:
|
||||
discharge:
|
||||
value_template: '{% raw %}{{ states.sensor.aare.attributes.Discharge }}{% endraw %}'
|
||||
value_template: '{{ states.sensor.aare.attributes.Discharge }}'
|
||||
friendly_name: 'Discharge'
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: samsung.png
|
||||
ha_category: Sensor
|
||||
ha_category: System Monitor
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.66
|
||||
---
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: page
|
||||
title: "IKEA Trådfri sensor"
|
||||
title: "IKEA Trådfri Sensor"
|
||||
description: "Access and control your ZigBee-based IKEA Trådfri (Tradfri) Sensors."
|
||||
date: 2017-04-12 22.04
|
||||
sidebar: true
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: upnp.png
|
||||
ha_category: "Other"
|
||||
ha_category: Network
|
||||
ha_release: 0.48
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: acer.png
|
||||
ha_category: Switch
|
||||
ha_category: Multimedia
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.19
|
||||
---
|
||||
@ -16,6 +16,8 @@ ha_release: 0.19
|
||||
|
||||
The `acer_projector` switch platform allows you to control the state of RS232 connected projectors from [Acer](http://www.acer.com).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your Acer Projector in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
0
source/_components/switch.digitalloggers.markdown
Executable file → Normal file
0
source/_components/switch.digitalloggers.markdown
Executable file → Normal file
@ -18,6 +18,8 @@ The `knx` switch component is used as in interface to switching actuators.
|
||||
|
||||
The `knx` component must be configured correctly, see [KNX Component](/components/knx).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your KNX switch in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
@ -26,12 +28,13 @@ switch:
|
||||
name: Kitchen.Coffee
|
||||
address: '1/1/6'
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
* **address** (*Required*): KNX group address for switching the switch on/off.
|
||||
* **name** (*Optional*): A name for this device used within Home Assistant.
|
||||
* **address**: KNX group address for switching the switch on/off
|
||||
* **state_address**: (*Optional*) separate KNX group address for retrieving the switch state.
|
||||
* **state_address** (*Optional*): separate KNX group address for retrieving the switch state.
|
||||
|
||||
Some KNX devices can change their state internally without any messages on the KNX bus, e.g., if you configure a timer on a channel. The optional `state_address` can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given state address, this will overwrite the state of the switch object.
|
||||
For switching actuators that are only controlled by a single group address and can't change their state internally, you don't have to configure the state address.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,13 +8,15 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: upcloud.png
|
||||
ha_category: Switch
|
||||
ha_category: System Monitor
|
||||
ha_release: 0.65
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `upcloud` switch platform allows you to control (start/stop) your UpCloud servers.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your UpCloud servers, you first have to set up your [UpCloud hub](/components/upcloud/) and then add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: ethernet.png
|
||||
ha_category: Switch
|
||||
ha_category: Network
|
||||
ha_release: 0.16
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
@ -7,7 +7,7 @@ sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Hub
|
||||
ha_category: System Monitor
|
||||
ha_release: 0.65
|
||||
logo: upcloud.png
|
||||
ha_iot_class: Cloud Polling
|
||||
@ -16,8 +16,12 @@ ha_iot_class: Cloud Polling
|
||||
|
||||
The `upcloud` component allows you to access the information about your [UpCloud](https://www.upcloud.com/) servers from Home Assistant.
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
Set up your API user credentials in your [UpCloud control panel](https://my.upcloud.com/).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To integrate your UpCloud servers with Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -8,13 +8,13 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: upnp.png
|
||||
ha_category: "Other"
|
||||
ha_category: Network
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
The `upnp` component enables you to collect network statistics from your router such as bytes in/out and packets in/out. This information is provided by the Internet Gateway Device (IGD) Protocol if enabled on your router.
|
||||
|
||||
The IGD automatically creates port forwarding mappings on your router for Home Assistant, exposing your installation to the internet. The mapping will never automatically expire. Upon stopping Home Assistant, the mapping will be removed from your router.
|
||||
The IGD automatically creates port forwarding mappings on your router for Home Assistant, exposing your installation to the internet. The mapping will never automatically expire. Upon stopping Home Assistant, the mapping will be removed from your router.
|
||||
|
||||
Please note that UPnP or NAT-PMP needs to be enabled on your router for this component to work.
|
||||
|
||||
|
||||
@ -48,7 +48,7 @@ Configuration variables:
|
||||
|
||||
## {% linkable_title Platform Services %}
|
||||
|
||||
In addition to all of the services provided by the `vacuum` component (`start`, `pause`, `stop`, `return_to_home`, `locate`, `set_fan_speed` and `send_command`), the `xiaomi` platform introduces specific services to access the remote control mode of the robot. These are:
|
||||
In addition to all of the services provided by the `vacuum` component (`start`, `pause`, `stop`, `return_to_base`, `locate`, `set_fan_speed` and `send_command`), the `xiaomi` platform introduces specific services to access the remote control mode of the robot. These are:
|
||||
|
||||
- `xiaomi_remote_control_start`
|
||||
- `xiaomi_remote_control_stop`
|
||||
|
||||
@ -8,13 +8,15 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: ethernet.png
|
||||
ha_category: Utility
|
||||
ha_category: Network
|
||||
ha_release: "0.49"
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `wake_on_lan` component enables the ability to send _magic packets_ to [Wake on LAN](https://en.wikipedia.org/wiki/Wake-on-LAN) capable devices, to turn them on.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use this component in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: avahi.png
|
||||
ha_category: "Other"
|
||||
ha_category: Network
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ To make the transition from API password to authentication system easier, we've
|
||||
## {% linkable_title Configuring auth providers %}
|
||||
|
||||
<p class='note warning'>
|
||||
By configuring your own instead of using the default configuration, you take full responsibility for the authentication of the system.
|
||||
Home Assistant automatically configures the standard auth providers and you **do not** need to specify `auth_providers` in your `configuration.yaml` file. Specifying `auth_providers` in your configuration will disable all auth providers that are not listed and can reduce your security or create difficulties logging in.
|
||||
</p>
|
||||
|
||||
Authentication providers are configured in your `configuration.yaml` under the `homeassistant:` block:
|
||||
|
||||
@ -78,7 +78,7 @@ ExecStopPost=/usr/bin/docker rm -f home-assistant-%i
|
||||
WantedBy=multi-user.target
|
||||
```
|
||||
|
||||
### Next Steps
|
||||
### {% linkable_title Next Steps %}
|
||||
|
||||
You need to reload `systemd` to make the daemon aware of the new configuration.
|
||||
|
||||
|
||||
@ -10,8 +10,86 @@ footer: true
|
||||
redirect_from: /getting-started/customizing-devices/
|
||||
---
|
||||
|
||||
## {% linkable_title Changing the entity_id %}
|
||||
|
||||
You can use the UI to change the `entity_id` and friendly name of supported entities. To do this:
|
||||
|
||||
1. Select the entity, either from or from the frontend, or by clicking <img src='/images/frontend/entity_box.png' /> next to the entity in the dev-states menu
|
||||
2. Click on the cog in the right corner of the entity's dialog
|
||||
3. Enter the new name or the new entity ID (remember not to change the domain of the entity - the part before the `.`)
|
||||
4. Select *Save*
|
||||
|
||||
## {% linkable_title Customizing entities %}
|
||||
|
||||
By default, all of your devices will be visible and have a default icon determined by their domain. You can customize the look and feel of your front page by altering some of these parameters. This can be done by overriding attributes of specific entities.
|
||||
|
||||
### {% linkable_title Customization using the UI %}
|
||||
|
||||
Under the *Configuration* menu you'll find the *Customization* menu. When you select an entity to customize, you'll see all the existing attributes listed and you can customize those, or select an additional supported attribute ([see below](/docs/configuration/customizing-devices/#possible-values)).
|
||||
|
||||
#### {% linkable_title Possible values %}
|
||||
|
||||
{% configuration customize %}
|
||||
friendly_name:
|
||||
description: Name of the entity as displayed in the UI.
|
||||
required: false
|
||||
type: string
|
||||
homebridge_name:
|
||||
description: Name of the entity in `HomeBridge`.
|
||||
required: false
|
||||
type: string
|
||||
hidden:
|
||||
description: Set to `true` to hide the entity.
|
||||
required: false
|
||||
type: boolean
|
||||
default: False
|
||||
homebridge_hidden:
|
||||
description: Set to `true` to hide the entity from `HomeBridge`.
|
||||
required: false
|
||||
type: boolean
|
||||
default: False
|
||||
emulated_hue_hidden:
|
||||
description: Set to `true` to hide the entity from `emulated_hue` (this will be deprecated in the near future and should be configured in [`emulated_hue`](/components/emulated_hue)).
|
||||
required: false
|
||||
type: boolean
|
||||
default: False
|
||||
entity_picture:
|
||||
description: URL to use as picture for entity.
|
||||
required: false
|
||||
type: string
|
||||
icon:
|
||||
description: Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com) ([Cheatsheet](https://materialdesignicons.com/cheatsheet)). Prefix name with `mdi:`, ie `mdi:home`.
|
||||
required: false
|
||||
type: string
|
||||
assumed_state:
|
||||
description: For switches with an assumed state two buttons are shown (turn off, turn on) instead of a switch. By setting `assumed_state` to `false` you will get the default switch icon.
|
||||
required: false
|
||||
type: boolean
|
||||
default: True
|
||||
device_class:
|
||||
description: Sets the class of the device, changing the device state and icon that is displayed on the UI (see below).
|
||||
required: false
|
||||
type: boolean
|
||||
initial_state:
|
||||
description: Sets the initial state for automations, `on` or `off`.
|
||||
required: false
|
||||
type: string
|
||||
unit_of_measurement:
|
||||
description: Defines the units of measurement, if any.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
#### {% linkable_title Device Class %}
|
||||
|
||||
Device class is currently supported by the following components:
|
||||
|
||||
* [Binary Sensor](/components/binary_sensor/)
|
||||
* [Sensor](/components/sensor/)
|
||||
* [Cover](/components/cover/)
|
||||
|
||||
### {% linkable_title Manual customization %}
|
||||
|
||||
<p class='note'>
|
||||
If you implement `customize`, `customize_domain`, or `customize_glob` you must make sure it is done inside of `homeassistant:` or it will fail.
|
||||
</p>
|
||||
@ -53,30 +131,6 @@ homeassistant:
|
||||
homebridge_hidden: true
|
||||
```
|
||||
|
||||
### {% linkable_title Possible values %}
|
||||
|
||||
| Attribute | Description |
|
||||
| --------- | ----------- |
|
||||
| `friendly_name` | Name of the entity.
|
||||
| `homebridge_name` | Name of the entity in `HomeBridge`.
|
||||
| `hidden` | Set to `true` to hide the entity.
|
||||
| `homebridge_hidden` | Set to `true` to hide the entity from `HomeBridge`.
|
||||
| `emulated_hue_hidden` | Set to `true` to hide the entity from `emulated_hue` (this will be deprecated in the near future and should be configured in [`emulated_hue`](/components/emulated_hue)).
|
||||
| `entity_picture` | Url to use as picture for entity.
|
||||
| `icon` | Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com) ([Cheatsheet](https://materialdesignicons.com/cheatsheet)). Prefix name with `mdi:`, ie `mdi:home`.
|
||||
| `assumed_state` | For switches with an assumed state two buttons are shown (turn off, turn on) instead of a switch. By setting `assumed_state` to `false` you will get the default switch icon.
|
||||
| `device_class` | Sets the class of the device, changing the device state and icon that is displayed on the UI (see below).
|
||||
| `initial_state` | Sets the initial state for automations. `on` or `off`.
|
||||
| `unit_of_measurement` | Defines the units of measurement, if any.
|
||||
|
||||
### {% linkable_title Device Class %}
|
||||
|
||||
Device class is currently supported by the following components:
|
||||
|
||||
* [Binary Sensor](/components/binary_sensor/)
|
||||
* [Sensor](/components/sensor/)
|
||||
* [Cover](/components/cover/)
|
||||
|
||||
### {% linkable_title Reloading customize %}
|
||||
|
||||
Home Assistant offers a service to reload the core configuration while Home Assistant is running called `homeassistant.reload_core_config`. This allows you to change your customize section and see it being applied without having to restart Home Assistant. To call this service, go to the <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> service developer tools, select the service `homeassistant.reload_core_config` and click "CALL SERVICE".
|
||||
@ -84,4 +138,3 @@ Home Assistant offers a service to reload the core configuration while Home Assi
|
||||
<p class='note warning'>
|
||||
New customize information will be applied the next time the state of the entity gets updated.
|
||||
</p>
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ One major advantage of Home Assistant is that it's not dependent on cloud servic
|
||||
|
||||
### {% linkable_title Checklist %}
|
||||
|
||||
- [Protect your web interface with a password](/getting-started/basic/#password-protecting-the-web-interface)
|
||||
- [Choose a strong password](/docs/authentication/).
|
||||
- Secure your host. Sources could be [Red Hat Enterprise Linux 7 Security Guide](https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/Security_Guide/Red_Hat_Enterprise_Linux-7-Security_Guide-en-US.pdf), [CIS Red Hat Enterprise Linux 7 Benchmark](https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.0.0.pdf), or the [Securing Debian Manual](https://www.debian.org/doc/manuals/securing-debian-howto/index.en.html).
|
||||
- Restrict network access to your devices. Set `PermitRootLogin no` in your sshd config (usually `/etc/ssh/sshd_config`) and to use SSH keys for authentication instead of passwords.
|
||||
- Don't run Home Assistant as root – consider the Principle of Least Privilege.
|
||||
|
||||
@ -10,6 +10,10 @@ footer: true
|
||||
redirect_from: /getting-started/installation-python/
|
||||
---
|
||||
|
||||
<p class='note'>
|
||||
If you're running a Linux-based platform, we strongly recommend you follow the instructions for a [virtual environment](/docs/installation/virtualenv/) instead. If you're running on Windows then [see here](/docs/installation/windows/#installing-in-a-python-virtual-environment) instead.
|
||||
</p>
|
||||
|
||||
Once Python is installed, execute the following code in a console:
|
||||
|
||||
```bash
|
||||
@ -22,12 +26,10 @@ Running these commands will:
|
||||
- Install Home Assistant
|
||||
- Launch Home Assistant and serve the web interface on [http://localhost:8123](http://localhost:8123)
|
||||
|
||||
If you're running a Linux-based platform, we suggest you follow the instructions for a [virtual environment](/docs/installation/virtualenv/) to avoid using `root`.
|
||||
|
||||
Video tutorials of this process for various operating systems are available here:
|
||||
|
||||
- [Windows 10](https://www.youtube.com/watch?v=X27eVvuqwnY)
|
||||
- [macOS](https://www.youtube.com/watch?v=hej6ipN86ls)
|
||||
- [Ubuntu 14.04](https://www.youtube.com/watch?v=SXaAG1lGNH0)
|
||||
|
||||
Keep in mind that the used operating systems and the shown software releases may be outdated.
|
||||
Keep in mind that the operating systems used and the software releases shown may be outdated.
|
||||
|
||||
@ -24,6 +24,7 @@ You need to have a [supported Z-Wave USB stick or module](https://github.com/Ope
|
||||
| Sigma Designs UZB Stick | | | |
|
||||
| Tricklestar | | | |
|
||||
| Vision USB Stick | | | |
|
||||
| ZWave.me Razberry Board | ✓ | | |
|
||||
| ZWave.me UZB1 | ✓ | | |
|
||||
|
||||
<p class='note'>
|
||||
|
||||
@ -34,3 +34,9 @@ entity:
|
||||
- type: weather-forecast
|
||||
entity: weather.demo_weather_north
|
||||
```
|
||||
|
||||
<p class="note">
|
||||
This card works only with platforms that define a `weather` entity.
|
||||
|
||||
E.g., it works with [Dark Sky](https://www.home-assistant.io/components/weather.darksky/) but not [Dark Sky Sensor](https://www.home-assistant.io/components/sensor.darksky/)
|
||||
</p>
|
||||
|
||||
@ -81,6 +81,18 @@ You didn't think we would forget about Lovelace, did you? This release include a
|
||||
[light.lifx docs]: /components/light.lifx/
|
||||
[wemo docs]: /components/wemo/
|
||||
|
||||
## {% linkable_title Release 0.77.3 - September 3 %}
|
||||
|
||||
Frontend changes only:
|
||||
|
||||
- Ask "save login" after hass connected [PR](https://github.com/home-assistant/home-assistant-polymer/pull/1631) [@awarecan]
|
||||
- Show an error when invalid client id or redirect uri [PR](https://github.com/home-assistant/home-assistant-polymer/pull/1620) [@balloob]
|
||||
- Disable autocapitalization of username field [PR](https://github.com/home-assistant/home-assistant-polymer/pull/1627) [@timmo001]
|
||||
- Upgrade MDI icons [PR](https://github.com/home-assistant/home-assistant-polymer/pull/1630) [@balloob]
|
||||
- Update translations
|
||||
|
||||
[@timmo001]: https://github.com/timmo001
|
||||
|
||||
## {% 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.
|
||||
|
||||
@ -10,13 +10,13 @@ footer: true
|
||||
redirect_from: /components/cloud.alexa/
|
||||
---
|
||||
|
||||
The Alexa integration allows users to control the entities via the [Home Assistant Smart Home skill for Alexa][alexa skill]. This means that you can say things like "Alexa, turn on the kitchen light" to control your local Home Assistant.
|
||||
The Alexa integration allows users to control the entities via the Home Assistant Smart Home skill for Alexa. This means that you can say things like "Alexa, turn on the kitchen light" to control your local Home Assistant.
|
||||
|
||||
To use this integration, you need to have:
|
||||
|
||||
- The cloud component set up. [Learn more](/components/cloud/)
|
||||
- An Alexa enabled device like the Amazon Echo
|
||||
- Activated the [Home Assistant Smart Home skill for Alexa][alexa skill]
|
||||
- Activated the Home Assistant Smart Home skill via the Alexa app
|
||||
|
||||
You can use `configuration.yaml` to configure the entities that are being shown to Alexa and how they are exposed.
|
||||
|
||||
@ -110,5 +110,3 @@ Currently, the following domains are available to be used with Alexa:
|
||||
- scene
|
||||
- script (enables/disables)
|
||||
- switch
|
||||
|
||||
[alexa skill]: https://alexa.amazon.com/spa/index.html#skills/dp/B0772J1QKB/?ref=skill_dsk_skb_sr_2
|
||||
|
||||
@ -77,14 +77,14 @@ A detailed guide about running Hass.io as a virtual machine is available in the
|
||||
[etcher]: https://etcher.io/
|
||||
[Virtual Appliance]: https://github.com/home-assistant/hassos/blob/dev/Documentation/boards/ova.md
|
||||
[hassos-network]: https://github.com/home-assistant/hassos/blob/dev/Documentation/network.md
|
||||
[pi0-w]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_rpi0-w-2.2.img.gz
|
||||
[pi1]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_rpi-2.2.img.gz
|
||||
[pi2]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_rpi2-2.2.img.gz
|
||||
[pi3-32]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_rpi3-2.2.img.gz
|
||||
[pi3-64]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_rpi3-64-2.2.img.gz
|
||||
[pi0-w]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi0-w-1.10.img.gz
|
||||
[pi1]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi-1.10.img.gz
|
||||
[pi2]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi2-1.10.img.gz
|
||||
[pi3-32]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi3-1.10.img.gz
|
||||
[pi3-64]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_rpi3-64-1.10.img.gz
|
||||
[tinker]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_tinker-2.2.img.gz
|
||||
[odroid-c2]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_odroid-c2-2.2.img.gz
|
||||
[vmdk]: https://github.com/home-assistant/hassos/releases/download/2.2/hassos_ova-2.2.vmdk.gz
|
||||
[vmdk]: https://github.com/home-assistant/hassos/releases/download/1.10/hassos_ova-1.10.vmdk.gz
|
||||
[linux]: https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio
|
||||
[local]: http://hassio.local:8123
|
||||
[samba]: /addons/samba/
|
||||
|
||||
BIN
source/images/frontend/entity_box.png
Normal file
BIN
source/images/frontend/entity_box.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 351 B |
Loading…
x
Reference in New Issue
Block a user