Advanced installation methods: rename, as they are no longer advanced… (#39171)

This commit is contained in:
c0ffeeca7 2025-05-23 15:24:56 +02:00 committed by GitHub
parent 412806cd8a
commit 0b0170c5c4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
8 changed files with 13 additions and 13 deletions

View File

@ -79,7 +79,7 @@
Home Assistant has built-in functionality to create files containing a copy
of your configuration. This can be used to restore your Home Assistant as
well as migrate to a new system. The backup feature is available for all
[installation types](/installation/#advanced-installation-methods).
[installation types](/installation/#about-installation-methods).
link: /common-tasks/general/#backups
aliases:
- backups
@ -307,7 +307,7 @@
Home Assistant Container is a standalone container-based installation of
Home Assistant Core. Any [OCI](https://opencontainers.org/) compatible
runtime can be used, but the documentation focus is on Docker.
link: /installation/#advanced-installation-methods
link: /installation/#about-installation-methods
- term: Home Assistant Core
definition: >-
Home Assistant Core is the Python program at the heart of Home Assistant. It

View File

@ -31,7 +31,7 @@ Example of a configuration.yaml file, accessed using the File editor add-on on a
## Editing `configuration.yaml`
How you edit your `configuration.yaml` file depends on your editor preferences and the [installation method](/installation/#advanced-installation-methods) you used to set up Home Assistant. Follow these steps:
How you edit your `configuration.yaml` file depends on your editor preferences and the [installation method](/installation/#about-installation-methods) you used to set up Home Assistant. Follow these steps:
1. [Set up file access](#to-set-up-access-to-the-files-and-prepare-an-editor).
2. [Locate the config directory](#to-find-the-configuration-directory).
@ -41,9 +41,9 @@ How you edit your `configuration.yaml` file depends on your editor preferences a
### To set up access to the files and prepare an editor
Before you can edit a file, you need to know how to access files in Home Assistant and setup an editor.
File access depends on your [installation method](/installation/#advanced-installation-methods). If you use {% term "Home Assistant Operating System" %} or {% term "Home Assistant Supervised" %}, you can use editor add-ons, for example, but not if you use {% term "Home Assistant Core" %} or {% term "Home Assistant Container" %}.
File access depends on your [installation method](/installation/#about-installation-methods). If you use {% term "Home Assistant Operating System" %} or {% term "Home Assistant Supervised" %}, you can use editor add-ons, for example, but not if you use {% term "Home Assistant Core" %} or {% term "Home Assistant Container" %}.
To set up file access, follow the steps for your [installation method](/installation/#advanced-installation-methods):
To set up file access, follow the steps for your [installation method](/installation/#about-installation-methods):
- [Configure file access on the Operating System](/common-tasks/os/#configuring-access-to-files):
- If you are unsure which option to choose, install the [file editor add-on](/common-tasks/os/#installing-and-using-the-file-editor-add-on).
@ -80,7 +80,7 @@ If you have watched any videos about setting up Home Assistant using `configurat
After changing configuration or automation files, you can check if the configuration is valid. A configuration check is also applied automatically when you reload the configuration or when you restart Home Assistant.
The method for running a configuration check depends on your [installation type](/installation/#advanced-installation-methods). Check the common tasks for your installation type:
The method for running a configuration check depends on your [installation type](/installation/#about-installation-methods). Check the common tasks for your installation type:
- [Configuration check on Operating System](/common-tasks/os/#configuration-check)
- [Configuration check on Supervised](/common-tasks/supervised/#configuration-check)

View File

@ -4,7 +4,7 @@
These below instructions are for an installation of {% term "Home Assistant Container" %} running in your own container environment, which you manage yourself. Any [OCI](https://opencontainers.org/) compatible runtime can be used, however this guide will focus on installing it with Docker.
{% note %}
This installation method **does not have access to add-ons**. If you want to use add-ons, you need to use another installation method. The recommended method is {% term "Home Assistant Operating System" %}. Checkout the [overview table of installation types](https://www.home-assistant.io/installation/#advanced-installation-methods) to see the differences.
This installation method **does not have access to add-ons**. If you want to use add-ons, you need to use another installation method. The recommended method is {% term "Home Assistant Operating System" %}. Checkout the [overview table of installation types](https://www.home-assistant.io/installation/#about-installation-methods) to see the differences.
{% endnote %}
{% important %}

View File

@ -25,7 +25,7 @@ related:
title: backup emergency kit
---
The **Backup** {% term integration %} is used by all [installation types](/installation/#advanced-installation-methods) to create and restore backups.
The **Backup** {% term integration %} is used by all [installation types](/installation/#about-installation-methods) to create and restore backups.
To learn how to create and restore a backup, refer to the backup section under [common tasks](/common-tasks/general/#backups).
@ -59,7 +59,7 @@ action: backup.create_automatic
The {% my developer_call_service service="backup.create" %} action can be used
to create a backup of your Home Assistant instance.
- This action is only available in [core and container installations](/installation/#advanced-installation-methods).
- This action is only available in [core and container installations](/installation/#about-installation-methods).
- The action has no additional options or parameters.
- The backup will only be saved on the local storage.
- The backup created with `backup.create` always includes the database.

View File

@ -89,7 +89,7 @@ To run a Z-Wave network, you need the following elements:
If you are running {% term "Home Assistant Operating System" %} or {% term "Home Assistant Supervised" %}, the easiest way to get started is by using the built-in Z-Wave JS add-on in Home Assistant.
For other ways to setup a Z-Wave server, refer to the [advanced installation instructions](#advanced-installation-instructions).
For other ways to setup a Z-Wave server, refer to the [advanced installation instructions](#about-installation-instructions).
Follow these steps:

View File

@ -48,7 +48,7 @@ The [Open Home Foundation Matter Server](https://csa-iot.org/csa_product/open-ho
If you're confused why we certified both Home Assistant and Open Home Foundation Matter Server, there are a couple of legal/procedural reasons, but it comes with some useful benefits. We certified the server as a standalone component to allow any project to use it. Each project that uses it, including Home Assistant, will have to go through a certification process to acknowledge that it uses a certified component as a "User Interface Component". Certification for the Open Home Foundation Matter Server means it properly connects and communicates with other Matter devices, while certification for Home Assistant is about being able to display the Matter trademark.
This separation is important because it means that we won't need to go through recertification every time we update Home Assistant. This way we can keep the Matter-related backend isolated in both a software and certification sense. This is also why we will need to continue to have the Open Home Foundation Matter Server as an add-on, and it cannot be built into [Home Assistant Core](/installation/#advanced-installation-methods).
This separation is important because it means that we won't need to go through recertification every time we update Home Assistant. This way we can keep the Matter-related backend isolated in both a software and certification sense. This is also why we will need to continue to have the Open Home Foundation Matter Server as an add-on, and it cannot be built into [Home Assistant Core](/installation/#about-installation-methods).
## The road to certification

View File

@ -254,7 +254,7 @@ toc: true
<span class="label expert">Expert</span>
<h2>Advanced installation methods</h2>
<h2>About installation methods</h2>
<p>
Home Assistant offers two different installation methods:
</p>

View File

@ -11,7 +11,7 @@ Included section for this page is located under source/_includes/installation
{% assign board = "Raspberry Pi" %}
{% assign installation_media = "SD card" %}
While we recommend Home Assistant OS, there are also alternative ways to install Home Assistant. Before you continue, be aware of the limitations and differences compared to Home Assistant OS. You can find more information on the [installation page](/installation/#advanced-installation-methods). Most notably,
While we recommend Home Assistant OS, there are also alternative ways to install Home Assistant. Before you continue, be aware of the limitations and differences compared to Home Assistant OS. You can find more information on the [installation page](/installation/#about-installation-methods). Most notably,
<a href="/addons">add-ons</a> are only available with the Home Assistant Operating System.
{% include installation/container.md %}