Skip to content

Document unsupported reason 'home_assistant_core_version' #40914

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Sep 23, 2025
Merged

Document unsupported reason 'home_assistant_core_version' #40914

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
63ca218
Document unsupported reason 'home_assistant_core_version'
agners Sep 18, 2025
ac5e856
Reword and add link to specific version update instructions
agners Sep 18, 2025
e1f302f
Update source/more-info/unsupported/home_assistant_core_version.markdown
agners Sep 18, 2025
06b1055
tweak
c0ffeeca7 Sep 18, 2025
925474e
Apply suggestions from code review
agners Sep 23, 2025
7a194db
Cosmetics
agners Sep 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions source/more-info/unsupported/home_assistant_core_version.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
---
title: "Home Assistant Core version"
Copy link
Contributor

@c0ffeeca7 c0ffeeca7 Sep 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Home Assistant Core version is a very generic title. Can we add the symptom in the title? Or is there a reason to just mention that it's something about the Core version?

This page seems like a troubleshooter to me.
We could use the Symptom, Description (or Cause), Resolution structure here.

Copy link
Member Author

@agners agners Sep 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These more-info unsupported come all in the same format, e.g.

https://www.home-assistant.io/more-info/unsupported/network_manager
https://www.home-assistant.io/more-info/unsupported/os_version

In a way the breadcrums above say that its about unsupported, but maybe that is not really clear enough. I think if we want to change then we should all at once, e.g. prefix with Unsupported: ... Or Unsupported - ...

description: "More information on why Home Assistant Core version marks the installation as unsupported."
---

## The issue

Supervisor considers Home Assistant Core versions older than 24 months (approximately 24 releases) as unsupported.
It is strongly recommend to keeping Home Assistant Core updated to the latest version.
At a minimum, update within 6 months (6 release cycles) to ensure you don't miss
automatic YAML integration migrations. Migration code that converts YAML-based
integrations to modern UI-based configuration is only available for 6 months
after deprecation, which corresponds to 6 Home Assistant Core releases.

On installations using an unsupported Home Assistant Core release, the
Supervisor stops refreshing its update information. This means you will no
longer receive updates for any component, including Home Assistant Core or
Add-on updates.

## The solution

1. Since you've not updated your system in a while, it is recommended to
[create a backup](/common-tasks/general/#backups) before updating your system.
- Make sure to download the backup or store it in a remote location.

2. Update your Home Assistant Core version.
- Go to {% my updates title="**System** > **Updates**" %} to update Home Assistant Core.
- If you don't see the update, you may have skipped it in the past. To see
previously skipped updates, select the three dots {% icon "mdi:dots-vertical" %}
and enable skipped updates.

- If you're significantly behind and have YAML-based integrations that need
migration, update in increments of no more than 6 releases at a time
(for example, from Home Assistant Core 2024.2 to 2024.8, then to 2025.2).
- This ensures automatic migrations can run properly during each update.
- You can use the Home Assistant CLI to update to a [specific Home Assistant Core version](/common-tasks/os/#home-assistant-versions).