Home Assistant OS 17.1

[sairon]

Changes

This release fixes issues discovered in 17.0. Bug in Containerd causing excessive logging has been fixed. Compatibility issue with the latest OpenCCU add-on has been resolved by updating the generic_raw_uart driver for glibc 2.42+. Linux kernel of all targets has been updated to the latest stable version. All users are encouraged to upgrade.

Note that Home Assistant OS 17.1 uses Docker Containerd snapshotter by default, optional migration steps for existing installations are available in the 17.0 release notes.

Home Assistant Operating System

• Add RAUC patch to annotate all messages with SYSLOG_IDENTIFIER (Add RAUC patch to annotate all messages with SYSLOG_IDENTIFIER #4510) @sairon
• Backport GLib patch adding SYSLOG_IDENTIFIER to logging messages (Backport GLib patch adding SYSLOG_IDENTIFIER to logging messages #4506) @sairon
• Add generic_raw_uart patch for termios2/glibc 2.42+ compatibility (Add generic_raw_uart patch for termios2/glibc 2.42+ compatibility #4504) @jens-maus
• Bump Containerd to v2.2.1 to fix possible log spam (Bump Containerd to v2.2.1 to fix possible log spam #4502) @sairon
• Bump Buildroot to 2025.02.10 (Bump Buildroot to 2025.02.10 #4499) @sairon

Home Assistant Green

• Remove dropped R8712U from Rockchip configs (Remove dropped R8712U from Rockchip configs #4511) @sairon
• Linux: Update kernel to 6.12.67 (Linux: Update kernel to 6.12.67 #4505) @sairon

Open Virtual Appliance

• Linux: Update kernel to 6.12.67 (Linux: Update kernel to 6.12.67 #4505) @sairon

Generic x86-64

• Linux: Update kernel to 6.12.67 (Linux: Update kernel to 6.12.67 #4505) @sairon

Hardkernel ODROID

• Remove dropped R8712U from Rockchip configs (Remove dropped R8712U from Rockchip configs #4511) @sairon
• Linux: Update kernel to 6.12.67 (Linux: Update kernel to 6.12.67 #4505) @sairon

Khadas VIM Series

• Linux: Update kernel to 6.12.67 (Linux: Update kernel to 6.12.67 #4505) @sairon

Generic aarch64

• Linux: Update kernel to 6.12.67 (Linux: Update kernel to 6.12.67 #4505) @sairon

Dependencies

• Bump actions/setup-python from 6.1.0 to 6.2.0 (Bump actions/setup-python from 6.1.0 to 6.2.0 #4507) @dependabot[bot]
• Bump actions/checkout from 6.0.1 to 6.0.2 (Bump actions/checkout from 6.0.1 to 6.0.2 #4508) @dependabot[bot]
• Bump release-drafter/release-drafter from 6.1.0 to 6.2.0 (Bump release-drafter/release-drafter from 6.1.0 to 6.2.0 #4509) @dependabot[bot]
• Bump actions/cache from 5.0.1 to 5.0.2 (Bump actions/cache from 5.0.1 to 5.0.2 #4489) @dependabot[bot]

---

This discussion was created from the release Home Assistant OS 17.1.

[carvalr]

After updating my instance running on VirtualBox, the CLI is not loading anymore. This is the second time in recent time with me and I had to recover from backup and lose the recent changes.

[uschindler]

Maybe related to that? #4534

[brandonee916]

v17.0 installed correctly on my Raspberry Pi 5. However v17.1 fails to install and reverts back to v17.0 after a significant delay.

[FredAloneForEver]

I just did this morning, from 17.0 to 17.1 with RPi5.
No problems detected so far

[TRON4R]

After uprading from 16.3 to 17.1, HA's connection to my Synology Backup folder, where I have Home Assistant store all my local backups, has stopped working. Looks like a problem with the mountd.

[TRON4R]

Ok. Apparently the resolution of hostnames has changed in that area and a full domain is now required even for local hosts instead of just using the hostname without extension. The logs led the way...

[TRON4R]

That has remained the only issue so far. And I have 2063 entities in my system.
So from my perspective, upgrading from 16.3 to 17.1 seems doable and worth taking the risk.

I have NOT manually changed the containerd to snapshotter yet, though. And I probably won't for the time being.

[richie510]

Upgraded from 17.0 to 17.1. Using x86-64 in Proxmox. No issues, no hiccups.

[CowboyBootsSP]

Sometimes I get some network errors displayed at my client OS screen, starting with something I guess could be milliseconds since start. Would it be more readable and useful if it could display the time that the error occurred? I know that it's a thing of minor importance but it annoys me since I started to use the OS. Or, maybe, it's just me...

[EDelsman]

I do not witness any problems, but do see increased and rising memory use immediately after installing 17.1 at 11:00 on my NUC with N100 processor and 16GB. No significant changes after restarting all addons, restarting HA or rebooting the entire host.

[illright]

Raspberry Pi 4, upgraded from 17.0 to 17.1 quickly and smoothly

[jimrkerry]

Updated quickly with no problems from 17.0 to 17.1 on x86_64.

Installation method: Home Assistant OS
Core: 2026.1.3
Supervisor: 2026.02.1
Operating System: 17.1
Frontend: 20260107.2

[hemaris-8b]

HA Yellow/CM5 with 1TB NVME M.2 Samsung 990 EVO SSD. Upgraded smoothly from 16.3 to 17.1, no issue.

[Frankster-NL]

After the update to 17.1 my cpu utilization became very stable and very low. Great work! Running HAOS on a NUC with i5 processor. Can be considered as a power user with over 300 devices.

[jhalldn]

Im using RPI5 with SSD, booting from SD. I ran upgrade 17.1 this morning without problems. Hopefully it sticks that way. I have not run The migration command and i Will probably wait until next upgrade before. Keep up The good work!