With House Assistant OS 11, there isn’t any large or flashy function to focus on. Moderately, there are a number of small enhancements and little gems. The elevated use of Bluetooth has uncovered fairly some points on House Assistant OS; a few of which we’re nonetheless engaged on. One of many foremost points in House Assistant OS 10 was attributable to a bug within the processing of Bluetooth ads within the Linux kernel’s Bluetooth stack itself. With the assistance of our neighborhood, we managed to breed, pinpoint, and supply the required hints to the Bluetooth builders. This led to a repair within the Bluetooth stack not just for House Assistant OS and Supervised customers however for the Linux neighborhood basically 🎉 (see subject https://github.com/home-assistant/operating-system/points/2535 for particulars).
We’ve additionally labored on the touchdown web page which is bundled with House Assistant OS 11. The touchdown web page is seen to the consumer when beginning a recent set up of House Assistant OS for the primary time. It options the identical new look because the House Assistant Core onboarding circulate, and tracks points through the bootstrapping section, robotically displaying errors in the event that they happen throughout that vital setup section.
The brand new touchdown web page shipped with House Assistant OS 11
This month we at Nabu Casa obtained a brand new addition to the House Assistant OS group: With Jan Čermák becoming a member of, we can have extra bandwidth to implement new options in addition to to sort out points reported by our neighborhood. Welcome Jan!
And eventually: House Assistant OS 11 will likely be pre-installed within the subsequent batch of House Assistant Inexperienced 🎉
Benefit from the newest model of House Assistant OS!
Stefan
Linux’ preemptible kernel configuration
We’ve utilized Linux’s preemptible kernel configuration throughout the board. The result’s decrease latencies even on busy techniques (for instance attributable to gradual I/O operations), making your good house much more responsive.
VM filesystem freeze is being relayed to House Assistant
VM filesystem freeze (as triggered by VM snapshots) is a neat function for extra superior setups based mostly on Proxmox (or different KVM based mostly VMs).
Right this moment, House Assistant’s recorder integration makes use of a database beneath (by default that is SQLite). When House Assistant takes a backup, the Supervisor notifies the database engine earlier than copying the database recordsdata (presently, that is applied for SQLite and MariaDB). To this point, this didn’t work for VM filesystem freezes With that notification, the database engine can take the required steps to make sure that the database recordsdata are in a constant state earlier than the backup takes place.
Nonetheless, when making a snapshot utilizing the VM snapshot function, the database doesn’t find out about this, and the snapshot can find yourself with an inconsistent state of the database. On snapshot restore, the database could or could not be capable to recuperate from that inconsistent state. This could result in partial and even full information lack of the recorder information.
With House Assistant OS 11, on Proxmox/KVM-based VMs, when utilizing the snapshot function, the file system freeze is now relayed to House Assistant. House Assistant then makes use of the identical notification mechanism as backups are utilizing. This ensures that VM snapshots are at all times coherent, ensuring rollbacks of your good house techniques are dependable.
Docker and containerd Upgrades
On this launch, House Assistant OS has adopted the newest variations of Docker (v24.0.6) and containerd (v1.7.6), guaranteeing higher efficiency and container administration. We’ve additionally improved the containerd configuration to drop pointless parts. With this, containerd makes use of much less CPU and reminiscence sources, guaranteeing higher total efficiency.
Extra Highlights in House Assistant OS 11
-
Constant community interface naming: On Arm-based boards, community names are actually enumerated based mostly on the gadget tree. Because of this the primary Ethernet gadget will not be named eth0 however end0. The identical community configuration used beforehand is robotically utilized to the community interface with the brand new identify.
This could be a breaking change ⚠️: For those who use the identify of the Ethernet interface in customized scripts or automation, you’ll have to regulate to the brand new identify (as proven within the community settings)! - Bluetooth enhancements: Updating to a more recent model of BlueZ, repair for the Bluetooth LE commercial stall bug, and optimizing Bluetooth gadget cache administration.
- Improved kernel configuration: Our improved kernel configuration goals to enhance Docker’s overlayfs efficiency, making container operations smoother.
- Help for LED management on House Assistant Inexperienced: The three LEDs on the entrance of House Assistant Inexperienced can now be managed by means of {hardware} settings.
- Adjusted improvement workflow (my private favourite, however I could be biased 😉): Our adjusted improvement workflow permits for extra incremental adjustments and incorporates extra automations. This can make it simpler for builders to work on and enhance House Assistant OS.