Merge branch 'current' into next

Gemfile.lock

@@ -24,7 +24,7 @@ GEM
       http_parser.rb (~> 0)
     eventmachine (1.2.7)
     eventmachine (1.2.7-x64-mingw32)
-    ffi (1.16.2)
+    ffi (1.16.3)
     forwardable-extended (2.6.0)
     google-protobuf (3.24.4)
     http_parser.rb (0.8.0)

_config.yml

@@ -110,8 +110,8 @@ social:
 # Home Assistant release details
 current_major_version: 2023
 current_minor_version: 10
-current_patch_version: 0
-date_released: 2023-10-04
+current_patch_version: 1
+date_released: 2023-10-06
 
 # 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/_dashboards/conditional.markdown

@@ -9,7 +9,7 @@ The Conditional card displays another card based on entity states.
 
 Note: Conditions with more than one entity are treated as an 'and' condition. This means that for the card to show, *all* entities must meet the state requirements set.
 
-To add the Conditional card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the **Add Card** button in the bottom right corner and select from the card picker.
+To add the Conditional card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the **Add Card** button in the bottom right corner and select from the card picker. Note that while editing the dashboard, the card will always be shown, so be sure to exit editing mode to test the conditions.
 
 All options for this card can be configured via the user interface.
 

source/_docs/blueprint/tutorial.markdown

@@ -177,15 +177,17 @@ blueprint:
       description: This sensor will be synchronized with the light.
       selector:
         entity:
-          domain: binary_sensor
-          device_class: motion
+          filter:
+            - domain: binary_sensor
+            - device_class: motion
     target_light:
       name: Lights
       description: The lights to keep in sync.
       selector:
         target:
           entity:
