How to Build a Home Assistant Dashboard Without YAML (Complete Practical Guide)

Okay, I get it. You set up Home Assistant because you wanted a smarter home — not because you wanted to learn a programming language. And then you opened your first dashboard tutorial and hit a wall of YAML: indentation errors, cryptic card configs, and that sinking feeling that your “quick weekend project” just became a semester-long course.

Here’s the good news: in 2026, you can build a genuinely great Home Assistant dashboard without writing a single line of YAML. I’ve done it, I’ll show you exactly how, and I’ll be honest with you about where the free tools shine and where they run out of road.

A companion video is coming, where I build the whole thing from a blank screen with a timer running. You won’t need it to follow along, though — every step is spelled out below, at your own pace.

What “without YAML” actually means now

A quick bit of history, because it explains why so much advice online is out of date. For years, building a custom Home Assistant dashboard meant hand-editing YAML — the configuration language that powers Lovelace under the hood. Then Home Assistant shipped the Sections view with real drag-and-drop, and they’ve been improving the visual editor almost every month since: an editor sidebar, an auto-generated Areas dashboard, a much smarter card picker.

Translation: the basics no longer require code. The question isn’t “can I avoid YAML?” anymore — it’s “how far can I get before I hit the ceiling?” Let’s find out.

What you’ll need

• A working Home Assistant install (any flavor — HAOS, container, doesn’t matter)
• Your devices already added (if a device works from the Overview page, you’re set)
• 20 minutes. Genuinely.

One tip before you start: give your rooms proper Areas in Home Assistant (Settings → Areas, labels & zones) and assign your devices to them. It’s five minutes of housekeeping that pays off in every step below.

Step 1: Start a fresh dashboard with the Sections view

Don’t fight your auto-generated Overview page — leave it alone and start clean.

1. Go to Settings → Dashboards → Add dashboard.
2. Pick “Start with an empty dashboard.”
3. Give it a name your family would recognize (“Home,” not “Lovelace-test-v2”).
4. Open it, hit the pencil icon, and add your first Section.

Sections are the magic here. Think of each section as a shelf: you drop cards onto it, drag them into order, and the shelf handles the arranging. No grid math, no column counts, no code.

Step 2: Let Areas do the boring work

Before you hand-place forty cards, try this: when you add a section, use the area shortcut — Home Assistant will offer to build a section from an Area, pre-filled with that room’s devices. It’s the fastest “blank page to something real” move in the entire platform, and it’s exactly how I start every build.

You’ll prune it afterward (auto-generated anything always needs pruning — more on that in Step 3), but starting from a populated page beats starting from zero every time.

Step 3: Add your cards — drag, drop, done

Now the fun part. In edit mode:

1. Add card → the picker now leads with your entities, not abstract card types. Search “kitchen light,” pick it, and it suggests sensible cards for it.
2. Use tile cards as your default. They’re compact, touch-friendly, and they show state at a glance.
3. Drag cards within and between sections until the layout feels right.
4. Be ruthless. Here’s my rule: if you haven’t tapped it in a week, it doesn’t belong on page one. Nobody needs the firmware version of their doorbell on the main dashboard.

My go-to structure: one section per room you actually control daily, plus one “glance” section up top — weather, who’s home, whether the garage is shut. That last one earns its spot every single day.

Step 4: Make it pretty with Mushroom (still no YAML)

Stock tile cards are fine, but if you want that clean, modern look you’ve seen on Reddit, the community answer is Mushroom — a free card collection installed through HACS.

Fair warning: installing HACS (the Home Assistant Community Store) is a one-time setup adventure of its own. But once it’s in, Mushroom cards configure entirely through the visual editor — pick a card, pick an entity, pick an icon color, done. No YAML unless you go looking for it.

Honest talk: where the free route runs out of road

I promised you honesty, so here it is. The free, no-YAML toolkit — Sections plus Mushroom — is genuinely enough for a lot of people. If what you want is a tidy grid of tiles organized by room, stop reading, you’re done, enjoy your dashboard.

But there’s a ceiling, and it’s not a skill-gap ceiling — it’s architectural:

• The grid is the grid. Sections auto-arrange everything into a responsive grid. You cannot put a card exactly there — pixel-perfect, freeform placement isn’t a missing feature, it’s incompatible with how the grid works. The Home Assistant team has said as much themselves.
• The moment you want logic, YAML is back. “Show this card only when someone’s home.” “Turn this tile red when the battery’s low.” Conditional display and state-driven styling are exactly where the visual editor ends and the code begins — usually via card-mod, which is a rabbit hole with its own dress code.
• Theming is a config-file affair. Real visual theming means editing theme YAML. There’s no visual theme designer in the box.

Think of it like a photo book service versus a blank scrapbook. The photo book (Sections) arranges everything neatly for you — fast, foolproof, and a little rigid. The scrapbook gives you total freedom, but you’re buying scissors and glue (YAML). For years, those were the only two options.

When you want more than the grid allows

This is where I reach for Dashable — a drag-and-drop dashboard builder for Home Assistant that runs in your browser. It’s the tool I use when the grid stops being enough: pixel-perfect placement (put the card exactly where you want it), conditional logic and state-based styling built visually instead of in YAML, and themes you design by clicking, not by editing config files.

Full honesty here too, because it matters: Dashable is a paid subscription, and the free tools above keep improving. If the Sections grid does what you need, use the Sections grid. But if you’ve ever spent an evening fighting card-mod to move something three pixels, or given up on “show this only when…” because the YAML made your eyes cross — that’s the exact gap Dashable exists to fill. You can build your first dashboard on it free and judge for yourself.

Troubleshooting the usual suspects

My new dashboard doesn’t show up on my phone. Check the dashboard’s visibility settings (Settings → Dashboards → your dashboard) and make sure it’s not admin-only. Then pull down to refresh in the app.

A card says “Entity not available.” The device dropped or got renamed. Tap the card in edit mode and re-pick the entity — and if you renamed devices recently, that’s your culprit.

Everything looks great on my laptop and cramped on my phone. Sections reflow by design. Check each section’s column span in edit mode, and remember: fewer, bigger cards beat many tiny ones on a phone.

I installed Mushroom but don’t see the cards. Clear your browser cache or do a hard refresh — HACS card installs are cached aggressively. It gets almost everyone once.

You’re 20 minutes away

That’s the whole guide: one empty dashboard, sections per room, tile cards, prune hard, Mushroom if you want it prettier. No YAML, no config files, no semester-long course. Your smart home deserves a front door that doesn’t need a manual — and honestly, so do you.

Stop wrestling with YAML and start building the interface you’ve always wanted. Visit dashable.app and build your first dashboard for free.