How to Build Your First Home Assistant Dashboard With Lovelace Cards

A fresh Home Assistant install hands you an auto-generated dashboard that works but rarely fits how you actually live in your home. Lovelace cards are how you fix that: drop entities into the right card types, arrange them on a grid, split them across tabbed views, and you turn a messy default page into a clean control centre. The best part is you can do nearly all of it visually, dragging and dropping, with no code required.

Quick Answer

Build a Home Assistant dashboard by opening the visual editor, then adding cards that suit each device: entity and entities cards for lists, button cards for one-tap toggles, gauge cards for sensor values, and picture-glance to overlay controls on a room photo. Group related cards into tabbed views by room or function. The whole process is drag-and-drop in the UI editor, so beginners never need to touch YAML.

Understanding the building blocks first

Three concepts make everything else click into place. Entities are the individual devices, sensors, and services in Home Assistant, things like your living-room lamp or an outdoor temperature sensor. Cards are the visual containers that display and control those entities. Views are the tabs or pages that hold groups of cards. You place entities into cards, and cards onto views. Once that hierarchy makes sense, building a dashboard is just deciding what goes where.

Step 1: Open the visual editor

On your dashboard, click the three dots in the top right and choose Edit Dashboard. This opens the UI editor, the graphical interface that lets you add, arrange, and configure cards without writing a line of code. It is the recommended starting point for beginners, because every change is visual and reversible. Before you start rearranging heavily, it is worth taking a backup of your configuration so you can roll back if an experiment goes wrong.

Step 2: Add your first entity card

Click to add a card and pick the entity or entities card. The entities card shows one or more devices as a tidy vertical list, which is the workhorse for grouping related controls, all your living-room lights, say, in one block. Select the entities you want from the list, and they appear stacked in the card. This single card type will cover a large share of any dashboard, so get comfortable with it first.

Step 3: Add button cards for quick actions

For controls you trigger constantly, a button card is better than a list. The entity-button card is a built-in type that shows a single large, tappable icon, ideal for toggling a light or scene with one press. Place buttons for your most-used actions where your thumb naturally lands, since most people use Home Assistant on a phone. A row of buttons for your common scenes makes the dashboard feel like a proper app rather than a settings page.

Step 4: Add a gauge card for sensor values

When you want to see a number at a glance, the gauge card displays a sensor value as a visual dial with a configurable name. Use it for things like temperature, humidity, or battery level, where a sweeping gauge reads faster than a bare figure. Point it at the relevant sensor entity, give it a clear label, and you have an instant readout that stands out on the page.

Step 5: Try a picture-glance card

For something more visual, the picture-glance card overlays multiple entity controls on top of an image. Use a photo of a room as the background and place that room's light, switch, and sensor icons over it, so you tap controls directly on a picture of the space. It is one of the most satisfying card types for a polished, at-a-glance layout, and it makes a dashboard genuinely pleasant to use.

Step 6: Split everything into views

A single endless page becomes unwieldy fast. Views are the tabs across the top of your dashboard, and the fix is to organise them by room or by function. Put lighting on one tab, climate on another, security on a third, or split by room: lounge, kitchen, bedroom. The widely recommended approach is to avoid one monolithic dashboard and instead give each area its own view, keeping every screen focused and quick to navigate.

Step 7: Tidy the layout and test on mobile

Finally, arrange the cards on the grid by dragging them into a sensible order, with your most-used controls and most important information near the top. Then check it on your phone, because the large majority of interactions happen on mobile, so the layout has to read well on a small screen. Adjust, test, and refine. Start simple and add cards and views as you bring more devices online, rather than trying to build the perfect dashboard in one sitting.

As you expand, browsing the Evetech smart home and appliances section turns up compatible sensors and switches that appear as new entities to drop onto your dashboard, and handy extras for the setup turn up among the most popular accessories.

Frequently Asked Questions

Do I need to know YAML to build a Lovelace dashboard?

No. The UI editor lets you add, arrange, and configure cards entirely through drag-and-drop, which is the recommended path for beginners. YAML is available for advanced customisation later, but you can build a complete dashboard without it.

Which card type should I use for a light or switch?

For a single quick toggle, a button card gives you a large tappable icon. For grouping several lights or switches together, an entities card lists them neatly. Picture-glance works well when you want controls overlaid on a room photo.

How should I organise my dashboard?

Split it into views by room or by function rather than cramming everything onto one page. Put lighting, climate, and security on separate tabs, or give each room its own view, and keep frequently used controls near the top where they are easy to reach.

What is the difference between a view and a card?

A card is a single container that displays and controls one or more entities. A view is a tab or page that holds a group of cards. You place entities into cards, then place cards onto views to organise the whole dashboard.

Why does my dashboard need to work on mobile?

Because most people control Home Assistant from their phone. A layout that looks fine on a desktop can be cramped on a small screen, so test on mobile and keep the most important cards and controls prominent and within easy thumb reach.