Skip to content

Commit fa294d4

Browse files
agnersCopilotc0ffeeca7
authored
Document unsupported reason 'home_assistant_core_version' (#40914)
Co-authored-by: Copilot <[email protected]> Co-authored-by: c0ffeeca7 <[email protected]>
1 parent 8c8b2c8 commit fa294d4

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
title: "Home Assistant Core version"
3+
description: "More information on why Home Assistant Core version marks the installation as unsupported."
4+
---
5+
6+
## The issue
7+
8+
Supervisor considers Home Assistant Core versions older than 24 months (approximately 24 releases) as unsupported.
9+
It is strongly recommend to keeping Home Assistant Core updated to the latest version.
10+
At a minimum, update within 6 months (6 release cycles) to ensure you don't miss
11+
automatic YAML integration migrations. Migration code that converts YAML-based
12+
integrations to modern UI-based configuration is only available for 6 months
13+
after deprecation, which corresponds to 6 Home Assistant Core releases.
14+
15+
On installations using an unsupported Home Assistant Core release, the
16+
Supervisor stops refreshing its update information. This means you will no
17+
longer receive updates for any component, including Home Assistant Core or
18+
Add-on updates.
19+
20+
## The solution
21+
22+
1. Since you've not updated your system in a while, it is recommended to
23+
[create a backup](/common-tasks/general/#backups) before updating your system.
24+
- Make sure to download the backup or store it in a remote location.
25+
26+
2. Update your Home Assistant Core version.
27+
- Go to {% my updates title="**System** > **Updates**" %} to update Home Assistant Core.
28+
- If you don't see the update, you may have skipped it in the past. To see
29+
previously skipped updates, select the three dots {% icon "mdi:dots-vertical" %}
30+
and enable skipped updates.
31+
32+
- If you're significantly behind and have YAML-based integrations that need
33+
migration, update in increments of no more than 6 releases at a time
34+
(for example, from Home Assistant Core 2024.2 to 2024.8, then to 2025.2).
35+
- This ensures automatic migrations can run properly during each update.
36+
- You can use the Home Assistant CLI to update to a [specific Home Assistant Core version](/common-tasks/os/#home-assistant-versions).

0 commit comments

Comments
 (0)