Running Home Assistant OS (HAOS) inside a Proxmox VE virtual machine gives you the full, officially supported installation - add-ons, Supervisor, automatic updates - while sharing hardware with other VMs and containers. On a modest Intel N305 mini PC, you can run HAOS alongside Plex, Vaultwarden, Nextcloud, and a WireGuard VPN with room to spare. The entire setup takes under 30 minutes. Download the HAOS QCOW2 image, create a VM in Proxmox, import the disk, boot, and you are up and running.

Home Assistant Blueprints are reusable automation templates. They split the logic from the per-device bits. You define a pattern once, say a motion light with a timeout, then spin it up for every room by filling in a form. No YAML to copy. No ten near-twin automations to babysit. In Home Assistant 2026.4, blueprints span three domains: automation, script, and template. They ship dozens of selector types for clean input forms and tidy collapsible sections for bigger setups. They’re the fastest way to keep smart home behavior the same across many devices.

Yes, Home Assistant ships a built-in conditional card. It shows or hides any dashboard card based on live state: entity value, time of day, who is home, screen size, and more. Add template sensors and a few HACS cards, and you can build dashboards where morning shows weather and coffee buttons, evening shows media and light scenes, and an empty house shows cameras and alarm controls. Cards pop in and out without leaving blank gaps, all through the stock Lovelace frontend. No custom code needed.

You can use HDMI-CEC commands through Home Assistant ’s HDMI-CEC integration - or a CEC-capable device like a Raspberry Pi running cec-client - to control TV power, input switching, and volume from automations and dashboards. Instead of juggling three or four remotes, you wire up a “Movie Mode” automation that dims the lights , powers on the TV, switches to the correct HDMI input, and sets volume to a comfortable level. One tap. Done.

Use Home Assistant ’s built-in packages system. Instead of one giant configuration.yaml that grows into a 2,000-line beast, packages let you split YAML by function: packages/lighting.yaml, packages/climate.yaml, packages/security.yaml, and so on. Each file can hold any mix of automations, sensors, scripts, input helpers, and templates. To tweak your thermostat logic, you open packages/climate.yaml. Nothing else.

As of Home Assistant 2026.4, packages support every integration domain, !secret references, Jinja2 templates, and nested subfolders. The rest of this post walks through setup, migration, design patterns, and Git workflows that make packages practical for a real smart home.

You can build a fully functional feature flag system using a JSON configuration file, environment variable overrides, and a single evaluation function in roughly 100 lines of Python. This gives you gradual rollouts, kill switches, and per-environment toggles without paying for LaunchDarkly , Unleash , or any other SaaS platform. The core pattern is straightforward: define each flag with a name, a boolean or percentage-based rule, and a list of target environments, then evaluate it at runtime through a thin SDK you own and control completely.