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-18 23:06:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2022-06-13 03:04:43 +02:00
commit 571092ff13
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
107 changed files with 543 additions and 513 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -43,6 +43,6 @@
- [ ] This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the `current` branch.
- I made a change that is related to an upcoming version of Home Assistant and used the `next` branch.
- [ ] The documentation follows the Home Assistant documentation [standards][].
- [ ] The documentation follows the Home Assistant documentation [standards].
[standards]: https://developers.home-assistant.io/docs/documenting/standards

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

@ -10,7 +10,7 @@ jobs:
- name: Check out files from GitHub
uses: actions/checkout@v3.0.2
- name: Setting up Node.js
uses: actions/setup-node@v3.2.0
uses: actions/setup-node@v3.3.0
with:
node-version: 16.x
cache: "npm"
@ -27,7 +27,7 @@ jobs:
- name: Check out files from GitHub
uses: actions/checkout@v3.0.2
- name: Setting up Node.js
uses: actions/setup-node@v3.2.0
uses: actions/setup-node@v3.3.0
with:
node-version: 16.x
cache: "npm"

4
Gemfile.lock
View File

@ -5,7 +5,7 @@ GEM
public_suffix (>= 2.0.2, < 5.0)
chunky_png (1.4.0)
colorator (1.1.0)
commonmarker (0.23.4)
commonmarker (0.23.5)
compass (1.0.3)
chunky_png (~> 1.2)
compass-core (~> 1.0.2)
@ -87,7 +87,7 @@ GEM
rb-inotify (0.10.1)
ffi (~> 1.0)
rexml (3.2.5)
rouge (3.28.0)
rouge (3.29.0)
ruby2_keywords (0.0.5)
safe_yaml (1.0.5)
sass (3.4.25)

2
README.md
View File

