Merge branch 'current' into next

_config.yml

@@ -107,8 +107,8 @@ social:
 # Home Assistant release details
 current_major_version: 2022
 current_minor_version: 8
-current_patch_version: 5
-date_released: 2022-08-15
+current_patch_version: 6
+date_released: 2022-08-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.

source/_data/glossary.yml

@@ -61,7 +61,7 @@
 - topic: Sensor
   description: "[Sensors](/integrations/sensor) return information about a thing, for instance the level of water in a tank."
 - topic: Selectors
-  description: "[Selectors](/docs/blueprint/selectors/) specify what values are accepted for a blueprint input and how the input is shown in the user interface."
+  description: "[Selectors](/docs/blueprint/selectors/) are components for the user interface. Some selectors can, for example, show a toggle button to turn something on or off, while another select can filter a list of devices to show only devices that have motion-sensing capabilities."
 - topic: Service
   description: "[Services](/docs/scripts/service-calls/) are called to perform actions."
 - topic: Switch
@@ -73,6 +73,6 @@
 - topic: TTS
   description: "TTS ([text to speech](/integrations/tts)) allows Home Assistant to talk to you."
 - topic: Variables
-  description: "[Variables](/docs/scripts/#variables) are a named storage for a value that can be processed e.g. in a script."
+  description: "[Variables](/docs/scripts/#variables) are used to store values in memory that can be processed e.g. in a script."
 - topic: Zone
   description: "[Zones](/integrations/zone/) are areas that can be used for presence detection."

source/_docs/configuration.markdown

