Home Assistant 2026.2: a big polish update… and two new features that will save you time

The version 2026.2 of Home Assistant has been available for a few days now, and it has a bit of a “we cleaned the house, and suddenly everything feels simpler” vibe. Not because Home Assistant is becoming basic (that’s not its style), but because the team continues to remove the rough edges that mostly block… when you want to go fast. This update revolves around five very concrete areas: the new Overview (the “Home” dashboard becomes the norm), quick search in the style of a command palette, automations that speak more human, add-ons renamed “Apps”, and a project more ambitious than it seems: an open database of devices.

The Overview becomes the default dashboard

The most visible change is that the “Home Dashboard” is officially becoming “Overview” and establishes itself as the default view for new installations. If you are a long-time user and have never really touched the default view, Home Assistant will offer to switch. If you already have a custom Lovelace that’s just right, nothing is broken: you remain in control, and you can also recreate a “Overview (legacy)” dashboard if you prefer the old approach.

In practice, this “next-generation” Overview plays the dynamic dashboard card: it adapts to the screen, better groups the information, and especially emphasizes organization by rooms (Areas) and categories. In concrete terms, it means less time aligning cards and more time managing the house.

A detail that changes everything when adding hardware: a “Discovered devices” card appears in the “For You” section. It displays detected devices and allows you to add them immediately, or jump straight to their management, without digging through menus.

And since a smart home is not just “entities”, Home Assistant also emphasizes tidiness. A dedicated area collects what is not assigned to a room, then the interface gently “nudges” you to classify the devices in the right place. The goal is clear: to keep a clean instance even when you’re adding sensors like crazy (yes, we all know that slippery slope).

Minor interface tweaks: themes, areas, navigation

Home Assistant continues its major visual cleanup. The blue bar from the default theme disappears in favor of a more coherent rendering with the Settings page, which emphasizes the cards and data more.

Another clever change: themes are now managed at the user profile level. In plain terms, each person can apply their look (useful if one wants a highly readable theme on a wall tablet and another prefers a darker theme on mobile).

Regarding areas, editing becomes faster: on certain pages, a shortcut from the edit button allows you to directly modify the “main” sensors of a room, such as temperature or humidity.

Quick search Ctrl/⌘+K: the “command center” of Home Assistant

If you like to control via keyboard, this is probably the most addictive novelty. The “quick bar” has been completely rethought and is now called Quick search. The idea is: a single search to do everything, with filters by categories (navigation, commands, entities, devices, areas). Universal shortcut: ⌘+K on macOS, Ctrl+K on Windows/Linux.

This is not just a “name” search. You can search for a room, a type of device, trigger an action, open a specific screen… and everything can be navigated by keyboard (arrows, Enter, Escape). In the official presentation, the team really emphasizes this “muscle memory” aspect: once you get the reflex, you navigate through the instance without touching the mouse.

Good news: the old shortcuts remain useful. The “e”, “d”, “c” keys continue to function but open Quick search directly filtered (entities, devices, commands). So you’re not losing your habits; they are being modernized.

Automations: triggers and conditions that “speak your language”

Home Assistant continues to push its “purpand conditions”, available via Home Assistant Labs. The goal is simple: stop reasoning in ultra-technical “state change” and choose blocks that express a clear intention.

With the 2026.2 update, new triggers arrive, notably for calendars (event start/end), people (arrives home / leaves home), and vacuums (returns to base).
A very concrete example: “When Elise leaves the house, set the heating to eco” and activate to manually handle home/not_home states or sometimes obscure attributes. The same idea with “when the vacuum returns to its base, notify the end of the cycle”, or “when a calendar event starts, switch the house to presence mode”.

The big step forward in February is especially the “purpose-specific” conditions that are finally expanding into many areas. We can now express “if the lock is locked”, “if the heating is in heating mode”, “if the alarm is armed”, “if a person is at home”, “if the vacuum is docked”, “if the lawn mower is mowing”, etc., without manually comparing states.
For installers, it’s a little gem: these blocks reduce logical errors and make automations easier to read, thus easier to maintain over time.

