Home Assistant OS 16.1

[sairon]

Changes

This Home Assistant OS release brings several updates and fixes for all platforms. A bug in systemd-journal-gatewayd causing high CPU usage when reading logs (e.g. Settings > Logs in the in the frontend) has been resolved. Additionally, an issue of unbootable Raspberry Pi 5 images when they are flashed from Windows has been fixed. All platforms, including Raspberry Pi, have received kernel updates to the latest stable versions. VDI images are now published for generic-aarch64 build to allow for easier resizing when used in VirtualBox on Apple silicon Macs. All users are recommended to update.

The Supervisor shipped with this Home Assistant OS version will enable IPv6 for Home Assistant Add-ons by default. Note that this does not apply to upgrades. If you want to enable IPv6, use ha docker options --enable-ipv6=true followed by a system reboot. See also home-assistant/supervisor#6029.

⚠️ Known issues

Some users have reported issues with USB-Serial converters on Home Assistant Yellow. The bug is possibly affecting also some USB-Serial converters connected to Raspberry Pi boards. In case you are affected, downgrade to OS 16.0 is recommended. See #4228 for details.

Home Assistant Operating System

• Update genimage to avoid unbootable RPi 5 images when flashed from Windows (Update genimage to avoid unbootable RPi 5 images when flashed from Windows #4199) @sairon
• Update to Docker v28.3.3 and containerd v2.1.4 (Update to Docker v28.3.3 and containerd v2.1.4 #4198) @sairon
• Fix systemd-journal-gatewayd 100% CPU issue when watching logs (Fix systemd-journal-gatewayd 100% CPU issue when watching logs #4197) @sairon
• Enable netfilter NETMAP target support in kernel (Enable netfilter NETMAP target support in kernel #4186) @sairon
• Drop experimental and ip6tables config (Drop experimental and ip6tables config #4173) @agners

Raspberry Pi

• Fix rpi-eeprom-update when device boots from NVMe (Fix rpi-eeprom-update when device boots from NVMe #4205) @sairon
• Bump to latest default FW version (2025-05-08) in rpi-eeprom-update (Bump to latest default FW version (2025-05-08) in rpi-eeprom-update #4208) @sairon
• RaspberryPi: Update kernel to 6.12.34 - stable_20250702 (RaspberryPi: Update kernel to 6.12.34 - stable_20250702 #4206) @sairon
• Update genimage to avoid unbootable RPi 5 images when flashed from Windows (Update genimage to avoid unbootable RPi 5 images when flashed from Windows #4199) @sairon

Home Assistant Yellow

• Fix rpi-eeprom-update when device boots from NVMe (Fix rpi-eeprom-update when device boots from NVMe #4205) @sairon
• Bump to latest default FW version (2025-05-08) in rpi-eeprom-update (Bump to latest default FW version (2025-05-08) in rpi-eeprom-update #4208) @sairon
• RaspberryPi: Update kernel to 6.12.34 - stable_20250702 (RaspberryPi: Update kernel to 6.12.34 - stable_20250702 #4206) @sairon

Home Assistant Green

• Linux: Update kernel to 6.12.41 (Linux: Update kernel to 6.12.41 #4200) @sairon

Open Virtual Appliance

• Linux: Update kernel to 6.12.41 (Linux: Update kernel to 6.12.41 #4200) @sairon

Generic x86-64

• Linux: Update kernel to 6.12.41 (Linux: Update kernel to 6.12.41 #4200) @sairon

Hardkernel ODROID

• Linux: Update kernel to 6.12.41 (Linux: Update kernel to 6.12.41 #4200) @sairon

ASUS Tinker

• Linux: Update kernel to 6.12.41 (Linux: Update kernel to 6.12.41 #4200) @sairon

Khadas VIM Series

• Linux: Update kernel to 6.12.41 (Linux: Update kernel to 6.12.41 #4200) @sairon

Generic aarch64

• Linux: Update kernel to 6.12.41 (Linux: Update kernel to 6.12.41 #4200) @sairon
• Enable driver for Xilinx AMS adc sensor (Enable driver for Xilinx AMS adc sensor #4192) @michalsimek
• Generate Virtual Disk Image (VDI) for aarch64 build (Generate Virtual Disk Image (VDI) for aarch64 build #4187) @sairon
• Enable Intel audio driver for virtualized sound on aarch64 (Enable Intel audio driver for virtualized sound on aarch64 #4185) @sairon

Build System

• Suppress new warnings from shellcheck v0.11.0 (Suppress new warnings from shellcheck v0.11.0 #4207) @sairon

---

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

[Anto79-ops]

There are no issues on installation and bootup on my NUC 12 (x86-64, bare-metal) with USB SkyConnect and USB Aeotec Z-Stick 7.

The system is running normally.

[keithr59]

Home Assistant Green updated from 16.0 to 16.1. All OK.

[foddy-foo]

Installed fine on my HA VM running on Proxmox. No issues seen.

[Turner-Home]

Home Assistant Yellow fails on Zigbee (Yellow Multi-PAN fails to initialize) as well as Open Thread Border Router.
Roll back to HAOS 15.2 resolves the issue.

[Picard16]

No issues with RasPi5 so far! Thanks!!

[pbenaim]

On my Generic x86-64 update don't work 😢
After pushed Update button, it look like install, reboot but I stay on V16.0 😱

[JEEMTECH]

Me pasa exactamente lo mismo. Hago la actualización desde el browser o desde el cli y hace que actualiza pero no actualiza la versión. Queda en 16.0

[pbenaim]

Same with ssh command : ha os update 😢

Say Successfuly but after reboot OS stay at 16.0 😭

[Red5Rebel]

HAOS updated from 16.0 to 16.1 on Proxmox LXC. OS and all Z-Wave & Zigbee devices running without issues.

Thanks Dev team!

[Skynetnexus]

Updated to 16.1 on a Home Assistant Blue ( Odroid ) and I lost contact with my USB attached APC UPS via Network UPS Tools addon.
NUT was saying end device could not be found.

I switched boot slots ( ha os boot-slot other ) and booted to 16.0. All good now.

➜ ~ ha os info
board: odroid-n2
boot: A
boot_slots:
A:
state: booted
status: good
version: "16.0"
B:
state: inactive
status: good
version: "16.1"
data_disk: G1J39E-0x0ed05d53
update_available: true
version: "16.0"
version_latest: "16.1"

It could be an issue with the add-on but I will stick with 16.0 for now.

[roberthawdon]

Ended up with a dead system on my RPi 5 with the message:

usb 1-1.4: 9:0: cannot get min/max values for control 2 (id 9)
repeated over and over.

I have an Argon One V5 case with their Argon Industria ZIGBEE Module installed for what it's worth.

Ended up reverting back to OS 16.0 which has mitigated the issue.

EDIT: looking at the error, it could be the USB DAC that's on the Argon One's USB board that's the culprit for me.

[kwithus]

Well, 16.1 was the burner for some of us 🫣
Brought a little bit of work to me and others, but that's software, always good for surprises, regardless how much testes before.
So no worries and many thanks to those who identified the bug and offered solutions (downgrade to 16.0 or install a patch)
However, I do have a question and suggestions.

Question first:
I have seen that a patch is available, I also can see that 16.1 is still available for installation, is this a patched version of 16.1 or will installing of this version still kill the USB connection for those affected before?
If it is not a patched version, would it better to take this offline until a patched version is available ? Otherwise other users who haven't upgraded yet might run into the same problems.

Suggestion:
I ended up downgrading to 16.0 for now, which took me some search and asking questions to other users about "how to".
As mentioned above, new software versions always have remaining risks for bugs. How about implementing an easy "on-click" solution for a downgrade to prior version, just similar to installations of integration etc. where I can choose to download prior versions.
Especially with OS this would be helpful, as the OS is not part of the regular HA Backups.
Well, maybe such an "on-click" solution is already available, if yes, may be it should be more prominent placed.

As HA is becoming more and more popular, more and more users are not really Nerds (and HA becomes more and more easy to handle for such users). For that such an easy to use downgrade option could be helpful for many of us.

[Dozi3]

Sadly still stuck on 15.8 on my R Pi 5 16gb tried 16.0 and failed with no knowledge of why and 16.1 failed saying ssl invalid and self reverted back to 15.8.

Will try taking a backup and rebuilding the nvme ssd and update this comment with the verdict!

Using HA cloud

Full hardware spec:
R Pi 5 16gb - eeprom 05-08-2025
R Pi official 256gb m.2 ssd
Argon one V5 inc m.2 hat & oled display

[DrDano]

Installed and ran with no issues on my HA VM running on KVM on Dell X64 hardware.

[pbenaim]

It's one update from 16.0 or fresh install ?

[sayzyeh]

stucked at Preparing Home Assistant

2025-08-19 00:50:32.340 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/generic-x86-64-homeassistant:2025.8.2: 404 Client Error for http+docker://localhost/v1.51/images/ghcr.io/home-assistant/generic-x86-64-homeassistant:2025.8.2/json: Not Found ("No such image: ghcr.io/home-assistant/generic-x86-64-homeassistant:2025.8.2")

[hocomadvies]

The last few updates I run into the problem that My HA system was not reachable through its normal IP-address. Only thing that help me out was a complete restore of my Proxmox VM. Now I tried again updating from 15.2 to 16.1. Apparently the update itself has been applied. But the result is that HA on the VM is stuck in some kind of loop. It is rebooting after some time. Now I think the problem is the ip4 address which seems to be no longer available? I have a reserved address for HA. Now I read above this post, that running docker options --enable-ipv6=true will make the ip6 address available. Will that be the on the same ip which I use for my ip4 than? Or will it get a different one? I'm not sure how to get things right. some screenshots attached:

[hocomadvies]

Any comments on this? I now booted form the A partition and its back up at version 15.2. So how to get this right?

[agners]

ova works here on Proxmox. What kind of network interface do you use/emulate?

After an update try, when there is no IPv4 address, can you check if dmesg shows something relevant using:

login # (to access Linux shell)
dmesg | grep enp0s18

[hocomadvies]

OK I will try that see what it brings. What is ova ?

[hocomadvies]