Merge branch 'current' into next

.github/workflows/test.yml

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

_config.yml

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

plugins/my.rb

@@ -80,7 +80,6 @@ module Jekyll
       DEFAULT_ICONS = {
         "config_flow_start" => "icon-plus-sign",
         "config" => "icon-cog",
-        "integrations" => "icon-puzzle-piece",
       }
 
       # Default title used for in-line text
@@ -103,6 +102,7 @@ module Jekyll
         "info" => "Information",
         "supervisor_info" => "Supervisor Information",
         "supervisor_backups" => "Backups",
+        "integrations" => "Devices & Services",
       }
 
       def parse_options(input, context)

source/_docs/authentication/providers.markdown

@@ -123,7 +123,9 @@ Specially, you can use `group: GROUP_ID` to assign all users in certain `user gr
 
 #### Skip Login Page Examples
 
-This is a feature to allow you bring back some of the experience before the user system was implemented. You can directly jump to main page if you are accessing from trusted networks, the `allow_bypass_login` is on, and you have ONLY ONE available user to choose in the login form.
+This is a feature to allow you to bring back some of the experience before the user system was implemented. You can directly jump to the main page if you are accessing from trusted networks, the `allow_bypass_login` is on, and you have ONLY ONE available user to choose from in the login form. 
+
+If you allow bypass login then your cookie will not be stored and every time you refresh the page in Home Assistant a new login will be created. This is because bypassing the login does not give you the option to save the login.
 
 ```yaml
 # assuming you have only one non-system user

source/_docs/automation/templating.markdown

@@ -29,7 +29,7 @@ The following describes trigger data associated with all platforms.
 | Template variable                    | Data                                                                                                                            |
 | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
 | `trigger.platform`                   | Hardcoded: `calendar`                                                                                                           |
-| `trigger.event_type`                 | The trigger event type, either `start`  or `end`                                                                                |
+| `trigger.event`                      | The trigger event type, either `start`  or `end`                                                                                |
 | `trigger.calendar_event`             | The calendar event object matched.                                                                                              |
 | `trigger.calendar_event.summary`     | The title or summary of the calendar event.                                                                                     |
 | `trigger.calendar_event.start`       | String representation of the start date or date time of the calendar event e.g. `2022-04-10`, or `2022-04-10 11:30:00-07:00`    |

source/_docs/scripts.markdown

@@ -154,7 +154,7 @@ The `condition` action only stops executing the current sequence block. When it
       below: 20
 ```
 
-## Delay
+## Wait for time to pass (delay)
 
 Delays are useful for temporarily suspending your script and start it at a later moment. We support different syntaxes for a delay as shown below.
 
@@ -204,7 +204,7 @@ All forms accept templates.
 
 These actions allow a script to wait for entities in the system to be in a certain state as specified by a template, or some event to happen as expressed by one or more triggers.
 
-### Wait Template
+### Wait for a template
 
 This action evaluates the template, and if true, the script will continue. If not, then it will wait until it is true.
 
@@ -220,7 +220,7 @@ The template is re-evaluated whenever an entity ID that it references changes st
 
 {% endraw %}
 
-### Wait for Trigger
+### Wait for a trigger
 
 This action can use the same triggers that are available in an automation's `trigger` section. See [Automation Trigger](/docs/automation/trigger). The script will continue whenever any of the triggers fires. All previously defined [trigger variables](/docs/automation/trigger#trigger-variables), [variables](#variables) and [script variables] are passed to the trigger.
 {% raw %}
@@ -461,7 +461,7 @@ repeat:
     - language: English
       message: Hello World
     - language: Dutch
-      hello: Hallo Wereld
+      message: Hallo Wereld
   sequence:
     - service: notify.phone
       data:

source/_includes/asides/component_navigation.html

@@ -14,7 +14,7 @@
   </div>
 
   <div class='section'>
-    The {{ page.name | default: page.title }} integration was introduced in Home Assistant {{ page.ha_release | default: "unknown" }},
+    The {{ page.name | default: page.title }} {{ page.ha_integration_type | default: "integration" }} was introduced in Home Assistant {{ page.ha_release | default: "unknown" }},
     and it's used by <a title="Open analytics.home-assistant.io" href="https://analytics.home-assistant.io/#integrations" target="_blank" rel="noopener">
     
     {% if percentage < 1 %}

source/_includes/asides/docs_navigation.html

@@ -56,11 +56,11 @@
         <b>Advanced Configuration</b>
         <ul>
           <li>{% active_link /docs/configuration/remote/ Remote access %}</li>
-          <li>{% active_link /docs/configuration/packages/ Packages %}</li>
           <li>
             {% active_link /docs/configuration/splitting_configuration/
             Splitting up the configuration %}
           </li>
+          <li>{% active_link /docs/configuration/packages/ Packages %}</li>
           <li>
             {% active_link /docs/configuration/secrets/ Storing Secrets %}
           </li>

source/_includes/common-tasks/beta_version.md

@@ -10,7 +10,7 @@ If you would like to test next release before anyone else, you can install the b
   content: |
 
    1. In your Home Assistant UI navigate to {% my updates title="System > Updates" %}
-   2. Click the operflow menu in the top right corner
+   2. Click the overflow menu in the top right corner
    3. Click "Join beta"
    4. Navigate to Configuration panel
    5. Install the update that is presented to you

source/_includes/installation/container.md

@@ -129,7 +129,7 @@ As jemalloc can cause issues on certain hardware, it can be disabled by passing
       homeassistant:
       ...
       environment:
-        DISABLE_JEMALLOC: true
+        - DISABLE_JEMALLOC: true
     ```
 
 {% endtabbed_block %}

