Daedalus Dashboard Project
After years of building and rebuilding dashboards in Home Assistant, I kept running into the same structural problem:
dashboards grow organically… until they become inconsistent, hard to navigate, and eventually require a full redesign.
So instead of redesigning again, I started working on something different:
an interface architecture designed to scale over time.
This is a single view from Daedalus Dashboard (Climate - Status - Temperatures), but the structure behind it is what matters.
Daedalus Dashboard is not just a UI, but a design framework based on:
- user intent instead of device structure
- semantic consistency across all views
- predictable navigation with a fixed 4-level hierarchy
- dynamic layouts that adapt to context
The goal is simple:
reduce cognitive load and make interactions intuitive without training.
What makes it different?
Most dashboards mirror integrations, entities, or rooms.
Daedalus tries to answer a different question:
What is the user trying to do right now?
Everything—from domains to navigation flow—is built around that.
Current status
The project is in an early but structured phase:
- architecture defined
- design principles formalized
- conceptual model documented
I’ve published the initial documentation here:
Daedalus Dashboard Project
Looking for feedback & collaboration
I’m particularly interested in input from people who:
- have built complex dashboards
- struggled with long-term scalability
- care about UX consistency in HA
If this resonates, I’d love to hear your thoughts, criticism included.
The goal is not to build my dashboard, but something that could evolve into a shared design approach for complex Home Assistant setups.
A number of views (as the one in the screenshot above) are already implemented , and I’m currently expanding the system further.
If there’s meaningful interest from the community, I plan to publish the full implementation in the same repository and open it up for feedback and contributions.