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-23 17:27:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'next' into rc

Browse Source
This commit is contained in:
Franck Nijhof 2022-09-19 12:41:30 +02:00
commit 3f6edf7ddf
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
67 changed files with 2733 additions and 1324 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CODEOWNERS
View File

@ -30,7 +30,6 @@ source/_integrations/alert.markdown @home-assistant/core
source/_integrations/alexa.markdown @home-assistant/cloud @ochlocracy
source/_integrations/alexa.smart_home.markdown @home-assistant/cloud @ochlocracy
source/_integrations/almond.markdown @gcampax @balloob
source/_integrations/ambee.markdown @frenck
source/_integrations/amberelectric.markdown @madpilot
source/_integrations/ambiclimate.markdown @danielhiversen
source/_integrations/ambient_station.markdown @bachya
@ -417,6 +416,7 @@ source/_integrations/nina.markdown @DeerMaximum
source/_integrations/nissan_leaf.markdown @filcole
source/_integrations/nmbs.markdown @thibmaek
source/_integrations/noaa_tides.markdown @jdelaney72
source/_integrations/nobo_hub.markdown @echoromeo @oyvindwe
source/_integrations/notify.markdown @home-assistant/core
source/_integrations/notify_events.markdown @matrozov @papajojo
source/_integrations/notion.markdown @bachya

4
_config.yml
View File

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

12
source/_docs/blueprint.markdown
View File

@ -9,14 +9,20 @@ If you're looking on how to use blueprints, see the [automation documentation](/
</div>
An automation blueprint is an automation configuration with certain parts marked as configurable. This allows users to create multiple automations based on the same blueprint, with each having its own configuration.
<div class='note'>
While the tutorial only shows how to create an automation blueprint, scripts also support blueprints in the same way.
</div>
A blueprint is a script or automation configuration with certain parts marked as configurable. This allows users to create multiple scripts or automations based on the same blueprint, with each having its own configuration.
Imagine a blueprint that controls a light based on motion, that allows you to configure the motion sensor to trigger on, and the light to control. It is now possible to create two automations that each have their own configuration for this blueprint and that act completely independent, yet are based on the same automation configuration.
<div class='note'>
This is an advanced feature and requires knowledge of writing [automations in YAML](/docs/automation/yaml/).
This is an advanced feature and requires knowledge of writing [automations](/docs/automation/yaml/) and [scripts](/docs/scripts/) in YAML.
</div>
### [Tutorial: Create a blueprint &raquo;](/docs/blueprint/tutorial/)
### [Tutorial: Create an automation blueprint &raquo;](/docs/blueprint/tutorial/)

4
source/_docs/blueprint/selectors.markdown
View File

@ -685,8 +685,8 @@ max:
type: [integer, float]
required: true
step:
description: The step value of the number value.
type: [integer, float]
description: The step size of the number value. Set to `"any"` to allow any number.
type: [integer, float, "any"]
required: false
default: 1
unit_of_measurement:

13
source/_docs/blueprint/tutorial.markdown
View File

