Versie 18.3 van Home Assistant OS is uitgekomen. Home Assistant OS is een minimaal, op Buildroot gebaseerd besturingssysteem dat het mogelijk maakt om op een fysieke of virtuele machine Home Assistant te draaien. Versie 18.3 gebruikt versie 2025.02.18 van Buildroot als basis en de Linux-kernel voor de meeste ondersteunde platforms is bijgewerkt naar versie 6.18.52. De releasenotes voor deze uitgave zien er als volgt uit:
Changes
Home Assistant OS 18.3 is a bugfix release with several reliability improvements. Container image layers are now synced to disk right after they are unpacked, which prevents corrupted images when the power is cut shortly after an update. For installations where the container images are already corrupted, a new
ha docker reset-storagecommand allows wiping the Docker storage and downloading all images again. F2FS is now supported on all targets. On Raspberry Pi, HDMI output on displays larger than 1920x1080 and booting from USB SSDs on Raspberry Pi 3 have been fixed, and Bluetooth on Home Assistant Yellow is stable again after the regression introduced in 18.0. The landing page shown during initial setup is now served on port 80 by default, with a redirect from the legacy port 8123. The Linux kernel has been updated to the latest stable version across all targets. All users are encouraged to upgrade.Noteworthy changes
Docker storage resetA corrupted Docker storage could until now only be recovered by wiping it manually from the OS shell. Removing and pulling a single image again is often not enough, because image layers are shared between images. The OS now provides a service which wipes the whole Docker storage on the next reboot when requested by the Supervisor. The reset can be scheduled from the CLI:
ha docker reset-storageUse it to recover from a corrupted or inconsistent Docker storage, for example when containers fail to start or images cannot be updated. All container images, including Supervisor, Home Assistant Core, plugins and apps, are deleted and downloaded again once the system is back up. Configuration and data of Home Assistant and apps are kept, as they are stored outside of the Docker storage.
Before resetting, please note:
NTP configuration as drop-in files
- Internet connectivity is required for downloading all container images again
- A reboot is required to apply the reset
The persistent time synchronization (timesyncd) configuration is now stored as drop-in files in
/etc/systemd/timesyncd.conf.d. Until now, a single copy of the whole/etc/systemd/timesyncd.confwas persisted, which meant that changes to the shipped defaults never reached existing installations and that NTP servers could not be updated reliably through the OS Agent. The configuration is now layered, from lowest to highest priority:
10-ntp.conf: NTP servers received from DHCP20-custom.conf:timesyncd.confimported from the CONFIG partition50-os-agent.conf: NTP servers set through the OS Agent D-Bus API (used by the Supervisor)On upgrade, any settings in the previously persisted
timesyncd.confthat differ from the shipped defaults are moved to20-custom.confautomatically, so no action is needed. Importingtimesyncd.conffrom the CONFIG partition keeps working and lands in20-custom.conf. Drop-ins with a higher priority can be added for more complex customizations.Together with this change, NTP servers can now be configured from the CLI without touching any files. The new
ha timecommands show the current settings and set or clear the primary and fallback NTP servers, which are stored in50-os-agent.conf.
:strip_exif()/i/2006193904.png?f=thumbmedium)
/i/2004673268.png?f=fpa)
:strip_icc():strip_exif()/u/64465/crop5db09addab56c_cropped.jpeg?f=community)
:strip_exif()/u/120134/Cucco.gif?f=community)
/u/176086/crop5f0823fa5e8d6_cropped.png?f=community)
:strip_icc():strip_exif()/u/25852/bowmore_18k.jpg?f=community)