@ -9,7 +9,7 @@ This is the source for the [Home-Assistant.io website](https://home-assistant.io
## Setup
Setting up to contribute to documentation and the process for submitting pull requests is explained in the [developer documentation](https://developers.home-assistant.io/docs/documenting).
Setting up to contribute to documentation and the process for submitting pull requests is explained in the [developer documentation](https://developers.home-assistant.io/docs/documenting/).
## Site preview

4
_config.yml
View File

@ -107,8 +107,8 @@ social:
# Home Assistant release details
current_major_version: 2022
current_minor_version: 6
current_patch_version: 0
date_released: 2022-06-01
current_patch_version: 5
date_released: 2022-06-10
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

2
source/_docs/mqtt/broker.markdown
View File

@ -18,7 +18,7 @@ The recommended setup method is to use the [Mosquitto MQTT broker add-on](https:
Neither ActiveMQ MQTT broker nor the RabbitMQ MQTT Plugin are supported, use a known working broker like Mosquitto instead.
There are [at least two](https://issues.apache.org/jira/browse/AMQ-6360) [issues](https://issues.apache.org/jira/browse/AMQ-6575) with the ActiveMQ MQTT broker which break MQTT message retention.
There is [an issue](https://github.com/rabbitmq/rabbitmq-mqtt/issues/154) with the RabbitMQ MQTT Plugin which breaks MQTT message retention.
There is [an issue](https://github.com/rabbitmq/rabbitmq-server/issues/154) with the RabbitMQ MQTT Plugin which breaks MQTT message retention.
</div>

6
source/_docs/mqtt/testing.markdown
View File

@ -4,13 +4,13 @@ description: "Instructions on how to test your MQTT setup."
logo: mqtt.png
---
The `mosquitto` broker package ships commandline tools (often as `*-clients` package) to send and receive MQTT messages. As an alternative have a look at [hbmqtt_pub](https://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_pub.html) and [hbmqtt_sub](https://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_sub.html) which are provided by HBMQTT. For sending test messages to a broker running on localhost check the example below:
The `mosquitto` broker package ships commandline tools (often as `*-clients` package) to send and receive MQTT messages. For sending test messages to a broker running on `localhost` check the example below:
```bash
mosquitto_pub -h 127.0.0.1 -t home-assistant/switch/1/on -m "Switch is ON"
```
Another way to send MQTT messages manually is to use the "MQTT" Integration in the frontend. Choose the "Configuration" tab, click "Integrations" and click the "Configure" option under the "MQTT" integration. Enter something similar to the example below into the "topic" field under "Publish a packet*.
Another way to send MQTT messages manually is to use the "MQTT" integration in the frontend. Choose "Settings" on the left menu, click "Devices & Services", and choose "Configure" in the "Mosquitto broker" tile. Enter something similar to the example below into the "topic" field under "Publish a packet" and press "PUBLISH" .
```bash
home-assistant/switch/1/power
@ -22,7 +22,7 @@ and in the Payload field
ON
```
In the "Listen to a topic" field, type # to see everything, or "home-assistant/switch/#" to just follow the published topic. Press "Start Listening" and then press "Publish". The result should appear similar to the text below
In the "Listen to a topic" field, type `#` to see everything, or "home-assistant/switch/#" to just follow a published topic, then press "START LISTENING". The messages should appear similar to the text below:
```bash
Message 23 received on home-assistant/switch/1/power/stat/POWER at 12:16 PM:

18
source/_docs/z-wave/controllers.markdown
View File

@ -7,6 +7,18 @@ description: "Extended instructions how to setup Z-Wave."
You need to have a compatible Z-Wave stick or module installed. The following devices have been confirmed to work with Z-Wave JS:
<div class='note warning'>
Until recently, 700 series Z-Wave Controllers had a bug that could cause the mesh to be flooded on some networks and the controller to become unresponsive. At present, all 700 series controllers share the same firmware and are subject to this bug. It appears that this bug is largely, if not completely, resolved as of firmware version 7.17.2.
Users should upgrade the firmware on all 700 series controllers to version 7.17.2 or greater. Firmware can be upgraded using the below directions:
- [Upgrade instructions using Linux](https://github.com/kpine/zwave-js-server-docker/wiki/700-series-Controller-Firmware-Updates-(Linux))
- [Upgrade instructions using Windows (Aeotec)](https://help.aeotec.com/support/solutions/articles/6000252296-update-z-stick-7-with-windows)
- [Upgrade instructions using Windows (Zooz)](https://www.support.getzooz.com/kb/article/931-how-to-perform-an-ota-firmware-update-on-your-zst10-700-z-wave-stick/)
</div>
- 700 series controllers
- Aeotec Z-Stick 7 USB stick (ZWA010)
- Aeotec Z-Pi 7 Raspberry Pi HAT/Shield (ZWA025)
@ -27,11 +39,7 @@ You need to have a compatible Z-Wave stick or module installed. The following de
- Aeotec Z-Pi 7 (700 series)
- ZWave.me Razberry Board (500 series)
If you are just starting out, we recommend that you purchase a 500 series controller. At the very least, you should purchase a [Z-Wave Plus](https://z-wavealliance.org/z-wave_plus_certification/) controller.
<div class='note'>
Not all of the above devices are supported by the deprecated Z-Wave integration.
</div>
If you are just starting out, we recommend that you purchase a 500 series controller.
<div class='note'>
If you're using Home Assistant OS, Supervised, or Container, it's recommended to use a USB stick, not a module. Passing a module through Docker is more complicated than passing a USB stick through.

10
source/_includes/common-tasks/beta_version.md
View File

@ -48,24 +48,26 @@ docker pull {{ site.installation.container }}:beta
{% elsif page.installation == "core" %}
1. Switch to the user that is running Home Assistant
1. Stop the Home Assistant service.
2. Switch to the user that is running Home Assistant
```bash
sudo -u homeassistant -H -s
```
2. Activate the virtual environment that Home Assistant is running in
3. Activate the virtual environment that Home Assistant is running in
```bash
source /srv/homeassistant/bin/activate
```
3. Download and install the beta version
4. Download and install the beta version
```bash
pip3 install --pre --upgrade homeassistant
```
4. When that is complete restart the service for it to use the new files.
5. When that is complete start the service again for it to use the new files.
{% endif %}

10
source/_includes/common-tasks/development_version.md
View File

@ -38,24 +38,26 @@ docker pull {{ site.installation.container }}:dev
{% elsif page.installation == "core" %}
1. Switch to the user that is running Home Assistant
1. Stop the Home Assistant service.
2. Switch to the user that is running Home Assistant
```bash
sudo -u homeassistant -H -s
```
2. Activate the virtual environment that Home Assistant is running in
3. Activate the virtual environment that Home Assistant is running in
```bash
source /srv/homeassistant/bin/activate
```
3. Download and install the version you want
4. Download and install the version you want
```bash
pip3 install --upgrade git+https://github.com/home-assistant/core.git@dev
```
4. When that is complete restart the service for it to use the new files.
5. When that is complete start the service again for it to use the new files.
{% endif %}

22
source/_includes/common-tasks/filters.md Normal file
View File

@ -0,0 +1,22 @@
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, accept
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), accept
- If domain is not included, glob pattern does not match, and entity not included, reject
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, reject
- If entity matches exclude glob pattern and entity not included, reject
- If entity does not match any exclude criteria (domain, glob pattern or listed), accept
- Neither include or exclude specifies domains or glob patterns
- If entity is included, accept (as #2 above)
- If entity include and exclude, the entity exclude is ignored
The following characters can be used in entity globs:
`*` - The asterisk represents zero, one, or multiple characters
`?` - The question mark represents a single character

10
source/_includes/common-tasks/specific_version.md
View File

@ -20,24 +20,26 @@ docker pull {{ site.installation.container }}:{{current_version}}
{% elsif page.installation == "core" %}
1. Switch to the user that is running Home Assistant
1. Stop the Home Assistant service.
2. Switch to the user that is running Home Assistant
```bash
sudo -u homeassistant -H -s
```
2. Activate the virtual environment that Home Assistant is running in
3. Activate the virtual environment that Home Assistant is running in
```bash
source /srv/homeassistant/bin/activate
```
3. Download and install the version you want
4. Download and install the version you want
```bash
pip3 install homeassistant=={{current_version}}
```
4. When that is complete restart the service for it to use the new files.
5. When that is complete start the service again for it to use the new files.
{% endif %}

10
source/_includes/common-tasks/update.md
View File

@ -61,24 +61,26 @@ To update Home Assistant Core when you run Home Assistant {{ page.installation_n
{% elsif page.installation == "core" %}
1. Switch to the user that is running Home Assistant
1. Stop the Home Assistant service.
2. Switch to the user that is running Home Assistant
```bash
sudo -u homeassistant -H -s
```
2. Activate the virtual environment that Home Assistant is running in
3. Activate the virtual environment that Home Assistant is running in
```bash
source /srv/homeassistant/bin/activate
```
3. Download and install the new version
4. Download and install the new version
```bash
pip3 install --upgrade homeassistant
```
4. When that is complete restart the service for it to use the new files.
5. When that is complete start the service again for it to use the new files.
{% endif %}

48
source/_includes/installation/container/alternative.md
View File

@ -89,51 +89,3 @@ The steps would be:
- Your Home Assistant within Docker should now run and will serve the web interface from port 8123 on your Docker host (this will be your Qnap NAS IP address - for example `http://192.xxx.xxx.xxx:8123`)
Remark: To update your Home Assistant on your Docker within Qnap NAS, you just remove container and image and do steps again (Don't remove "config" folder).
If you want to use a USB Bluetooth adapter or Z-Wave USB stick with Home Assistant on Qnap Docker, follow those steps:
#### Z-Wave
- Connect to your NAS over SSH
- Load cdc-acm kernel module(when NAS restart need to run this command)
`insmod /usr/local/modules/cdc-acm.ko`
- Find USB devices attached. Type command:
`ls /dev/tty*`
The above command should show you any USB devices plugged into your NAS. If you have more than one, you may get multiple items returned. Like : `ttyACM0`
- Run Docker command:
```bash
docker run --init --name homeassistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e TZ=Europe/London --device /dev/ttyACM0 {{ site.installation.container }}:stable
```
`-v` is your configuration path
`-e` is set timezone
- Edit `configuration.yaml`
```yaml
zwave:
usb_path: /dev/ttyACM0
```
That will tell Home Assistant where to look for our Z-Wave radio.
#### Bluetooth
- Connect to your NAS over SSH
- Run Docker command:
```bash
docker run --init --name homeassistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e TZ=Europe/London -v /dev/bus/usb:/dev/bus/usb -v /var/run/dbus:/var/run/dbus {{ site.installation.container }}:stable
```
First `-v` is your configuration path
`-e` is set timezone
- Edit the `configuration.yaml` file
```yaml
device_tracker:
- platform: bluetooth_tracker
```

23
source/_integrations/aladdin_connect.markdown
View File

@ -20,25 +20,4 @@ The `aladdin_connect` cover platform lets you control Genie Aladdin Connect gara
Only doors that are owned by your Aladdin Connect account will be available. Doors that your account has been granted shared access to are not yet supported.
</div>
## Configuration
To use your Aladdin Connect cover in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
cover:
- platform: aladdin_connect
username: YOUR_USERNAME
password: YOUR_PASSWORD
```
{% configuration %}
username:
description: Your Aladdin Connect account username.
required: true
type: string
password:
description: Your Aladdin Connect account password.
required: true
type: string
{% endconfiguration %}
{% include integrations/config_flow.md %}

6
source/_integrations/alarm_control_panel.mqtt.markdown
View File

@ -306,7 +306,8 @@ mqtt:
value_template: "{{ value_json.state }}"
command_topic: "alarmdecoder/panel/set"
code: REMOTE_CODE_TEXT
command_template: "{ action: '{{ action }}', code: '{{ code }}'}"
command_template: >
{ "action": "{{ action }}", "code": "{{ code }}" }
```
```yaml
@ -318,7 +319,8 @@ mqtt:
value_template: "{{ value_json.state }}"
command_topic: "alarmdecoder/panel/set"
code: REMOTE_CODE
command_template: "{ action: '{{ action }}', code: '{{ code }}'}"
command_template: >
{ "action": "{{ action }}", "code": "{{ code }}" }
```
{% endraw %}

18
source/_integrations/alexa.smart_home.markdown
View File

@ -385,23 +385,7 @@ alexa:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}
See the [troubleshooting](#troubleshooting) if for issues setting up the integration.

18
source/_integrations/apache_kafka.markdown
View File

@ -104,20 +104,4 @@ apache_kafka:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}

18
source/_integrations/azure_event_hub.markdown
View File

@ -57,23 +57,7 @@ azure_event_hub:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}
{% configuration %}
filter:

20
source/_integrations/buienradar.markdown
View File

@ -48,7 +48,25 @@ The following entities will be created:
- **Station name**: The name of the selected meteo-station
- **Barometer forecast**: A numeric barometric forecast (1 to 7)
- **Barometer forecast name**: A textual representation of the barometer forecast (eg: Thunderstorms, Stable, etc.)
- **Condition code**: A symbol and a unique code identifying the current weather condition (`[a..z]`)
- **Condition code**: A symbol and a unique code identifying the current weather condition
* `a`: sunny/clear
* `b`: Mix of clear and medium or low clouds
* `j`: Mix of clear and high clouds
* `o/r`: Partly cloudy (increasing character increases the condition)
* `c`: Heavily clouded
* `p`: Cloudy
* `d`: Alternating cloudy with local fog
* `n`: Clear and local mist or fog
* `f`: Alternatingly cloudy with some light rain
* `h/k/l`: rainy (increasing character increases the condition)
* `q`: Heavily clouded with rain
* `w`: Heavily clouded with rain and winter precipitation
* `m`: Heavily clouded with some light rain
* `u`: Cloudy with light snow
* `i/v`: Heavily clouded with light snowfall (increasing character increases the condition)
* `t`: (Heavy snowfall)
* `g`: (Clear with (possibly) some heavy lightning)
* `s`: (Cloudy with (possibly) some heavy (thunderstorms) showers)
- **Condition**: A symbol and the current weather condition (`clear`, `cloudy`, `fog`, `rainy`, `snowy` or `lightning`)
- **Condition detailed**: A symbol and detailed current weather condition (`clear`, `partlycloudy`, `cloudy`, `partlycloudy-fog`, `partlycloudy-light-rain`, `partlycloudy-rain`, `light-rain`, `rainy`, `snowy-rainy`, `partlycloudy-light-snow`, `partlycloudy-snow`, `light-snow`, `snowy`, `partlycloudy-lightning` or `lightning`)
- **Condition exact**: A symbol with the full current weather condition (in English)

2
source/_integrations/daikin.markdown
View File

@ -38,7 +38,7 @@ There is currently support for the following device types within Home Assistant:
- The European versions of the Wifi Controller Unit (BRP069A41, 42, 43, 45), which is powered by the [Daikin Online Controller](https://play.google.com/store/apps/details?id=eu.daikin.remoapp) application. The new version of WiFi Controller Unit BRP069Bxx is also confirmed to work, tested and working devices are the BRP069B41 and BRP069B45.
- The Australian version of the Daikin Wifi Controller Unit BRP072A42, which is operated by the [Daikin Mobile Controller (iOS)](https://itunes.apple.com/au/app/daikin-mobile-controller/id917168708?mt=8) ([Android](https://play.google.com/store/apps/details?id=ao.daikin.remoapp)) application. Confirmed working on a Daikin Cora Series Reverse Cycle Split System Air Conditioner 2.5kW Cooling FTXM25QVMA with operation mode, temp, fan swing (3d, horizontal, vertical).
- BRP072Cxx based units (including Zena devices)*.
- The United States version of the Wifi Controller Unit (BRP069A43), which is powered by the [Daikin Comfort Control](https://play.google.com/store/apps/details?id=us.daikin.wwapp) application. Confirmed working on a Daikin Wall Unit FTXS15LVJU and a Floor Unit FVXS15NVJU with operation mode, temp, fan swing (3d, horizontal, vertical).
- The United States version of the Wifi Controller Unit (BRP069A43), which is powered by the [Daikin Comfort Control](https://play.google.com/store/apps/details?id=us.daikin.wwapp) application. Confirmed working on a Daikin Wall Units FTXS09LVJU, FTXS15LVJU, FTXS18LVJU and a Floor Unit FVXS15NVJU with operation mode, temp, fan swing (3d, horizontal, vertical).
- The Australian version of the Daikin Wifi Controller for **AirBase** units (BRP15B61), which is operated by the [Daikin Airbase](https://play.google.com/store/apps/details?id=au.com.daikin.airbase) application.
- **SKYFi** based units, which is operated by the SKYFi application*.

1
source/_integrations/denonavr.markdown
View File

@ -47,6 +47,7 @@ Known supported devices:
- Denon AVR-X4300H
- Denon AVR-X4400H
- Denon AVR-X4500H
- Denon AVR-X4700H
- Denon AVR-X6500H
- Denon AVR-X6700H
- Denon AVR-1912

2
source/_integrations/dlink.markdown
View File

@ -23,7 +23,7 @@ To use your D-Link smart plugs in your installation, add the following to your `
```yaml
# Example configuration.yaml entry
switch:
platform: dlink
- platform: dlink
host: IP_ADRRESS
username: YOUR_USERNAME
password: YOUR_PASSWORD

1
source/_integrations/dsmr.markdown
View File

@ -72,7 +72,6 @@ It is also possible to connect to a [RFXtrx device](http://www.rfxcom.com/epages
#### USB serial converters:
- Cheap (Banggood/ebay) Generic PL2303
- [Smartmeter Webshop](https://sites.google.com/site/nta8130p1smartmeter/webshop)
- [SOS Solutions](https://www.sossolutions.nl/slimme-meter-kabel)
- [AliExpress](https://nl.aliexpress.com/item/32945187155.html)

3
source/_integrations/epsonworkforce.markdown
View File

@ -69,7 +69,8 @@ Tested devices:
- Epson WF3640
- Epson EcoTank ET-77x0
- Epson ET-2650
- Espon ET-4750
- Epson ET-4750
- Epson EcoTank ET-5150 (51x0)
- Epson Expression Home XP-2105
To make this module work you need to connect your printer to your LAN.

4
source/_integrations/google.markdown
View File

@ -38,7 +38,7 @@ This section explains how to generate a Client ID and Client Secret on
1. You will then be automatically taken to the OAuth consent screen, you do not need to add any scopes here so click `SAVE AND CONTINUE` to move to the `Test users` page. You will need to add the Gmail address you will be using with this integration as a test user before you will be allowed to use the API. Once you have added your email address under `Test users` click `SAVE AND CONTINUE` which will take to the 'Summary' page (you do not need to do anything here).
1. Click Credentials in the menu on the left hand side of the screen, then click `+ Create credentials` (at the top of the screen), then select `OAuth client ID`.
1. Set the Application type to `TV and Limited Input` and give this credential set a name (like "Home Assistant Credentials") then click 'Create'.
1. You will then be presented with a pop-up saying 'OAuth client created' showing `Your Client ID` and `Your Client Secret`. Make a note of these (for example, copy and paste them into a text editor) as you will need to put these in your `configuration.yaml` file shortly. Once you have noted these strings, click `OK`. If you need to find these credentials again at any point then simply navigate to `APIs & Services` > `Credentials` and you will see `Home Assistant Credentials` (or whatever you named them in the previous step) under `OAuth 2.0 Clident IDs`. To view both the `Client ID` and `Client secret`, click on the pencil icon, this will take you to the settings page for these credentials and the information will be on the right hand side of the page.
1. You will then be presented with a pop-up saying 'OAuth client created' showing `Your Client ID` and `Your Client Secret`. Make a note of these (for example, copy and paste them into a text editor) as you will need to put these in your `configuration.yaml` file shortly. Once you have noted these strings, click `OK`. If you need to find these credentials again at any point then simply navigate to `APIs & Services` > `Credentials` and you will see `Home Assistant Credentials` (or whatever you named them in the previous step) under `OAuth 2.0 Client IDs`. To view both the `Client ID` and `Client secret`, click on the pencil icon, this will take you to the settings page for these credentials and the information will be on the right hand side of the page.
1. We need to double check that the "Google Calendar API" has been automatically enabled. To do this, select `Library` from the menu, then search for "Google Calendar API". If it is enabled you will see `API Enabled` with a green tick next to it. If it is not enabled, then enable it.
{% enddetails %}
@ -160,7 +160,7 @@ compatible with other Home Assistant features, but this documentation is availab
for existing users.
</div>
The integration supports additional configuration from a file `google_calendars.yaml` which is avaialble for existing users before version `2022.06`. This file is no longer automatically populated.
The integration supports additional configuration from a file `google_calendars.yaml` which is available for existing users before version `2022.06`. This file is no longer automatically populated.
{% configuration %}
cal_id:

1
source/_integrations/google_assistant.markdown
View File

@ -115,7 +115,6 @@ Google Assistant devices can send their commands locally to Home Assistant allow
Your Home Assistant instance needs to be connected to the same network as the Google Assistant device that you’re talking to so that it can be discovered via mDNS discovery (UDP broadcasts).
Your Google Assistant devices will still communicate via the internet to:
- Sync entities.
- Get credentials to establish a local connection.
- Send commands that involve a [secure device](#secure-device).
- Send commands if local fulfillment fails.

18
source/_integrations/google_pubsub.markdown
View File

@ -104,23 +104,7 @@ google_pubsub:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}
### Saving the data using a Google Cloud Function

12
source/_integrations/history.markdown
View File

@ -147,17 +147,7 @@ history:
- light.front_porch
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes - include specified entities and exclude specified entities from the remaining.
The following characters can be used in entity globs:
`*` - The asterisk represents zero, one, or multiple characters
`.` - The period represents a single character
{% include common-tasks/filters.md %}
#### Implementation details

23
source/_integrations/home_connect.markdown
View File

@ -56,25 +56,6 @@ Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://hom
{% enddetails %}
Next, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
home_connect:
client_id: CLIENT_ID
client_secret: CLIENT_SECRET
```
{% configuration %}
client_id:
description: Your Home Connect client ID.
required: true
type: string
client_secret:
description: Your Home Connect client secret.
required: true
type: string
{% endconfiguration %}
{% include integrations/config_flow.md %}
The integration configuration will ask for the *Client ID* and *Client Secret* created above. See [Application Credentials](/integrations/application_credentials) for more details.

18
source/_integrations/homekit.markdown
View File

@ -356,23 +356,7 @@ homekit:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}
Categorized entities are not included (config, diagnostic, and system entities) unless they are explicitly matched by `include_entity_globs` or `include_entities` or selected in the UI in include mode.

2
source/_integrations/http.markdown
View File

@ -2,9 +2,7 @@
title: HTTP
description: Offers a web framework to serve files.
ha_category:
- Binary Sensor
- Other
- Sensor
ha_release: pre 0.7
ha_iot_class: Local Push
ha_quality_scale: internal

18
source/_integrations/influxdb.markdown
View File

@ -229,23 +229,7 @@ influxdb:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}
## Examples

12
source/_integrations/logbook.markdown
View File

@ -83,17 +83,7 @@ logbook:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes - include specified entities and exclude specified entities from the remaining.
The following characters can be used in entity globs:
- `*` - The asterisk represents zero, one, or multiple characters
- `.` - The period represents a single character
{% include common-tasks/filters.md %}
### Common filtering examples

13
source/_integrations/lyric.markdown
View File

@ -42,21 +42,12 @@ Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://hom
{% enddetails %}
Once your app is created, copy the `Consumer Key` and `Consumer Secret`. These will be your `client_id` and `client_secret` to add to your `configuration.yaml`:
```yaml
# Example configuration.yaml entry
lyric:
client_id: MY_CONSUMER_KEY
client_secret: MY_CONSUMER_SECRET
```
You should now restart the server.
You can then add the integration in the frontend via the steps below.
{% include integrations/config_flow.md %}
The integration configuration will ask for the *Client ID* and *Client Secret* created above. See [Application Credentials](/integrations/application_credentials) for more details.
## Sensors
This integration provides the following sensors:

18
source/_integrations/mqtt_statestream.markdown
View File

@ -93,23 +93,7 @@ mqtt_statestream:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}
### Common filtering examples

26
source/_integrations/neato.markdown
View File

@ -32,7 +32,7 @@ There is support for the following platform types within Home Assistant:
## Prerequisites
1. Visit [the Neato Developer Network](https://developers.neatorobotics.com/applications) and create a new app.
Visit [the Neato Developer Network](https://developers.neatorobotics.com/applications) and create a new app.
<div class='note'>
@ -60,30 +60,10 @@ instance does not need to be exposed to the Internet.
{% enddetails %}
2. Add the newly created `client_id` and `client_secret` to your configuration.yaml:
```yaml
# Example configuration.yaml entry
neato:
client_id: YOUR_CLIENT_ID
client_secret: YOUR_CLIENT_SECRET
```
3. Restart Home Assistant
{% configuration %}
client_id:
description: Client ID for the Neato account.
required: true
type: string
client_secret:
description: Client Secret for the Neato account.
required: true
type: string
{% endconfiguration %}
{% include integrations/config_flow.md %}
The integration configuration will ask for the *Client ID* and *Client Secret* created above. See [Application Credentials](/integrations/application_credentials) for more details.
<div class='note'>
After the update to firmware 4.0 (which adds cleaning maps) there is also support for displaying the maps of the Botvac D3 Connected and Botvac D5 Connected robots. More information on how to update can be found [here](https://support.neatorobotics.com/hc/en-us/articles/115004320694-Software-Update-4-0-for-Neato-Botvac-Connected-D3-D5-).

2
source/_integrations/octoprint.markdown
View File

@ -56,7 +56,7 @@ verify ssl:
{% endconfiguration_basic %}
### API Key
For the integration to work, please check that the plugin Discovery is enabled.
For the integration to work, please check that in Octoprint, the plugin Discovery is enabled and in the settings -> printer notifications menu pop-ups are enabled.
The Octoprint integration will attempt to register itself via the [application keys plugin](https://docs.octoprint.org/en/master/bundledplugins/appkeys.html). After submitting the configuration UI in Home Assistant, open the Octoprint UI and click allow on the prompt.
## Binary Sensor

12
source/_integrations/plex.markdown
View File

@ -325,14 +325,14 @@ The search will attempt to guess the type of media based on the search parameter
### Compatibility
| Client | Limitations |
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Any (when all controls disabled) | A stop button will appear but is not functional. |
| Any (when casting) | Controlling playback will work but with error logging. |
| Any (remote client) | Controls disabled. |
| --- | --- |
| Remote clients | Controls are unavailable |
| Apple TV | None |
| iOS | None |
| NVidia Shield | Controlling playback when the Shield is both a client and a server will work but with error logging |
| Plex Web | None |
| NVidia Shield | None |
| Plexamp | None (music playback only) |
| Plex Desktop & Web | Controls are unavailable (as of June 2022) |
| Plex HTPC | None |
## Sonos Playback

18
source/_integrations/prometheus.markdown
View File

@ -112,23 +112,7 @@ prometheus:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}
## Full Example

18
source/_integrations/recorder.markdown
View File

@ -137,23 +137,7 @@ recorder:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}
If you only want to hide events from your history, take a look at the [`history` integration](/integrations/history/). The same goes for the [logbook](/integrations/logbook/). But if you have privacy concerns about certain events or want them in neither the history or logbook, you should use the `exclude`/`include` options of the `recorder` integration. That way they aren't even in your database, you can reduce storage and keep the database small by excluding certain often-logged events (like `sensor.last_boot`).

34
source/_integrations/siren.mqtt.markdown
View File

@ -87,15 +87,16 @@ available_tones:
required: false
type: list
command_template:
description: Defines a [template](/docs/configuration/templating/#processing-incoming-data) to generate the payload to send to `command_topic`. The variable `value` will be assigned with the configured `payload_on` or `payload_off` setting. The siren turn on service parameters `tone`, `volume_level` or `duration` can be used as variables in the template. When operation in optimistic mode the corresponding state attributes will be set. Turn parameters will be filtered if a device misses the support.
description: Defines a [template](/docs/configuration/templating/#processing-incoming-data) to generate a custom payload to send to `command_topic`. The variable `value` will be assigned with the configured `payload_on` or `payload_off` setting. The siren turn on service parameters `tone`, `volume_level` or `duration` can be used as variables in the template. When operation in optimistic mode the corresponding state attributes will be set. Turn on parameters will be filtered if a device misses the support.
required: false
type: template
command_off_template:
description: Defines a [template](/docs/configuration/templating/#processing-incoming-data) to generate the payload to send to `command_topic` when the siren turn off service is called. By default `command_template` will be used as template for service turn off. The variable `value` will be assigned with the configured `payload_off` setting.
description: Defines a [template](/docs/configuration/templating/#processing-incoming-data) to generate a custom payload to send to `command_topic` when the siren turn off service is called. By default `command_template` will be used as template for service turn off. The variable `value` will be assigned with the configured `payload_off` setting.
required: false
type: template
command_topic:
description: The MQTT topic to publish commands to change the siren state. Without command template a JSON payload is published. When the siren turn on service is called, the startup parameters will be added to the JSON payload. The `state` value of the JSON payload will be set to the the `payload_on` or `payload_off` configured payload.
description: >
The MQTT topic to publish commands to change the siren state. Without command templates, a default JSON payload like `{"state":"ON", "tone": "bell", "duration": 10, "volume_level": 0.5 }` is published. When the siren turn on service is called, the startup parameters will be added to the JSON payload. The `state` value of the JSON payload will be set to the the `payload_on` or `payload_off` configured payload.
required: false
type: string
device:
@ -221,7 +222,7 @@ state_on:
type: string
default: "`payload_on` if defined, else `'ON'`"
state_topic:
description: "The MQTT topic subscribed to receive state updates. When a JSON payload is detected, the `state` value of the JSON payload should supply the `payload_on` or `payload_off` defined payload to turn the siren on or off. Additional the state attributes `duration`, `tone` and `volume_level` can be updated. Use `value_template` to update render custom payload to a compliant JSON payload. Attributes will only be set if the function is supported by the device and a valid value is supplied. The initial state will be `unknown`. The state will be reset to `unknown` if a `None` payload or `null` JSON value is received as a state update."
description: "The MQTT topic subscribed to receive state updates. The state update may be either JSON or a simple string. When a JSON payload is detected, the `state` value of the JSON payload should supply the `payload_on` or `payload_off` defined payload to turn the siren on or off. Additionally, the state attributes `duration`, `tone` and `volume_level` can be updated. Use `value_template` to transform the received state udpate to a compliant JSON payload. Attributes will only be set if the function is supported by the device and a valid value is supplied. When a non JSON payload is detected, it should be either of the `payload_on` or `payload_off` defined payloads or `None` to reset the siren's state to `unknown`. The initial state will be `unknown`. The state will be reset to `unknown` if a `None` payload or `null` JSON value is received as a state update."
required: false
type: string
state_value_template:
@ -284,6 +285,31 @@ mqtt:
{% endraw %}
### On/Off only siren controlling a Tasmota relay
The example below shows a configuration for an On/Off type siren, which does not accept JSON commands.
{% raw %}
```yaml
# Example configuration.yaml entry
mqtt:
siren:
- unique_id: tasmota_siren
name: "garage"
state_topic: "stat/SIREN/RESULT"
command_topic: "cmnd/SIREN/POWER"
availability_topic: "tele/SIREN/LWT"
command_template: "{{ value }}"
state_value_template: "{{ value_json.POWER }}"
payload_on: "ON"
payload_off: "OFF"
payload_available: "Online"
payload_not_available: "Offline"
```
{% endraw %}
For a check, you can use the command line tools `mosquitto_pub` shipped with `mosquitto` to send MQTT messages. This allows you to operate your siren manually:
```bash

18
source/_integrations/splunk.markdown
View File

@ -102,20 +102,4 @@ splunk:
- light.kitchen_light
```
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}

12
source/_integrations/steam_online.markdown
View File

@ -18,6 +18,18 @@ The Steam integration will allow you to track the online status of public [Steam
{% include integrations/config_flow.md %}
<div class='note'>
Steam has a friends list privacy feature that interferes with easily adding sensors to track friends' activities. Setting the friends list to Public during initial setup will allow the integration to see them for easy adding. It is **not** necessary to keep the friends list Public.
Go to your profile, select "Edit Profile", "Privacy Settings".
</div>
<p class='img'>
<img src='/images/screenshots/steam_privacy_settings.png' />
</p>
## Setup
You need a [free API key](https://steamcommunity.com/dev/apikey) to use the platform.

6
source/_integrations/synology_dsm.markdown
View File

@ -39,6 +39,12 @@ Having cameras or the Home mode toggle from [Surveillance Station](https://www.s
</div>
<div class='note'>
If you have two or more NICs with different IP addresses from the same subnet and SSDP is activated, this leads to problems with this integration, as the NAS is detected several times with different IPs and the integration always adopts the new "detected" IP address in its configuration and then reloads it.
In this case, it is recommended to use NIC bonding instead or to deactivate SSDP.
</div>
## Separate User Configuration

4
source/_integrations/tag.markdown
View File

@ -96,11 +96,11 @@ NFC tags come in many different shapes and formats. [NFC Stickers](https://amzn.
To get started with printing cards, you need the following hardware:
- [Inkjet Printer](https://amzn.to/3khMrts)
- [Canon TS702a Inkjet Printer](https://www.amazon.com/TS702a-Compact-Connected-Inkjet-Printer/dp/B09TG8F4YS/)
- [Compatible card printing tray](https://amzn.to/3hq59x2)
- [Printable NFC cards](https://amzn.to/3iqHpKx)
The seller of above tray + cards also made a [layout tool](https://brainstormidsupply.com/id-card-printing-layout-tool.html/) available to prepare printable PDFs. It runs fully in your browser and no data is sent to their server. If you've used above equipment, pick Canon MP tray as what you're printing on.
The seller of above tray + cards also made an [ID card printing app](https://brainstormidsupply.com/try-id-maker/) available to prepare printable PDFs. It runs fully in your browser and no data is sent to their server. If you've used above equipment, pick Canon MP tray as what you're printing on.
Happy printing!

4
source/_integrations/tank_utility.markdown
View File

@ -63,7 +63,7 @@ sensor:
email: YOUR_EMAIL_ADDRESS
password: YOUR_PASSWORD
devices:
- 000000000000000000000000
- "000000000000000000000000"
```
{% configuration %}
@ -75,7 +75,7 @@ password:
description: "Your [https://app.tankutility.com](https://app.tankutility.com) password."
required: true
type: string
unit_of_measurement:
devices:
description: All devices to monitor.
required: true
type: map

2
source/_integrations/unifi_direct.markdown
View File

@ -11,7 +11,7 @@ ha_platforms:
ha_integration_type: integration
---
This platform allows you to detect presence by looking at devices connected to a [UniFi AP](https://www.ui.com/products/#unifi). This device tracker differs form [Ubiquiti UniFi](/integrations/unifi) because it doesn't require the UniFi controller software.
This platform allows you to detect presence by looking at devices connected to a [UniFi AP](https://www.ui.com/products/#unifi). This device tracker differs from [Ubiquiti UniFi](/integrations/unifi) because it doesn't require the UniFi controller software.
To use this device tracker in your installation, add the following to your `configuration.yaml` file:

4
source/_integrations/venstar.markdown
View File

@ -26,8 +26,10 @@ Currently supported and tested thermostats:
- ColorTouch T7900
- ColorTouch T7850 (No Humidity control)
- Explorer Mini T2000
- Explorer IAQ T3950
Currently supported functionality:
- Setting heat/cool temperature when the thermostat is in the appropriate mode.
- Changing the operation mode of the thermostat (heat/cool/off/auto)
- Turning the fan on/off
@ -36,8 +38,10 @@ Currently supported functionality:
- Turning on hold mode preset
- Remote temperature sensors
- Thermostat alerts (Filter replacement/etc)
- Reading IAQ and CO2 levels (on supported devices, e.g. T3950, only)
The following values are supported for the preset_mode state attribute:
- `none`: *Enables* the scheduling functionality.
- `temperature`: *Disables* the schedule and holds the set temperature indefinitely.
- `away`: Places the thermostat in away mode

2
source/_integrations/waze_travel_time.markdown
View File

@ -27,7 +27,7 @@ Notes:
## Manual Polling
Some users will want to have more control over polling frequencies. To use more granular polling, disable automated polling in your config entry's System Options. To manually trigger a polling request, call the [`homeassistant.update_entity` service](/integrations/homeassistant/#service-homeassistantupdate_entity) as needed, either manually or via automations.
Some users want more control over polling intervals. To use more granular polling, you can disable automated polling from the entry on the Integration page. Go to the Integrtaion page, select the entry, click on the vertical 3 dots, and then select System Options to turn off or on polling. Afterwards to manually trigger a polling request, call the [`homeassistant.update_entity` service](/integrations/homeassistant/#service-homeassistantupdate_entity) as needed, either manually or via automations.
## Example using dynamic destination

40
source/_integrations/withings.markdown
View File

@ -18,11 +18,7 @@ ha_integration_type: integration
The `withings` sensor platform consumes data from various health products produced by [Withings](https://www.withings.com).
## Setup
For simplicity, these instructions assume your installation uses Home Assistant Cloud.
### Step 1 - Create a Withings Account
## Create a Withings Account
You must have a developer account to distribute the data. [Create a free development account](https://account.withings.com/partner/add_oauth2).
@ -54,26 +50,14 @@ Withings will validate (with HTTP HEAD) these requirements each time you save yo
{% enddetails %}
### Step 2 - Configure Home Assistant
{% include integrations/config_flow.md %}
- Add the Withings configuration YAML.
```yaml
# Example configuration.yaml entry
withings:
client_id: CLIENT_ID
client_secret: CONSUMER_SECRET
```
- Confirm your YAML configuration is valid by using the `Check Config` tool (see note).
- Note: In order for "Check Configuration" to be visible, you must enable "Advanced Mode" on your user profile. The "Check Configuration" tool can be found by clicking "Configuration" from the sidebar (cog icon) and then clicking "Server Control".
- Restart Home Assistant.
The integration configuration will ask for the *Client ID* and *Client Secret* created above. See [Application Credentials](/integrations/application_credentials) for more details.
### Step 3 - Authorize Home Assistant
- Add the Withings integration.
- Once authorized, the tab/window will close and the integration page will prompt to select a profile. Select the profile you chose while on the Withings site.
Once authorized, the tab/window will close and the integration page will prompt to select a profile. Select the profile you chose while on the Withings site.
- Note: It's important you select the same profile from the previous step. Choosing a different one will result in Home Assistant displaying the wrong data.
- Data will synchronize immediately and update under the following conditions:
Data will synchronize immediately and update under the following conditions:
- If `use_webhook` is enabled:
- Each time Withings notifies Home Assistant of a data change.
- Every 120 minutes.
@ -82,23 +66,15 @@ Withings will validate (with HTTP HEAD) these requirements each time you save yo
## Configuration
There are additional configuration options available:
```yaml
# Example configuration.yaml entry
withings:
client_id: CLIENT_ID
client_secret: CONSUMER_SECRET
use_webhook: true
```
{% configuration %}
client_id:
description: The OAuth client id (get from https://account.withings.com/partner/add_oauth2)
required: true
type: string
client_secret:
description: The OAuth secret (get from https://account.withings.com/partner/add_oauth2)
required: true
type: string
use_webhook:
description: "Configure Withings to notify Home Assistant when data changes. This also required to populate the in_bed sensor. Note: In order for this to work, your Home Assistant install must be accessible to the internet."
required: false

18
source/_integrations/zabbix.markdown
View File

@ -134,23 +134,7 @@ zabbix:
{% endraw %}
Filters are applied as follows:
1. No includes or excludes - pass all entities
2. Includes, no excludes - only include specified entities
3. Excludes, no includes - only exclude specified entities
4. Both includes and excludes:
- Include domain and/or glob patterns specified
- If domain is included, and entity not excluded or match exclude glob pattern, pass
- If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- If domain is not included, glob pattern does not match, and entity not included, fail
- Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- If domain is excluded and entity not included, fail
- If entity matches exclude glob pattern and entity not included, fail
- If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- Neither include or exclude specifies domains or glob patterns
- If entity is included, pass (as #2 above)
- If entity include and exclude, the entity exclude is ignored
{% include common-tasks/filters.md %}
## Sensor

12
source/_integrations/zha.markdown
View File

@ -79,14 +79,14 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl
- dresden elektronik deCONZ based Zigbee radios (via the [zigpy-deconz](https://github.com/zigpy/zigpy-deconz) library for zigpy)
- [ConBee II (a.k.a. ConBee 2) USB adapter from dresden elektronik](https://phoscon.de/conbee2)
- [ConBee USB adapter from dresden elektronik](https://phoscon.de/conbee)
- [RaspBee II (a.k.a. RaspBee 2) Raspberry Pi Shield from dresden elektronik](https://www.dresden-elektronik.com/product/raspbee-II.html)
- [RaspBee II (a.k.a. RaspBee 2) Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee2)
- [RaspBee Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee)
- Silicon Labs EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy)
- [ITead Zigbee 3.0 USB Dongle (EFR32MG21) Model 9888010100045](https://www.itead.cc/zigbee-3-0-usb-dongle.html)
- [ITead Sonoff ZBBridge](https://www.itead.cc/smart-home/sonoff-zbbridge.html) (Note! [WiFi-based bridges are not recommended for ZHA with EZSP radios](https://github.com/home-assistant/home-assistant.io/issues/17170). Also, this first have to be flashed with [Tasmota firmware and Silabs EmberZNet NCP EZSP UART Host firmware to use as Serial-to-IP adapter](https://www.digiblur.com/2020/07/how-to-use-sonoff-zigbee-bridge-with.html))
- [ITead Zigbee 3.0 USB Dongle (EFR32MG21) Model 9888010100045](https://itead.cc/product/zigbee-3-0-usb-dongle/)
- [ITead Sonoff ZBBridge](https://itead.cc/product/sonoff-zbbridge/) (Note! [WiFi-based bridges are not recommended for ZHA with EZSP radios](https://github.com/home-assistant/home-assistant.io/issues/17170). Also, this first have to be flashed with [Tasmota firmware and Silabs EmberZNet NCP EZSP UART Host firmware to use as Serial-to-IP adapter](https://www.digiblur.com/2020/07/how-to-use-sonoff-zigbee-bridge-with.html))
- [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee Ember 3581 USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/walthowd/husbzb-firmware))
- [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs_usb_adapter.html)/[POPP ZB-Stick](https://shop.zwave.eu/detail/index/sArticle/2496) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility))
- [Elelabs Zigbee Raspberry Pi Shield](https://elelabs.com/products/elelabs_zigbee_shield.html) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility))
- [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs-usb-adapter.html)/[POPP ZB-Stick](https://shop.zwave.eu/detail/index/sArticle/2496) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility))
- [Elelabs Zigbee Raspberry Pi Shield](https://elelabs.com/products/elelabs-zigbee-shield.html) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility))
- [Bitron Video/Smabit BV AV2010/10 USB-Stick](https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/) with Silicon Labs Ember 3587
- Telegesis ETRX357USB/ETRX357USB-LR/ETRX357USB-LRS+8M (Note! These first have to be [flashed with other EmberZNet firmware](https://github.com/walthowd/husbzb-firmware))
- Texas Instruments based radios (via the [zigpy-znp](https://github.com/zigpy/zigpy-znp) library for zigpy)
@ -173,7 +173,7 @@ Some devices can be auto-discovered, which can simplify the ZHA setup process. T
| -------| ---------------- | ---------- |
| [ITead SONOFF Zigbee 3.0 USB Dongle Plus](https://itead.cc/product/sonoff-zigbee-3-0-usb-dongle-plus/) | USB | 10C4:EA60 |
| [Bitron Video/SMaBiT BV AV2010/10](https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/) | USB | 10C4:8B34 |
| [ConBee II](https://phoscon.de/en/conbee2) | USB | 1CF1:0030 |
| [ConBee II](https://phoscon.de/conbee2) | USB | 1CF1:0030 |
| [Nortek HUSBZB-1](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) | USB | 10C4:8A2A |
| [slae.sh CC2652RB development stick](https://slae.sh/projects/cc2652/) | USB | 10C4:EA60 |
| [ZigStar Stick (CC2652 + CH340B variant)](https://zig-star.com/projects/zigbee-stick-v4/) | USB | 1A86:7523 |

2
source/_integrations/zone.markdown
View File

@ -12,7 +12,7 @@ ha_domain: zone
ha_integration_type: integration
---
Zones allow you to specify certain regions on earth (for now). When a device tracker sees a device to be within a zone, the state will take the name from the zone. Zones can also be used as a [trigger](/getting-started/automation-trigger/#zone-trigger) or [condition](/getting-started/automation-condition/#zone-condition) inside automation setups.
Zones allow you to specify certain regions on earth (for now). When a device tracker sees a device to be within a zone, the state will take the name from the zone. Zones can also be used as a [trigger](/docs/automation/trigger#zone-trigger) or [condition](/docs/scripts/conditions/#zone-condition) inside automation setups.
Zones can be added and managed through the user interface at **{% my zones title="Settings -> Areas & Zones" %}**.

6
source/_posts/2016-07-19-visualizing-your-iot-data.markdown
View File

@ -19,9 +19,9 @@ This blog post will show you ways to export data for reporting, visualization, o
In this blog post I use the temperature of the [Aare](https://en.wikipedia.org/wiki/Aare) river close to where I live as a show case. The temperatures were recorded with the [Swiss Hydrological Data sensor](/integrations/swiss_hydrological_data) and the name of the sensor is `sensor.aare`.
The database is stored at `<path to config dir>/.homeassistant/home-assistant_v2.db` as [SQLite database](https://www.sqlite.org/). In all examples we are going to use the path: `/home/ha/.homeassistant/home-assistant_v2.db`
The database is stored at `<path to config dir>/.homeassistant/home-assistant_v2.db` as [SQLite database](https://www.sqlite.org/index.html). In all examples we are going to use the path: `/home/ha/.homeassistant/home-assistant_v2.db`
If you are just curious what's stored in your database then you can use the `sqlite3` command-line tool or a graphical one like [DB Browser for SQLite](http://sqlitebrowser.org/).
If you are just curious what's stored in your database then you can use the `sqlite3` command-line tool or a graphical one like [DB Browser for SQLite](https://sqlitebrowser.org/).
The table that is holding the states is called `states`. The `events` tables is responsible for storing the events which occurred. So, we will first check how many entries there are in the `states` table. `sqlite3` needs to know where the databases is located. To work with your database make sure that Home Assistant is not running or create a copy of the existing database. It's recommended to work with a copy.
@ -72,7 +72,7 @@ After the import a graph can be created over the existing data.
Graph in LibreOffice
</p>
You can also use [matplotlib](http://matplotlib.org/) to generate graphs as an alternative to a spreadsheet application. This is a powerful Python 2D plotting library. With the built-in support for SQLite in Python it will only take a couple lines of code to visualize your data.
You can also use [matplotlib](https://matplotlib.org/) to generate graphs as an alternative to a spreadsheet application. This is a powerful Python 2D plotting library. With the built-in support for SQLite in Python it will only take a couple lines of code to visualize your data.
```python
import sqlite3

8
source/_posts/2016-07-23-internet-of-things-data-exploration-with-jupyter-notebooks.markdown
View File

@ -26,11 +26,11 @@ One of the graphs created with this tutorial.
_TL; DR: Use [this Jupyter Notebook][nb-prev] to visualize of your data_
[blog post by Fabian]: /blog/2016/07/19/visualizing-your-iot-data/
[DB Browser for SQLite]: http://sqlitebrowser.org/
[Pandas]: http://pandas.pydata.org/
[matplotlib]: http://matplotlib.org/
[DB Browser for SQLite]: https://sqlitebrowser.org/
[Pandas]: https://pandas.pydata.org/
[matplotlib]: https://matplotlib.org/
[Jupyter notebook]: https://jupyter.org/
[nb-prev]: https://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/other/DataExploration-1/DataExploration-1.ipynb
[nb-prev]: https://nbviewer.org/github/home-assistant/home-assistant-notebooks/blob/master/other/DataExploration-1/DataExploration-1.ipynb
<!--more-->

2
source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown
View File

@ -114,7 +114,7 @@ If you reboot, you should see your current IP address in the terminal.
>>> Network configuration: ('192.168.0.10', '255.255.255.0', '192.168.0.1', '192.168.0.1')
```
First let's create a little consumer for Home Assistant sensor's state. The code to place in `main.py` is a mixture of code from above and the [RESTful API](/developers/rest_api/) of Home Assistant. If the temperature in the kitchen is higher than 20 °C then the LED connected to pin 5 is switched on.
First let's create a little consumer for Home Assistant sensor's state. The code to place in `main.py` is a mixture of code from above and the [RESTful API](https://developers.home-assistant.io/docs/api/rest/) of Home Assistant. If the temperature in the kitchen is higher than 20 °C then the LED connected to pin 5 is switched on.
<div class='note'>

2
source/_posts/2016-08-19-github-style-calendar-heatmap-of-device-data.markdown
View File

@ -19,4 +19,4 @@ Heatmap
[heatmap]: https://en.wikipedia.org/wiki/Heat_map
[Jupyter notebook]: https://jupyter.org/
[nb-prev]: https://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/other/DataExploration-2/DataExploration-2.ipynb
[nb-prev]: https://nbviewer.org/github/home-assistant/home-assistant-notebooks/blob/master/other/DataExploration-2/DataExploration-2.ipynb

2
source/_posts/2016-08-31-esp8266-and-micropython-part2.markdown
View File

@ -21,7 +21,7 @@ An example for pulling is [aREST](/integrations/arest#sensor). This is a great w
## MQTT
You can find a simple examples for publishing and subscribing with MQTT in the [MicroPython](https://github.com/micropython/micropython-lib) library overview in the section for [umqtt](https://github.com/micropython/micropython-lib/tree/master/umqtt.simple).
You can find a simple examples for publishing and subscribing with MQTT in the [MicroPython](https://github.com/micropython/micropython-lib) library overview in the section for [umqtt](https://github.com/micropython/micropython-lib/tree/master/micropython/umqtt.simple).
The example below is adopted from the work of [@davea](https://github.com/davea) as we don't want to re-invent the wheel. The configuration feature is crafty and simplyfies the code with the usage of a file called `/config.json` which stores the configuration details. The ESP8266 device will send the value of a pin every 5 seconds.

2
source/_posts/2017-11-29-hassio-virtual-machine.markdown
View File

@ -10,7 +10,7 @@ og_image: /images/blog/2017-11-hassio-virtual/social.png
---
The images for the Raspberry Pi family and the Intel NUC are an easy way to get started with [Hass.io](/hassio/). For a test or if you have a system which is already hosting virtual machines then the [**Hass.io installer**](/hassio/installation/#alternative-install-on-generic-linux-server) is an option to use Hass.io in a virtualized environment. In this guide the host is a Fedora 27 system with [libvirt](https://libvirt.org/) support and the guest will be running Debian 9. Hass.io will be installed on the guest.
The images for the Raspberry Pi family and the Intel NUC are an easy way to get started with [Hass.io](/getting-started). For a test or if you have a system which is already hosting virtual machines then the [**Hass.io installer**](/installation/) is an option to use Hass.io in a virtualized environment. In this guide the host is a Fedora 27 system with [libvirt](https://libvirt.org/) support and the guest will be running Debian 9. Hass.io will be installed on the guest.
<!--more-->

14
source/_posts/2018-06-04-esphomelib.markdown
View File

@ -9,17 +9,17 @@ categories: How-To ESP8266
og_image: /images/blog/2018-06-esphomelib/social.png
---
The [ESP8266](https://www.espressif.com/en/products/hardware/esp8266ex/overview) and [ESP32](https://www.espressif.com/en/products/hardware/esp32/overview) are dirt cheap WiFi-enabled microcontrollers that have established themselves as the base for many DIY home automation projects. Even quite a few manufacturers like iTead with their Sonoff devices have chosen these controllers because of their competitive price.
The [ESP8266](https://www.espressif.com/products/socs/esp8266) and [ESP32](https://www.espressif.com/products/socs/esp32) are dirt cheap WiFi-enabled microcontrollers that have established themselves as the base for many DIY home automation projects. Even quite a few manufacturers like iTead with their Sonoff devices have chosen these controllers because of their competitive price.
Setting up these microcontrollers for some basic functionality has also gotten really easy over the years with popular projects like ESPEasy or Sonoff-Tasmota: You just download their firmware and flash it onto your chip. But if you’ve ever tried to go a bit beyond the basic set of functions of those frameworks and tried to do some customization, you will have probably noticed that it’s not that easy. Often times you’ll end up having to download some Arduino code project from the internet and customizing it to your needs.
This is where esphomelib comes in: The [esphomelib suite](https://esphomelib.com/esphomeyaml/index.html) is a set of tools that are designed with the goal of achieving the best possible user experience. esphomelib a) allows for lots of customization without touching *a single line* of code and b) has complete Home Assistant integration. Inside the esphomelib ecosystem, you essentially just have to write a simple YAML configuration file. The rest like compiling, flashing, uploading etc. will then be taken care of automatically.
This is where esphomelib comes in: The [esphomelib suite](https://esphome.io/) is a set of tools that are designed with the goal of achieving the best possible user experience. esphomelib a) allows for lots of customization without touching *a single line* of code and b) has complete Home Assistant integration. Inside the esphomelib ecosystem, you essentially just have to write a simple YAML configuration file. The rest like compiling, flashing, uploading etc. will then be taken care of automatically.
<!--more-->
## Installation
An example probably illustrates this the best. To use esphomeyaml, there are two main ways: From a [HassIO add-on](https://esphomelib.com/esphomeyaml/guides/getting_started_hassio.html), or from the [command line](https://esphomelib.com/esphomeyaml/guides/getting_started_command_line.html). For the esphomeyaml add-on, you just have to add "[https://github.com/ottowinter/esphomeyaml](https://github.com/ottowinter/esphomeyaml)" as an add-on repository (see [Installing third party add-ons](/hassio/installing_third_party_addons/)). Then select and install “esphomeyaml” and wait for the installation to complete. After that, you will be able to start the add-on and view the web interface.
An example probably illustrates this the best. To use esphomeyaml, there are two main ways: From a [HassIO add-on](https://esphome.io/guides/getting_started_hassio.html), or from the [command line](https://esphome.io/guides/getting_started_command_line.html). For the esphomeyaml add-on, you just have to add "[https://github.com/esphome/esphome](https://github.com/esphome/esphome)" as an add-on repository (see [Installing third party add-ons](/hassio/installing_third_party_addons/)). Then select and install “esphomeyaml” and wait for the installation to complete. After that, you will be able to start the add-on and view the web interface.
From the command line you just need to install the **Python 2** package using the pip command seen below. Then visit `localhost:6052` to view the dashboard.
@ -77,11 +77,11 @@ If you now press upload again (this time the ESP doesn't need to be connected vi
discovery</a> is enabled and a <a href='/integrations/group/'>default view</a> is used.
</p>
Granted, this functionality would have been pretty simple with other projects too. But once you start adding [lights](https://esphomelib.com/esphomeyaml/index.html#light-components), [covers](https://esphomelib.com/esphomeyaml/index.html#cover-components) and [other sensors](https://esphomelib.com/esphomeyaml/index.html#sensor-components), esphomelib’s modular design really starts to shine.
Granted, this functionality would have been pretty simple with other projects too. But once you start adding [lights](https://esphome.io/index.html#light-components), [covers](https://esphome.io/index.html#cover-components) and [other sensors](https://esphome.io/index.html#sensor-components), esphomelib’s modular design really starts to shine.
## See Also
- [View the full getting started guide (including how to migrate from other projects)](https://esphomelib.com/esphomeyaml/index.html#guides)
- [Device-specific setup guides](https://esphomelib.com/esphomeyaml/index.html#devices)
- [List of supported sensors/actuators](https://esphomelib.com/esphomeyaml/index.html)
- [View the full getting started guide (including how to migrate from other projects)](https://esphome.io/guides/)
- [Device-specific setup guides](https://esphome.io/#devices)
- [List of supported sensors/actuators](https://esphome.io/)
- Join the [discord server](https://discord.gg/KhAMKrd) if you need help.

2
source/_posts/2021-01-23-security-disclosure2.markdown
View File

@ -26,7 +26,7 @@ TL;DR:
- Upgrade the custom integrations to a fixed version or remove them from your installation.
- If you have used any of the custom integrations with a known vulnerability, we recommend that you update your credentials.
On the morning of Saturday, January 23 2021, the Home Assistant project was informed by [security researcher Nathan Brady](https://twitter.com/NateBrady23) about a security vulnerability. It provided more insight on the implementation of the fixes done for the [previous security vulnerability](/blog/2021/01/22/security-disclosure/). We learned that not all custom integrations that implement security patches are sufficient to deflect the problem.
On the morning of Saturday, January 23 2021, the Home Assistant project was informed by security researcher Nathan Brady about a security vulnerability. It provided more insight on the implementation of the fixes done for the [previous security vulnerability](/blog/2021/01/22/security-disclosure/). We learned that not all custom integrations that implement security patches are sufficient to deflect the problem.
We verified all fixes made to custom integrations that were found to be vulnerable in the previous security disclosure. The conclusion is that some custom integrations are still vulnerable to a directory traversal attack while not being authenticated with Home Assistant. It allows an attacker to access any file without having to log in. This access includes any credentials that you might have stored to allow Home Assistant to access other services.

4
source/_posts/2021-05-12-integrations-api.markdown
View File

@ -9,7 +9,7 @@ categories: Public-Service-Announcement
og_image: /images/blog/2021-05-integrations-api/social.png
---
Home Assistant is the world’s largest home automation platform talking with [over 1700 different devices and services](/integrations/). Home Assistant works with these via “integrations”.
Home Assistant is the world’s largest home automation platform talking with [over 1900 different devices and services](/integrations/). Home Assistant works with these via “integrations”.
Each integration runs inside Home Assistant. They convert the data from the device into data that Home Assistant understands and forward commands from Home Assistant back to the device. For this to work a device or service needs to have an application programming interface (API).
@ -25,4 +25,4 @@ This stance will hurt us in the short term because we get less integrations. It
In the long term the user will win. Devices with local APIs will still work 10 years from now and no one will be held hostage by vendor lock-in because some of their devices only work with Home Assistant.
_Note about Home Assistant APIs: Home Assistant does have [an API](https://developers.home-assistant.io/docs/api/websocket), just not for integrations. It allows you to access all your data in real-time. We also have a [data science portal](https://data.home-assistant.io/) that documents how you can query the historical data stored on disk._
_Note about Home Assistant APIs: Home Assistant does have [an API](https://developers.home-assistant.io/docs/api/websocket/), just not for integrations. It allows you to access all your data in real-time. We also have a [data science portal](https://data.home-assistant.io/) that documents how you can query the historical data stored on disk._

4
source/_posts/2022-05-29-matter-in-home-assistant-workshop-announcement.markdown
View File

@ -28,9 +28,9 @@ The workshop will contain two parts. In the first part we will talk about what M
The workshop will be free but you will need a couple of things if you want to be able to follow along with the second part:
- Home Assistant OS 8.0 or newer (Matter relies on an add-on and Bluetooth)
- Home Assistant OS 8.0 or newer, 64-bit version only (x86-64 or aarch64). Matter relies on an add-on and Bluetooth.
- [Home Assistant Community Store](https://hacs.xyz/) installed
- Espressif ESP32-C3-DevKitM-1 ($9 @ [Mouser](https://www.mouser.com/ProductDetail/356-ESP32-C3DEVKITM1), €17 @ [Conrad](https://www.conrad.de/de/p/espressif-entwicklungsboard-esp32-c3-devkitm-1-2490158.html)) or M5Stamp C3 ($6 @ [M5Stack](https://twitter.com/home_assistant/status/1531712479016890369))
- Espressif ESP32-C3-DevKitM-1 ($9 @ [Mouser](https://www.mouser.com/ProductDetail/356-ESP32-C3DEVKITM1), €17 @ [Conrad](https://www.conrad.com/p/espressif-pcb-design-board-esp32-c3-devkitm-1-2490158)) or M5Stamp C3 ($6 @ [M5Stack](https://twitter.com/home_assistant/status/1531712479016890369))
- Bluetooth. If you use a Raspberry Pi to run Home Assistant you’re set. If you have a Home Assistant Blue or another device without Bluetooth, get a Bluetooth USB adapter that is supported by Home Assistant OS ([like this one](https://www.amazon.com/gp/product/B09DMP6T22/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=B09DMP6T22&linkCode=as2&tag=homeassista0e-20&linkId=c5046239bf04d5b21835299dfb393f0e)).
Even if you can’t follow along, it will still be an informative session!

303
source/_posts/2022-06-01-release-20226.markdown
View File

@ -59,26 +59,20 @@ Enjoy the release (and upcoming events)!
- [Other noteworthy changes](#other-noteworthy-changes)
- [New Integrations](#new-integrations)
- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
- [Release 2022.6.1 - June 2](#release-202261---june-2)
- [Release 2022.6.2 - June 4](#release-202262---june-4)
- [Release 2022.6.3 - June 6](#release-202263---june-6)
- [Release 2022.6.4 - June 7](#release-202264---june-7)
- [Release 2022.6.5 - June 10](#release-202265---june-10)
- [Need help? Join the community!](#need-help-join-the-community)
- [Breaking Changes](#breaking-changes)
- [Farewell to the following](#farewell-to-the-following)
- [All changes](#all-changes)
Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=LVDex3IV44M) today at 12:00 PDT / 21:00 CET!
<div class="videoWrapper">
<iframe width="853" height="480" src="https://www.youtube-nocookie.com/embed/LVDex3IV44M" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
</div>
{% comment %}
<!-- Replace the wrapper above with the following after the livestream...-->
Missed our release party live stream on YouTube? Don't worry! You can watch
the recording of it right here!
<lite-youtube videoid="LVDex3IV44M" videotitle="Home Assistant 2022.6 Release Party" posterquality="maxresdefault"></lite-youtube>
{% endcomment %}
<lite-youtube videoid="LVDex3IV44M" videotitle="Home Assistant 2022.6 Release Party"></lite-youtube>
## Comparing data in the energy dashboard
@ -336,6 +330,271 @@ The following integrations are now available via the Home Assistant UI:
[HERE Travel Time]: /integrations/here_travel_time
[Slack]: /integrations/slack
## Release 2022.6.1 - June 2
- Cleanup and use new MQTT_BASE_SCHEMA constants ([@jbouwh] - [#72283]) ([mqtt docs])
- Move MQTT config schemas and client to separate modules ([@emontnemery] - [#71995]) ([mqtt docs])
- Update MQTT tests to use the config entry setup ([@jbouwh] - [#72373]) ([mqtt docs])
- Remove announce workaround for Sonos ([@jjlawren] - [#72854]) ([sonos docs])
- Update frontend to 20220601.0 ([@bramkragten] - [#72855]) ([frontend docs])
- Ensure recorder shuts down when its startup future is canceled out from under it ([@bdraco] - [#72866]) ([recorder docs])
- Fix logbook not setting up with an recorder filter that has empty fields ([@bdraco] - [#72869]) ([recorder docs]) ([logbook docs])
- Only present history_stats state as unknown if the time is in the future ([@bdraco] - [#72880]) ([history_stats docs])
- Fix migration of MySQL data when InnoDB is not being used ([@bdraco] - [#72893]) ([recorder docs])
- Fix performance of logbook entity and devices queries with large MySQL databases ([@bdraco] - [#72898]) ([logbook docs])
- Fix reload of MQTT yaml config ([@emontnemery] - [#72901]) ([mqtt docs])
- Bump yolink-api to 0.0.6 ([@matrixd2] - [#72903]) ([yolink docs])
- Fix logging & exit code reporting to S6 on HA shutdown ([@nojocodex] - [#72921])
- Fix bug in caldav and avoid unnecessary copy of dataclass ([@allenporter] - [#72922]) ([caldav docs])
- Fix Hive authentication ([@KJonline] - [#72929]) ([hive docs])
- Only sync when HA is started up as we already sync at startup ([@balloob] - [#72940]) ([cloud docs])
- Fix misalignments between sql based filtering with the entityfilter based filtering ([@bdraco] - [#72936]) ([recorder docs])
- Only create auto comfort entities for BAF devices that support them ([@bdraco] - [#72948]) ([baf docs])
[#71995]: https://github.com/home-assistant/core/pull/71995
[#72283]: https://github.com/home-assistant/core/pull/72283
[#72373]: https://github.com/home-assistant/core/pull/72373
[#72854]: https://github.com/home-assistant/core/pull/72854
[#72855]: https://github.com/home-assistant/core/pull/72855
[#72866]: https://github.com/home-assistant/core/pull/72866
[#72869]: https://github.com/home-assistant/core/pull/72869
[#72880]: https://github.com/home-assistant/core/pull/72880
[#72893]: https://github.com/home-assistant/core/pull/72893
[#72898]: https://github.com/home-assistant/core/pull/72898
[#72901]: https://github.com/home-assistant/core/pull/72901
[#72903]: https://github.com/home-assistant/core/pull/72903
[#72921]: https://github.com/home-assistant/core/pull/72921
[#72922]: https://github.com/home-assistant/core/pull/72922
[#72929]: https://github.com/home-assistant/core/pull/72929
[#72936]: https://github.com/home-assistant/core/pull/72936
[#72940]: https://github.com/home-assistant/core/pull/72940
[#72948]: https://github.com/home-assistant/core/pull/72948
[@KJonline]: https://github.com/KJonline
[@allenporter]: https://github.com/allenporter
[@balloob]: https://github.com/balloob
[@bdraco]: https://github.com/bdraco
[@bramkragten]: https://github.com/bramkragten
[@emontnemery]: https://github.com/emontnemery
[@jbouwh]: https://github.com/jbouwh
[@jjlawren]: https://github.com/jjlawren
[@matrixd2]: https://github.com/matrixd2
[@nojocodex]: https://github.com/nojocodex
[baf docs]: /integrations/baf/
[caldav docs]: /integrations/caldav/
[cloud docs]: /integrations/cloud/
[frontend docs]: /integrations/frontend/
[history_stats docs]: /integrations/history_stats/
[hive docs]: /integrations/hive/
[logbook docs]: /integrations/logbook/
[mqtt docs]: /integrations/mqtt/
[recorder docs]: /integrations/recorder/
[sonos docs]: /integrations/sonos/
[yolink docs]: /integrations/yolink/
## Release 2022.6.2 - June 4
- Fix statistics_during_period being incorrectly cached ([@bdraco] - [#72947]) ([history docs])
- Allow `log` template function to return specified `default` on math domain error ([@XaF] - [#72960])
- Bump pynetgear to 0.10.4 ([@starkillerOG] - [#72965]) ([netgear docs])
- Bump bimmer_connected to 0.9.4 ([@rikroe] - [#72973]) ([bmw_connected_drive docs])
- fjaraskupan: Don't filter anything in backend ([@elupus] - [#72988]) ([fjaraskupan docs])
- Check ISY994 climate for unknown humidity value on Z-Wave Thermostat ([@shbatm] - [#72990]) ([isy994 docs])
- Fix google calendar bug where expired tokens are not refreshed ([@allenporter] - [#72994]) ([google docs])
- Provide Sonos media position if duration not available ([@jjlawren] - [#73001]) ([sonos docs])
- Bump pypck to 0.7.15 ([@alengwenus] - [#73009]) ([lcn docs])
- Fix missing historical context data in logbook for MySQL and PostgreSQL ([@bdraco] - [#73011]) ([recorder docs])
- Fix history stats not comparing all times in UTC ([@bdraco] - [#73040]) ([history_stats docs])
[#72947]: https://github.com/home-assistant/core/pull/72947
[#72960]: https://github.com/home-assistant/core/pull/72960
[#72965]: https://github.com/home-assistant/core/pull/72965
[#72973]: https://github.com/home-assistant/core/pull/72973
[#72988]: https://github.com/home-assistant/core/pull/72988
[#72990]: https://github.com/home-assistant/core/pull/72990
[#72994]: https://github.com/home-assistant/core/pull/72994
[#73001]: https://github.com/home-assistant/core/pull/73001
[#73009]: https://github.com/home-assistant/core/pull/73009
[#73011]: https://github.com/home-assistant/core/pull/73011
[#73040]: https://github.com/home-assistant/core/pull/73040
[@XaF]: https://github.com/XaF
[@alengwenus]: https://github.com/alengwenus
[@allenporter]: https://github.com/allenporter
[@bdraco]: https://github.com/bdraco
[@elupus]: https://github.com/elupus
[@jjlawren]: https://github.com/jjlawren
[@rikroe]: https://github.com/rikroe
[@shbatm]: https://github.com/shbatm
[@starkillerOG]: https://github.com/starkillerOG
[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
[fjaraskupan docs]: /integrations/fjaraskupan/
[google docs]: /integrations/google/
[history docs]: /integrations/history/
[history_stats docs]: /integrations/history_stats/
[isy994 docs]: /integrations/isy994/
[lcn docs]: /integrations/lcn/
[netgear docs]: /integrations/netgear/
[recorder docs]: /integrations/recorder/
[sonos docs]: /integrations/sonos/
## Release 2022.6.3 - June 6
- Throttle multiple requests to the velux gateway ([@marcelveldt] - [#72974]) ([velux docs])
- Bump wallbox to 0.4.9 ([@hesselonline] - [#72978]) ([wallbox docs])
- Fix fibaro cover detection ([@rappenze] - [#72986]) ([fibaro docs])
- Reduce branching in generated lambda_stmts ([@bdraco] - [#73042]) ([recorder docs])
- Send an empty logbook response when all requested entity_ids are filtered away ([@bdraco] - [#73046]) ([logbook docs])
- Bump aiolookup to 0.1.1 ([@bdraco] - [#73048]) ([lookin docs])
- Bump simplisafe-python to 2022.06.0 ([@bachya] - [#73054]) ([simplisafe docs])
- Fix unhandled exception when RainMachine coordinator data doesn't exist ([@bachya] - [#73055]) ([rainmachine docs])
- Bump regenmaschine to 2022.06.0 ([@bachya] - [#73056]) ([rainmachine docs])
- Fix incompatiblity with live logbook and google_assistant ([@bdraco] - [#73063]) ([logbook docs])
- Fix elk attributes not being json serializable ([@gwww] - [#73096]) ([elkm1 docs])
- Mark counter domain as continuous to exclude it from logbook ([@bdraco] - [#73101]) ([logbook docs])
- Tomorrowio utc fix ([@lymanepp] - [#73102]) ([tomorrowio docs])
- Remove available property from Kodi ([@Bikonja] - [#73103]) ([kodi docs])
- Point iAlarm XR at PyPI fork ([@balloob] - [#73143]) ([ialarm_xr docs])
- Fix state_changes_during_period history query when no entities are passed ([@bdraco] - [#73139]) ([recorder docs])
- Remove unused code from logbook ([@bdraco] - [#72950]) ([logbook docs])
[#72950]: https://github.com/home-assistant/core/pull/72950
[#72974]: https://github.com/home-assistant/core/pull/72974
[#72978]: https://github.com/home-assistant/core/pull/72978
[#72986]: https://github.com/home-assistant/core/pull/72986
[#73042]: https://github.com/home-assistant/core/pull/73042
[#73046]: https://github.com/home-assistant/core/pull/73046
[#73048]: https://github.com/home-assistant/core/pull/73048
[#73054]: https://github.com/home-assistant/core/pull/73054
[#73055]: https://github.com/home-assistant/core/pull/73055
[#73056]: https://github.com/home-assistant/core/pull/73056
[#73063]: https://github.com/home-assistant/core/pull/73063
[#73096]: https://github.com/home-assistant/core/pull/73096
[#73101]: https://github.com/home-assistant/core/pull/73101
[#73102]: https://github.com/home-assistant/core/pull/73102
[#73103]: https://github.com/home-assistant/core/pull/73103
[#73139]: https://github.com/home-assistant/core/pull/73139
[#73143]: https://github.com/home-assistant/core/pull/73143
[@Bikonja]: https://github.com/Bikonja
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@bdraco]: https://github.com/bdraco
[@gwww]: https://github.com/gwww
[@hesselonline]: https://github.com/hesselonline
[@lymanepp]: https://github.com/lymanepp
[@marcelveldt]: https://github.com/marcelveldt
[@rappenze]: https://github.com/rappenze
[elkm1 docs]: /integrations/elkm1/
[fibaro docs]: /integrations/fibaro/
[ialarm_xr docs]: /integrations/ialarm_xr/
[kodi docs]: /integrations/kodi/
[logbook docs]: /integrations/logbook/
[lookin docs]: /integrations/lookin/
[rainmachine docs]: /integrations/rainmachine/
[recorder docs]: /integrations/recorder/
[simplisafe docs]: /integrations/simplisafe/
[tomorrowio docs]: /integrations/tomorrowio/
[velux docs]: /integrations/velux/
[wallbox docs]: /integrations/wallbox/
## Release 2022.6.4 - June 7
- Fix errors when unjoining multiple Sonos devices simultaneously ([@jjlawren] - [#73133]) ([sonos docs])
- Bump async-upnp-client==0.31.1 ([@StevenLooman] - [#73135]) ([upnp docs]) ([yeelight docs]) ([dlna_dmr docs]) ([samsungtv docs]) ([ssdp docs]) ([dlna_dms docs])
- Use default None for voltage property of FritzDevice in Fritz!Smarthome ([@mib1185] - [#73141]) ([fritzbox docs])
- Fix KeyError from ESPHome media players on startup ([@jesserockz] - [#73149]) ([esphome docs])
- Fix bugs with RainMachine zone run time sensors ([@bachya] - [#73179]) ([rainmachine docs])
- Fix creating unique IDs for WiFi switches in Fritz!Tools ([@mib1185] - [#73183]) ([fritz docs])
- Bump pywemo to 0.9.1 ([@esev] - [#73186]) ([wemo docs])
- Remove sqlalchemy lambda_stmt usage from history, logbook, and statistics ([@bdraco] - [#73191]) ([recorder docs]) ([logbook docs])
[#73133]: https://github.com/home-assistant/core/pull/73133
[#73135]: https://github.com/home-assistant/core/pull/73135
[#73141]: https://github.com/home-assistant/core/pull/73141
[#73149]: https://github.com/home-assistant/core/pull/73149
[#73179]: https://github.com/home-assistant/core/pull/73179
[#73183]: https://github.com/home-assistant/core/pull/73183
[#73186]: https://github.com/home-assistant/core/pull/73186
[#73191]: https://github.com/home-assistant/core/pull/73191
[@StevenLooman]: https://github.com/StevenLooman
[@bachya]: https://github.com/bachya
[@bdraco]: https://github.com/bdraco
[@esev]: https://github.com/esev
[@jesserockz]: https://github.com/jesserockz
[@jjlawren]: https://github.com/jjlawren
[@mib1185]: https://github.com/mib1185
[dlna_dmr docs]: /integrations/dlna_dmr/
[dlna_dms docs]: /integrations/dlna_dms/
[esphome docs]: /integrations/esphome/
[fritz docs]: /integrations/fritz/
[fritzbox docs]: /integrations/fritzbox/
[logbook docs]: /integrations/logbook/
[rainmachine docs]: /integrations/rainmachine/
[recorder docs]: /integrations/recorder/
[samsungtv docs]: /integrations/samsungtv/
[sonos docs]: /integrations/sonos/
[ssdp docs]: /integrations/ssdp/
[upnp docs]: /integrations/upnp/
[wemo docs]: /integrations/wemo/
[yeelight docs]: /integrations/yeelight/
## Release 2022.6.5 - June 10
- Ensure netgear devices are tracked with one enabled config entry ([@starkillerOG] - [#72969]) ([netgear docs])
- Bump yolink-api to 0.0.8 ([@matrixd2] - [#73173]) ([yolink docs])
- Fix Feedreader Atom feeds using `updated` date ([@d0nni3q84] - [#73208]) ([feedreader docs])
- Hive auth fix for users ([@KJonline] - [#73247]) ([hive docs])
- Fix handling of connection error during Synology DSM setup ([@mib1185] - [#73248]) ([synology_dsm docs])
- Bump regenmaschine to 2022.06.1 ([@bachya] - [#73250]) ([rainmachine docs])
- Improve Netgear logging ([@starkillerOG] - [#73274]) ([netgear docs])
- Fix polling frequency for Starling integration ([@Dullage] - [#73282]) ([starlingbank docs])
- Fix reloading themes crashing if no themes configured ([@balloob] - [#73287]) ([frontend docs])
- Bump version of pyunifiprotect to 3.9.0 ([@AngellusMortis] - [#73168]) ([unifiprotect docs])
- Bumps version of pyunifiprotect to 3.9.1 ([@AngellusMortis] - [#73252]) ([unifiprotect docs])
- Bumps version of pyunifiprotect to 3.9.2 to fix compat with protect 2.1.1 ([@AngellusMortis] - [#73299]) ([unifiprotect docs])
- Fix initial tilt value of MQTT cover ([@emontnemery] - [#73308]) ([mqtt docs])
- Fix wallbox sensor rounding ([@hesselonline] - [#73310]) ([wallbox docs])
- Improve MQTT reload performance ([@emontnemery] - [#73313]) ([mqtt docs])
- Guard MySQL size calculation returning None ([@balloob] - [#73331]) ([recorder docs])
[#72969]: https://github.com/home-assistant/core/pull/72969
[#73168]: https://github.com/home-assistant/core/pull/73168
[#73173]: https://github.com/home-assistant/core/pull/73173
[#73208]: https://github.com/home-assistant/core/pull/73208
[#73247]: https://github.com/home-assistant/core/pull/73247
[#73248]: https://github.com/home-assistant/core/pull/73248
[#73250]: https://github.com/home-assistant/core/pull/73250
[#73252]: https://github.com/home-assistant/core/pull/73252
[#73274]: https://github.com/home-assistant/core/pull/73274
[#73282]: https://github.com/home-assistant/core/pull/73282
[#73287]: https://github.com/home-assistant/core/pull/73287
[#73299]: https://github.com/home-assistant/core/pull/73299
[#73308]: https://github.com/home-assistant/core/pull/73308
[#73310]: https://github.com/home-assistant/core/pull/73310
[#73313]: https://github.com/home-assistant/core/pull/73313
[#73331]: https://github.com/home-assistant/core/pull/73331
[@AngellusMortis]: https://github.com/AngellusMortis
[@Dullage]: https://github.com/Dullage
[@KJonline]: https://github.com/KJonline
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@d0nni3q84]: https://github.com/d0nni3q84
[@emontnemery]: https://github.com/emontnemery
[@hesselonline]: https://github.com/hesselonline
[@matrixd2]: https://github.com/matrixd2
[@mib1185]: https://github.com/mib1185
[@starkillerOG]: https://github.com/starkillerOG
[feedreader docs]: /integrations/feedreader/
[frontend docs]: /integrations/frontend/
[hive docs]: /integrations/hive/
[mqtt docs]: /integrations/mqtt/
[netgear docs]: /integrations/netgear/
[rainmachine docs]: /integrations/rainmachine/
[recorder docs]: /integrations/recorder/
[starlingbank docs]: /integrations/starlingbank/
[synology_dsm docs]: /integrations/synology_dsm/
[unifiprotect docs]: /integrations/unifiprotect/
[wallbox docs]: /integrations/wallbox/
[yolink docs]: /integrations/yolink/
## Need help? Join the community!
Home Assistant has a great community of users who are all more than willing
@ -464,6 +723,26 @@ the documentation of the specific integration on how to configure this.
{% enddetails %}
{% details "Home Assistant Container" %}
If you run Home Assistant Container in Docker (e.g., using Portainer,
Docker (Compose), QNAP, and others), please make sure you are not specifying
an init process.
This can be an `init` configuration option in your Docker management tools or
Docker Compose, or the `--init` command line flag on the raw Docker command.
These should **NOT** be set, as Home Assistant ships with the S6 init system.
While you are at it, make sure you also do not set a `cmd` or `entrypoint`.
Setting these are not breaking, however, you should not set them.
([@pvizeli] - [#72425]) ([documentation](/installation))
[@pvizeli]: https://github.com/pvizeli
[#72425]: https://github.com/home-assistant/core/pull/72425
{% enddetails %}
{% details "1-Wire" %}
Using the 1-Wire via SysBus, previously deprecated, has been removed;

1
source/dashboards/index.markdown
View File

@ -27,7 +27,6 @@ To try it yourself, check out [the demo](https://demo.home-assistant.io).
## Additional Resources
- [Awesome HA](https://www.awesome-ha.com/#lovelace-user-interface)
- [Community Custom Cards](https://github.com/custom-cards)
- [Home Assistant Cards](https://home-assistant-cards.bessarabov.com/)
- [Material Design Icons](https://materialdesignicons.com/tag/community)

2
source/getting-started/automation.markdown
View File

@ -12,7 +12,7 @@ In the user interface, click Configuration in the sidebar, then click Automation
The automation editor.
</p>
Click the orange button at the bottom right to create a new automation. You are presented with a blank automation screen.
Click the blue button at the bottom right to create a new automation. You are presented with a blank automation screen.
<p class='img'>
<img src='/images/getting-started/new-automation.png'>

2
source/getting-started/configuration.markdown
View File

@ -11,7 +11,7 @@ The steps below do not apply to Home Assistant Core & Container installations, f
</div>
We are going to help you make your first changes to `configuration.yaml`. To do this, we are going to install an add-on from the Home Assistant add-on store: the File editor. To get to the add-on store, click on the menu icon in the top left, then open {% my supervisor title="Settings > Add-ons" %}. On the new page, open the add-on store tab.
We are going to help you make your first changes to `configuration.yaml`. To do this, we are going to install an add-on from the Home Assistant add-on store: the File editor. To get to the add-on store, go to {% my supervisor title="Settings > Add-ons" %}. On the new page, open the add-on store tab.
![Add-on store.](/images/hassio/screenshots/dashboard.png)

27
source/getting-started/onboarding.markdown
View File

@ -7,38 +7,23 @@ Alright, you made it here. The tough part is done.
With Home Assistant installed, it's time to configure it. Here you will create the owner account of Home Assistant. This account will be an administrator and will always be able to change everything. Enter a name, username, password and click on "create account".
<p class='img'>
<img src='/images/getting-started/username.png' />
Set your username and password.
</p>
![Set your username and password.](/images/getting-started/username.png)
Next, you can enter a name for your home and set your location and unit system. Click "DETECT" to find your location and set your time zone and unit system based on that location. If you'd rather not send your location, you can set these values manually.
<p class='img'>
<img src='/images/getting-started/location.png' />
Set your location, time zone, and unit system.
</p>
![Set your location, time zone, and unit system.](/images/getting-started/location.png)
Once you are done, click Next. In this screen, Home Assistant will show any devices that it has discovered on your network. Don't be alarmed if you see fewer items than what is shown below; you can always manually add devices later.
<p class='img'>
<img src='/images/getting-started/devices.png' />
Discovery of devices on your network.
</p>
![Discovery of devices on your network.](/images/getting-started/devices.png)
Finally, click Finish. Now you're brought to the Home Assistant web interface. This screen will show all of your devices. So let's get that screen filled up!
<p class='img'>
<img src='/images/getting-started/lovelace.png' />
The Home Assistant user interface.
</p>
![The Home Assistant user interface.](/images/getting-started/lovelace.png)
Click on "Configuration" in the sidebar on the left. On the next screen, click on "Devices & Services". At this screen you will be able to set up integrations with Home Assistant. You might notice a "discovered" section. This section contains integrations that were found on your network and can easily be added with a few clicks. If your integrations are not discovered, click the "Add integration" button in the lower right and search for your integration in that list.
From the side bar, click on {% my integrations title="Settings -> Devices & Services" %}. At this screen you will be able to set up integrations with Home Assistant. You might notice a "discovered" section. This section contains integrations that were found on your network and can easily be added with a few clicks. If your integrations are not discovered, click the **Add integration** button in the lower right and search for your integration in that list.
<p class='img'>
<img src='/images/getting-started/integrations.png' />
The integrations page in the configurations panel shows you all your configured integrations.
</p>
![The integrations page in the configurations panel shows you all your configured integrations.](/images/getting-started/integrations.png)
When each integration is done setting up, it will ask you to put the new devices in areas. Areas allow you to organize all the devices in your home.

2
source/help/talking-points.markdown
View File

@ -7,7 +7,7 @@ sidebar: false
People are starting to present Home Assistant at meetings and get-togethers. Below you find a couple of bullet points for your presentation.
- [Numbers, numbers, numbers](/help/trivia/) and other details
- Over 1000 implementations
- Over 1900 implementations
- Not depending on cloud services. We like to keep your privacy private
- Control all your devices from a single, mobile-friendly interface
- Written in Python3 with 94% test coverage

BIN
source/images/addons/addon-store.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 148 KiB

After

Width:  |  Height:  |  Size: 132 KiB

BIN
source/images/blog/2021-12-stanford-genie/social.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 35 KiB

After

Width:  |  Height:  |  Size: 25 KiB

BIN
source/images/blog/2022-02-android/Companion.png Executable file → Normal file
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 141 KiB

After

Width:  |  Height:  |  Size: 128 KiB

BIN
source/images/blog/2022-04-for-insteon-users/insteon-panel-1.jpg
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 92 KiB

After

Width:  |  Height:  |  Size: 68 KiB

BIN
source/images/blog/2022-04-for-insteon-users/insteon-panel-2.jpg
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 86 KiB

After

Width:  |  Height:  |  Size: 64 KiB

BIN
source/images/blog/2022-05-matter-in-home-assistant-workshop-announcement/social.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 102 KiB

After

Width:  |  Height:  |  Size: 83 KiB

BIN
source/images/dashboards/lovelace_gauge_segments.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 12 KiB

After

Width:  |  Height:  |  Size: 9.2 KiB

BIN
source/images/docs/quick-bar/disable-shortcuts-toggle.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 76 KiB

After

Width:  |  Height:  |  Size: 55 KiB

BIN
source/images/energy/cost.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 32 KiB

After

Width:  |  Height:  |  Size: 24 KiB

BIN
source/images/getting-started/automation-editor.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 40 KiB

After

Width:  |  Height:  |  Size: 40 KiB

BIN
source/images/getting-started/integrations.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 74 KiB

After

Width:  |  Height:  |  Size: 74 KiB

BIN
source/images/getting-started/lovelace.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 76 KiB

After

Width:  |  Height:  |  Size: 65 KiB

BIN
source/images/getting-started/new-automation.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 75 KiB

After

Width:  |  Height:  |  Size: 75 KiB

BIN
source/images/getting-started/username.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 31 KiB

After

Width:  |  Height:  |  Size: 27 KiB

BIN
source/images/hassio/screenshots/adding_repositories.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 16 KiB

After

Width:  |  Height:  |  Size: 13 KiB

BIN
source/images/hassio/screenshots/dashboard.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 22 KiB

BIN
source/images/hassio/screenshots/exit-shell.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 33 KiB

After

Width:  |  Height:  |  Size: 27 KiB

BIN
source/images/installation/etcher1.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 18 KiB

After

Width:  |  Height:  |  Size: 14 KiB

BIN
source/images/installation/etcher2.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 23 KiB

After

Width:  |  Height:  |  Size: 19 KiB

BIN
source/images/installation/etcher3.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 20 KiB

After

Width:  |  Height:  |  Size: 14 KiB

BIN
source/images/installation/etcher4.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 20 KiB

BIN
source/images/installation/etcher5.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 22 KiB

After

Width:  |  Height:  |  Size: 15 KiB

BIN
source/images/installation/etcher6.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 52 KiB

After

Width:  |  Height:  |  Size: 51 KiB

BIN
source/images/installation/intel-nuc-disable-secure-boot.jpg
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 94 KiB

After

Width:  |  Height:  |  Size: 74 KiB

BIN
source/images/installation/intel-nuc-enter-bios.jpg
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 31 KiB

After

Width:  |  Height:  |  Size: 15 KiB

BIN
source/images/installation/intel-nuc-uefi-boot.jpg
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 101 KiB

After

Width:  |  Height:  |  Size: 96 KiB

BIN
source/images/integrations/homekit_controller/device_automation_finish.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 89 KiB

After

Width:  |  Height:  |  Size: 81 KiB

BIN
source/images/integrations/homekit_controller/device_automation_new.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 100 KiB

After

Width:  |  Height:  |  Size: 93 KiB

BIN
source/images/screenshots/button_classes_icons.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 8.3 KiB

After

Width:  |  Height:  |  Size: 5.9 KiB

BIN
source/images/screenshots/steam_privacy_settings.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 36 KiB

Some files were not shown because too many files have changed in this diff Show More