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-28 11:47:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2022-07-18 22:32:47 +02:00
commit 8eb250d671
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
42 changed files with 641 additions and 265 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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.3.0
uses: actions/setup-node@v3.4.1
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.3.0
uses: actions/setup-node@v3.4.1
with:
node-version: 16.x
cache: "npm"

4
Gemfile
View File

@ -19,8 +19,8 @@ group :jekyll_plugins do
gem 'jekyll-toc', '0.17.1'
end
gem 'sinatra', '2.2.0'
gem 'nokogiri', '1.13.6'
gem 'sinatra', '2.2.1'
gem 'nokogiri', '1.13.7'
# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
# and associated library

18
Gemfile.lock
View File

@ -28,7 +28,7 @@ GEM
ffi (1.15.5-x64-mingw32)
forwardable-extended (2.6.0)
http_parser.rb (0.8.0)
i18n (1.10.0)
i18n (1.12.0)
concurrent-ruby (~> 1.0)
jekyll (4.2.2)
addressable (~> 2.4)
@ -68,19 +68,19 @@ GEM
mercenary (0.4.0)
mini_portile2 (2.8.0)
multi_json (1.15.0)
mustermann (1.1.1)
mustermann (1.1.2)
ruby2_keywords (~> 0.0.1)
nokogiri (1.13.6)
nokogiri (1.13.7)
mini_portile2 (~> 2.8.0)
racc (~> 1.4)
nokogiri (1.13.6-x64-mingw32)
nokogiri (1.13.7-x64-mingw32)
racc (~> 1.4)
pathutil (0.16.2)
forwardable-extended (~> 2.6)
public_suffix (4.0.7)
racc (1.6.0)
rack (2.2.4)
rack-protection (2.2.0)
rack-protection (2.2.1)
rack
rake (13.0.6)
rb-fsevent (0.11.1)
@ -97,10 +97,10 @@ GEM
ffi (~> 1.9)
sassc (2.1.0-x64-mingw32)
ffi (~> 1.9)
sinatra (2.2.0)
sinatra (2.2.1)
mustermann (~> 1.0)
rack (~> 2.2)
rack-protection (= 2.2.0)
rack-protection (= 2.2.1)
tilt (~> 2.0)
stringex (2.8.5)
terminal-table (2.0.0)
@ -123,11 +123,11 @@ DEPENDENCIES
jekyll-paginate (= 1.1.0)
jekyll-sitemap (= 1.4.0)
jekyll-toc (= 0.17.1)
nokogiri (= 1.13.6)
nokogiri (= 1.13.7)
rake (= 13.0.6)
sass-globbing (= 1.1.5)
sassc (= 2.1.0)
sinatra (= 2.2.0)
sinatra (= 2.2.1)
stringex (= 2.8.5)
tzinfo (~> 2.0)
tzinfo-data

4
_config.yml
View File

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

4
source/_dashboards/gauge.markdown
View File

@ -61,7 +61,7 @@ max:
default: 100
needle:
required: false
description: Show the gauge as a needle gauge.
description: Show the gauge as a needle gauge. Required to be set to true, if using segments.
type: boolean
default: false
severity:
@ -83,7 +83,7 @@ severity:
type: integer
segments:
required: false
description: List of colors and their corresponding start values. Segments will override the severity settings.
description: List of colors and their corresponding start values. Segments will override the severity settings. Needle required to be true.
type: list
keys:
from:

2
source/_docs/energy/faq.markdown
View File

@ -13,7 +13,7 @@ Electrical Power is measured in Watts (W) and Electrical Energy is measured in k
Think of this in a parallel to speed and distance: Power is the speed you are going and Energy is the distance driven.
Therefore Energy (kiloWatt-hour) is not an average of the Power you are consuming over a given period of time (that would be kiloWatt/hour). Energy is the integral (mathematical operation) of the Power function.
Therefore Energy (kiloWatt-hour) is not an average of the Power you are consuming over a given period of time (the unit of the average power would be Watt or kiloWatt again). Energy is the integral (mathematical operation) of the Power function.
This difference is very important as you need to use the proper entities in our Energy Panel.

82
source/_docs/mqtt/discovery.markdown
View File

@ -363,7 +363,7 @@ mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/config
For more details please refer to the [MQTT testing section](/docs/mqtt/testing/).
### Sensors with multiple values
### Sensors
Setting up a sensor with multiple measurement values requires multiple consecutive configuration topic submissions.
@ -373,9 +373,9 @@ Setting up a sensor with multiple measurement values requires multiple consecuti
- Configuration payload no2: `{"device_class": "humidity", "name": "Humidity", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "%", "value_template": "{% raw %}{{ value_json.humidity}}{% endraw %}" }`
- Common state payload: `{ "temperature": 23.20, "humidity": 43.70 }`
### Switches
### Entities with command topics
Setting up a switch is similar but requires a `command_topic` as mentioned in the [MQTT switch documentation](/integrations/switch.mqtt/).
Setting up a light, switch etc. is similar but requires a `command_topic` as mentioned in the [MQTT switch documentation](/integrations/switch.mqtt/).
- Configuration topic: `homeassistant/switch/irrigation/config`
- State topic: `homeassistant/switch/irrigation/state`
@ -394,7 +394,7 @@ Set the state.
mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/switch/irrigation/set" -m ON
```
### Abbreviating topic names
### Using abbreviations and base topic
Setting up a switch using topic prefix and abbreviated configuration variable names to reduce payload length.
@ -403,7 +403,7 @@ Setting up a switch using topic prefix and abbreviated configuration variable na
- State topic: `homeassistant/switch/irrigation/state`
- Configuration payload: `{"~": "homeassistant/switch/irrigation", "name": "garden", "cmd_t": "~/set", "stat_t": "~/state"}`
### Lighting
### Another example using abbreviations topic name and base topic
Setting up a [light that takes JSON payloads](/integrations/light.mqtt/#json-schema), with abbreviated configuration variable names:
@ -425,78 +425,6 @@ Setting up a [light that takes JSON payloads](/integrations/light.mqtt/#json-sch
}
```
### Climate control
Setting up a climate integration (heat only):
- Configuration topic: `homeassistant/climate/livingroom/config`
- Configuration payload:
```json
{
"name":"Livingroom",
"mode_cmd_t":"homeassistant/climate/livingroom/thermostatModeCmd",
"mode_stat_t":"homeassistant/climate/livingroom/state",
"mode_stat_tpl":"{{value_json.mode}}",
"avty_t":"homeassistant/climate/livingroom/available",
"pl_avail":"online",
"pl_not_avail":"offline",
"temp_cmd_t":"homeassistant/climate/livingroom/targetTempCmd",
"temp_stat_t":"homeassistant/climate/livingroom/state",
"temp_stat_tpl":"{{value_json.target_temp}}",
"curr_temp_t":"homeassistant/climate/livingroom/state",
"curr_temp_tpl":"{{value_json.current_temp}}",
"min_temp":"15",
"max_temp":"25",
"temp_step":"0.5",
"modes":["off", "heat"]
}
```
- State topic: `homeassistant/climate/livingroom/state`
- State payload:
```json
{
"mode":"off",
"target_temp":"21.50",
"current_temp":"23.60"
}
```
### Presence detection (device tracker)
Setting up a device tracker:
- Configuration topic: `homeassistant/device_tracker/paulus/config`
- Example configuration payload:
```json
{
"name":"Paulus",
"state_topic": "homeassistant/device_tracker/paulus/state",
"payload_home": "home",
"payload_not_home": "not_home",
"source_type": "bluetooth"
}
```
- State topic: `homeassistant/device_tracker/paulus/state`
- Example state payload: `home` or `not_home` or `location name`
If the device supports GPS coordinates then they can be sent to Home Assistant by specifying an attributes topic (i.e. "json_attributes_topic") in the configuration payload:
- Attributes topic: `homeassistant/device_tracker/paulus/attributes`
- Example attributes payload:
```json
{
"latitude": 32.87336,
"longitude": -117.22743,
"gps_accuracy": 1.2
}
```
### Use object_id to influence the entity id

2
source/_includes/installation/container.md
View File

@ -8,7 +8,7 @@ These below instructions are for an installation of Home Assistant Container run
This guide assumes that you already have an operating system setup and a container runtime installed (like Docker).
If you are using Docker then you need to be on at least version 19.03.9, ideally an even higher version, and `libseccomp` 2.42 or newer.
If you are using Docker then you need to be on at least version 19.03.9, ideally an even higher version, and `libseccomp` 2.4.2 or newer.
</div>
### Platform Installation

2
source/_includes/installation/operating_system.md
View File

@ -165,7 +165,7 @@ This can be accomplished either by using a live operating system (e.g. Ubuntu) a
```text
efibootmgr --create --disk /dev/<drivename> --part 1 --label "HAOS" \
--loader \EFI\BOOT\bootx64.efi
--loader "\EFI\BOOT\bootx64.efi"
```
Or else, the BIOS might provide you with a tool to add boot options, there you can specify the path to the EFI file:

2
source/_integrations/amcrest.markdown
View File

@ -48,7 +48,7 @@ host:
required: true
type: string
username:
description: The username for accessing your camera.
description: The username for accessing your camera. Most Amcrest devices use "admin" for the username, even if you've configured another username in their app.
required: true
type: string
password:

2
source/_integrations/counter.markdown
View File

@ -47,7 +47,7 @@ counter:
required: false
type: string
initial:
description: Initial value when Home Assistant starts or the counter is reset.
description: Initial value (0 or positive integer) when Home Assistant starts or the counter is reset.
required: false
type: integer
default: 0

2
source/_integrations/denon.markdown
View File

