Raspberry Pi 5 help and extra in House Assistant OS launch 12 & Supervisor replace

TL;DR: House Assistant OS 12 provides help for Raspberry Pi 5 and ODROID-M1S boards, with the Linux kernel up to date to six.6. Moreover, backups have develop into sooner, and add-ons can now sign after they shouldn’t be auto-updated.

Raspberry Pi 5

With the discharge of House Assistant OS 12, we formally announce Raspberry Pi 5 help! Many House Assistant OS customers have extensively examined the preview releases throughout the previous couple of months, and after some preliminary hiccups with the Raspberry Pi 5-specific replace mechanism, issues are steady and strong at present. As a 3rd of all House Assistant customers at the moment use a Raspberry Pi board as their devoted House Assistant system, we’re certain this help will make many customers very joyful!

In comparison with different Raspberry Pi boards, HAOS doesn’t use U-Boot as an additional bootloader. As a substitute, the Raspberry Pi’s built-in “tryboot” performance is used to routinely fall again to a earlier launch in case of an replace failure. This new replace mechanism integration required us to have an extended testing part.

In our testing, the upper CPU clock of the Raspberry Pi 5 (as much as 2.4GHz) makes House Assistant really feel noticeably snappier in comparison with earlier Raspberry Pi boards. Moreover, a Raspberry Pi HAT that gives NVMe SSD help lets you prolong your Raspberry Pi with quick, dependable, and cost-effective storage. We do suggest utilizing an SD card because the boot medium and utilizing the data disk feature to move most of the Home Assistant installation onto the NVMe. This is easy to set up and guarantees a reliable boot.


The Raspberry Pi 5 is not the only new board that is supported with this release. We are happy to announce that the family of supported ODROID devices from the Korean manufacturer Hardkernel has become bigger thanks to a community contribution from Tim Lunn (darkxst), who implemented board support for the ODROID-M1S. The ODROID-M1S is the newest single-board computer from Hardkernel, which is similar to the already supported ODROID-M1, which was added in Home Assistant OS 10. This new board offers a slimmer form factor, 4 or 8 GB of RAM on board, and an embedded 64 GB eMMC storage. Home Assistant OS can be booted either from an SD card or the system can be flashed to the eMMC card using the procedure described in the documentation. Whereas the board additionally has an NVMe slot for a solid-state drive, it isn’t supported as a boot system. Nevertheless, identical to on the Raspberry Pi 5, it will possibly nonetheless be used as the information disk.

Similar to its bigger brother, the ODROID-M1S is powered by a quad-core ARM Cortex-A55, however whereas ODROID-M1 has (very barely) beefier Rockchip RK3568 SoC, this board sports activities the RK3566. A few of our extra curious readers could discover this is identical processor that’s discovered on our House Assistant Inexperienced! Whereas there are some similarities between these two boards, House Assistant Inexperienced can give you a seamless out-of-box expertise, permitting you to arrange your sensible dwelling in a matter of minutes. However House Assistant can be concerning the freedom of alternative, so if you’re in search of a extra DIY strategy, ODROID-M1S may be the proper alternative for you.

Linux 6.6

House Assistant OS 12 now comes with Linux kernel 6.6! That is excellent news for individuals who wish to run their House Assistant on newer {hardware} that lacked help within the earlier 6.1 kernel. This model replace additionally permits us to increase the listing of supported Wi-Fi and Bluetooth playing cards, together with ones chances are you’ll discover in new mini-PCs, a well-liked platform for House Assistant OS. Those that run their installations on a Raspberry Pi (together with the CM4 in House Assistant Yellow) could discover their kernel model nonetheless begins with 6.1. It is because we’re not utilizing the upstream kernel however the downstream one maintained by the Raspberry Pi builders. However this kernel was additionally up to date to the newest steady model, which we hope will resolve some sporadic bugs.

House Assistant OS sticks to the LTS (long-term help) kernels, that are normally launched as soon as per yr – identical to Buildroot, the bottom system we use for House Assistant OS. This time, we’re barely forward of schedule, as a result of normally the kernel replace is completed alongside the bump of the Buildroot model. However don’t fear, the Buildroot replace is coming quickly as effectively, and we count on to incorporate its replace in one of many subsequent minor House Assistant OS releases coming within the following weeks. It will conclude this yr’s spring cleansing of House Assistant OS, and we will probably be able to concentrate on new options and enhancements once more!

Sooner Backups

House Assistant Supervisor and Core’s built-in backup performance has develop into a lot sooner. Because of contributions from bdraco, the backup characteristic gained sooner compression speeds because of a library named isal, which supplies optimized low-level features for compression and decompression. Extra importantly, the backup characteristic now avoids intermediate copies, making it sooner on slower storage media particularly. When you used uncompressed backups earlier than as a result of the backup was too sluggish for you, now could be the time to offer compressed backups a strive once more! 😀

Comparison of the speed of a 100MB backup on a Home Assistant Yellow, between Supervisor 2023.12.1 and 2024.02.0.

House Assistant OS customers’ backup performance is a part of Supervisor. You’ll have acquired the enhancements incrementally over the releases of the previous few weeks. On the time of writing, your set up ought to run on House Assistant Supervisor 2024.02.0 with all these enhancements inbuilt.

Safer add-on auto-updates

Final, however not least, the Supervisor options an auto-update flag for add-ons. Nevertheless, relying on the character of an replace to the add-on, the brand new model would possibly want consumer intervention or have breaking modifications. Add-on builders now have the choice to stop auto-updates to such variations. Customers of the auto-update characteristic would possibly see an replace notification regardless of auto-updates being enabled. Which means the writer of the add-on determined that this specific replace shouldn’t be auto-updated and as an alternative be manually authorised by the consumer.

Be aware: We usually don’t suggest auto-updates for add-ons, as even secure updates would possibly intrude with common operation. For instance, throughout the automated replace of an add-on like Z-Wave JS, your Z-Wave units would unexpectedly develop into unavailable for a short while. The higher strategy for such add-ons is to plan a while to take care of your House Assistant system each occasionally and replace your add-ons in a batch.