Home Assistant OS 18.0 #4780
Replies: 2 comments 6 replies
-
|
I have a Home Assistant Yellow with a Raspberry Pi 5. Do I need to heed the warnings and do something to update the bootloader, or is that handled for me? |
Beta Was this translation helpful? Give feedback.
-
|
I'm in the same boat - this is a bit confusing. When I run |
Beta Was this translation helpful? Give feedback.
-
|
I'm hoping to get an official answer as I am also in the same boat, but it looks like under Yellow, they are trying to warn us if we need to do it when we update:
Update: I took the leap. It worked without any extra commands by updating it from the HA UI |
Beta Was this translation helpful? Give feedback.
-
|
The system still boots, it's just the display output which is affected. Since the Yellow has no display output this combination is not problematic or rather it does not matter. It is safe to upgrade to OS 18. |
Beta Was this translation helpful? Give feedback.
-
|
I’m curious about the statement that raspberry pi firmware can only be updated when booting from an sd card. I’m using a usb ssd drive so it’s unclear what I should do to update… |
Beta Was this translation helpful? Give feedback.
-
|
I‘ve just updated my pi 5 (nvme ssd) without problems, Firmware was older than 2025-12. I updated the bootloader afterwards with I assume My rpi5 with haos 18 has no external display attached, so I ignored this warning: |
Beta Was this translation helpful? Give feedback.
-
|
How a Yellow booting CM4 on SSD could be updated to latest f/w ? ~ # ha os boards raspberrypi firmware I tried to move my data partition back to CM4 MMC (32GB), but this failed with following error: |
Beta Was this translation helpful? Give feedback.
-
|
Hardware: Just tried upgrading HA OS from 17.3 to 18.0 just now. Hard reset by switching power off. Would um...wait a little bit more before trying it again, just finished prolonging Tuya dev Trial and re-linking my Local Tuya devices, enough tinkering for today. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Home Assistant OS 18.0 is a major release bringing significant updates to all platforms. The Linux kernel has been updated from 6.12 to 6.18 across all targets, Docker has been upgraded to v29.5.3 with containerd v2.2.4, and the underlying Buildroot has been updated to 2025.02.14. Disk images are now significantly faster to flash, the default swap size is now bounded to avoid problems on systems with very low or very high amounts of RAM, and the Raspberry Pi bootloader firmware can now be updated directly from Home Assistant. All users are recommended to update.
Noteworthy changes
Raspberry Pi firmware updates
The Raspberry Pi bootloader (EEPROM) firmware can now be checked and updated directly from Home Assistant OS. Use the following CLI commands to show the current firmware status and to install an update:
Home Assistant Core 2026.7.0 will also expose the firmware as an update entity. Note that updating the firmware is only possible when the system is booted from an SD card, or in general on Raspberry Pi 5 and on Home Assistant Yellow with a CM5.
Note that Rasbperry Pi 5 now requires firmware 2025-02-12 or newer. See the Raspberry Pi section below for details.
Default swap size
The default swap file size was previously set to 33% of the system RAM, which produced a swap file too small to be useful on low-RAM systems and an unnecessarily large one on systems with plenty of RAM. The default size is now clamped between 1 and 4 GB:
Leaner disk images and faster flashing
Disk images no longer overprovision the data partition, it is now sized to fit only its initial contents. Since the published images are compressed, the download size is not affected, but flashing is considerably faster, because the unused space at the end of the filesystem no longer needs to be written to the target storage. As before, the data partition is automatically expanded to use the available space on first boot.
Images for virtual machines (Open Virtual Appliance and the aarch64 VM formats) are pre-sized to 32 GB, so they no longer need to be resized before use.
Unified "haos" naming
The mix of legacy
hassos/HassOSand newerhaosnaming across the operating system has been harmonized tohaos. Most visibly, systemd units and helper binaries previously prefixedhassos-are now prefixedhaos-. If you have scripts or tooling that reference these names on the host (for example via the console or host logs), they may need adjusting. On-disk partition and filesystem labels are unchanged, so existing installations are not affected by the rename.Smoother first boot and landing page
The landing page, shown during the initial setup before Home Assistant Core has finished installing, has received a number of improvements that make the first boot easier to follow.
Downloading and installing Core on a fresh system can take a while, especially on slower connections, and until now the landing page gave no indication of how far along the process was. It now shows a progress bar while Core is being downloaded, so it is clear that something is happening and roughly how much is left.
The initial mDNS announcements during the first boot have also been fixed. The device now announces itself correctly from the start, so it can be discovered in the mobile apps right away while the system is still setting itself up, without having to wait for the Core installation to complete.
Home Assistant Operating System
_workstation._tcpservice annoucement from HAOS (Drop_workstation._tcpservice annoucement from HAOS #4739) @agnersRaspberry Pi
Warning
Raspberry Pi 5 users need a bootloader from at least 2025-02-12, otherwise the display output may freeze early during the boot. Update the bootloader before installing this update, using one of the following methods:
rpi-eeprom-update -awhile connected directly to the device (using a display and keyboard), prior to installing the OS update.ha os boards raspberrypi firmware updateover SSH right after updating the OS.Note
The default graphics (DRM) driver on Raspberry Pi 4 has been switched from the legacy, no longer maintained FKMS driver to the modern KMS driver, which among other things enables HDMI-CEC support. This only applies to new installations. On existing ones,
config.txtin the boot partition must be adjusted manually to make the switch.Home Assistant Yellow
Home Assistant Green
Open Virtual Appliance
Generic x86-64
Hardkernel ODROID
Khadas VIM Series
Generic aarch64
Build System
Documentation
Dependencies
Dependency updates (click to expand)
This discussion was created from the release Home Assistant OS 18.0.
Beta Was this translation helpful? Give feedback.
All reactions