source/_includes/integrations/config_flow.md

@@ -24,9 +24,15 @@ manually:
 
 - Browse to your Home Assistant instance.
 - In the sidebar click on _**{% my config icon %}**_.
-- From the configuration menu select: _**{% my integrations icon %}**_.
+- From the configuration menu select: _**{% my integrations %}**_.
+{% if page.ha_integration_type == 'helper' %}
+- In top of the screen click the tab: _**{% my helpers %}**_.
+- In the bottom right, click on the
+  _**{% my config_flow_start icon domain=page.ha_domain title="Create helper" %}**_ button.
+{% else %}
 - In the bottom right, click on the
   _**{% my config_flow_start icon domain=page.ha_domain %}**_ button.
+{% endif %}
 - From the list, search and select _**"{{ name }}"**_.
 - Follow the instruction on screen to complete the set up.
 

source/_includes/integrations/option_flow.md

@@ -6,6 +6,6 @@ Options for {{ name }} can be set via the user interface, by taking the followin
 
 - Browse to your Home Assistant instance.
 - In the sidebar click on _**{% my config icon %}**_.
-- From the configuration menu select: _**{% my integrations icon %}**_.
+- From the configuration menu select: _**{% my integrations %}**_.
 - If multiple instances of {{ name }} are configured, choose the instance you want to configure.
 - Click on _**"Options"**_.

source/_integrations/ambee.markdown

@@ -27,12 +27,10 @@ themselves.
 
 ## Prerequisites
 
-To use the Ambee integration, you will need to obtain an API key from Ambee
-
-Ambee provides free API keys, that are limited to 100 requests a day. This
-is enough for a single Ambee integration instance. If
-you are in need for more, Ambee offers paid options to raise the limits on
-your API key as well.
+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

source/_integrations/analytics.markdown

@@ -21,7 +21,7 @@ Home Assistant allows users to share their usage data via the analytics integrat
 
 The information sent depends on what options you opt-in to. You can opt-in during onboarding and by going to **{% my analytics title="Settings > System > Analytics" %}** .
 
-{% my general badge %}
+{% my analytics badge %}
 
 When enabled, data will be sent 15 minutes after each start, and every 24h after startup. Sent data is printed to your log.
 

source/_integrations/daikin.markdown

@@ -150,3 +150,5 @@ Currently known region codes:
 - JP
 - US
 - TH
