Setting Up Home Assistant Lovelace Cards and Dashboard Views

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

Quick take: The fastest way to build a useful Home Assistant dashboard is to start with the Entities card for room overviews, add Gauge cards for numeric sensors like temperature and humidity, and use Glance cards for dense status views. I set up my first functional dashboard in about 30 minutes using just those three card types. Custom cards from HACS look better but aren't necessary to start.

This guide covers setting up a useful Home Assistant dashboard, which is one of the first things most people do after getting devices integrated. The dashboard is where you actually interact with your smart home day-to-day, and getting the cards right makes a real difference in how often you actually use it versus reaching for the original manufacturer app.

The Lovelace system (now officially called Dashboards in recent HA releases, though the term Lovelace still appears everywhere in documentation and community forums) organizes everything into cards. Each card displays one or more entity states, provides controls, or shows historical data. Understanding which card type fits which use case is what separates a useful dashboard from a frustrating one.

What Is the Lovelace Dashboard in Home Assistant?

The dashboard is the primary interface for Home Assistant. It's the page you see when you open the Home Assistant web UI or the companion app. Everything on it consists of cards arranged in a grid layout across one or more views.

The official Home Assistant Lovelace documentation describes the system as a flexible card-based interface that you configure through the UI or YAML. The UI editor is fine for most setups. YAML gives you more control and lets you version your configuration in git, but it requires more time to learn.

Each dashboard contains views (the tabs across the top). Each view contains cards. That's the whole structure: dashboards contain views, views contain cards, and cards display entities. A newly installed Home Assistant instance comes with one default dashboard called Overview with a single default view. The initial auto-generated layout adds cards automatically based on your integrated devices, which is a reasonable starting point but rarely what you'll want long-term.

You can have multiple dashboards, which is useful if different household members want different layouts, or if you want separate dashboards for different purposes (one for home controls, one for energy monitoring, one for security cameras).

How Do You Add and Edit Cards?

Entering edit mode is how all dashboard changes happen. Click the three-dot menu in the top-right corner of any dashboard and select Edit Dashboard. This switches the view to editing mode with a pencil icon on each existing card and an Add Card button in each section.

To add a new card, click Add Card. A card picker dialog appears showing all available card types. Select one, and a configuration panel opens on the right. Most cards have a graphical editor where you pick the entity or entities to display. Click Save when done.

To modify an existing card, click the pencil icon that appears on it in edit mode. The same configuration panel opens with your current settings. Change what you need and save.

The key thing to know about editing: changes in the UI editor save immediately to your configuration. There's no separate deploy step. If you switch to YAML editing for a card, clicking Save writes the YAML to your dashboard config. You can switch between UI and YAML editing for individual cards, but once you've edited a card in YAML, the UI editor may no longer be available for that card type (some YAML-only features disable the visual editor).

Which Card Types Are Most Useful?

Home Assistant ships with roughly 20 built-in card types. Most people use 5 to 6 regularly.

The main card types worth knowing:

• Entities card: shows a list of entities with their current state and optional controls. The workhorse of most dashboards. You can put a whole room's worth of devices in one card.
• Glance card: a compact grid showing entity states as icons and values. Good for quick status overviews when you don't need per-entity controls.
• Gauge card: a semicircle meter showing a numeric value against a min/max range. Ideal for temperature, humidity, CO2 level, and battery percentage.
• Button card: a single tap control for a switch, script, or scene. Use it for one-tap actions you want prominently visible.
• Entity card: shows a single entity with full detail including state history sparkline. Better than the Entities card when one entity deserves focused attention.
• History graph card: a line chart of an entity's state over time. Useful for temperature trends, energy usage patterns, and sensor history.
• Logbook card: shows a list of state changes for one or more entities. Helpful for troubleshooting and reviewing when devices changed state.
• Thermostat card: a circular control for climate entities. Shows current temperature, target temperature, and HVAC mode with a visual dial.

For a starting dashboard layout, I'd suggest: one Entities card per room (all lights and switches in that room), Gauge cards for temperature and humidity sensors, and one Glance card at the top for a whole-home status summary. That covers 80% of what you'll actually look at daily.

Configuring the Entities Card

The Entities card is flexible enough that it's worth understanding in more detail. In addition to listing entities, it supports:

• Custom headers and dividers to group entities within one card
• Optional state-color badges (the icon changes color based on state)
• Tap actions (tap an entity row to navigate to a detail page or run a service)
• Hiding entities from the list based on their current state

The most useful configuration option is the header. Add a header with the room name and the card becomes a labeled room control panel. One card per room, one label per card.

When to Use Glance vs Entities

The choice between Glance and Entities comes down to whether you need controls or just status. Entities cards give you toggle switches and sliders you can interact with. Glance cards show state compactly but with limited interaction by default. Use Glance for "how are things right now?" and Entities for "I need to change something."

How Do Views Organize a Dashboard?

Views are the tabs at the top of a dashboard. A single-view dashboard works fine for a small setup. Once you're managing 20+ entities, organizing by room or category into multiple views makes everything faster to navigate.

The default view type is "Masonry", which arranges cards in a responsive grid and fills columns automatically. The "Panel" view type dedicates the full width to a single card (useful for a full-screen map or camera feed). The "Sidebar" view type puts one wide card on the right and stacks smaller cards on the left.

Creating a view takes 30 seconds: click the plus icon next to the existing view tabs, give it a title and optionally an icon, and it appears in the tab bar. You can reorder views by dragging in edit mode. Icons for views use the Material Design icon set (mdi:home, mdi:lightning-bolt, mdi:thermometer, etc.).

A layout that works well for most homes: a Summary view with a Glance card for whole-home status, then separate views for Lights, Climate, Security, and Energy. Navigation becomes much faster than scrolling a single long view.

What About Custom Cards and HACS?

Home Assistant's built-in cards are functional but visually dated compared to the custom card ecosystem. HACS (Home Assistant Community Store) is a third-party add-on that makes installing community-built cards straightforward. It's not part of the official installation but it's widely used.

Popular custom cards worth knowing about:

• mini-graph-card: a more flexible and visually polished version of the history graph card, with multiple entity comparison and color gradients
• button-card: a highly configurable replacement for the Button card, supporting custom templates, icons, and styles based on entity state
• mushroom cards: a complete redesign of the standard entity controls with a modern look, widely used in community dashboards
• apexcharts-card: advanced charting for numeric sensor data, supports stacked bars, area charts, and custom time ranges

Should you install HACS and custom cards early? Not necessarily. Custom cards require maintenance when Home Assistant updates. Built-in cards work reliably across every update. My recommendation: build your dashboard with built-in cards first, get your layout working, then selectively add custom cards where the built-in options genuinely fall short.

Summary

Setting up Home Assistant's Lovelace dashboard starts with understanding that everything is a card, cards live in views, and views live in dashboards. The Entities card handles most room-based layouts. Gauge cards work for numeric sensors. Glance cards give quick status overviews. Adding a view per room or category keeps navigation fast as your device count grows. Custom cards through HACS improve the visual design but aren't required for a functional setup. Start with built-in cards, validate your layout actually works for daily use, and upgrade individual cards where they fall short.