Adjust docs to use the new "Settings" panel name and new "System" sub menu (#22645)

plugins/my.rb

@@ -85,6 +85,7 @@ module Jekyll
 
       # Default title used for in-line text
       DEFAULT_TITLES = {
+        "automations" => "Automations & Scenes",
         "blueprint_import" => "Import Blueprint",
         "cloud" => "Home Assistant Cloud",
         "config_energy" => "Energy Configuration",

source/_docs/automation/troubleshooting.markdown

@@ -3,7 +3,7 @@ title: "Troubleshooting Automations"
 description: "Tips on how to troubleshoot your automations."
 ---
 
-When an automation is run, all steps are recorded and a trace is made. From the UI choose **Configuration** which is located in the sidebar, then click on **Automation** to go to the automation editor or click this button directly: {% my automations badge %}
+When an automation is run, all steps are recorded and a trace is made. From the UI choose **Settings** which is located in the sidebar, then click on **Automations & Scenes** to go to the automation editor or click this button directly: {% my automations badge %}
 
 Click on the clock icon next to an automation to enter the debugging screen. Alternatively, click on **Show trace** directly from a Logbook automation entry.
 

source/_docs/blueprint/tutorial.markdown

@@ -230,7 +230,7 @@ For this tutorial, we're going to share it on GitHub Gists. This is a good optio
 - Content is the content of the blueprint file.
 - Click the "Create Gist" button
 
-You can now copy the URL of your new Gist and share it with other people. They can import it by going to **Configuration**, **Blueprints** and clicking on the blue "Import Blueprint" button.
+You can now copy the URL of your new Gist and share it with other people. They can import it by going to **Settings** -> **Automations & Scenes** -> **Blueprints** and clicking on the blue "Import Blueprint" button.
 
 ### Share on the Blueprint Exchange
 

source/_docs/configuration.markdown

@@ -3,7 +3,7 @@ title: "Configuration.yaml"
 description: "Configuring Home Assistant via text files."
 ---
 
-While you can configure most of Home Assistant directly from the user interface under {% my config title="Configuration" %}, some parts need you to edit `configuration.yaml`. This file contains integrations to be loaded along with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable specific functionality.
+While you can configure most of Home Assistant directly from the user interface under {% my config %}, some parts need you to edit `configuration.yaml`. This file contains integrations to be loaded along with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable specific functionality.
 
 If you run into trouble while configuring Home Assistant, refer to the [configuration troubleshooting page](/docs/configuration/troubleshooting/) and the [`configuration.yaml` examples](/examples/#example-configurationyaml).
 

source/_docs/locked_out.md

@@ -34,7 +34,7 @@ If you are running Home Assistant in a container, you can use the command line i
 #### To reset a user's password, as an administrator via the web interface
 
 1. Confirm that you have "Advanced Mode" activated on your "Profile" page.
-2. Click "Configuration" in the sidebar.
+2. Click "Settings" in the sidebar.
 3. Scroll down to "Users", and click in to that section.
 4. Click on the user, this should bring up a dialog box.
 5. At the bottom of the dialog box, click "Change Password".
@@ -45,7 +45,7 @@ If you are running Home Assistant in a container, you can use the command line i
 
 #### To delete a user, as an administrator via the web interface
 
-1. Click "Configuration" in the sidebar.
+1. Click "Settings" in the sidebar.
 2. Scroll down to "Users", and click in to that section.
 3. Click on the user, this should bring up a dialog box.
 4. At the bottom of the dialog box, click "Delete User".

source/_docs/scene/editor.markdown

@@ -5,7 +5,7 @@ description: "Instructions on how to use the scenes editor."
 
 In Home Assistant 0.102 we introduced the first version of our scene editor. If you just created a new configuration with Home Assistant, then you're all set! Go to the UI and enjoy.
 
-From the UI choose **Configuration** which is located in the sidebar, then click on **Scenes** to go to the scene editor. Press the **Add Scene** button in the lower right corner to get started.
+From the UI choose **Settings** which is located in the sidebar, then click on **Automations & Scenes** to go to the scene editor. Press the **Add Scene** button in the lower right corner to get started.
 
 Choose a meaningful name for your scene.
 

source/_includes/common-tasks/update.md

@@ -20,7 +20,7 @@ To update Home Assistant Core when you run Home Assistant {{ page.installation_n
   content: |
 
     1. Open your Home Assistant UI
-    2. Navigate to the Configuration panel
+    2. Navigate to the Settings panel
     3. On the top you will be presented with an update notification
 
     _If you do not see that notification you can click the overflow menu in the top right and select "Check for updates"._

source/_includes/installation/container.md

@@ -34,7 +34,7 @@ Once the Home Assistant Container is running Home Assistant should be accessible
 
 If you change the configuration you have to restart the server. To do that you have 3 options.
 
-1. In your Home Assistant UI go to the **Configuration** panel -> **Server management** and click the "Restart" button.
+1. In your Home Assistant UI go to the **Settings** -> **System** and click the "Restart" button.
 2. You can go to the **Developer Tools** -> **Services**, select the service `homeassistant.restart` and click "Call Service".
 3. Restart it from a terminal.
 

source/_integrations/aemet.markdown

@@ -26,7 +26,7 @@ The AEMET OpenData service is completely free but is limited to the Spanish terr
 
 ## Configuration
 
-To add AEMET OpenData integration go to **Configuration** >> **Devices & Services** and find the integration in the list.
+To add AEMET OpenData integration go to **Settings** -> **Devices & Services** and find the integration in the list.
 
 {% configuration_basic %}
 API Key:

source/_integrations/backup.markdown

@@ -28,7 +28,7 @@ backup:
 ```
 
 You need to restart Home Assistant after you add this configuration.
-When it has started up again you will find a new "Backup" entry in the main menu (**Configuration** -> **Backup**).
+When it has started up again you will find a new "Backup" entry in the main menu (**Settings** -> **System** -> **Backup**).
 
 The backup files are stored in a new "backups" subdirectory in the root of your configuration directory.
 

source/_integrations/bmw_connected_drive.markdown

@@ -47,7 +47,7 @@ This integration provides the following platforms:
 
 ## Configuration
 
-Enable the `BMW Connected Drive` integration via **Configuration** > **Devices & Services**.
+Enable the `BMW Connected Drive` integration via **Settings** -> **Devices & Services**.
 
 <div class='note'>
 

source/_integrations/cloud.markdown

@@ -29,7 +29,7 @@ cloud:
 
 Documentation of further configuration possibilities are located at [NabuCasa](https://www.nabucasa.com/config/)
 
-Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Configuration** panel, make sure you have the following option enabled in your `configuration.yaml` file.
+Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Settings** panel, make sure you have the following option enabled in your `configuration.yaml` file.
 
 ```yaml
 config:

source/_integrations/control4.markdown

@@ -25,7 +25,7 @@ Before setting up, you should assign a static IP address/DHCP reservation on you
 
 ## Options
 
-The Control4 integration offers additional options in **Configuration** -> **Devices & Services** -> **Control4** -> **Options**:
+The Control4 integration offers additional options in **Settings** -> **Devices & Services** -> **Control4** -> **Options**:
 
 {% configuration %}
 Seconds between updates:

source/_integrations/dexcom.markdown

@@ -32,7 +32,7 @@ There are two Dexcom Share servers, `US` for United States customers, and `OUS`
 
 ### Unit of measurement
 
-The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, go to **Configuration** >> **Devices & Services** in the UI, and click `OPTIONS`.
+The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, go to **Settings** -> **Devices & Services** in the UI, and click `OPTIONS`.
 
 ## Sensor
 

source/_integrations/dlna_dmr.markdown

@@ -24,7 +24,7 @@ Please note that some devices, such as Samsung TVs, are rather picky about the s
 
 ## Options
 
-Options for DLNA DMR devices can be set going to **Configuration** -> **Devices & Services** -> **DLNA Digital Media Renderer** -> **Configuration**.
+Options for DLNA DMR devices can be set going to **Settings** -> **Devices & Services** -> **DLNA Digital Media Renderer** -> **Configuration**.
 
 {% configuration_basic %}
 Event listener port:

source/_integrations/dsmr.markdown

@@ -39,7 +39,7 @@ A sensor platform for Belgian, Dutch, Luxembourg and Swedish Smart Meters which
 
 ### Options
 
-To configure options for DSMR integration go to **Configuration** >> **Devices & Services** and press **Options** on the DSMR card.
+To configure options for DSMR integration go to **Settings** -> **Devices & Services** and press **Options** on the DSMR card.
 
 #### Time between updates
 

source/_integrations/eafm.md

@@ -21,7 +21,7 @@ The UK Environment Agency Flood Monitoring only provides data for England - Nort
 
 ## Configuration
 
-Home Assistant offers the flood monitoring integration through **Configuration** -> **Devices & Services** -> **Environment Agency Flood Gauges**.
+Home Assistant offers the flood monitoring integration through **Settings** -> **Devices & Services** -> **Environment Agency Flood Gauges**.
 
 You will be prompted to select a monitoring station. You can find the name of nearby monitoring stations on the Flood information service [website](https://flood-warning-information.service.gov.uk/river-and-sea-levels).
 

source/_integrations/ecobee.markdown

@@ -53,7 +53,7 @@ Your new application will now appear on the left. Upon clicking on the applicati
 
 ## Configuration
 
-1. In the **Configuration** > **Devices & Services** menu, click **+** and then select "ecobee" from the pop-up menu.
+1. In the **Settings** -> **Devices & Services** menu, click **+** and then select "ecobee" from the pop-up menu.
 2. In the pop-up box, enter the API key you obtained from ecobee's [developer portal](https://ecobee.com/developers).
 3. In the next pop-up box, you will be presented with a unique four-character PIN code which you will need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by logging in, selecting **My Apps** from the hamburger menu, clicking **Add Application** on the left, entering the PIN code from Home Assistant, clicking **Validate** and then **Add Application** in the bottom right.
 4. After authorizing the app with ecobee, return to Home Assistant and click **Submit**. If the authorization was successful, a configuration entry will be created and your thermostats and sensors will be available in Home Assistant.
@@ -80,7 +80,7 @@ api_key:
   <img src='/images/screenshots/ecobee-thermostat-card.png' />
 </p>
 
-You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Configuration** > **Devices & Services** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.
+You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Settings** -> **Devices & Services** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.
 
 ## Notifications
 

source/_integrations/flume.markdown

@@ -26,7 +26,7 @@ You can find your Client ID and Client Secret under "API Access" on the [setting
 
 The Flume API access is available to Flume Insight users only, which may require a paid subscription.
 
-To add `Flume` to your installation, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Flume**.
+To add `Flume` to your installation, go to **Settings** -> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Flume**.
 
 ## Configuration for Binary Sensor
 

source/_integrations/freebox.markdown

@@ -38,7 +38,7 @@ Please consult the [API documentation](https://dev.freebox.fr/sdk/os/) for more
 
 ### Via the frontend
 
-Menu: **Configuration** -> **Devices & Services**. Search for "Freebox", add your host and port, click submit.
+Menu: **Settings** -> **Devices & Services**. Search for "Freebox", add your host and port, click submit.
 
 If you add the integration for the first time, follow the instructions in the [Initial setup](#initial-setup) section.
 

source/_integrations/harmony.markdown

@@ -35,7 +35,7 @@ Supported units:
 
 **Note:** Depending on the firmware, you may need to enable XMPP for this integration to work. From your Harmony app, go to: **Menu** > **Harmony Setup** > **Add/Edit Devices & Activities** > **Remote & Hub** > **Enable XMPP**.
 
-Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Configuration** >> **Devices & Services** >> **Your Logitech Harmony Hub**
+Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Settings** -> **Devices & Services** >> **Your Logitech Harmony Hub**
 
 ### Configuration file
 

source/_integrations/homekit.markdown

@@ -313,7 +313,7 @@ The HomeKit Accessory Protocol Specification only allows a maximum of 150 unique
 
 ### Multiple HomeKit instances
 
-If you create a HomeKit integration via the UI (i.e., **Configuration** >> **Devices & Services**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port.
+If you create a HomeKit integration via the UI (i.e., **Settings** -> **Devices & Services**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port.
 
 It is recommended to only edit a HomeKit instance in the UI that was created in the UI, and likewise, only edit a HomeKit instance in YAML that was created in YAML.
 
@@ -636,7 +636,7 @@ Ensure that the [`ffmpeg`](/integrations/ffmpeg) integration is configured corre
 
 #### Camera streaming is unstable or slow 
 
-If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Configuration** >> **Devices & Services** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen.
+If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Settings** -> **Devices & Services** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen.
 
 #### Multiple camera streams
 

source/_integrations/input_datetime.markdown

@@ -16,7 +16,7 @@ The `input_datetime` integration allows the user to define date and time values
 that can be controlled via the frontend and can be used within automations and
 templates.
 
-The preferred way to configure input datetime is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Date and/or time** option.
+The preferred way to configure input datetime is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Date and/or time** option.
 
 To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it.
 If you removed `default_config:` from your configuration, you must add `input_datetime:` to your `configuration.yaml` first, then you can use the UI.

source/_integrations/input_number.markdown

@@ -14,7 +14,7 @@ ha_integration_type: helper
 
 The `input_number` integration allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. The frontend can display a slider, or a numeric input box. Changes to the slider or numeric input box generate state events. These state events can be utilized as `automation` triggers as well.
 
-The preferred way to configure an input number is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Number** option.
+The preferred way to configure an input number is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Number** option.
 
 To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it.
 If you removed `default_config:` from you configuration, you must add `input_number:` to your `configuration.yaml` first, then you can use the UI.

source/_integrations/input_select.markdown

@@ -14,7 +14,7 @@ ha_integration_type: helper
 
 The `input_select` integration allows the user to define a list of values that can be selected via the frontend and can be used within conditions of an automation. When a user selects a new item, a state transition event is generated. This state event can be used in an `automation` trigger.
 
-The preferred way to configure an input select is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Dropdown** option.
+The preferred way to configure an input select is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Dropdown** option.
 
 To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it.
 If you removed `default_config:` from you configuration, you must add `input_select:` to your `configuration.yaml` first, then you can use the UI.

source/_integrations/input_text.markdown

@@ -14,7 +14,7 @@ ha_integration_type: helper
 
 The `input_text` integration allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the value stored in the text box generate state events. These state events can be utilized as `automation` triggers as well. It can also be configured in password mode (obscured text).
 
-The preferred way to configure an input text is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Text** option.
+The preferred way to configure an input text is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Text** option.
 
 To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it.
 If you removed `default_config:` from you configuration, you must add `input_text:` to your `configuration.yaml` first, then you can use the UI.

source/_integrations/keenetic_ndms2.markdown

@@ -21,4 +21,4 @@ Router running NDMS firmware versions 2.05 and up. It uses telnet connection so
 
 ## Configuration
 
-To add Keenetic router to your installation, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Keenetic NDMS2 Router**.
+To add Keenetic router to your installation, go to **Settings** -> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Keenetic NDMS2 Router**.

source/_integrations/konnected.markdown

@@ -48,7 +48,7 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i
 
 ### Web Interface
 
-Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Configuration** -> **Devices & Services** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
+Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Settings** -> **Devices & Services** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
 
 Selecting one of these discovered panels will guide you through connecting and configuring the panel. If your panel was discovered via SSDP, you shouldn't need any information to complete configuration - simply confirm that the information displayed is correct. If the UI prompts you for IP/Port, you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
 
@@ -56,15 +56,15 @@ Selecting one of these discovered panels will guide you through connecting and c
 
 If you have an existing `configuration.yaml` completing the UI configuration will do a one time import of the settings contained in `configuration.yaml`. Once the import creates a **Configured** integration the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the `konnected` section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the settings provided in the Home Assistant web interface.
 
-If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Devices & Services** -> **Configured** and repeat the UI configuration for that device.
+If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Settings** -> **Devices & Services** -> **Configured** and repeat the UI configuration for that device.
 
 </div>  
 
-Once configuration is completed you'll see a Konnected.io entry in **Configuration** -> **Devices & Services** => **Configured**.  If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the settings UI to configure zone behavior.
+Once configuration is completed you'll see a Konnected.io entry in **Settings** -> **Devices & Services** -> **Configured**.  If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the settings UI to configure zone behavior.
 
 #### Using Settings UI to Configure Zone Behavior
 
-The settings for each panel can be accessed by selecting the entry in **Configuration** -> **Devices & Services** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure these settings at any time and once completed the settings will be immediately applied.
+The settings for each panel can be accessed by selecting the entry in **Settings** -> **Devices & Services** -> **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure these settings at any time and once completed the settings will be immediately applied.
 
 The settings UI starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone.  After that, you'll be prompted, for each zone that is not disabled, to configure details of the zones' behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone.  
 **Note some zones do not support all behaviors. The UI will reflect specific options available to each zone.**
@@ -310,7 +310,7 @@ konnected:
 
 ## Unique IDs and the Entity Registry
 
-Beginning in Home Assistant release 0.90, unique IDs are generated for each sensor or switch entity. This enables end users to modify the entity names and entity IDs through the Home Assistant UI at **Configuration** -> **Entities**.
+Beginning in Home Assistant release 0.90, unique IDs are generated for each sensor or switch entity. This enables end users to modify the entity names and entity IDs through the Home Assistant UI at **Settings** -> **Devices & Services** -> **Entities**.
 
 Unique IDs are internally generated as follows:
 

source/_integrations/meteo_france.markdown

@@ -34,7 +34,7 @@ It displays the current weather along with a 5 days forecast and create sensors,
 
 To be used with the weather dashboard card to access current condition, today and next four days forecast.
 
-The weather platform can be configured in the frontend to decide if the forecast is given daily (default) or hourly. To change the setting go in **Configuration** -> **Devices & Services**, click on the city name in **Météo-France** box and click on **Options**. You can update the `Forecast mode` by choosing between `daily` or `hourly`.
+The weather platform can be configured in the frontend to decide if the forecast is given daily (default) or hourly. To change the setting go in **Settings** -> **Devices & Services**, click on the city name in **Météo-France** box and click on **Options**. You can update the `Forecast mode` by choosing between `daily` or `hourly`.
 
 ## Sensor platforms
 
@@ -59,7 +59,7 @@ All the following sensors will be created :
 
 Warning: The probability entities data are not always provided by the API. They are added only if available.
 
-To enable an entity disabled by default, go in **Configuration** -> **Devices & Services**, click on the city name in **Météo-France** and then the **X entities** link. You will have the list of the enabled entities. Here click the filter button and select **Show disable entities**. The disabled entities will be visible in the list, select the one you want to enable and click the **Enable Selected** button.
+To enable an entity disabled by default, go in **Settings** -> **Devices & Services**, click on the city name in **Météo-France** and then the **X entities** link. You will have the list of the enabled entities. Here click the filter button and select **Show disable entities**. The disabled entities will be visible in the list, select the one you want to enable and click the **Enable Selected** button.
 
 ### About `next_rain` condition sensor
 

source/_integrations/nest.markdown

@@ -465,7 +465,7 @@ This feature is enabled by the following permissions:
 
 - For general trouble with the SDM API OAuth authorization flow with Google, see [Troubleshooting](https://developers.google.com/nest/device-access/authorize#troubleshooting).
 
-- Check **Configuration** then **Logs** to see if there are any error messages or misconfigurations then see the error messages below.
+- Check **Settings** -> **System** -> **Logs** to see if there are any error messages or misconfigurations then see the error messages below.
 
 - *Reauthentication required often*: If you are getting logged out every 7 days, this means an OAuth Consent Screen misconfiugration or your authentication token was revoked by Google for some other reason.
 

source/_integrations/netatmo.markdown

@@ -244,7 +244,7 @@ client_secret:
 
 **After the `client_id` and `client_secret` are added to your `configuration.yaml` you must restart Home Assistant and then enable Netatmo through the integrations page.**
 
-Menu: **Configuration** -> **Devices & Services**.
+Menu: **Settings** -> **Devices & Services**.
 
 Click on the `+` sign to add an integration and click on **Netatmo**.
 After completing the configuration flow, the Netatmo integration will be available.

source/_integrations/plex.markdown

@@ -376,5 +376,5 @@ Refresh a Plex library to scan for new and updated media.
 
 ## Notes
 
-- The Plex integration supports multiple Plex servers. Additional connections can be configured under **Configuration** > **Devices & Services**.
+- The Plex integration supports multiple Plex servers. Additional connections can be configured under **Settings** -> **Devices & Services**.
 - Movies must be located under the 'Movies' section in a Plex library to properly view the 'playing' state.

source/_integrations/rfxtrx.markdown

@@ -88,7 +88,7 @@ connection: &rfxtrx
 
 ## Settings options
 
-To configure options for RFXtrx integration go to **Configuration** >> **Devices & Services** and press **Options** on the RFXtrx card.
+To configure options for RFXtrx integration go to **Settings** -> **Devices & Services** and press **Options** on the RFXtrx card.
 
 <img src='/images/integrations/rfxtrx/options.png' />
 

source/_integrations/roon.markdown

@@ -20,7 +20,7 @@ This integration uses Roon Core, a Roon application that runs on a machine on yo
 
 ## Configuration
 
-1. From the Home Assistant front-end, navigate to **Configuration** then **Integrations**. Under **Set up a new integration** locate 'Roon' and click **Configure**.
+1. From the Home Assistant front-end, navigate to **Settings** -> **Devices & Services**. Under **Set up a new integration** locate 'Roon' and click **Configure**.
 2. Home Assistant will then try to find your Roon Core - if it is successful it will display `Authorize HomeAssistant in Roon`. Click **Submit** and skip to step 4
 3. If your Roon Core is not automatically found you can enter the `Hostname` or `IP address` for the Roon Core machine when requested and click **Submit**.
 4. Home Assistant will then contact your Roon Core and ask to be authorized. You will need to enable this extension in the Room Application. Go to **Settings** and then **Extensions**, there you will see an entry for Home Assistant with a button next to it. Click **Enable**.

source/_integrations/ruckus_unleashed.markdown

@@ -22,7 +22,7 @@ There is currently support for the following device types within Home Assistant:
 
 ## Configuration
 
-To add a Ruckus Unleashed device to your installation, go to **Configuration** -> **Devices & Services**, click the `+` button, then select **Ruckus** from the list of integrations.
+To add a Ruckus Unleashed device to your installation, go to **Settings** -> **Devices & Services**, click the `+` button, then select **Ruckus** from the list of integrations.
 
 It is required to configure the IP address of your **master access point**. See the section Access Points on the management web interface. And perhaps consider to set a preferred master (Admin & Services>System>System Info>Preferred master).
 

source/_integrations/screenlogic.markdown

@@ -32,7 +32,7 @@ The Pentair ScreenLogic integration allows you to integrate your Pentair Intelli
 
 ## Options
 
-ScreenLogic options are set via **Configuration** -> **Devices & Services** -> **Pentair ScreenLogic** -> **Options**.
+ScreenLogic options are set via **Settings** -> **Devices & Services** -> **Pentair ScreenLogic** -> **Options**.
 
 * Seconds between scans - How many seconds between each polling of the ScreenLogic gateway.
 

source/_integrations/sentry.markdown

@@ -46,6 +46,6 @@ The Sentry integration provides settings to:
 - Ability to send out events originating from third-party Python packages.
 - Enable performance tracing and tune the tracing sample rate used.
 
-To change the settings go in **Configuration** -> **Devices & Services**, find the already installed **Sentry** box and click on **Options**.
+To change the settings go in **Settings** -> **Devices & Services**, find the already installed **Sentry** box and click on **Options**.
 
 After changing Sentry settings, you'll need to restart Home Assistant in order to make them effective.

source/_integrations/somfy_mylink.markdown

@@ -18,4 +18,4 @@ The `Somfy MyLink` integration is used as an interface to a compatible Somfy MyL
 
 {% include integrations/config_flow.md %}
 
-If any of your devices are reversed, they can be adjusted in **Configuration** >> **Devices & Services** >> **Somfy MyLink** >> `Options`.
+If any of your devices are reversed, they can be adjusted in **Settings** -> **Devices & Services** -> **Somfy MyLink** >> `Options`.

source/_integrations/subaru.markdown

@@ -70,7 +70,7 @@ The current lock status is always unknown due to the fact that the Subaru API do
 
 Subaru integration options are set via:
 
-**Configuration** -> **Devices & Services** -> **Subaru** -> **Options**.
+**Settings** -> **Devices & Services** -> **Subaru** -> **Options**.
 
 - **Enable vehicle polling *[Default: off]*:** When enabled, vehicle polling will send a remote command to your vehicle every 2 hours to obtain new sensor data. This involves "waking" your vehicle and requesting that it send new data to Subaru servers. Without vehicle polling, new sensor data is only received when the vehicle automatically pushes data (normally after engine shutdown). This option only applies to Gen 2 vehicles with Security Plus subscriptions because it uses a "locate" command to request the data.
 

source/_integrations/system_health.markdown

@@ -18,6 +18,6 @@ This integration is by default enabled, unless you've disabled or removed the [`
 system_health:
 ```
 
-System Health integration data can be viewed at **Configuration** -> **Info**.
+System Health integration data can be viewed at **Settings** -> **System** -> **System Health**.
 
 Data includes information about your system architecture, operating system and version, Home Assistant installation type and version, Python version, frontend version, the number of [Dashboards](/dashboards/dashboards/) and [Views](/dashboards/views/) you have, and more.

source/_integrations/system_log.markdown

@@ -9,7 +9,7 @@ ha_domain: system_log
 ha_integration_type: integration
 ---
 
-The `system_log` integration stores information about all logged errors and warnings in Home Assistant. To view your logs, navigate to **Configuration** -> **Settings** -> **Logs**. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`.
+The `system_log` integration stores information about all logged errors and warnings in Home Assistant. To view your logs, navigate to **Settings** -> **System** -> **Logs**. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`.
 
 ## Configuration
 

source/_integrations/xiaomi_aqara.markdown

@@ -66,7 +66,7 @@ Please note, there are two versions of the hub: v1 and v2. v1 can be used with H
 
 Follow the setup process using your phone and Mi-Home app. From here you will be able to retrieve the key (password) from within the app following [this tutorial](https://www.domoticz.com/wiki/Xiaomi_Gateway_(Aqara)#Adding_the_Xiaomi_Gateway_to_Domoticz).
 
-To enable {{ page.title }} in your installation, go to **Configuration** in the sidebar, then click **Devices & Services**. Xiaomi Aqara gateways should be discovered automatically and should show up in the overview. Hit configure and go through the steps to specify the optional settings. If your aqara gateway does not show up automatically, click the + icon in the lower right. Then search for "xiaomi_aqara" and enter the setup. Multiple gateways can be configured by simply repeating the setup multiple times.
+To enable {{ page.title }} in your installation, go to **Settings** -> **Devices & Services**. Xiaomi Aqara gateways should be discovered automatically and should show up in the overview. Hit configure and go through the steps to specify the optional settings. If your aqara gateway does not show up automatically, click the + icon in the lower right. Then search for "xiaomi_aqara" and enter the setup. Multiple gateways can be configured by simply repeating the setup multiple times.
 
 {% configuration %}
 interface:

source/_integrations/zha.markdown

@@ -424,7 +424,7 @@ When reporting issues, please provide the following information in addition to i
 1. Debug logs for the issue, see [debug logging](#debug-logging)
 2. Model of Zigbee radio being used
 3. If issue is related to a specific Zigbee device, provide device Zigbee signature. Signature is available at
-**Configuration** -> **Devices & Services** -> **Zigbee Home Automation** (click **Configure**) -> **Devices** (pick your device) -> **Zigbee Device Signature**
+**Settings** -> **Devices & Services** -> **Zigbee Home Automation** (click **Configure**) -> **Devices** (pick your device) -> **Zigbee Device Signature**
 
 ### Debug logging
 

source/_integrations/zwave_js.markdown

@@ -860,7 +860,7 @@ If the interview is complete, then the device does not yet have a device file fo
 
 When trying to determine why something isn't working as you expect, or when reporting an issue with the integration, it is helpful to know what Z-Wave JS sees as the current state of your Z-Wave network. To get a dump of your current network state, follow the menu:
 
-{% my integrations title="**Configuration** -> **Devices & Services**" %} -> **Z-Wave JS** -> **...** -> **Download diagnostics**
+{% my integrations title="**Settings** -> **Devices & Services**" %} -> **Z-Wave JS** -> **...** -> **Download diagnostics**
 
 ### Interference issues
 

source/dashboards/dashboards.markdown

@@ -5,7 +5,7 @@ description: "Multiple powerful and configurable dashboards in Home Assistant."
 
 You can define multiple dashboards in Home Assistant. Each dashboard can be added to the sidebar. This makes it possible to create separate control dashboards for each individual part of your house.
 
-You can manage your dashboards via the user interface. Go to **Configuration** -> **Dashboards**. Here you can see all defined dashboards and create new ones.
+You can manage your dashboards via the user interface. Go to **Settings** -> **Dashboards**. Here you can see all defined dashboards and create new ones.
 
 ## Using YAML for the default dashboard
 

source/help/reporting_issues.markdown

@@ -8,7 +8,7 @@ If you have an installation, a setup or a configuration issue please use our [Fo
 
 If you found a bug then please report it in one of our [trackers](/help/#bugs-feature-requests-and-alike). To help you and our developers to identify the issue quickly, please fill out the provided template. The "weird" content you will see is there to render your entry in a nice format after submitting. It's just [markdown](https://guides.github.com/features/mastering-markdown/).
 
-Please refer to the **Info** page, which is accessible inside the **Configuration** panel in the Home Assistant frontend.
+Please refer to the **Settings** -> **About** page, which is accessible inside the Home Assistant frontend.
 
 ## First Home Assistant release with the issue
 

source/more-info/no-url-available.markdown

@@ -36,7 +36,7 @@ There are multiple options to consider:
 If you have Nabu Casa's Home Assistant Cloud, the easiest way to resolve this,
 is by visiting your Home Assistant instance from the remote UI URL.
 
-Go to **Configuration** -> **Cloud**.
+Go to **Settings** -> **Home Assistant Cloud**.
 
 Visit your instance on the remote URL. Now you can set up the integration as normal, without getting the No URL
 Available message.
@@ -64,7 +64,7 @@ like this.
 Please note, you'll need to enable advanced mode in your user profile in order
 to set this up.
 
-Go to **Configuration** -> **General**.
+Go to **Settings** -> **System** -> **General**.
 
 On this page, two fields that can resolve this issue: "External URL"
 and "Internal URL".