-            domain: light
+            filter:
+              - domain: light
 ```
 
 By limiting our blueprint to working with lights and motion sensors, we unlock a couple of benefits: the UI will be able to limit suggested values to lights and motion sensors instead of all devices. It will also allow the user to pick an area to control the lights in.
@@ -207,15 +209,17 @@ blueprint:
       description: This sensor will be synchronized with the light.
       selector:
         entity:
-          domain: binary_sensor
-          device_class: motion
+          filter:
+            - domain: binary_sensor
+            - device_class: motion
     target_light:
       name: Lights
       description: The lights to keep in sync.
       selector:
         target:
           entity:
-            domain: light
+            filter:
+              - domain: light
 
 trigger:
   - platform: state
@@ -282,4 +286,4 @@ If you follow the [Rules and format for posting](/get-blueprints), you can share
 - [Blueprint selectors](/docs/blueprint/selectors/)
 - [Blueprint schema](/docs/blueprint/schema/)
 - [About blueprints](/docs/blueprint/)
-- [Using automation blueprints](/docs/automation/using_blueprints/)
+- [Using automation blueprints](/docs/automation/using_blueprints/)

source/_docs/configuration/remote.markdown

@@ -3,11 +3,7 @@ title: "Remote access"
 description: "Setting up remote access for Home Assistant."
 ---
 
-<div class='note'>
-Users of <a href="https://www.nabucasa.com">Home Assistant Cloud</a> can use the <a href="https://www.nabucasa.com/config/remote/">Remote UI</a> without requiring any configuration.
-</div>
-
-If you're interested in logging in to Home Assistant while away, you'll have to make your instance remotely accessible.
+If you're interested in logging in to Home Assistant while away, you'll have to make your instance remotely accessible. Below are a few options to do this.
 
 <div class='note warning'>
 
@@ -15,7 +11,21 @@ Remember to follow the [securing checklist](/docs/configuration/securing/) befor
 
 </div>
 
-The most common approach is to set up port forwarding (for any port) from your router to port 8123 on the computer that is hosting Home Assistant. General instructions on how to do this can be found by searching `<router model> port forwarding instructions`. You can use any free port on your router and forward that to port 8123.
+## Home Assistant Cloud
+
+Users of <a href="https://www.nabucasa.com">Home Assistant Cloud</a> can use the <a href="https://www.nabucasa.com/config/remote/">Remote UI</a> without requiring any configuration.
+
+A unique remote URL will be generated and given to you along with a certificate so all your traffic to Home Assistant is encrypted automatically.
+
+## VPN
+
+A secure way to remotely access your Home Assistant is to use a Virtual Private Network (VPN) service such as [Tailscale](https://tailscale.com/) or [ZeroTier One](https://www.zerotier.com/).
+
+A VPN connection needs to be established before you can connect to your Home Assistant from outside your local network. The VPN makes this connection secure. When using the Home Assistant Companion app (such as on a mobile device), without this connection, your sensors will not update in Home Assistant.
+
+## Port Forwarding
+
+Set up port forwarding (for any port) from your router to port 8123 on the computer that is hosting Home Assistant. General instructions on how to do this can be found by searching `<router model> port forwarding instructions`. You can use any free port on your router and forward that to port 8123.
 
 A problem with making a port accessible is that some Internet Service Providers only offer dynamic IPs. This can cause you to lose access to Home Assistant while away. You can solve this by using a free Dynamic DNS service like [DuckDNS](https://www.duckdns.org/).
 

source/_docs/energy.markdown

@@ -21,22 +21,3 @@ Home Assistant is an open platform and so home energy management is not restrict
 If you have a sensor that returns instantaneous power readings (W or kW), then to add a sensor that returns energy usage or generation (kWh) refer to [Riemann sum integral integration](/integrations/integration/#energy)
 
 <img src='/images/docs/energy/energy-overview.png' alt='Visual representation of how all different energy forms relate.' style='border: 0;box-shadow: none;'>
-
-## Troubleshooting missing entities 
-
-### Condition
-
-You are trying to add a sensor to the energy dashboard, but it does not appear in the selection list. 
-
-### Resolution
-
-To find out why the sensor is not showing, check the following points:
-- The sensor must have the appropriate attributes. Check your entity attributes in {% my developer_states title="**Developer Tools** > **States**" %} to confirm the following:
-  - `device_class` must be `energy` for electricity grid, solar, or battery categories. It must be `gas` for gas, or `water` for water.
-  - `state_class` must be `total` or `total_increasing`.
-  - The sensor must have an appropriate `unit_of_measurement`. See the help text for each category to see which units are accepted. Units containing an exponent must match superscript characters exactly as defined, e.g. `m³` is accepted, `m3` is not.
-  
-  If any of the attributes are not correct, please open an issue against the integration that provides your sensor, or if you are developing custom template sensors, make sure the templates have the correct settings.
- 
-- The entity must be a `sensor`. If you are trying to add something from another domain (for example an `input_number`), then you must first create a template sensor from it.
-- The entity must not have any statistics errors. Go to {% my developer_statistics title="**Developer Tools** > **Statistics**" %} to check your specific entity. If your unit has a listed issue here, you must fix the issue before it can be added to the dashboard.

source/_docs/energy/faq.markdown

@@ -32,3 +32,22 @@ To accomplish such, you can use [the utility_meter integration](/integrations/ut
 ## The Energy panel is not visible
 
 If you do not see the Energy panel in the sidebar, make sure you have not removed [`default_config:`](/integrations/default_config/) from your `configuration.yaml`. If you have, you will need to add the `energy:` integration manually.
+
+## Troubleshooting missing entities 
+
+### Condition
+
+You are trying to add a sensor to the energy dashboard, but it does not appear in the selection list. 
+
+### Resolution
+
+To find out why the sensor is not showing, check the following points:
+- The sensor must have the appropriate attributes. Check your entity attributes in {% my developer_states title="**Developer Tools** > **States**" %} to confirm the following:
+  - `device_class` must be `energy` for electricity grid, solar, or battery categories. It must be `gas` for gas, or `water` for water.
+  - `state_class` must be `total` or `total_increasing`.
+  - The sensor must have an appropriate `unit_of_measurement`. See the help text for each category to see which units are accepted. Units containing an exponent must match superscript characters exactly as defined, e.g. `m³` is accepted, `m3` is not.
+  
+  If any of the attributes are not correct, please open an issue against the integration that provides your sensor, or if you are developing custom template sensors, make sure the templates have the correct settings.
+ 
+- The entity must be a `sensor`. If you are trying to add something from another domain (for example an `input_number`), then you must first create a template sensor from it.
+- The entity must not have any statistics errors. Go to {% my developer_statistics title="**Developer Tools** > **Statistics**" %} to check your specific entity. If your unit has a listed issue here, you must fix the issue before it can be added to the dashboard.

source/_docs/locked_out.md

@@ -64,13 +64,19 @@ If you are running Home Assistant in a container, you can use the command line i
 
 #### Start a new onboarding process
 
-If you lose the password associated with the owner account and the steps above do not work to reset the password, the only way to resolve this is to delete *all* the authentication data. You do this by shutting down Home Assistant and deleting the following files from the `.storage/` folder in your [configuration folder](/docs/configuration/):
+If you lose the password associated with the owner account and the steps above do not work to reset the password, the only way to resolve this is to start a new onboarding process. If you have an external backup with an administrator account of which you still know the login credentials, you can restore that backup. If you do not have a backup, resetting the device will erase all data.
 
-- `auth`
-- `auth_provider.homeassistant`
-- `onboarding`
-- `hassio`
-- `cloud`
+- If you have a Home Assistant Green, [reset the Green](https://green.home-assistant.io/guides/reset/).
+- If you have a Home Assistant Yellow, [reset the Yellow](https://yellow.home-assistant.io/guides/factory-reset/).
+- If you have a Raspberry Pi, delete *all* the authentication data.
+  - Shut down Home Assistant.
+  - Remove your SD card and access it from your PC.
+  - Delete the following files from the `.storage/` folder in your [configuration folder](/docs/configuration/):
+    - `auth`
+    - `auth_provider.homeassistant`
+    - `onboarding`
+    - `hassio`
+    - `cloud`
 
 ## Recovering Data for Home Assistant (including Supervised)
 

source/_includes/asides/component_navigation.html

@@ -3,11 +3,7 @@
 {% assign percentage = 100.0 | times: active_installations | divided_by: site.data.analytics_data.reports_integrations | round: 1 %}
 <section class="aside-module grid__item one-whole lap-one-half">
   <div class='brand-logo-container section'>
-    {%- if page.logo -%}
-      <img src='/images/supported_brands/{{ page.logo }}' />
-    {%- else -%}
       <img src='https://brands.home-assistant.io/{% if page.ha_brand %}brands{% else %}_{% endif %}/{{ domain }}/logo.png' srcset='https://brands.home-assistant.io/{% if page.ha_brand %}brands{% else %}_{% endif %}/{{ page.ha_domain }}/logo@2x.png 2x' />
-    {%- endif -%}
 
     {%- if page.ha_config_flow and domain -%}
       {% my config_flow_start badge domain=domain %}

source/_integrations/alexa.markdown

@@ -30,7 +30,7 @@ There are a few ways that you can use Amazon Alexa and Home Assistant together.
   - Support for viewing and controlling devices with the Alexa mobile app.
 - [Create a Custom Alexa Skill to build custom commands](/integrations/alexa.intent/)
 - [Create a new Flash Briefing source](/integrations/alexa.flash_briefings/)
-- Alternative: use the [Emulated Hue integration](/integrations/emulated-hue) to trick Alexa into thinking Home Assistant is a Philips Hue hub.
+- Alternative: use the [Emulated Hue integration](/integrations/emulated_hue) to trick Alexa into thinking Home Assistant is a Philips Hue hub.
 
 ### Requirements
 

source/_integrations/blebox.markdown

@@ -28,71 +28,554 @@ ha_zeroconf: true
 
 For the best experience, make sure your BleBox devices have the most recent available firmware installed.
 
-Additionally, if you are configuring a gateBox, it may be useful to set the second button as "stop" in your device's settings (via website or phone app).
 
-## Covers
+## BleBox controllers
 
-This integration adds the BleBox device as a cover in Home Assistant.
+### rollerGate
 
-Currently, this includes support for the following product classes:
+This integration adds the Blebox device as a cover entity to Home Assistant.
 
-- BleBox shutterBox
-- BleBox rollerGate
-- BleBox gateBox
+#### Key supported features
 
-Set of features includes tilt support for shutterBox.
+- Open
+- Close
+- Position
+- Stop
 
-## Binary sensors
-This integration adds BleBox device as a binary_sensor in Home Assistant.
+### gateBox
 
-Currently, this includes support for the following product classes:
+This integration adds the Blebox device as a cover entity to Home Assistant.
 
-- BleBox rainSensor
-- BleBox wind&rainSensor 
+#### Key supported features
 
-## Sensors
+- Open (trigger primary output)
+- Close (trigger primary output)
+- Stop (trigger secondary output)
+- Gate state (open, close, unknown)
 
-This integration adds the BleBox device as a sensor in Home Assistant.
+#### Additional features
 
-Currently, this includes support for the following product classes and their features:
+- "stop" requires setting your device's secondary trigger as stop (via website or phone app).
 
-- BleBox tempSensor (temperature only)
-- Blebox humiditySensor
-- BleBox airSensor
+### gateBox Pro
 
-## Switches
+This integration adds the Blebox device as a cover entity to Home Assistant.
 
-This integration adds the BleBox device as a switch (or multiple switches) in Home Assistant.
+#### Key supported features
 
-Currently, this includes support for the following product classes:
+- Open (trigger primary output)
+- Close (trigger primary output)
+- Stop (trigger secondary output)
+- Gate state (open, close, unknown)
 
-- BleBox switchBox
-- BleBox switchBoxD
+#### Additional features
 
-## Climate
+- "stop" requires setting your device's secondary trigger as stop (via website or phone app).
 
-This integration adds the BleBox device as a climate in Home Assistant.
+### doorBox
 
-Currently, this includes support for the following product classes:
+This integration adds the Blebox device as a cover entity to Home Assistant.
 
-- BleBox saunaBox
-- BleBox thermoBox
+#### Key supported features
 
+- Open
+- Door state (open, close, unknown)
 
-## Lights
+### saunaBox
 
-This integration adds the BleBox device as a light in Home Assistant.
+This integration adds the Blebox device as a climate entity to Home Assistant.
 
-Currently, the following product classes are supported:
+#### Key supported features
 
-- BleBox dimmerBox
-- BleBox wLightBoxS
-- BleBox wLightBox
+- On
+- Off
+- Setting target temperature
+- Read current temperature
 
-## Button
+### thermoBox
 
-This integration adds the BleBox device as a button in Home Assistant
+This integration adds the Blebox device as a climate entity to Home Assistant.
 
-Currently, this includes support for the following product classes:
+#### Key supported features
 
-- BleBox tvLiftBox
+- On
+- Off
+- Set target temperature
+- Read current temperature
+
+#### Additional features
+
+- Changing operation mode (cooling/heating) requires direct access to device or from wBox app
+
+### shutterBox
+
+This integration adds the Blebox device as a cover entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Close
+- Position
+- Tilt regulation
+
+### shutterBoxDC
+
+This integration adds the Blebox device as a cover entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Close
+- Position
+- Tilt regulation
+
+### shutterBox DIN
+
+This integration adds the Blebox device as a cover entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Close
+- Position
+- Tilt regulation
+
+### switchBox
+
+This integration adds the Blebox device as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Energy consumption measurement
+
+### switchBox DIN
+
+This integration adds the Blebox device as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Energy consumption measurement
+
+### switchBoxD
+
+This integration adds the Blebox device as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Energy consumption measurement
+
+### switchBoxD DIN
+
+This integration adds the Blebox device as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Energy consumption measurement
+
+### switchBoxDC
+
+This integration adds the Blebox device as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+
+### switchBox LIGHT
+
+This integration adds the Blebox device as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+
+### switchBoxT PRO
+
+This integration adds the Blebox device as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+
+### dimmerBox
+
+This integration adds the Blebox device as a light entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Brightness
+
+### wLightBox
+
+This integration adds the Blebox device as a light entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+- Color
+
+#### Additional features
+
+- Changing color mode available from direct device access or wBox app. Device needs to be reloaded from Home Assistant.
+
+### wLightBox PRO
+
+This integration adds the Blebox device as a light entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+- Color
+
+#### Additional features
+
+- Changing color mode available from direct device access or wBox app. Device needs to be reloaded from Home Assistant.
+
+### wLightBoxS
+
+This integration adds the Blebox device as a light entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+
+### wLightBoxS PRO
+
+This integration adds the Blebox device as a light entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+
+### pixelBox
+
+This integration adds the Blebox device as a light entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+- Color
+
+### tempSensor
+
+This integration adds the Blebox device as a sensor entity to Home Assistant.
+
+#### Key supported features
+
+- Periodic read of temperature
+
+### tempSensorAC
+
+This integration adds the Blebox device as a sensor entity to Home Assistant.
+
+#### Key supported features
+
+- Periodic read of temperature for all probes
+
+### tempSensor PRO
+
+This integration adds the Blebox device as a sensor entity to Home Assistant.
+
+#### Key supported features
+
+- Periodic read of temperature for all probes
+
+### humiditySensor
+
+This integration adds the Blebox device as a sensor entity to Home Assistant.
+
+#### Key supported features
+
+- Periodic read of humidity
+- Periodic read of temperature
+
+### wind&RainSensor
+
+This integration adds the Blebox device as a sensor & binary sensor entity to Home Assistant.
+
+#### Key supported features
+
+- Periodic read of current wind speed
+- Periodic read of state of rain detection
+
+### rainSensor
+
+This integration adds the Blebox device as a binary sensor entity to Home Assistant.
+
+#### Key supported features
+
+- Periodic read of state of rain detection
+
+### airSensor
+
+This integration adds the Blebox device as a sensor entity to Home Assistant.
+
+#### Key supported features
+
+- Periodic read of:
+  - pm1
+  - pm2.5
+  - pm10
+
+### windSensor PRO
+
+This integration adds the Blebox device as a sensor entity to Home Assistant.
+
+#### Key supported features
+
+- Periodic read of current wind speed
+
+------
+
+## "BleBox inside" controllers
+
+### Simon 54 GO SHUTTER
+
+This integration adds the Simon 54 GO device ("blebox inside")  as a cover entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Close
+- Position
+- Tilt regulation
+
+### Simon 54 GO SWITCH
+
+This integration adds the Simon 54 GO device ("blebox inside") as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+
+### Simon 54 GO SWITCH D
+
+This integration adds the Simon 54 GO device ("blebox inside") as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+
+### Simon 54 GO LED 230V (dimmer)
+
+This integration adds the Simon 54 GO device ("blebox inside") as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Brightness
+
+### Simon 54 GO LED MONO
+
+This integration adds the Simon 54 GO device ("blebox inside") as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+- Color
+
+### Simon 54 GO RGBW
+
+This integration adds the Simon 54 GO device ("blebox inside") as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+- Color
+
+### Simon 55 GO SHUTTER
+
+This integration adds the Simon 55 GO device ("blebox inside") as a cover entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Close
+- Position
+- Tilt regulation
+
+### Simon 55 GO SWITCH
+
+This integration adds the Simon 55 GO device ("blebox inside") as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+
+### Simon 55 GO SWITCH D
+
+This integration adds the Simon 55 GO device ("blebox inside") as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Brightness
+
+### Simon 55 GO LED 230V (dimmer)
+
+This integration adds the Simon 55 GO device ("blebox inside") as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Brightness
+
+### Simon 55 GO LED MONO
+
+This integration adds the Simon 55 GO device ("blebox inside") as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+- Color
+
+### Simon 55 GO RGBW
+
+This integration adds the Simon 55 GO device ("blebox inside") as a switch entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+- Color
+
+### FAKRO FTP-V/FTU-V WiFi
+
+This integration adds the Fakro device ("blebox inside") as a cover entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Close
+- Position
+
+### FAKRO ARF/ARP WiFi
+
+This integration adds the Fakro device ("blebox inside") as a cover entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Close
+- Position
+
+### FAKRO ARZ/AMZ/VMZ WiFi
+
+This integration adds the Fakro device ("blebox inside") as a cover entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Close
+- Position
+
+### SABAJ TV K-SMRT-4 - WIFI RJ-45
+
+This integration adds the SABAJ device ("blebox inside") as a button entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Close
+- Up
+- Down
+- Fav
+
+### Wiśniowski RiCo
+
+This integration adds the Wiśniowski device ("blebox inside") as a cover entity to Home Assistant.
+
+- Open (trigger primary output)
+- Close (trigger primary output)
+- Stop (trigger secondary output)
+- Gate state (open, close, unknown) - only Pro version
+
+#### Additional features
+
+- "stop" requires setting your device's secondary trigger as stop (via website or phone app)
+
+### Polfendo smartGateControl
+
+This integration adds the Polfendo device ("blebox inside") as a cover entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Close
+- Position
+- Stop
+
+### Plast-met SMART LIGHT BOSSPIO
+
+This integration adds the Plast-met device ("blebox inside") as a light entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+
+### Plast-met SMART LIGHT SIMPIO
+
+This integration adds the Plast-met device ("blebox inside") as a light entity to Home Assistant.
+
+#### Key supported features
+
+- On
+- Off
+- Effects
+- Brightness
+
+### Tedee relay module
+
+This integration adds the Tedee device ("blebox inside") as a cover entity to Home Assistant.
+
+#### Key supported features
+
+- Open
+- Door state (open, close, unknown)

source/_integrations/daikin.markdown

@@ -45,7 +45,8 @@ There is currently support for the following device types within Home Assistant:
 <div class='note'>
 
 - The integration for BRP072Cxx and SKYFi based units need API-key / password respectively. The API-key/password can be found on a sticker under the front cover. The other models are auto detected and the API-key and password field must be left empty.
-  
+- BRP084Cxx firmware update from 1.19.0 to 2.8.0 breaks local API there is however ongoing work in fixing local API support again.
+
 </div>
 
 {% include integrations/config_flow.md %}

source/_integrations/fully_kiosk.markdown

@@ -104,7 +104,6 @@ Example:
 ```yaml
 service: fully_kiosk.set_config
 data:
