How to Build a Smart Home Dashboard
The Problem That Started It All
About two years ago, I got tired of answering the same question from my wife: "Is the garage door closed?" We'd be lying in bed, and one of us would have that nagging feeling. I'd pull out my phone, open the myQ app, wait for it to load, realize I needed to log in again, wait some more, and finally confirm that yes, the garage door was closed. Total elapsed time: about 45 seconds that felt like five minutes.
I thought: what if there was just a screen on the wall that showed this stuff at a glance? No unlocking a phone, no opening an app, no waiting for some cloud server to respond. Just... look at the wall and know.
That's how my smart home dashboard obsession began. And after three iterations, a drawer full of abandoned tablets, and one very patient spouse, I've landed on something that my whole family actually uses every day.
Choosing a Dashboard Platform
I tried almost everything before settling on my current setup, so let me save you some time.
Where I Started: Apple Home on an iPad
This was my first attempt. I had an old iPad Air gathering dust, so I wall-mounted it next to the kitchen and set Apple Home as the default screen. It looked nice. For about a week. The problem is that Apple Home's dashboard is designed for a phone you're holding, not a wall display you're glancing at from six feet away. The tiles are too small, there's no way to customize what shows first, and it kept locking itself despite my Guided Access settings. I also couldn't display non-HomeKit devices, which ruled out half my setup.
Attempt Two: SharpTools
SharpTools is a web-based dashboard builder that connects to SmartThings, Hubitat, and Home Assistant. I liked that it was drag-and-drop and didn't require me to learn YAML. But the free tier is limited, and even on the paid plan, it felt like I was fighting the layout engine constantly. Everything was either too big or too small. I used it for about a month before moving on.
Where I Landed: Home Assistant Dashboards
If you're running Home Assistant -- and at this point I think most serious smart home people should be -- its built-in dashboard system is unmatched. The default Lovelace editor is fine for getting started, but the real magic happens when you install community card packs. I use Mushroom Cards for most of my interface, and the difference is night and day. Clean, modern, and actually designed to look good on a wall-mounted tablet.
The learning curve is real, though. My first Home Assistant dashboard was an ugly grid of toggle switches that looked like a 1990s control panel. It took me a solid weekend of experimenting with Mushroom Cards and custom layouts before I had something I was happy showing to other humans.
What Actually Goes on the Dashboard
Here's what I learned the hard way: your first dashboard will have too much on it. You'll want to show every sensor reading, every camera feed, every automation status. Resist that urge. After a few weeks, you'll notice you only look at five or six things.
What My Family Actually Uses
My current dashboard has three "pages" you can swipe between, but the main screen is the only one that gets used 90% of the time. Here's what's on it:
- Weather and outdoor temperature at the top -- everyone checks this before walking out the door
- Garage door status with a big open/close button -- the thing that started this whole project
- Front door lock status with lock/unlock
- Thermostat showing current temperature and setpoint, with quick up/down controls
- Four scene buttons: Good Morning, Good Night, Movie Mode, and Away
- Front door camera as a small live feed in the corner
That's it for the main screen. The second page has room-by-room light controls, and the third has energy monitoring and sensor data that only I ever look at. My wife uses the main screen daily. My kids use the scene buttons. Nobody has ever voluntarily swiped to page three except me.
The Scene Buttons Are the Killer Feature
I cannot overstate how much the scene buttons changed things. Before the dashboard, I had all these clever automations that nobody in my family could trigger because they didn't want to learn the Home Assistant app. Now my 10-year-old walks up to the wall, taps "Movie Mode," and the living room lights dim, the bias lighting behind the TV turns on, and the blinds close. She thinks it's magic. I think it's a YAML file with 30 lines in it, but I'll take the credit.
The Hardware: Finding the Right Display
The Amazon Fire Tablet Sweet Spot
After trying an old iPad, an old Android phone (too small), and briefly considering one of those expensive dedicated smart home panels, I landed on a Fire HD 10. Here's why: they go on sale for $75-80, the screen is big enough to read from across a room, and they run an app called Fully Kiosk Browser that turns them into a perfect dedicated dashboard.
Fully Kiosk Browser is the unsung hero of this whole setup. It keeps the screen on, wakes on motion (using the front camera), prevents kids from switching to YouTube, auto-refreshes the dashboard page, and dims the screen at night. It costs $7 for a license and it's worth ten times that.
Wall Mounting Without Destroying Your Wall
I used a 3D-printed wall mount from Thingiverse (search "Fire HD 10 wall mount" and you'll find dozens). The tablet clips in, and a right-angle USB-C cable runs down the wall to a plug hidden behind a small cable raceway. The whole installation took about 20 minutes and looks surprisingly clean. If I sell this house someday, I'll fill two small screw holes and you'd never know it was there.
One tip I wish someone had told me: mount it at standing eye level in a high-traffic area. I initially put mine in the hallway, and nobody used it because you had to make a detour to see it. I moved it to the kitchen, right next to the light switch by the back door, and usage went up immediately. People naturally glance at it when entering or leaving.
Dealing with Screen Burn-In
This scared me at first. An always-on screen showing the same layout seemed like a recipe for burn-in. After 18 months, here's what I can report: no burn-in on the Fire HD 10. LCD screens are much more resistant to it than OLED. That said, I do take precautions:
- Dark theme -- Mushroom Cards has an excellent dark mode that looks great and reduces pixel fatigue
- Screen dimming -- Fully Kiosk drops brightness to 5% between 11 PM and 6 AM
- Motion wake -- the screen goes to a dim clock face after 2 minutes of no motion, then lights up when someone walks by
If you go the iPad route, be more careful. OLED iPads can burn in. Stick with the LCD models for a wall dashboard, or use aggressive screen-off timers.
Mistakes I Made So You Don't Have To
A few things I'd do differently if starting over:
Don't build the dashboard first. I jumped straight into designing dashboards before my smart home was fully set up. The dashboard changed constantly as I added devices, and I wasted hours on layouts I scrapped. Get your devices and automations stable first, then build the dashboard around your actual daily patterns.
Don't put cameras on the main screen in full resolution. Camera feeds are cool but they eat bandwidth and slow down the dashboard. I use a small, low-resolution thumbnail on the main screen with a tap-to-fullscreen option. Much smoother.
Test with your least technical family member. I showed my dashboard to my mother-in-law during a visit. She couldn't figure out what half the icons meant. I replaced a bunch of clever icons with text labels, and suddenly everyone could use it. Pretty icons lose to readable text every time on a wall display.
Getting Started Without Overthinking It
If you want to try this, here's what I'd recommend as a starting point:
- Grab a Fire HD 10 tablet (wait for a sale if you can)
- Install Fully Kiosk Browser from the Amazon app store
- Set up a basic Home Assistant dashboard with your most-used controls -- start with just five or six things
- Prop the tablet up on a kitchen counter for a week before committing to wall mounting
- Pay attention to what you and your family actually tap, and ruthlessly remove everything else
The propped-up-on-the-counter phase is important. You'll learn more about what belongs on a dashboard in one week of actual use than in a month of planning. My "final" layout looks nothing like what I originally designed, and that's fine. The best dashboard is the one your household actually uses, not the one that looks coolest on Reddit.