|
| 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 older than two years as unsupported. |
| 9 | +We generally recommend to always update to the latest Home Assistant Core, or |
| 10 | +at least update within 6 months to the latest release to not miss out on |
| 11 | +automatic migration of YAML integration (the migration code to migrate YAML |
| 12 | +integration to regular config entry based integration is available for 6 |
| 13 | +months, today this is for 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 | +Since you've not updated your system in a while, we recommend to [create a backup](/common-tasks/general/#backups) |
| 23 | +before updating your system. Make sure to download the backup or store it at |
| 24 | +a remote location. |
| 25 | + |
| 26 | +To resolve this issue, update your Home Assistant Core version. Go to |
| 27 | +{% 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 | +enabling skipped updates. |
| 31 | + |
| 32 | +If you would like to take advantage of YAML integration migration, update 6 |
| 33 | +releases at a time (e.g. from Home Assistant Core 2024.2 to 2024.8). You can |
| 34 | +use the HA CLI to update to a specific version. |
0 commit comments