jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-13 12:26:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2020-07-13 13:31:08 +02:00
commit 2dfbbd6a1d
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
40 changed files with 1731 additions and 111 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
.github/dependabot.yml vendored Normal file
View File

@ -0,0 +1,26 @@
version: 2
updates:
- package-ecosystem: npm
directory: "/"
schedule:
interval: daily
time: "06:00"
open-pull-requests-limit: 10
target-branch: current
- package-ecosystem: bundler
directory: "/"
schedule:
interval: daily
time: "06:00"
open-pull-requests-limit: 10
target-branch: current
allow:
- dependency-type: direct
- dependency-type: indirect
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: daily
time: "06:00"
open-pull-requests-limit: 10
target-branch: current

14
.github/workflows/test.yml vendored
View File

@ -10,11 +10,11 @@ jobs:
- name: Check out files from GitHub
uses: actions/checkout@v2
- name: Setting up Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v1
uses: actions/setup-node@v2.1.0
with:
node-version: 12.x
- name: Setup NPM cache
uses: actions/cache@v1
uses: actions/cache@v2
with:
path: ~/.npm
key: npm-${{ hashFiles('**/package-lock.json') }}
@ -33,11 +33,11 @@ jobs:
- name: Check out files from GitHub
uses: actions/checkout@v2
- name: Setting up Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v1
uses: actions/setup-node@v2.1.0
with:
node-version: 12.x
- name: Setup NPM cache
uses: actions/cache@v1
uses: actions/cache@v2
with:
path: ~/.npm
key: npm-${{ hashFiles('**/package-lock.json') }}
@ -57,11 +57,11 @@ jobs:
- name: Check out files from GitHub
uses: actions/checkout@v2
- name: Setting up Ruby 2.6
uses: actions/setup-ruby@v1
uses: actions/setup-ruby@v1.1.1
with:
ruby-version: 2.6
- name: Setup Ruby Gems cache
uses: actions/cache@v1
uses: actions/cache@v2
with:
path: vendor/bundle
key: gems-${{ hashFiles('**/Gemfile.lock') }}
@ -73,7 +73,7 @@ jobs:
bundle config path vendor/bundle
bundle install --jobs 4 --retry 3
- name: Setting up Jekyll cache
uses: actions/cache@v1
uses: actions/cache@v2
with:
path: source/.jekyll-cache
key: jekyll-${{ hashFiles('**/Gemfile.lock') }}-${{ hashFiles('**/_config.yml') }}

2
Gemfile
View File

@ -19,7 +19,7 @@ group :jekyll_plugins do
end
gem 'sinatra', '2.0.8.1'
gem 'nokogiri', '1.10.9'
gem 'nokogiri', '1.10.10'
# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
# and associated library

6
Gemfile.lock
View File

@ -73,9 +73,9 @@ GEM
multi_json (1.14.1)
mustermann (1.1.1)
ruby2_keywords (~> 0.0.1)
nokogiri (1.10.9)
nokogiri (1.10.10)
mini_portile2 (~> 2.4.0)
nokogiri (1.10.9-x64-mingw32)
nokogiri (1.10.10-x64-mingw32)
mini_portile2 (~> 2.4.0)
pathutil (0.16.2)
forwardable-extended (~> 2.6)
@ -127,7 +127,7 @@ DEPENDENCIES
jekyll-redirect-from (= 0.16.0)
jekyll-sitemap (= 1.4.0)
jekyll-time-to-read (= 0.1.2)
nokogiri (= 1.10.9)
nokogiri (= 1.10.10)
rake (= 13.0.1)
sass-globbing (= 1.1.5)
sinatra (= 2.0.8.1)

4
_config.yml
View File

@ -100,9 +100,9 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 111
current_minor_version: 112
current_patch_version: 4
date_released: 2020-06-17
date_released: 2020-07-08
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

40
package-lock.json generated
View File

