Home Assistant OS 15.0

[sairon]

Home Assistant Operating System

• Update all platforms to latest stable Linux 6.12 (Update all platforms to latest stable Linux 6.12 #3850) @sairon
• Update U-Boot to 2025.01 (Update U-Boot to 2025.01 #3878) @sairon
• Make swap size configurable (Make swap size configurable #3882) @sairon
• Allow overriding sysctl parameters via /etc/sysctl.d files (Allow overriding sysctl parameters via /etc/sysctl.d files #3883) @sairon
• Update Hailo PCIe driver and firmware to v4.20.1 (Update Hailo PCIe driver and firmware to v4.20.1 #3922) @sairon
• Move swappiness config to 15-swappiness.conf (Move swappiness config to 15-swappiness.conf #3884) @sairon
• Use shell script instead of OS Agent for device wipe (Use shell script instead of OS Agent for device wipe #3916) @sairon
• Use auditd to process AppArmor/audit logs (Use auditd to process AppArmor/audit logs #3885) @sairon
• Update firmware for Intel Wi-Fi 6/6E/7 cards, bump linux-firmware to 20240513 (Update firmware for Intel Wi-Fi 6/6E/7 cards, bump linux-firmware to 20240513 #3876) @sairon
• Update linux-firmware to 20250211 (Update linux-firmware to 20250211 #3901) @sairon
• Bump buildroot to 2024.02.11 (Bump buildroot to 2024.02.11 #3897) @sairon
• Bump os-agent to v1.7.2 (Bump os-agent to v1.7.2 #3914) @sairon
• Bump BlueZ to v5.79 (Bump BlueZ to v5.79 #3903) @sairon
• Update Docker to v28.0.1 (Update Docker to v28.0.1 #3902) @sairon
• Ensure haos-wipe service can be called only once per boot (Ensure haos-wipe service can be called only once per boot #3924) @sairon
• Fix runtime device permissions update in runc v1.2.x (Fix runtime device permissions update in runc v1.2.x #3921) @sairon
• Improve log clarity and fix typos (Improve log clarity and fix typos #3896) @pisanvs
• Remove all info pages in post-build script (Remove all info pages in post-build script #3888) @sairon
• Remove USB stack patches working around obsoleted Z-Wave devices issues (Remove USB stack patches working around obsoleted Z-Wave devices issues #3854) @sairon

Raspberry Pi

• Fix RPi 5 getting stuck in bootloader after some reboots (Fix RPi 5 getting stuck in bootloader after some reboots #3842) @sairon
• Update RPi firmware to fix boot with 2025-02-11 bootloader (Update RPi firmware to fix boot with 2025-02-11 bootloader #3913) @sairon
• Fix RAUC tryboot handler set-state idempotency, add more checks (Fix RAUC tryboot handler set-state idempotency, add more checks #3891) @sairon
• Disable UAS via usb-storage.quirks on RPi for JMicron JMS578 (Disable UAS via usb-storage.quirks on RPi for JMicron JMS578 #3857) @sairon
• Disable linux-firmware zstd compression (Disable linux-firmware zstd compression #3898) @sairon
• RaspberryPi: Update kernel to 6.6.74 - stable_20250127 ( RaspberryPi: Update kernel to 6.6.74 - stable_20250127  #3860) @sairon
• Backport upstream patch to fix downstream patch collision in RPi 6.6 kernel (Backport upstream patch to fix downstream patch collision in RPi 6.6 kernel #3856) @sairon

Home Assistant Yellow

• RaspberryPi: Update kernel to 6.6.74 - stable_20250127 ( RaspberryPi: Update kernel to 6.6.74 - stable_20250127  #3860) @sairon
• Update RPi firmware to fix boot with 2025-02-11 bootloader (Update RPi firmware to fix boot with 2025-02-11 bootloader #3913) @sairon
• Disable linux-firmware zstd compression (Disable linux-firmware zstd compression #3898) @sairon
• Fix order of patches for Yellow (Fix order of patches for Yellow #3862) @sairon

Home Assistant Green

• Linux: Update kernel to 6.12.18 (Linux: Update kernel to 6.12.18 #3919) @sairon
• Disable linux-firmware zstd compression (Disable linux-firmware zstd compression #3898) @sairon
• Drop kernel patch for fixed ODROID-M1/M1S kernel regression (Drop kernel patch for fixed ODROID-M1/M1S kernel regression #3895) @sairon

Open Virtual Appliance

• Linux: Update kernel to 6.12.18 (Linux: Update kernel to 6.12.18 #3919) @sairon
• Disable linux-firmware zstd compression (Disable linux-firmware zstd compression #3898) @sairon
• Remove unnecessary GRUB userspace tools and other files (Remove unnecessary GRUB userspace tools and other files #3887) @sairon
• Enable Intel 40 Gigabit ethernet driver module for x86-64 and OVA (Enable Intel 40 Gigabit ethernet driver module for x86-64 and OVA #3858) @sairon
• Update OVA to Linux 6.12 (Update OVA to Linux 6.12 #3845) @sairon

Generic x86-64

• Update generic-x86-64 Linux kernel to 6.12 (Update generic-x86-64 Linux kernel to 6.12 #3767) @nijave
• Linux: Update kernel to 6.12.18 (Linux: Update kernel to 6.12.18 #3919) @sairon
• Remove unnecessary GRUB userspace tools and other files (Remove unnecessary GRUB userspace tools and other files #3887) @sairon
• Use EROFS LZMA compression of firmware on x86 instead of per-file ZSTD (Use EROFS LZMA compression of firmware on x86 instead of per-file ZSTD #3877) @sairon
• Enable Intel 40 Gigabit ethernet driver module for x86-64 and OVA (Enable Intel 40 Gigabit ethernet driver module for x86-64 and OVA #3858) @sairon

Hardkernel ODROID

• Linux: Update kernel to 6.12.18 (Linux: Update kernel to 6.12.18 #3919) @sairon
• Disable linux-firmware zstd compression (Disable linux-firmware zstd compression #3898) @sairon
• Drop kernel patch for fixed ODROID-M1/M1S kernel regression (Drop kernel patch for fixed ODROID-M1/M1S kernel regression #3895) @sairon
• Allow boot from USB and NVMe on ODROID-M1 (Allow boot from USB and NVMe on ODROID-M1 #3852) @rpardini
• Revert kernel patch causing USB 3 and PCIe breakage on ODROID-M1/M1S (Revert kernel patch causing USB 3 and PCIe breakage on ODROID-M1/M1S #3843) @sairon

ASUS Tinker

• Linux: Update kernel to 6.12.18 (Linux: Update kernel to 6.12.18 #3919) @sairon
• Disable linux-firmware zstd compression (Disable linux-firmware zstd compression #3898) @sairon

Khadas VIM Series

• Linux: Update kernel to 6.12.18 (Linux: Update kernel to 6.12.18 #3919) @sairon
• Disable linux-firmware zstd compression (Disable linux-firmware zstd compression #3898) @sairon

Generic aarch64

• Linux: Update kernel to 6.12.18 (Linux: Update kernel to 6.12.18 #3919) @sairon
• Disable linux-firmware zstd compression (Disable linux-firmware zstd compression #3898) @sairon
• Remove unnecessary GRUB userspace tools and other files (Remove unnecessary GRUB userspace tools and other files #3887) @sairon
• Change Cadence i2c and Zynq GPIO from modules to built-in drivers (Change Cadence i2c and Zynq GPIO from modules to built-in drivers #3821) @michalsimek

Build System

• Improve tests traceability, add test for Systemd dependency cycles (Improve tests traceability, add test for Systemd dependency cycles #3917) @sairon
• Add test that no AppArmor denied events are produced (Add test that no AppArmor denied events are produced #3912) @sairon
• Remove unnecessary and invalid e2scrub removal from post-build (Remove unnecessary and invalid e2scrub removal from post-build #3886) @sairon
• Use Python 3.13 for the build and artifacts index jobs (Use Python 3.13 for the build and artifacts index jobs #3840) @sairon

Dependencies

• Bump docker/setup-buildx-action from 3.9.0 to 3.10.0 (Bump docker/setup-buildx-action from 3.9.0 to 3.10.0 #3910) @dependabot[bot]
• Bump docker/build-push-action from 6.14.0 to 6.15.0 (Bump docker/build-push-action from 6.14.0 to 6.15.0 #3909) @dependabot[bot]
• Bump docker/build-push-action from 6.13.0 to 6.14.0 (Bump docker/build-push-action from 6.13.0 to 6.14.0 #3894) @dependabot[bot]
• Bump docker/setup-buildx-action from 3.8.0 to 3.9.0 (Bump docker/setup-buildx-action from 3.8.0 to 3.9.0 #3869) @dependabot[bot]
• Bump docker/build-push-action from 6.12.0 to 6.13.0 (Bump docker/build-push-action from 6.12.0 to 6.13.0 #3836) @dependabot[bot]
• Bump actions/stale from 9.0.0 to 9.1.0 (Bump actions/stale from 9.0.0 to 9.1.0 #3835) @dependabot[bot]

---

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

[michalsimek]

Works fine on AMD/Xilinx kd240.

[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.

[foddy-foo]

Updated my HA installation, running on Proxmox. No issues seen.

[brugk000]

Can confirm this

[Th3K1ngP1n]

Confirm +1

[santi8ago8]

+1, update without issues.

[4rianton]

unfortunately, 15.0 has led to a total disabling of c states which wasn't the case with 14.x. My proxmox host is now constantly using 16w instead of 9w average earlier.

[danez]

I'm trying the update on my raspberry pi 5. It starts the update, reboots, but then still 14.2 is reported and the update is offered again.

[danners430]

Same behaviour here... not confident enough to play around with the bootloader though!

[sairon]

There is definitely something fishy with RPi 5 updates, with one known problem already fixed in OS 15. Hopefully we'll get down to that in #3943.

[pablopezg]

Same here, but from 14.1. I didn't try again to update it or modify the bootloader. I will wait for a fix on it.

[danez]

So reading the cold boot recommendation, that is what maybe solved it for me too and not the bootloader update. When switching between rasberry os and haos SD card i always unplugged power of course.

[derkorte]

Updated my Pi 5 8GB from 14.2 to 15 without any problems.
Core: 2025.3.3
Supervisor: 2025.03.3

[agr-bmw]

Update my raspberry pi5 from OS 14.1. No issues seen and OS Version 15 is reported in HA.

[rahul-cant-code]

+1 same.

Note: I think I updated from 14.2

[NickdeK]

Mine failed and now can't start the Home Assistant CLI and gets into the emergency mode
Eventually it worked again but it did not update, still 14.2 the CLI does say it's on the latest version.

[huizebruin]

What did you do, to update to the 15.0. after the error on your screen.

[NickdeK]

@huizebruin I don't know, after I think the 3rd reboot it suddenly worked. But I'm skeptical about if it's updated or not, the web ui still says 14.2.

[danners430]

I've just had two Pis go completely unresponsive while installing the update - been a good 15 minutes since the updates were initiated, and neither are reachable now... Not wanting to bash anyone, just looking for advice above all else!

[danners430]

A force reboot of the devices has unbricked them, but back to 14.2

[sairon]

Tracking in #3943.

[brugk000]

HP T620 thinclient booted back to 14.2

[kridness]

Same here

[FoxScout]

Same here. I dont know what I did, but it restored automatically to 14.2 after several hard resets

[FoxScout]

Have you tried booting it with the display connected? Where does it get stuck?

1. Hard reset, two or three times in 12hr aprox.
2. I told ChatGPT to help me.
3. I tried to connect through SSH, but "connection refused"
4. I connected Screen, keyboard and mouse. NO LAN initially. Start HP T620. No stuck in anypoint. CLI starts "correctly" to me. I switched from HDMI (laptop) to DisplayPort (HP T620). after switch back to HP, the screen was black. Nothing seen there. I typed "ha core restart" without sight. But I think it didn't do anything, so hard reset again.
5. Now, disconnected the HDMI of my laptop and work In parallel, mi laptop cannot access to HA through local IP web. I was trying to restore back trough "ha backup" command in HP T620, but very stupidly I didnt know how to "move" the information in CLI, because my backup list was very large. ChatGPT was not very helpul here, because CLI of HA is a little bit different -I think- or I am too newby. After many times. Misteriously, the webpage of HA refreshed in Laptop and... I dont know what I did. But it work.

[Daafip]

Same issue here, not working on HP thin client 620

[bjorns163]

My t620 won't boot anymore after upgrade.

[lpwevers]

HP T520 thin client boots, but gets stuck on can't start Home Assistant CLI and gets into the emergency mode. Booted back to 14.2 and everything's fine. I'll skip this one for now.

[sairon]

This really seems unrelated to the OS upgrade. You should check Core logs (ha core logs) if you find anything there, and rule out it's not some of the custom integrations by restarting the Core in the safe mode by ha core restart --safe-mode.

[sairon]

@lpwevers I realized the original post was hijacked with another issue. Please try checking the output of commands posted here: #3933 (reply in thread)

[hvandonge]

@lpwevers I have the same hardware, and boot is also failing. You found no solution yet? Is there an issue tracking this?

[lpwevers]

@hvandonge Nope. I just rebooted it and choose to boot the 14.2 version when grub gave me the option. I've decided to skip 15.0 and hope it'll be fixed in 15.1.

[sairon]

The root cause was later identified for these HP thin clients (and couple of other PCs that are running those AMD SoCs), see:

• HP T620 stuck after HAOS15 update #3944
• Enable amdgpu SI and CIK support for x86 #3957

[Wendelstein7]

Intel NUC (Generic x86-64) doing very well 👍

[keithr59]

Home Assistant Green updated from 14.2 to 15.0. All OK.

[wfmer]

2nd confirmation

[badaz]

Home Assistant Green updated from 14.2 to 15.0. All OK.

3rd confirmation. Install was very fast (around 3 minutes including full restart)

[Peterpc58]

HP T730, get Waiting for the Home Assistant CLI to be ready.....
After 3x reboot back to 14.2

[sairon]

It should eventually drop down to a normal shell (aka "emergency console"). There you should be able to troubleshoot further, e.g. check systemctl --failed to check for failed units or check docker ps -a to see what containers are (not) running.

[amcort]

I had a similar issue. Installed HAOS 15.0 and was running fine. I shut it down to move the machine elsewhere and when trying to boot up again, it never came up in the network. Connected a monitor and saw it was stuck on the emergency console. It didn't move forward until I connected a keyboard and followed the instructions on the screen. It's been running fine since, but scared of shutting it down and having to do the little dance again.

[Zippo2000]

HP EliteDesk 800 G4 with proxmox: HA 15.0 started but gets unusable slow approx. 5 Minutes after startup, with around 30% CPU usage inside VM

[RickyKeys]

I have the exact same setup, so I'll wait a couple of days before I update.
Thanks for the warning.
Please let me know if you find a solution.

[sairon]

This was already discussed in another thread: #3933 (reply in thread)

@RickyKeys You can follow the same steps to troubleshoot your issue but the @Zippo2000's one is most probably unrelated to the OS update.

[nijave]

14.2 -> branch with kernel 6.12 (rauc cli) -> 15.0rc2 (rauc cli) -> 15.0 (gui) worked on my Beelink N150 with x86-64 generic

[kveldscholten]

I get the following error on my Pi 4

2025-03-17 22:06:50.658 INFO (MainThread) [supervisor.os.manager] Fetch OTA update from https://os-artifacts.home-assistant.io/15.0/haos_rpi4-64-15.0.raucb
2025-03-17 22:06:58.869 INFO (MainThread) [supervisor.os.manager] Completed download of OTA update file /data/tmp/hassos-15.0.raucb
2025-03-17 22:10:33.909 ERROR (MainThread) [supervisor.os.manager] Home Assistant Operating System update failed with: Installation error: Failed marking slot kernel.1 bootable: failed to activate slot kernel.1: uboot backend: Failed to run fw_setenv: Child process exited with code 1

After restart the same error again

[sairon]

It seems something is wrong with the U-Boot environment, can you connect to the device (with keyboard and display) and run login and then fw_printenv? There might be also more detailed error in journalctl -u rauc or journalctl -t rauc after the failed update.

[decibelio99]

Hi,
It doesn't work in Odroid N2 with emmc
I have had to install a before version

[Tanjohnson99]

Synology VM > OK !

[CH-Tefi]

HI
I've an intel n100 nuc. After updateing no response. Reboot 14.2. This for 2 times
I'm waiting now.

[bilogics]

Unable to install on a Intel HP t620 Flexible Thin Client

[alvinchen1]

Successfully able to install on Beelink GTi14 Ultra AI PC Intel® Core™ UItra 9 185H with the following BIOS Changes

Advanced - CPU Configuration - X2APIC Enable from Enabled to Disabled
Advanced - System (SA) Configuration - VT-d Configuration - VT-d Change from Disabled to Enabled
Advanced - System (SA) Configuration - VT-d Configuration - X2APIC Opt Out Change from Disabled to Enabled
Security - Secure Boot - Secure Boot - from Enabled to Disabled

[sairon]

I wonder, was any of the BIOS options set to a different value before? With previous versions some people reported the VT-d had to be actually disabled: #3474

[Miketmechanic]

Hello everyone, My HA Yellow with CM5 & Samsung NVME would not update to 14.2, so I started a fresh and loaded from scratch, completely erased (not formatted) the SSD and eMMC. It has come to update to 15.0 and it will not update again. ANy help would be really appreciated. Is there anyway i can do it through the terminal manually ?

[jeroen-vd-nl]

No luck here on a RPI5
Update downloaded and installed, rebooted, HAOS still on 14.2

[Miketmechanic]

Same here

[LarsKumbier]

Same here.

[Flerbizky]

Dell Wyse 5070 thin client with M.2 SATA SSD and 8Gb of memory - bare-metal install - no issues upgrading.

[gaalday]

Same problem on Intel NUC x86 after upgrading to 15.0 from 14.2...
Got it alive after booting with no ethernet cable connected. Still on 14.2.

[sairon]

What NUC exactly? Would it be possible to connect an HDMI display and update with it connected to see where it gets stuck? If it falls into the emergency console, check dmesg -l warn+ for errors. Eventually, there might be something in the Host logs for previous boots (click three dots and select previous boot in "Show HAOS startups").

[gaalday]

Hi sairon: Intel NUC DN2820FYKH
https://www.intel.la/content/www/xl/es/products/sku/78953/intel-nuc-kit-dn2820fykh/specifications.html

I'm not able to identify anything special on previous boot log. A lot of network events.
You can see it attached (from 10:40 on 19/03/25 - yesterday).
host_2025-03-20T07-33-32.982Z.log

Will try a new upgrade with a display connected this weekend.

[sairon]

Unfortunately nothing there, the last log line from 2025-03-19 10:40:49.634 is when it rebooted after the OS update. In case the device doesn't boot fully, the boot might not be shown in the list of boots, however, there might be still logs if you keep scrolling up in them. Can you check whether you see something after that log line from 10:40:49 that is not the boot to the working slot? Should start with something like homeassistant kernel: Linux version 6.12.18-haos.

[brugk000]

I tryed this suggestion:
sed -i.bak "s/$/ modprobe.blacklist=amdgpu/" /mnt/boot/cmdline.txt

I have en empty /mnt directory if I ssh into HA

[sairon]

If it's not SSH on port 22222, then you're connecting to a container that has no access to the boot partition. As I wrote, direct display/keyboard connection or "developer SSH" access is needed.

[brugk000]

Stupid mistake. Sorry for this.
The suggested workaround works on the T620.
Thanks

[mirbusak]

Hello, I also have an HP T620, can you please post a working solution for updating to 15.0? I'm a complete layman, could you describe it for laymen how to do the update? Thank you very much. Martin

[brugk000]

Sorry for the delay.
My solution:
1 install this addon. It gives you developer SSH. https://community.home-assistant.io/t/add-on-hassos-ssh-port-22222-configurator/264109
2 generate public/private keys with puttygen
3. copy the public key to the addon and start it
4. login with putty and the private key to your HA instance port 22222
5. execute sed -i.bak "s/$/ modprobe.blacklist=amdgpu/" /mnt/boot/cmdline.txt
6. reboot HA
7. now you can upgrade to 15.0

[atifhub]

15.0 Not working on a Generic x86-64 fresh install :
Tested on HP T620 and some Nucs.
It stucks on HassOS data resizing…

No issues with 14.2 fresh install.

[Smogli74]

Not working on RPI 3. Back to 14.2
no reboot possible

[ctdavi]

Update 15 never installs despite tries across several days incl hard reboot(s) of HA
IIRC my RPI5 might have been non-responsive after the first attempt but eventually came back to ~life. I think. That sounds familiar, at least.

RPICM5+yellow+M.2.2280 SSD
No SD card
No monitor attached
Gbps ethernet attached & in use
Wi-fi also attached & in use

Possibly edge-case software(s) installed:
HACS+Frigate (incl Mosquitto, i think)
roborock.vacuum.a01
Advanced camera card
ESPHome Device Builder

I forget what my Yellow is set for, Zigbee or the other one, but I think it's Zigbee. The whole contraption is pretty new so I don't have a whole lot goin' on with it as of yet for actual HA beyond the (very-old) roborock (vacubot), a couple ceiling fans and a really old HS100 outlet-plug-in. I believe the Zigbee sees only itself.

Have not seen anything interesting logged to /HomeAssistant/home-assistant.log. Looks like normal complaining about HACS + Frigate + my very old roborock a01. Not sure where to look for installation logs / not seeing them (or possibly i dont recognize their filenames as install logs)

HTH & LMK if i can do/try/provide anything

[ctdavi]

Dang I forgot about my Hey Jarvis. Voice Assistant preview offical ~store-bought box installed & running. Local processing of voice commands but no custom wake word. So that's Wyoming+umm+the+other+thing(s)

[ctdavi]

I have a lil battery charger plugged into a USB port, too. Both batteries in it are fully charged and the red charging LED is off, but who even knows how it might affect startup. This charger charges two drone batteries @ 3.7v / 530mAh. And that 530mAh might be a S30mAh or something with an initial number or letter that looks like a very small 5 to my old eyes

[taco-con-carne]

This update totally bricked my Rpi 3. Let it sit for a few days, hard booted about 10 times (waiting in between). No luck.

Watching the light on the pi, it looks like it was getting stuck in the first few seconds of boot

[sairon]

There's a report for that already: #3965

It appears that a change in the Raspberry Pi firmware caused issues with some SD cards. A workaround is suggested there. I would also appreciate if you could follow the steps described there and post details about your SD card.

[toniuhlemann]

I am using WLAN USB Stick in Proxmox Server in order to connect against my Huawei Inverter using the Huawei Solar Integration. So while homeassistent connects via LAN i also have WLAN entry to connect to the Inverter. It seems upgrading to haos 15.0 seems to break my WLAN functionality not being able to connect against anY Wireless Network anymore. I can confirm that downgrading to HA OS 14.2 fixed this Problem. I am using a tp Link WLAN USB Stick. Is this a regression in the latest ha os Version 15.x or is it just not compatible anymore? This issue currently prevents me from upgrading to ha os 15.x.