+
+If you experience problems with certain apps like the Daikin ONECTA try setting a lower-case region code (e.g. 'eu').

source/_integrations/forecast_solar.markdown

@@ -120,8 +120,8 @@ results less optimistic and more tuned to your reality.
 The **inverter** size can be used in a situation where the maximum power of your
 inverter is lower than the total power of all your solar panels (as entered under
 "total modules power") together. As a result, the forecast takes into account that
-the maximum solar power cannot exceed what your inverter can handle and you would
-therefore get a more realistic graph of your forecast.
+the maximum solar power cannot exceed what your inverter can handle, giving you
+a more realistic forecast graph.
 
 [Read more about the damping factor in the Forecast.Solar documentation](https://doc.forecast.solar/doku.php?id=damping&s[]=damping).
 
@@ -130,6 +130,6 @@ instance:
 
 - Browse to your Home Assistant instance.
 - In the sidebar click on _**{% my config icon %}**_.
-- From the configuration menu select: _**{% my integrations icon %}**_.
+- From the configuration menu select: _**{% my integrations %}**_.
 - If multiple instances of {{ name }} are configured, choose the instance you want to configure.
 - Click on _**"Configure"**_.

source/_integrations/hikvision.markdown

@@ -56,6 +56,7 @@ and has been confirmed to work with the following models:
 
 - DS-2CD2032-I
 - DS-2CD2042WD-I
+- DS-2CD2043G0-I
 - DS-2CD2142FWD-I
 - DS-2CD2155FWD-IS
 - DS-2CD2232-I5

source/_integrations/history_stats.markdown

@@ -90,7 +90,7 @@ Depending on the sensor type you choose, the `history_stats` integration can sho
 
 - **time**: The default value, which is the tracked time, in hours
 - **ratio**: The tracked time divided by the length of your period, as a percentage
-- **count**: How many times the integration you track was changed to the state you track
+- **count**: How many times the tracked entity matched the configured state during the time period
 
 ## Time periods
 
@@ -107,12 +107,12 @@ The duration variable is used when the time period is fixed. Different syntaxes
 
 ```yaml
 # 6 hours
-duration: 06:00
+duration: "06:00"
 ```
 
 ```yaml
 # 1 minute, 30 seconds
-duration: 00:01:30
+duration: "00:01:30"
 ```
 
 ```yaml

source/_integrations/home_connect.markdown

@@ -31,7 +31,7 @@ The integration will add one Home Assistant device for each connected home appli
 - For hood's functional light a light switch including brightness control will be added.
 - For hood's and dishwasher's ambient light a light switch including brightness and color control will be added.
 
-Note that it depends on the appliance and on API permissions which of the features are supported. A notable limitation is that oven programs cannot be started currently.
+Note that it depends on the appliance and on API permissions which of the features are supported.
 
 ## Prerequisites
 

source/_integrations/nest.markdown

@@ -202,8 +202,8 @@ Once `configuration.yaml` has a valid `nest` entry, you need to add Nest to your
 
 1. Browse to your Home Assistant instance.
 1. In the sidebar click on _**{% my config icon %}**_.
-1. From the configuration menu select: _**{% my integrations icon %}**_.
-1. In the bottom right, click on the
+2. From the configuration menu select: _**{% my integrations %}**_.
+3. In the bottom right, click on the
   _**{% my config_flow_start icon domain=page.ha_domain %}**_ button.
 1. From the list, search and select _**"Nest"**_ and follow the instructions.
 

source/_integrations/nmap_tracker.markdown

@@ -29,6 +29,27 @@ On a Fedora host run `sudo dnf -y install nmap`.
 {% include integrations/config_flow.md %}
 
 An example of how the Nmap scanner can be customized:
+![nmap customization example](/images/integrations/nmap/nmap_customization_example.png)
+
+{% configuration_basic %}
+Network addresses to scan:
+  description: Network range to scan using [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing). In the example above it will scan addresses from `192.168.1.1` to `192.168.1.254`.
+  required: true
+  type: string
+Minimum number of minutes between scans of active devices:
+  description: Frequency of the scans. The lower the number, the quicker it will detect devices connected and disconnected usually at the cost of the devices battery life. The example above will scan every minute.
+  required: true
+  type: integer
+Network addresses to exclude from scanning:
+  description: A comma-separated list of IP addresses not to scan. The above example will skip `192.168.1.50`.
+  required: false
+  type: string
+Raw configurable scan options for Nmap:
+  description: Nmap command line parameters which can be used to configure how Nmap scans the network. For more details see [Nmap reference guide](https://nmap.org/book/man.html).
+  required: false
+  type: string
+  default: -F T4 --min-rate 10 --host-timeout 5s
+{% endconfiguration_basic %}
 
 ### Linux capabilities
 

source/_integrations/number.markdown

@@ -14,6 +14,10 @@ ha_integration_type: integration
 
 Keeps track on `number` entities in your environment, their state, and allows you to control them. This integration allows other integrations to get a value input from user within a range.
 
+Number entities cannot be implemented manually, but can be provided by other
+integrations. If you are looking for a way to create a number entity,
+please take a look at the [Number helper](/integrations/input_number).
+
 ### Services
 
 The Number entities registers the following services:

source/_integrations/pandora.markdown

@@ -13,6 +13,10 @@ ha_integration_type: integration
 
 If you have a Pandora account, you can control it from Home Assistant with this media player.
 
+<div class='note'>
+This integration is only available on Home Assistant Core installation types. Unfortunately, it cannot be used with Home Assistant OS, Supervised or Container.
+</div>
+
 ### Installation of Pianobar
 
 This media player uses the [Pianobar command-line Pandora client](https://github.com/PromyLOPh/pianobar), which you have to install separately. This can be done on a Raspberry Pi 2/3 with Raspbian Jessie as follows . _(Note: Other platforms may have different installation processes)_

source/_integrations/peco.markdown

@@ -24,7 +24,10 @@ This integration is only for PECO customers. To see if your county is supported,
 
 </div>
 
----
+{% include integrations/config_flow.md %}
+
+
+## Available entities
 
 The PECO Outage Counter integration allows you to get the current count of power outages for any county, and the total for the operating region too.
 
@@ -35,5 +38,3 @@ This integration will create 5 entities.
 - A sensor that shows the total amount of customers served in the county.
 - A sensor that shows the percentage of customers with no power.
 - A sensor that shows the alert that appears when you open the online outage map.
-
-{% include integrations/config_flow.md %}

source/_integrations/powerwall.markdown

@@ -32,16 +32,17 @@ There is currently support for the following device types within Home Assistant:
 
 The following binary sensors are added for each Powerwall:
 
-- Grid Service Active
-- Grid Status
-- Powerwall Charging
-- Powerwall Connected to Tesla
-- Powerwall Status
+- Grid Services - On/ Off
+- Grid Status - On/ Off
+- Powerwall Charging - Charging/ Not Charging
+- Powerwall Connected to Tesla - Connected / Not Connected
+- Powerwall Status - On/ Off
 
 ### Sensor
 
 The following sensors are added for each Powerwall:
 
+- Powerwall Backup Reserve - Reserve energy for grid outages in %
 - Powerwall Battery Now - Usage in kW
 - Powerwall Charge - Percent charge remaining in %
 - Powerwall Generator Now - Usage in kW (if applicable)
@@ -49,6 +50,7 @@ The following sensors are added for each Powerwall:
 - Powerwall Solar Now - Solar usage in kW (if applicable)
 - Powerwall Site Now - Site usage in kW
 - Powerwall Backup Reserve - Percentage of battery which will be reserved for a grid outage
+- Frequency/ Average Current/ Average Voltage Now
 
 The following sensors show the direction of energy:
 
@@ -62,3 +64,8 @@ The following sensors show the direction of energy:
 - Powerwall Load Import - Load energy imported in kWh
 - Powerwall Generator Export - Generator energy exported in kWh
 - Powerwall Generator Import - Generator energy imported in kWh
+
+### Device Info
+
+- Model number: PowerWall 2 (GW2) by Tesla
+- Firmware Revision

source/_integrations/script.markdown

@@ -13,6 +13,10 @@ ha_integration_type: integration
 
 The script integration allows users to specify a sequence of actions to be executed by Home Assistant. These are run when you turn the script on. The script integration will create an entity for each script and allow them to be controlled via services.
 
+Scripts can be created via YAML configuration (described below) or via {% my scripts title="the UI" %}.
+
+{% my scripts badge %}
+
 ## Configuration
 
 The sequence of actions is specified using the [Home Assistant Script Syntax](/getting-started/scripts/).

source/_integrations/sensibo.markdown

@@ -92,13 +92,13 @@ switch:
           target:
             entity_id: climate.ac
           data:
-            hvac_mode: cool
+            hvac_mode: "cool"
         turn_off:
           service: climate.set_hvac_mode
           target:
             entity_id: climate.ac
           data:
-            hvac_mode: off
+            hvac_mode: "off"
 ```
 
 {% endraw %}

source/_integrations/sensor.markdown

@@ -43,7 +43,7 @@ The type of data a sensor returns impacts how it is displayed in the frontend. T
 - **pm25**: Concentration of particulate matter less than 2.5 micrometers in µg/m³
 - **power_factor**: Power factor in %
 - **power**: Power in W or kW
-- **pressure**: Pressure in hPa or mbar
+- **pressure**: Pressure in Pa, kPa, hPa, bar, cbar, mbar, mmHg, inHg or psi
 - **reactive_power**: Reactive power in var
 - **signal_strength**: Signal strength in dB or dBm
 - **sulphur_dioxide**: Concentration of sulphur dioxide in µg/m³

source/_integrations/seventeentrack.markdown

@@ -52,6 +52,33 @@ show_delivered:
   default: false
 {% endconfiguration %}
 
+## Package statuses
+
+[17track's API](https://api.17track.net/en/doc) provides the following tracking statuses. The integration creates a sensor for each status, which contains the packages in that status. The sensor's displayed value is the number of packages in that status.
+
+- Not found
+- In transit
+- Expired
+- Pick up
+- Undelivered
+- Delivered
+- Alert
+
+## Package-level attributes
+
+Each package entry (for example, within a status sensor) contains the following attributes.
+
+- package.friendly_name
+- package.status
+- package.destination_country
+- package.info_text
+- package.timestamp
+- package.location
+- package.origin_country
+- package.package_type
+- package.tracking_info_language
+- package.tracking_number
+
 ## Examples
 
 ### Dashboard summary card

source/_integrations/template.markdown

@@ -385,13 +385,13 @@ You can use a trigger-based template entity to convert any event or other automa
 
 ```yaml
 template:
-  trigger:
-    platform: event
-    event_type: my_event
-  binary_sensor:
-    - name: Event recently fired
-      auto_off: 5
-      state: "true"
+  - trigger:
+      platform: event
+      event_type: my_event
+    binary_sensor:
+      - name: Event recently fired
+        auto_off: 5
+        state: "true"
 ```
 
 ### Sun Angle

source/_integrations/unifiprotect.markdown

@@ -5,6 +5,7 @@ ha_category:
   - Binary Sensor
   - Button
   - Camera
+  - Doorbell
   - Hub
   - Light
   - Lock

source/_integrations/viaggiatreno.markdown

@@ -16,8 +16,8 @@ The `viaggiatreno` sensor will give you information about configured train ids a
 To activate the sensor you need at least two parameters: the `train_id` and the `station_id`.
 
 The first is available just looking at the [ViaggiaTreno](http://viaggiatreno.it/) timetable, the latter can be obtained using the dedicated API endpoint:
-`http://www.viaggiatreno.it/viaggiatrenonew/resteasy/viaggiatreno/autocompletaStazione/<Station name>`
-(e.g., `http://www.viaggiatreno.it/viaggiatrenonew/resteasy/viaggiatreno/autocompletaStazione/ROMA` will list all station names (with ids) that starts with *ROMA*).
+`http://www.viaggiatreno.it/infomobilita/resteasy/viaggiatreno/autocompletaStazione/<Station name>`
+(e.g., `http://www.viaggiatreno.it/infomobilita/resteasy/viaggiatreno/autocompletaStazione/ROMA` will list all station names (with ids) that starts with *ROMA*).
 
 <div class='note'>
 

source/_integrations/yeelight.markdown

@@ -180,7 +180,9 @@ This integration is tested to work with the following models. If you have a diff
 | `color1`   | YLDP03YL     | LED Bulb (Color) - E26                           |
 | `color2`   | YLDP06YL     | LED Bulb (Color) - 2nd generation                |
 | `color4`   | YLDP13YL     | LED Bulb 1S (Color)                              |
+| `color4`   | YLDP04YL     | LED Bulb 1S (Color)                              |
 | `color6`   | YLDP13AYL    | LED Bulb 1S (Color)                              |
+| `colorb`   | YLDP005      | LED Bulb (Color)                                 |
 | `colorc`   | YLDP004-A    | GU10 W1 (Color)                                  |
 | `strip1`   | YLDD01YL     | Lightstrip (Color)                               |
 | `strip1`   | YLDD02YL     | Lightstrip (Color)                               |

source/_integrations/zha.markdown

@@ -461,7 +461,7 @@ Using a Philips Hue Dimmer Switch or Lutron Connected Bulb Remote is probably th
 3. Press and hold the (I)/(ON) and (O)/(OFF) buttons on the Philips Hue Dimmer Switch. The bulb should start blinking in 10-20 seconds. The bulb will blink, then turn off, then turn on. You can now release the dimmer buttons.
 4. Your bulb is now factor resey and ready for pairing. A green light on the top left of the dimmer remote indicates that your bulb has been successfully reset to factory default settings.
 
-Note: If you are not unable to reset the bulb, remove it from the Hue Bridge and retry the procedure.
+Note: If you are unable to reset the bulb, remove it from the Hue Bridge and retry the procedure.
 
 #### Lutron Connected Bulb Remote
 

source/_posts/2022-05-04-release-20225.markdown

@@ -65,6 +65,7 @@ Enjoy the release!
 - [Release 2022.5.2 - May 6](#release-202252---may-6)
 - [Release 2022.5.3 - May 8](#release-202253---may-8)
 - [Release 2022.5.4 - May 12](#release-202254---may-12)
+- [Release 2022.5.5 - May 18](#release-202255---may-18)
 - [Need help? Join the community!](#need-help-join-the-community)
 - [Breaking Changes](#breaking-changes)
 - [Farewell to the following](#farewell-to-the-following)
@@ -886,6 +887,59 @@ The following integrations are now available via the Home Assistant UI:
 [unifiprotect docs]: /integrations/unifiprotect/
 [zwave_js docs]: /integrations/zwave_js/
 
+## Release 2022.5.5 - May 18
+
+- Refresh camera stream source of Synology DSM connected cameras ([@mib1185] - [#70938])
+- Warn user if "model" key is missing from Shelly firmware ([@chemelli74] - [#71612]) ([shelly docs])
+- Remove LIFX bulb discovery from the inflight list if it fails to connect ([@Djelibeybi] - [#71673]) ([lifx docs])
+- Limit parallel requests in fibaro light ([@rappenze] - [#71762]) ([fibaro docs])
+- Fix VeSync air_quality fan attribute ([@jetpacktuxedo] - [#71771]) ([vesync docs])
+- Fix handling package detection for latest UniFi Protect beta ([@AngellusMortis] - [#71821]) ([unifiprotect docs])
+- Add missing Shelly Cover sensors bugfix ([@RadekHvizdos] - [#71831]) ([shelly docs])
+- Revert changing `pysnmp` to `pysnmplib` ([@bieniu] - [#71901]) ([snmp docs]) ([brother docs])
+- Suppress Upnp error in SamsungTV resubscribe ([@epenet] - [#71925]) ([samsungtv docs])
+- Properly handle Shelly gen2 device disconnect ([@chemelli74] - [#71937]) ([shelly docs])
+- Include initial state in history_stats count ([@bdraco] - [#71952]) ([history_stats docs])
+- Fix filesize doing IO in event loop ([@thecode] - [#72038]) ([filesize docs])
+- Ignore UpnpXmlContentError in SamsungTV ([@epenet] - [#72056]) ([samsungtv docs])
+- Cleanup unused import in SamsungTV ([@epenet] - [#72102]) ([samsungtv docs])
+
+[#70938]: https://github.com/home-assistant/core/pull/70938
+[#71612]: https://github.com/home-assistant/core/pull/71612
+[#71673]: https://github.com/home-assistant/core/pull/71673
+[#71762]: https://github.com/home-assistant/core/pull/71762
+[#71771]: https://github.com/home-assistant/core/pull/71771
+[#71821]: https://github.com/home-assistant/core/pull/71821
+[#71831]: https://github.com/home-assistant/core/pull/71831
+[#71901]: https://github.com/home-assistant/core/pull/71901
+[#71925]: https://github.com/home-assistant/core/pull/71925
+[#71937]: https://github.com/home-assistant/core/pull/71937
+[#71952]: https://github.com/home-assistant/core/pull/71952
+[#72038]: https://github.com/home-assistant/core/pull/72038
+[#72056]: https://github.com/home-assistant/core/pull/72056
+[#72102]: https://github.com/home-assistant/core/pull/72102
+[@AngellusMortis]: https://github.com/AngellusMortis
+[@Djelibeybi]: https://github.com/Djelibeybi
+[@RadekHvizdos]: https://github.com/RadekHvizdos
+[@bdraco]: https://github.com/bdraco
+[@bieniu]: https://github.com/bieniu
+[@chemelli74]: https://github.com/chemelli74
+[@epenet]: https://github.com/epenet
+[@jetpacktuxedo]: https://github.com/jetpacktuxedo
+[@mib1185]: https://github.com/mib1185
+[@rappenze]: https://github.com/rappenze
+[@thecode]: https://github.com/thecode
+[brother docs]: /integrations/brother/
+[fibaro docs]: /integrations/fibaro/
+[filesize docs]: /integrations/filesize/
+[history_stats docs]: /integrations/history_stats/
+[lifx docs]: /integrations/lifx/
+[samsungtv docs]: /integrations/samsungtv/
+[shelly docs]: /integrations/shelly/
+[snmp docs]: /integrations/snmp/
+[unifiprotect docs]: /integrations/unifiprotect/
+[vesync docs]: /integrations/vesync/
+
 ## Need help? Join the community!
 
 Home Assistant has a great community of users who are all more than willing

source/_posts/2022-05-16-home-assistant-os-release-8.markdown

@@ -0,0 +1,123 @@
+---
+layout: post
+title: "Home Assistant OS Release 8"
+description: "Now using GRUB2 for UEFI-based systems, Home Assistant Yellow support, and support for UEFI-based AArch64 systems!"
+date: 2022-05-16 00:00:00
+date_formatted: "May 16, 2022"
+author: Stefan Agner
+author_twitter: falstaff_ch
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2022-05-16-os8/social.png
+---
+
+<a href='https://github.com/home-assistant/operating-system/releases/tag/8.0'>
+<img title='Home Assistant OS Release 8' alt='Home Assistant OS Release 8 Logo'
+     src='/images/blog/2022-05-16-os8/social.png' style='border: 0;box-shadow: none;'>
+</a>
+
+Home Assistant OS 8.0 stable is available now!
+
+**Highlights**:
+
+- Use of GRUB2 for UEFI based systems
+- Support for additional Wi-Fi and Bluetooth devices
+- New image: Generic AArch64 for UEFI based AArch64 VMs and boards
+- New image: Home Assistant Yellow
+
+For existing installations, no manual intervention is needed! You can safely
+update without reading these rather technical release notes.
+
+## Table of contents
+
+- [Table of contents](#table-of-contents)
+- [Operating System Changes](#operating-system-changes)
+  - [GRUB2 for UEFI based systems](#grub2-for-uefi-based-systems)
+  - [Under the Hood](#under-the-hood)
+  - [Other Changes](#other-changes)
+- [Device Support](#device-support)
+  - [Raspberry Pi](#raspberry-pi)
+  - [Home Assistant Yellow](#home-assistant-yellow)
+  - [Generic x86-64](#generic-x86-64)
+  - [Generic AArch64 support](#generic-aarch64-support)
+
+## Operating System Changes
+
+### GRUB2 for UEFI based systems
+
+For Generic x86-64, OVA and the new Generic AArch64 Home Assistant uses GRUB2
+as boot loader now. GRUB2 (GRand Unified Bootloader) is the de-facto standard
+boot loader used by most Linux distributions. The main reason for switching from
+Barebox to GRUB2 was the missing AArch64 UEFI boot support in Barebox. We also
+expect GRUB2 to be more stable especially on Desktop style x86-64 systems as
+it gets used by much more users since generic Linux distributions use GRUB2.
+Although, we actually hit a bug in GRUB2 during the RC phase, let's hope
+this was a one-off. 🤞
+
+<img src='/images/blog/2022-05-16-os8/haos-grub2-menu.png' alt='Screenshot showing GRUB2 menu of Home Assistant OS'>
+
+The boot menu shows the two boot slots. Typically you don't have to change
+selection here, unless you intentionally want to boot the previously installed
+Home Assistant OS version.
+
+Note: Upgrading from any version 7.x is safe, but we recommend upgrading from
+the last version of the previous major release. This is also the best tested
+upgrade path. From any release with GRUB2 it is only safe to downgrade to 7.6!
+Downgrading to releases before 7.6 can be done by downgrading to 7.6 first.
+
+### Under the Hood
+
+Under the hood, the OS was updated to the latest upstream Linux 5.15 kernel
+as well as Buildroot 2022.02.1. The latest Buildroot release brings new
+versions of various core components like systemd 250, NetworkManager 1.34.0
+and Docker 20.10.14.
+
+Additional networking drivers and settings prepare Home Assistant OS to
+host the [OpenThread Border Router add-on].
+
+### Other Changes
+
+- IP set support for advanced firewalling (also used by the OTBR add-on).
+- Support for NTP configuration via DHCP.
+- Google Coral support is now using Google's latest driver. This enables
+  additional Coral device support such as PCI Dual Edge TPU.
+- Legacy wext backend for wpa_suppilcant is now enabled to support more Wi-Fi
+  devices.
+
+## Device Support
+
+### Raspberry Pi
+
+All Raspberry Pi versions use the latest LTS Linux Kernel 5.15 and firmware
+(tag 1.20220331) from the Raspberry Pi team. These are the same versions as
+the Raspberry Pi OS is using currently.
+
+### Home Assistant Yellow
+
+This is the first release that supports Home Assistant Yellow. Since Home
+Assistant Yellow uses the Raspberry Pi Compute Module 4, the support is
+based on the regular Raspberry Pi support currently. The Yellow image is
+using the same kernel and firmware version. The Yellow board also supports
+booting directly off of an NVMe device for those using a CM4 Lite (without
+eMMC storage).
+
+### Generic x86-64
+
+Besides the move to GRUB2 Generic x86-64 received quite some additional device
+support. The Wi-Fi devices 3945ABG/BG/4965AGN and 22000 series are now supported.
+
+Other Changes:
+
+- Support 32-bit UEFI boot. This is required by older Intel Atom systems. Note
+  that only the boot loader is 32-bit, everything else uses the same 64-bit
+  binaries as 64-bit UEFI boot.
+- Driver and firmware for Broadcom BNX2/BNX2X network interfaces are included.
+
+### Generic AArch64 support
+
+[@Doridian] contributed support for generic AArch64 systems which use the UEFI
+boot flow. It should support real boards as well as virtual machines. So far
+it has been successfully tested on KVM Virtual Machines.
+
+[@Doridian]: https://github.com/Doridian
+[OpenThread Border Router add-on]: https://github.com/home-assistant/addons-development/tree/master/openthread_border_router