@ -1620,9 +1620,9 @@
}
},
"minimist": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz",
"integrity": "sha1-o1AIsg9BOD7sH7kU9M1d95omQoQ=",
"version": "1.2.5",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz",
"integrity": "sha512-FM9nNUYrRBAELZQT3xeZQ7fmMOBg6nWNmJKTcgsJeaLstP/UODVpGsr5OhXhhXg6f+qtJ8uiZ+PUxkDWcgIXLw==",
"dev": true
},
"misspellings": {
@ -1632,20 +1632,12 @@
"dev": true
},
"mkdirp": {
"version": "0.5.1",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"integrity": "sha1-MAV0OOrGz3+MR2fzhkjWaX11yQM=",
"version": "0.5.5",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.5.tgz",
"integrity": "sha512-NKmAlESf6jMGym1++R0Ra7wvhV+wFW63FaSOFPwRahvea0gMUcGUhVeAg/0BC0wiv9ih5NYPB1Wn1UEI1/L+xQ==",
"dev": true,
"requires": {
"minimist": "0.0.8"
},
"dependencies": {
"minimist": {
"version": "0.0.8",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
"integrity": "sha1-hX/Kv8M5fSYluCKCYuhqp6ARsF0=",
"dev": true
}
"minimist": "^1.2.5"
}
},
"ms": {
@ -2107,18 +2099,18 @@
}
},
"remark-lint": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-7.0.0.tgz",
"integrity": "sha512-OLrWPYy0MUcGLa/2rjuy1kQILTRRK+JiRtyUzqe4XRoHboGuvFDcy/W2e7sq5hu/0xmD+Eh7cEa1Coiqp7LeaA==",
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-7.0.1.tgz",
"integrity": "sha512-caZXo3qhuBxzvq9JSJFVQ/ERDq/6TJVgWn0KDwKOIJCGOuLXfQhby5XttUq+Rn7kLbNMtvwfWHJlte14LpaeXQ==",
"dev": true,
"requires": {
"remark-message-control": "^6.0.0"
}
},
"remark-lint-fenced-code-flag": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/remark-lint-fenced-code-flag/-/remark-lint-fenced-code-flag-2.0.0.tgz",
"integrity": "sha512-SyQ31cdQlbsS+eBw2DUxkuzNwGIGlWnnCLyHLz3D1nxtZBVUaUOnIAturSA3PsguIrnxH4qD2JYCTp5aPbZhzQ==",
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/remark-lint-fenced-code-flag/-/remark-lint-fenced-code-flag-2.0.1.tgz",
"integrity": "sha512-+COnWHlS/h02FMxoZWxNlZW3Y8M0cQQpmx3aNCbG7xkyMyCKsMLg9EmRvYHHIbxQCuF3JT0WWx5AySqlc7d+NA==",
"dev": true,
"requires": {
"unified-lint-rule": "^1.0.0",
@ -2157,9 +2149,9 @@
}
},
"remark-lint-no-shell-dollars": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/remark-lint-no-shell-dollars/-/remark-lint-no-shell-dollars-2.0.1.tgz",
"integrity": "sha512-N+wOq3nmZ8WnCreWhi/rfIKQJPAz+pcbErQATcnQzH0znzldXlX8Ovlm54yDx/A+TmGMex/epkCwuiewIj9m4g==",
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/remark-lint-no-shell-dollars/-/remark-lint-no-shell-dollars-2.0.2.tgz",
"integrity": "sha512-zhkHZOuyaD3r/TUUkkVqW0OxsR9fnSrAnHIF63nfJoAAUezPOu8D1NBsni6rX8H2DqGbPYkoeWrNsTwiKP0yow==",
"dev": true,
"requires": {
"unified-lint-rule": "^1.0.0",

9
package.json
View File

@ -6,14 +6,17 @@
"devDependencies": {
"remark-cli": "^8.0.0",
"remark-frontmatter": "^2.0.0",
"remark-lint": "^7.0.0",
"remark-lint-fenced-code-flag": "^2.0.0",
"remark-lint-no-shell-dollars": "^2.0.1",
"remark-lint": "^7.0.1",
"remark-lint-fenced-code-flag": "^2.0.1",
"remark-lint-no-shell-dollars": "^2.0.2",
"remark-stringify": "^8.1.0",
"textlint": "^11.6.3",
"textlint-rule-common-misspellings": "^1.0.1",
"textlint-rule-terminology": "^2.1.4"
},
"resolutions": {
"minimist": ">=1.2.5"
},
"scripts": {
"markdown:lint": "remark --quiet --frail .",
"textlint:all": "textlint source",

3
source/_docs/configuration/customizing-devices.markdown
View File

@ -100,6 +100,9 @@ homeassistant:
icon: mdi:kettle
switch.rfxtrx_switch:
assumed_state: false
media_player.my_media_player:
source_list:
- Channel/input from my available sources
# Customize all entities in a domain
customize_domain:
light:

2
source/_docs/installation/raspberry-pi.markdown
View File

@ -41,7 +41,7 @@ sudo apt-get upgrade -y
Install the dependencies.
```bash
sudo apt-get install python3 python3-dev python3-venv python3-pip libffi-dev libssl-dev autoconf
sudo apt-get install python3 python3-dev python3-venv python3-pip libffi-dev libssl-dev autoconf build-essential
```
Add an account for Home Assistant Core called `homeassistant`.

14
source/_docs/scene.markdown
View File

@ -10,21 +10,21 @@ You can create scenes that capture the states you want certain entities to be. F
scene:
- name: Romantic
entities:
light.tv_back_light: on
light.tv_back_light: "on"
light.ceiling:
state: on
state: "on"
xy_color: [0.33, 0.66]
brightness: 200
- name: Movies
entities:
light.tv_back_light:
state: on
state: "on"
brightness: 125
light.ceiling: off
media_player.sony_bravia_tv:
state: on
state: "on"
source: HDMI 1
state: on
state: "on"
```
{% configuration %}
@ -75,11 +75,11 @@ automation:
data:
entities:
light.tv_back_light:
state: on
state: "on"
brightness: 100
light.ceiling: off
media_player.sony_bravia_tv:
state: on
state: "on"
source: HDMI 1
```

10
source/_docs/tools/dev-tools.markdown
View File

@ -14,10 +14,8 @@ Screenshot of Home Assistant's Developer Tools.
| ------- |----- |
| States | Sets the representation of an entity |
| Services | Calls services from integrations |
| Logs | Displays contents of Home Assistant log file |
| Events | Fires events |
| Templates | Renders templates |
| Info | Details about Home Assistant |
## What can I do with Developer Tools?
@ -92,11 +90,3 @@ For more information about jinja2, visit [jinja2 documentation](http://jinja.poc
This section is only visible if the MQTT integration is configured. To configure MQTT, add `mqtt:` to the `configuration.yaml` file. For more information, refer to the [MQTT](/integrations/mqtt/) integration.
Even though MQTT in general provides deeper functionality, the developer tools section of MQTT is limited to publishing messages to a given topic. It supports templates for the payload. To publish a message, simply specify the topic name and the payload and click “PUBLISH” button.
## Logs
This section displays `syslog` information, and the contents of `home-assistant.log` with an option to clear and refresh the logs.
## Info
The Information tab simply provides information about the current installed version, [system health](/integrations/system_health/) (if enabled), additional links and credits.

2
source/_integrations/arcam_fmj.markdown
View File

@ -10,7 +10,7 @@ ha_codeowners:
ha_domain: arcam_fmj
---
The `arcam_fmj` integration allows you to control [Arcam FMJ Receveivers](https://www.arcam.co.uk/range/fmj.htm) from Home Assistant.
The `arcam_fmj` integration allows you to control [Arcam FMJ Receivers](https://www.arcam.co.uk/range/fmj.htm) from Home Assistant.
Supported devices:

2
source/_integrations/cast.markdown
View File

@ -93,7 +93,7 @@ Optional:
### Manual configuration
By default, any discovered Cast device is added to Home Assistant. This can be restricted by supplying a white list of wanted chrome casts.
By default, any discovered Cast device is added to Home Assistant. This can be restricted by supplying a list of wanted chrome casts.
```yaml
# Example configuration.yaml entry

14
source/_integrations/denonavr.markdown
View File

@ -23,6 +23,7 @@ Known supported devices:
- Denon AVR-X2100W
- Denon AVR-X2200W
- Denon AVR-X2300W
- Denon AVR-X3200W
- Denon AVR-X3300W
- Denon AVR-X3400H
- Denon AVR-X3600H
@ -37,14 +38,20 @@ Known supported devices:
- Denon AVR-S710W
- Denon AVR-S720W
- Denon AVR-S750H
- Denon DN-500AV
- Marantz M-CR510
- Marantz M-CR511
- Marantz M-CR603
- Marantz M-CR610
- Marantz M-CR611
- Marantz SR5006
- Marantz SR5008
- Marantz SR5011
- Marantz SR6007 - SR6012
- Marantz NR1504
- Marantz NR1604
- Marantz NR1506
- Marantz NR1602
- Marantz NR1604
- Marantz NR1607
- Other Denon AVR receivers (untested)
- Marantz receivers (experimental)
@ -67,11 +74,6 @@ show_all_sources:
required: false
default: false
type: boolean
timeout:
description: Timeout in seconds for HTTP requests to the receiver.
required: false
default: 2
type: integer
zone1:
description: Specifies if zone 1 should be activated. Zones are displayed as additional media players with the same functionality as the Main Zone of the device supports.
required: false

2
source/_integrations/dialogflow.markdown
View File

@ -111,6 +111,6 @@ intent_script:
switch.turn_off
{%- endif -%}
data_template:
entity_id: "switch.light_{{ Room | replace(' ', '_') }}"
entity_id: "switch.light_{{ Room | striptags | replace(' ', '_') }}"
```
{% endraw %}

3
source/_integrations/home_connect.markdown
View File

@ -34,7 +34,8 @@ Note that it depends on the appliance and on API permissions which of the featur
- Application ID: Home Assistant (or whatever name makes sense to you)
- OAuth Flow: Authorization Code Grant Flow
- Redirect URI : `<YOUR_HOME_ASSISTANT_URL>/auth/external/callback`
- Redirect URI: "`<INTERNAL_HOME_ASSISTANT_URL>/auth/external/callback`
Use your internal Home Assistant URL, if you didn't configure one manually, use your local IP address. Examples: `http://192.168.0.2:8123/auth/external/callback`, `http://homeassistant.local:8123/auth/external/callback`."
3. Add the client ID and client secret to your `configuration.yaml` (see below).
4. Once Home Assistant has restarted, go to Configuration > Integrations.

2
source/_integrations/humidifier.markdown
View File

@ -18,7 +18,7 @@ Available services: `humidifier.set_mode`, `humidifier.set_humidity`, `humidifie
<div class='note'>
Not all humidifier services may be available for your platform. Be sure to check the available services Home Assistant has enabled by checking <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> **Services**.
Not all humidifier services may be available for your platform. Be sure to check the available services Home Assistant has enabled by checking the Services page in the [Developer Tools](/docs/tools/dev-tools/).
</div>

4
source/_integrations/hvv_departures.markdown
View File

@ -1,6 +1,6 @@
---
title: HVV Departures
description: Display the departures of busses, trains and fairies in Hamburg within Home Assistant.
description: Display the departures of busses, trains and ferries in Hamburg within Home Assistant.
ha_category:
- Transport
ha_iot_class: Cloud Polling
@ -11,7 +11,7 @@ ha_codeowners:
ha_domain: hvv_departures
---
The `hvv_departures` sensor will display the departures of busses, trains and fairies in Hamburg.
The `hvv_departures` sensor will display the departures of busses, trains and ferries in Hamburg.
## Configuration

8
source/_integrations/recorder.markdown
View File

@ -212,11 +212,11 @@ Note that purging will not immediately decrease disk space usage but it will sig
| Database engine | `db_url` |
| :----------------------------- | :------------------------------------------------------------------------------------------- |
| SQLite | `sqlite:////PATH/TO/DB_NAME` |
| MariaDB | `mysql+pymysql://SERVER_IP/DB_NAME?charset=utf8` |
| MariaDB | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` |
| MariaDB (omit pymysql) | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` |
| MySQL | `mysql://SERVER_IP/DB_NAME?charset=utf8` |
| MySQL | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` |
| MariaDB | `mysql+pymysql://SERVER_IP/DB_NAME?charset=utf8` |
| MariaDB | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` |
| PostgreSQL | `postgresql://SERVER_IP/DB_NAME` |
| PostgreSQL | `postgresql://user:password@SERVER_IP/DB_NAME` |
| PostgreSQL (Socket) | `postgresql://@/DB_NAME` |
@ -231,7 +231,9 @@ Some installations of MariaDB/MySQL may require an ALTERNATE_PORT (3rd-party hos
<div class='note'>
If using an external MariaDB backend (e.g., running on a separate NAS) with Home Assistant, you should omit `pymysql` from the URL. `pymysql` is not included in the base Docker image, and is not necessary for this to work.
When using a MariaDB or MySQL server, adding `+pymysql` to the URL will use the pure Python MySQL library, which is slower but may be required if the C MySQL library is not available.
When using the official Docker image, the C MySQL library will always be available. `pymysql` is most commonly used with `venv` where the C MySQL library is not installed.
</div>

3
source/_integrations/samsungtv.markdown
View File

@ -118,6 +118,7 @@ For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North Am
- MU6170UXZG
- MU6179
- MU6199
- MU650D (on works with WOL, channel change not tested)
- NU7090 (On/Off)
- NU7400
- NU8000
@ -125,7 +126,9 @@ For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North Am
- U6000
- U6300
- RU7100
- RU7170
- RU7172
- RU7475
- Q90RATXZT
#### Models tested but not yet working

16
source/_integrations/scene.markdown
View File

@ -18,19 +18,19 @@ scene:
- name: Romantic
icon: "mdi:flower-tulip"
entities:
light.tv_back_light: on
light.tv_back_light: "on"
light.ceiling:
state: on
state: "on"
xy_color: [0.33, 0.66]
brightness: 200
- name: Movies
entities:
light.tv_back_light:
state: on
state: "on"
brightness: 125
light.ceiling: off
media_player.sony_bravia_tv:
state: on
state: "on"
source: HDMI 1
```
@ -86,11 +86,11 @@ automation:
data:
entities:
light.tv_back_light:
state: on
state: "on"
brightness: 100
light.ceiling: off
media_player.sony_bravia_tv:
state: on
state: "on"
source: HDMI 1
```
@ -145,11 +145,11 @@ automation:
scene_id: my_scene
entities:
light.tv_back_light:
state: on
state: "on"
brightness: 100
light.ceiling: off
media_player.sony_bravia_tv:
state: on
state: "on"
source: HDMI 1
```

2
source/_integrations/sensor.mqtt.markdown
View File

@ -71,7 +71,7 @@ expire_after:
default: 0
force_update:
description: Sends update events even if the value hasn't changed. Useful if you want to have meaningful value graphs in history.
reqired: false
required: false
type: boolean
default: false
icon:

3
source/_integrations/smappee.markdown
View File

@ -18,7 +18,8 @@ The Smappee integration will allow users to integrate their Smappee monitors, pl
## Configuration
To use the Smappee integration you need a personal `client_id` and `client_secret` and add these to your `configuration.yaml` file. The `client_id` and `client_secret` can be obtained by contacting [support@smappee.com](mailto:support@smappee.com).
To use the Smappee integration you need a personal `client_id` and `client_secret` and add these to your `configuration.yaml` file. The `client_id` and `client_secret` can be obtained by contacting [info@smappee.com](mailto:info@smappee.com) and require a recurring monthly fee.
For any information about the use of the API please refer to the [Smappee API space](https://smappee.atlassian.net/wiki/spaces/DEVAPI/overview).
```yaml
# Example configuration.yaml entry

4
source/_integrations/switch.mqtt.markdown
View File

@ -135,6 +135,10 @@ state_topic:
description: The MQTT topic subscribed to receive state updates.
required: false
type: string
unique_id:
description: An ID that uniquely identifies this switch device. If two switches have the same unique ID, Home Assistant will raise an exception.
required: false
type: string
value_template:
description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract device's state from the `state_topic`. To determine the switches's state result of this template will be compared to `state_on` and `state_off`."
required: false

2
source/_integrations/system_log.markdown
View File

@ -8,7 +8,7 @@ ha_quality_scale: internal
ha_domain: system_log
---
The `system_log` integration stores information about all logged errors and warnings in Home Assistant. All collected information is accessible directly in the frontend, just navigate to the `Info` section under `Developer Tools`. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`.
The `system_log` integration stores information about all logged errors and warnings in Home Assistant. To view your logs, navigate to **Configuration** -> **Logs**. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`.
## Configuration

14
source/_integrations/vacuum.mqtt.markdown
View File

@ -158,7 +158,7 @@ retain:
type: boolean
default: false
schema:
description: The schema to use. Must be `legacy` or omitted to select the legacy schema".
description: The schema to use. Must be `legacy` or omitted to select the legacy schema.
required: false
type: string
default: legacy
@ -171,10 +171,14 @@ set_fan_speed_topic:
required: false
type: string
supported_features:
description: List of features that the vacuum supports (possible values are `turn_on`, `turn_off`, `pause`, `stop`, `return_home`, `battery`, `status`, `locate`, `clean_spot`, `fan_speed`, `send_command`)."
description: List of features that the vacuum supports (possible values are `turn_on`, `turn_off`, `pause`, `stop`, `return_home`, `battery`, `status`, `locate`, `clean_spot`, `fan_speed`, `send_command`).
required: false
type: [string, list]
default: "`turn_on`, `turn_off`, `stop`, `return_home`, `status`, `battery`, `clean_spot`"
unique_id:
description: An ID that uniquely identifies this vacuum. If two vacuums have the same unique ID, Home Assistant will raise an exception.
required: false
type: string
{% endconfiguration %}
### Legacy configuration example
@ -370,7 +374,7 @@ retain:
type: boolean
default: false
schema:
description: The schema to use. Must be `state` to select the state schema".
description: The schema to use. Must be `state` to select the state schema.
required: false
type: string
default: legacy
@ -391,6 +395,10 @@ supported_features:
required: false
type: [string, list]
default: "`start`, `stop`, `return_home`, `status`, `battery`, `clean_spot`"
unique_id:
description: An ID that uniquely identifies this vacuum. If two vacuums have the same unique ID, Home Assistant will raise an exception.
required: false
type: string
{% endconfiguration %}
### State configuration example

1
source/_integrations/vesync.markdown
View File

@ -89,6 +89,7 @@ Adapted from the [TP-Link integration](https://www.home-assistant.io/integration
```yaml
sensor:
- platform: template
sensors:
vesync_switch_watts:
friendly_name_template: "{{ states.switch.vesync_switch.name}} Current Consumption"
value_template: '{{ states.switch.vesync_switch.attributes["current_power_w"] | float }}'

11
source/_integrations/zha.markdown
View File

@ -163,11 +163,12 @@ Note that the `otau_directory` setting is optional and can be used for any firmw
## Adding devices
Go to the **Configuration** page and select the **ZHA** integration that was added by the configuration steps above.
To add a new device:
Click on **ADD DEVICES** to start a scan for new devices.
Reset your Zigbee devices according to the device instructions provided by the manufacturer (e.g., turn on/off lights up to 10 times, switches usually have a reset button/pin).
1. Go to the **Integrations** page, find the **Zigbee Home Automation** integration that was added by the configuration steps above, and select **Configure**.
1. Click on the plus button at the bottom right corner to start a scan for new devices.
1. Reset your Zigbee devices according to the device instructions provided by the manufacturer (e.g., turn on/off lights up to 10 times, switches usually have a reset button/pin). It might take a few seconds for the devices to appear. You can click on **Show logs** for more verbose output.
1. Once the device is found, it will appear on that page and will be automatically added to your devices. You can optionally change its name and add it to an area (you can change this later). You can search again to add another device, or you can go back to the list of added devices.
## Troubleshooting
@ -178,7 +179,7 @@ When reporting issues, please provide the following information in addition to i
1. Debug logs for the issue, see [debug logging](#debug-logging)
2. Model of Zigbee radio being used
3. If issue is related to a specific Zigbee device, provide device Zigbee signature. Signature is available at
`Configuration` Panel -> `Zigbee Home Automation` -> Pick your Device -> `Zigbee Information`
**Configuration** -> **Integrations** -> **Zigbee Home Automation** (click **Configure**) -> **Devices** (pick your device) -> **Zigbee Device Signature**
### Debug logging

1581
source/_posts/2020-07-01-release-112.markdown Normal file
View File

File diff suppressed because it is too large Load Diff

34
source/hassio/installation.markdown
View File

@ -107,23 +107,23 @@ If you would like to test next release before anyone else, you can install the b
[balenaEtcher]: https://www.balena.io/etcher
[hassos-network]: https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md
[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi0-w-4.10.img.gz
[pi1]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi-4.10.img.gz
[pi2]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi2-4.10.img.gz
[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi3-4.10.img.gz
[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi3-64-4.10.img.gz
[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi4-4.10.img.gz
[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi4-64-4.10.img.gz
[tinker]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_tinker-4.10.img.gz
[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_odroid-c2-4.10.img.gz
[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_odroid-n2-4.10.img.gz
[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_odroid-xu4-4.10.img.gz
[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_intel-nuc-4.10.img.gz
[vmdk]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_ova-4.10.vmdk.gz
[vhdx]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_ova-4.10.vhdx.gz
[vdi]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_ova-4.10.vdi.gz
[qcow2]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_ova-4.10.qcow2.gz
[Virtual Appliance]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_ova-4.10.ova
[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi0-w-4.11.img.gz
[pi1]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi-4.11.img.gz
[pi2]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi2-4.11.img.gz
[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi3-4.11.img.gz
[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi3-64-4.11.img.gz
[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi4-4.11.img.gz
[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi4-64-4.11.img.gz
[tinker]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_tinker-4.11.img.gz
[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_odroid-c2-4.11.img.gz
[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_odroid-n2-4.11.img.gz
[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_odroid-xu4-4.11.img.gz
[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_intel-nuc-4.11.img.gz
[vmdk]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vmdk.gz
[vhdx]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vhdx.gz
[vdi]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vdi.gz
[qcow2]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.qcow2.gz
[Virtual Appliance]: https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.ova
[local]: http://homeassistant.local:8123
[samba]: /addons/samba/
[ssh]: /addons/ssh/

2
source/help/index.markdown
View File

@ -22,6 +22,8 @@ Have you found an issue in your Home Assistant installation? Please report it. R
- [Issue tracker Home Assistant Frontend](https://github.com/home-assistant/frontend/issues)
- [Issue tracker Home Assistant Supervisor](https://github.com/home-assistant/supervisor/issues)
- [Issue tracker Home Assistant Operating System](https://github.com/home-assistant/operating-system/issues)
- [Issue tracker Home Assistant Android App](https://github.com/home-assistant/android/issues)
- [Issue tracker Home Assistant iOS App](https://github.com/home-assistant/ios/issues)
- [Issue tracker website & documentation](https://github.com/home-assistant/home-assistant.io/issues)
## Videos, talks, workshops and alike

BIN
source/images/blog/2020-07-0.112/configure-mqtt.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 16 KiB

BIN
source/images/blog/2020-07-0.112/datetime-picker.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 32 KiB

BIN
source/images/blog/2020-07-0.112/logbook-who.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 16 KiB

BIN
source/images/blog/2020-07-0.112/new-home.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 41 KiB

BIN
source/images/blog/2020-07-0.112/social.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 114 KiB

BIN
source/images/blog/2020-07-0.112/zha-device.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 51 KiB

BIN
source/images/screenshots/configuration-validation.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 8.8 KiB

After

Width:  |  Height:  |  Size: 11 KiB

BIN
source/images/screenshots/developer-tools.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 6.8 KiB

After

Width:  |  Height:  |  Size: 12 KiB

2
source/ios/beta.markdown
View File

@ -3,4 +3,4 @@ title: "Join Home Assistant iOS beta"
description: "Invitation to join the Home Assistant iOS beta."
---
<script>document.location.href = 'https://testflight.apple.com/join/VBsqCiBv';</script>
<script>document.location.href = 'https://companion.home-assistant.io/app/ios/beta';</script>