Skip to content

Conversation

@agners
Copy link
Member

@agners agners commented Nov 5, 2025

Proposed change

The Supervisor gains a new unsupported flag "system_architecture" which marks systems running on the deprecated architectures (i386, armhf and armv7) as unsupported. Add documentation about this new flag to the unsupported system architecture page.

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

The Supervisor gains a new unsupported flag "system_architecture" which
marks systems running on the deprecated architectures (`i386`, `armhf`
and `armv7`) as unsupported. Add documentation about this new flag to
the unsupported system architecture page.
Copilot AI review requested due to automatic review settings November 5, 2025 08:55
@home-assistant home-assistant bot added current This PR goes into the current branch has-parent This PR has a parent PR in another repo in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch labels Nov 5, 2025
@home-assistant
Copy link

home-assistant bot commented Nov 5, 2025

It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the next branch. Please change the target branch of this PR to next and rebase if needed.

@netlify
Copy link

netlify bot commented Nov 5, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit c65730d
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/690b2594b85dd900081624b1
😎 Deploy Preview https://deploy-preview-41618--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds a new documentation page explaining why certain 32-bit system architectures (i386, armhf, and armv7) are marked as unsupported by Home Assistant Supervisor, and provides guidance on migrating to supported 64-bit hardware.

Key changes:

  • Documents the sunset of 32-bit architectures announced in May 2025
  • Explains the impact on updates for unsupported architectures
  • Provides migration steps using backup and restore

Comment on lines +8 to +9
Supervisor considers `i386`, `armhf` and `armv7` (all 32-bit system architectures)
as unsupported. Home Assistant announced sunset of these architectures in May 2025
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Supervisor considers `i386`, `armhf` and `armv7` (all 32-bit system architectures)
as unsupported. Home Assistant announced sunset of these architectures in May 2025
Supervisor considers `i386`, `armhf`, and `armv7` (all 32-bit system architectures)
as unsupported. Home Assistant announced the sunset of these architectures in May 2025

Comment on lines +11 to +13
On these system architectures 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.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
On these system architectures 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.
On these system architectures, 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.

Comment on lines +17 to +19
You'll be able to continue to use the system as is, but we recommend to move your
Home Assistant installation onto supported hardware. This makes sure that you'll
continue to receive software updates, including security updates.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
You'll be able to continue to use the system as is, but we recommend to move your
Home Assistant installation onto supported hardware. This makes sure that you'll
continue to receive software updates, including security updates.
You can continue to use the system as is, but it is recommended to move your
Home Assistant installation onto supported hardware. This makes sure that you'll
continue to receive software updates, including security updates.

Comment on lines +21 to +25
To migrate to a supported architecture, [create a full backup](/common-tasks/general/#backups)
and download it. Install Home Assistant OS on supported 64-bit hardware. Use the
[restore from backup feature during on-boarding](https://www.home-assistant.io/getting-started/onboarding/) (Option 2).
If you use a Raspberry Pi 3 or Raspberry Pi 4, you can install the 64-bit variants
of Home Assistant OS. See the [Raspberry Pi installation documentation](https://www.home-assistant.io/installation/raspberrypi/) for detailed instructions.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
To migrate to a supported architecture, [create a full backup](/common-tasks/general/#backups)
and download it. Install Home Assistant OS on supported 64-bit hardware. Use the
[restore from backup feature during on-boarding](https://www.home-assistant.io/getting-started/onboarding/) (Option 2).
If you use a Raspberry Pi 3 or Raspberry Pi 4, you can install the 64-bit variants
of Home Assistant OS. See the [Raspberry Pi installation documentation](https://www.home-assistant.io/installation/raspberrypi/) for detailed instructions.
1. To migrate to a supported architecture, [create a full backup](/common-tasks/general/#backups)
and download it.
2. Install Home Assistant OS on supported 64-bit hardware.
- Use the [restore from backup feature during onboarding](https://www.home-assistant.io/getting-started/onboarding/) (Option 2).
- If you use a Raspberry Pi 3 or Raspberry Pi 4, you can install the 64-bit variants
of Home Assistant OS.
- See the [Raspberry Pi installation documentation](https://www.home-assistant.io/installation/raspberrypi/) for detailed instructions.

I think numbered steps would be helpful here.

@home-assistant
Copy link

home-assistant bot commented Nov 6, 2025

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@home-assistant home-assistant bot marked this pull request as draft November 6, 2025 06:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

current This PR goes into the current branch has-parent This PR has a parent PR in another repo in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants