How to Customize Your Home Assistant Dashboard in 2026

This post may contain affiliate links. As an Amazon Associate we earn from qualifying purchases. Disclosure.

Home Assistant's Lovelace dashboards have been around since 2018. The gap between the default auto-generated view and a properly customized dashboard is enormous. This guide walks through every layer: built-in cards, HACS custom cards, sections layout, room-by-room organization, themes, and mobile optimization.

TL;DR: Home Assistant's Lovelace dashboard supports full manual customization via YAML or the visual editor. Installing HACS unlocks custom cards like Mushroom and mini-graph-card that make dashboards far more usable. Start with auto mode, export the YAML, then rebuild manually room by room.

New to the platform? Our getting started with Home Assistant guide (linked below) covers installation before you get to the dashboard.

Auto Mode vs Manual Mode: Which Should You Use?

Auto mode in Lovelace builds a dashboard automatically from every entity in your system. It's useful for day one. After that it becomes a mess, every sensor, every attribute, every helper floods a single scrollable wall. Manual mode gives you a blank canvas. You place exactly what you want, where you want it. For a card-by-card reference on what each option does, our guide to Lovelace cards is the place to start.

Switching is simple. Go to Settings > Dashboards, click the three-dot menu on your main dashboard, and select "Take control." Home Assistant exports the auto-generated YAML so you can use it as a starting point. Doing this first saves manually re-adding device entities you'd otherwise have to hunt down.

Auto mode stops being usable sooner than most people expect, usually somewhere in the first few dozen devices. Switching to manual and rebuilding room by room is a one-off job, and it pays for itself the first time someone else in the house asks where the bedroom light is.

What Are the Essential Built-In Lovelace Cards?

The built-in cards ship with every Home Assistant install and require no extra packages. They cover most common use cases when arranged thoughtfully.

Entities card is the workhorse. It lists multiple entities in a compact stack and supports header/footer rows, secondary info display, and toggle icons. Use it for grouped lights or climate controls within a single room section.

Glance card shows a row of entities with icons and states. It's ideal for a quick overview row at the top of a dashboard, think: all motion sensors in one glance. It doesn't allow direct control, which keeps the display clean.

Gauge card renders a half-circle gauge for numeric values like temperature, humidity, or battery level. Set min/max and severity ranges with color thresholds.

History graph card plots entity state history over a configurable time window. Use it to track energy usage, temperature swings, or door open frequency.

Map card plots device trackers and zones on an embedded map. If you're tracking family member locations or robot mower boundaries, this card earns its place on a dedicated "Family" dashboard view.

Picture elements card overlays entity controls on top of a floor plan image. It's the most complex built-in card but produces the most impressive result. Upload a PNG floor plan, then place light switches, sensor badges, and climate controls exactly where the physical devices sit.

Which HACS Custom Cards Are Worth Installing?

Before any of these work, you need HACS itself, our guide on installing HACS (linked below) walks through the current device-code setup flow.

HACS hosts a large number of community frontend repositories, and most aren't worth your time. These five are a sensible shortlist.

Mushroom Cards (github.com/piitaya/lovelace-mushroom) is one of the most widely used custom card sets in the HACS ecosystem. It replaces most default cards with modern pill-shaped designs that scale well on both desktop and mobile. Install the whole package, it's a single HACS entry.

mini-graph-card produces far cleaner graphs than the built-in history card. It supports bar charts, area fills, multi-entity overlays, and custom color gradients.

button-card by RomRider is among the most flexible cards in HACS. It renders any entity as a customizable button with Jinja2 templates for labels, icons, styles, and actions. Steep learning curve. Worth every minute once it clicks.

apexcharts-card brings interactive charts, zooming, panning, multiple axes, to any Lovelace dashboard. It uses the ApexCharts.js library under the hood, which makes it a natural fit for overlays such as production against consumption once that data lives in Home Assistant.

layout-card unlocks CSS Grid-style layouts in Lovelace. It lets you break out of the default vertical column stack and arrange cards in truly arbitrary grids.

