Home Assistant OS 16.3

[sairon]

Changes

This release brings updates and fixes for all platforms. Linux kernel of all targets including Raspberry Pi-based boards has been updated to the latest stable version. Bug in Docker causing slow or compeletely stalled system startup has been identified and fixed. Compatibility issues of the generic x86-64 build with latest Intel Ultra platforms have been resolved and several system components updated. The default console now shows more helpful messages when Home Assistant services don't start in time. All users are recommended to update.

Home Assistant Operating System

• Fix Docker issue that could cause slow system startup (Fix Docker issue that could cause slow system startup #4369) @sairon
• Bump Buildroot to 2025.02.7 (Bump buildroot to 2025.02.7 #4351) @sairon
• Bump rpi-rf-mod dt overlay to latest version (1.13.3) (Bump rpi-rf-mod dt overlay to latest version (1.13.3) #4349) @jens-maus
• Improve UX of HA CLI wrapper and emergency console (Improve UX of HA CLI wrapper and emergency console #4326) @sairon
• Enable HID multitouch support in kernel (Enable HID multitouch support in kernel #4298) @puterboy
• Update HOME_URL in os-release metadata (Update HOME_URL in os-release metadata #4299) @sairon
• Bump Buildroot to 2025.02.6 (Bump Buildroot to 2025.02.6 #4297) @sairon
• Start Supervisor container with its cidfile mounted to /run/cid (Start Supervisor container with its cidfile mounted to /run/cid #4276) @sairon
• Enable Pressure Stall Information PSI (Enable Pressure Stall Information PSI #4279) @ajfriesen

Raspberry Pi

• Disable UAS via usb-storage.quirks on RPi for JMicron JMS583Gen 2 to PCIe Gen3x2 Bridge (Disable UAS via usb-storage.quirks on RPi for JMicron JMS583Gen 2 to PCIe Gen3x2 Bridge #4366) @vichle
• RaspberryPi: Update kernel to 6.12.47 - stable_20250916 (RaspberryPi: Update kernel to 6.12.47 - stable_20250916  #4327) @sairon

Home Assistant Yellow

• Disable UAS via usb-storage.quirks on RPi for JMicron JMS583Gen 2 to PCIe Gen3x2 Bridge (Disable UAS via usb-storage.quirks on RPi for JMicron JMS583Gen 2 to PCIe Gen3x2 Bridge #4366) @vichle
• RaspberryPi: Update kernel to 6.12.47 - stable_20250916 (RaspberryPi: Update kernel to 6.12.47 - stable_20250916  #4327) @sairon

Home Assistant Green

• Linux: Update kernel to 6.12.51 (Linux: Update kernel to 6.12.51 #4343) @sairon

Open Virtual Appliance

• Enable x2APIC controller support on x86 and OVA (Enable x2APIC controller support on x86 and OVA #4342) @sairon
• Linux: Update kernel to 6.12.51 (Linux: Update kernel to 6.12.51 #4343) @sairon
• Add driver for Creative Sound Blastr X-Fi PCI cards (Add driver for Creative Sound Blastr X-Fi PCI cards #4331) @sairon
• Support Chelsio T4/T5/T6 VF in SRIOV mode (Support Chelsio T4/T5/T6 VF in SRIOV mode #4281) @servesh

Generic x86-64

• Enable x2APIC controller support on x86 and OVA (Enable x2APIC controller support on x86 and OVA #4342) @sairon
• Enable powersave CPU frequency governor (Enable powersave CPU frequency governor #4346) @agners
• Linux: Update kernel to 6.12.51 (Linux: Update kernel to 6.12.51 #4343) @sairon
• Add driver for Creative Sound Blastr X-Fi PCI cards (Add driver for Creative Sound Blastr X-Fi PCI cards #4331) @sairon

Hardkernel ODROID

• Linux: Update kernel to 6.12.51 (Linux: Update kernel to 6.12.51 #4343) @sairon

ASUS Tinker

• Linux: Update kernel to 6.12.51 (Linux: Update kernel to 6.12.51 #4343) @sairon

Khadas VIM Series

• Linux: Update kernel to 6.12.51 (Linux: Update kernel to 6.12.51 #4343) @sairon

Generic aarch64

• Linux: Update kernel to 6.12.51 (Linux: Update kernel to 6.12.51 #4343) @sairon

Build System

• Remove usage of --content-trust CLI option in Supervisor tests (Remove usage of --content-trust CLI option in Supervisor tests #4371) @sairon
• Use matching version of DinD daemon when creating hassio data partition (Use matching version of DinD daemon when creating hassio data partition #4344) @sairon
• Use original hadolint action instead of outdated fork (Use original hadolint action instead of outdated fork #4332) @sairon
• Fix build failure caused by RaspberryMatic project renaming (Fix build failure caused by RaspberryMatic project renaming #4324) @sairon
• Pin SHA for all Github Actions (Pin SHA for all Github Actions #4305) @silamon
• Implement better support for --silent flag in top-level Makefile (Implement better support for --silent flag in top-level Makefile #4292) @sairon

Dependencies

• Bump actions/stale from 10.0.0 to 10.1.0 (Bump actions/stale from 10.0.0 to 10.1.0 #4338) @dependabot[bot]
• Bump docker/login-action from 3.5.0 to 3.6.0 (Bump docker/login-action from 3.5.0 to 3.6.0 #4322) @dependabot[bot]
• Bump actions/cache from 4.2.4 to 4.3.0 (Bump actions/cache from 4.2.4 to 4.3.0 #4323) @dependabot[bot]
• Bump actions/github-script from 7 to 8 (Bump actions/github-script from 7 to 8 #4285) @dependabot[bot]
• Bump actions/setup-python from 5 to 6 (Bump actions/setup-python from 5 to 6 #4284) @dependabot[bot]
• Bump actions/stale from 9.1.0 to 10.0.0 (Bump actions/stale from 9.1.0 to 10.0.0 #4283) @dependabot[bot]

---

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

[ephirial]

The CPUfreq governor "powersave" will lock the CPU to it´s minimum clock speed. This has significant performance impact on some devices, my cpu is locked to 800 mhz with this governor.

[sairon]

The default governor should be still schedutil because CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y is set. The PR only added support for enabling the powersave governor e.g. with a cmdline option, see the PR description of #4346.

[aavdberg]

Think that the first one must be 2025.02.7 or is the 2024.02.7 correct?

[sairon]

Yes, that's indeed a typo, thanks.

[1nordlicht]

After upgrading my system deconz does not start anymore. See attached logfile.
core_deconz_2025-11-05T12-30-10.114Z.log

I just found this one:

Device '/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2190408-if00' does not exist in deCONZ (core_deconz).

I even cannot find the device attached to any USB port.

[1nordlicht]

My issue has been solved. Apparently the USB port where my deconz conbee was connected to stopped working. After moving it to another port all is fine.

[hprombex]

Dell Wyse Dx0Q, x86-64 - all ok after update

[rummin-git]

Hardkernel ODROID N2+ After upgrading, won’t start.

[Hannes-D-0815]

Same here.
After change extetnal SSD to other USB port, sytem start, but with old OS 16.2
After starting complete, I starzet OS update once again, now all is ok with new OS 16.3

[whalik]

Raspberry Pi5 won't update. I had to power reset every time to go back to initial state. It was able to upgrad the core though. Can't find error logs in SU logs.

[avegao]

One more here

[whalik]

SU_log_Pi5.txt

[brandonee916]

Same, PI5 won't boot after upgrade to 16.3. Eventually after a long period of time, pulled power and reverted back to booting with 16.2

[trex2000]

Same also with the cm5 on HA yellow. The issue happened sporadically on every version since 16.0

[trademarksteve]

Ditto for me with a Raspberry Pi 5.

[ajfriesen]

Home Assistant Blue/Hardkernel Odroid N2+ works as expected.

[keithr59]

Home Assistant Green updated from 16.2 to 16.3. All OK.

[mehtam89]

My green stopped detecting sonoff dongle (z2m). Had to downgrade.

[Juggler00]

I continue to have problems with an USB Insteon PLM (see here: #4309). Running a Yellow with CM5)

[trex2000]

[ 33.792991] F2FS-fs (nvme0n1p3): Can't find valid F2FS filesystem in 1th superblock
[ 33.800708] F2FS-fs (nvme0n1p3): Magic Mismatch, valid(0xf2f52010) - read(0x6909f1e6)
[ 33.808540] F2FS-fs (nvme0n1p3): Can't find valid F2FS filesystem in 2th superblock
[ 33.816454] erofs: (device nvme0n1p3): mounted with root inode @ nid 37.
[ 33.823171] VFS: Mounted root (erofs filesystem) readonly on device 259:3.
[ 33.830060] devtmpfs: mounted
[ 33.834843] Freeing unused kernel memory: 2176K
[ 33.839442] Run /sbin/init as init process
[ 33.844646] __cma_alloc: 1 callbacks suppressed
[ 33.844649] cma: __cma_alloc: linux,cma: alloc failed, req-size: 256 pages, ret: -12
[ 33.856935] cma: number of available pages: => 0 free of 16384 total pages
[ 33.922651] systemd[1]: System time before build time, advancing clock.
[ 33.950922] systemd[1]: MachineID '' is not valid, ignoring: Invalid argument
[ 33.965425] systemd[1]: systemd 256.17 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR -IMA -SMACK +SECCOMP -GCRYPT -GNUTLS +OPENSSL -ACL +BLKID +CURL -ELFUTILS -FIDO2 -IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE -TPM2 -BZIP2 -LZ4 -XZ +ZLIB -ZSTD -BPF_FRAMEWORK -XKBCOMMON -UTMP -SYSVINIT -LIBARCHIVE)
[ 33.998027] systemd[1]: Detected architecture arm64.
[ 34.003021] systemd[1]: Kernel command line argument says we are in first boot.

Welcome to Home Assistant OS 16.3!

[ 34.017971] systemd[1]: Hostname set to .
[ 34.023505] systemd[1]: Initializing machine ID from random generator.
[ 34.047718] systemd[1]: Failed to create timezone change event source: No such file or directory
[ 34.056742] systemd[1]: Using hardware watchdog 'Broadcom BCM2835 Watchdog timer', version 0, device /dev/watchdog0
[ 34.067210] systemd[1]: Watchdog running with a hardware timeout of 15s.
[ 34.241533] systemd[1]: Populated /etc with preset unit settings.
[ 34.335254] systemd[1]: Queued start job for default target Multi-User System.

[trex2000]

same for me
and then restarts

[trex2000]

Since switching to 16.0, there are always issues with booting. Something broke at 16.0. I had to reinstall 15.2 each time HA attempted to upgrade the OS.

[MartinW2]

Obviously, my x86 system upgraded slot B to 16.3, but now leaves me booting into slot A:

CLI "ha os boot-slot other" has no effect, still boots into slot A.
I only have remote access, via a terminal within HA.
How can I fix this version mismatch?
Any hints appreciated!

[DominicTheD3v]

16.3 refuses to boot when trying to use the qcow2 image for proxmox.