Adjust supervisor references (#20556)

source/_faq/addon_not_starting.markdown

@@ -3,6 +3,6 @@ title: "Why does the start button for an add-on flash red when I click it?"
 ha_category: Home Assistant
 ---
 
-If you are looking for more information about add-ons, which won't start or install, navigate to Supervisor > System in the UI and check the logs.
+If you are looking for more information about add-ons, which won't start or install, navigate to {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} in the UI and check the logs.
 
-The logs on this page are the same you would see using `ha logs` in the custom CLI.
+The logs on this page are the same you would see using `su logs` in the custom CLI.

source/_includes/common-tasks/backups.md

@@ -14,7 +14,7 @@ A partial backup consists of any number of the above default directories and ins
 
 ### Making a Backup from the UI
 
-1. Go to {% my supervisor_backups title="Supervisor > Backups" %} in the UI.
+1. Go to {% my supervisor_backups title="Configuration > Add-ons & Backups > Backups" %} in the UI.
 2. Provide a name for the backup.
 3. Choose full or partial.
 4. Choose to password protect or not. Password-protected backups cannot easily be browsed outside of Home Assistant OS.

source/_includes/common-tasks/beta_version.md

@@ -9,11 +9,10 @@ If you would like to test next release before anyone else, you can install the b
 - title: From the UI
   content: |
 
-   1. In your Home Assistant UI navigate to the Supervisor panel
-   2. Navigate to the System tab
-   3. Click the link that says "Join beta"
-   4. Navigate to the Dashboard tab
-   5. Install the update that is presented to you
+   1. In your Home Assistant UI navigate to {% my supervisor_info title="Configuration > Add-ons & Backups > System" %}
+   2. Click the link that says "Join beta"
+   3. Navigate to Configuration panel
+   4. Install the update that is presented to you
 
 - title: From the CLI
   content: |

source/_includes/common-tasks/data_disk.md

@@ -27,7 +27,7 @@ The data disk feature can be used on an existing installation without losing dat
 ### Using UI to move the data partition
 
 1. Connect the data disk to your system.
-2. Go to **{% my supervisor_info title="Supervisor >> System" %}** in the UI.
+2. Go to **{% my supervisor_info title="Configuration > Add-ons & Backups > System" %}** in the UI.
 3. Press the three dots on the bottom right of the Host card and choose "Move datadisk"
 4. Select the data disk from the list of available devices.
 5. Press "Move".

source/_includes/common-tasks/file_access.md

@@ -1,6 +1,6 @@
 ## Configuring access to files
 
-Your Home Assistant Operating server includes two repositories by default: The official core add-on repository, and the community add-on repository. All of the add-ons mentioned here can be installed by navigating to the add-on store using Supervisor > Add-on Store in the UI.
+Your Home Assistant Operating server includes two repositories by default: The official core add-on repository, and the community add-on repository. All of the add-ons mentioned here can be installed by navigating to the add-on store using {% my supervisor_addon_store title="Configuration > Add-ons & Backups > Add-on Store" %} in the UI.
 
 One of the first things to take care of after installing Home Assistant OS is to provide yourself access to files. There are several add-ons commonly used for this, and most users employ a mix of various add-ons. Default directories on the host are mapped to the add-ons so that they can be accessed by the services any particular add-on might provide. On the host system these directories exist on the `/data` partition at `/mnt/data/supervisor/`.
 
@@ -21,7 +21,7 @@ The Samba add-on creates smb shares which can be accessed from another computer.
 
 To configure the Samba add-on, you only need to set a user and password of your choice on the configuration page, save, and then start the add-on. The add-on will not start without setting a password!
 
-To connect to the Samba server from another device, you will use the IP address or hostname of your server. Either of these can be found on the Supervisor > System > page of your UI within the Host card.
+To connect to the Samba server from another device, you will use the IP address or hostname of your server. Either of these can be found on the {% my supervisor_info title="Configuration > Add-ons & Backups > System" %} page of your UI within the Host card.
 
 For connecting from Windows 10, you can enter the IP address or hostname in File Explorer's address bar with two backslashes, as shown in the example screenshot.
 

source/_includes/common-tasks/third-party-addons.md

@@ -11,8 +11,8 @@ Home Assistant cannot guarantee the quality or security of third-party add-ons.
 </div>
 
 <p class='img'>
-<img src='/images/hassio/screenshots/main_panel_addon_store.png' />
-From the Supervisor main panel open the add-on store.
+<img src='/images/hassio/screenshots/dashboard.png' />
+From {% my supervisor title="Configuration > Add-ons & Backups" %} open the add-on store.
 </p>
 
 <p class='img'>
@@ -22,4 +22,4 @@ Add the URL of the repository and then press "Add". A new card for the repositor
 
 ### Help: Repository is not showing up
 
-If you have added a repository, but it's not showing up, it means that the repository contains invalid configuration. Go to the Supervisor panel and then the System tab to find the System log. It should tell you what went wrong. Report this information to the repository author.
+If you have added a repository, but it's not showing up, it means that the repository contains invalid configuration. Go to {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} to find the System log. It should tell you what went wrong. Report this information to the repository author.

source/_includes/common-tasks/update.md

@@ -20,10 +20,10 @@ To update Home Assistant Core when you run Home Assistant {{ page.installation_n
   content: |
 
     1. Open your Home Assistant UI
-    2. Navigate to the Supervisor panel
-    3. On the Dashboard tab you will be presented with an update notification
+    2. Navigate to the Configuration panel
+    3. On the top you will be presented with an update notification
 
-    _If you do not see that notification you can navigate to the System tab. and click the "Reload Supervisor" button._
+    _If you do not see that notification you can navigate to the {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} panel. and click the "Reload Supervisor" button._
 
 - title: Using the CLI
   content: |

source/_integrations/firmata.markdown

@@ -50,7 +50,7 @@ You may configure multiple Firmata boards. Each board has the following options:
 
 {% configuration %}
 serial_port:
-  description: The port where your board is connected to your Home Assistant host. It is recommended to use the `by-id` reference (instead of numerical like `/dev/ttyACM0` or `/dev/ttyUSB0`) since these will never change after a reboot. If you are using HassOS, you can find a list of connected serial devices in the Hardware dialog on the System tab of the Supervisor.
+  description: The port where your board is connected to your Home Assistant host. It is recommended to use the `by-id` reference (instead of numerical like `/dev/ttyACM0` or `/dev/ttyUSB0`) since these will never change after a reboot. If you are using Home Assistant Operating System, you can find a list of connected serial devices in the Hardware dialog on the {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} panel.
   required: true
   type: string
 serial_baud_rate:

source/_integrations/zha.markdown

@@ -141,7 +141,7 @@ radio type. In the pop-up:
 Most devices need at the very least the serial device path, like `/dev/ttyUSB0`, but it is recommended to use
 device path from `/dev/serial/by-id` folder,
 e.g., `/dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C0F003D3-if01-port0`  
-A list of available device paths can be found in **Supervisor** > **System** > **Host System** > **dot menu** > **Hardware**.
+A list of available device paths can be found in {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} > **Host** > **dot menu** > **Hardware**.
 
 Press `Submit`. The success dialog will appear or an error will be displayed in the popup. An error is likely if Home Assistant can't access the USB device or your device is not up to date. Refer to [Troubleshooting](#troubleshooting) below for more information.
 

source/_integrations/zwave.markdown

@@ -427,7 +427,7 @@ The first run after adding a device is when the `zwave` integration will take ti
 
 You do not need to install any software to use Z-Wave.
 
-If the path of `/dev/ttyACM0` doesn't work, look in the *System* section of the *Supervisor* menu. There you'll find a *Hardware* button which will list all the hardware found.
+If the path of `/dev/ttyACM0` doesn't work, look in {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %}. There you'll find a *Hardware* button which will list all the hardware found.
 
 You can also check what hardware has been found using the [`ha` command](/hassio/commandline/#hardware):
 

source/_integrations/zwave_js.markdown

@@ -41,7 +41,7 @@ Please review the limitations [below](/integrations/zwave_js/#current-limitation
 
 ## Quick start (Home Assistant including Supervisor)
 
-To add Z-Wave JS to your installation, plug the Z-Wave stick into the device that runs Home Assistant. Then Go to Configuration >> Integrations in the UI. Click the "Add integration" button in the bottom right and from the list of integrations, select "Z-Wave JS" and follow the instructions shown.
+To add Z-Wave JS to your installation, plug the Z-Wave stick into the device that runs Home Assistant. Then Go to {% my integrations title="Configuration > Devices & Services" %} in the UI. Click the "Add integration" button in the bottom right and from the list of integrations, select "Z-Wave JS" and follow the instructions shown.
 
 Note: A new network key is automatically generated for you. If this Z-Wave stick has already paired with secure devices, you need to enter the previously used network key. Make sure that you keep a backup of this key in a safe place in case you need to move your Z-Wave stick to another device.
 

source/addons/index.html

@@ -11,7 +11,7 @@ regenerate: false
 <p>
   This can be running an application that Home Assistant can integrate with
     (like an MQTT broker) or to share the configuration via Samba for easy editing
-    from other computers. Add-ons can be configured via the Supervisor panel in Home
+    from other computers. Add-ons can be configured via the {% my supervisor title="Configuration > Add-ons & Backups" %} panel in Home
     Assistant.
 </p>
 
@@ -21,7 +21,7 @@ regenerate: false
 </p>
 
 <p>
-  To install add-ons, navigate to the Supervisor panel in your Home Assistant
+  To install add-ons, navigate to the {% my supervisor title="Configuration > Add-ons & Backups" %} panel in your Home Assistant
     frontend, and click on the "Add-on store" tab. All add-ons, including their documentation, are available right from the store.
     Some advanced add-ons will only be visible after you opt-in to "Advanced Mode" which can be changed on your user profile page.
     Click on an add-on you are interested in, to read the documentation or to install the add-on.

source/getting-started/configuration.markdown

@@ -11,11 +11,11 @@ The steps below do not apply to Home Assistant Core installations, for those typ
 
 </div>
 
-We are going to help you make your first changes to `configuration.yaml`. To do this, we are going to install an add-on from the Home Assistant add-on store: the File editor. To get to the add-on store, click on the menu icon in the top left, then click on Supervisor. On the new page, open the add-on store tab.
+We are going to help you make your first changes to `configuration.yaml`. To do this, we are going to install an add-on from the Home Assistant add-on store: the File editor. To get to the add-on store, click on the menu icon in the top left, then open {% my supervisor title="Configuration > Add-ons & Backups" %}. On the new page, open the add-on store tab.
 
 <p class='img'>
-<img src='/images/hassio/screenshots/main_panel_addon_store.png' />
-From the Supervisor main panel, open the add-on store.
+<img src='/images/hassio/screenshots/dashboard.png' />
+From the {% my supervisor title="Configuration > Add-ons & Backups" %} panel, open the add-on store.
 </p>
 
 Under the "Official add-ons" section you will find the File editor add-on.

source/more-info/dockerhub-rate-limit.markdown

@@ -22,8 +22,8 @@ _If you do not have a Docker Hub account [you can create one here][dockerhub-sig
 To use your Docker Hub credentials with the Supervisor:
 
 - You need to have the advanced user toggle enabled in your user profile setting.
-- Go to the Supervisor panel in the Home Assistant UI.
-- Next, to the "Add-on Store" tab.
+- Go to the {% my supervisor title="Configuration > Add-ons & Backups" %} in the Home Assistant UI.
+- Click on "Add-on Store".
 - Click the three dots in the top right corner of the screen, and select "Registries".
 
 In the dialog that opens up, click on "Add new registry" and enter `hub.docker.com` as the registry followed by your credentials:

source/more-info/free-space.markdown

@@ -24,7 +24,7 @@ the database, and even change how long it stores the data
 
 ## Delete old backups
 
-Open the Home Assistant UI and go to "Supervisor" in the sidebar, and then to
+Open the Home Assistant UI and go to {% my supervisor title="Configuration > Add-ons & Backups" %}, and then to
 the "Backups" tab, here you will see all your backups, these can be
 downloaded and placed somewhere safe. When you have done that, you can delete
 them in the UI and it will free up some space for you.
@@ -33,8 +33,8 @@ them in the UI and it will free up some space for you.
 
 Add-ons can take a lot of space, not just the add-on itself but also their data.
 
-Open the Home Assistant UI and go to "Supervisor" in the sidebar, you will be
-on the "Dashboard" tab when you click on the "Supervisor", here you will see
+Open the Home Assistant UI and go to {% my supervisor title="Configuration > Add-ons & Backups" %} in the sidebar, you will be
+on the "Dashboard" tab when you click on {% my supervisor title="Configuration > Add-ons & Backups" %}, here you will see
 all your installed add-ons, maybe you have some that you no longer use, if
 you do those can be uninstalled to free up some space.
 

source/more-info/local-media/add-media.markdown

@@ -15,7 +15,7 @@ If you are running Home Assistant OS or Supervised, you can access your
 (automatically) created media folder using the Samba add-on.
 
 If you haven't installed the Samba add-on yet, you can do so by browsing to
-the Supervisor panel by clicking "Supervisor" in the sidebar. Next, click on
+the {% my supervisor title="Configuration > Add-ons & Backups" %} panel. Next, click on
 the "Add-on store" tab and search for "Samba" and click on it.
 
 On the Samba add-on page, you can find a tab called "Documentation" with

source/more-info/unhealthy/setup.markdown

@@ -12,7 +12,7 @@ This happens when any of the setup tasks fails to complete, this can be due to t
 If the issue is related to DBUS, you will see an unsupported message about that as well; You can have a look [here][DBUS] on how to resolve that.
 
 If DBUS is not the problem, the first thing you should try is to restart the Supervisor.
-This can be done from the "System" tab in the Supervisor panel. On the card for "Supervisor", there is a button to restart the Supervisor.
+This can be done from {% my supervisor_logs title="Configuration > Add-ons & Backups" > System" %}. On the card for "Supervisor", there is a button to restart the Supervisor.
 
 This can also be done with the CLI, by running the following command:
 
@@ -23,6 +23,6 @@ ha supervisor restart
 If this does not help, you can try to reboot the host.
 If you are running Home Assistant Operating System, this can be done from the "System" tab in the Supervisor panel. On the card for "Host System", there is a button to reboot the host.
 
-To help us make the setup more robust, please enable the sharing of diagnostics and crash logs on the "System" tab in the Supervisor panel.
+To help us make the setup more robust, please enable the sharing of diagnostics and crash logs on the {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} panel.
 
 [DBUS]: /more-info/unsupported/dbus

source/more-info/unhealthy/supervisor.markdown

@@ -9,7 +9,7 @@ This can happen when there was a network issue during the startup of the Supervi
 
 ## The solution
 
-Manually update the Supervisor. This can be done from the "System" tab in the Supervisor panel. On the card for "Supervisor", there is a button to update the Supervisor.
+Manually update the Supervisor. This can be done from the {% my configuration title="Configuration" %} panel. On the card for "Supervisor", there is a button to update the Supervisor.
 
 This can also be done with the CLI, by running the following command:
 ```bash

source/more-info/unsupported/docker_configuration.markdown

@@ -12,7 +12,7 @@ needs to be set to `overlay2`.
 
 ## The solution
 
-If you are running an older version of our Home Assistant OS, update it to the latest version in the Supervisor panel.
+If you are running an older version of our Home Assistant OS, update it to the latest version in the {% my configuration title="Configuration" %} panel.
 
 If you are running Home Assistant Supervised, you need to modify the Docker daemon
 configuration on the host. The configuration is located at `/etc/docker/daemon.json`.

source/more-info/unsupported/docker_version.markdown

@@ -17,7 +17,7 @@ before we publish a version that will require you to upgrade Docker.
 ## The solution
 
 If you are running an older version of our Home Assistant OS, update it the
-supervisor panel.
+{% my configuration title="Configuration" %} panel.
 
 If this is not our Home Assistant OS, you need to manually update Docker on your
 host for instructions on how to do that, check the official

source/more-info/unsupported/privileged.markdown

@@ -11,7 +11,7 @@ to be able to do everything it needs to do.
 ## The solution
 
 If you are running an older version of our Home Assistant OS, update it in the
-supervisor panel.
+{% my configuration title="Configuration" %} panel.
 
 If this is not our Home Assistant OS, you need to re-run our
 [convenience installation script](https://github.com/home-assistant/supervised-installer).