@ -11,7 +11,7 @@ ha_platforms:
ha_integration_type: integration
---
The `denon` platform allows you to control a [Denon Network Receiver](https://www.denon.com/category/homecinema/avreceiver) from Home Assistant. It might be that your device is supported by the [Denon AVR] platform.
The `denon` platform allows you to control a Denon Network Receiver from Home Assistant. It might be that your device is supported by the [Denon AVR] platform.
Supported devices:

6
source/_integrations/denonavr.markdown
View File

@ -16,7 +16,7 @@ ha_platforms:
ha_integration_type: integration
---
The `denonavr` platform allows you to control [Denon Network Receivers](https://www.denon.com/en-gb/shop/networkmusicsystem/ceolpiccolon4) from Home Assistant. It might be that your device is supported by the [Denon] platform.
The `denonavr` platform allows you to control [Denon Network Receivers](https://www.denon.com/category/heos) from Home Assistant. It might be that your device is supported by the [Denon] platform.
Known supported devices:
@ -51,6 +51,7 @@ Known supported devices:
- Denon AVR-X6500H
- Denon AVR-X6700H
- Denon AVR-1912
- Denon AVR-2112CI
- Denon AVR-2312CI
- Denon AVR-3311CI
- Denon AVR-3312
@ -61,6 +62,7 @@ Known supported devices:
- Denon AVR-S720W
- Denon AVR-S750H
- Denon AVR-S760H
- Denon AVR-S950H
- Denon AVR-S960H
- Denon DN-500AV
- Marantz AV7702
@ -118,7 +120,7 @@ A few notes:
- The `denonavr` platform supports some additional functionalities like album covers, custom input source names and auto discovery.
- Marantz receivers seem to a have quite a similar interface. Thus if you own one, give it a try.
- To remotely power on Marantz receivers with Home Assistant, the Auto-Standby feature must be enabled in the receiver's settings.
- Sound mode: The command to set a specific sound mode is different from the value of the current sound mode reported by the receiver (sound_mode_raw). There is a key-value structure (sound_mode_dict) that matches the raw sound mode to one of the possible commands to set a sound mode (for instance {'MUSIC':['PLII MUSIC']}. If you get a "Not able to match sound mode" warning, please open an issue on the [denonavr library](https://github.com/scarface-4711/denonavr), stating which raw sound mode could not be matched so it can be added to the matching dictionary. You can find the current raw sound mode under **Developer Tools** -> **States**.
- Sound mode: The command to set a specific sound mode is different from the value of the current sound mode reported by the receiver (sound_mode_raw). There is a key-value structure (sound_mode_dict) that matches the raw sound mode to one of the possible commands to set a sound mode (for instance {'MUSIC':['PLII MUSIC']}. If you get a "Not able to match sound mode" warning, please open an issue on the [denonavr library](https://github.com/ol-iver/denonavr), stating which raw sound mode could not be matched so it can be added to the matching dictionary. You can find the current raw sound mode under **Developer Tools** -> **States**.
#### Service `denonavr.get_command`

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

@ -234,7 +234,7 @@ You can use the command line tool `mosquitto_pub` shipped with `mosquitto` or th
To create the device_tracker:
```bash
mosquitto_pub -h 127.0.0.1 -t home-assistant/device_tracker/a4567d663eaf/config -m '{"state_topic": "a4567d663eaf/state", "name": "My Tracker", "payload_home": "home", "payload_not_home": "not_home"}'
mosquitto_pub -h 127.0.0.1 -t homeassistant/device_tracker/a4567d663eaf/config -m '{"state_topic": "a4567d663eaf/state", "name": "My Tracker", "payload_home": "home", "payload_not_home": "not_home"}'
```
To set the state of the device tracker to "home":
@ -243,6 +243,38 @@ To set the state of the device tracker to "home":
mosquitto_pub -h 127.0.0.1 -t a4567d663eaf/state -m 'home'
```
To set the state of the device tracker to a named location:
```bash
mosquitto_pub -h 127.0.0.1 -t a4567d663eaf/state -m 'location_name'
```
If the device supports GPS coordinates then they can be sent to Home Assistant by specifying an attributes topic (i.e. "json_attributes_topic") in the configuration payload:
- Attributes topic: `a4567d663eaf/attributes`
- Example attributes payload:
```json
{
"latitude": 32.87336,
"longitude": -117.22743,
"gps_accuracy": 1.2
}
```
To create the device_tracker with GPS coordinates support:
```bash
mosquitto_pub -h 127.0.0.1 -t homeassistant/device_tracker/a4567d663eaf/config -m '{"state_topic": "a4567d663eaf/state", "name": "My Tracker", "payload_home": "home", "payload_not_home": "not_home", "json_attributes_topic": "a4567d663eaf/attributes"}'
```
To set the state of the device tracker to specific coordinates:
```bash
mosquitto_pub -h 127.0.0.1 -t a4567d663eaf/state -m '{"latitude": 32.87336, "longitude": -117.22743, "gps_accuracy": 1.2}'
```
### YAML configuration
The following example shows how to configure the same device tracker through configuration.yaml

2
source/_integrations/ecobee.markdown
View File

@ -34,7 +34,7 @@ The `ecobee` integration lets you control and view sensor data from [ecobee](htt
You will need to obtain an API key from ecobee's [developer site](https://www.ecobee.com/developers/) to use this integration. To get the key, your thermostat must be registered on ecobee's website (which you likely would have already done while installing your thermostat). Once you have done that, perform the following steps.
1. Click on the **Become a developer** link on the [developer site](https://www.ecobee.com/home/developer/loginDeveloper.jsp).
2. Log in with your ecobee credentials. (Make sure your password is at most 16 characters and multifactor authentication is disabled to meet the developer login form's limits. If you've already enabled MFA, the web portal and iOS apps don't support disabling it. The Android app does under Account > Account Security. You can re-enable MFA after becoming a developer.)
2. Log in with your ecobee credentials. (Make sure multifactor authentication is disabled to meet the developer login form's limits. If you've already enabled MFA, the web portal doesn't support disabling it. The iOS and Android apps do under Account > Account Security. You can re-enable MFA after becoming a developer.)
3. Accept the SDK agreement.
4. Fill in the fields.
5. Click **save**.

30
source/_integrations/google.markdown
View File

@ -28,24 +28,26 @@ This section explains how to generate a Client ID and Client Secret on
1. First go to the [Google Developers Console](https://console.developers.google.com/start/api?id=calendar)
1. The wizard will ask you to choose a project to manage your application. Select a project and click continue.
1. Verify that your calendar API was enabled and click 'Go to credentials'
1. When it gets to the Page titled _Add credentials to your project_ just click cancel.
1. Navigate to APIs & Services (left sidebar) > Credentials
1. Click on the field on the right of the screen, 'CONFIGURE CONSENT SCREEN', select "External" and create.
1. Set the 'Application Name' (the name of the application asking for consent) to anything you want. We suggest `Home-Assistant`.
1. You then need to select a `Support email`. To do this, simply click the drop down box and select your email address.
1. You finally need to complete the section: `Developer contact information`. To do this, simply enter your email address (same as above is fine).
1. Scroll to the bottom and click `save`. (You don't have to fill out anything else)
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 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.
1. Navigate to APIs & Services (left sidebar) > [Credentials](https://console.cloud.google.com/apis/credentials)
1. Click on the field on the right of the screen, **OAuth Consent Screen**.
1. Select **External** and **Create**.
1. Set the *App Name* (the name of the application asking for consent) to anything you want e.g. *Home Assistant*.
1. You then need to select a *Support email*. To do this, simply click the drop down box and select your email address.
1. You finally need to complete the section: *Developer contact information*. To do this, simply enter your email address (same as above is fine).
1. Scroll to the bottom and click **Save and Continue**. Don't have to fill out anything else or it may enable additional review.
1. You will then be automatically taken to the Scopes page. You do not need to add any scopes here so click Save and Continue to move to the Optional info page. You do not need to add anything to the Optional info page so click Save and Continue which will take you to the Summary page. Click Back to Dashboard.
1. Click **OAuth consent screen** again and set *Publish Status* to **Production** otherwise your credentials will expire every 7 days.
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 these 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. 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 %}
{% include integrations/config_flow.md %}
The integration setup will next give you instructions to enter the Application Credentials (OAuth Client ID and Client Secret) and authorize Home Assistant to access your account and Calendars.
The integration setup will next give you instructions to enter the [Application Credentials](/integrations/application_credentials/) (OAuth Client ID and Client Secret) and authorize Home Assistant to access your account and Calendars.
{% details "OAuth and Device Authorization steps" %}
@ -81,6 +83,8 @@ to all the Google Calendars available to your linked account.
If the setup process fails and you see an error message such as *Authentication code expired, please try again* you may want to try the flow again. You may also check the logs for additional error messages that may indicate a misconfiguration such as an invalid client id or secret.
If you have an error with your credentials you can delete them in the [Application Credentials](/integrations/application_credentials/) user interface.
## Calendar Entities
Each Google Calendar from *My Calendars* ([more info](https://support.google.com/calendar/answer/37095)) is represented as a [calendar](/integrations/calendar) entity in Home Assistant.

11
source/_integrations/history_stats.markdown
View File

@ -181,6 +181,17 @@ Here, last Monday is _today_ as a timestamp, minus 86400 times the current weekd
{% endraw %}
**Current month**: starts the first day of the current month at 00:00, ends right now.
{% raw %}
```yaml
start: "{{ now().replace(day=1, hour=0, minute=0, second=0, microsecond=0 ) }}"
end: "{{ now() }}"
```
{% endraw %}
**Next 4 pm**: 24 hours, from the last 4 pm till the next 4 pm. If it hasn't been 4 pm today, that would be 4 pm yesterday until 4 pm today. If it is already past 4 pm today, it will be 4 pm today until 4 pm tomorrow. When changing the start time, then add or subtract to the 8-hour buffer to match the next midnight.
{% raw %}

4
source/_integrations/homematicip_cloud.markdown
View File

@ -184,12 +184,12 @@ Within this delay the device registration should be completed in the App, otherw
## What to do, if a device is missing in Home Assistant
In order for a device to be integrated into Home Assistant, it must first be implemented in the upstream library. A dump of your configuration is required for this, which is then attached to a new issue in the [upstream lib's](https://github.com/coreGreenberet/homematicip-rest-api) GitHub repository.
In order for a device to be integrated into Home Assistant, it must first be implemented in the upstream library. A dump of your configuration is required for this, which is then attached to a new issue in the [upstream lib's](https://github.com/hahn-th/homematicip-rest-api) GitHub repository.
1. Create a dump of your access point configuration in Home Assistant:
Developer Tools -> Services -> Select `homematicip_cloud.dump_hap_config` -> Execute.
The default dump is anonymized and is written to your configuration directory (`hmip_config_XXXX.json`).
2. Create a [new issue](https://github.com/coreGreenberet/homematicip-rest-api/issues/new) at this GitHub repository and attach the created dump file.
2. Create a [new issue](https://github.com/hahn-th/homematicip-rest-api/issues/new) at this GitHub repository and attach the created dump file.
Please be patient, wait for the implementation and a new release of the upstream library.
Afterward, this device can be implemented into Home Assistant.

2
source/_integrations/ifttt.markdown
View File

@ -61,7 +61,7 @@ ifttt:
key: YOUR_API_KEY
```
`key` is your API key which can be obtained by viewing the **Settings** of the [Webhooks applet](https://ifttt.com/services/maker_webhooks/settings). It's the last part of the URL (e.g., https://maker.ifttt.com/use/MYAPIKEY) you will find under **My Applets** > **Webhooks** > **Settings**.
`key` is your API key which can be obtained by viewing the **Settings** of the [Webhooks applet](https://ifttt.com/maker_webhooks/settings). It's the last part of the URL (e.g., https://maker.ifttt.com/use/MYAPIKEY) you will find under **My Applets** > **Webhooks** > **Settings**.
![Property screen of the Maker Channel.](/images/integrations/ifttt/finding_key.png)
Once you have added your key to your `configuration.yaml` file, restart your Home Assistant instance. This will load up the IFTTT integration and make a service available to trigger events in IFTTT.

2
source/_integrations/imap.markdown
View File

@ -67,7 +67,7 @@ charset:
### Gmail with App Password
If you’re going to use Gmail, it’s always good practice to create a [App Password](https://support.google.com/mail/answer/185833?hl=en).
If you’re going to use Gmail, it’s always good practice to create a [App Password](https://support.google.com/mail/answer/185833).
1. Go to your [Google Account](https://myaccount.google.com/)
2. Select **Security**

2
source/_integrations/keyboard.markdown
View File

@ -34,6 +34,6 @@ pip3 install [package name]
### Windows
x64 Windows users may have trouble installing pywin through pip. Using an [executable installer](https://sourceforge.net/projects/pywin32/files/pywin32/) should work around this issue.
x64 Windows users may have trouble installing pywin through pip. Using an [executable installer](https://github.com/mhammond/pywin32) should work around this issue.
[Similar installers](https://www.lfd.uci.edu/~gohlke/pythonlibs/#pyhook) (unofficial) for pyhook have been ported to Python 3.4 and should help with x64 pip issues with pyhook.

37
source/_integrations/litterrobot.markdown
View File

@ -26,7 +26,7 @@ The Litter-Robot integration allows you to control and monitor your Wi-Fi-enable
You will need a Litter-Robot account as well as a Wi-Fi-enabled Litter-Robot unit that has already been associated with your account.
The Feeder-Robot is not currently supported by this integration.
The Feeder-Robot and Litter-Robot 4 are not currently supported by this integration.
{% include integrations/config_flow.md %}
@ -34,16 +34,18 @@ The Feeder-Robot is not currently supported by this integration.
The following entities are created for this component and identified by a single device per Litter-Robot unit:
| Entity | Domain | Description |
| ----------------------------- | -------- | -------------------------------------------------------------------------------- |
| Litter Box | `vacuum` | Main entity that represents a Litter-Robot unit. |
| Night Light Mode | `switch` | When turned on, automatically turns on the night light in darker settings. |
| Panel Lockout | `switch` | When turned on, disables the buttons on the unit to prevent changes to settings. |
| Sleep Mode Start Time | `sensor` | When sleep mode is enabled, displays the current or next sleep mode start time. |
| Sleep Mode End Time | `sensor` | When sleep mode is enabled, displays the current or last sleep mode end time. |
| Waste Drawer | `sensor` | Displays the current waste drawer level. |
| Clean Cycle Wait Time Minutes | `select` | View and select the clean cycle wait time. |
| Reset Waste Drawer | `button` | Button to reset the waste drawer level to 0%. |
| Entity | Domain | Description |
| ----------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Litter Box | `vacuum` | Main entity that represents a Litter-Robot unit. |
| Night Light Mode | `switch` | When turned on, automatically turns on the night light in darker settings. |
| Panel Lockout | `switch` | When turned on, disables the buttons on the unit to prevent changes to settings. |
| Last Seen | `sensor` | Displays the time the unit was last seen / reported an update. |
| Sleep Mode Start Time | `sensor` | When sleep mode is enabled, displays the current or next sleep mode start time. |
| Sleep Mode End Time | `sensor` | When sleep mode is enabled, displays the current or last sleep mode end time. |
| Status Code | `sensor` | Displays the status code (Clean Cycle in Progress, Ready, Drawer Full, etc). |
| Waste Drawer | `sensor` | Displays the current waste drawer level. |
| Clean Cycle Wait Time Minutes | `select` | View and select the clean cycle wait time. |
| Reset Waste Drawer | `button` | Button to reset the waste drawer level to 0%. |
## Additional Attributes
@ -51,14 +53,11 @@ Some entities have attributes in addition to the default ones that are available
### Litter Box `vacuum` entity
| Attribute | Type | Description |
| ----------------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| clean_cycle_wait_time_minutes | integer | Current wait time, in minutes, between when your cat uses the Litter-Robot and when the unit cycles automatically. |
| is_sleeping | boolean | Whether or not the unit is currently in sleep mode. |
| sleep_mode_enabled | boolean | Whether or not sleep mode is enabled. |
| power_status | string | Current power status of the unit. `AC` indicates normal power, `DC` indicates battery backup and `NC` indicates that the unit is not connected and/or powered off. |
| status_code | string | The [status code](https://github.com/natekspencer/pylitterbot/blob/884944b011f5fea9639b7d21d19fa3f7708e25a7/pylitterbot/enums.py#L44) associated with the current status of the vacuum. |
| last_seen | string | UTC datetime the unit last reported its status. |
| Attribute | Type | Description |
| ------------------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| is_sleeping | boolean | Whether or not the unit is currently in sleep mode. |
| sleep_mode_enabled | boolean | Whether or not sleep mode is enabled. |
| power_status | string | Current power status of the unit. `AC` indicates normal power, `DC` indicates battery backup and `NC` indicates that the unit is not connected and/or powered off. |
## Services

2
source/_integrations/lutron_caseta.markdown
View File

@ -51,7 +51,7 @@ When configured, the Lutron Caséta integration will automatically discover the
## Manual hub configuration
To use Lutron Caseta devices in your installation, you must first log in to your Lutron account and generate a certificate that allows Home Assistant to connect to your bridge. This can be accomplished by downloading and executing [get_lutron_cert.py](https://github.com/gurumitts/pylutron-caseta/blob/master/get_lutron_cert.py), which will generate three files: caseta.key, caseta.crt, caseta-bridge.crt when you run it. See the instructions at the top of the script for more information.
To use Lutron Caseta devices in your installation, you must first log in to your Lutron account and generate a certificate that allows Home Assistant to connect to your bridge. This can be accomplished by following the [steps here](https://github.com/gurumitts/pylutron-caseta/tree/master#getting-started), which will generate three files: caseta.key, caseta.crt, caseta-bridge.crt when you run it.
If you already have `caseta.key`, `caseta.crt`, `caseta-bridge.crt`, and cannot physically access the bridge to press the button, pairing can be done by utilizing these existing files.

43
source/_integrations/nest.markdown
View File

@ -44,12 +44,15 @@ The Nest Smart Device Management (SDM) API **requires a US$5 fee**.
</div>
<lite-youtube videoid="RwZmQ7QfhsM" videotitle="Finally! A WORKING NEST Integration with Home Assistant using Oauth!" posterquality="maxresdefault"></lite-youtube>
## Configuration
Adding Nest to your Home Assistant instance can be done via the user interface, by using this My Button:
{% my config_flow_start badge domain=page.ha_domain %}
![Screenshot of Setup prompt](/images/integrations/nest/setup_prompt.png)
{% details "Manual configuration steps" %}
1. Browse to your Home Assistant instance.
@ -182,9 +185,14 @@ Now that you have authentication configured, you will create a Nest Device Acces
In this section you will authorize Home Assistant to access your account by generating an *Authentication Token*.
Note that *OAuth for Auth* has been [deprecated](https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html) by Google and will break by October 2022.
See [Troubleshooting](#troubleshooting) below for steps to resolve the common misconfigurations that result in errors such as *Can't link...* or *Error 400* from Google.
1. A new tab opens, allowing you to choose a Google account. This should be the same developer account you configured above.
Note that *OAuth for Apps* has been [deprecated](https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html) by Google and will break by October 2022.
1. In Home Assistant, you should already be going through the setup flow. If not, go back and click the *My: Add Integration* button above to start the setup. The integration will ask you for all of the necessary integration configuration.
1. Once all configuration information is entered in Home Assistant, a new tab opens, allowing you to choose a Google account. This should be the same developer account you configured above.
1. The *Google Nest permissions* screen will allow you to choose which devices to configure and lets you select devices from multiple homes. You likely want to enable everything, however, you can leave out any feature you do not wish to use with Home Assistant.
@ -410,14 +418,23 @@ This feature is enabled by the following permissions:
## Deprecated App Auth Credentials
To improve security and reduce phishing risk Google has [deprecated](https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html) a previous authentication method used by Home Assistant. **This requires action by you to resolve.**
To improve security and reduce phishing risk Google has [deprecated](https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html) a previous authentication method used by Home Assistant. **This requires action by you to resolve** if you previously configured *Nest* using *App Auth*.
{% details "Reconfigure the integration %}
1. Make sure to upgrade to the latest version of Home Assistant.
1. In the sidebar click on _**{% my config icon %}**_.
1. From the configuration menu select: _**{% my integrations %}**_.
1. The *Nest* integration should appear with alert. Click **Reconfigure**.
1. The *Nest* integration should appear with alert.
![Screenshot of success](/images/integrations/nest/attention.png)
1. Click **Reconfigure**.
![Screenshot of success](/images/integrations/nest/deprecation.png)
If the *Nest* integration does not have an Alert then you probably used *Web Auth* and have nothing to do.
{% enddetails %}
@ -432,7 +449,7 @@ To improve security and reduce phishing risk Google has [deprecated](https://dev
1. Pick a new name for your credential.
1. Add **Authorized redirect URIs** end enter `https://my.home-assistant.io/redirect/oauth`
1. Click *Create* to create the credential.
1. You now have *OAuth Client ID* and *OAuth Client Secret* needed by Home Assistant.
1. You now have *OAuth Client ID* and *OAuth Client Secret* needed by Home Assistant.
1. Back in Home Assistant, you should now be prompted to create [Application Credentials](/integrations/application_credentials) where you will enter the *Client ID* and *Client Secret*.
{% enddetails %}
@ -486,7 +503,21 @@ authentication process.
- *Something went wrong: Please contact the developer of this app if the issue persists*: This typically means you are using the wrong type of credential (e.g. *Desktop Auth*). Make sure the credential in the [Google Cloud Console](https://console.developers.google.com/apis/credentials) is a *Web Application* credential following the instructions above.
- *Can’t link to Home Assistant Local Dev: Please contact Home Assistant Local Dev if the issue persists* : This typically means that the [Device Access Project](https://console.nest.google.com/device-access/project-list) is set up with on old or incorrect *OAuth Client ID*
- *Can’t link to [Project Name]: Please contact [Project Name] if the issue persists*: This typically means that the *OAuth Client ID* used is mismatched
{% details "Resolving mismatched OAuth Client ID" %}
The *OAuth Client ID* used must be consistent, so check these:
- [Google Cloud Console](https://console.cloud.google.com/apis/credentials) - See instructions above to create new Web Auth OAuth Credentials if needed
- [Device Access Project](https://console.nest.google.com/device-access/project-list) - The OAuth Client ID for your Device Access Project must refer to the Web Auth OAuth Client ID in the Google Cloud Console
- Make sure you are using the same Google Account in the Device Access Console and Google Cloud Console e.g. double-check the photo and account name in the top right of the screen
- [Application Credentials](/integrations/application_credentials/) - Home Assistant needs to be configured with the same credentials. Delete any existing entries if they do not match, then either manually enter or re-enter as part of the setup.
![Screenshot of success](/images/integrations/nest/application_credentials.png)
{% enddetails %}
- *Reauthentication required often*: If you are getting logged out every 7 days, this means an OAuth Consent Screen misconfiugration or your authentication token was revoked by Google for some other reason.

3
source/_integrations/overkiz.markdown
View File

@ -56,6 +56,7 @@ The Overkiz (by Somfy) integration platform is used by many different vendors, l
- Somfy Connexoon RTS
- Somfy TaHoma
- Somfy TaHoma Switch [(instructions)](#tahoma-switch)
- Somfy Connection Kit
- Thermor Cozytouch
### TaHoma Switch
@ -86,4 +87,4 @@ This integration communicates via the cloud-based Overkiz API, since Overkiz doe
#### Local API via HomeKit Controller
If your hub (e.g. Somfy TaHoma) supports HomeKit natively, your setup code will be added as a sensor in Home Assistant. Look up your hub in Home Assistant and retrieve the value from the 'HomeKit Setup Code' sensor. You can now configure the [HomeKit Controller](/integrations/homekit_controller/) integration in Home Assistant and benefit from local support.
If your hub (e.g. Somfy TaHoma or Somfy Connection Kit) supports HomeKit natively, your setup code will be added as a sensor in Home Assistant. Look up your hub in Home Assistant and retrieve the value from the 'HomeKit Setup Code' sensor. You can now configure the [HomeKit Controller](/integrations/homekit_controller/) integration in Home Assistant and benefit from local support.

2
source/_integrations/simplepush.markdown
View File

@ -14,7 +14,7 @@ ha_codeowners:
- '@engrbm87'
---
The `simplepush` platform uses [Simplepush](https://simplepush.io/) to delivery notifications from Home Assistant to your Android device. Unlike similar apps the Simplepush app requires no registration.
The `simplepush` platform uses [Simplepush](https://simplepush.io/) to deliver notifications from Home Assistant to your Android device. Unlike similar apps the Simplepush app requires no registration.
{% include integrations/config_flow.md %}

182
source/_integrations/smartthings.markdown
View File

@ -97,7 +97,7 @@ The SmartThings integration triggers events for select device capabilities.
### smartthings.button
The integration will trigger an event when a device with the [button](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Button) capability is actuated and can be used to trigger automations within Home Assistant. Below is an example of the data payload:
The integration will trigger an event when a device with the [button](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#button) capability is actuated and can be used to trigger automations within Home Assistant. Below is an example of the data payload:
```json
{
@ -114,14 +114,14 @@ The integration will trigger an event when a device with the [button](https://sm
| `component_id` | Describes which integration of the device triggered the event. `main` represents the parent device. For devices with child-devices, this attribute identifies the child that raised the event. |
| `device_id` | The unique id of the device in SmartThings. This can be located in the Home Assistant device registry or in the [SmartThings Developer Workspace](https://smartthings.developer.samsung.com/workspace/). |
| `location_id` | The unique id of the location the device is part of. This can be found in the configuration entry registry or in the [SmartThings Developer Workspace](https://smartthings.developer.samsung.com/workspace/). |
| `value` | Describes the action taken on the button. See the [button](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Button) capability reference for a list of possible values (not all are supported by every device). |
| `value` | Describes the action taken on the button. See the [button](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#button) capability reference for a list of possible values (not all are supported by every device). |
| `name` | The name given to the device in SmartThings. |
Event data payloads are logged at the debug level, see [debugging](#debugging) for more information.
## Platforms
SmartThings represents devices as a set of [capabilities](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html) and the SmartThings integration maps those to entity platforms in Home Assistant. A single device may be represented by one or more platforms.
SmartThings represents devices as a set of [capabilities](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities) and the SmartThings integration maps those to entity platforms in Home Assistant. A single device may be represented by one or more platforms.
- [Binary Sensor](#binary-sensor)
- [Climate](#climate)
@ -141,14 +141,14 @@ The SmartThings Binary Sensor platform lets you view devices that have binary se
| Capability | Attribute | On-Value |
| ----------------------------------------------------------------------------------------------------------------------- | -------------- | ---------- |
| [`accelerationSensor`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Acceleration-Sensor) | `acceleration` | `active` |
| [`contactSensor`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Contact-Sensor) | `contact` | `open` |
| [`filterStatus`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Filter-Status) | `filterStatus` | `replace` |
| [`motionSensor`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Motion-Sensor) | `motion` | `active` |
| [`presenceSensor`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Presence-Sensor) | `presence` | `present` |
| [`tamperAlert`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Tamper-Alert) | `tamper` | `detected` |
| [`valve`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Valve) | `valve` | `open` |
| [`waterSensor`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Water-Sensor) | `water` | `wet` |
| [`accelerationSensor`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#accelerationSensor) | `acceleration` | `active` |
| [`contactSensor`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#contactSensor) | `contact` | `open` |
| [`filterStatus`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#filterStatus) | `filterStatus` | `replace` |
| [`motionSensor`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#motionSensor) | `motion` | `active` |
| [`presenceSensor`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#presenceSensor) | `presence` | `present` |
| [`tamperAlert`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#tamperAlert) | `tamper` | `detected` |
| [`valve`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#valve) | `valve` | `open` |
| [`waterSensor`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#waterSensor) | `water` | `wet` |
### Climate
@ -160,11 +160,11 @@ For a SmartThings Air Conditioner to be represented by the climate platform, it
| Capability | Climate Features |
| ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`airConditionerMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Air-Conditioner-Mode) (required) | `hvac mode`, `hvac action` |
| `airConditionerFanMode` (required) | `fan mode` |
| [`temperatureMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Temperature-Measurement) (required) | `temperature` |
| [`thermostatCoolingSetpoint`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Cooling-Setpoint) (required) | `target temp` |
| [`demandResponseLoadControl`](https://docs.smartthings.com/en/latest/capabilities-reference.html#demand-response-load-control) | `drlc_status_duration` (state attribute), `drlc_status_level` (state attribute), `drlc_status_override` (state attribute), `drlc_status_start` (state attribute) |
| [`airConditionerMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#airConditionerMode) (required) | `hvac mode`, `hvac action` |
| [`airConditionerFanMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#airConditionerFanMode) (required) | `fan mode` |
| [`temperatureMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#temperatureMeasurement) (required) | `temperature` |
| [`thermostatCoolingSetpoint`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatCoolingSetpoint) (required) | `target temp` |
| [`demandResponseLoadControl`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#demandResponseLoadControl) | `drlc_status_duration` (state attribute), `drlc_status_level` (state attribute), `drlc_status_override` (state attribute), `drlc_status_start` (state attribute) |
#### Thermostats
@ -172,14 +172,14 @@ For a SmartThings thermostat to be represented by the climate platform, it must
| Capability | Climate Features |
| ---------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| [`thermostat`](https://docs.smartthings.com/en/latest/capabilities-reference.html#thermostat) (set a) | `hvac mode`, `hvac action`, `target temp high`, `target temp low` and `fan mode` |
| [`thermostatMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Mode) (set b) | `hvac mode` |
| [`thermostatCoolingSetpoint`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Cooling-Setpoint) (seb b) | `target temp low` |
| [`thermostatHeatingSetpoint`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Heating-Setpoint) (set b) | `target temp high` |
| [`temperatureMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Temperature-Measurement) (set b) |
| [`thermostatOperatingState`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Operating-State) | `hvac action` |
| [`thermostatFanMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Fan-Mode) | `fan mode` |
| [`relativeHumidityMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Relative-Humidity-Measurement) | `humidity` (state attribute) |
| [`thermostat`](https://developer-preview.smartthings.com/docs/devices/capabilities/deprecated#thermostat) (set a) | `hvac mode`, `hvac action`, `target temp high`, `target temp low` and `fan mode` |
| [`thermostatMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatMode) (set b) | `hvac mode` |
| [`thermostatCoolingSetpoint`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatCoolingSetpoint) (seb b) | `target temp low` |
| [`thermostatHeatingSetpoint`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatHeatingSetpoint) (set b) | `target temp high` |
| [`temperatureMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#temperatureMeasurement) (set b) |
| [`thermostatOperatingState`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatOperatingState) | `hvac action` |
| [`thermostatFanMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatFanMode) | `fan mode` |
| [`relativeHumidityMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#relativeHumidityMeasurement) | `humidity` (state attribute) |
### Cover
@ -187,11 +187,11 @@ The SmartThings Cover platform lets you control devices that have open/close rel
| Capability | Cover Features |
| ------------------------------------------------------------------------------------------------------------------------------ | --------------------------------- |
| [`doorControl`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Door-Control) (set a) | `open` and `close` |
| [`garageDoorControl`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Garage-Door-Control) (seb a) | `open` and `close` |
| [`windowShade`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Window-Shade) (set a) | `open` and `close` |
| [`switchLevel`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Switch-Level) | `position` |
| [`battery`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Battery) | `battery_level` (state attribute) |
| [`doorControl`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#doorControl) (set a) | `open` and `close` |
| [`garageDoorControl`](https://developer-preview.smartthings.com/docs/devices/capabilities/deprecated#garageDoorControl) (seb a) | `open` and `close` |
| [`windowShade`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#windowShade) (set a) | `open` and `close` |
| [`switchLevel`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#switchLevel) | `position` |
| [`battery`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#battery) | `battery_level` (state attribute) |
### Fan
@ -199,7 +199,7 @@ The SmartThings Fan platform lets you control devices that have fan-related capa
| Capability | Fan Features |
| --------------------------------------------------------------------------------------------------- | -------------------------------------------- |
| [`fanSpeed`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Fan-Speed) | `speed` (`off`, `low`, `medium`, and `high`) |
| [`fanSpeed`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#fanSpeed) | `speed` (`off`, `low`, `medium`, and `high`) |
### Light
@ -207,13 +207,13 @@ The SmartThings Light platform lets you control devices that have light-related
| Capability | Light Features |
| ------------------------------------------------------------------------------------------------------------------- | ----------------------------- |
| [`switchLevel`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Switch-Level) | `brightness` and `transition` |
| [`colorControl`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Color-Control) | `color` |
| [`colorTemperature`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Color-Temperature) | `color_temp` |
| [`switchLevel`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#switchLevel) | `brightness` and `transition` |
| [`colorControl`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#colorControl) | `color` |
| [`colorTemperature`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#colorTemperature) | `color_temp` |
### Lock
The SmartThings Lock platform lets you control devices that have the [`lock`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Lock) capability, showing current lock status and supporting lock and unlock commands.
The SmartThings Lock platform lets you control devices that have the [`lock`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#lock) capability, showing current lock status and supporting lock and unlock commands.
### Sensor
@ -221,60 +221,60 @@ The SmartThings Sensor platform lets your view devices that have sensor-related
| Capability | Attributes |
| --------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
| [`activityLightingMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Activity-Lighting-Mode) | `lightingMode` |
| [`airConditionerMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Air-Conditioner-Mode) | `airConditionerMode` |
| [`airQualitySensor`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Air-Quality-Sensory) | `airQuality` |
| [`alarm`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Alarm) | `alarm` |
| [`audioVolume`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Audio-Volume) | `volume` |
| [`battery`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Battery) | `battery` |
| [`bodyMassIndexMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Body-Mass-Index-Measurement) | `bmiMeasurement` |
| [`bodyWeightMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Body-Weight-Measurement) | `bodyWeightMeasurement` |
| [`carbonDioxideMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Carbon-Dioxide-Measurement) | `carbonDioxide` |
| [`carbonMonoxideDetector`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Carbon-Monoxide-Detector) | `carbonMonoxide` |
| [`carbonMonoxideMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Carbon-Monoxide-Measurement) | `carbonMonoxideLevel` |
| [`dishwasherOperatingState`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Dishwasher-Operating-State) | `machineState`, `dishwasherJobState` and `completionTime` |
| [`dryerMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Dryer-Mode) | `dryerMode` |
| [`dryerOperatingState`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Dryer-Operating-State) | `machineState`, `dryerJobState` and `completionTime` |
| [`dustSensor`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Dust-Sensor) | `fineDustLevel` and `dustLevel` |
| [`energyMeter`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Energy-Meter) | `energy` |
| [`equivalentCarbonDioxideMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Equivalent-Carbon-Dioxide-Measurement) | `equivalentCarbonDioxideMeasurement` |
| [`formaldehydeMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Formaldehyde-Measurement) | `formaldehydeLevel` |
| `gasMeter` | `gasMeter`, `meterCalorific`, `meterTime`, and `meterVolume` |
| [`illuminanceMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Illuminance-Measurement) | `illuminance` |
| [`infraredLevel`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Infrared-Level) | `infraredLevel` |
| [`lock`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Lock) | `lock` |
| [`mediaInputSource`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Media-Input-Source) | `inputSource` |
| [`mediaPlaybackRepeat`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Media-Playback-Repeat) | `playbackRepeatMode` |
| [`mediaPlaybackShuffle`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Media-Playback-Shuffle) | `playbackShuffle` |
| [`mediaPlayback`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Media-Playback) | `playbackStatus` |
| [`odorSensor`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Odor-Sensor) | `odorLevel` |
| [`ovenMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Oven-Mode) | `ovenMode` |
| [`ovenOperatingState`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Oven-Operating-State) | `machineState`, `ovenJobState` and `completionTime` |
| [`ovenSetpoint`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Oven-Setpoint) | `ovenSetpoint` |
| [`powerConsumptionReport`](https://docs.smartthings.com/en/latest/capabilities-reference.html#power-consumption-report) | `deltaEnergy`, `energy`, `energySaved`, `power`, `powerEnergy` |
| [`powerMeter`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Power-Meter) | `power` |
| [`powerSource`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Power-Source) | `powerSource` |
| [`refrigerationSetpoint`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Refrigeration-Setpoint) | `refrigerationSetpoint` |
| [`relativeHumidityMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Relative-Humidity-Measurement) | `humidity` |
| [`robotCleanerCleaningMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Robot-Cleaner-CleaningMode) | `robotCleanerCleaningMode` |
| [`robotCleanerMovement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Robot-Cleaner-Movement) | `robotCleanerMovement` |
| [`robotCleanerTurboMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Robot-Cleaner-Turbo-Mode) | `robotCleanerTurboMode` |
| [`signalStrength`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Signal-Strength) | `lqi` and `rssi` |
| [`smokeDetector`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Smoke-Detector) | `smoke` |
| [`temperatureMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Temperature-Measurement) | `temperature` |
| [`thermostatCoolingSetpoint`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Cooling-Setpoint) | `coolingSetpoint` |
| [`thermostatFanMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Fan-Mode) | `thermostatFanMode` |
| [`thermostatHeatingSetpoint`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Heating-Setpoint) | `heatingSetpoint` |
| [`thermostatMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Mode) | `thermostatMode` |
| [`thermostatOperatingState`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Operating-State) | `thermostatOperatingState` |
| [`thermostatSetpoint`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Thermostat-Setpoint) | `thermostatSetpoint` |
| [`threeAxis`](https://docs.smartthings.com/en/latest/capabilities-reference.html#three-axis) | `threeAxis` (as discrete sensors `X`, `Y` and `Z`) |
| [`tvChannel`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Tv-Channel) | `tvChannel` and `tvChannelName` |
| [`tvocMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Tvoc-Measurement) | `tvocLevel` |
| [`ultravioletIndex`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Ultraviolet-Index) | `ultravioletIndex` |
| [`voltageMeasurement`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Voltage-Measurement) | `voltage` |
| [`washerMode`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Washer-Mode) | `washerMode` |
| [`washerOperatingState`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Washer-Operating-State) | `machineState`, `washerJobState` and `completionTime` |
| [`activityLightingMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#activityLightingMode) | `lightingMode` |
| [`airConditionerMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#airConditionerMode) | `airConditionerMode` |
| [`airQualitySensor`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#airQualitySensor) | `airQuality` |
| [`alarm`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#alarm) | `alarm` |
| [`audioVolume`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#audioVolume) | `volume` |
| [`battery`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#battery) | `battery` |
| [`bodyMassIndexMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#bodyMassIndexMeasurement) | `bmiMeasurement` |
| [`bodyWeightMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#bodyWeightMeasurement) | `bodyWeightMeasurement` |
| [`carbonDioxideMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#carbonDioxideMeasurement) | `carbonDioxide` |
| [`carbonMonoxideDetector`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#carbonMonoxideDetector) | `carbonMonoxide` |
| [`carbonMonoxideMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#carbonMonoxideMeasurement) | `carbonMonoxideLevel` |
| [`dishwasherOperatingState`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#dishwasherOperatingState) | `machineState`, `dishwasherJobState` and `completionTime` |
| [`dryerMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#dryerMode) | `dryerMode` |
| [`dryerOperatingState`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#dryerOperatingState) | `machineState`, `dryerJobState` and `completionTime` |
| [`dustSensor`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#dustSensor) | `fineDustLevel` and `dustLevel` |
| [`energyMeter`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#energyMeter) | `energy` |
| [`equivalentCarbonDioxideMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#equivalentCarbonDioxideMeasurement) | `equivalentCarbonDioxideMeasurement` |
| [`formaldehydeMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#formaldehydeMeasurement) | `formaldehydeLevel` |
| [`gasMeter`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#gasMeter) | `gasMeter`, `meterCalorific`, `meterTime`, and `meterVolume` |
| [`illuminanceMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#illuminanceMeasurement) | `illuminance` |
| [`infraredLevel`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#infraredLevel) | `infraredLevel` |
| [`lock`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#lock) | `lock` |
| [`mediaInputSource`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#mediaInputSource) | `inputSource` |
| [`mediaPlaybackRepeat`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#mediaPlaybackRepeat) | `playbackRepeatMode` |
| [`mediaPlaybackShuffle`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#mediaPlaybackShuffle) | `playbackShuffle` |
| [`mediaPlayback`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#mediaPlayback) | `playbackStatus` |
| [`odorSensor`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#odorSensor) | `odorLevel` |
| [`ovenMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#ovenMode) | `ovenMode` |
| [`ovenOperatingState`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#ovenOperatingState) | `machineState`, `ovenJobState` and `completionTime` |
| [`ovenSetpoint`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#ovenSetpoint) | `ovenSetpoint` |
| [`powerConsumptionReport`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#powerConsumptionReport) | `deltaEnergy`, `energy`, `energySaved`, `power`, `powerEnergy` |
| [`powerMeter`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#powerMeter) | `power` |
| [`powerSource`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#powerSource) | `powerSource` |
| [`refrigerationSetpoint`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#refrigerationSetpoint) | `refrigerationSetpoint` |
| [`relativeHumidityMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#relativeHumidityMeasurement) | `humidity` |
| [`robotCleanerCleaningMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#robotCleanerCleaningMode) | `robotCleanerCleaningMode` |
| [`robotCleanerMovement`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#robotCleanerMovement) | `robotCleanerMovement` |
| [`robotCleanerTurboMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#robotCleanerTurboMode) | `robotCleanerTurboMode` |
| [`signalStrength`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#signalStrength) | `lqi` and `rssi` |
| [`smokeDetector`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#smokeDetector) | `smoke` |
| [`temperatureMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#temperatureMeasurement) | `temperature` |
| [`thermostatCoolingSetpoint`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatCoolingSetpoint) | `coolingSetpoint` |
| [`thermostatFanMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatFanMode) | `thermostatFanMode` |
| [`thermostatHeatingSetpoint`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatHeatingSetpoint) | `heatingSetpoint` |
| [`thermostatMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatMode) | `thermostatMode` |
| [`thermostatOperatingState`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#thermostatOperatingState) | `thermostatOperatingState` |
| [`thermostatSetpoint`](https://developer-preview.smartthings.com/docs/devices/capabilities/deprecated#thermostatSetpoint) | `thermostatSetpoint` |
| [`threeAxis`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#threeAxis) | `threeAxis` (as discrete sensors `X`, `Y` and `Z`) |
| [`tvChannel`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#tvChannel) | `tvChannel` and `tvChannelName` |
| [`tvocMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#tvocMeasurement) | `tvocLevel` |
| [`ultravioletIndex`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#ultravioletIndex) | `ultravioletIndex` |
| [`voltageMeasurement`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#voltageMeasurement) | `voltage` |
| [`washerMode`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#washerMode) | `washerMode` |
| [`washerOperatingState`](https://developer-preview.smartthings.com/docs/devices/capabilities/proposed#washerOperatingState) | `machineState`, `washerJobState` and `completionTime` |
### Scene
@ -282,12 +282,12 @@ The SmartThings Scene platform lets you activate scenes defined in SmartThings w
### Switch
The SmartThings Switch platform lets you control devices that have the [`switch`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Switch) capability that are not already represented by a more specific platform. The following optional capabilities will provide energy and power utilization information:
The SmartThings Switch platform lets you control devices that have the [`switch`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#switch) capability that are not already represented by a more specific platform. The following optional capabilities will provide energy and power utilization information:
| Capability | Switch Features |
| --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| [`energyMeter`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Energy-Meter) | energy consumption (`today_energy_kwh` state attribute) |
| [`powerMeter`](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Power-Meter) | power consumption (`current_power_w` state attribute) |
| [`energyMeter`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#energyMeter) | energy consumption (`today_energy_kwh` state attribute) |
| [`powerMeter`](https://developer-preview.smartthings.com/docs/devices/capabilities/capabilities-reference#powerMeter) | power consumption (`current_power_w` state attribute) |
## Troubleshooting

2
source/_integrations/unifiprotect.markdown
View File

@ -136,7 +136,7 @@ and in many cases, get a read-only sensor instead of an editable switch/select/n
**Smart Detections**: The following cameras have Smart Detections:
* All "AI" series cameras. This includes the AI 360 and the AI Bullet.
* All "G4" series cameras _except_ the G4 Instant. This includes the G4 Doorbell, G4 Bullet and G4 Pro.
* All "G4" series cameras. This includes the G4 Doorbell, G4 Bullet, G4 Pro and G4 Instant.
G3 Series cameras do _not_ have Smart detections.

6
source/_integrations/wemo.markdown
View File

@ -30,8 +30,8 @@ There is currently support for the following device types within Home Assistant:
- Binary Sensor
- Fan (Belkin WeMo (Holmes) Smart Humidifier)
- Light (Belkin WeMo LED lights and [Smart Dimmer Switch](https://www.belkin.com/us/F7C059-Belkin/p/P-F7C059/))
- Switch ([Belkin WeMo Switches](https://www.belkin.com/us/Products/home-automation/c/wemo-home-automation/) and includes support for WeMo enabled [Mr. Coffee](https://www.mrcoffee.com/wemo-landing-page.html) smart coffee makers.)
- Light (Belkin WeMo LED lights and [Smart Dimmer Switch](https://www.belkin.com/smart-home/wemo/wemo-wifi-smart-dimmer/p/p-wds060/))
- Switch ([Belkin WeMo Switches](https://www.belkin.com/us/smart-home/c/wemo/) and includes support for WeMo enabled [Mr. Coffee](https://www.mrcoffee.com/) smart coffee makers.)
## Configuration
@ -87,7 +87,7 @@ wemo:
## Fan
The `wemo` platform allows you to control your Belkin WeMo humidifiers from within Home Assistant. This includes support for the [Holmes Smart Humidifier](https://www.holmesproducts.com/wemo-humidifier.html).
The `wemo` platform allows you to control your Belkin WeMo humidifiers from within Home Assistant. This includes support for the Holmes Smart Humidifier.
WeMo devices are automatically discovered if the `discovery` integration is enabled.

4
source/_integrations/wiz.markdown
View File

@ -46,10 +46,12 @@ These devices have been sold under at least the following brands:
- [Laurie Lumiere](https://www.laurielumiere.com/)
- [Lednify](https://lednify.com/)
- [Leyton](https://www.leyton-lighting.co.uk/)
- [Liteline](https://www.liteline.com/)
- [Liteline](https://www.liteline.com/page/oncloud)
- [Lutec](https://www.lutec.com/highlight/wiz)
- [Philips Smart LED lights with WiZ Connected](https://www.usa.lighting.philips.com/consumer/smart-wifi-led)
- [Spex](https://spexlighting.com/pages/smart-lights)
- [SLV](https://www.slv.com/)
- [Trenz](https://trenzlighting.com/pages/smart-lights)
- [Trio](https://wiz.trio-lighting.com/en/)
- [Wofi](https://wofi-wiz.com/)

4
source/_integrations/xiaomi_miio.markdown
View File

@ -1487,7 +1487,7 @@ Main Brush Left*:
Sensor Dirty Left*:
description: How long the sensor can be used in seconds
Current Clean Time:
description: The current cleaning time of the vacuum. If the vaccuum is not cleaning, this sensor will have the same value as the "Last Clean Duration" sensor.
description: The current cleaning time of the vacuum. If the vacuum is not cleaning, this sensor will have the same value as the "Last Clean Duration" sensor.
Current Clean Area:
description: The current area that has been cleaned. If the vacuum is not cealning, this sensor will have the same value as the "Last Clean Area" sensor.
Last Clean Area*:
@ -1594,7 +1594,7 @@ vacuum_kitchen:
Valid room numbers can be retrieved using miio command-line tool:
```bash
miiocli vacuum --ip <ip of the vacuum> --token <your vacuum token> get_room_mapping
miiocli roborockvacuum --ip <ip of the vacuum> --token <your vacuum token> get_room_mapping
```
It will return the full mapping of room numbers to user-defined names as a list of (number,name) tuples.

2
source/_integrations/zha.markdown
View File

@ -44,7 +44,7 @@ ha_zeroconf: true
ha_integration_type: integration
---
The ZHA (Zigbee Home Automation) integration allows you to connect many off-the-shelf [Zigbee based devices](https://zigbeealliance.org) directly to Home Assistant, using one of the many available Zigbee coordinators.
The ZHA (Zigbee Home Automation) integration allows you to connect many off-the-shelf [Zigbee based devices](https://csa-iot.org/) directly to Home Assistant, using one of the many available Zigbee coordinators.
ZHA uses an open-source Python library implementing a hardware-independent Zigbee stack called [zigpy](https://github.com/zigpy/zigpy). All coordinators compatible with zigpy can be used with ZHA.

13
source/_posts/2022-05-04-release-20225.markdown
View File

@ -1225,6 +1225,19 @@ This makes the discovery of LIFX faster and more reliable.
{% enddetails %}
{% details "Media Player" %}
Media Player now supports a new state, `buffering`. Integrations supporting this state previously reported `playing` but may now report `buffering`. This may also introduce new state transitions between the two states during playback.
In order to maintain previous behavior, replace usage of `playing` with both the `buffering` and `playing` states, and consider how to handle transitions between the two.
([@emontnemery] - [#70863]) ([documentation](/integrations/media_player))
[@emontnemery]: [https://github.com/emontnemery]
[#70863]: https://github.com/home-assistant/core/pull/70863
{% enddetails %}
{% details "Media Source" %}
Filenames and directories starting with a `.` will no longer appear in the

349
source/_posts/2022-07-06-release-20227.markdown
View File

@ -29,7 +29,7 @@ the soon-to-be-released [Home Assistant Yellow]! 💛 More about that soon™.
This release is definitely representing the "streamlining experiences"
motto we have been using. The performance improvements in this release are
once more: stunning! Furthermore, there are some wonderful new features to
explore too.
explore too.
This release has the perfect mix! I'm sure there is something in here you
like. So without further due: Enjoy the release!
@ -51,6 +51,11 @@ like. So without further due: Enjoy the release!
- [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.7.1 - July 7](#release-202271---july-7)
- [Release 2022.7.2 - July 8](#release-202272---july-8)
- [Release 2022.7.3 - July 10](#release-202273---july-10)
- [Release 2022.7.4 - July 13](#release-202274---july-13)
- [Release 2022.7.5 - July 14](#release-202275---july-14)
- [Need help? Join the community!](#need-help-join-the-community)
- [Breaking Changes](#breaking-changes)
- [Farewell to the following](#farewell-to-the-following)
@ -159,9 +164,8 @@ Home Assistant will take care of converting the values for you.
<img class="no-shadow" src='/images/blog/2022-07/weather-units.png' alt='Screenshot showing energy usage being compared from last week with the week before that'>
As a bonus, this same unit-changing feature is added to the number entities
that represent a temperature. For those number entities, you can now change
the units from Celsius to Fahrenheit (and the other way around).
On a similar note, number entities that represent a temperature are now converted to
the temperature unit used by the configured unit system.
Thanks [@emontnemery] and [@gjohansson-ST] for adding this and updating
all existing weather integrations to support this 👍.
@ -269,10 +273,10 @@ noteworthy changes this release:
locks, and vibration, CO, and Smoke Sensors!
- [Jellyfin] now supports movie collections in the media browser, thanks [@j-stienstra]!
- Thanks to [@dmulcahey], the widely discussed Aqara FP1 sensor is now
supported by [ZHA]!
supported by [ZHA]!
- [@ghedo] has been busy improving the [Area Card]. It can now show
moisture/flood alerts, humidity, and shows an icon for temperature. Nice!
- [@king444] added support for Top/Down, Bottom/Up to [Hunter Douglas PowerView].
- [@kingy444] added support for Top/Down, Bottom/Up to [Hunter Douglas PowerView].
Additionally, buttons to calibrate and jog (identify) have been added. [@bdraco]
added support for polling in case the device is mains powered.
- Thanks to [@thrawnarn], you can now send polls via [Telegram bot]!
@ -294,7 +298,7 @@ noteworthy changes this release:
[@iAutom8]: https://github.com/@iAutom8
[@j-stienstra]: https://github.com/j-stienstra
[@jjlawren]: https://github.com/jjlawren
[@king444]: https://github.com/king444
[@kingy444]: https://github.com/kingy444
[@matrixd2]: https://github.com/matrixd2
[@mdegat01]: https://github.com/mdegat01
[@thrawnarn]: https://github.com/thrawnarn
@ -333,6 +337,301 @@ The following integrations are now available via the Home Assistant UI:
[Simplepush]: /integrations/simplepush
[SkyBell]: /integrations/skybell
## Release 2022.7.1 - July 7
- Bump deCONZ dependency to v96 ([@Kane610] - [#74460]) ([deconz docs])
- Bump satel_integra to 0.3.7 to fix compat with python 3.10 ([@c-soft] - [#74543]) ([satel_integra docs])
- fjaraskupan: Make sure we stop bleak on home assistant stop ([@elupus] - [#74545]) ([fjaraskupan docs])
- Minimize Sonos `media_player.unjoin` timeout ([@jjlawren] - [#74549]) ([sonos docs])
- Bump aioskybell to 22.7.0 ([@tkdrob] - [#74559]) ([skybell docs])
- Bump pyenvisalink version to 4.6 ([@ufodone] - [#74561]) ([envisalink docs])
- ElkM1 bump lib to support Python 3.10 SSL ([@gwww] - [#74569]) ([elkm1 docs])
- Fix openweathermap hourly forecast ([@emontnemery] - [#74578]) ([openweathermap docs])
- Fix mix of aiohttp and requests in Bloomsky ([@frenck] - [#74598]) ([bloomsky docs])
- Update aiokafka to 0.7.2 ([@frenck] - [#74601]) ([apache_kafka docs])
- Poll cast groups when media player is added or reconnected ([@emontnemery] - [#74610]) ([cast docs])
- Ikea Starkvind support all models ([@arnemauer] - [#74615]) ([zha docs])
- Update frontend to 20220707.0 ([@bramkragten] - [#74625]) ([frontend docs])
- Fix mix of aiohttp and requests in ZAMG ([@frenck] - [#74628]) ([zamg docs])
- Fix smart energy polling for Tuya plugs ([@TheJulianJES] - [#74640]) ([zha docs])
- Fix exception in doorbird logbook during startup ([@bdraco] - [#74649]) ([doorbird docs])
- Update kaiterra-async-client to 1.0.0 ([@Michsior14] - [#74677]) ([kaiterra docs])
[#74460]: https://github.com/home-assistant/core/pull/74460
[#74543]: https://github.com/home-assistant/core/pull/74543
[#74545]: https://github.com/home-assistant/core/pull/74545
[#74549]: https://github.com/home-assistant/core/pull/74549
[#74559]: https://github.com/home-assistant/core/pull/74559
[#74561]: https://github.com/home-assistant/core/pull/74561
[#74569]: https://github.com/home-assistant/core/pull/74569
[#74578]: https://github.com/home-assistant/core/pull/74578
[#74598]: https://github.com/home-assistant/core/pull/74598
[#74601]: https://github.com/home-assistant/core/pull/74601
[#74610]: https://github.com/home-assistant/core/pull/74610
[#74615]: https://github.com/home-assistant/core/pull/74615
[#74625]: https://github.com/home-assistant/core/pull/74625
[#74628]: https://github.com/home-assistant/core/pull/74628
[#74640]: https://github.com/home-assistant/core/pull/74640
[#74649]: https://github.com/home-assistant/core/pull/74649
[#74677]: https://github.com/home-assistant/core/pull/74677
[@Kane610]: https://github.com/Kane610
[@Michsior14]: https://github.com/Michsior14
[@TheJulianJES]: https://github.com/TheJulianJES
[@arnemauer]: https://github.com/arnemauer
[@bdraco]: https://github.com/bdraco
[@bramkragten]: https://github.com/bramkragten
[@c-soft]: https://github.com/c-soft
[@elupus]: https://github.com/elupus
[@emontnemery]: https://github.com/emontnemery
[@frenck]: https://github.com/frenck
[@gwww]: https://github.com/gwww
[@jjlawren]: https://github.com/jjlawren
[@tkdrob]: https://github.com/tkdrob
[@ufodone]: https://github.com/ufodone
[apache_kafka docs]: /integrations/apache_kafka/
[bloomsky docs]: /integrations/bloomsky/
[cast docs]: /integrations/cast/
[deconz docs]: /integrations/deconz/
[doorbird docs]: /integrations/doorbird/
[elkm1 docs]: /integrations/elkm1/
[envisalink docs]: /integrations/envisalink/
[fjaraskupan docs]: /integrations/fjaraskupan/
[frontend docs]: /integrations/frontend/
[kaiterra docs]: /integrations/kaiterra/
[openweathermap docs]: /integrations/openweathermap/
[satel_integra docs]: /integrations/satel_integra/
[skybell docs]: /integrations/skybell/
[sonos docs]: /integrations/sonos/
[zamg docs]: /integrations/zamg/
[zha docs]: /integrations/zha/
## Release 2022.7.2 - July 8
- Add missing strings for here_travel_time ([@eifinger] - [#74641]) ([here_travel_time docs])
- Add ssh-rsa as acceptable an host key algorithm ([@siyuan-nz] - [#74684]) ([unifi_direct docs])
- Fix ZHA group not setting the correct color mode ([@TheJulianJES] - [#74687]) ([zha docs])
- Bump deconz dependency to fix #74523 ([@Kane610] - [#74710]) ([deconz docs])
- Bump atomicwrites ([@balloob] - [#74758])
- Bump regenmaschine to 2022.07.0 ([@bachya] - [#74680]) ([rainmachine docs])
- Fix error with HDD temperature report in Freebox integration ([@BenoitAnastay] - [#74718]) ([freebox docs])
[#74641]: https://github.com/home-assistant/core/pull/74641
[#74680]: https://github.com/home-assistant/core/pull/74680
[#74684]: https://github.com/home-assistant/core/pull/74684
[#74687]: https://github.com/home-assistant/core/pull/74687
[#74710]: https://github.com/home-assistant/core/pull/74710
[#74718]: https://github.com/home-assistant/core/pull/74718
[#74758]: https://github.com/home-assistant/core/pull/74758
[@BenoitAnastay]: https://github.com/BenoitAnastay
[@Kane610]: https://github.com/Kane610
[@TheJulianJES]: https://github.com/TheJulianJES
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@eifinger]: https://github.com/eifinger
[@siyuan-nz]: https://github.com/siyuan-nz
[deconz docs]: /integrations/deconz/
[freebox docs]: /integrations/freebox/
[here_travel_time docs]: /integrations/here_travel_time/
[rainmachine docs]: /integrations/rainmachine/
[unifi_direct docs]: /integrations/unifi_direct/
[zha docs]: /integrations/zha/
## Release 2022.7.3 - July 10
- Fix Vicare One Time Charge ([@oischinger] - [#74872]) ([vicare docs])
- Fix KeyError from zwave_js diagnostics ([@kpine] - [#74579]) ([zwave_js docs])
- Update systembridgeconnector to 3.3.2 ([@timmo001] - [#74701]) ([system_bridge docs])
- `air_quality` and `filter_life` fixes for Pur131S ([@jetpacktuxedo] - [#74740]) ([vesync docs])
- Update pyCEC to version 0.5.2 ([@inytar] - [#74742]) ([hdmi_cec docs])
- Bump pyezviz to 0.2.0.9 ([@regevbr] - [#74755]) ([ezviz docs])
- Update aioqsw to v0.1.1 ([@Noltari] - [#74784]) ([qnap_qsw docs])
- Bump python-gammu to 3.2.4 with Python 3.10 support ([@PaulAnnekov] - [#74797]) ([sms docs])
- Bump deCONZ dependency to fix #74791 ([@Kane610] - [#74804]) ([deconz docs])
- Bump regenmaschine to 2022.07.1 ([@bachya] - [#74815]) ([rainmachine docs])
- Fixed unit of measurement. #70121 ([@StephanU] - [#74838]) ([edl21 docs])
- Bump rokuecp to 0.17.0 ([@ctalkington] - [#74862]) ([roku docs])
- Bump pymazda to 0.3.6 ([@bdr99] - [#74863]) ([mazda docs])
- Fix Vicare One Time Charge ([@oischinger] - [#74872]) ([vicare docs])
- Bump pysml to 0.0.8 (fixes #74382) ([@DavidMStraub] - [#74875]) ([edl21 docs])
- Bump afsapi to 0.2.5 ([@wlcrs] - [#74907]) ([frontier_silicon docs])
[#74579]: https://github.com/home-assistant/core/pull/74579
[#74701]: https://github.com/home-assistant/core/pull/74701
[#74740]: https://github.com/home-assistant/core/pull/74740
[#74742]: https://github.com/home-assistant/core/pull/74742
[#74755]: https://github.com/home-assistant/core/pull/74755
[#74784]: https://github.com/home-assistant/core/pull/74784
[#74797]: https://github.com/home-assistant/core/pull/74797
[#74804]: https://github.com/home-assistant/core/pull/74804
[#74815]: https://github.com/home-assistant/core/pull/74815
[#74838]: https://github.com/home-assistant/core/pull/74838
[#74862]: https://github.com/home-assistant/core/pull/74862
[#74863]: https://github.com/home-assistant/core/pull/74863
[#74872]: https://github.com/home-assistant/core/pull/74872
[#74875]: https://github.com/home-assistant/core/pull/74875
[#74907]: https://github.com/home-assistant/core/pull/74907
[@DavidMStraub]: https://github.com/DavidMStraub
[@Kane610]: https://github.com/Kane610
[@Noltari]: https://github.com/Noltari
[@PaulAnnekov]: https://github.com/PaulAnnekov
[@StephanU]: https://github.com/StephanU
[@bachya]: https://github.com/bachya
[@bdr99]: https://github.com/bdr99
[@ctalkington]: https://github.com/ctalkington
[@inytar]: https://github.com/inytar
[@jetpacktuxedo]: https://github.com/jetpacktuxedo
[@kpine]: https://github.com/kpine
[@oischinger]: https://github.com/oischinger
[@regevbr]: https://github.com/regevbr
[@timmo001]: https://github.com/timmo001
[@wlcrs]: https://github.com/wlcrs
[deconz docs]: /integrations/deconz/
[edl21 docs]: /integrations/edl21/
[ezviz docs]: /integrations/ezviz/
[frontier_silicon docs]: /integrations/frontier_silicon/
[hdmi_cec docs]: /integrations/hdmi_cec/
[mazda docs]: /integrations/mazda/
[qnap_qsw docs]: /integrations/qnap_qsw/
[rainmachine docs]: /integrations/rainmachine/
[roku docs]: /integrations/roku/
[sms docs]: /integrations/sms/
[system_bridge docs]: /integrations/system_bridge/
[vesync docs]: /integrations/vesync/
[vicare docs]: /integrations/vicare/
[zwave_js docs]: /integrations/zwave_js/
## Release 2022.7.4 - July 13
- Migrate ecobee to native_* ([@emontnemery] - [#74043]) ([ecobee docs])
- Migrate homematicip_cloud to native_* ([@emontnemery] - [#74385]) ([homematicip_cloud docs])
- Update pyialarm to 2.2.0 ([@RyuzakiKK] - [#74874]) ([ialarm docs])
- Correctly handle device triggers for missing ZHA devices ([@Adminiuga] - [#74894]) ([zha docs])
- Remove pip --prefix workaround ([@henryptung] - [#74922])
- Fix Pyload request content type headers ([@iMarkus] - [#74957]) ([pyload docs])
- JSON serialize NamedTuple subclasses with aiohttp ([@bdraco] - [#74971])
- Fix mix of aiohttp and requests in ClickSend TTS ([@frenck] - [#74985]) ([clicksend_tts docs])
- Do not spam log when Life360 member location is missing ([@pnbruckner] - [#75029]) ([life360 docs])
- Upgrade huawei-lte-api to 1.6.1 ([@scop] - [#75030]) ([huawei_lte docs])
- Fix Ruckus Unleashed SSH connection failures ([@gabe565] - [#75032]) ([ruckus_unleashed docs])
- Bump afsapi to 0.2.6 ([@wlcrs] - [#75041]) ([frontier_silicon docs])
- Bump homematicip to 1.0.4 ([@hahn-th] - [#75053]) ([homematicip_cloud docs])
- Bump AIOAladdinConnect to 0.1.23 ([@mkmer] - [#75065]) ([aladdin_connect docs])
- Fix Insteon thermostat issues ([@teharris1] - [#75079]) ([insteon docs])
- Fix missing ordered states in universal media player ([@Drafteed] - [#75099]) ([universal docs])
- Make sure device tuple is a list on save ([@elupus] - [#75103]) ([rfxtrx docs])
- Fix Powerview top shade open position ([@kingy444] - [#75110]) ([hunterdouglas_powerview docs])
- Bump ZHA dependencies ([@puddly] - [#75133]) ([zha docs])
- Ensure SimpliSafe diagnostics redact the `code` option ([@bachya] - [#75137]) ([simplisafe docs])
- Block bad pubnub version ([@balloob] - [#75138])
[#74043]: https://github.com/home-assistant/core/pull/74043
[#74385]: https://github.com/home-assistant/core/pull/74385
[#74874]: https://github.com/home-assistant/core/pull/74874
[#74894]: https://github.com/home-assistant/core/pull/74894
[#74922]: https://github.com/home-assistant/core/pull/74922
[#74957]: https://github.com/home-assistant/core/pull/74957
[#74971]: https://github.com/home-assistant/core/pull/74971
[#74985]: https://github.com/home-assistant/core/pull/74985
[#75029]: https://github.com/home-assistant/core/pull/75029
[#75030]: https://github.com/home-assistant/core/pull/75030
[#75032]: https://github.com/home-assistant/core/pull/75032
[#75041]: https://github.com/home-assistant/core/pull/75041
[#75053]: https://github.com/home-assistant/core/pull/75053
[#75065]: https://github.com/home-assistant/core/pull/75065
[#75079]: https://github.com/home-assistant/core/pull/75079
[#75099]: https://github.com/home-assistant/core/pull/75099
[#75103]: https://github.com/home-assistant/core/pull/75103
[#75110]: https://github.com/home-assistant/core/pull/75110
[#75133]: https://github.com/home-assistant/core/pull/75133
[#75137]: https://github.com/home-assistant/core/pull/75137
[#75138]: https://github.com/home-assistant/core/pull/75138
[@Adminiuga]: https://github.com/Adminiuga
[@Drafteed]: https://github.com/Drafteed
[@RyuzakiKK]: https://github.com/RyuzakiKK
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@bdraco]: https://github.com/bdraco
[@elupus]: https://github.com/elupus
[@emontnemery]: https://github.com/emontnemery
[@frenck]: https://github.com/frenck
[@gabe565]: https://github.com/gabe565
[@hahn-th]: https://github.com/hahn-th
[@henryptung]: https://github.com/henryptung
[@iMarkus]: https://github.com/iMarkus
[@kingy444]: https://github.com/kingy444
[@mkmer]: https://github.com/mkmer
[@pnbruckner]: https://github.com/pnbruckner
[@puddly]: https://github.com/puddly
[@scop]: https://github.com/scop
[@teharris1]: https://github.com/teharris1
[@wlcrs]: https://github.com/wlcrs
[aladdin_connect docs]: /integrations/aladdin_connect/
[clicksend_tts docs]: /integrations/clicksend_tts/
[ecobee docs]: /integrations/ecobee/
[frontier_silicon docs]: /integrations/frontier_silicon/
[homematicip_cloud docs]: /integrations/homematicip_cloud/
[huawei_lte docs]: /integrations/huawei_lte/
[hunterdouglas_powerview docs]: /integrations/hunterdouglas_powerview/
[ialarm docs]: /integrations/ialarm/
[insteon docs]: /integrations/insteon/
[life360 docs]: /integrations/life360/
[pyload docs]: /integrations/pyload/
[rfxtrx docs]: /integrations/rfxtrx/
[ruckus_unleashed docs]: /integrations/ruckus_unleashed/
[simplisafe docs]: /integrations/simplisafe/
[universal docs]: /integrations/universal/
[zha docs]: /integrations/zha/
## Release 2022.7.5 - July 14
- Address Blebox uniapi review sidenotes ([@riokuu] - [#74298]) ([blebox docs])
- Fix Alexa: Only trigger doorbell event on actual state change to "ON" ([@Tho85] - [#74924]) ([alexa docs])
- Fix Blebox light scenes ([@riokuu] - [#75106]) ([blebox docs])
- Fix playback of hls cameras in stream ([@uvjustin] - [#75166]) ([stream docs])
- Bump version of pyunifiprotect to 4.0.10 ([@AngellusMortis] - [#75180]) ([unifiprotect docs])
- Bumped AIOAladdin Connect to 0.1.24 ([@mkmer] - [#75182]) ([aladdin_connect docs])
- Bump zigpy from 0.47.2 to 0.47.3 ([@puddly] - [#75194]) ([zha docs])
- Skip `iso4217` version 1.10, which includes a broken `__init__.pyi` file ([@puddly] - [#75200])
- Fix Hive power unit of measurement ([@KJonline] - [#75210]) ([hive docs])
- Bump frontend to 20220707.1 ([@zsarnett] - [#75232]) ([frontend docs])
- Bump AIOAladdinConnect to 0.1.25 ([@mkmer] - [#75235]) ([aladdin_connect docs])
- Bump pylitterbot to 2022.7.0 ([@natekspencer] - [#75241]) ([litterrobot docs])
- Remove nest mac prefix that matches cast devices ([@allenporter] - [#75108]) ([nest docs])
[#74298]: https://github.com/home-assistant/core/pull/74298
[#74924]: https://github.com/home-assistant/core/pull/74924
[#75106]: https://github.com/home-assistant/core/pull/75106
[#75108]: https://github.com/home-assistant/core/pull/75108
[#75166]: https://github.com/home-assistant/core/pull/75166
[#75180]: https://github.com/home-assistant/core/pull/75180
[#75182]: https://github.com/home-assistant/core/pull/75182
[#75194]: https://github.com/home-assistant/core/pull/75194
[#75200]: https://github.com/home-assistant/core/pull/75200
[#75210]: https://github.com/home-assistant/core/pull/75210
[#75232]: https://github.com/home-assistant/core/pull/75232
[#75235]: https://github.com/home-assistant/core/pull/75235
[#75241]: https://github.com/home-assistant/core/pull/75241
[@AngellusMortis]: https://github.com/AngellusMortis
[@KJonline]: https://github.com/KJonline
[@Tho85]: https://github.com/Tho85
[@allenporter]: https://github.com/allenporter
[@mkmer]: https://github.com/mkmer
[@natekspencer]: https://github.com/natekspencer
[@puddly]: https://github.com/puddly
[@riokuu]: https://github.com/riokuu
[@uvjustin]: https://github.com/uvjustin
[@zsarnett]: https://github.com/zsarnett
[aladdin_connect docs]: /integrations/aladdin_connect/
[alexa docs]: /integrations/alexa/
[blebox docs]: /integrations/blebox/
[frontend docs]: /integrations/frontend/
[hive docs]: /integrations/hive/
[litterrobot docs]: /integrations/litterrobot/
[nest docs]: /integrations/nest/
[stream docs]: /integrations/stream/
[unifiprotect docs]: /integrations/unifiprotect/
[zha docs]: /integrations/zha/
## Need help? Join the community!
Home Assistant has a great community of users who are all more than willing
@ -540,7 +839,7 @@ entities from the Home Assistant Interface, selecting "REMOVE ENTITY", and
then confirming the removal by clicking "REMOVE".
- If you have automations to set shade position based on entity ID, you will
need to reconfigure these as the new entities will be named differently.
need to reconfigure these as the new entities will be named differently.
- If you only have automations set to trigger scenes you **do not** need to
reconfigure automations.
@ -601,6 +900,30 @@ integration, you will have to re-add it manually via the user interface.
{% details "Life360" %}
### Overview
The Life360 integration has been converted from the old "legacy"
implementation (which uses `known_devices.yaml`) to the newer entity based
design, similar to what was done back in the 0.94.0 release to many other
device tracker integrations.
Due to this change, all your existing Life360 entities will become
non-functional, and there will be new entities, with different entity IDs,
that _are_ functional.
### Steps to replace old entities with new ones
1. Edit the `known_devices.yaml` file in your configuration directory to
remove any Life360-related entries. Or, if there are only Life360 entries in
this file, simply delete the file entirely.
2. Restart Home Assistant. All the old, non-functional Life360 entities
should now be gone. (If you are still seeing the old entities, try refreshing
your browser.)
3. Go to the Entities page (under Settings -> Devices & Services -> Entities)
and change the entity IDs for the new Life360 entities as desired.
### Removed/changed functionality
The previously deprecated YAML configuration of the Life360
integration has been removed.
@ -608,17 +931,13 @@ Life360 is now configured via the UI. Any "advanced" options in
YAML configuration will be imported. Once the migration is complete,
any `life360` entries in YAML configuration should be removed.
As per other device tracker platforms that have migrated to entity-based,
entries in `known_devices.yaml` will no longer be created, and any existing
entries for `life360` should be removed.
The following options are no longer supported:
The following options are no longer supported:
- `circles`
- `members`
- `error_threshold`
- `warning_threshold`
- `max_update_wait`
- `max_update_wait` (including the `life360_update_overdue` & `life360_update_restored` events)
- `show_as_state: moving`
Additionally, the following entity attributes have been changed:
@ -1037,7 +1356,7 @@ Vesync switches that support energy monitoring will have their:
- Voltage attribute moved from the switch entity to a dedicated Voltage Sensor
entity
- Weekly, monthly and yearly moved from the switch entity attributes into new
energy sensors.
energy sensors.
If you used these entity attributes in your automation or scripts, you'd need
to adapt them to this change.

33
source/_posts/2022-07-12-partner-program.markdown Normal file
View File

@ -0,0 +1,33 @@
---
layout: post
title: "Introducing the Works with Home Assistant program"
description: "Our goal is to work together with manufacturers to build the best experience for our shared user base."
date: 2022-07-12 00:00:00
date_formatted: "July 12, 2022"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories:
- Announcements
og_image: /images/blog/2022-07-12-partner-program/partner_program_og.jpg
---
With Home Assistant, we integrate with over 1000 different APIs. The majority of these integrations are created and maintained by the Home Assistant community. Over the years a number of companies have stepped up to work with our community offering samples and engineering support. In a few cases, we saw companies pick up the maintenance of integrating their products in Home Assistant.
Sadly, a couple of times it happened that companies went silent after their initial contribution, causing users to be wondering why new devices are not being supported. We want to protect our users from investing in products for their homes that won't work well with Home Assistant.
Today we’re introducing the Works with Home Assistant program to allow manufacturers to show their support and commitment to Home Assistant and its community.
The program requires manufacturers to maintain the integration of their products in Home Assistant, offer a good user experience, provide product samples and give us an engineering contact to escalate issues. In return, manufacturers will be able to use the “Works with Home Assistant” badge on their products and documentation. The terms of the Works with Home Assistant program are enforced in an agreement signed by both Nabu Casa and the manufacturer.
<img src='/images/blog/2022-07-12-partner-program/partner-program-logos.jpg' alt="Decorative header." class='no-shadow'>
<br><br>
With Home Assistant we are always working on educating our users about preferring local control and open standards when acquiring new products. This is also reflected in the “Works with Home Assistant” badges.
There are manufacturers that are creating products that integrate into Home Assistant using standards like Z-Wave, Zigbee, or Matter (soon). In these cases, the integration is maintained by the Home Assistant community and Nabu Casa. These companies can still become a member of the Works with Home Assistant program but are relieved from integration maintenance.
Products that are approved for the [Made with ESPHome program](https://esphome.io/guides/made_for_esphome.html) will be eligible to use the “Works locally with Home Assistant” badge as part of their Made with ESPHome membership.
For more information for manufacturers, see our [Works with Home Assistant portal](https://partner.home-assistant.io).

BIN
source/images/blog/2022-07-12-partner-program/partner-program-logos.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 63 KiB

BIN
source/images/blog/2022-07-12-partner-program/partner_program_og.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 62 KiB

BIN
source/images/integrations/nest/application_credentials.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 51 KiB

BIN
source/images/integrations/nest/attention.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 57 KiB

BIN
source/images/integrations/nest/deprecation.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 70 KiB

BIN
source/images/integrations/nest/setup_prompt.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 13 KiB

3
source/more-info/unsupported/privileged.markdown
View File

@ -13,5 +13,6 @@ to be able to do everything it needs to do.
If you are running an older version of our Home Assistant OS, update it in the
{% my configuration title="Configuration" %} panel.
If this is not our Home Assistant OS, you need to re-run our
If this is not our Home Assistant OS, your operating system might be out of date. Try checking for and
installing updates, then restarting your system. If this doesn't work, you may need to re-run our
[convenience installation script](https://github.com/home-assistant/supervised-installer).