@@ -13,12 +13,12 @@ The easiest option to edit `configuration.yaml` is to use the {% my supervisor_a
 
 If you prefer to use a file editor on your computer, use the {% my supervisor_addon title="Samba add-on" addon="core_samba" %} to access the files as a network share.
 
-The path to your configuration directory can be found in the Home Assistant frontend by going to {% my system_health title="Settings > System > System Health" %}
+The path to your configuration directory can be found in the Home Assistant frontend by going to {% my system_health title="Settings > System > Repairs > System information from the top right menu" %}
 
-<p class='img'>
-  <img src='/images/screenshots/system_health_config_dir.png' alt='Screenshot showing the top of the system health panel'>
-  Right under the version you are running, you will find what path Home Assistant has loaded the configuration from.
-</div>
+![Show system menu option](/images/screenshots/System_information_menu.png)
+
+Right under the version you are running, you will find what path Home Assistant has loaded the configuration from.
+![Screenshot showing the top of the system information panel](/images/screenshots/System_information.png)
 
 _If you use Home Assistant Container, you can find `configuration.yaml` in the config folder that you mounted in your container._
 

source/_includes/installation/operating_system.md

@@ -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:

source/_integrations/bluetooth_le_tracker.markdown

@@ -17,7 +17,7 @@ Devices discovered are stored with 'BLE_' as the prefix for device mac addresses
 
 ## Setup
 
-This platform requires pybluez to be installed, which is already the case if you're using Home Assistant OS, Supervised or Container. For Home Assistant Core installs see below on the required steps.
+This integration requires the [Bluetooth](/integrations/bluetooth) integration to be enabled and functional.
 
 ## Configuration
 
@@ -58,30 +58,3 @@ Some BTLE devices (e.g., fitness trackers) are only visible to the devices that
 Enabling the battery tracking might slightly decrease the duration of the battery, but since this is only done at most once a day, this shouldn't be noticeable. Not all devices offer battery status information; if the information is not available, the integration will only try once at startup.
 
 For additional configuration variables check the [Device tracker page](/integrations/device_tracker/).
-
-{% details "Notes for Home Assistant Core Installations" %}
-
-On Debian based Home Assistant Core installations, run:
-
-```bash
-sudo apt install bluetooth
-```
-
-Before you get started with this platform, please note that:
-
-- This platform is incompatible with Windows
-- This platform requires access to the Bluetooth stack, see [Rootless Setup section](#rootless-setup) for further information
-
-### Rootless Setup on Core installs
-
-Normally accessing the Bluetooth stack is reserved for root, but running programs that are networked as root is a bad security wise. To allow non-root access to the Bluetooth stack we can give Python 3 and hcitool the missing capabilities to access the Bluetooth stack. Quite like setting the setuid bit (see [Stack Exchange](https://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root) for more information).
-
-```bash
-sudo apt-get install libcap2-bin
-sudo setcap 'cap_net_raw,cap_net_admin+eip' $(readlink -f $(which python3))
-sudo setcap 'cap_net_raw+ep' $(readlink -f $(which hcitool))
-```
-
-A restart of Home Assistant is required.
-
-{% enddetails %}

source/_integrations/ffmpeg.markdown

@@ -10,14 +10,13 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `ffmpeg` integration allows other Home Assistant integrations to process video and audio streams. This integration supports all FFmpeg versions since 3.0.0; if you have an older version, please update.
+The FFmpeg integration allows other Home Assistant integrations to process
+video and audio streams.
 
-<div class='note'>
-
-If you are running Home Assistant Core in a Python environment, you'll need have the `ffmpeg` binary in your system path.
-On Debian 8 or Raspbian (Jessie) you can install it from [debian-backports](https://backports.debian.org/Instructions/). If you want [hardware acceleration](https://trac.ffmpeg.org/wiki/HWAccelIntro) support on a Raspberry Pi, you will need to build from source by yourself.
-
-</div>
+This integration supports all FFmpeg versions since 3.0.0. If you run
+the Home Assistant Operating System or use the Home Assistant Container,
+this is already pre-installed for you. In all other cases, make sure
+you have FFmpeg installed on your system.
 
 ## Configuration
 
@@ -35,27 +34,14 @@ ffmpeg_bin:
   type: string
 {% endconfiguration %}
 
-### Raspbian Debian Jessie Lite Installations
-To get the binary on Raspbian Debian Jessie Lite on a Raspberry Pi you need to perform the following:
-
-```bash
-sudo echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list
-sudo apt-get update
-sudo apt-get -t jessie-backports install ffmpeg
-```
-
-We can use now following in the configuration:
-
-```yaml
-ffmpeg:
-  ffmpeg_bin: /usr/bin/ffmpeg
-```
-
 ### Troubleshooting
 
-In most cases, `ffmpeg` automatically detects all needed options to read a video or audio stream or file. But it is possible in rare cases that you will need to set options to help `ffmpeg` out.
+In most cases, `ffmpeg` automatically detects all needed options to read
+a video or audio stream or file. But it is possible in rare cases that you
+will need to set options to help `ffmpeg` out.
 
-First, check that your stream is playable by `ffmpeg` outside of Home Assistant with (use option `-an` or `-vn` to disable video or audio stream):
+First, check that your stream is playable by `ffmpeg` outside of Home Assistant
+with (use option `-an` or `-vn` to disable video or audio stream):
 
 ```bash
 ffmpeg -i INPUT -an -f null -

source/_integrations/filter.markdown

@@ -78,16 +78,16 @@ filters:
       description: Algorithm to be used to filter data. Available filters are  `lowpass`, `outlier`, `range`, `throttle`, `time_throttle` and `time_simple_moving_average`.
       required: true
       type: string
+    precision:
+      description: Defines the precision of the filtered state, through the argument of round().
+      required: false
+      type: integer
+      default: 2
     window_size:
       description: Size of the window of previous states. Time based filters such as `time_simple_moving_average` will require a time period (size in time), while other filters such as `outlier` will require an integer (size in number of states). Time periods are in _hh:mm_ format and must be quoted.
       required: false
       type: [integer, time]
       default: 1
-    precision:
-      description: See [_lowpass_](#low-pass) filter. Defines the precision of the filtered state, through the argument of round().
-      required: false
-      type: integer
-      default: None
     time_constant:
       description: See [_lowpass_](#low-pass) filter. Loosely relates to the amount of time it takes for a state to influence the output.
       required: false
@@ -129,8 +129,6 @@ A = 1.0 - B
 LowPass(state) = A * previous_state + B * state
 ```
 
-The returned value is rounded to the number of decimals defined in (`precision`).
-
 ### Outlier
 
 The Outlier filter (`outlier`) is a basic Band-pass filter, as it cuts out any value outside a specific range.

source/_integrations/generic_thermostat.markdown

@@ -60,7 +60,7 @@ ac_mode:
   type: boolean
   default: false
 min_cycle_duration:
-  description: Set a minimum amount of time that the switch specified in the *heater* option must be in its current state prior to being switched either off or on.
+  description: Set a minimum amount of time that the switch specified in the *heater* option must be in its current state prior to being switched either off or on. This option will be ignored if the `keep_alive` option is set.
   required: false
   type: [time, integer]
 cold_tolerance:
@@ -74,7 +74,7 @@ hot_tolerance:
   default: 0.3
   type: float
 keep_alive:
-  description: Set a keep-alive interval. If set, the switch specified in the *heater* option will be triggered every time the interval elapses. Use with heaters and A/C units that shut off if they don't receive a signal from their remote for a while. Use also with switches that might lose state. The keep-alive call is done with the current valid climate integration state (either on or off).
+  description: Set a keep-alive interval. If set, the switch specified in the *heater* option will be triggered every time the interval elapses. Use with heaters and A/C units that shut off if they don't receive a signal from their remote for a while. Use also with switches that might lose state. The keep-alive call is done with the current valid climate integration state (either on or off). When `keep_alive` is set the `min_cycle_duration` option will be ignored.
   required: false
   type: [time, integer]
 initial_hvac_mode:

source/_integrations/homematicip_cloud.markdown

@@ -27,7 +27,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The [HomematicIP](https://www.homematic-ip.com/) integration platform is used as an interface to the cloud server. Since there is no official documentation about this API, everything was done via reverse engineering. The [homematicip-rest-api](https://github.com/coreGreenberet/homematicip-rest-api) is used for communicating. Use at your own risk.
+The [HomematicIP](https://www.homematic-ip.com/) integration platform is used as an interface to the cloud server. Since there is no official documentation about this API, everything was done via reverse engineering. Use at your own risk.
 
 There is currently support for the following device types within Home Assistant:
 

source/_integrations/motion_blinds.markdown

@@ -35,6 +35,7 @@ Additionally the following brands have been reported to also work with this inte
 - [Martec](https://www.martec.co.nz/)
 - [Motion Blinds](https://motionblinds.com/)
 - [Raven Rock MFG](https://www.ravenrockmfg.com/)
+- [ScreenAway](https://www.screenaway.com.au/)
 - [Smart Blinds](https://www.smartblinds.nl/)
 - [Smart Home](https://www.smart-home.hu)
 - [Uprise Smart Shades](http://uprisesmartshades.com)

source/_integrations/statistics.markdown

@@ -62,7 +62,7 @@ The following characteristics are supported for `sensor` source sensors:
 | `total` | The sum of all source sensor measurements within the given time and sampling size limits.
 | `value_max` | The biggest value among the number of measurements.
 | `value_min` | The smallest value among the number of measurements.
-| `variance` | The [variance](https://en.wikipedia.org/wiki/Standard_deviation) of an assumed normal distribution from all measurements.
+| `variance` | The [variance](https://en.wikipedia.org/wiki/Variance) of an assumed normal distribution from all measurements.
 
 ### Binary Source Sensor
 

source/_integrations/uk_transport.markdown

@@ -11,11 +11,11 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `uk_transport` sensor will display the time in minutes until the next departure in a specified direction from of a configured train station or bus stop. The sensor uses [transportAPI](https://www.transportapi.com/) to query live departure data and requires a developer application ID and key which can be obtained [here](https://developer.transportapi.com/). The [free tier](https://www.transportapi.com/benefits/) allows 30,000 requests a month, which is sufficient for a single sensor refreshing every 87 seconds.
+The `uk_transport` sensor will display the time in minutes until the next departure in a specified direction from of a configured train station or bus stop. The sensor uses [transportAPI](https://www.transportapi.com/) to query live departure data and requires a developer application ID and key which can be obtained [here](https://developer.transportapi.com/). The [free tier]([https://www.transportapi.com/benefits/](https://www.transportapi.com/blog/2022/08/introducing-the-home-use-plan-for-transportapi/)) allows 30 requests a day, which is sufficient for a single sensor refreshing every 48 minutes.
 
 <div class='note warning'>
 
-Additional sensors can be added but at the expense of a reduced refresh rate. 2 sensors can be updated every 2*87 = 174 seconds, and so on. Calculating and setting this rate is automatically handles by the integration.
+Additional sensors can be added but at the expense of a reduced refresh rate. 2 sensors can be updated every 2*48 = 96 minutes, and so on. Calculating and setting this rate is automatically handles by the integration.
 
 </div>
 

source/_posts/2022-08-03-release-20228.markdown

@@ -48,6 +48,7 @@ Enjoy the release!
 - [Release 2022.8.3 - August 9](#release-202283---august-9)
 - [Release 2022.8.4 - August 12](#release-202284---august-12)
 - [Release 2022.8.5 - August 15](#release-202285---august-15)
+- [Release 2022.8.6 - August 17](#release-202286---august-17)
 - [Need help? Join the community!](#need-help-join-the-community)
 - [Breaking Changes](#breaking-changes)
 - [Farewell to the following](#farewell-to-the-following)
@@ -570,6 +571,41 @@ The following integrations are now available via the Home Assistant UI:
 [switchbot docs]: /integrations/switchbot/
 [system_bridge docs]: /integrations/system_bridge/
 
+## Release 2022.8.6 - August 17
+
+- Fix displayed units for BMW Connected Drive ([@rikroe] - [#76613]) ([bmw_connected_drive docs])
+- Fix Overkiz startup order to prevent unnamed device showing up ([@iMicknl] - [#76695]) ([overkiz docs])
+- Bump pynetgear to 0.10.7 ([@starkillerOG] - [#76754]) ([netgear docs])
+- Correct restoring of mobile_app sensors ([@emontnemery] - [#76886]) ([mobile_app docs])
+- Fix acmeda set cover tilt position ([@epenet] - [#76927]) ([acmeda docs])
+- Fix race in notify setup ([@bdraco] - [#76954]) ([notify docs])
+- Pass the real config for Discord ([@tkdrob] - [#76959]) ([discord docs])
+- Pass the real config for Slack ([@tkdrob] - [#76960]) ([slack docs])
+
+[#76613]: https://github.com/home-assistant/core/pull/76613
+[#76695]: https://github.com/home-assistant/core/pull/76695
+[#76754]: https://github.com/home-assistant/core/pull/76754
+[#76886]: https://github.com/home-assistant/core/pull/76886
+[#76927]: https://github.com/home-assistant/core/pull/76927
+[#76954]: https://github.com/home-assistant/core/pull/76954
+[#76959]: https://github.com/home-assistant/core/pull/76959
+[#76960]: https://github.com/home-assistant/core/pull/76960
+[@bdraco]: https://github.com/bdraco
+[@emontnemery]: https://github.com/emontnemery
+[@epenet]: https://github.com/epenet
+[@iMicknl]: https://github.com/iMicknl
+[@rikroe]: https://github.com/rikroe
+[@starkillerOG]: https://github.com/starkillerOG
+[@tkdrob]: https://github.com/tkdrob
+[acmeda docs]: /integrations/acmeda/
+[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
+[discord docs]: /integrations/discord/
+[mobile_app docs]: /integrations/mobile_app/
+[netgear docs]: /integrations/netgear/
+[notify docs]: /integrations/notify/
+[overkiz docs]: /integrations/overkiz/
+[slack docs]: /integrations/slack/
+
 ## Need help? Join the community!
 
 Home Assistant has a great community of users who are all more than willing

source/getting-started/configuration.markdown

@@ -41,8 +41,8 @@ Now let's make a change using the file editor: we are going to change the name,
 </div>
 
  - Click the save icon in the top right to commit changes.
- - Most changes in `configuration.yaml` require Home Assistant to be restarted to see the changes. You can verify that your changes are acceptable by running a configuration check. Do this by clicking on Configuration in the sidebar, click on `Developer-Tools -> YAML` and click on the **Check configuration** button. When it's valid, it will show the text "Configuration valid!". In order for the **Check Configuration**" button to be visible, you must enable "Advanced Mode" on your user profile.
- - Now Restart Home Assistant using the **Restart** button in the Server management section on the same page.
+ - Most changes in `configuration.yaml` require Home Assistant to be restarted to see the changes. You can verify that your changes are acceptable by running a configuration check. Do this by navigating to {% my server_controls title="Developer Tools -> YAML" %} and and then clicking on the **Check configuration** button. When it's valid, it will show the text "Configuration valid!". In order for the **Check Configuration**" button to be visible, you must enable "Advanced Mode" on your user profile.
+ - Now Restart Home Assistant. You can do so by either using the **Restart** option in the ⚙ menu of the File Editor UI or by navigating to {% my system_dashboard title="Settings -> System" %} and then clicking on the **Restart** button on the top right of the page.
 
 ![Screenshot of the "General" page in the configuration panel.](/images/screenshots/configuration-validation.png)