@ -1,9 +1,15 @@
---
title: "Blueprint tutorial"
description: "Tutorial on creating a blueprint."
title: "Automation blueprint tutorial"
description: "Tutorial on creating an automation blueprint."
---
In this tutorial, we're going to create a blueprint that controls a light based on a motion sensor. We will do this by taking an existing automation and converting it to a blueprint.
<div class='note'>
While the tutorial only shows how to create an automation blueprint, scripts also support blueprints in the same way.
</div>
In this tutorial, we're going to create an automation blueprint that controls a light based on a motion sensor. We will do this by taking an existing automation and converting it to a blueprint.
For this tutorial, we use a simple automation. The process for converting a complex automation is not any different.
@ -120,6 +126,7 @@ Blueprints are easier to use if it's easy to see what each field is used for. We
```yaml
blueprint:
name: Motion Light Tutorial
description: Turn a light on based on detected motion
domain: automation
input:
motion_sensor:

2
source/_docs/configuration/splitting_configuration.markdown
View File

@ -161,7 +161,7 @@ This (large) sensor configuration gives us another example:
- platform: steam_online
api_key: ["not telling"]
accounts:
- 76561198012067051
- 76561198012067051
#### TIME/DATE ##################################
- platform: time_date

18
source/_docs/configuration/templating.markdown
View File

@ -548,6 +548,23 @@ Example using `is_defined` to parse a JSON payload:
This will throw an error `UndefinedError: 'value_json' is undefined` if the JSON payload has no `val` attribute.
### Version
- `version()` Returns a [AwesomeVersion object](https://github.com/ludeeus/awesomeversion) for the value given inside the brackets.
- This is also available as a filter (`| version`).
Examples:
{% raw %}
- `{{ version("2099.9.9") > "2000.0.0" }}` Will return `True`
- `{{ version("2099.9.9") < "2099.10" }}` Will return `True`
- `{{ "2099.9.9" | version < "2099.10" }}` Will return `True`
- `{{ (version("2099.9.9") - "2100.9.10").major }}` Will return `True`
- `{{ (version("2099.9.9") - "2099.10.9").minor }}` Will return `True`
- `{{ (version("2099.9.9") - "2099.9.10").patch }}` Will return `True`
{% endraw %}
### Distance
@ -556,6 +573,7 @@ Not supported in [limited templates](#limited-templates).
- `distance()` will measure the distance in kilometers between home, entity, coordinates.
- `closest()` will find the closest entity.
#### Distance examples
If only one location is passed in, Home Assistant will measure the distance from home.

1
source/_integrations/abode.markdown
View File

@ -59,6 +59,7 @@ They are grouped into the below events:
- **abode_panel_restore**: Fired when the panel fault is restored.
- **abode_disarm**: Fired when the alarm is disarmed.
- **abode_arm**: Fired when the alarm is armed (home or away).
- **abode_arm_fault**: Fired when the alarm is armed (home or away) and has a fault. This includes open door/windows, low battery, backup connection. abode_arm is not fired if a fault is present.
- **abode_test**: Fired when a sensor is in test mode.
- **abode_capture**: Fired when an image is captured.
- **abode_device**: Fired for device changes/additions/deletions.

19
source/_integrations/accuweather.markdown
View File

@ -21,7 +21,24 @@ The AccuWeather integration uses the [AccuWeather](https://accuweather.com/) web
## Setup
To generate an AccuWeather API key, go to [AccuWeather APIs](https://developer.accuweather.com/) page, register and create application with product **Limited Trial**.
To generate an AccuWeather API key, go to [AccuWeather APIs](https://developer.accuweather.com/) page, register and create application with the following settings:
- Products
- Core Weather
- **Core Weather Limited Trial**
- Minute Cast
- **None**
- Where will the API be used?
- **Other**
- What will you be creating with this API?
- **Internal App**
- What programming language is your APP written in?
- **Python**
- Is this for Business to Business or Business to Consumer use?
- **Business to Business**
- Is this Worldwide or Country specific use?
- **Worldwide**
You can test your newly created API key [here](https://developer.accuweather.com/accuweather-current-conditions-api/apis)
{% include integrations/config_flow.md %}

2
source/_integrations/advantage_air.markdown
View File

@ -3,7 +3,7 @@ title: Advantage Air
description: Instructions on how to integrate Advantage Air A/C controller into Home Assistant.
ha_category:
- Climate
- Updates
- Update
ha_release: 0.117
ha_iot_class: Local Polling
ha_config_flow: true

2
source/_integrations/alarm_control_panel.template.markdown
View File

@ -50,7 +50,7 @@ alarm_control_panel:
- condition: state
entity_id: device_tracker.paulus
state: "home"
- service: alarm_control_panel.alarm_arm_home
- service: alarm_control_panel.alarm_disarm
target:
entity_id: alarm_control_panel.real_alarm
data:

95
source/_integrations/ambee.markdown
View File

@ -1,95 +0,0 @@
---
title: Ambee
description: Instructions on how to integrate Ambee within Home Assistant.
ha_category:
- Environment
- Health
ha_release: 2021.7
ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@frenck'
ha_domain: ambee
ha_platforms:
- sensor
ha_quality_scale: platinum
ha_integration_type: integration
---
<div class='note warning'>
This integration is pending removal from Home Assistant and will be no longer available as of Home Assistant 2022.10.
</div>
The Ambee integration integrates the [Ambee](https://www.getambee.com/) API
platform with Home Assistant.
Ambee fuses the power of thousands of on-ground sensor data and hundreds of
remote imagery from satellites. Their state-of-the-art AI and ML techniques with
proprietary models analyze environmental factors such as air quality, soil,
micro weather, pollen, and more to help millions worldwide say safe and protect
themselves.
## Prerequisites
To use the Ambee integration, you will need to obtain an API key from Ambee.
Ambee provides free evulation API keys, that are limited to 50,000 credits
and for a period of 30 days. After that, you will need to sign up for a
paid enterprise plan in order to continue using Ambee.
[Sign up for an Ambee account](https://api-dashboard.getambee.com/#/signup).
Once you have completed the sign up and logged in for the first time, the
API token will be displayed on the top of your
[Ambee dashboard](https://api-dashboard.getambee.com/#/). Make sure you select
both the Air Quality API and the Pollen API.
{% include integrations/config_flow.md %}
## Sensors
The Ambee platform mainly provides sensors that you can use in your automations.
### Air Quality
Polluted air affects planetary well-being with disruption to our ecosystem and
various health risks. The following sensors from Ambee are available on this:
- Air Quality Index (AQI)
- Carbon Monoxide (CO)
- Nitrogen Dioxide (NO2)
- Ozone
- Particulate Matter < 10 μm
- Particulate Matter < 2.5 μm
- Sulphur Dioxide (SO2)
### Pollen
Pollen is a fine powder produced by trees and plants. Pollen can severely affect
people, especially those with different ailments such as asthma and respiratory
issues. This integration provides a lot of sensors to monitor pollen counts and
risks.
Generic pollen count sensors (in pollen/m3)
and as risk level (low, moderate, high, very high):
- Grass
- Tree
- Weed
Additionally, sensors for specific pollen from specific grasses,
trees or weeds, in pollen/m3, are provided. These are disabled by default.
Enable those entities in the user interface if you like to use these:
- Alder Tree
- Birch Tree
- Chenopod Weed
- Cypress Tree
- Elm Tree
- Hazel Tree
- Mugwort Weed
- Nettle Weed
- Oak Tree
- Pine Tree
- Plane Tree
- Poaceae Grass
- Poplar Tree
- Ragweed

2
source/_integrations/androidtv.markdown
View File

@ -38,6 +38,8 @@ For Fire TV devices, the instructions are as follows:
- From the main (Launcher) screen, select Settings.
- Select My Fire TV > About > Network.
If Develper Options is missing from Settings then select My Fire TV and press the button seven times on About.
{% include integrations/config_flow.md %}
{% include integrations/option_flow.md %}

2
source/_integrations/aws.markdown
View File

@ -147,7 +147,7 @@ If you do not download them, you will lose them and will have to recreate a new
</div>
- Copy/Paste the two keys that are shown here in your `configuration.yaml` file.
- On the left-hand side of the screen go back to "Users" and select the user you just created. On the "Permissions" tab click the "Attach Policy" icon. Search for "SNS" and attach the policy "AmazonSNSFUullAccess".
- On the left-hand side of the screen go back to "Users" and select the user you just created. On the "Permissions" tab click the "Attach Policy" icon. Search for "SNS" and attach the policy "AmazonSNSFullAccess".
- Back to the AWS Console you now need to find "SNS" and click in to that service. It is under the Mobile Services group.
- On the left-hand side, select "Topics" then "Create new topic".
- Choose a Topic Name and Display Name.

2
source/_integrations/bluetooth.markdown
View File

@ -93,7 +93,7 @@ Integrations that have followed the [Best practices for library authors](https:/
## Passive Scanning
Passive Scanning on Linux can be enabled in the options flow per adapter if the host system runs BlueZ 4.63 or later with experimental features enabled.
Passive Scanning on Linux can be enabled in the options flow per adapter if the host system runs BlueZ 5.63 or later with experimental features enabled.
Many integrations require active scanning and may not function when scanning is passive.

6
source/_integrations/bthome.markdown
View File

@ -1,6 +1,6 @@
---
title: BTHome
description: Instructions on how to integrate BThome BLE devices into Home Assistant.
description: Instructions on how to integrate BTHome BLE devices into Home Assistant.
ha_category:
- Sensor
ha_bluetooth: true
@ -23,10 +23,6 @@ The BTHome BLE integration will automatically discover devices once the [Bluetoo
BTHome is an energy effective but flexible BLE format to broadcast data with Bluetooth and allows you to create your own DIY BLE sensors. More information about the BTHome BLE format and projects that use the format can be found on the [BTHome website](https://bthome.io/).
## Supported sensor measurements
The current release only supports sensors, no binary sensors.
## Bindkey
When using encryption for your BTHome sensor, you will promted to enter your 32 character hexadecimal (16 bytes) encryption key. This key is called the bindkey. More information about the bindkey can be found in the [specifications](https://bthome.io/#encryption).

2
source/_integrations/clickatell.markdown
View File

@ -11,7 +11,7 @@ ha_platforms:
ha_integration_type: integration
---
The `clickatell` platform uses [Clickatell](https://clickatell.com) to deliver SMS notifications from Home Assistant.
The `clickatell` platform uses [Clickatell](https://www.clickatell.com) to deliver SMS notifications from Home Assistant.
## Setup

6
source/_integrations/daikin.markdown
View File

@ -100,11 +100,11 @@ The `daikin` sensor platform integrates Daikin air conditioning systems into Hom
- Inside temperature
- Outside temperature
- Inside humidity
- Estimated power consumption
- Estimated power consumption (not per device, but sum of installation)
- Hourly energy consumption in cool mode
- Hourly energy consumption in heat mode
- Outside unit's compressor frequency
- Today's total energy consumption (resets at 00:00)
- Today's total energy consumption (not per device, but sum of installation, resets at 00:00)
<div class='note'>
@ -117,7 +117,7 @@ The `daikin` sensor platform integrates Daikin air conditioning systems into Hom
<div class='note'>
- The 'Today's total energy consumption' and 'Estimated power consumption' sensor is updated every time 100 Wh are consumed by all different operating modes summed together.
- The 'Today's total energy consumption' and 'Estimated power consumption' sensor is updated every time 100 Wh are consumed by all different operating modes summed together. These values are the values for the whole installation, not per device (unless, you have only one device).
- The 'Estimated power consumption' sensor is derived from the energy consumption and not provided by the AC directly.
- The 'cool/heat' energy sensors are updated hourly with the previous hour energy consumption
of a given mode and a given AC.

1
source/_integrations/default_config.markdown
View File

@ -38,6 +38,7 @@ This integration is a meta-component and configures a default set of integration
- [Mobile App Support](/integrations/mobile_app/) (`mobile_app`)
- [My Home Assistant](/integrations/my/) (`my`)
- [Person](/integrations/person/) (`person`)
- [Schedule](/integrations/schedule/) (`schedule`)
- [Scene](/integrations/scene/) (`scene`)
- [Scripts](/integrations/script/) (`script`)
- [Simple Service Discovery Protocol (SSDP)](/integrations/ssdp/) (`ssdp`)

2
source/_integrations/demo.markdown
View File

@ -3,7 +3,7 @@ title: Demo
description: Instructions on how to use the Platform demos with Home Assistant.
ha_category:
- Other
- Updates
- Update
ha_release: 0.7
ha_quality_scale: internal
ha_codeowners:

2
source/_integrations/dwd_weather_warnings.markdown
View File

@ -68,7 +68,7 @@ monitored_conditions:
| ------------ | -------------------------------------- |
| `last_update` | *(time)* Time and date (UTC) of last update from DWD. |
| `region_name` | *(str)* Requested region name. This should be the same as the region name in the configuration if a name was given. |
| `region_id` | *(int)* Region ID assigned by DWD. This should be the same as the region name in the configuration if an id was given. |
| `region_id` | *(int)* Region ID assigned by DWD. This should be the same as the region id in the configuration if an id was given. |
| `warning_count` | *(int)* Number of issued warnings. There can be more than one warning issued at once. |
| `warning_<x>` | *(list)* The warning as a whole object containing the following attributes as nested attributes. |
| `warning_<x>_level` | *(int)* Issued warning level (0 - 4).<br/>0: Keine Warnungen <br/>1: Wetterwarnungen <br/>2: Warnungen vor markantem Wetter<br/>3: Unwetterwarnungen<br/>4: Warnungen vor extremem Unwetter |

4
source/_integrations/ecowitt.markdown
View File

@ -27,5 +27,7 @@ The following steps must be performed to set up this integration. For security r
2. Pick your station -> Menu Others -> DIY Upload Servers.
3. Hit next and select 'Customized'
4. Pick the protocol Ecowitt, and put in the ip/hostname of your Home Assistant server.
5. Path have to match, you can copy with secure token /.
5. Path have to match!
6. Save configuration.
Ecowitt doesn't support TLS/SSL, you can use the NGINX TLS Proxy Add-on to support HTTPS and HTTP at the same time.

2
source/_integrations/fritz.markdown
View File

@ -5,7 +5,7 @@ ha_category:
- Binary Sensor
- Presence Detection
- Sensor
- Updates
- Update
ha_release: '0.10'
ha_domain: fritz
ha_config_flow: true

8
source/_integrations/guardian.markdown
View File

@ -37,14 +37,6 @@ There is currently support for the following device types within Home Assistant:
## Services
### `guardian.disable_ap`
Disable the device's onboard access point.
### `guardian.enable_ap`
Enable the device's onboard access point.
### `guardian.pair_sensor`
Add a new paired sensor to the valve controller.

2
source/_integrations/hassio.markdown
View File

@ -4,7 +4,7 @@ description: Control Supervisor Add-ons and OS from Home Assistant
ha_category:
- Binary Sensor
- Sensor
- Updates
- Update
ha_iot_class: Local Polling
ha_release: 0.42
ha_domain: hassio

2
source/_integrations/justnimbus.markdown
View File

@ -14,7 +14,7 @@ ha_codeowners:
- '@kvanzuijlen'
---
The JustNimbus integration queries the JustNumbus API used by the JustNimbus web dashboard.
The JustNimbus integration queries the JustNimbus API used by the JustNimbus web dashboard.
This integration allows you to collect and save data to get an historic overview of your water bag
usage.

2
source/_integrations/leviton_z_wave.markdown
View File

@ -22,7 +22,7 @@ ha_category:
- Sensor
- Siren
- Switch
- Updates
- Update
ha_domain: leviton_z_wave
ha_integration_type: integration
works_with:

23
source/_integrations/lifx.markdown
View File

@ -40,10 +40,23 @@ Change the light to a new state.
| `entity_id` | String or list of strings that point at `entity_id`s of lights. Use `entity_id: all` to target all.
| `transition` | Duration (in seconds) for the light to fade to the new state.
| `zones` | List of integers for the zone numbers to affect (each LIFX Z strip has 8 zones, starting at 0).
| `infrared` | Automatic infrared level (0..255) when light brightness is low (for compatible bulbs).
| `power` | Turn the light on (`True`) or off (`False`). Leave out to keep the power as it is.
| `...` | Use `color_name`, `brightness` etc. from [`light.turn_on`](/integrations/light/#service-lightturn_on) to specify the new state.
## Set HEV cycle state
You can control the HEV LEDs in LIFX Clean bulbs using the `set_hev_cycle_state` service. The service can start or stop a HEV (or "Clean") cycle either using the default duration configured on the bulb or for a custom duration specified when calling the service. Home Assistant will return or log an error if an incompatible bulb is specified when calling the service.
To determine whether or not a HEV cycle is currently running, Home Assistant exposes a Clean Cycle binary sensor for all HEV-enabled bulbs. This sensor can be used to trigger automations to occur when a HEV cycle starts or stops. To reduce network load, HEV cycle status is only checked every 10 seconds so this sensor may not update instantaneously.
### Service `lifx.set_hev_cycle_state`
| Service data attribute | Description |
| ---------------------- | ----------- |
| `entity_id` | String or list of strings that point at `entity_id`s of LIFX Clean bulbs.
| `power` | Start a HEV cycle (`True`) or stop a cycle (`False`).
| `duration` | Duration (in seconds) for the HEV cycle. The default duration of two hours (7200 seconds) is used if this attribute is omitted.
## Light effects
The LIFX platform supports several light effects. You can start these effects with default options by using the `effect` attribute of the normal [`light.turn_on`](/integrations/light/#service-lightturn_on) service, for example like this:
@ -117,15 +130,19 @@ Run an effect that does nothing, thereby stopping any other effect that might be
| ---------------------- | ----------- |
| `entity_id` | String or list of strings that point at `entity_id`s of lights. Use `entity_id: all` to target all.
## Infrared brightness
Home Assistant will automatically create an Infrared Brightness configuration entity for LIFX Night Vision bulbs. Changing the state of this entity will change the brightness of the LEDs on the bulb.
## Buttons
The LIFX button platform creates two buttons for each LIFX device.
### Identify Button
### Identify button
The Identify button will flash the bulb three times at maximum brightness then return the bulb to the state it was in prior. Successful identification requires the bulb to be powered on and already configured in Home Assistant.
### Restart Button
### Restart button
The Restart button triggers the bulb to restart in exactly the same way as a physical power cycle, which makes it ideal for triggering a new DHCP request from the bulb.

3
source/_integrations/litterrobot.markdown
View File

@ -7,7 +7,7 @@ ha_category:
- Sensor
- Switch
- Vacuum
ha_iot_class: Cloud Polling
ha_iot_class: Cloud Push
ha_release: 2021.3
ha_config_flow: true
ha_codeowners:
@ -40,6 +40,7 @@ You will need a Litter-Robot account as well as a Wi-Fi-enabled Litter-Robot or
| 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. |
| Litter level | `sensor` | Displays the litter level, only for Litter-Robot 4. |
| Pet weight | `sensor` | Displays the last measured pet weight, only for Litter-Robot 4. |
| 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. |

16
source/_integrations/lutron_caseta.markdown
View File

@ -33,9 +33,19 @@ ha_integration_type: integration
[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches, dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` integration in Home Assistant is responsible for communicating with the Lutron Caseta Smart Bridge for the [Caseta](https://www.casetawireless.com/) product line of dimmers, switches, shades, and sensors. It will also communicate with the Lutron Radio RA2 Main Repeater for the [RA2 Select](http://www.lutron.com/en-US/Products/Pages/WholeHomeSystems/RA2Select/Overview.aspx) product line of dimmers, switches, shades, and sensors.
This integration only supports the [Caseta](https://www.casetawireless.com/) line of products. The Smart Bridge (L-BDG2-WH), Smart Bridge PRO (L-BDGPRO2-WH), and RA2 Select (RR-SEL-REP2-BL) models are supported. For the RadioRA 2 and HomeWorks QS product lines, see the [Lutron component](/integrations/lutron/).
This integration supports the [Caséta](https://www.casetawireless.com/), [RA2 Select](https://www.lutron.com/en-US/Products/Pages/WholeHomeSystems/RA2Select/Overview.aspx), [RadioRA 3](https://radiora3.lutron.com/), and [Homeworks QSX](https://www.lutron.com/en-US/Products/Pages/WholeHomeSystems/Homeworks/Overview.aspx) **(not QS)** lines of products.
The currently supported Caseta and RA2 Select devices are:
Supports Bridges:
- Lutron Caséta Smart Hub (L-BDG2-WH)
- Lutron Caséta Smart Bridge PRO (L-BDGPRO2-WH)
- RA2 Select Main Repeaters (RR-SEL-REP2-BL)
- QSX Processor (HQP7)
- RadioRA 3 All-in-One Processor (RR-PROC3)
For the RadioRA 2 and HomeWorks QS product lines, see the [Lutron component](/integrations/lutron/).
The currently supported devices are:
- Wall and plug-in dimmers as [lights](#light)
- Wall switches as [switches](#switch)
@ -128,6 +138,8 @@ After setup, scenes will appear in Home Assistant using an `entity_id` based on
For more information on working with scenes in Home Assistant, see the [Scenes component](/integrations/scene/).
Scenes are not currently supported on RA3 and QSX models.
Available services: `scene.turn_on`.
## Switch

2
source/_integrations/melnor.markdown
View File

@ -2,6 +2,7 @@
title: Melnor Bluetooth
description: Instructions on setting up Melnor Bluetooth devices within Home Assistant.
ha_category:
- Sensor
- Switch
ha_iot_class: Local Polling
ha_bluetooth: true
@ -11,6 +12,7 @@ ha_codeowners:
- '@vanstinator'
ha_domain: melnor
ha_platforms:
- sensor
- switch
ha_integration_type: integration
---

2
source/_integrations/netgear.markdown
View File

@ -3,7 +3,7 @@ title: NETGEAR
description: Instructions on how to integrate NETGEAR routers into Home Assistant.
ha_category:
- Presence Detection
- Updates
- Update
ha_iot_class: Local Polling
ha_release: pre 0.7
ha_domain: netgear

2
source/_integrations/nmbs.markdown
View File

@ -63,5 +63,5 @@ show_on_map:
<p class='img'>
<img src='/images/screenshots/nmbs-card-example.png' />
<p>Example using the <a href="https://github.com/custom-cards/entity-attributes-card">Lovelace Attributes custom card</a> </p>
<p>Example using the <a href="https://github.com/custom-cards/entity-attributes-card">Entity Attributes custom card</a> </p>
</p>

51
source/_integrations/nobo_hub.markdown Normal file
View File

@ -0,0 +1,51 @@
---
title: Nobø Ecohub
description: Instructions on how to integrate Nobø Ecohub into Home Assistant.
ha_category: Climate
ha_release: 2021.10
ha_iot_class: Local Push
ha_config_flow: true
ha_codeowners:
- '@echoromeo'
- '@oyvindwe'
ha_domain: nobo_hub
ha_platforms:
- climate
---
Integrates [Nobø Ecohub](https://www.glendimplex.no/produkter/varmestyring/11123610/noboe-hub/c-77/p-330)
into Home Assistant. This integration is not officially supported or endorsed by Glen Dimplex Nordic AS,
and the authors/maintainers are not official partners of Glen Dimplex Nordic AS.
To configure the integration, you need the 3 last digits of the serial number of your hub. These are located
on the back of the hub. If the hub is on a different local network than Home Assistant, you also need the
IP address of the hub.
{% include integrations/config_flow.md %}
## Operation modes
As for now you can see and change operation and preset for zones and set eco/comfort temperatures if you have
a supported thermostat.
The possible operation modes are as follows:
- "Auto" - In this mode, the zone is in the normal setting and preset shows which state the zone is in right now
(according to calendar setup).
- "Heat" - In this mode the zone in the override setting and in the state selected by preset ("Away", "Eco"
or "Comfort").
This can be utilized the following ways:
- Changing preset to "Away", "Eco", or "Comfort" will automatically change operation to "Heat".
- Changing preset to none will automatically change operation to "Auto" and update preset.
- Changing operation to "Auto" will automatically update preset.
- Changing operation to "Heat" will set preset to "Comfort".
### No preset "Off"
Nobø heaters does not support preset "Off". This is not a limitation in the integration, but a safety mechanism in the
Nobø system (maybe they don't want you to accidentally turn off all your heaters and get frozen pipes). "Away"
temperature is fixed to 7°C and cannot be altered. On/off receivers will be off when the zone is in "Away" status.
For more information, see the [Nobø Ecohub manual](https://help.nobo.no/en/user-manual/before-you-start/what-is-a-weekly-program/).

2
source/_integrations/openweathermap.markdown
View File

@ -30,7 +30,7 @@ You need an API key, which is free, but requires a [registration](https://home.o
<div class='note'>
If you register an new API key with OpenWeatherMap, it will be activated automatically, this typically takes between 10 minutes and 2 hours
after your successful registration. Keep in mind when configuring this integration, that you new API key might
not be activated yet.
not be activated yet. Recent policy changes limit the API access for new registered users with a free plan, they should select the `hourly` mode. The other modes require a paid subscription plan. Invalid API-key errors might occur if your API key is used with the other modes.
</div>
{% include integrations/config_flow.md %}

4
source/_integrations/panasonic_bluray.markdown
View File

@ -22,6 +22,10 @@ Currently known supported models:
- DMP-BDT500
- DMP-BBT01
Models reported not working:
- DP-UB420
If your model is not on the list, then give it a try, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/panasonic_bluray.markdown).
Example configuration:

2
source/_integrations/pi_hole.markdown
View File

@ -5,7 +5,7 @@ ha_category:
- Sensor
- Switch
- System Monitor
- Updates
- Update
ha_iot_class: Local Polling
ha_config_flow: true
ha_release: 0.28

28
source/_integrations/pioneer.markdown
View File

@ -177,3 +177,31 @@ sources:
'Favorites': '45'
'Game': '49'
```
#### VSX-1021
```yaml
port: 8102
sources:
'Phono': '00'
'CD': '01'
'Tuner': '02'
'CD-R/Tape': '03'
'DVD': '04'
'TV/Sat': '05'
'Video 1': '10'
'Multi Channel In': '12'
'Video 2': '14'
'DVR/BDR': '15'
'iPod/USB': '17'
'XM Radio': '18'
'HDMI 1': '19'
'HDMI 2': '20'
'HDMI 3': '21'
'HDMI 4': '22'
'HDMI 5': '23'
'Blu-Ray': '25'
'Home Media Gallery (Internet Radio)': '26'
'Sirius': '27'
'Adapter Port': '33'
```

2
source/_integrations/qnap_qsw.markdown
View File

@ -6,7 +6,7 @@ ha_category:
- Binary Sensor
- Button
- Sensor
- Updates
- Update
ha_iot_class: Local Polling
ha_config_flow: true
ha_domain: qnap_qsw

1
source/_integrations/rainmachine.markdown
View File

@ -7,7 +7,6 @@ ha_category:
- Sensor
- Switch
- Update
- Updates
ha_release: 0.69
ha_iot_class: Local Polling
ha_config_flow: true

2
source/_integrations/rpi_power.markdown
View File

@ -15,6 +15,6 @@ ha_platforms:
ha_integration_type: integration
---
The `rpi_power` integration allows you to detect [bad power supply](https://www.raspberrypi.org/documentation/hardware/raspberrypi/power/README.md) on Raspberry Pi.
The `rpi_power` integration allows you to detect [bad power supply](https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#power-supply-warnings) on Raspberry Pi.
{% include integrations/config_flow.md %}

2
source/_integrations/sensibo.markdown
View File

@ -10,7 +10,7 @@ ha_category:
- Select
- Sensor
- Switch
- Updates
- Update
ha_release: 0.44
ha_iot_class: Cloud Polling
ha_config_flow: true

1
source/_integrations/sensor.markdown
View File

@ -33,6 +33,7 @@ The type of data a sensor returns impacts how it is displayed in the frontend. T
- **gas**: Gasvolume in m³ or ft³
- **humidity**: Percentage of humidity in the air
- **illuminance**: The current light level in lx or lm
- **moisture**: Percentage of water in a substance
- **monetary**: The monetary value
- **nitrogen_dioxide**: Concentration of Nitrogen Dioxide in µg/m³
- **nitrogen_monoxide**: Concentration of Nitrogen Monoxide in µg/m³

8
source/_integrations/simplisafe.markdown
View File

@ -5,6 +5,7 @@ ha_release: 0.81
ha_iot_class: Cloud Polling
ha_category:
- Alarm
- Button
- Lock
ha_config_flow: true
ha_codeowners:
@ -13,6 +14,7 @@ ha_domain: simplisafe
ha_platforms:
- alarm_control_panel
- binary_sensor
- button
- diagnostics
- lock
- sensor
@ -53,12 +55,6 @@ SimpliSafe authenticates users via its web app. Due to technical limitations, th
## Services
### `simplisafe.clear_notifications`
Clear any existing notifications within the SimpliSafe cloud; this will mark existing
notifications as "read" in the SimpliSafe web and mobile apps, as well as prevent them
from triggering future `SIMPLISAFE_NOTIFICATION` events.
### `simplisafe.remove_pin`
Remove a SimpliSafe PIN (by label or PIN value).

1
source/_integrations/sms.markdown
View File

@ -121,7 +121,6 @@ You will need a USB GSM stick modem or device like SIM800L v2 connected via USB
Need to unlock it using [this guide](http://blog.asiantuntijakaveri.fi/2015/07/convert-huawei-e3372h-153-from.html))
- [Huawei E3531](https://www.amazon.com/Modem-Huawei-Unlocked-Caribbean-Desbloqueado/dp/B011YZZ6Q2/ref=sr_1_1?keywords=Huawei+E3531&qid=1581447800&sr=8-1)
- [Huawei E3272](https://www.amazon.com/Huawei-E3272s-506-Unlocked-Americas-Europe/dp/B00HBL51OQ)
- [SIM800C](https://www.amazon.com/gp/product/B087Z6F953/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1)
- ZTE K3565-Z
### List of modems known to NOT work

13
source/_integrations/sonos.markdown
View File

@ -69,7 +69,18 @@ The microphone can only be enabled/disabled from physical buttons on the Sonos d
The favorites sensor provides the names and `media_content_id` values for each of the favorites saved to My Sonos in the native Sonos app. This sensor is intended for users that need to access the favorites in a custom template. For most users, accessing favorites by using the Media Browser functionality and "Play media" script/automation action is recommended.
If using the provided `media_content_id` with the `media_player.play_media` service, the `media_content_type` must be set to "favorite_item_id".
When calling the `media_player.play_media` service, the `media_content_type` must be set to "favorite_item_id" and the `media_content_id` must be set to just the key portion of the favorite item.
Example service call:
```yaml
service: media_player.play_media
target:
entity_id: media_player.sonos_speaker1
data:
media_content_type: "favorite_item_id"
media_content_id: "FV:2/31"
```
Example templates:

10
source/_integrations/speedtestdotnet.markdown
View File

@ -18,7 +18,6 @@ ha_integration_type: integration
The Speedtest.net integration uses the [Speedtest.net](https://speedtest.net/) web service to measure network bandwidth performance.
{% include integrations/config_flow.md %}
Most Speedtest.net servers require TCP port 8080 outbound to function. Without this port open you may experience significant delays or no results at all. See note on their [help page](https://www.speedtest.net/help).
@ -34,15 +33,6 @@ sensors:
- Ping sensor: Reaction time in ms of your connection (how fast you get a response after you’ve sent out a request).
- Download sensor: The download speed (Mbit/s).
- Upload sensor: The upload speed (Mbit/s).
### Service
Once loaded, the integration will expose a service (`speedtestdotnet.speedtest`) that can be called to run a Speedtest.net speed test on demand. This service takes no parameters. This can be useful when auto update has been disabled in the integration options.
```yaml
action:
service: speedtestdotnet.speedtest
```
This integration uses [speedtest-cli](https://github.com/sivel/speedtest-cli) to gather network performance data from Speedtest.net.
Please be aware of the potential [inconsistencies](https://github.com/sivel/speedtest-cli#inconsistency) that this integration may display.

28
source/_integrations/switchbee.markdown Normal file
View File

@ -0,0 +1,28 @@
---
title: SwitchBee
description: Instructions for how to integrate SwitchBee accessories within Home Assistant.
ha_category:
- Switch
ha_release: 2022.10
ha_iot_class: local Polling
ha_config_flow: true
ha_codeowners:
- '@jafar-atili'
ha_domain: switchbee
ha_platforms:
- switch
ha_integration_type: integration
---
[SwitchBee](https://www.switchbee.com), is an innovation company making smart homes more accessible and affordable to any household environment.
There is currently support for the following device types:
- Switch
- Timed Power Switch (Boiler)
- Group Switch
- Timed Switch
Supported devices will be discovered after the SwitchBee integration is configured.
{% include integrations/config_flow.md %}

2
source/_integrations/synology_dsm.markdown
View File

@ -4,7 +4,7 @@ description: Instructions on how to integrate the Synology DSM sensor within Hom
ha_category:
- Camera
- System Monitor
- Updates
- Update
ha_release: 0.32
ha_iot_class: Local Polling
ha_domain: synology_dsm

2
source/_integrations/thermopro.markdown
View File

@ -21,6 +21,8 @@ Integrates [ThermoPro](https://buythermopro.com/) devices into Home Assistant.
- [TP359](https://buythermopro.com/product/thermopro-tp59-bluetooth-wireless-thermometer-hygrometer-humidity-monitor/)
- [TP357](https://buythermopro.com/product/thermopro-tp357-bluetooth-digital-indoor-hygrometer-thermometer/)
- [TP358](https://buythermopro.com/product/tp358/)
- [TP393](https://buythermopro.com/product/tp393/)
The ThermoPro integration will automatically discover devices once the [Bluetooth](/integrations/bluetooth) integration is enabled and functional.

26
source/_integrations/tilt_ble.markdown Normal file
View File

@ -0,0 +1,26 @@
---
title: Tilt Hydrometer Bluetooth
description: Instructions on how to integrate Tilt Hydrometer BLE devices into Home Assistant.
ha_category:
- Sensor
ha_bluetooth: true
ha_release: "2022.10"
ha_iot_class: Local Push
ha_codeowners:
- '@apt-itude'
ha_domain: tilt_ble
ha_config_flow: true
ha_platforms:
- sensor
ha_integration_type: integration
---
Integrates [Tilt Hydrometer](https://tilthydrometer.com/) BLE devices into Home Assistant.
{% include integrations/config_flow.md %}
The Tilt Hydrometer BLE integration will automatically discover devices once the [Bluetooth](/integrations/bluetooth) integration is enabled and functional.
## Supported devices
- [Tilt Hydrometer and Thermometer](https://tilthydrometer.com/products/copy-of-tilt-floating-wireless-hydrometer-and-thermometer-for-brewing) (all colors)

8
source/_integrations/time_date.markdown
View File

@ -1,6 +1,6 @@
---
title: Time & Date
description: Instructions on how to integrate the time and the date within Home Assistant.
description: Instructions on how to create time and the date sensors within Home Assistant.
ha_category:
- Calendar
ha_iot_class: Local Push
@ -14,7 +14,7 @@ ha_platforms:
ha_integration_type: integration
---
The time and date (`time_date`) integration allows one to show the current date or time in different formats. All values are based on the timezone which is set in "General Configuration".
The time and date (`time_date`) integration allows one to create sensors for the current date or time in different formats. All values are based on the timezone which is set in "General Configuration".
To have these sensors available in your installation, add the following to your `configuration.yaml` file (each option creates a separate sensor that contains appropriate data, e.g., `sensor.date` for the `date` option):
@ -36,7 +36,7 @@ sensor:
{% configuration %}
display_options:
description: The option to display. The types *date_time*, *date_time_utc*, *time_date*, and *date_time_iso* shows the date and the time. The other types just the time or the date. *beat* shows the [Swatch Internet Time](https://en.wikipedia.org/wiki/Swatch_Internet_Time).
description: The sensors to create. The types *date_time*, *date_time_utc*, *time_date*, and *date_time_iso* create combined date and the time sensors. The other types just the time sensor or the date sensor. *beat* creates the [Swatch Internet Time](https://en.wikipedia.org/wiki/Swatch_Internet_Time).
required: true
type: list
{% endconfiguration %}
@ -50,8 +50,6 @@ Sensors including the time update every minute, the date sensor updates each day
# Producing your own custom time and date sensor
Whilst there are a number of `display_options` exposed by this sensor, they cannot hope to satisfy everyone, and large parts of the world will find that their local display conventions are not included.
The following can be used to create a time and date sensor whose output can be properly customised to use your own preferred formatting, specified in the call to timestamp_custom() using standard [Python datetime formatting](https://docs.python.org/3.8/library/datetime.html#strftime-and-strptime-behavior).
{% raw %}

2
source/_integrations/unifi.markdown
View File

@ -6,7 +6,7 @@ ha_category:
- Presence Detection
- Sensor
- Switch
- Updates
- Update
ha_release: 0.81
ha_iot_class: Local Push
ha_config_flow: true

6
source/_integrations/universal.markdown
View File

@ -58,6 +58,7 @@ media_player:
is_volume_muted: ENTITY_ID|ATTRIBUTE
state: ENTITY_ID|ATTRIBUTE
device_class: tv
unique_id: a_unique_string
```
{% configuration %}
@ -85,6 +86,10 @@ device_class:
description: The device class that this entity represents. Can be `tv`, `speaker`, or `receiver`.
required: false
type: string
unique_id:
description: A unique identifier for this entity. Needs to be unique within the `media_player` platform.
required: false
type: string
{% endconfiguration %}
The Universal Media Player will primarily imitate one of its `children`. The Universal Media Player will control the first child on the list that is active (not idle/off). The Universal Media Player will also inherit its state from the first active child if a `state_template` is not provided. Entities in the `children:` list must be media players, but the state template can contain any entity.
@ -305,6 +310,7 @@ media_player:
data:
activity: "{{ source }}"
device_class: tv
unique_id: media_room_harmony_hub
```
{% endraw %}

43
source/_integrations/uscis.markdown
View File

@ -1,43 +0,0 @@
---
title: U.S. Citizenship and Immigration Services (USCIS)
description: Instructions on how to set up USCIS within Home Assistant.
ha_category:
- Sensor
ha_release: 0.68
ha_iot_class: Cloud Polling
ha_domain: uscis
ha_platforms:
- sensor
ha_integration_type: integration
---
<div class='note warning'>
This integration is pending removal from Home Assistant and will be no longer available as of Home Assistant 2022.10.
</div>
The `uscis` sensor integration allows you get updates on your USCIS case using your case/receipt number. The sensor gets the case information from the [USCIS Website](https://egov.uscis.gov/casestatus/landing.do).
## Configuration
To use this sensor in your installation, add the following to your `configuration.yaml` file:
```yaml
sensor:
- platform: uscis
case_id: YOUR_CASE_NUMBER
name: OPTIONAL_NAME
```
{% configuration %}
name:
description: Name of the sensor in Home Assistant.
required: false
default: USCIS
type: string
case_id:
description: Case/receipt number used to get the case details from the USCIS web client.
required: true
type: string
{% endconfiguration %}
All the data will be fetched from [USCIS](https://egov.uscis.gov/casestatus/mycasestatus.do).

2
source/_integrations/wemo.markdown
View File

@ -30,7 +30,7 @@ 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/smart-home/wemo/wemo-wifi-smart-dimmer/p/p-wds060/))
- Light (Belkin WeMo LED lights and Smart Dimmer Switch)
- 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

2
source/_integrations/wled.markdown
View File

@ -5,7 +5,7 @@ ha_category:
- Light
- Sensor
- Switch
- Updates
- Update
ha_release: 0.102
ha_iot_class: Local Push
ha_config_flow: true

6
source/_integrations/workday.markdown
View File

@ -165,9 +165,3 @@ automation:
target:
entity_id: switch.heater
```
<div class='note'>
Please remember that [as explained here](/docs/configuration/devices/) you can only have a single `automation:` entry. Add the automation to your existing automations.
</div>

2
source/_integrations/xiaomi_ble.markdown
View File

@ -33,7 +33,7 @@ It is possible that we detect your device because it uses the MiBeacon protocol
- Moisture
- Illumination
- Conductivity
- Formalehyde
- Formaldehyde
- Consumable
- Voltage
- Battery

10
source/_integrations/zha.markdown
View File

@ -180,6 +180,8 @@ Some devices can be auto-discovered, which can simplify the ZHA setup process. T
| [slae.sh CC2652RB development stick](https://slae.sh/projects/cc2652/) | USB | 10C4:EA60 |
| [ZigStar Stick (CC2652 + CH340B variant)](https://zig-star.com/projects/zigbee-stick-v4/) | USB | 1A86:7523 |
| [Tube’s EFR32 Pro Ethernet/Serial Coordinator](https://www.tubeszb.com/) | USB| 10C4:EA60 |
| [ZigStar Coordinators](https://zig-star.com/) | USB| 1A86:7523 |
| [ZigStar LAN/POE Coordinators ](https://zig-star.com/projects/zigbee-gw-lan/) | Zeroconf | zigstargw.local. |
| [Tube's CC2652P2 USB-powered Zigbee to Ethernet Serial Coordinator)](https://www.tubeszb.com/) | Zeroconf | tube_zb_gw_cc2652p2.local. |
| [Tube's CC2652P2 PoE-powered Zigbee to Ethernet Serial Coordinator)](https://www.tubeszb.com/) | Zeroconf | tube_zb_gw_cc2652p2_poe.local. |
| [Tube's EFR32 Based Zigbee to Ethernet Serial Coordinator)](https://www.tubeszb.com/) | Zeroconf | tube_zb_gw_efr32.local. |
@ -402,6 +404,14 @@ Note that not all devices support binding as it depends on the Zigbee implementa
Binding a remote directly to a bulb or group has the benefit of faster response time and smoother control. This greatly improves user feedback experience functions like dimming as the remote then directly dims the lightbulb and thus does not have to make the software roundtrip via the ZHA coordinator.
## Zigbee backup and restore in ZHA
Zigbee Home Automation (ZHA) integration now features Zigbee network backup, restore/recovery, and migrating between Zigbee coordinators. Backups are taken automatically however, a single backup to a file for easy download can also be manually created from the configuration page under Network Settings.
After restoring a Home Assistant backup, you can re-configure ZHA and migrate to a new Zigbee Coordinator adapter without any loss of your settings or devices that were connected. This is helpful if your current radio fails or a new radio adapter type and model comes out that you may want to migrate to.
Within ZHA is possible to use this backup and restore feature to migrate between some different radio types, if the respective radio library supports it. Currently, ZHA supports migrating the Zigbee network between different Zigbee Coordinator adapters based on chips from Silicon Labs, Texas Instruments, or ConBee/RaspBee if the backup was made from inside ZHA.
## Troubleshooting
To help resolve any kinks or compatibility problems, report bugs as issues with debug logs. Please follow the instructions in this troubleshooting section.

6
source/_integrations/zwave_js.markdown
View File

@ -17,7 +17,7 @@ ha_category:
- Sensor
- Siren
- Switch
- Updates
- Update
ha_release: '2021.2'
ha_iot_class: Local Push
ha_config_flow: true
@ -717,9 +717,9 @@ Some Z-Wave USB sticks can be auto-discovered, which can simplify the Z-Wave set
| Device | Identifier | Vendor |
| -------| ---------- | ------ |
| Aeotec Z-Stick Gen5+ | 0658:0200 | https://aeotec.com/z-wave-usb-stick/ |
| Aeotec Z-Stick Gen5+ | 0658:0200 | https://aeotec.com/products/aeotec-z-stick-gen5/ |
| Nortek HUSBZB-1 | 10C4:8A2A | https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/ |
| Zooz ZST10 | 10C4:EA60 | https://www.getzooz.com/zooz-zst10-s2-stick.html |
| Zooz ZST10 | 10C4:EA60 | https://www.getzooz.com/zooz-zst10-s2-stick/ |
| Z-WaveMe UZB | 0658:0200 | https://z-wave.me/products/uzb/ |
Additional devices may be discoverable, however only devices that have been confirmed discoverable are listed above.

374
source/_posts/2022-09-07-release-20229.markdown
View File

@ -37,6 +37,11 @@ Now I know that everyone usually expects [@frenck] to be writing these release n
- [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.9.1 - September 8](#release-202291---september-8)
- [Release 2022.9.2 - September 11](#release-202292---september-11)
- [Release 2022.9.3 - September 13](#release-202293---september-13)
- [Release 2022.9.4 - September 14](#release-202294---september-14)
- [Release 2022.9.5 - September 18](#release-202295---september-18)
- [Need help? Join the community](#need-help-join-the-community)
- [Breaking Changes](#breaking-changes)
- [All changes](#all-changes)
@ -126,7 +131,7 @@ For now, only Jasco products are supported. Nabu Casa has been talking to other
## Zigbee backup and restore + migration
The Zigbee Home Automation (ZHA) integration now supports network backups and migrating between Zigbee coordinators. Backups are taken automatically but can also be manually created from the configuration page. After restoring a Home Assistant backup, you can re-configure ZHA and migrate to a new Zigbee coordinator without any loss of your settings or devices that were connected. This is helpful if your current radio fails or a new radio comes out that you may want to migrate to.s
The Zigbee Home Automation (ZHA) integration now supports network backups and migrating between Zigbee coordinators. Backups are taken automatically but can also be manually created from the configuration page. After restoring a Home Assistant backup, you can re-configure ZHA and migrate to a new Zigbee coordinator without any loss of your settings or devices that were connected. This is helpful if your current radio fails or a new radio comes out that you may want to migrate to.
<img class="no-shadow" src='/images/blog/2022-09/zigbee.png' alt='Screenshot showing the Zigbee Home Automation configuration page and the new backup functionality'><br>
@ -230,6 +235,373 @@ The following integrations are now available via the Home Assistant UI:
[Pushover]: /integrations/pushover
[Volvo On Call]: /integrations/volvooncall
## Release 2022.9.1 - September 8
- Show progress for zwave_js.update entity ([@raman325] - [#77905]) ([zwave_js docs])
- Fix `len` method typo for Osram light ([@Vaskivskyi] - [#78008]) ([osramlightify docs])
- Add value ID to zwave_js device diagnostics ([@raman325] - [#78015]) ([zwave_js docs])
- Fix zwave_js default emulate hardware in options flow ([@MartinHjelmare] - [#78024]) ([zwave_js docs])
- Extract lametric device from coordinator in notify ([@ludeeus] - [#78027]) ([lametric docs])
- Bump velbus-aio to 2022.9.1 ([@Cereal2nd] - [#78039]) ([velbus docs])
- Fix zwave_js device re-interview ([@MartinHjelmare] - [#78046]) ([zwave_js docs])
- Bump bluetooth-adapters to 0.3.5 ([@bdraco] - [#78052]) ([bluetooth docs])
- Bump bluetooth-auto-recovery to 0.3.2 ([@bdraco] - [#78063]) ([bluetooth docs])
- Fix bug with 1st gen RainMachine controllers and unknown API calls ([@bachya] - [#78070]) ([rainmachine docs])
- Bump pylitterbot to 2022.9.1 ([@natekspencer] - [#78071]) ([litterrobot docs])
- Allow OpenWeatherMap config flow to test using old API to pass ([@jbouwh] - [#78074]) ([openweathermap docs])
- Fix Ecobee remote sensors not updating ([@rlippmann] - [#78035]) ([ecobee docs])
[#77905]: https://github.com/home-assistant/core/pull/77905
[#77968]: https://github.com/home-assistant/core/pull/77968
[#78008]: https://github.com/home-assistant/core/pull/78008
[#78015]: https://github.com/home-assistant/core/pull/78015
[#78024]: https://github.com/home-assistant/core/pull/78024
[#78027]: https://github.com/home-assistant/core/pull/78027
[#78035]: https://github.com/home-assistant/core/pull/78035
[#78039]: https://github.com/home-assistant/core/pull/78039
[#78046]: https://github.com/home-assistant/core/pull/78046
[#78052]: https://github.com/home-assistant/core/pull/78052
[#78063]: https://github.com/home-assistant/core/pull/78063
[#78070]: https://github.com/home-assistant/core/pull/78070
[#78071]: https://github.com/home-assistant/core/pull/78071
[#78074]: https://github.com/home-assistant/core/pull/78074
[@Cereal2nd]: https://github.com/Cereal2nd
[@MartinHjelmare]: https://github.com/MartinHjelmare
[@Vaskivskyi]: https://github.com/Vaskivskyi
[@bachya]: https://github.com/bachya
[@bdraco]: https://github.com/bdraco
[@frenck]: https://github.com/frenck
[@jbouwh]: https://github.com/jbouwh
[@ludeeus]: https://github.com/ludeeus
[@natekspencer]: https://github.com/natekspencer
[@raman325]: https://github.com/raman325
[@rlippmann]: https://github.com/rlippmann
[abode docs]: /integrations/abode/
[accuweather docs]: /integrations/accuweather/
[acmeda docs]: /integrations/acmeda/
[bluetooth docs]: /integrations/bluetooth/
[ecobee docs]: /integrations/ecobee/
[lametric docs]: /integrations/lametric/
[litterrobot docs]: /integrations/litterrobot/
[openweathermap docs]: /integrations/openweathermap/
[osramlightify docs]: /integrations/osramlightify/
[rainmachine docs]: /integrations/rainmachine/
[velbus docs]: /integrations/velbus/
[zwave_js docs]: /integrations/zwave_js/
## Release 2022.9.2 - September 11
- Fix reload of MQTT config entries ([@jbouwh] - [#76089]) ([mqtt docs])
- Clear MQTT discovery topic when a disabled entity is removed ([@jbouwh] - [#77757]) ([mqtt docs])
- Improve warning messages on invalid received modes ([@jbouwh] - [#77909]) ([mqtt docs])
- Handle missing supported brands ([@balloob] - [#78090]) ([websocket_api docs])
- Fix switchbot writing state too frequently ([@bdraco] - [#78094]) ([switchbot docs])
- Fix LIFX light turning on while fading off ([@amelchio] - [#78095]) ([lifx docs])
- Fix zwave_js update entity ([@raman325] - [#78116]) ([zwave_js docs])
- Improve unique_id collision checks in entity_platform ([@emontnemery] - [#78132])
- Allow non-integers in threshold sensor config flow ([@emontnemery] - [#78137]) ([threshold docs])
- Bump bluetooth-adapters to 0.3.6 ([@bdraco] - [#78138]) ([bluetooth docs])
- Add missing strings for errors in amberelectric config flow ([@Vaskivskyi] - [#78140]) ([amberelectric docs])
- Bump aioecowitt to 2022.09.1 ([@pvizeli] - [#78142]) ([ecowitt docs])
- Add missing moisture sensor to xiaomi_ble ([@Jc2k] - [#78160]) ([xiaomi_ble docs])
- Bump pySwitchbot to 0.19.1 ([@bdraco] - [#78168]) ([switchbot docs])
- Bump aiohomekit to 1.5.3 ([@bdraco] - [#78170]) ([homekit_controller docs])
- Fix ecowitt typing ([@balloob] - [#78171]) ([ecowitt docs])
- Fix sending notification to multiple targets in Pushover ([@engrbm87] - [#78111]) ([pushover docs])
- Add dependencies to ecowitt ([@pvizeli] - [#78187]) ([ecowitt docs])
- Bump led-ble to 0.8.3 ([@bdraco] - [#78188]) ([led_ble docs])
- Fix switchbot not setting up when already connected at startup ([@bdraco] - [#78198]) ([switchbot docs])
- Fix Yale Access Bluetooth not setting up when already connected at startup ([@bdraco] - [#78199]) ([yalexs_ble docs])
- Bump ZHA dependencies ([@puddly] - [#78201]) ([zha docs])
- Close stale switchbot connections at setup time ([@bdraco] - [#78202]) ([switchbot docs])
- Bump aiohomekit to 1.5.4 to handle stale ble connections at startup ([@bdraco] - [#78203]) ([homekit_controller docs])
- Landis+Gyr integration: increase timeout and add debug logging ([@vpathuis] - [#78025]) ([landisgyr_heat_meter docs])
- Bump bluetooth-adapters to 0.4.1 ([@bdraco] - [#78205]) ([bluetooth docs])
- Bump `regenmaschine` to 2022.09.1 ([@bachya] - [#78210]) ([rainmachine docs])
- Bump led_ble to 0.8.5 ([@bdraco] - [#78215]) ([led_ble docs])
- Bump pysensibo to 1.0.20 ([@gjohansson-ST] - [#78222]) ([sensibo docs])
- Bump PySwitchbot to 0.19.5 ([@bdraco] - [#78224]) ([switchbot docs])
- Bump yalexs-ble to 1.8.1 ([@bdraco] - [#78225]) ([yalexs_ble docs])
- Bump led-ble to 0.9.1 ([@bdraco] - [#78226]) ([led_ble docs])
- Bump aiohomekit to 1.5.6 ([@bdraco] - [#78228]) ([homekit_controller docs])
[#76089]: https://github.com/home-assistant/core/pull/76089
[#77757]: https://github.com/home-assistant/core/pull/77757
[#77909]: https://github.com/home-assistant/core/pull/77909
[#77968]: https://github.com/home-assistant/core/pull/77968
[#78025]: https://github.com/home-assistant/core/pull/78025
[#78081]: https://github.com/home-assistant/core/pull/78081
[#78090]: https://github.com/home-assistant/core/pull/78090
[#78094]: https://github.com/home-assistant/core/pull/78094
[#78095]: https://github.com/home-assistant/core/pull/78095
[#78111]: https://github.com/home-assistant/core/pull/78111
[#78116]: https://github.com/home-assistant/core/pull/78116
[#78132]: https://github.com/home-assistant/core/pull/78132
[#78137]: https://github.com/home-assistant/core/pull/78137
[#78138]: https://github.com/home-assistant/core/pull/78138
[#78140]: https://github.com/home-assistant/core/pull/78140
[#78142]: https://github.com/home-assistant/core/pull/78142
[#78160]: https://github.com/home-assistant/core/pull/78160
[#78168]: https://github.com/home-assistant/core/pull/78168
[#78170]: https://github.com/home-assistant/core/pull/78170
[#78171]: https://github.com/home-assistant/core/pull/78171
[#78187]: https://github.com/home-assistant/core/pull/78187
[#78188]: https://github.com/home-assistant/core/pull/78188
[#78198]: https://github.com/home-assistant/core/pull/78198
[#78199]: https://github.com/home-assistant/core/pull/78199
[#78201]: https://github.com/home-assistant/core/pull/78201
[#78202]: https://github.com/home-assistant/core/pull/78202
[#78203]: https://github.com/home-assistant/core/pull/78203
[#78205]: https://github.com/home-assistant/core/pull/78205
[#78210]: https://github.com/home-assistant/core/pull/78210
[#78215]: https://github.com/home-assistant/core/pull/78215
[#78222]: https://github.com/home-assistant/core/pull/78222
[#78224]: https://github.com/home-assistant/core/pull/78224
[#78225]: https://github.com/home-assistant/core/pull/78225
[#78226]: https://github.com/home-assistant/core/pull/78226
[#78228]: https://github.com/home-assistant/core/pull/78228
[@Jc2k]: https://github.com/Jc2k
[@Vaskivskyi]: https://github.com/Vaskivskyi
[@amelchio]: https://github.com/amelchio
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@bdraco]: https://github.com/bdraco
[@emontnemery]: https://github.com/emontnemery
[@engrbm87]: https://github.com/engrbm87
[@frenck]: https://github.com/frenck
[@gjohansson-ST]: https://github.com/gjohansson-ST
[@jbouwh]: https://github.com/jbouwh
[@puddly]: https://github.com/puddly
[@pvizeli]: https://github.com/pvizeli
[@raman325]: https://github.com/raman325
[@vpathuis]: https://github.com/vpathuis
[abode docs]: /integrations/abode/
[accuweather docs]: /integrations/accuweather/
[acmeda docs]: /integrations/acmeda/
[amberelectric docs]: /integrations/amberelectric/
[bluetooth docs]: /integrations/bluetooth/
[ecowitt docs]: /integrations/ecowitt/
[homekit_controller docs]: /integrations/homekit_controller/
[landisgyr_heat_meter docs]: /integrations/landisgyr_heat_meter/
[led_ble docs]: /integrations/led_ble/
[lifx docs]: /integrations/lifx/
[mqtt docs]: /integrations/mqtt/
[pushover docs]: /integrations/pushover/
[rainmachine docs]: /integrations/rainmachine/
[sensibo docs]: /integrations/sensibo/
[switchbot docs]: /integrations/switchbot/
[threshold docs]: /integrations/threshold/
[websocket_api docs]: /integrations/websocket_api/
[xiaomi_ble docs]: /integrations/xiaomi_ble/
[yalexs_ble docs]: /integrations/yalexs_ble/
[zha docs]: /integrations/zha/
[zwave_js docs]: /integrations/zwave_js/
## Release 2022.9.3 - September 13
- Move up setup of service to make it more robust when running multiple instances of deCONZ ([@Kane610] - [#77621]) ([deconz docs])
- Bump blinkpy to 0.19.2 ([@Vaskivskyi] - [#78097]) ([blink docs])
- Bump PyViCare==2.17.0 ([@TheJulianJES] - [#78232]) ([vicare docs])
- Fix missing dependency for dbus_next ([@d-walsh] - [#78235]) ([bluetooth docs])
- Bump bluetooth-auto-recovery to 0.3.3 ([@bdraco] - [#78245]) ([bluetooth docs])
- Bump aiodiscover to 1.4.13 ([@bdraco] - [#78253]) ([dhcp docs])
- Bump pySwitchbot to 0.19.6 ([@bdraco] - [#78304]) ([switchbot docs])
- Make yalexs_ble matcher more specific ([@bdraco] - [#78307]) ([yalexs_ble docs])
- Fix sengled bulbs in ZHA ([@dmulcahey] - [#78315]) ([zha docs])
- Fix calculating gas cost for gas measured in ft3 ([@emontnemery] - [#78327]) ([energy docs])
- Bump bleak to 0.17.0 ([@bdraco] - [#78333]) ([bluetooth docs])
- Drop initial when loading input_number from storage ([@emontnemery] - [#78354]) ([input_number docs])
- Don't allow partial update of input_number settings ([@emontnemery] - [#78356]) ([input_number docs])
- Bump PySwitchbot to 0.19.8 ([@bdraco] - [#78361]) ([switchbot docs])
- Bump yalexs-ble to 1.9.0 ([@bdraco] - [#78362]) ([yalexs_ble docs])
- Bump xiaomi-ble to 0.9.3 ([@bdraco] - [#78301]) ([xiaomi_ble docs])
- Bump xiaomi-ble to 0.10.0 ([@bdraco] - [#78365]) ([xiaomi_ble docs])
- Bump led-ble to 0.10.0 ([@bdraco] - [#78367]) ([led_ble docs])
- Bump aiohomekit to 1.5.7 ([@bdraco] - [#78369]) ([homekit_controller docs])
- Don't allow partial update of counter settings ([@emontnemery] - [#78371]) ([counter docs])
- Don't allow partial update of input_boolean settings ([@emontnemery] - [#78372]) ([input_boolean docs])
- Don't allow partial update of input_datetime settings ([@emontnemery] - [#78373]) ([input_datetime docs])
- Don't allow partial update of input_button settings ([@emontnemery] - [#78374]) ([input_button docs])
- Don't allow partial update of input_select settings ([@emontnemery] - [#78376]) ([input_select docs])
- Don't allow partial update of input_text settings ([@emontnemery] - [#78377]) ([input_text docs])
- Don't allow partial update of timer settings ([@emontnemery] - [#78378]) ([timer docs])
- Unregister EcoWitt webhook at unload ([@pvizeli] - [#78388]) ([ecowitt docs])
- Fix flapping system log test ([@bdraco] - [#78391]) ([system_log docs])
- Fix CI workflow caching ([@cdce8p] - [#78398])
- Update frontend to 20220907.1 ([@bramkragten] - [#78404]) ([frontend docs])
- Bump govee-ble to 0.17.3 ([@bdraco] - [#78405]) ([govee_ble docs])
- Fix bug with RainMachine update entity ([@bachya] - [#78411]) ([rainmachine docs])
- Retry on unavailable IPMA api ([@dgomes] - [#78332]) ([ipma docs])
[#77621]: https://github.com/home-assistant/core/pull/77621
[#77968]: https://github.com/home-assistant/core/pull/77968
[#78081]: https://github.com/home-assistant/core/pull/78081
[#78097]: https://github.com/home-assistant/core/pull/78097
[#78169]: https://github.com/home-assistant/core/pull/78169
[#78232]: https://github.com/home-assistant/core/pull/78232
[#78235]: https://github.com/home-assistant/core/pull/78235
[#78245]: https://github.com/home-assistant/core/pull/78245
[#78253]: https://github.com/home-assistant/core/pull/78253
[#78301]: https://github.com/home-assistant/core/pull/78301
[#78304]: https://github.com/home-assistant/core/pull/78304
[#78307]: https://github.com/home-assistant/core/pull/78307
[#78315]: https://github.com/home-assistant/core/pull/78315
[#78327]: https://github.com/home-assistant/core/pull/78327
[#78332]: https://github.com/home-assistant/core/pull/78332
[#78333]: https://github.com/home-assistant/core/pull/78333
[#78354]: https://github.com/home-assistant/core/pull/78354
[#78356]: https://github.com/home-assistant/core/pull/78356
[#78361]: https://github.com/home-assistant/core/pull/78361
[#78362]: https://github.com/home-assistant/core/pull/78362
[#78365]: https://github.com/home-assistant/core/pull/78365
[#78367]: https://github.com/home-assistant/core/pull/78367
[#78369]: https://github.com/home-assistant/core/pull/78369
[#78371]: https://github.com/home-assistant/core/pull/78371
[#78372]: https://github.com/home-assistant/core/pull/78372
[#78373]: https://github.com/home-assistant/core/pull/78373
[#78374]: https://github.com/home-assistant/core/pull/78374
[#78376]: https://github.com/home-assistant/core/pull/78376
[#78377]: https://github.com/home-assistant/core/pull/78377
[#78378]: https://github.com/home-assistant/core/pull/78378
[#78388]: https://github.com/home-assistant/core/pull/78388
[#78391]: https://github.com/home-assistant/core/pull/78391
[#78398]: https://github.com/home-assistant/core/pull/78398
[#78404]: https://github.com/home-assistant/core/pull/78404
[#78405]: https://github.com/home-assistant/core/pull/78405
[#78411]: https://github.com/home-assistant/core/pull/78411
[@Kane610]: https://github.com/Kane610
[@TheJulianJES]: https://github.com/TheJulianJES
[@Vaskivskyi]: https://github.com/Vaskivskyi
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@bdraco]: https://github.com/bdraco
[@bramkragten]: https://github.com/bramkragten
[@cdce8p]: https://github.com/cdce8p
[@d-walsh]: https://github.com/d-walsh
[@dgomes]: https://github.com/dgomes
[@dmulcahey]: https://github.com/dmulcahey
[@emontnemery]: https://github.com/emontnemery
[@frenck]: https://github.com/frenck
[@pvizeli]: https://github.com/pvizeli
[abode docs]: /integrations/abode/
[accuweather docs]: /integrations/accuweather/
[acmeda docs]: /integrations/acmeda/
[blink docs]: /integrations/blink/
[bluetooth docs]: /integrations/bluetooth/
[counter docs]: /integrations/counter/
[deconz docs]: /integrations/deconz/
[dhcp docs]: /integrations/dhcp/
[ecowitt docs]: /integrations/ecowitt/
[energy docs]: /integrations/energy/
[frontend docs]: /integrations/frontend/
[govee_ble docs]: /integrations/govee_ble/
[homekit_controller docs]: /integrations/homekit_controller/
[input_boolean docs]: /integrations/input_boolean/
[input_button docs]: /integrations/input_button/
[input_datetime docs]: /integrations/input_datetime/
[input_number docs]: /integrations/input_number/
[input_select docs]: /integrations/input_select/
[input_text docs]: /integrations/input_text/
[ipma docs]: /integrations/ipma/
[led_ble docs]: /integrations/led_ble/
[rainmachine docs]: /integrations/rainmachine/
[switchbot docs]: /integrations/switchbot/
[system_log docs]: /integrations/system_log/
[timer docs]: /integrations/timer/
[vicare docs]: /integrations/vicare/
[xiaomi_ble docs]: /integrations/xiaomi_ble/
[yalexs_ble docs]: /integrations/yalexs_ble/
[zha docs]: /integrations/zha/
## Release 2022.9.4 - September 14
- Update frontend to 20220907.2 ([@bramkragten] - [#78431]) ([frontend docs])
[#78431]: https://github.com/home-assistant/core/pull/78431
[@bramkragten]: https://github.com/bramkragten
[frontend docs]: /integrations/frontend
## Release 2022.9.5 - September 18
- Fix fan speed regression for some xiaomi fans ([@peteh] - [#78406]) ([xiaomi_miio docs])
- Only redact zwave_js values that are worth redacting ([@raman325] - [#78420]) ([zwave_js docs])
- Prevent deleting blueprints which are in use ([@emontnemery] - [#78444]) ([automation docs]) ([script docs]) ([blueprint docs])
- Bump bleak-retry-connector to 0.17.1 ([@bdraco] - [#78474]) ([bluetooth docs])
- Bump python-songpal to 0.15.1 ([@rytilahti] - [#78481]) ([songpal docs])
- Bump PySwitchbot to 0.19.9 ([@bdraco] - [#78504]) ([switchbot docs])
- Bump yalexs_ble to 1.9.2 ([@bdraco] - [#78508]) ([yalexs_ble docs])
- Bump led-ble to 0.10.1 ([@bdraco] - [#78511]) ([led_ble docs])
- Bump aiohomekit to 1.5.8 ([@bdraco] - [#78515]) ([homekit_controller docs])
- Fix zwave_js update entity startup state ([@raman325] - [#78563]) ([zwave_js docs])
- Bump pyrisco to v0.5.5 ([@OnFreund] - [#78566]) ([risco docs])
- Fix WebSocket condition testing ([@frenck] - [#78570]) ([websocket_api docs])
- Fix switchbot not accepting the first advertisement ([@bdraco] - [#78610]) ([switchbot docs])
- Fix reconnect race in HomeKit Controller ([@bdraco] - [#78629]) ([homekit_controller docs])
- Bump qingping-ble to 0.7.0 ([@skgsergio] - [#78630]) ([qingping docs])
- Add a helpful message to the config_entries.OperationNotAllowed exception ([@bdraco] - [#78631])
- Update demetriek to 0.2.4 ([@frenck] - [#78646]) ([lametric docs])
- Handle multiple files properly in zwave_js update entity ([@raman325] - [#78658]) ([zwave_js docs])
- Remove mDNS iteration from Plugwise unique ID ([@frenck] - [#78680]) ([plugwise docs])
- Fix bluetooth callback matchers when only matching on connectable ([@bdraco] - [#78687]) ([bluetooth docs])
- Bump thermobeacon-ble to 0.3.2 ([@bdraco] - [#78693]) ([thermobeacon docs])
[#77968]: https://github.com/home-assistant/core/pull/77968
[#78081]: https://github.com/home-assistant/core/pull/78081
[#78169]: https://github.com/home-assistant/core/pull/78169
[#78406]: https://github.com/home-assistant/core/pull/78406
[#78410]: https://github.com/home-assistant/core/pull/78410
[#78420]: https://github.com/home-assistant/core/pull/78420
[#78438]: https://github.com/home-assistant/core/pull/78438
[#78444]: https://github.com/home-assistant/core/pull/78444
[#78474]: https://github.com/home-assistant/core/pull/78474
[#78481]: https://github.com/home-assistant/core/pull/78481
[#78504]: https://github.com/home-assistant/core/pull/78504
[#78508]: https://github.com/home-assistant/core/pull/78508
[#78511]: https://github.com/home-assistant/core/pull/78511
[#78515]: https://github.com/home-assistant/core/pull/78515
[#78563]: https://github.com/home-assistant/core/pull/78563
[#78566]: https://github.com/home-assistant/core/pull/78566
[#78570]: https://github.com/home-assistant/core/pull/78570
[#78610]: https://github.com/home-assistant/core/pull/78610
[#78629]: https://github.com/home-assistant/core/pull/78629
[#78630]: https://github.com/home-assistant/core/pull/78630
[#78631]: https://github.com/home-assistant/core/pull/78631
[#78646]: https://github.com/home-assistant/core/pull/78646
[#78658]: https://github.com/home-assistant/core/pull/78658
[#78680]: https://github.com/home-assistant/core/pull/78680
[#78687]: https://github.com/home-assistant/core/pull/78687
[#78693]: https://github.com/home-assistant/core/pull/78693
[@OnFreund]: https://github.com/OnFreund
[@balloob]: https://github.com/balloob
[@bdraco]: https://github.com/bdraco
[@emontnemery]: https://github.com/emontnemery
[@frenck]: https://github.com/frenck
[@peteh]: https://github.com/peteh
[@raman325]: https://github.com/raman325
[@rytilahti]: https://github.com/rytilahti
[@skgsergio]: https://github.com/skgsergio
[abode docs]: /integrations/abode/
[accuweather docs]: /integrations/accuweather/
[acmeda docs]: /integrations/acmeda/
[automation docs]: /integrations/automation/
[blueprint docs]: /integrations/blueprint/
[bluetooth docs]: /integrations/bluetooth/
[frontend docs]: /integrations/frontend/
[homekit_controller docs]: /integrations/homekit_controller/
[lametric docs]: /integrations/lametric/
[led_ble docs]: /integrations/led_ble/
[plugwise docs]: /integrations/plugwise/
[qingping docs]: /integrations/qingping/
[risco docs]: /integrations/risco/
[script docs]: /integrations/script/
[songpal docs]: /integrations/songpal/
[switchbot docs]: /integrations/switchbot/
[thermobeacon docs]: /integrations/thermobeacon/
[websocket_api docs]: /integrations/websocket_api/
[xiaomi_miio docs]: /integrations/xiaomi_miio/
[yalexs_ble docs]: /integrations/yalexs_ble/
[zwave_js docs]: /integrations/zwave_js/
## Need help? Join the community
Home Assistant has a great community of users who are all more than willing

2
source/_redirects
View File

@ -411,6 +411,7 @@
# Removed integrations
/integrations/alarmdotcom /more-info/removed-integration 301
/integrations/ambee /more-info/removed-integration 301
/integrations/apns /more-info/removed-integration 301
/integrations/arlo /more-info/removed-integration 301
/integrations/arduino /more-info/removed-integration 301
@ -502,6 +503,7 @@
/integrations/uber /more-info/removed-integration 301
/integrations/updater /more-info/removed-integration 301
/integrations/ups /more-info/removed-integration 301
/integrations/uscis /more-info/removed-integration 301
/integrations/usps /more-info/removed-integration 301
/integrations/weblink /more-info/removed-integration 301
/integrations/wink /more-info/removed-integration 301

3099
source/developers/credits.markdown
View File

File diff suppressed because it is too large Load Diff

24
source/more-info/unsupported/cgroup_version.markdown Normal file
View File

@ -0,0 +1,24 @@
---
title: "CGroup Version"
description: "More information on why CGroup version marks the installation as unsupported."
---
## The issue
Supervisor depends on a particular version of Docker CGroup to be in use since
it depends on its features to work properly.
Currently Supervisor requires CGroup v1 in a supervised installation.
However, the feature set changes and improves over time and therefore, the minimal
required version may change in the future. When that happens, it will be communicated
before we publish a version that will require you to upgrade CGroups.
## The solution
In a supervised installation if you have switched to CGroup v2 you will need to
revert what you did. Or you can re-run the [supervised installer](https://github.com/home-assistant/supervised-installer)
to fix it.
You should never see this issue on Home Assistant OS as all versions of the OS
ship with a supported CGroup version.

17
source/more-info/unsupported/connectivity_check.markdown Normal file
View File

@ -0,0 +1,17 @@
---
title: "Connectivity check"
description: "More information on why disabling Network Manager's connectivity check marks the installation as unsupported."
---
## The issue
Home Assistant needs to know when it has a stable network connection in order to disable functionality which requires that.
Without this check you will face an increased number of errors and performance issues due to connection timeouts.
## The solution
From the host shell execute the following command to re-enable Network Manager's connectivity check:
```sh
busctl set-property org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager ConnectivityCheckEnabled b true
```

2
source/more-info/unsupported/docker_version.markdown
View File

@ -8,7 +8,7 @@ description: "More information on why Docker version marks the installation as u
The version that is needed by the Supervisor, depends on the features it needs
for it to work properly.
The current minimum supported version of Docker is: `19.03.0`.
The current minimum supported version of Docker is: `20.10.17`.
However, the feature set changes and improves over time and therefore, the minimal
required version may change in the future. When that happens, it will be communicated