# jimmy-landry/ha-tablet-dashboard-config architecture

> Architecture diagram of the GitHub repository jimmy-landry/ha-tablet-dashboard-config, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-29). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/jimmy-landry/ha-tablet-dashboard-config
- Repository: https://github.com/jimmy-landry/ha-tablet-dashboard-config

## Overview

##### Main Components
- Home Assistant Server (Backend): Represent the HA instance running on the Raspberry Pi 3B+ where all the configuration (including the dashboard setup, templating, and sensors) is loaded.
- Dashboard Configuration Files: Show the YAML files (such as theme.yaml and wall_tablet_grid_redacted.yaml) that define the dashboard’s layout, themes, and behavior.
- Tablet Frontend (Dashboard Client): Represent the Amazon Fire HD 10 running Android with the WallPanel app, which consumes the HA dashboard configuration and renders the user interface based on the provided themes and layouts.
- (Optional) Additional HA Configuration: Include any optional sensors and custom automations (like the date/time and weekday sensors mentioned in the README) that interact with the dashboard.

##### Relationships and Interactions
- That the HA Server loads and applies the YAML configuration files (themes, dashboard layout, sensor definitions) at startup.
- Integration points where HACS custom cards are embedded into the dashboard, indicating how they enhance or modify the UI.

##### Architectural Patterns and Techniques
- Configuration-as-Code: The entire dashboard is defined via YAML files (configuration files), meaning that the logic, layout, and theming are externalized and version-controlled.
- Modular UI Components: The use of multiple custom cards (each provided by a different repository) illustrates a modular, plug-and-play approach to building the UI.
- Custom Theming: A dedicated theme.yaml is provided to define a unique visual style, which is applied across the dashboard.
- Frontend/Backend Separation: Although it is a configuration repository, the architecture cleanly separates the backend (HA and configuration files) from the frontend (the rendering on the tablet).

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Dashboard Configuration Group
    subgraph "Dashboard Configuration"
        direction TB
        T1["theme.yaml"]:::config
        W1["wall_tablet_grid_redacted.yaml"]:::config
        HACS["Custom HACS Integrations<br/>(layout-card,button-card,<br/>vertical-stack-in-card,<br/>lovelace-mushroom,<br/>mini-media-player,<br/>browser-mod,simple-weather-card,<br/>card-mod 3,Custom Brand Icons)"]:::integration
    end

    %% Backend Group
    subgraph "Backend"
        direction TB
        HA["Home Assistant Server (Raspberry Pi 3B+)"]:::backend
        SENSORS["Additional HA Configuration<br/>(Sensors & Automations)"]:::config2
    end

    %% Tablet Frontend
    TABLET["WallPanel Tablet Client (Android on Fire HD 10)"]:::tablet

    %% Relationships
    T1 --> HA
    W1 --> HA
    HACS --> HA
    SENSORS --> HA
    HA -->|"dashboard_UI"| TABLET

    %% Click events
    click T1 "https://github.com/jimmy-landry/ha-tablet-dashboard-config/blob/main/theme.yaml"
    click W1 "https://github.com/jimmy-landry/ha-tablet-dashboard-config/blob/main/wall_tablet_grid_redacted.yaml"
    click HA "https://github.com/jimmy-landry/ha-tablet-dashboard-config/blob/main/README.md"

    %% Styles
    classDef backend fill:#fceabb,stroke:#fcbf1e,stroke-width:2px;
    classDef config fill:#a0d8ef,stroke:#1f77b4,stroke-width:2px;
    classDef integration fill:#d2a6ff,stroke:#512da8,stroke-width:2px;
    classDef tablet fill:#ffcccb,stroke:#e53935,stroke-width:2px;
    classDef config2 fill:#e0f8d8,stroke:#388e3c,stroke-width:2px;
```
