<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dashboards on Rusty Bower</title><link>https://www.rustybower.com/categories/dashboards/</link><description>Recent content in Dashboards on Rusty Bower</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© Rusty Bower</copyright><lastBuildDate>Mon, 26 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.rustybower.com/categories/dashboards/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Home Assistant Dashboard with Whole Home Audio Control</title><link>https://www.rustybower.com/posts/home-assistant-dashboard-whole-home-audio/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://www.rustybower.com/posts/home-assistant-dashboard-whole-home-audio/</guid><description>&lt;p&gt;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&amp;rsquo;s how I built it, with a focus on the whole home audio system that ties everything together.&lt;/p&gt;</description></item><item><title>Building a Self-Updating Dashboard with Homepage and Kubernetes</title><link>https://www.rustybower.com/posts/homepage-kubernetes-service-discovery/</link><pubDate>Sat, 17 Jan 2026 00:00:00 +0000</pubDate><guid>https://www.rustybower.com/posts/homepage-kubernetes-service-discovery/</guid><description>&lt;p&gt;One of the challenges of running a homelab with dozens of services is keeping track of what&amp;rsquo;s running and where. I recently deployed &lt;a href="https://gethomepage.dev/" target="_blank" rel="noreferrer"&gt;Homepage&lt;/a&gt; - a modern, fully static dashboard that automatically discovers services from Kubernetes ingresses.&lt;/p&gt;</description></item></channel></rss>