Dashboard

My Home Assistant dashboard has evolved significantly over the past year. What started as the default auto-generated cards has become a carefully organized interface that my whole family actually uses. Here’s how I built it, with a focus on the whole home audio system that ties everything together. Dashboard Philosophy Before diving into implementation, a few principles guided the design: Function over flash - Every card earns its screen space One-tap actions - Common tasks shouldn’t require drilling into menus Status at a glance - The overview tells you what’s happening without interaction Mobile-first - Tablets mounted around the house are the primary interface The Stack Lovelace YAML mode - Full control over layout and structure Mushroom cards - Clean, consistent UI components Custom Layout Card - Responsive grid layouts that work on any screen Stack-in-card - Grouping related controls together Overview Page The overview page is designed to answer “what’s happening right now?” at a glance: ...

One of the challenges of running a homelab with dozens of services is keeping track of what’s running and where. I recently deployed Homepage - a modern, fully static dashboard that automatically discovers services from Kubernetes ingresses. Why Homepage? I evaluated several dashboard options including Homarr and Heimdall. Homepage stood out for a few reasons: Kubernetes-native service discovery - no manual configuration needed Real-time pod status - shows if services are actually running Clean, modern UI - dark theme, customizable layout Lightweight - just a static site with no database The Setup Homepage runs as a simple deployment in Kubernetes with a ServiceAccount that has read access to the cluster. The magic happens through ingress annotations. ...