Most guides recommend button-card as a beginner pick. It isn't. Start with Mushroom, get comfortable with the sections layout, then add button-card once you understand Jinja2 templates. Jumping straight to button-card frustrates most newcomers into abandoning customization entirely.

How Do You Build a Mobile-Friendly Dashboard Layout?

The "sections" layout is now the default view type in Home Assistant, according to the dashboard documentation. It arranges content in sections on a grid, and you can drag sections and cards around in the editor.

Create a new dashboard view, select "Sections" as the layout type, and set the maximum columns to 4 for desktop. Narrow screens get fewer columns. Check how cards span columns in the layout options, so wide cards take more space and small status indicators take less.

Use Mushroom chips for a compact top row on mobile. The mushroom-chips-card packs several quick-glance entities into a single horizontal bar. That one row replaces what would otherwise be a stack of separate cards.

How Should You Organize Your Dashboard Room by Room?

Room-by-room organization is the fastest way to make a dashboard actually usable for non-technical household members. Create one dashboard view per floor or functional zone: Ground Floor, First Floor, Garden, Energy.

Within each view, use a section per room. Each section gets a title (Living Room, Kitchen, Bedroom 1) and contains only cards relevant to that space. A typical room section includes: one Mushroom light control, one climate indicator, one motion sensor state, and optionally a history graph for temperature.

Of the two approaches, one dashboard with many sections or one view per floor, the multi-view layout is the one I'd recommend for families: people tap through to a named tab rather than scrolling a long page looking for their room.

Conditional cards help keep things tidy. Use conditional card type to show a media player card only when something is actually playing. Dead cards cluttering a dashboard are more confusing than having no card at all.

How Do Themes Work in Home Assistant?

Home Assistant supports YAML-defined themes that override CSS variables across the entire UI. The built-in theme selector lives at your profile page (click your name in the sidebar). A growing library of community themes is available via HACS under the "Themes" category.

Switching themes via automation is where it gets interesting. Pair a time-of-day or sun elevation trigger with frontend.set_theme service call to shift automatically between a bright daytime theme and a dark nighttime theme. Here's a minimal automation trigger example:

trigger:
  - platform: sun
    event: sunset
action:
  - service: frontend.set_theme
    data:
      name: slate

The slate theme ships with Home Assistant by default. For dark mode, community themes such as the Mushroom theme in HACS are designed to complement Mushroom cards.

How Do Conditional Cards and Decluttering Templates Work?

Conditional cards reduce noise. Add a conditional wrapper around any card and it only renders when a specified entity meets a condition. A lock card that appears only when the front door is unlocked. A water leak sensor card that appears only when wet is detected. These aren't luxuries, they make the dashboard genuinely usable at a glance.

decluttering-card (HACS) takes this further by letting you define card templates with variables. Define a "room_card" template once with placeholder variables for room name, light entity, and climate entity. Then instantiate it once per room with a short YAML block each. That cuts dashboard YAML down dramatically.

How Do You Back Up and Share Your Dashboard?

Dashboard configuration lives in config/ui-lovelace.yaml (manual mode) or in .storage/lovelace (stored mode). Both are included in the standard Home Assistant backup. The backup UI is under Settings > System > Backups, run one before any major dashboard restructure.

To share a dashboard layout, export the raw YAML from the visual editor (three-dot menu > Edit in YAML) and paste it to a GitHub Gist or the Home Assistant Community forum. Others can import it directly. The official Home Assistant dashboard documentation covers every built-in card type with full YAML references, bookmark it. The HA Community forum (community.home-assistant.io) hosts hundreds of dashboard YAML shares in the "Share your Projects" section, it's the fastest way to learn what's possible.

A final piece of advice: build the dashboard for the person who'll actually use it, not for yourself at 11 PM mid-project. The fancy graph card you love means nothing if your partner just wants a big button that says "Goodnight." The sound pattern is one dense admin view for tuning and one stripped-back family view with a handful of large controls. The second one is the screen everyone but the tinkerer will actually tap, and it's what makes the whole setup get used instead of resented.

Once the dashboard looks right, our best Home Assistant integrations roundup is the next step for filling those cards with more data.