Update: remove Core- and Supervised-specific steps (#39221)

This commit is contained in:
c0ffeeca7 2025-05-26 13:15:09 +02:00 committed by GitHub
parent 9f7f68fa8b
commit 10b8d870bc
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -3,12 +3,9 @@ Best practice for updating Home Assistant Core:
1. [Back up your installation](/common-tasks/general/#backups) and store the backup and the [backup emergency kit](/more-info/backup-emergency-kit/) somewhere safe.
- This ensures that you can [restore your installation from backup](/common-tasks/general/#restoring-a-backup) if needed.
2. Check the release notes for backward-incompatible changes on [Home Assistant release notes](/blog/categories/core/). Be sure to check all release notes between the version you are running and the one you are upgrading to. Use the search function in your browser (`CTRL + f` / `CMD + f`) and search for **Backward-incompatible changes**.
3. Update Home Assistant.
4. Review persistent notifications and log to see if there are any issues with your configuration that need to be addressed.
3. To update Home Assistant Core, choose one of the following options.
{% if page.installation == "os" or page.installation == "supervised" %}
To update Home Assistant Core when you run Home Assistant {{ page.installation_name }} you have 2 options.
{% if page.installation == "os" %}
{% tabbed_block %}
@ -60,28 +57,6 @@ To update Home Assistant Core when you run Home Assistant {{ page.installation_n
{% endtabbed_block %}
{% elsif page.installation == "core" %}
1. Stop the Home Assistant service.
2. Switch to the user that is running Home Assistant
```bash
sudo -u homeassistant -H -s
```
3. Activate the virtual environment that Home Assistant is running in
```bash
source /srv/homeassistant/bin/activate
```
4. Download and install the new version
```bash
pip3 install --upgrade homeassistant
```
5. When that is complete start the service again for it to use the new files.
{% endif %}
4. Check if there are any repair issues and check the logs to see if there are any issues with your configuration that need to be addressed.