# Mission Control Dashboard — TLC Project **Status: Parked (awaiting direction decision) — Needs Consolidation & Refresh **Created: 2026-02-17 (Next.js) / 2026-02-20 (Python) **Goal:** Combine both dashboards into one unified system --- ## Current State We have **TWO** Mission Control dashboards: ### 1. Next.js Dashboard | Attribute | Value | |-----------|-------| | **Location** | `C:\web\htdocs\mission-control` | | **URL** | http://localhost:3000 | | **Tech** | Next.js 14, TypeScript, Tailwind | | **Status** | ✅ Running but needs updates | | **Features** | Project cards, Kanban boards, Status widgets, Themes | ### 2. Python/Flask Dashboard | Attribute | Value | |-----------|-------| | **Location** | `C:\web\htdocs\mission-control-py` | | **URL** | http://localhost:5050 | | **Tech** | Python/Flask, MySQL, HA API | | **Status** | ✅ Running but needs updates | | **Features** | Admin CRUD, Weather, Gateway status, Projects | --- ## The Problem Two dashboards doing similar things. Need to: | Decision | Status | |----------|--------| | **Pick one as primary?** | Undecided | | **Merge features?** | Undecided | | **Start fresh?** | Option on table | --- ## Features to Preserve (From Both) ### From Next.js Version: - ✅ Project cards with Kanban boards - ✅ Drag-and-drop task management - ✅ Real-time status widgets (Gateway, Discord, Cron) - ✅ 4 themes (NASA Retro, Luxury Commander, Cyberpunk, Organic) - ✅ Knowledge base reference cards - ✅ GLaDOS voice control integration ### From Python Version: - ✅ MySQL persistence (vs JSON files) - ✅ Home Assistant API integration - ✅ Weather widget - ✅ Admin CRUD interface - ✅ News tracking - ✅ Gateway status with real endpoints --- ## Known Issues / TLC Needed | Issue | Dashboard | Priority | |-------|-----------|----------| | Status widgets outdated | Both | High | | Memory system not integrated | Both | High | | Mobile responsiveness | Next.js | Medium | | Theme switching flaky | Next.js | Low | | No unified data source | Both | High | --- ## Possible Directions ### Option A: Refactor Next.js - Keep Next.js as frontend - Add MySQL backend (like Python version) - Port Python features over - Add memory system widgets ### Option B: Enhance Python - Keep Python as primary - Add theme system from Next.js - Better UI/UX polish - Mobile responsiveness ### Option C: Start Fresh - New tech stack (Svelte? Vue?) - Learn from both versions - Design unified architecture - Full rebuild ### Option D: Hybrid API - Python as backend API - Next.js as frontend - Separate concerns properly --- ## Next Steps (When We Pick This Up) 1. **Audit both dashboards** — what works, what doesn't 2. **Decide architecture** — A, B, C, or D 3. **Design unified schema** — data models, APIs 4. **Migrate/merge features** — one dashboard to rule them all --- **Notes:** - Frigate is ✅ working (Docker) - UniFi is 🟡 parked (auth issues later) - This project is on hold until direction decided --- *Trigger words: dashboard tlc, mission control refresh, combine dashboards, dashboard v2*