-  config_type: "string"
   key: "startURL"
   value: "https://home-assistant.io"
 target:

source/_integrations/gogogate2.markdown

@@ -1,7 +1,6 @@
 ---
 title: Gogogate2 and ismartgate
 description: Instructions on how to integrate Gogogate2 and iSmartGate enabled garage door covers into Home Assistant.
-logo: gogogate2.png
 ha_category:
   - Cover
 ha_release: 0.67

source/_integrations/humidifier.markdown

@@ -14,6 +14,8 @@ ha_integration_type: entity
 
 The `humidifier` integration is built for the controlling and monitoring of humidifiers, dehumidifiers, and hygrostat devices.
 
+{% include integrations/building_block_integration.md %}
+
 ## Services
 
 ### Humidifier services

source/_integrations/idasen_desk.markdown

@@ -17,6 +17,14 @@ ha_codeowners:
 
 The IKEA IDÅSEN integration allows you to connect your IKEA Idåsen motorized desk to Home Assistant, making it possible to control the desk height and also monitor height changes from the physical controller.
 
+<div class='note warning'>
+
+The recommended way to connect the desk to Home Assistant is by using an [ESPHome Bluetooth Proxy](https://esphome.io/projects/?type=bluetooth), as they provide the best experience.
+  
+If you are not using an ESPHome Bluetooth Proxy, you need to keep `bluetoothctl` (or any other Bluetooth Agent) open during the integration setup, or it will fail to authenticate with the desk. The connection process is also less reliable than with ESPHome, so you may need to retry a few times until it succeeds. This is due to a limitation in the third-party Bluetooth implementation used by Home Assistant.
+
+</div>
+
 {% include integrations/config_flow.md %}
 
 Home Assistant will display a list of addresses of the available desks, and you just need to select the one you want to add. Repeat the process to add more than one desk.

source/_integrations/image.markdown

@@ -12,3 +12,5 @@ ha_integration_type: entity
 ---
 
 The image integration allows other integrations to display a static image.
+
+{% include integrations/building_block_integration.md %}

source/_integrations/image_processing.markdown

@@ -13,6 +13,8 @@ ha_integration_type: entity
 
 Image processing enables Home Assistant to process images from [cameras](/integrations/#camera). Only camera entities are supported as sources.
 
+{% include integrations/building_block_integration.md %}
+
 ## ALPR
 
 ALPR entities have a vehicle counter attribute `vehicles` and all found plates are stored in the `plates` attribute.

source/_integrations/lawn_mower.markdown

@@ -13,7 +13,7 @@ ha_integration_type: entity
 
 The lawn mower integration allows the control of robotic lawn mowers to be reflected within Home Assistant.
 
-Please note, the lawn mower integration cannot be directly used; you cannot create your own lawn mower entities using this integration. This integration is a building block for other integrations to use, enabling them to create lawn mower entities for you.
+{% include integrations/building_block_integration.md %}
 
 ## Services
 

source/_integrations/lifx_cloud.markdown

@@ -1,7 +1,6 @@
 ---
 title: LIFX Cloud
 description: Instructions on using native LIFX scenes with Home Assistant.
-logo: lifx.png
 ha_category:
   - Scene
 ha_iot_class: Cloud Push

source/_integrations/light.markdown

@@ -13,6 +13,8 @@ ha_integration_type: entity
 
 This integration allows you to track and control various light bulbs. Read the integration documentation for your particular light hardware to learn how to enable it.
 
+{% include integrations/building_block_integration.md %}
+
 ### Default turn-on values
 
 To set the default color, brightness and transition values when the light is turned on, create a custom `light_profiles.csv`, normally located in the default configuration folder where you find `configuration.yaml`.

source/_integrations/lock.markdown

@@ -16,6 +16,8 @@ Keeps track which locks are in your environment, their state and allows you to c
 - Maintains a state per lock and a combined state `all_locks`.
 - Registers services `lock.lock`, `lock.unlock` and `lock.open` (unlatch) to control locks.
 
+{% include integrations/building_block_integration.md %}
+
 ### Services
 
 A lock integration provides the following services:

source/_integrations/mailbox.markdown

@@ -13,3 +13,5 @@ Mailboxes provide a list of messages with short information about each. Mailbox
 Home Assistant currently supports only the [Asterisk Voicemail](/integrations/asterisk_mbox/) mailbox.
 
 Each mailbox also provides an entity to indicate the number of messages available on the main page.
+
+{% include integrations/building_block_integration.md %}

source/_integrations/medcom_ble.markdown

@@ -24,7 +24,7 @@ This integration supports the Medcom [Inspector BLE](https://medcom.com/product/
 
 {% include integrations/config_flow.md %}
 
-The Medcom Bluetooth integration will automatically discover devices once the [Bluetooth](integrations/bluetooth) integration is enabled and working. It will list each detected Inspector using its Bluetooth MAC address as the serial number.
+The Medcom Bluetooth integration will automatically discover devices once the [Bluetooth](/integrations/bluetooth) integration is enabled and working. It will list each detected Inspector using its Bluetooth MAC address as the serial number.
 
 To limit the load on the Bluetooth radio on the Home Assistant side, the integration only polls for a reading every 5 minutes, which should be adequate for ongoing background monitoring. An Inspector BLE battery should last several months with continuous use before needing replacement.
 
@@ -34,4 +34,4 @@ To limit the load on the Bluetooth radio on the Home Assistant side, the integra
 
 ## Sensors
 
-This integration adds a counts-per-minute ("CPM") sensor for each detected Inspector BLE device. See the Inspector BLE manual for how to convert this CPM reading into another unit if desired, which can be done via a custom [template sensor](integrations/template)
+This integration adds a counts-per-minute ("CPM") sensor for each detected Inspector BLE device. See the Inspector BLE manual for how to convert this CPM reading into another unit if desired, which can be done via a custom [template sensor](/integrations/template)

source/_integrations/media_player.markdown

@@ -13,6 +13,8 @@ ha_integration_type: entity
 
 Interacts with media players on your network.
 
+{% include integrations/building_block_integration.md %}
+
 ## Services
 
 ### Media control services

source/_integrations/modbus.markdown

@@ -22,7 +22,7 @@ ha_integration_type: integration
 
 [modbus](http://www.modbus.org/) is a communication protocol to control PLCs (Programmable Logic Controller) and RTUs (Remote Terminal Unit).
 
-The integration adheres strictly to the [protocol specification](https://www.modbus.org/docs/Modbus_Application_Protocol_V1_1b3.pdf) using [pymodbus](https://github.com/pymodbus-dev/pymodbus) for the actual protocol implmentation.
+The integration adheres strictly to the [protocol specification](https://www.modbus.org/docs/Modbus_Application_Protocol_V1_1b3.pdf) using [pymodbus](https://github.com/pymodbus-dev/pymodbus) for the protocol implementation.
 
 The modbus integration supports all devices adhering to the modbus standard. The communication to the device/devices can be serial (rs-485), TCP, or UDP connections. The modbus integration allows multiple communication channels e.g. a serial port connection combined with one or more TCP connections.
 

source/_integrations/mqtt.markdown

@@ -797,7 +797,7 @@ mqtt:
 - [Event](/integrations/event.mqtt/)
 - [Fan](/integrations/fan.mqtt/)
 - [Humidifier](/integrations/humidifier.mqtt/)
-- [Image](/integrations/imahe.mqtt/)
+- [Image](/integrations/image.mqtt/)
 - [Climate/HVACs](/integrations/climate.mqtt/)
 - [Lawn Mower](/integrations/lawn_mower.mqtt/)
 - [Light](/integrations/light.mqtt/)

source/_integrations/notify.markdown

@@ -15,6 +15,8 @@ The `notify` integration makes it possible to send notifications to a wide varie
 
 If you want to send notifications to the Home Assistant web interface, you may use the [Persistent Notification integration](/integrations/persistent_notification/). The Persistent Notification integration is also available as an automatically configured notifier. See [its documentation](/integrations/persistent_notification/) for more details.
 
+{% include integrations/building_block_integration.md %}
+
 ## Service
 
 Once loaded, the `notify` platform will expose a service that can be called to send notifications.

source/_integrations/number.markdown

@@ -14,9 +14,9 @@ ha_integration_type: entity
 
 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).
+{% include integrations/building_block_integration.md %}
+
+If you are looking for a way to create a number entity, please take a look at the [Number helper](/integrations/input_number).
 
 ## Device Class
 

source/_integrations/nzbget.markdown

@@ -3,7 +3,6 @@ title: NZBGet
 description: Instructions on how to integrate NZBGet within Home Assistant.
 ha_category:
   - Downloading
-logo: nzbget.png
 ha_iot_class: Local Polling
 ha_release: 0.17
 ha_config_flow: true
@@ -76,6 +75,6 @@ Available services:
 
 ### Service `nzbget/set_speed`
 
-| Service data attribute | Optional | Description |
-|------------------------|----------|-------------------------------------------------------------------------------------------------|
-| `speed`                |      yes | Sets the download speed limit, specified in Kb/s. 0 disables the speed limit. Defaults to 1000. |
+| Service data attribute | Optional | Description                                                                                     |
+| ---------------------- | -------- | ----------------------------------------------------------------------------------------------- |
+| `speed`                | yes      | Sets the download speed limit, specified in Kb/s. 0 disables the speed limit. Defaults to 1000. |

source/_integrations/oem.markdown

@@ -11,7 +11,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-This platform supports the ESP8266 based "WiFi MQTT Relay / Thermostat" sold by [OpenEnergyMonitor](https://shop.openenergymonitor.com/wifi-mqtt-relay-thermostat/). The underlying [library](https://oemthermostat.readthedocs.io/) only supports this single relay variant of the [original device](https://harizanov.com/2014/12/wifi-iot-3-channel-relay-board-with-mqtt-and-http-api-using-esp8266/).
+This platform supports the ESP8266 based "WiFi MQTT Relay / Thermostat" sold by [OpenEnergyMonitor](https://web.archive.org/web/20220426080315/https://shop.openenergymonitor.com/wifi-mqtt-relay-thermostat/) (archived page, no longer for sale). The underlying [library](https://oemthermostat.readthedocs.io/) only supports this single relay variant of the [original device](https://harizanov.com/2014/12/wifi-iot-3-channel-relay-board-with-mqtt-and-http-api-using-esp8266/).
 
 This platform controls the setpoint of the thermostat in its "manual" mode.
 

source/_integrations/oralb.markdown

@@ -26,18 +26,18 @@ The integration can discover most Bluetooth-enabled Oral-B toothbrushes. Brushes
 
 ## Supported devices
 
-- [IO 4 Series](https://oralb.com/en-us/products/electric-toothbrushes/oralbio)
-- [IO 6 Series](https://oralb.com/en-us/products/electric-toothbrushes/io-series-6-electric-toothbrush-gray-opal/)
-- [IO 7 Series](https://oralb.com/en-us/products/electric-toothbrushes/oralbio)
-- [IO 8 Series](https://oralb.com/en-us/products/electric-toothbrushes/oralbio)
-- [IO 9 Series](https://oralb.com/en-us/products/electric-toothbrushes/oralbio)
-- Smart Series 4000
-- Smart Series 6000
+- [IO Series 4](https://oralb.com/en-us/products/electric-toothbrushes/io-series-4-rechargeable-electric-toothbrush-blue/)
+- [IO Series 6](https://oralb.com/en-us/products/electric-toothbrushes/io-series-6-electric-toothbrush-gray-opal/)
+- [IO Series 7](https://oralb.com/en-us/products/electric-toothbrushes/io-series-7-electric-toothbrush-sapphire-blue/)
+- [IO Series 8](https://oralb.com/en-us/products/electric-toothbrushes/io-series-8-electric-toothbrush-black-onyx/)
+- [IO Series 9](https://oralb.com/en-us/products/electric-toothbrushes/io-series-9-rechargeable-electric-toothbrush-in-rose-quartz/)
+- [Smart Series 4000](https://www.service.oralb.com/us/en/products/3754/)
+- [Smart Series 6000](https://www.service.oralb.com/us/en/products/3754/)
 - [Smart Series 7000](https://oralb.com/en-us/products/electric-toothbrushes/smart-7000-rechargeable-electric-toothbrush/)
-- Smart Series 8000
-- [Genius Series 9000](https://oralb.com/en-us/products/electric-toothbrushes/genius-9600-rechargeable-electric-toothbrush-white/)
-- Genius Series 10000
-- Triumph V2
+- [Genius Series 8000](https://oralb.com/en-us/products/electric-toothbrushes/genius-8000-rechargeable-electric-toothbrush-pink/)
+- [Genius Series 9000](https://www.service.oralb.com/us/en/products/3765/)
+- [Genius Series 10000](https://www.service.oralb.com/us/en/products/3765/)
+- [Triumph V2](https://www.service.oralb.com/us/en/products/3745/)
 - [Genius X](https://www.service.oralb.com/us/en/products/3771/)
 
 ## Sensor

source/_integrations/point.markdown

@@ -20,7 +20,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Point hub enables integration with the [Minut Point](https://minut.com/). To connect with Point, you will have to [sign up for a developer account and have a Pro subscription](https://minut.com/community/developers/) and get a `client_id` and `client_secret` with the `callback url` configured as your Home Assistant URL + `/api/minut`, e.g.,  `http://localhost:8123/api/minut`. The `client_id` and `client_secret` should be used as below.
+The Point hub enables integration with the [Minut Point](https://minut.com/). To connect with Point, you will have to [sign up for a developer account and have a Pro subscription](https://minut.com/community/developers/) and get a `client_id` and `client_secret` with the `callback url` configured as your Home Assistant URL + `/api/minut`, e.g.,  `http://homeassistant.local:8123/api/minut`. The `client_id` and `client_secret` should be used as below.
 
 Once Home Assistant is started, a configurator will pop up asking you to Authenticate your Point account via a link. When you follow the link and click on **Accept** you will be redirected to the `callback url` and the Point integration will be automatically configured and you can go back to the original dialog and press **Submit**.
 

source/_integrations/python_script.markdown

@@ -128,6 +128,14 @@ The above `python_script` can be called using the following YAML as an input.
     rgb_color: [255, 0, 0]
 ```
 
+Services can also respond with data. Retrieving this data in your Python script can be done by setting the `blocking` and `return_response` arguments of the `hass.services.call` function to `True`. This is shown in the example below, in this case, retrieving the weather forecast and putting it into a variable:
+
+```python
+# get_forecast.py
+service_data = {"type": "daily", "entity_id": "weather.YOUR_HOME"}
+current_forecast = hass.services.call("weather", "get_forecast", service_data, blocking=True, return_response=True)
+```
+
 ## Documenting your Python scripts
 
 You can add names and descriptions for your Python scripts that will be shown in the frontend. To do so, simply create a `services.yaml` file in your `<config>/python_scripts` folder. Using the above Python script as an example, the `services.yaml` file would look like:

source/_integrations/remote.markdown

@@ -16,6 +16,8 @@ Keeps track which remotes are in your environment, their state and allows you to
 - Maintains a state per remote and a combined state `all_remotes`.
 - Registers services `remote/turn_on`, `remote/turn_off`, `remote/toggle`, and `remote/send_command` to control remotes.
 
+{% include integrations/building_block_integration.md %}
+
 ### Use the services
 
 Go to the **Developer Tools**, then to **Call Service** in the frontend, and choose `remote/turn_on`, `remote/turn_off`, or `remote/toggle` from the list of available services (**Available services:** on the left). Enter something like the sample below into the **Service Data** field and hit **Call Service**.

source/_integrations/roku.markdown

@@ -148,49 +148,6 @@ action:
       media_content_type: channel
 ```
 
-## Play on Roku
-
-The `media_player.play_media` service may be used to send media URLs (primarily videos) for direct playback on your device. This feature makes use of the built-in PlayOnRoku application.
-
-| Service data attribute | Optional | Description | Example |
-| ---------------------- | -------- | ----------- | ------- |
-| `entity_id` | no | Target a specific media player. | 
-| `media_content_id` | no | A media URL. | http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4
-| `media_content_type` | no | A media type. | `url`
-| `extra.format` | no | A media format. Should be one of `mp4` (supports mov and m4v), `mp3`, `hls`, `ism` (smooth streaming), `dash` (MPEG-DASH), `mkv`, `mka`, `mks` | `mp4`
-| `extra.name` | yes | A name for the media. | Big Buck Bunny
-| `extra.thumbnail` | yes | A thumbnail URL for the media. | 
-| `extra.artist_name` | yes | The name of the media artist. | Blender
-
-### Example
-
-```yaml
-action:
-  - service: media_player.play_media
-    target:
-      entity_id: media_player.roku
-    data:
-      media_content_id: http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4
-      media_content_type: url
-      extra:
-        format: mp4
-        name: Big Buck Bunny
-```
-
-## Camera Stream Integration
-
-The `camera.play_stream` service may be used to send camera streams (HLS) directly to your device. This feature requires the `stream` integration and makes use of the built-in PlayOnRoku application.
-
-### Example
-```yaml
-action:
-  service: camera.play_stream
-    target:
-      entity_id: camera.camera
-    data:
-      media_player: media_player.roku
-```
-
 ## Content Deeplinking
 
 The `media_player.play_media` service may be used to deep link to content within an application.

source/_integrations/scene.markdown

@@ -14,6 +14,8 @@ ha_integration_type: entity
 A scene entity is an entity that can restore the state of a group of entities.
 Scenes can be user-defined or can be provided through an integration.
 
+{% include integrations/building_block_integration.md %}
+
 ## The state of a scene
 
 The scene entity is stateless, as in, it cannot have a state like the `on` or

source/_integrations/select.markdown

@@ -15,6 +15,8 @@ Keeps track on `select` entities in your environment, their state, and allows
 you to control them. This integration allows other integrations to offer
 a limited set of selectable options for the entity.
 
+{% include integrations/building_block_integration.md %}
+
 ## Services
 
 The select entity exposes additional services to control the entity in, for example,

source/_integrations/siren.markdown

@@ -14,7 +14,7 @@ ha_integration_type: entity
 
 The Siren integration is built for the controlling and monitoring of siren/chime devices.
 
-Siren entities are created automatically by integrations that support them.
+{% include integrations/building_block_integration.md %}
 
 ## Services
 

source/_integrations/stt.markdown

@@ -13,7 +13,7 @@ ha_integration_type: entity
 
 A speech-to-text (STT) entity allows other integrations or applications to stream speech data to the STT API and get text back.
 
-The speech-to-text entities cannot be implemented manually, but can be provided by integrations.
+{% include integrations/building_block_integration.md %}
 
 ## The state of a speech-to-text entity
 

source/_integrations/switch.markdown

@@ -18,6 +18,8 @@ Keeps track which switches are in your environment, their state and allows you t
 - Maintains a state per switch and a combined state `all_switches`.
 - Registers services `switch.turn_on`, `switch.turn_off`, and `switch.toggle` to control switches.
 
+{% include integrations/building_block_integration.md %}
+
 ## Device Class
 
 The way these switches are displayed in the frontend can be modified in the [customize section](/docs/configuration/customizing-devices/). The following device classes are supported for switches:

source/_integrations/switchbot_cloud.markdown

@@ -21,7 +21,7 @@ The SwitchBot Cloud integration allows you to control SwitchBot [devices](https:
 
 ## Prerequisites
 
-In order to use this integration, you will need at least a SwitchBot Hub and a SwitchBot account to get a token and secret key from the SwitchBot mobile app in Profiles>Preferences>Developer Options.
+In order to use this integration, you will need at least a SwitchBot Hub and a SwitchBot account to get a token and secret key from the SwitchBot mobile app in **Profiles** > **Preferences** > **Developer Options**. If **Developer Options** is not present in preferences, tap the App Version (e.g. 6.24) several times (5~15 times) in succession to open the **Developer Options**.
 
 Please note, device names configured in the SwitchBot app are transferred into Home Assistant.
 
@@ -31,7 +31,7 @@ Please note, device names configured in the SwitchBot app are transferred into H
 
 - Plug (Wi-Fi only, only available in Japan)
 - Plug Mini, both the original and HomeKit-enabled
-- Remotes exposed through the different hubs excepted "Others" (State is inferred from previous commands in Home Assistant and might not reflect reality if you use other ways to control the device)
+- IR appliances exposed through the different hubs excepted "Others" (State is inferred from previous commands in Home Assistant and might not reflect reality if you use other ways to control the device)
 
 <div class='note warning'>
 Only the switch platform is currently supported.

source/_integrations/text.markdown

@@ -13,7 +13,9 @@ ha_integration_type: entity
 
 The Text integration is built for the controlling and monitoring of text values on devices.
 
-Text entities cannot be implemented manually, but can be provided by other integrations. If you are looking for a way to create a text entity, please take a look at the [Text helper](/integrations/input_text).
+{% include integrations/building_block_integration.md %}
+
+If you are looking for a way to create a text entity, please take a look at the [Text helper](/integrations/input_text).
 
 ## Services
 

source/_integrations/time.markdown

@@ -13,7 +13,9 @@ ha_integration_type: entity
 
 The Time integration is built for the controlling and monitoring of times on devices.
 
-Time entities cannot be implemented manually, but can be provided by other integrations. If you are looking for a way to create a similar entity, please take a look at the [Date/Time helper](/integrations/input_datetime).
+{% include integrations/building_block_integration.md %}
+
+If you are looking for a way to create a similar entity, please take a look at the [Date/Time helper](/integrations/input_datetime).
 
 ## Services
 

source/_integrations/todoist.markdown

@@ -18,7 +18,7 @@ This platform allows you to connect to your [Todoist Projects](https://todoist.c
 
 ## Prerequisites
 
-You need to determine your Todoist API token. This is fairly simple to do; just go [to the Integrations section on your Todoist settings page](https://todoist.com/app/settings/integrations) and find the section labeled "API token" at the bottom of the page. Copy that token and use it in your configuration file.
+You need to determine your Todoist API token. Go to the [**Integrations** > **Developer** section on your Todoist settings page](https://todoist.com/app/settings/integrations/developer) and find the section labeled **API token** at the bottom of the page. Copy that token and use it in your configuration file.
 
 {% include integrations/config_flow.md %}
 

source/_integrations/tts.markdown

@@ -17,6 +17,8 @@ ha_integration_type: entity
 
 Text-to-speech (TTS) enables Home Assistant to speak to you.
 
+{% include integrations/building_block_integration.md %}
+
 ## Services
 
 ### Service speak

source/_integrations/twitch.markdown

@@ -18,6 +18,6 @@ The Twitch integration will allow you to monitor [Twitch](https://www.twitch.tv/
 
 ## Get Twitch application credentials
 
-Create a new app at "Register Your Application" in the [Twitch developer portal](https://dev.twitch.tv/console/apps). Then get the __Client ID__ and __Client secret__ for the new application.
+Create a new app at **Register Your Application** in the [Twitch developer portal](https://dev.twitch.tv/console/apps). Enter `https://my.home-assistant.io/redirect/oauth` in the **OAuth Redirect URL** field. Then, get the **Client ID** and **Client secret** from the new application.
 
 {% include integrations/config_flow.md %}

source/_integrations/update.markdown

@@ -26,16 +26,9 @@ made available by the integration providing the update entity, triggering
 the actual update from Home Assistant. The other service exposed allows for
 skipping the offered update.
 
-<div class='note'>
+{% include integrations/building_block_integration.md %}
 
-Update entities are here to be consumed and provided by other integrations and
-are are not designed to be created manually directly.
-
-This page, therefore, does not provide instructions on how to create update
-entities. Please see the ["Update" category](/integrations/#update) on the
-integrations page to find integration offering update entities.
-
-</div>
+For a list of integrations offering update entities, on the integrations page, select the ["Update" category](/integrations/#update).
 
 ## The state of an update entity
 

source/_integrations/vacuum.markdown

@@ -13,6 +13,8 @@ ha_integration_type: entity
 
 The `vacuum` integration enables the ability to control home cleaning robots within Home Assistant.
 
+{% include integrations/building_block_integration.md %}
+
 ## Services
 
 Available services: `start`, `pause`, `stop`, `return_to_base`, `locate`, `clean_spot`, `set_fan_speed` and `send_command`.

source/_integrations/vicare.markdown

@@ -44,6 +44,8 @@ The required Client ID can be obtained as follows:
 
 The `heating_type` can either be `auto` to automatically find the most suitable type for your device or one of `gas`, `oil`, `pellets`, `heatpump`, `fuelcell`, `hybrid`.
 
+Important: the redirect URI that you configure requires that you perform the initial setup on a device that has the ViCare application installed. If your device does not know how to handle the `vicare://` URL, you will receive an **Invalid credentials** notification and the setup procedure will fail. This means: install the ViCare app on your phone and set up the integration from your phone.
+
 Multiple device instances might be generated depending on the number of burners and/or circuits of your installation. If there is more than a single instance all devices are suffixed with the circuit or burner ID.
 
 ## Viessmann API limits

source/_integrations/wake_word.markdown

@@ -15,6 +15,4 @@ A wake-word-detection entity allows other integrations or applications to detect
 
 The wake-word-detection entities cannot be implemented manually, but can be provided by integrations such as [Wyoming](/integrations/wyoming). The API in [Assist Pipelines](https://developers.home-assistant.io/docs/voice/pipelines/) enables wake-word-detection as part of [Assist](/voice_control/).
 
-
-
 {% include integrations/building_block_integration.md %}

source/_integrations/weather.markdown

@@ -11,7 +11,13 @@ ha_domain: weather
 ha_integration_type: entity
 ---
 
-The `weather` platforms gather meteorological information from web services and display the conditions and other details about the weather at the given location. Read the integration documentation for your particular weather provider to learn how to set it up.
+The `weather` platforms gather meteorological information from web services and display the conditions and other details about the weather at the given location. 
+
+{% include integrations/building_block_integration.md %}
+
+For a list of weather integrations, on the integrations page, select the [weather category](/integrations/#weather).
+
+Read the integration documentation for your particular weather provider to learn how to set it up.
 
 Home Assistant currently supports free web services some of which require registration.
 

source/_integrations/weatherkit.markdown

@@ -51,4 +51,11 @@ You can add a new WeatherKit integration entry now that you have all the credent
 - **Apple team ID**: `ABC123DEFG`
   - This value can be found in the top-right of the Apple Developer website.
 - **Private key**: `-----BEGIN PRIVATE KEY----- [...]`
-  - Open the `.p8` file you downloaded earlier in a text editor and copy the contents into this field.
+  - Open the `.p8` file you downloaded earlier in a text editor and copy the _entire_ contents into this field, including the header and footer.
+
+### Troubleshooting
+
+If you are having issues setting up the integration, please make sure the following are true:
+
+- You are entering the key exactly as it appears in the `.p8` file, including the header and footer.
+- There are no leading or trailing spaces in other configuration values.

source/_integrations/zha.markdown

@@ -92,7 +92,8 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl
 ### Recommended Zigbee radio adapters and modules
 
 - Silicon Labs EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy)
-  - [Home Assistant SkyConnect](/skyconnect/)
+  - [Home Assistant SkyConnect](/skyconnect/) (EFR32MG21-based USB dongle)
+  - [Home Assistant Yellow](/yellow/) with integrated EFR32MG21 radio
   - [ITead SONOFF Zigbee 3.0 USB Dongle Plus Model "ZBDongle-E" (EFR32MG21 variant)](https://itead.cc/product/zigbee-3-0-usb-dongle/)
   - [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs-usb-adapter.html)/POPP ZB-Stick (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility))
   - [Elelabs Zigbee Raspberry Pi Shield](https://elelabs.com/products/elelabs-zigbee-shield.html) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility))

source/_posts/2023-10-04-release-202310.markdown

@@ -39,6 +39,7 @@ Enjoy the release!
 - [Other noteworthy changes](#other-noteworthy-changes)
 - [New integrations](#new-integrations)
 - [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
+- [Release 2023.10.1 - October 6](#release-2023101---october-6)
 - [Need help? Join the community!](#need-help-join-the-community)
 - [Breaking changes](#breaking-changes)
 - [All changes](#all-changes)
@@ -251,6 +252,86 @@ The following integrations are now available via the Home Assistant UI:
 [Twitch]: /integrations/twitch
 [World Air Quality Index (WAQI)]: /integrations/waqi
 
+## Release 2023.10.1 - October 6
+
+- 2023.10.0 ([@frenck] - [#101386])
+- Fix ZHA device diagnostics error for unknown unsupported attributes ([@TheJulianJES] - [#101239])
+- Bump pyyardian to 1.1.1 ([@h3l1o5] - [#101363])
+- Fix Withings translations ([@joostlek] - [#101397])
+- Raise vol.Invalid for invalid mqtt device_tracker config ([@jbouwh] - [#101399])
+- Bump dbus-fast to 2.11.1 ([@bdraco] - [#101406])
+- Add translation for Tamper binary sensor ([@joostlek] - [#101416])
+- Add wake word cooldown to avoid duplicate wake-ups ([@synesthesiam] - [#101417])
+- Adjust WeatherFlow wind sensors to appropriately match native unit and library field ([@natekspencer] - [#101418])
+- Bump env_canada to v0.5.37 ([@michaeldavie] - [#101435])
+- Fix device_class.capitalize() in Point ([@fredrike] - [#101440])
+- SMA add missing entity descriptions ([@rklomp] - [#101462])
+- Fix Trafikverket Camera if no location data ([@gjohansson-ST] - [#101463])
+- Update frontend to 20231005.0 ([@piitaya] - [#101480])
+- Bump zeroconf to 0.115.2 ([@bdraco] - [#101482])
+- bump pywaze to 0.5.1 sets timeout to 60s ([@eifinger] - [#101487])
+- Fix caching of latest short term stats after insertion of external stats ([@bdraco] - [#101490])
+- Fix key error in config flow when duplicate stop names exist ([@ViViDboarder] - [#101491])
+- Fix bug in calendar state where alarms due to alarms not scheduled ([@allenporter] - [#101510])
+- Fix for rainbird unique id ([@allenporter] - [#101512])
+- Limit waze_travel_time to 0.5call/s over all entries ([@eifinger] - [#101514])
+- Use config flow in color extractor tests ([@joostlek] - [#101524])
+- Delete existing Withings cloudhook ([@joostlek] - [#101527])
+- Modbus, wrong length when reading strings ([@janiversen] - [#101529])
+- Update LoqedAPI to handle invalid transitions better ([@mikewoudenberg] - [#101534])
+- Cancel callbacks on Withings entry unload ([@joostlek] - [#101536])
+- Bump HAP-python to 4.8.0 ([@bdraco] - [#101538])
+- Add Withings webhooks after a slight delay ([@joostlek] - [#101542])
+- Only import color extractor when domain is in config ([@joostlek] - [#101522])
+
+[#101239]: https://github.com/home-assistant/core/pull/101239
+[#101363]: https://github.com/home-assistant/core/pull/101363
+[#101386]: https://github.com/home-assistant/core/pull/101386
+[#101397]: https://github.com/home-assistant/core/pull/101397
+[#101399]: https://github.com/home-assistant/core/pull/101399
+[#101406]: https://github.com/home-assistant/core/pull/101406
+[#101416]: https://github.com/home-assistant/core/pull/101416
+[#101417]: https://github.com/home-assistant/core/pull/101417
+[#101418]: https://github.com/home-assistant/core/pull/101418
+[#101435]: https://github.com/home-assistant/core/pull/101435
+[#101440]: https://github.com/home-assistant/core/pull/101440
+[#101462]: https://github.com/home-assistant/core/pull/101462
+[#101463]: https://github.com/home-assistant/core/pull/101463
+[#101480]: https://github.com/home-assistant/core/pull/101480
+[#101482]: https://github.com/home-assistant/core/pull/101482
+[#101487]: https://github.com/home-assistant/core/pull/101487
+[#101490]: https://github.com/home-assistant/core/pull/101490
+[#101491]: https://github.com/home-assistant/core/pull/101491
+[#101510]: https://github.com/home-assistant/core/pull/101510
+[#101512]: https://github.com/home-assistant/core/pull/101512
+[#101514]: https://github.com/home-assistant/core/pull/101514
+[#101522]: https://github.com/home-assistant/core/pull/101522
+[#101524]: https://github.com/home-assistant/core/pull/101524
+[#101527]: https://github.com/home-assistant/core/pull/101527
+[#101529]: https://github.com/home-assistant/core/pull/101529
+[#101534]: https://github.com/home-assistant/core/pull/101534
+[#101536]: https://github.com/home-assistant/core/pull/101536
+[#101538]: https://github.com/home-assistant/core/pull/101538
+[#101542]: https://github.com/home-assistant/core/pull/101542
+[@TheJulianJES]: https://github.com/TheJulianJES
+[@ViViDboarder]: https://github.com/ViViDboarder
+[@allenporter]: https://github.com/allenporter
+[@bdraco]: https://github.com/bdraco
+[@eifinger]: https://github.com/eifinger
+[@fredrike]: https://github.com/fredrike
+[@frenck]: https://github.com/frenck
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[@h3l1o5]: https://github.com/h3l1o5
+[@janiversen]: https://github.com/janiversen
+[@jbouwh]: https://github.com/jbouwh
+[@joostlek]: https://github.com/joostlek
+[@michaeldavie]: https://github.com/michaeldavie
+[@mikewoudenberg]: https://github.com/mikewoudenberg
+[@natekspencer]: https://github.com/natekspencer
+[@piitaya]: https://github.com/piitaya
+[@rklomp]: https://github.com/rklomp
+[@synesthesiam]: https://github.com/synesthesiam
+
 ## Need help? Join the community!
 
 Home Assistant has a great community of users who are all more than willing
@@ -367,6 +448,17 @@ backup was initiated. Instead, the local date and time are used for the name.
 
 {% enddetails %}
 
+{% details "Twitch" %}
+
+Any existing app you have created in the [Twitch Developer Portal](https://dev.twitch.tv/console/apps/) to work with this integration must be updated to work with Home Assistant's UI authentication flow. Update the app's configuration to include `https://my.home-assistant.io/redirect/oauth` in its list of "OAuth Redirect URLs"
+
+([@joostlek] - [issue#101414]) ([documentation](/integrations/twitch))
+
+[@joostlek]: https://github.com/joostlek
+[issue#101414]: https://github.com/home-assistant/core/issues/101414
+
+{% enddetails %}
+
 {% details "Z-Wave" %}
 
 Multiple WebSocket commands have been renamed based on [this change in Z-Wave JS](https://zwave-js.github.io/node-zwave-js/#/getting-started/migrating-to-v12?id=renamed-network-heal-to-rebuild-routes).

source/getting-started/onboarding.markdown

@@ -5,9 +5,13 @@ description: "Instructions to get Home Assistant configured."
 
 Alright, you made it here. The tough part is done.
 
-After entering the Home Assistant device's address in your browser's address bar, the welcome screen is shown. Depending on your hardware, preparation may take a while.
+- As the last step of the [installation procedure](/installation/) specific to your device, you entered the Home Assistant device's address in your browser's address bar.
+    - Typically, this is `http://homeassistant.local:8123/`
+    - If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at <a href="http://homeassistant:8123" target="_blank">homeassistant:8123</a> or `http://X.X.X.X:8123` (replace X.X.X.X with your device's IP address).
 
-![Home Assistant preparation](/images/getting-started/onboarding_preparing_01_.png)
+    - **Result**: You now see the welcome screen. Depending on your hardware, preparation may take a while.
+
+    ![Home Assistant preparation](/images/getting-started/onboarding_preparing_01_.png)
 
 With Home Assistant installed, it's time to set up the basics.
 

source/help/trivia.markdown

@@ -26,7 +26,7 @@ Home Assistant is open source software and available under the [Apache 2.0](http
 
 - End of 2020, [Home Assistant Blue](/blue/) was launched. The first dedicated smart home hub for Home Assistant. This limited edition is based on an ODROID and known for its blue aluminum case.
 - In September 2021, [Home Assistant Yellow](/yellow/) was launched. This extendable smart home hub is a custom, open-source design powered by a Raspberry Pi Compute Module 4. Home Assistant Yellow supports both Zigbee and Thread.
-- End of 2022, [Home Assistant SkyConnect](skyconnect) was launched: a USB dongle that provides Zigbee and Thread network support for hubs that do not have this built-in.
+- End of 2022, [Home Assistant SkyConnect](/skyconnect/) was launched: a USB dongle that provides Zigbee and Thread network support for hubs that do not have this built-in.
 
 ## Numbers