Add-ons become “Applications”

This is a change of vocabulary… but not only. From 2026.2, add-ons are called Applications, with a very down-to-earth explanation: “add-ons” and “integrations” look too similar for a newcomer, while “app”, everyone knows what that is.

Home Assistant also clarifies the difference, and it’s important when troubleshooting someone (or a client): an Application is an application that runs alongside Home Assistant (code editor, MQTT broker, Node-RED, etc.), while an integration is the connector that links Home Assistant to a device or service.

The Applications interface has also been “replaced under the hood” to become more responsive while still remaining visually familiar.

Device database: the discreet project… but potentially huge

Home Assistant also highlights a project carried by the Open Home Foundation: an open database of devices, powered by the community, using real (and anonymized) installation data. The team clearly speaks of a “Wikipedia of smart devices”, with the goal of answering very practical questions before purchase: does this product expose this specific sensor? Does it work locally? Through which integrations and protocols?

Concretely, this comes through Home Assistant Labs: you can “opt-in” to share aggregated and anonymized information about your devices. A “Device analytics” section then appears, and you can even preview what is sent.

At the time of the announcement, Home Assistant already indicates over 10,000 unique devices reported across more than 260 integrations, giving an idea of the project’s traction. In the long term, the ambition is also to improve the “plug & play” experience, with better icons, units, and pre-configured categories when a device is recognized.

New “Distribution” card: visualize distributions at a glance

Home Assistant introduces a new dashboard card: Distribution card. It displays a distribution in the form of a proportional horizontal bar, with an interactive legend (hide/show an item, recalculate percentages, click to open details).

On paper, it’s “just a graph”, but there are very home automation uses. For example, energy: visualize the share of consumption by major category (heating, hot water, EV charging, servers/NAS, etc.) or the instant power distribution by phase if you’re closely monitoring your installation.

Energy: finally more flexible with certain power sensors

A small point that will please those who tinker with meters, clamps, or solar integrations: the Energy dashboard now accepts power sensors in other formats without going through a template sensor. Home Assistant notably indicates the possibility of using a single sensor with reversed polarity for grid/battery, or two separate positive sensors for charge/discharge (import/export). A change that will certainly simplify our lives!

Developer tools moved to Settings (and a sidebar that could evolve)

The Developer Tools are moving to the Settings section. The stated goal: to group everything related to “administration/system” in one place and lighten the interface. Home Assistant acknowledges that this requires an adjustment period and even mentions a track awaited by many: a complete sidebar customization in the future.

The idea is also not to “put under the nose” of non-technical users the technical tools, while making access to settings more coherent.

Integrations: news, improvements, and even more “everything in UI”

As every month, there are new integrations. Among the highlighted new features in the official announcement, we find for example Cloudflare R2 (cloud backups, with an interesting positioning on costs), but also energy-oriented integrations, ventilation, air quality, HDMI/AV video, or local EV charging depending on the case.

Another very “practical” point: several integrations are now configurable directly from the interface, without YAML. Home Assistant specifically mentions Namecheap DynamicDNS, OpenEVSE, Proxmox VE and WaterFurnace. And yes, seeing Proxmox VE becoming UI configurable is the kind of detail that makes all those with a “serious” home automation stack smile :D

What to remember

If you are installing Home Assistant for the first time (or helping relatives, clients, or on a project), 2026.2 is very good news: the default Overview, assistance with organizing devices, and the renaming of Apps/Integrations reduce misunderstandings right from the start.

If you are an advanced user, the winning duo is Quick search and “purpose-specific” automations. The former saves you time on every navigation, and the latter saves you time on every scenario… and prevents you from making “fragile” automations based on low-level states.

And if you are interested in home automation in general, keep an eye on the device database: this is the kind of foundation that, once sufficiently populated, changes the way of choosing hardware (and understanding why “it works for one, but not for another”).