fix: address five review findings (NM retry loop, start_display message, code quality)

- wifi_monitor_daemon: reset _consecutive_internet_failures = 0 in both
  NM-restart exception handlers; previously both left the counter at threshold,
  causing an immediate retry on the next iteration instead of waiting another
  full backoff period

- api_v3: fix start_display failure message — when mode is set and systemctl
  returns non-zero, message now includes the failure reason and a hint rather
  than always reporting success phrasing

- wifi_manager: move _redirect_backend from class variable to instance variable
  in __init__ alongside _ap_enabled_at; class-level default shadowed correctly
  in practice (single instance) but was misleading

- wifi_manager: narrow broad except Exception in _check_internet_connectivity
  to (subprocess.SubprocessError, OSError) for ping and OSError for HTTP
  (urllib.error.URLError is an OSError subclass in Python 3)

- wifi_manager: remove redundant local 'import re as _re' in _validate_ap_config;
  re is already imported at module level (line 37)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.cursor/README.md

@@ -43,39 +43,48 @@ cp ../../.cursor/plugin_templates/*.template .
 2. **Using dev_plugin_setup.sh**:
 ```bash
 # Link from GitHub
-./dev_plugin_setup.sh link-github my-plugin
+./scripts/dev/dev_plugin_setup.sh link-github my-plugin
 
 # Link local repo
-./dev_plugin_setup.sh link my-plugin /path/to/repo
+./scripts/dev/dev_plugin_setup.sh link my-plugin /path/to/repo
 ```
 
-### Running Plugins
+### Running the Display
 
 ```bash
-# Emulator (development)
+# Emulator mode (development, no hardware required)
-python run.py --emulator
+python3 run.py --emulator
+# (equivalent: EMULATOR=true python3 run.py)
 
-# Hardware (production)
+# Hardware (production, requires the rpi-rgb-led-matrix submodule built)
-python run.py
+python3 run.py
 
-# As service
+# As a systemd service
 sudo systemctl start ledmatrix
+
+# Dev preview server (renders plugins to a browser without running run.py)
+python3 scripts/dev_server.py  # then open http://localhost:5001
 ```
 
+The `-e`/`--emulator` CLI flag is defined in `run.py:19-20` and
+sets `os.environ["EMULATOR"] = "true"` before any display imports,
+which `src/display_manager.py:2` then reads to switch between the
+hardware and emulator backends.
+
 ### Managing Plugins
 
 ```bash
 # List plugins
-./dev_plugin_setup.sh list
+./scripts/dev/dev_plugin_setup.sh list
 
 # Check status
-./dev_plugin_setup.sh status
+./scripts/dev/dev_plugin_setup.sh status
 
 # Update plugin(s)
-./dev_plugin_setup.sh update [plugin-name]
+./scripts/dev/dev_plugin_setup.sh update [plugin-name]
 
 # Unlink plugin
-./dev_plugin_setup.sh unlink <plugin-name>
+./scripts/dev/dev_plugin_setup.sh unlink <plugin-name>
 ```
 
 ## Using These Files with Cursor
@@ -118,9 +127,13 @@ Refer to `plugins_guide.md` for:
 - **Plugin System**: `src/plugin_system/`
 - **Base Plugin**: `src/plugin_system/base_plugin.py`
 - **Plugin Manager**: `src/plugin_system/plugin_manager.py`
-- **Example Plugins**: `plugins/hockey-scoreboard/`, `plugins/football-scoreboard/`
+- **Example Plugins**: see the
+  [`ledmatrix-plugins`](https://github.com/ChuckBuilds/ledmatrix-plugins)
+  repo for canonical sources (e.g. `plugins/hockey-scoreboard/`,
+  `plugins/football-scoreboard/`). Installed plugins land in
+  `plugin-repos/` (default) or `plugins/` (dev fallback).
 - **Architecture Docs**: `docs/PLUGIN_ARCHITECTURE_SPEC.md`
-- **Development Setup**: `dev_plugin_setup.sh`
+- **Development Setup**: `scripts/dev/dev_plugin_setup.sh`
 
 ## Getting Help
 

.cursor/plugin_templates/QUICK_START.md

@@ -156,11 +156,15 @@ def _fetch_data(self):
 
 ### Adding Image Rendering
 
+There is no `draw_image()` helper on `DisplayManager`. To render an
+image, paste it directly onto the underlying PIL `Image`
+(`display_manager.image`) and then call `update_display()`:
+
 ```python
 def _render_content(self):
-    # Load and render image
+    # Load and paste image onto the display canvas
-    image = Image.open("assets/logo.png")
+    image = Image.open("assets/logo.png").convert("RGB")
-    self.display_manager.draw_image(image, x=0, y=0)
+    self.display_manager.image.paste(image, (0, 0))
 
     # Draw text overlay
     self.display_manager.draw_text(
@@ -168,8 +172,18 @@ def _render_content(self):
         x=10, y=20,
         color=(255, 255, 255)
     )
+
+    self.display_manager.update_display()
 ```
 
+For transparency, paste with a mask:
+
+```python
+icon = Image.open("assets/icon.png").convert("RGBA")
+self.display_manager.image.paste(icon, (5, 5), icon)
+```
+
+
 ### Adding Live Priority
 
 1. Enable in config:

.cursor/plugins_guide.md

@@ -53,13 +53,13 @@ This method is best for plugins stored in separate Git repositories.
 
 ```bash
 # Link a plugin from GitHub (auto-detects URL)
-./dev_plugin_setup.sh link-github <plugin-name>
+./scripts/dev/dev_plugin_setup.sh link-github <plugin-name>
 
 # Example: Link hockey-scoreboard plugin
-./dev_plugin_setup.sh link-github hockey-scoreboard
+./scripts/dev/dev_plugin_setup.sh link-github hockey-scoreboard
 
 # With custom URL
-./dev_plugin_setup.sh link-github <plugin-name> https://github.com/user/repo.git
+./scripts/dev/dev_plugin_setup.sh link-github <plugin-name> https://github.com/user/repo.git
 ```
 
 The script will:
@@ -71,10 +71,10 @@ The script will:
 
 ```bash
 # Link a local plugin repository
-./dev_plugin_setup.sh link <plugin-name> <path-to-repo>
+./scripts/dev/dev_plugin_setup.sh link <plugin-name> <path-to-repo>
 
 # Example: Link a local plugin
-./dev_plugin_setup.sh link my-plugin ../ledmatrix-my-plugin
+./scripts/dev/dev_plugin_setup.sh link my-plugin ../ledmatrix-my-plugin
 ```
 
 ### Method 2: Manual Plugin Creation
@@ -321,7 +321,8 @@ Each plugin has its own section in `config/config.json`:
 
 ### Secrets Management
 
-Store sensitive data (API keys, tokens) in `config/config_secrets.json`:
+Store sensitive data (API keys, tokens) in `config/config_secrets.json`
+under the same plugin id you use in `config/config.json`:
 
 ```json
 {
@@ -331,19 +332,21 @@ Store sensitive data (API keys, tokens) in `config/config_secrets.json`:
 }
 ```
 
-Reference secrets in main config:
+At load time, the config manager deep-merges `config_secrets.json` into
+the main config (verified at `src/config_manager.py:162-172`). So in
+your plugin's code:
 
-```json
+```python
-{
+class MyPlugin(BasePlugin):
-  "my-plugin": {
+    def __init__(self, plugin_id, config, display_manager, cache_manager, plugin_manager):
-    "enabled": true,
+        super().__init__(plugin_id, config, display_manager, cache_manager, plugin_manager)
-    "config_secrets": {
+        self.api_key = config.get("api_key")  # already merged from secrets
-      "api_key": "my-plugin.api_key"
-    }
-  }
-}
 ```
 
+There is no separate `config_secrets` reference field — just put the
+secret value under the same plugin namespace and read it from the
+merged config.
+
 ### Plugin Discovery
 
 Plugins are automatically discovered when:
@@ -355,7 +358,7 @@ Check discovered plugins:
 
 ```bash
 # Using dev_plugin_setup.sh
-./dev_plugin_setup.sh list
+./scripts/dev/dev_plugin_setup.sh list
 
 # Output shows:
 # ✓ plugin-name (symlink)
@@ -368,7 +371,7 @@ Check discovered plugins:
 Check plugin status and git information:
 
 ```bash
-./dev_plugin_setup.sh status
+./scripts/dev/dev_plugin_setup.sh status
 
 # Output shows:
 # ✓ plugin-name
@@ -391,13 +394,19 @@ cd ledmatrix-my-plugin
 
 # Link to LEDMatrix project
 cd /path/to/LEDMatrix
-./dev_plugin_setup.sh link my-plugin ../ledmatrix-my-plugin
+./scripts/dev/dev_plugin_setup.sh link my-plugin ../ledmatrix-my-plugin
 ```
 
 ### 2. Development Cycle
 
 1. **Edit plugin code** in linked repository
-2. **Test with emulator**: `python run.py --emulator`
+2. **Test with the dev preview server**:
+   `python3 scripts/dev_server.py` (then open `http://localhost:5001`).
+   Or run the full display in emulator mode with
+   `python3 run.py --emulator` (or equivalently
+   `EMULATOR=true python3 run.py`). The `-e`/`--emulator` CLI flag is
+   defined in `run.py:19-20` and sets the same `EMULATOR` environment
+   variable internally.
 3. **Check logs** for errors or warnings
 4. **Update configuration** in `config/config.json` if needed
 5. **Iterate** until plugin works correctly
@@ -406,30 +415,30 @@ cd /path/to/LEDMatrix
 
 ```bash
 # Deploy to Raspberry Pi
-rsync -avz plugins/my-plugin/ pi@raspberrypi:/path/to/LEDMatrix/plugins/my-plugin/
+rsync -avz plugins/my-plugin/ ledpi@your-pi-ip:/path/to/LEDMatrix/plugins/my-plugin/
 
 # Or if using git, pull on Pi
-ssh pi@raspberrypi "cd /path/to/LEDMatrix/plugins/my-plugin && git pull"
+ssh ledpi@your-pi-ip "cd /path/to/LEDMatrix/plugins/my-plugin && git pull"
 
 # Restart service
-ssh pi@raspberrypi "sudo systemctl restart ledmatrix"
+ssh ledpi@your-pi-ip "sudo systemctl restart ledmatrix"
 ```
 
 ### 4. Updating Plugins
 
 ```bash
 # Update single plugin from git
-./dev_plugin_setup.sh update my-plugin
+./scripts/dev/dev_plugin_setup.sh update my-plugin
 
 # Update all linked plugins
-./dev_plugin_setup.sh update
+./scripts/dev/dev_plugin_setup.sh update
 ```
 
 ### 5. Unlinking Plugins
 
 ```bash
 # Remove symlink (preserves repository)
-./dev_plugin_setup.sh unlink my-plugin
+./scripts/dev/dev_plugin_setup.sh unlink my-plugin
 ```
 
 ---
@@ -625,8 +634,8 @@ python run.py --emulator
 **Solutions**:
 1. Check symlink: `ls -la plugins/my-plugin`
 2. Verify target exists: `readlink -f plugins/my-plugin`
-3. Update plugin: `./dev_plugin_setup.sh update my-plugin`
+3. Update plugin: `./scripts/dev/dev_plugin_setup.sh update my-plugin`
-4. Re-link plugin if needed: `./dev_plugin_setup.sh unlink my-plugin && ./dev_plugin_setup.sh link my-plugin <path>`
+4. Re-link plugin if needed: `./scripts/dev/dev_plugin_setup.sh unlink my-plugin && ./scripts/dev/dev_plugin_setup.sh link my-plugin <path>`
 5. Check git status: `cd plugins/my-plugin && git status`
 
 ---
@@ -697,22 +706,22 @@ python run.py --emulator
 
 ```bash
 # Link plugin from GitHub
-./dev_plugin_setup.sh link-github <name>
+./scripts/dev/dev_plugin_setup.sh link-github <name>
 
 # Link local plugin
-./dev_plugin_setup.sh link <name> <path>
+./scripts/dev/dev_plugin_setup.sh link <name> <path>
 
 # List all plugins
-./dev_plugin_setup.sh list
+./scripts/dev/dev_plugin_setup.sh list
 
 # Check plugin status
-./dev_plugin_setup.sh status
+./scripts/dev/dev_plugin_setup.sh status
 
 # Update plugin(s)
-./dev_plugin_setup.sh update [name]
+./scripts/dev/dev_plugin_setup.sh update [name]
 
 # Unlink plugin
-./dev_plugin_setup.sh unlink <name>
+./scripts/dev/dev_plugin_setup.sh unlink <name>
 
 # Run with emulator
 python run.py --emulator

.cursorrules

@@ -2,7 +2,31 @@
 
 ## Plugin System Overview
 
-The LEDMatrix project uses a plugin-based architecture. All display functionality (except core calendar) is implemented as plugins that are dynamically loaded from the `plugins/` directory.
+The LEDMatrix project uses a plugin-based architecture. All display
+functionality (except core calendar) is implemented as plugins that are
+dynamically loaded from the directory configured by
+`plugin_system.plugins_directory` in `config.json` — the default is
+`plugin-repos/` (per `config/config.template.json:130`).
+
+> **Fallback note (scoped):** `PluginManager.discover_plugins()`
+> (`src/plugin_system/plugin_manager.py:154`) only scans the
+> configured directory — there is no fallback to `plugins/` in the
+> main discovery path. A fallback to `plugins/` does exist in two
+> narrower places:
+> - `store_manager.py:1700-1718` — store operations (install/update/
+>   uninstall) check `plugins/` if the plugin isn't found in the
+>   configured directory, so plugin-store flows work even when your
+>   dev symlinks live in `plugins/`.
+> - `schema_manager.py:70-80` — `get_schema_path()` probes both
+>   `plugins/` and `plugin-repos/` for `config_schema.json` so the
+>   web UI form generation finds the schema regardless of where the
+>   plugin lives.
+>
+> The dev workflow in `scripts/dev/dev_plugin_setup.sh` creates
+> symlinks under `plugins/`, which is why the store and schema
+> fallbacks exist. For day-to-day development, set
+> `plugin_system.plugins_directory` to `plugins` so the main
+> discovery path picks up your symlinks.
 
 ## Plugin Structure
 
@@ -27,14 +51,15 @@ The LEDMatrix project uses a plugin-based architecture. All display functionalit
 **Option A: Use dev_plugin_setup.sh (Recommended)**
 ```bash
 # Link from GitHub
-./dev_plugin_setup.sh link-github <plugin-name>
+./scripts/dev/dev_plugin_setup.sh link-github <plugin-name>
 
 # Link local repository
-./dev_plugin_setup.sh link <plugin-name> <path-to-repo>
+./scripts/dev/dev_plugin_setup.sh link <plugin-name> <path-to-repo>
 ```
 
 **Option B: Manual Setup**
-1. Create directory in `plugins/<plugin-id>/`
+1. Create directory in `plugin-repos/<plugin-id>/` (or `plugins/<plugin-id>/`
+   if you're using the dev fallback location)
 2. Add `manifest.json` with required fields
 3. Create `manager.py` with plugin class
 4. Add `config_schema.json` for configuration
@@ -63,7 +88,13 @@ Plugins are configured in `config/config.json`:
 ### 3. Testing Plugins
 
 **On Development Machine:**
-- Use emulator: `python run.py --emulator` or `./run_emulator.sh`
+- Run the dev preview server: `python3 scripts/dev_server.py` (then
+  open `http://localhost:5001`) — renders plugins in the browser
+  without running the full display loop
+- Or run the full display in emulator mode:
+  `python3 run.py --emulator` (or equivalently
+  `EMULATOR=true python3 run.py`, or `./scripts/dev/run_emulator.sh`).
+  The `-e`/`--emulator` CLI flag is defined in `run.py:19-20`.
 - Test plugin loading: Check logs for plugin discovery and loading
 - Validate configuration: Ensure config matches `config_schema.json`
 
@@ -75,15 +106,22 @@ Plugins are configured in `config/config.json`:
 ### 4. Plugin Development Best Practices
 
 **Code Organization:**
-- Keep plugin code in `plugins/<plugin-id>/`
+- Keep plugin code in `plugin-repos/<plugin-id>/` (or its dev-time
+  symlink in `plugins/<plugin-id>/`)
 - Use shared assets from `assets/` directory when possible
-- Follow existing plugin patterns (see `plugins/hockey-scoreboard/` as reference)
+- Follow existing plugin patterns — canonical sources live in the
+  [`ledmatrix-plugins`](https://github.com/ChuckBuilds/ledmatrix-plugins)
+  repo (`plugins/hockey-scoreboard/`, `plugins/football-scoreboard/`,
+  `plugins/clock-simple/`, etc.)
 - Place shared utilities in `src/common/` if reusable across plugins
 
 **Configuration Management:**
 - Use `config_schema.json` for validation
-- Store secrets in `config/config_secrets.json` (not in main config)
+- Store secrets in `config/config_secrets.json` under the same plugin
-- Reference secrets via `config_secrets` key in main config
+  id namespace as the main config — they're deep-merged into the main
+  config at load time (`src/config_manager.py:162-172`), so plugin
+  code reads them directly from `config.get(...)` like any other key
+- There is no separate `config_secrets` reference field
 - Validate all required fields in `validate_config()`
 
 **Error Handling:**
@@ -138,18 +176,32 @@ Located in: `src/display_manager.py`
 
 **Key Methods:**
 - `clear()`: Clear the display
-- `draw_text(text, x, y, color, font)`: Draw text
+- `draw_text(text, x, y, color, font, small_font, centered)`: Draw text
-- `draw_image(image, x, y)`: Draw PIL Image
+- `update_display()`: Push the buffer to the physical display
-- `update_display()`: Update physical display
+- `draw_weather_icon(condition, x, y, size)`: Draw a weather icon
 - `width`, `height`: Display dimensions
 
+**Image rendering**: there is no `draw_image()` helper. Paste directly
+onto the underlying PIL Image:
+```python
+self.display_manager.image.paste(pil_image, (x, y))
+self.display_manager.update_display()
+```
+For transparency, paste with a mask: `image.paste(rgba, (x, y), rgba)`.
+
 ### Cache Manager
 Located in: `src/cache_manager.py`
 
 **Key Methods:**
-- `get(key, max_age=None)`: Get cached value
+- `get(key, max_age=300)`: Get cached value (returns None if missing/stale)
 - `set(key, value, ttl=None)`: Cache a value
-- `delete(key)`: Remove cached value
+- `delete(key)` / `clear_cache(key=None)`: Remove a single cache entry,
+  or (for `clear_cache` with no argument) every cached entry. `delete`
+  is an alias for `clear_cache(key)`.
+- `get_cached_data_with_strategy(key, data_type)`: Cache get with
+  data-type-aware TTL strategy
+- `get_background_cached_data(key, sport_key)`: Cache get for the
+  background-fetch service path
 
 ## Plugin Manifest Schema
 

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,38 +1,84 @@
 ---
 name: Bug report
-about: Create a report to help us improve
+about: Report a problem with LEDMatrix
 title: ''
-labels: ''
+labels: bug
 assignees: ''
 
 ---
 
-**Describe the bug**
+<!--
-A clear and concise description of what the bug is.
+Before filing: please check existing issues to see if this is already
+reported. For security issues, see SECURITY.md and report privately.
+-->
 
-**To Reproduce**
+## Describe the bug
-Steps to reproduce the behavior:
-1. Go to '...'
-2. Click on '....'
-3. Scroll down to '....'
-4. See error
 
-**Expected behavior**
+<!-- A clear and concise description of what the bug is. -->
-A clear and concise description of what you expected to happen.
 
-**Screenshots**
+## Steps to reproduce
-If applicable, add screenshots to help explain your problem.
 
-**Desktop (please complete the following information):**
+1.
- - OS: [e.g. iOS]
+2.
- - Browser [e.g. chrome, safari]
+3.
- - Version [e.g. 22]
 
-**Smartphone (please complete the following information):**
+## Expected behavior
- - Device: [e.g. iPhone6]
- - OS: [e.g. iOS8.1]
- - Browser [e.g. stock browser, safari]
- - Version [e.g. 22]
 
-**Additional context**
+<!-- What you expected to happen. -->
-Add any other context about the problem here.
+
+## Actual behavior
+
+<!-- What actually happened. Include any error messages. -->
+
+## Hardware
+
+- **Raspberry Pi model**: <!-- e.g. Pi 3B+, Pi 4 8GB, Pi Zero 2W -->
+- **OS / kernel**: <!-- output of `cat /etc/os-release` and `uname -a` -->
+- **LED matrix panels**: <!-- e.g. 2x Adafruit 64x32, 1x Waveshare 96x48 -->
+- **HAT / Bonnet**: <!-- e.g. Adafruit RGB Matrix Bonnet, Electrodragon HAT -->
+- **PWM jumper mod soldered?**: <!-- yes / no -->
+- **Display chain**: <!-- chain_length × parallel, e.g. "2x1" -->
+
+## LEDMatrix version
+
+<!-- Run `git rev-parse HEAD` in the LEDMatrix directory, or paste the
+release tag if you installed from a release. -->
+
+```
+git commit:
+```
+
+## Plugin involved (if any)
+
+- **Plugin id**:
+- **Plugin version** (from `manifest.json`):
+
+## Configuration
+
+<!-- Paste the relevant section from config/config.json. Redact any
+API keys before pasting. For display issues, the `display.hardware`
+block is most relevant. For plugin issues, paste that plugin's section. -->
+
+```json
+```
+
+## Logs
+
+<!-- The first 50 lines of the relevant log are usually enough. Run:
+  sudo journalctl -u ledmatrix -n 100 --no-pager
+or for the web service:
+  sudo journalctl -u ledmatrix-web -n 100 --no-pager
+-->
+
+```
+```
+
+## Screenshots / video (optional)
+
+<!-- A photo of the actual display, or a screenshot of the web UI,
+helps a lot for visual issues. -->
+
+## Additional context
+
+<!-- Anything else that might be relevant: when did this start happening,
+what's different about your setup, what have you already tried, etc. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,62 @@
+# Pull Request
+
+## Summary
+
+<!-- 1-3 sentences describing what this PR does and why. -->
+
+## Type of change
+
+<!-- Check all that apply. -->
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Documentation
+- [ ] Refactor (no functional change)
+- [ ] Build / CI
+- [ ] Plugin work (link to the plugin)
+
+## Related issues
+
+<!-- "Fixes #123" or "Refs #123". Use "Fixes" for bug PRs so the issue
+auto-closes when this merges. -->
+
+## Test plan
+
+<!-- How did you test this? Check all that apply. Add details for any
+checked box. -->
+
+- [ ] Ran on a real Raspberry Pi with hardware
+- [ ] Ran in emulator mode (`EMULATOR=true python3 run.py`)
+- [ ] Ran the dev preview server (`scripts/dev_server.py`)
+- [ ] Ran the test suite (`pytest`)
+- [ ] Manually verified the affected code path in the web UI
+- [ ] N/A — documentation-only change
+
+## Documentation
+
+- [ ] I updated `README.md` if user-facing behavior changed
+- [ ] I updated the relevant doc in `docs/` if developer behavior changed
+- [ ] I added/updated docstrings on new public functions
+- [ ] N/A — no docs needed
+
+## Plugin compatibility
+
+<!-- For changes to BasePlugin, the plugin loader, the web UI, or the
+config schema. -->
+
+- [ ] No plugin breakage expected
+- [ ] Some plugins will need updates — listed below
+- [ ] N/A — change doesn't touch the plugin system
+
+## Checklist
+
+- [ ] My commits follow the message convention in `CONTRIBUTING.md`
+- [ ] I read `CONTRIBUTING.md` and `CODE_OF_CONDUCT.md`
+- [ ] I've not committed any secrets or hardcoded API keys
+- [ ] If this adds a new config key, the form in the web UI was
+      verified (the form is generated from `config_schema.json`)
+
+## Notes for reviewer
+
+<!-- Anything reviewers should know — gotchas, things you weren't
+sure about, decisions you'd like a second opinion on. -->

.gitignore

@@ -40,3 +40,10 @@ htmlcov/
 # See docs/MULTI_ROOT_WORKSPACE_SETUP.md for details
 plugins/*
 !plugins/.gitkeep
+
+# Binary files and backups
+bin/pixlet/
+config/backups/
+
+# Starlark apps runtime storage (installed .star files and cached renders)
+/starlark-apps/

.gitmodules

@@ -1,66 +1,3 @@
-[submodule "plugins/odds-ticker"]
-	path = plugins/odds-ticker
-	url = https://github.com/ChuckBuilds/ledmatrix-odds-ticker.git
-[submodule "plugins/clock-simple"]
-	path = plugins/clock-simple
-	url = https://github.com/ChuckBuilds/ledmatrix-clock-simple.git
-[submodule "plugins/text-display"]
-	path = plugins/text-display
-	url = https://github.com/ChuckBuilds/ledmatrix-text-display.git
 [submodule "rpi-rgb-led-matrix-master"]
 	path = rpi-rgb-led-matrix-master
 	url = https://github.com/hzeller/rpi-rgb-led-matrix.git
-[submodule "plugins/basketball-scoreboard"]
-	path = plugins/basketball-scoreboard
-	url = https://github.com/ChuckBuilds/ledmatrix-basketball-scoreboard.git
-[submodule "plugins/soccer-scoreboard"]
-	path = plugins/soccer-scoreboard
-	url = https://github.com/ChuckBuilds/ledmatrix-soccer-scoreboard.git
-[submodule "plugins/calendar"]
-	path = plugins/calendar
-	url = https://github.com/ChuckBuilds/ledmatrix-calendar.git
-[submodule "plugins/mqtt-notifications"]
-	path = plugins/mqtt-notifications
-	url = https://github.com/ChuckBuilds/ledmatrix-mqtt-notifications.git
-[submodule "plugins/olympics-countdown"]
-	path = plugins/olympics-countdown
-	url = https://github.com/ChuckBuilds/ledmatrix-olympics-countdown.git
-[submodule "plugins/ledmatrix-stocks"]
-	path = plugins/ledmatrix-stocks
-	url = https://github.com/ChuckBuilds/ledmatrix-stocks.git
-[submodule "plugins/ledmatrix-music"]
-	path = plugins/ledmatrix-music
-	url = https://github.com/ChuckBuilds/ledmatrix-music.git
-[submodule "plugins/static-image"]
-	path = plugins/static-image
-	url = https://github.com/ChuckBuilds/ledmatrix-static-image.git
-[submodule "plugins/football-scoreboard"]
-	path = plugins/football-scoreboard
-	url = https://github.com/ChuckBuilds/ledmatrix-football-scoreboard.git
-[submodule "plugins/hockey-scoreboard"]
-	path = plugins/hockey-scoreboard
-	url = https://github.com/ChuckBuilds/ledmatrix-hockey-scoreboard.git
-[submodule "plugins/baseball-scoreboard"]
-	path = plugins/baseball-scoreboard
-	url = https://github.com/ChuckBuilds/ledmatrix-baseball-scoreboard.git
-[submodule "plugins/christmas-countdown"]
-	path = plugins/christmas-countdown
-	url = https://github.com/ChuckBuilds/ledmatrix-christmas-countdown.git
-[submodule "plugins/ledmatrix-flights"]
-	path = plugins/ledmatrix-flights
-	url = https://github.com/ChuckBuilds/ledmatrix-flights.git
-[submodule "plugins/ledmatrix-leaderboard"]
-	path = plugins/ledmatrix-leaderboard
-	url = https://github.com/ChuckBuilds/ledmatrix-leaderboard.git
-[submodule "plugins/ledmatrix-weather"]
-	path = plugins/ledmatrix-weather
-	url = https://github.com/ChuckBuilds/ledmatrix-weather.git
-[submodule "plugins/ledmatrix-news"]
-	path = plugins/ledmatrix-news
-	url = https://github.com/ChuckBuilds/ledmatrix-news.git
-[submodule "plugins/ledmatrix-of-the-day"]
-	path = plugins/ledmatrix-of-the-day
-	url = https://github.com/ChuckBuilds/ledmatrix-of-the-day.git
-[submodule "plugins/youtube-stats"]
-	path = plugins/youtube-stats
-	url = https://github.com/ChuckBuilds/ledmatrix-youtube-stats.git

.pre-commit-config.yaml

@@ -0,0 +1,64 @@
+# Pre-commit hooks for LEDMatrix
+# Install: pip install pre-commit && pre-commit install
+# Run manually: pre-commit run --all-files
+
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.5.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-json
+      - id: check-added-large-files
+        args: ['--maxkb=1000']
+      - id: check-merge-conflict
+
+  - repo: https://github.com/PyCQA/flake8
+    rev: 7.0.0
+    hooks:
+      - id: flake8
+        args: ['--select=E9,F63,F7,F82,B', '--ignore=E501']
+        additional_dependencies: [flake8-bugbear]
+
+  - repo: local
+    hooks:
+      - id: no-bare-except
+        name: Check for bare except clauses
+        entry: bash -c 'if grep -rn "except:\s*pass" src/; then echo "Found bare except:pass - please handle exceptions properly"; exit 1; fi'
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      - id: no-hardcoded-paths
+        name: Check for hardcoded user paths
+        entry: bash -c 'if grep -rn "/home/chuck/" src/; then echo "Found hardcoded user paths - please use relative paths or config"; exit 1; fi'
+        language: system
+        types: [python]
+        pass_filenames: false
+
+  - repo: https://github.com/pre-commit/mirrors-mypy
+    rev: v1.8.0
+    hooks:
+      - id: mypy
+        additional_dependencies: [types-requests, types-pytz]
+        args: [--ignore-missing-imports, --no-error-summary]
+        pass_filenames: false
+        files: ^src/
+
+  - repo: https://github.com/PyCQA/bandit
+    rev: 1.8.3
+    hooks:
+      - id: bandit
+        args:
+          - '-r'
+          - '-ll'
+          - '-c'
+          - 'bandit.yaml'
+          - '-x'
+          - './tests,./test,./venv,./.venv,./scripts/prove_security.py,./rpi-rgb-led-matrix-master'
+
+  - repo: https://github.com/gitleaks/gitleaks
+    rev: v8.24.3
+    hooks:
+      - id: gitleaks

CLAUDE.md

@@ -0,0 +1,37 @@
+# LEDMatrix
+
+## Project Structure
+- `src/plugin_system/` — Plugin loader, manager, store manager, base plugin class
+- `web_interface/` — Flask web UI (blueprints, templates, static JS)
+- `config/config.json` — User plugin configuration (persists across plugin reinstalls)
+- `plugin-repos/` — **Default** plugin install directory used by the
+  Plugin Store, set by `plugin_system.plugins_directory` in
+  `config.json` (default per `config/config.template.json:130`).
+  Not gitignored.
+- `plugins/` — Legacy/dev plugin location. Gitignored (`plugins/*`).
+  Used by `scripts/dev/dev_plugin_setup.sh` for symlinks. The plugin
+  loader falls back to it when something isn't found in `plugin-repos/`
+  (`src/plugin_system/schema_manager.py:77`).
+
+## Plugin System
+- Plugins inherit from `BasePlugin` in `src/plugin_system/base_plugin.py`
+- Required abstract methods: `update()`, `display(force_clear=False)`
+- Each plugin needs: `manifest.json`, `config_schema.json`, `manager.py`, `requirements.txt`
+- Plugin instantiation args: `plugin_id, config, display_manager, cache_manager, plugin_manager`
+- Config schemas use JSON Schema Draft-7
+- Display dimensions: always read dynamically from `self.display_manager.matrix.width/height`
+
+## Plugin Store Architecture
+- Official plugins live in the `ledmatrix-plugins` monorepo (not individual repos)
+- Plugin repo naming convention: `ledmatrix-<plugin-id>` (e.g., `ledmatrix-football-scoreboard`)
+- `plugins.json` registry at `https://raw.githubusercontent.com/ChuckBuilds/ledmatrix-plugins/main/plugins.json`
+- Store manager (`src/plugin_system/store_manager.py`) handles install/update/uninstall
+- Monorepo plugins are installed via ZIP extraction (no `.git` directory)
+- Update detection for monorepo plugins uses version comparison (manifest version vs registry latest_version)
+- Plugin configs stored in `config/config.json`, NOT in plugin directories — safe across reinstalls
+- Third-party plugins can use their own repo URL with empty `plugin_path`
+
+## Common Pitfalls
+- paho-mqtt 2.x needs `callback_api_version=mqtt.CallbackAPIVersion.VERSION1` for v1 compat
+- BasePlugin uses `get_logger()` from `src.logging_config`, not standard `logging.getLogger()`
+- When modifying a plugin in the monorepo, you MUST bump `version` in its `manifest.json` and run `python update_registry.py` — otherwise users won't receive the update

CODE_OF_CONDUCT.md

@@ -0,0 +1,137 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+This includes the LEDMatrix Discord server, GitHub repositories owned by
+ChuckBuilds, and any other forums hosted by or affiliated with the project.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement on the
+[LEDMatrix Discord](https://discord.gg/uW36dVAtcT) (DM a moderator or
+ChuckBuilds directly) or by opening a private GitHub Security Advisory if
+the issue involves account safety. All complaints will be reviewed and
+investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,113 @@
+# Contributing to LEDMatrix
+
+Thanks for considering a contribution! LEDMatrix is built with help from
+the community and we welcome bug reports, plugins, documentation
+improvements, and code changes.
+
+## Quick links
+
+- **Bugs / feature requests**: open an issue using one of the templates
+  in [`.github/ISSUE_TEMPLATE/`](.github/ISSUE_TEMPLATE/).
+- **Real-time discussion**: the
+  [LEDMatrix Discord](https://discord.gg/uW36dVAtcT).
+- **Plugin development**:
+  [`docs/PLUGIN_DEVELOPMENT_GUIDE.md`](docs/PLUGIN_DEVELOPMENT_GUIDE.md)
+  and the [`ledmatrix-plugins`](https://github.com/ChuckBuilds/ledmatrix-plugins)
+  repository.
+- **Security issues**: see [`SECURITY.md`](SECURITY.md). Please don't
+  open public issues for vulnerabilities.
+
+## Setting up a development environment
+
+1. Clone with submodules:
+   ```bash
+   git clone --recurse-submodules https://github.com/ChuckBuilds/LEDMatrix.git
+   cd LEDMatrix
+   ```
+2. For development without hardware, run the dev preview server:
+   ```bash
+   python3 scripts/dev_server.py
+   # then open http://localhost:5001
+   ```
+   See [`docs/DEV_PREVIEW.md`](docs/DEV_PREVIEW.md) for details.
+3. To run the full display in emulator mode:
+   ```bash
+   EMULATOR=true python3 run.py
+   ```
+4. To target real hardware on a Raspberry Pi, follow the install
+   instructions in the root [`README.md`](README.md).
+
+## Running the tests
+
+```bash
+pip install -r requirements.txt
+pytest
+```
+
+See [`docs/HOW_TO_RUN_TESTS.md`](docs/HOW_TO_RUN_TESTS.md) for details
+on test markers, the per-plugin tests, and the web-interface
+integration tests.
+
+## Submitting changes
+
+1. **Open an issue first** for non-trivial changes. This avoids
+   wasted work on PRs that don't fit the project direction.
+2. **Create a topic branch** off `main`:
+   `feat/<short-description>`, `fix/<short-description>`,
+   `docs/<short-description>`.
+3. **Keep PRs focused.** One conceptual change per PR. If you find
+   adjacent bugs while working, fix them in a separate PR.
+4. **Follow the existing code style.** Python code uses standard
+   `black`/`ruff` conventions; HTML/JS in `web_interface/` follows the
+   patterns already in `templates/v3/` and `static/v3/`.
+5. **Update documentation** alongside code changes. If you add a
+   config key, document it in the relevant `*.md` file (or, for
+   plugins, in `config_schema.json` so the form is auto-generated).
+6. **Run the tests** locally before opening the PR.
+7. **Use the PR template** — `.github/PULL_REQUEST_TEMPLATE.md` will
+   prompt you for what we need.
+
+## Commit message convention
+
+Conventional Commits is encouraged but not strictly enforced:
+
+- `feat: add NHL playoff bracket display`
+- `fix(plugin-loader): handle missing class_name in manifest`
+- `docs: correct web UI port in TROUBLESHOOTING.md`
+- `refactor(cache): consolidate strategy lookup`
+
+Keep the subject under 72 characters; put the why in the body.
+
+## Contributing a plugin
+
+LEDMatrix plugins live in their own repository:
+[`ledmatrix-plugins`](https://github.com/ChuckBuilds/ledmatrix-plugins).
+Plugin contributions go through that repo's
+[`SUBMISSION.md`](https://github.com/ChuckBuilds/ledmatrix-plugins/blob/main/SUBMISSION.md)
+process. The
+[`hello-world` plugin](https://github.com/ChuckBuilds/ledmatrix-plugins/tree/main/plugins/hello-world)
+is the canonical starter template.
+
+## Reviewing pull requests
+
+Maintainer review is by [@ChuckBuilds](https://github.com/ChuckBuilds).
+Community review is welcome on any open PR — leave constructive
+comments, test on your hardware if applicable, and call out anything
+unclear.
+
+## Code of conduct
+
+This project follows the [Contributor Covenant](CODE_OF_CONDUCT.md). By
+participating you agree to abide by its terms.
+
+## License
+
+LEDMatrix is licensed under the [GNU General Public License v3.0 or
+later](LICENSE). By submitting a contribution you agree to license it
+under the same terms (the standard "inbound = outbound" rule that
+GitHub applies by default).
+
+LEDMatrix builds on
+[`rpi-rgb-led-matrix`](https://github.com/hzeller/rpi-rgb-led-matrix),
+which is GPL-2.0-or-later. The "or later" clause makes it compatible
+with GPL-3.0 distribution.

LEDMatrix.code-workspace

@@ -4,89 +4,9 @@
 			"path": ".",
 			"name": "LEDMatrix (Main)"
 		},
-		{
-			"path": "../ledmatrix-odds-ticker",
-			"name": "Odds Ticker"
-		},
-		{
-			"path": "../ledmatrix-clock-simple",
-			"name": "Clock Simple"
-		},
-		{
-			"path": "../ledmatrix-text-display",
-			"name": "Text Display"
-		},
-		{
-			"path": "../ledmatrix-basketball-scoreboard",
-			"name": "Basketball Scoreboard"
-		},
-		{
-			"path": "../ledmatrix-soccer-scoreboard",
-			"name": "Soccer Scoreboard"
-		},
-		{
-			"path": "../ledmatrix-calendar",
-			"name": "Calendar"
-		},
-		{
-			"path": "../ledmatrix-olympics-countdown",
-			"name": "Olympics Countdown"
-		},
-		{
-			"path": "../ledmatrix-stocks",
-			"name": "Stocks"
-		},
-		{
-			"path": "../ledmatrix-music",
-			"name": "Music"
-		},
-		{
-			"path": "../ledmatrix-static-image",
-			"name": "Static Image"
-		},
-		{
-			"path": "../ledmatrix-football-scoreboard",
-			"name": "Football Scoreboard"
-		},
-		{
-			"path": "../ledmatrix-hockey-scoreboard",
-			"name": "Hockey Scoreboard"
-		},
-		{
-			"path": "../ledmatrix-baseball-scoreboard",
-			"name": "Baseball Scoreboard"
-		},
-		{
-			"path": "../ledmatrix-christmas-countdown",
-			"name": "Christmas Countdown"
-		},
-		{
-			"path": "../ledmatrix-flights",
-			"name": "Flights"
-		},
-		{
-			"path": "../ledmatrix-leaderboard",
-			"name": "Leaderboard"
-		},
-		{
-			"path": "../ledmatrix-weather",
-			"name": "Weather"
-		},
-		{
-			"path": "../ledmatrix-news",
-			"name": "News"
-		},
-		{
-			"path": "../ledmatrix-of-the-day",
-			"name": "Of The Day"
-		},
-		{
-			"path": "../ledmatrix-youtube-stats",
-			"name": "YouTube Stats"
-		},
 		{
 			"path": "../ledmatrix-plugins",
-			"name": "Plugin Registry"
+			"name": "Plugins (Monorepo)"
 		}
 	],
 	"settings": {

LICENSE

@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.

README.md

@@ -14,8 +14,12 @@ I'm very new to all of this and am *heavily* relying on AI development tools to
 I'm trying to be open to constructive criticism and support, as long as it's a realistic ask and aligns with my priorities on this project. If you have ideas for improvements, find bugs, or want to add features to the base project, please don't hesitate to reach out on Discord or submit a pull request. Similarly, if you want to develop a plugin of your own, please do so! I'd love to see what you create.
 
 
+### Installing the LEDMatrix project on a pi video:
+[![Installing LEDMatrix on a Pi](https://img.youtube.com/vi/bkT0f1tZI0Y/hqdefault.jpg)](https://www.youtube.com/watch?v=bkT0f1tZI0Y)
+
 ### Setup video and feature walkthrough on Youtube (Outdated but still useful) : 
-[![IMAGE ALT TEXT HERE](https://img.youtube.com/vi/_HaqfJy1Y54/0.jpg)](https://www.youtube.com/watch?v=_HaqfJy1Y54)
+[![Outdated Video about the project](https://img.youtube.com/vi/_HaqfJy1Y54/hqdefault.jpg)](https://www.youtube.com/watch?v=_HaqfJy1Y54)
+
 
 -----------------------------------------------------------------------------------
 ### Connect with ChuckBuilds
@@ -23,7 +27,7 @@ I'm trying to be open to constructive criticism and support, as long as it's a r
 - Show support on Youtube: https://www.youtube.com/@ChuckBuilds
 - Check out the write-up on my website: https://www.chuck-builds.com/led-matrix/
 - Stay in touch on Instagram: https://www.instagram.com/ChuckBuilds/
-- Want to chat? Reach out on the ChuckBuilds Discord: https://discord.com/invite/uW36dVAtcT
+- Want to chat? Reach out on the LEDMatrix Discord: [https://discord.com/invite/uW36dVAtcT](https://discord.gg/dfFwsasa6W)
 - Feeling Generous? Consider sponsoring this project or sending a donation (these AI credits aren't cheap!)          
 
 -----------------------------------------------------------------------------------
@@ -138,7 +142,7 @@ The system supports live, recent, and upcoming game information for multiple spo
 (2x in a horizontal chain is recommended)
 - [Adafruit 64×32](https://www.adafruit.com/product/2278) – designed for 128×32 but works with dynamic scaling on many displays (pixel pitch is user preference)
 - [Waveshare 64×32](https://amzn.to/3Kw55jK) - Does not require E addressable pad
-- [Waveshare 92×46](https://amzn.to/4bydNcv) – higher resolution, requires soldering the **E addressable pad** on the [Adafruit RGB Bonnet](https://www.adafruit.com/product/3211) to “8” **OR** toggling the DIP switch on the Adafruit Triple LED Matrix Bonnet *(no soldering required!)*  
+- [Waveshare 96×48](https://amzn.to/4bydNcv) – higher resolution, requires soldering the **E addressable pad** on the [Adafruit RGB Bonnet](https://www.adafruit.com/product/3211) to “8” **OR** toggling the DIP switch on the Adafruit Triple LED Matrix Bonnet *(no soldering required!)*  
   > Amazon Affiliate Link – ChuckBuilds receives a small commission on purchases  
 
 ### Power Supply
@@ -152,7 +156,7 @@ The system supports live, recent, and upcoming game information for multiple spo
 ![DSC00079](https://github.com/user-attachments/assets/4282d07d-dfa2-4546-8422-ff1f3a9c0703)
 
 ## Possibly required depending on the display you are using.
-- Some LED Matrix displays require an "E" addressable line to draw the display properly. The [64x32 Adafruit display](https://www.adafruit.com/product/2278) does NOT require the E addressable line, however the [92x46 Waveshare display](https://amzn.to/4pQdezE) DOES require the "E" Addressable line.
+- Some LED Matrix displays require an "E" addressable line to draw the display properly. The [64x32 Adafruit display](https://www.adafruit.com/product/2278) does NOT require the E addressable line, however the [96x48 Waveshare display](https://amzn.to/4pQdezE) DOES require the "E" Addressable line.
 - Various ways to enable this depending on your Bonnet / HAT.
 
 Your display will look like it is "sort of" working but still messed up. 
@@ -778,14 +782,18 @@ The LEDMatrix system includes Web Interface that runs on port 5000 and provides
 
 ### Installing the Web Interface Service
 
+> The first-time installer (`first_time_install.sh`) already installs the
+> web service. The steps below only apply if you need to (re)install it
+> manually.
+
 1. Make the install script executable:
 ```bash
-chmod +x install_web_service.sh
+chmod +x scripts/install/install_web_service.sh
 ```
 
 2. Run the install script with sudo:
 ```bash
-sudo ./install_web_service.sh
+sudo ./scripts/install/install_web_service.sh
 ```
 
 The script will:
@@ -870,3 +878,27 @@ sudo systemctl enable ledmatrix-web.service
 
 
 ### If you've read this far — thanks!  
+
+-----------------------------------------------------------------------------------
+
+## License
+
+LEDMatrix is licensed under the
+[GNU General Public License v3.0 or later](LICENSE).
+
+LEDMatrix builds on
+[`rpi-rgb-led-matrix`](https://github.com/hzeller/rpi-rgb-led-matrix),
+which is GPL-2.0-or-later. The "or later" clause makes it compatible
+with GPL-3.0 distribution.
+
+Plugin contributions in
+[`ledmatrix-plugins`](https://github.com/ChuckBuilds/ledmatrix-plugins)
+are also GPL-3.0-or-later unless individual plugins specify otherwise.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, the PR
+flow, and how to add a plugin. Bug reports and feature requests go in
+the [issue tracker](https://github.com/ChuckBuilds/LEDMatrix/issues).
+Security issues should be reported privately per
+[SECURITY.md](SECURITY.md).

SECURITY.md

@@ -0,0 +1,86 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+If you've found a security issue in LEDMatrix, **please don't open a
+public GitHub issue**. Disclose it privately so we can fix it before it's
+exploited.
+
+### How to report
+
+Use one of these channels, in order of preference:
+
+1. **GitHub Security Advisories** (preferred). On the LEDMatrix repo,
+   go to **Security → Advisories → Report a vulnerability**. This
+   creates a private discussion thread visible only to you and the
+   maintainer.
+   - Direct link: <https://github.com/ChuckBuilds/LEDMatrix/security/advisories/new>
+2. **Discord DM**. Send a direct message to a moderator on the
+   [LEDMatrix Discord](https://discord.gg/uW36dVAtcT). Don't post in
+   public channels.
+
+Please include:
+
+- A description of the issue
+- The version / commit hash you're testing against
+- Steps to reproduce, ideally a minimal proof of concept
+- The impact you can demonstrate
+- Any suggested mitigation
+
+### What to expect
+
+- An acknowledgement within a few days (this is a hobby project, not
+  a 24/7 ops team).
+- A discussion of the issue's severity and a plan for the fix.
+- Credit in the release notes when the fix ships, unless you'd
+  prefer to remain anonymous.
+- For high-severity issues affecting active deployments, we'll
+  coordinate disclosure timing with you.
+
+## Scope
+
+In scope for this policy:
+
+- The LEDMatrix display controller, web interface, and plugin loader
+  in this repository
+- The official plugins in
+  [`ledmatrix-plugins`](https://github.com/ChuckBuilds/ledmatrix-plugins)
+- Installation scripts and systemd unit files
+
+Out of scope (please report upstream):
+
+- Vulnerabilities in `rpi-rgb-led-matrix` itself —
+  report to <https://github.com/hzeller/rpi-rgb-led-matrix>
+- Vulnerabilities in Python packages we depend on — report to the
+  upstream package maintainer
+- Issues in third-party plugins not in `ledmatrix-plugins` — report
+  to that plugin's repository
+
+## Known security model
+
+LEDMatrix is designed for trusted local networks. Several limitations
+are intentional rather than vulnerabilities:
+
+- **No web UI authentication.** The web interface assumes the network
+  it's running on is trusted. Don't expose port 5000 to the internet.
+- **Plugins run unsandboxed.** Installed plugins execute in the same
+  Python process as the display loop with full file-system and
+  network access. Review plugin code (especially third-party plugins
+  from arbitrary GitHub URLs) before installing. The Plugin Store
+  marks community plugins as **Custom** to highlight this.
+- **The display service runs as root** for hardware GPIO access. This
+  is required by `rpi-rgb-led-matrix`.
+- **`config_secrets.json` is plaintext.** API keys and tokens are
+  stored unencrypted on the Pi. Lock down filesystem permissions on
+  the config directory if this matters for your deployment.
+
+These are documented as known limitations rather than bugs. If you
+have ideas for improving them while keeping the project usable on a
+Pi, open a discussion — we're interested.
+
+## Supported versions
+
+LEDMatrix is rolling-release on `main`. Security fixes land on `main`
+and become available the next time users run **Update Code** from the
+web UI's Overview tab (which does a `git pull`). There are no LTS
+branches.

assets/fonts/AUTHORS

@@ -0,0 +1,42 @@
+The identity of the designer(s) of the original ASCII repertoire and
+the later Latin-1 extension of the misc-fixed BDF fonts appears to
+have been lost in history. (It is likely that many of these 7-bit
+ASCII fonts were created in the early or mid 1980s as part of MIT's
+Project Athena, or at its industrial partner, DEC.)
+
+In 1997, Markus Kuhn at the University of Cambridge Computer
+Laboratory initiated and headed a project to extend the misc-fixed BDF
+fonts to as large a subset of Unicode/ISO 10646 as is feasible for
+each of the available font sizes, as part of a wider effort to
+encourage users of POSIX systems to migrate from ISO 8859 to UTF-8.
+
+Robert Brady <rwb197@ecs.soton.ac.uk> and Birger Langkjer
+<birger.langkjer@image.dk> contributed thousands of glyphs and made
+very substantial contributions and improvements on almost all fonts.
+Constantine Stathopoulos <cstath@irismedia.gr> contributed all the
+Greek characters. Markus Kuhn <http://www.cl.cam.ac.uk/~mgk25/> did
+most 6x13 glyphs and the italic fonts and provided many more glyphs,
+coordination, and quality assurance for the other fonts. Mark Leisher
+<mleisher@crl.nmsu.edu> contributed to 6x13 Armenian, Georgian, the
+first version of Latin Extended Block A and some Cyrillic. Serge V.
+Vakulenko <vak@crox.net.kiae.su> donated the original Cyrillic glyphs
+from his 6x13 ISO 8859-5 font. Nozomi Ytow <nozomi@biol.tsukuba.ac.jp>
+contributed 6x13 halfwidth Katakana. Henning Brunzel
+<hbrunzel@meta-systems.de> contributed glyphs to 10x20.bdf. Theppitak
+Karoonboonyanan <thep@linux.thai.net> contributed Thai for 7x13,
+7x13B, 7x13O, 7x14, 7x14B, 8x13, 8x13B, 8x13O, 9x15, 9x15B, and 10x20.
+Karl Koehler <koehler@or.uni-bonn.de> contributed Arabic to 9x15,
+9x15B, and 10x20 and Roozbeh Pournader <roozbeh@sharif.ac.ir> and
+Behdad Esfahbod revised and extended Arabic in 10x20. Raphael Finkel
+<raphael@cs.uky.edu> revised Hebrew/Yiddish in 10x20. Jungshik Shin
+<jshin@pantheon.yale.edu> prepared 18x18ko.bdf. Won-kyu Park
+<wkpark@chem.skku.ac.kr> prepared the Hangul glyphs used in 12x13ja.
+Janne V. Kujala <jvk@iki.fi> contributed 4x6. Daniel Yacob
+<perl@geez.org> revised some Ethiopic glyphs. Ted Zlatanov
+<tzz@lifelogs.com> did some 7x14. Mikael Öhman <micketeer@gmail.com>
+worked on 6x12.
+
+The fonts are still maintained by Markus Kuhn and the original
+distribution can be found at:
+
+  http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html

assets/fonts/README

@@ -0,0 +1,369 @@
+
+Unicode versions of the X11 "misc-fixed-*" fonts
+------------------------------------------------
+
+Markus Kuhn <http://www.cl.cam.ac.uk/~mgk25/> -- 2008-04-21
+
+
+This package contains the X Window System bitmap fonts
+
+   -Misc-Fixed-*-*-*--*-*-*-*-C-*-ISO10646-1
+
+These are Unicode (ISO 10646-1) extensions of the classic ISO 8859-1
+X11 terminal fonts that are widely used with many X11 applications
+such as xterm, emacs, etc.
+
+COVERAGE
+--------
+
+None of these fonts covers Unicode completely. Complete coverage
+simply would not make much sense here. Unicode 5.1 contains over
+100000 characters, and the large majority of them are
+Chinese/Japanese/Korean Han ideographs (~70000) and Korean Hangul
+Syllables (~11000) that cannot adequately be displayed in the small
+pixel sizes of the fixed fonts. Similarly, Arabic characters are
+difficult to fit nicely together with European characters into the
+fixed character cells and X11 lacks the ligature substitution
+mechanisms required for using Indic scripts.
+
+Therefore these fonts primarily attempt to cover Unicode subsets that
+fit together with European scripts. This includes the Latin, Greek,
+Cyrillic, Armenian, Georgian, and Hebrew scripts, plus a lot of
+linguistic, technical and mathematical symbols. Some of the fixed
+fonts now also cover Arabic, Thai, Ethiopian, halfwidth Katakana, and
+some other non-European scripts.
+
+We have defined 3 different target character repertoires (ISO 10646-1
+subsets) that the various fonts were checked against for minimal
+guaranteed coverage:
+
+  TARGET1    617 characters
+             Covers all characters of ISO 8859 part 1-5,7-10,13-16,
+             CEN MES-1, ISO 6937, Microsoft CP1251/CP1252, DEC VT100
+             graphics symbols, and the replacement and default
+             character. It is intended for small bold, italic, and
+             proportional fonts, for which adding block graphics
+             characters would make little sense. This repertoire
+             covers the following ISO 10646-1:2000 collections
+             completely: 1-3, 8, 12.
+
+  TARGET2    886 characters
+             Adds to TARGET1 the characters of the Adobe/Microsoft
+             Windows Glyph List 4 (WGL4), plus a selected set of
+             mathematical characters (covering most of ISO 31-11
+             high-school level math symbols) and some combining
+             characters. It is intended to be covered by all normal
+             "fixed" fonts and covers all European IBM, Microsoft, and
+             Macintosh character sets. This repertoire covers the
+             following ISO 10646-1:2000 (including Amd 1:2002)
+             collections completely: 1-3, 8, 12, 33, 45.
+
+  TARGET3    3282 characters
+
+             Adds to TARGET2 all characters of all European scripts
+             (Latin, Greek, Cyrillic, Armenian, Georgian), all
+             phonetic alphabet symbols, many mathematical symbols
+             (including all those available in LaTeX), all typographic
+             punctuation, all box-drawing characters, control code
+             pictures, graphical shapes and some more that you would
+             expect in a very comprehensive Unicode 4.0 font for
+             European users. It is intended for some of the more
+             useful and more widely used normal "fixed" fonts. This
+             repertoire is, with two exceptions, a superset of all
+             graphical characters in CEN MES-3A and covers the
+             following ISO 10646-1:2000 (including Amd 1:2002)
+             collections completely: 1-12, 27, 30-31, 32 (only
+             graphical characters), 33-42, 44-47, 63, 65, 70 (only
+             graphical characters).
+
+             [The two MES-3A characters deliberately omitted are the
+             angle bracket characters U+2329 and U+232A. ISO and CEN
+             appears to have included these into collection 40 and
+             MES-3A by accident, because there they are the only
+             characters in the Unicode EastAsianWidth "wide" class.]
+
+CURRENT STATUS:
+
+   6x13.bdf 8x13.bdf 9x15.bdf 9x18.bdf 10x20.bdf:
+
+     Complete (TARGET3 reached and checked)
+
+   5x7.bdf 5x8.bdf 6x9.bdf 6x10.bdf 6x12.bdf 7x13.bdf 7x14.bdf clR6x12.bdf:
+
+     Complete (TARGET2 reached and checked)
+
+   6x13B.bdf 7x13B.bdf 7x14B.bdf 8x13B.bdf 9x15B.bdf 9x18B.bdf:
+
+     Complete (TARGET1 reached and checked)
+
+   6x13O.bdf 7x13O.bdf 8x13O.bdf
+
+     Complete (TARGET1 minus Hebrew and block graphics)
+
+[None of the above fonts contains any character that has in Unicode
+the East Asian Width Property "W" or "F" assigned. This way, the
+desired combination of "half-width" and "full-width" glyphs can be
+achieved easily. Most font mechanisms display a character that is not
+covered in a font by using a glyph from another font that appears
+later in a priority list, which can be arranged to be a "full-width"
+font.]
+
+The supplement package
+
+  http://www.cl.cam.ac.uk/~mgk25/download/ucs-fonts-asian.tar.gz
+
+contains the following additional square fonts with Han characters for
+East Asian users:
+
+   12x13ja.bdf:
+
+     Covers TARGET2, JIS X 0208, Hangul, and a few more. This font is
+     primarily intended to provide Japanese full-width Hiragana,
+     Katakana, and Kanji for applications that take the remaining
+     ("halfwidth") characters from 6x13.bdf. The Greek lowercase
+     characters in it are still a bit ugly and will need some work.
+
+  18x18ja.bdf:
+
+     Covers all JIS X 0208, JIS X 0212, GB 2312-80, KS X 1001:1992,
+     ISO 8859-1,2,3,4,5,7,9,10,15, CP437, CP850 and CP1252 characters,
+     plus a few more, where priority was given to Japanese han style
+     variants. This font should have everything needed to cover the
+     full ISO-2022-JP-2 (RFC 1554) repertoire. This font is primarily
+     intended to provide Japanese full-width Hiragana, Katakana, and
+     Kanji for applications that take the remaining ("halfwidth")
+     characters from 9x18.bdf.
+
+  18x18ko.bdf:
+
+     Covers the same repertoire as 18x18ja plus full coverage of all
+     Hangul syllables and priority was given to Hanja glyphs in the
+     unified CJK area as they are used for writing Korean.
+
+The 9x18 and 6x12 fonts are recommended for use with overstriking
+combining characters.
+
+Bug reports, suggestions for improvement, and especially contributed
+extensions are very welcome!
+
+INSTALLATION
+------------
+
+You install the fonts under Unix roughly like this (details depending
+on your system of course):
+
+System-wide installation (root access required):
+
+  cd submission/
+  make
+  su
+  mv -b *.pcf.gz /usr/lib/X11/fonts/misc/
+  cd /usr/lib/X11/fonts/misc/
+  mkfontdir
+  xset fp rehash
+
+Alternative: Installation in your private user directory:
+
+  cd submission/
+  make
+  mkdir -p ~/local/lib/X11/fonts/
+  mv *.pcf.gz ~/local/lib/X11/fonts/
+  cd ~/local/lib/X11/fonts/
+  mkfontdir
+  xset +fp ~/local/lib/X11/fonts   (put this last line also in ~/.xinitrc)
+
+Now you can have a look at say the 6x13 font with the command
+
+  xfd -fn '-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1'
+
+If you want to have short names for the Unicode fonts, you can also
+append the fonts.alias file to that in the directory where you install
+the fonts, call "mkfontdir" and "xset fp rehash" again, and then you
+can also write
+
+  xfd -fn 6x13U
+
+Note: If you use an old version of xfontsel, you might notice that it
+treats every font that contains characters >0x00ff as a Japanese JIS
+font and therefore selects inappropriate sample characters for display
+of ISO 10646-1 fonts. An updated xfontsel version with this bug fixed
+comes with XFree86 4.0 / X11R6.8 or newer.
+
+If you use the Exceed X server on Microsoft Windows, then you will
+have to convert the BDF files into Microsoft FON files using the
+"Compile Fonts" function of Exceed xconfig. See the file exceed.txt
+for more information.
+
+There is one significant efficiency problem that X11R6 has with the
+sparsely populated ISO10646-1 fonts. X11 transmits and allocates 12
+bytes with the XFontStruct data structure for the difference between
+the lowest and the highest code value found in a font, no matter
+whether the code positions in between are used for characters or not.
+Even a tiny font that contains only two glyphs at positions 0x0000 and
+0xfffd causes 12 bytes * 65534 codes = 786 kbytes to be requested and
+stored by the client. Since all the ISO10646-1 BDF files provided in
+this package contain characters in the U+00xx (ASCII) and U+ffxx
+(ligatures, etc.) range, all of them would result in 786 kbyte large
+XCharStruct arrays in the per_char array of the corresponding
+XFontStruct (even for CharCell fonts!) when loaded by an X client.
+Until this problem is fixed by extending the X11 font protocol and
+implementation, non-CJK ISO10646-1 fonts that lack the (anyway not
+very interesting) characters above U+31FF seem to be the best
+compromise. The bdftruncate.pl program in this package can be used to
+deactivate any glyphs above a threshold code value in BDF files. This
+way, we get relatively memory-economic ISO10646-1 fonts that cause
+"only" 150 kbyte large XCharStruct arrays to be allocated. The
+deactivated glyphs are still present in the BDF files, but with an
+encoding value of -1 that causes them to be ignored.
+
+The ISO10646-1 fonts can not only be used directly by Unicode aware
+software, they can also be used to create any 8-bit font. The
+ucs2any.pl Perl script converts a ISO10646-1 BDF font into a BDF font
+file with some different encoding. For instance the command
+
+  perl ucs2any.pl 6x13.bdf MAPPINGS/8859-7.TXT ISO8859-7
+
+will generate the file 6x13-ISO8859-7.bdf according to the 8859-7.TXT
+Latin/Greek mapping table, which available from
+<ftp://ftp.unicode.org/Public/MAPPINGS/>. [The shell script
+./map_fonts automatically generates a subdirectory derived-fonts/ with
+many *.bdf and *.pcf.gz 8-bit versions of all the
+-misc-fixed-*-iso10646-1 fonts.]
+
+When you do a "make" in the submission/ subdirectory as suggested in
+the installation instructions above, this will generate exactly the
+set of fonts that have been submitted to the XFree86 project for
+inclusion into XFree86 4.0. These consists of all the ISO10646-1 fonts
+processed with "bdftruncate.pl U+3200" plus a selected set of derived
+8-bit fonts generated with ucs2any.pl.
+
+Every font comes with a *.repertoire-utf8 file that lists all the
+characters in this font.
+
+
+CONTRIBUTING
+------------
+
+If you want to help me in extending or improving the fonts, or if you
+want to start your own ISO 10646-1 font project, you will have to edit
+BDF font files. This is most comfortably done with the gbdfed font
+editor (version 1.3 or higher), which is available from
+
+    http://crl.nmsu.edu/~mleisher/gbdfed.html
+
+Once you are familiar with gbdfed, you will notice that it is no
+problem to design up to 100 nice characters per hour (even more if
+only placing accents is involved).
+
+Information about other X11 font tools and Unicode fonts for X11 in
+general can be found on
+
+    http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html
+
+The latest version of this package is available from
+
+    http://www.cl.cam.ac.uk/~mgk25/download/ucs-fonts.tar.gz
+
+If you want to contribute, then get the very latest version of this
+package, check which glyphs are still missing or inappropriate for
+your needs, and send me whatever you had the time to add and fix. Just
+email me the extended BDF-files back, or even better, send me a patch
+file of what you changed. The best way of preparing a patch file is
+
+  ./touch_id newfile.bdf
+  diff -d -u -F STARTCHAR oldfile.bdf newfile.bdf >file.diff
+
+which ensures that the patch file preserves information about which
+exact version you worked on and what character each "hunk" changes.
+
+I will try to update this packet on a daily basis. By sending me
+extensions to these fonts, you agree that the resulting improved font
+files will remain in the public domain for everyone's free use. Always
+make sure to load the very latest version of the package immediately
+before your start, and send me your results as soon as you are done,
+in order to avoid revision overlaps with other contributors.
+
+Please try to be careful with the glyphs you generate:
+
+  - Always look first at existing similar characters in order to
+    preserve a consistent look and feel for the entire font and
+    within the font family. For block graphics characters and geometric
+    symbols, take care of correct alignment.
+
+  - Read issues.txt, which contains some design hints for certain
+    characters.
+
+  - All characters of CharCell (C) fonts must strictly fit into
+    the pixel matrix and absolutely no out-of-box ink is allowed.
+
+  - The character cells will be displayed directly next to each other,
+    without any additional pixels in between. Therefore, always make
+    sure that at least the rightmost pixel column remains white, as
+    otherwise letters will stick together, except of course for
+    characters -- like Arabic or block graphics -- that are supposed to
+    stick together.
+
+  - Place accents as low as possible on the Latin characters.
+
+  - Try to keep the shape of accents consistent among each other and
+    with the combining characters in the U+03xx range.
+
+  - Use gbdfed only to edit the BDF file directly and do not import
+    the font that you want to edit from the X server. Use gbdfed 1.3
+    or higher.
+
+  - The glyph names should be the Adobe names for Unicode characters
+    defined at
+
+      http://www.adobe.com/devnet/opentype/archives/glyph.html
+
+    which gbdfed can set automatically. To make the Edit/Rename Glyphs/
+    Adobe Names function work, you have to download the file
+
+      http://www.adobe.com/devnet/opentype/archives/glyphlist.txt
+
+    and configure its location either in Edit/Preferences/Editing Options/
+    Adobe Glyph List, or as "adobe_name_file" in "~/.gbdfed".
+
+  - Be careful to not change the FONTBOUNDINGBOX box accidentally in
+    a patch.
+
+You should have a copy of the ISO 10646 standard
+
+  ISO/IEC 10646:2003, Information technology -- Universal
+  Multiple-Octet Coded Character Set (UCS),
+  International Organization for Standardization, Geneva, 2003.
+  http://standards.iso.org/ittf/PubliclyAvailableStandards/
+
+and/or the Unicode 5.0 book:
+
+  The Unicode Consortium: The Unicode Standard, Version 5.0,
+  Reading, MA, Addison-Wesley, 2006,
+  ISBN 9780321480910.
+  http://www.amazon.com/exec/obidos/ASIN/0321480910/mgk25
+
+All these fonts are from time to time resubmitted to the X.Org
+project, XFree86 (they have been in there since XFree86 4.0), and to
+other X server developers for inclusion into their normal X11
+distributions.
+
+Starting with XFree86 4.0, xterm has included UTF-8 support. This
+version is also available from
+
+  http://dickey.his.com/xterm/xterm.html
+
+Please make the developer of your favourite software aware of the
+UTF-8 definition in RFC 2279 and of the existence of this font
+collection. For more information on how to use UTF-8, please check out
+
+  http://www.cl.cam.ac.uk/~mgk25/unicode.html
+  ftp://ftp.ilog.fr/pub/Users/haible/utf8/Unicode-HOWTO.html
+
+where you will also find information on joining the
+linux-utf8@nl.linux.org mailing list.
+
+A number of UTF-8 example text files can be found in the examples/
+subdirectory or on 
+
+  http://www.cl.cam.ac.uk/~mgk25/ucs/examples/
+

assets/fonts/README.md

@@ -0,0 +1,72 @@
+## Provided fonts
+These are BDF fonts, a simple bitmap font-format that can be created
+by many font tools. Given that these are bitmap fonts, they will look good on
+very low resolution screens such as the LED displays.
+
+Fonts in this directory (except tom-thumb.bdf) are public domain (see the [README](./README)) and
+help you to get started with the font support in the API or the `text-util`
+from the utils/ directory.
+
+Tom-Thumb.bdf is included in this directory under [MIT license](http://vt100.tarunz.org/LICENSE). Tom-thumb.bdf was created by [@robey](http://twitter.com/robey) and originally published at https://robey.lag.net/2010/01/23/tiny-monospace-font.html
+
+The texgyre-27.bdf font was created using the [otf2bdf] tool from the TeX Gyre font.
+```bash
+otf2bdf -v -o texgyre-27.bdf -r 72 -p 27 texgyreadventor-regular.otf
+```
+
+## Create your own
+
+Fonts are in a human-readable and editable `*.bdf` format, but unless you
+like reading and writing pixels in hex, generating them is probably easier :)
+
+You can use any font-editor to generate a BDF font or use the conversion
+tool [otf2bdf] to create one from some other font format.
+
+Here is an example how you could create a 30-pixel high BDF font from some
+TrueType font:
+
+```bash
+otf2bdf -v -o myfont.bdf -r 72 -p 30 /path/to/font-Bold.ttf
+```
+
+## Getting otf2bdf
+
+Installing the tool should be fairly straightforward.
+
+```bash
+sudo apt-get install otf2bdf
+```
+
+## Compiling otf2bdf
+
+If you like to compile otf2bdf, you might notice that the configure script
+uses some old way of getting the freetype configuration. There does not seem
+to be much activity on the mature code, so let's patch that first:
+
+```bash
+sudo apt-get install -y libfreetype6-dev pkg-config autoconf
+git clone https://github.com/jirutka/otf2bdf.git   # check it out
+cd otf2bdf
+patch -p1 <<"EOF"
+--- a/configure.in
++++ b/configure.in
+@@ -5,8 +5,8 @@ AC_INIT(otf2bdf.c)
+ AC_PROG_CC
+
+ OLDLIBS=$LIBS
+-LIBS="$LIBS `freetype-config --libs`"
+-CPPFLAGS="$CPPFLAGS `freetype-config --cflags`"
++LIBS="$LIBS `pkg-config freetype2 --libs`"
++CPPFLAGS="$CPPFLAGS `pkg-config freetype2 --cflags`"
+ AC_CHECK_LIB(freetype, FT_Init_FreeType, LIBS="$LIBS -lfreetype",[
+              AC_MSG_ERROR([Can't find Freetype library! Compile FreeType first.])])
+ AC_SUBST(LIBS)
+EOF
+
+autoconf       # rebuild configure script
+./configure    # run configure
+make           # build the software
+sudo make install   # install it
+```
+
+[otf2bdf]: https://github.com/jirutka/otf2bdf

config/config.template.json

@@ -43,6 +43,50 @@
             }
         }
     },
+    "dim_schedule": {
+        "enabled": false,
+        "dim_brightness": 30,
+        "mode": "global",
+        "start_time": "20:00",
+        "end_time": "07:00",
+        "days": {
+            "monday": {
+                "enabled": true,
+                "start_time": "20:00",
+                "end_time": "07:00"
+            },
+            "tuesday": {
+                "enabled": true,
+                "start_time": "20:00",
+                "end_time": "07:00"
+            },
+            "wednesday": {
+                "enabled": true,
+                "start_time": "20:00",
+                "end_time": "07:00"
+            },
+            "thursday": {
+                "enabled": true,
+                "start_time": "20:00",
+                "end_time": "07:00"
+            },
+            "friday": {
+                "enabled": true,
+                "start_time": "20:00",
+                "end_time": "07:00"
+            },
+            "saturday": {
+                "enabled": true,
+                "start_time": "20:00",
+                "end_time": "07:00"
+            },
+            "sunday": {
+                "enabled": true,
+                "start_time": "20:00",
+                "end_time": "07:00"
+            }
+        }
+    },
     "timezone": "America/Chicago",
     "location": {
         "city": "Dallas",
@@ -64,15 +108,23 @@
             "disable_hardware_pulsing": false,
             "inverse_colors": false,
             "show_refresh_rate": false,
+            "led_rgb_sequence": "RGB",
             "limit_refresh_rate_hz": 100
         },
         "runtime": {
             "gpio_slowdown": 3
         },
-        "display_durations": {
+        "display_durations": {},
-            "calendar": 30
+        "use_short_date_format": true,
-        },
+        "vegas_scroll": {
-        "use_short_date_format": true
+            "enabled": false,
+            "scroll_speed": 50,
+            "separator_width": 32,
+            "plugin_order": [],
+            "excluded_plugins": [],
+            "target_fps": 125,
+            "buffer_ahead": 2
+        }
     },
     "plugin_system": {
         "plugins_directory": "plugin-repos",

config/config_secrets.template.json

@@ -1,16 +1,8 @@
 {
-    "weather": {
-        "api_key": "YOUR_OPENWEATHERMAP_API_KEY"
-    },
     "youtube": {
         "api_key": "YOUR_YOUTUBE_API_KEY",
         "channel_id": "YOUR_YOUTUBE_CHANNEL_ID"
     },
-    "music": {
-        "SPOTIFY_CLIENT_ID": "YOUR_SPOTIFY_CLIENT_ID_HERE",
-        "SPOTIFY_CLIENT_SECRET": "YOUR_SPOTIFY_CLIENT_SECRET_HERE",
-        "SPOTIFY_REDIRECT_URI": "http://127.0.0.1:8888/callback"
-    },
     "github": {
         "api_token": "YOUR_GITHUB_PERSONAL_ACCESS_TOKEN"
     }

docs/CONFIG_DEBUGGING.md

@@ -0,0 +1,316 @@
+# Configuration Debugging Guide
+
+This guide helps troubleshoot configuration issues in LEDMatrix.
+
+## Configuration Files
+
+### Main Files
+
+| File | Purpose |
+|------|---------|
+| `config/config.json` | Main configuration |
+| `config/config_secrets.json` | API keys and sensitive data |
+| `config/config.template.json` | Template for new installations |
+
+### Plugin Configuration
+
+Each plugin's configuration is a top-level key in `config.json`:
+
+```json
+{
+  "football-scoreboard": {
+    "enabled": true,
+    "display_duration": 30,
+    "nfl": {
+      "enabled": true,
+      "live_priority": false
+    }
+  },
+  "odds-ticker": {
+    "enabled": true,
+    "display_duration": 15
+  }
+}
+```
+
+## Schema Validation
+
+Plugins define their configuration schema in `config_schema.json`. This enables:
+- Automatic default value population
+- Configuration validation
+- Web UI form generation
+
+### Missing Schema Warning
+
+If a plugin doesn't have `config_schema.json`, you'll see:
+
+```
+WARNING - Plugin 'my-plugin' has no config_schema.json - configuration will not be validated.
+```
+
+**Fix**: Add a `config_schema.json` to your plugin directory.
+
+### Schema Example
+
+```json
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "type": "object",
+  "properties": {
+    "enabled": {
+      "type": "boolean",
+      "default": true,
+      "description": "Enable or disable this plugin"
+    },
+    "display_duration": {
+      "type": "number",
+      "default": 15,
+      "minimum": 1,
+      "description": "How long to display in seconds"
+    },
+    "api_key": {
+      "type": "string",
+      "description": "API key for data access"
+    }
+  },
+  "required": ["api_key"]
+}
+```
+
+## Common Configuration Issues
+
+### 1. Type Mismatches
+
+**Problem**: String value where number expected
+
+```json
+{
+  "display_duration": "30"  // Wrong: string
+}
+```
+
+**Fix**: Use correct types
+
+```json
+{
+  "display_duration": 30    // Correct: number
+}
+```
+
+**Logged Warning**:
+```
+WARNING - Config display_duration has invalid string value '30', using default 15.0
+```
+
+### 2. Missing Required Fields
+
+**Problem**: Required field not in config
+
+```json
+{
+  "football-scoreboard": {
+    "enabled": true
+    // Missing api_key which is required
+  }
+}
+```
+
+**Logged Error**:
+```
+ERROR - Plugin football-scoreboard configuration validation failed: 'api_key' is a required property
+```
+
+### 3. Invalid Nested Objects
+
+**Problem**: Wrong structure for nested config
+
+```json
+{
+  "football-scoreboard": {
+    "nfl": "enabled"  // Wrong: should be object
+  }
+}
+```
+
+**Fix**: Use correct structure
+
+```json
+{
+  "football-scoreboard": {
+    "nfl": {
+      "enabled": true
+    }
+  }
+}
+```
+
+### 4. Invalid JSON Syntax
+
+**Problem**: Malformed JSON
+
+```json
+{
+  "plugin": {
+    "enabled": true,  // Trailing comma
+  }
+}
+```
+
+**Fix**: Remove trailing commas, ensure valid JSON
+
+```json
+{
+  "plugin": {
+    "enabled": true
+  }
+}
+```
+
+**Tip**: Validate JSON at https://jsonlint.com/
+
+## Debugging Configuration Loading
+
+### Enable Debug Logging
+
+Set environment variable:
+```bash
+export LEDMATRIX_DEBUG=1
+python run.py
+```
+
+### Check Merged Configuration
+
+The configuration is merged with schema defaults. To see the final merged config:
+
+1. Enable debug logging
+2. Look for log entries like:
+   ```
+   DEBUG - Merged config with schema defaults for football-scoreboard
+   ```
+
+### Configuration Load Order
+
+1. Load `config.json`
+2. Load `config_secrets.json`
+3. Merge secrets into main config
+4. For each plugin:
+   - Load plugin's `config_schema.json`
+   - Extract default values from schema
+   - Merge user config with defaults
+   - Validate merged config against schema
+
+## Web Interface Issues
+
+### Changes Not Saving
+
+1. Check file permissions on `config/` directory
+2. Check disk space
+3. Look for errors in browser console
+4. Check server logs for save errors
+
+### Form Fields Not Appearing
+
+1. Plugin may not have `config_schema.json`
+2. Schema may have syntax errors
+3. Check browser console for JavaScript errors
+
+### Checkboxes Not Working
+
+Boolean values from checkboxes should be actual booleans, not strings:
+
+```json
+{
+  "enabled": true,     // Correct
+  "enabled": "true"    // Wrong
+}
+```
+
+## Config Key Collision Detection
+
+LEDMatrix detects potential config key conflicts:
+
+### Reserved Keys
+
+These plugin IDs will trigger a warning:
+- `display`, `schedule`, `timezone`, `plugin_system`
+- `display_modes`, `system`, `hardware`, `debug`
+- `log_level`, `emulator`, `web_interface`
+
+**Warning**:
+```
+WARNING - Plugin ID 'display' conflicts with reserved config key.
+```
+
+### Case Collisions
+
+Plugin IDs that differ only in case:
+```
+WARNING - Plugin ID 'Football-Scoreboard' may conflict with 'football-scoreboard' on case-insensitive file systems.
+```
+
+## Checking Configuration via API
+
+The API blueprint mounts at `/api/v3` (`web_interface/app.py:144`).
+
+```bash
+# Get full main config (includes all plugin sections)
+curl http://localhost:5000/api/v3/config/main
+
+# Save updated main config
+curl -X POST http://localhost:5000/api/v3/config/main \
+  -H "Content-Type: application/json" \
+  -d @new-config.json
+
+# Get config schema for a specific plugin
+curl "http://localhost:5000/api/v3/plugins/schema?plugin_id=football-scoreboard"
+
+# Get a single plugin's current config
+curl "http://localhost:5000/api/v3/plugins/config?plugin_id=football-scoreboard"
+```
+
+> There is no dedicated `/config/plugin/<id>` or `/config/validate`
+> endpoint — config validation runs server-side automatically when you
+> POST to `/config/main` or `/plugins/config`. See
+> [REST_API_REFERENCE.md](REST_API_REFERENCE.md) for the full list.
+
+## Backup and Recovery
+
+### Manual Backup
+
+```bash
+cp config/config.json config/config.backup.json
+```
+
+### Automatic Backups
+
+LEDMatrix creates backups before saves:
+- Location: `config/backups/`
+- Format: `config_YYYYMMDD_HHMMSS.json`
+
+### Recovery
+
+```bash
+# List backups
+ls -la config/backups/
+
+# Restore from backup
+cp config/backups/config_20240115_120000.json config/config.json
+```
+
+## Troubleshooting Checklist
+
+- [ ] JSON syntax is valid (no trailing commas, quotes correct)
+- [ ] Data types match schema (numbers are numbers, not strings)
+- [ ] Required fields are present
+- [ ] Nested objects have correct structure
+- [ ] File permissions allow read/write
+- [ ] No reserved config key collisions
+- [ ] Plugin has `config_schema.json` for validation
+
+## Getting Help
+
+1. Check logs: `tail -f logs/ledmatrix.log`
+2. Enable debug: `LEDMATRIX_DEBUG=1`
+3. Check error dashboard: `/api/v3/errors/summary`
+4. Validate JSON: https://jsonlint.com/
+5. File an issue: https://github.com/ChuckBuilds/LEDMatrix/issues

docs/DEVELOPER_QUICK_REFERENCE.md

@@ -62,7 +62,7 @@ display_manager.defer_update(lambda: self.update_cache(), priority=0)
 # Basic caching
 cached = cache_manager.get("key", max_age=3600)
 cache_manager.set("key", data)
-cache_manager.delete("key")
+cache_manager.delete("key")       # alias for clear_cache(key)
 
 # Advanced caching
 data = cache_manager.get_cached_data_with_strategy("key", data_type="weather")

docs/DEVELOPMENT.md

@@ -141,19 +141,27 @@ stage('Checkout') {
 
 ---
 
-## Plugin Submodules
+## Plugins
 
-Plugin submodules are located in the `plugins/` directory and are managed similarly:
+Plugins are **not** git submodules of this repository. The plugins
+directory (configured by `plugin_system.plugins_directory` in
+`config/config.json`, default `plugin-repos/`) is populated at install
+time by the plugin loader as users install plugins from the Plugin Store
+or from a GitHub URL via the web interface. Plugin source lives in a
+separate repository:
+[ChuckBuilds/ledmatrix-plugins](https://github.com/ChuckBuilds/ledmatrix-plugins).
 
-**Initialize all plugin submodules:**
+To work on a plugin locally without going through the Plugin Store, clone
-```bash
+that repo and symlink (or copy) the plugin directory into your configured
-git submodule update --init --recursive plugins/
+plugins directory — by default `plugin-repos/<plugin-id>/`. The plugin
-```
+loader will pick it up on the next display restart. The directory name
+must match the plugin's `id` in `manifest.json`.
 
-**Initialize a specific plugin:**
+For more information, see:
-```bash
-git submodule update --init --recursive plugins/hockey-scoreboard
-```
-
-For more information about plugins, see the [Plugin Development Guide](.cursor/plugins_guide.md) and [Plugin Architecture Specification](docs/PLUGIN_ARCHITECTURE_SPEC.md).
 
+- [PLUGIN_DEVELOPMENT_GUIDE.md](PLUGIN_DEVELOPMENT_GUIDE.md) — end-to-end
+  plugin development workflow
+- [PLUGIN_ARCHITECTURE_SPEC.md](PLUGIN_ARCHITECTURE_SPEC.md) — plugin system
+  specification
+- [DEV_PREVIEW.md](DEV_PREVIEW.md) — preview plugins on a desktop without a
+  Pi

docs/DEV_PREVIEW.md

@@ -0,0 +1,166 @@
+# Dev Preview & Visual Testing
+
+Tools for rapid plugin development without deploying to the RPi.
+
+## Dev Preview Server
+
+Interactive web UI for tweaking plugin configs and seeing the rendered display in real time.
+
+### Quick Start
+
+```bash
+python scripts/dev_server.py
+# Opens at http://localhost:5001
+```
+
+### Options
+
+```bash
+python scripts/dev_server.py --port 8080                          # Custom port
+python scripts/dev_server.py --extra-dir /path/to/custom-plugin   # 3rd party plugins
+python scripts/dev_server.py --debug                              # Flask debug mode
+```
+
+### Workflow
+
+1. Select a plugin from the dropdown (auto-discovers from `plugins/` and `plugin-repos/`)
+2. The config form auto-generates from the plugin's `config_schema.json`
+3. Tweak any config value — the display preview updates automatically
+4. Toggle "Auto" off for plugins with slow `update()` calls, then click "Render" manually
+5. Use the zoom slider to scale the tiny display (128x32) up for detailed inspection
+6. Toggle the grid overlay to see individual pixel boundaries
+
+### Mock Data for API-dependent Plugins
+
+Many plugins fetch data from APIs (sports scores, weather, stocks). To render these locally, expand "Mock Data" and paste a JSON object with cache keys the plugin expects.
+
+To find the cache keys a plugin uses, search its `manager.py` for `self.cache_manager.set(` calls.
+
+Example for a sports plugin:
+```json
+{
+  "football_scores": {
+    "games": [
+      {"home": "Eagles", "away": "Chiefs", "home_score": 24, "away_score": 21, "status": "Final"}
+    ]
+  }
+}
+```
+
+---
+
+## CLI Render Script
+
+Render any plugin to a PNG image from the command line. Useful for AI-assisted development and scripted workflows.
+
+### Usage
+
+```bash
+# Basic — renders with default config
+python scripts/render_plugin.py --plugin hello-world --output /tmp/hello.png
+
+# Custom config
+python scripts/render_plugin.py --plugin clock-simple \
+  --config '{"timezone":"America/New_York","time_format":"12h"}' \
+  --output /tmp/clock.png
+
+# Different display dimensions
+python scripts/render_plugin.py --plugin hello-world --width 64 --height 32 --output /tmp/small.png
+
+# 3rd party plugin from a custom directory
+python scripts/render_plugin.py --plugin my-plugin --plugin-dir /path/to/repo --output /tmp/my.png
+
+# With mock API data
+python scripts/render_plugin.py --plugin football-scoreboard \
+  --mock-data /tmp/mock_scores.json \
+  --output /tmp/football.png
+```
+
+### Using with Claude Code / AI
+
+Claude can run the render script, then read the output PNG (Claude is multimodal and can see images). This enables a visual feedback loop:
+
+```bash
+Claude → bash: python scripts/render_plugin.py --plugin hello-world --output /tmp/render.png
+Claude → Read /tmp/render.png   ← Claude sees the actual rendered display
+Claude → (makes code changes based on what it sees)
+Claude → bash: python scripts/render_plugin.py --plugin hello-world --output /tmp/render2.png
+Claude → Read /tmp/render2.png  ← verifies the visual change
+```
+
+---
+
+## VisualTestDisplayManager (for test suites)
+
+A display manager that renders real pixels for use in pytest, without requiring hardware.
+
+### Basic Usage
+
+```python
+from src.plugin_system.testing import VisualTestDisplayManager, MockCacheManager, MockPluginManager
+
+def test_my_plugin_renders_title():
+    display = VisualTestDisplayManager(width=128, height=32)
+    cache = MockCacheManager()
+    pm = MockPluginManager()
+
+    plugin = MyPlugin(
+        plugin_id='my-plugin',
+        config={'enabled': True, 'title': 'Hello'},
+        display_manager=display,
+        cache_manager=cache,
+        plugin_manager=pm
+    )
+
+    plugin.update()
+    plugin.display(force_clear=True)
+
+    # Verify pixels were drawn (not just that methods were called)
+    pixels = list(display.image.getdata())
+    assert any(p != (0, 0, 0) for p in pixels), "Display should not be blank"
+
+    # Save snapshot for manual inspection
+    display.save_snapshot('/tmp/test_my_plugin.png')
+```
+
+### Pytest Fixture
+
+A `visual_display_manager` fixture is available in plugin tests:
+
+```python
+def test_rendering(visual_display_manager):
+    visual_display_manager.draw_text("Test", x=10, y=10, color=(255, 255, 255))
+    assert visual_display_manager.width == 128
+    pixels = list(visual_display_manager.image.getdata())
+    assert any(p != (0, 0, 0) for p in pixels)
+```
+
+### Key Differences from MockDisplayManager
+
+| Feature | MockDisplayManager | VisualTestDisplayManager |
+|---------|-------------------|--------------------------|
+| Renders pixels | No (logs calls only) | Yes (real PIL rendering) |
+| Loads fonts | No | Yes (same fonts as production) |
+| Save to PNG | No | Yes (`save_snapshot()`) |
+| Call tracking | Yes | Yes (backwards compatible) |
+| Use case | Unit tests (method call assertions) | Visual tests, dev preview |
+
+---
+
+## Plugin Test Runner
+
+The test runner auto-detects `plugin-repos/` for monorepo development:
+
+```bash
+# Auto-detect (tries plugins/ then plugin-repos/)
+python scripts/run_plugin_tests.py
+
+# Test specific plugin
+python scripts/run_plugin_tests.py --plugin clock-simple
+
+# Explicit directory
+python scripts/run_plugin_tests.py --plugins-dir plugin-repos/
+
+# With coverage
+python scripts/run_plugin_tests.py --coverage --verbose
+```

docs/EMULATOR_SETUP_GUIDE.md

@@ -32,10 +32,15 @@ The LEDMatrix emulator allows you to run and test LEDMatrix displays on your com
 ### 1. Clone the Repository
 
 ```bash
-git clone https://github.com/your-username/LEDMatrix.git
+git clone --recurse-submodules https://github.com/ChuckBuilds/LEDMatrix.git
 cd LEDMatrix
 ```
 
+> The emulator does **not** require building the
+> `rpi-rgb-led-matrix-master` submodule (it uses `RGBMatrixEmulator`
+> instead), so `--recurse-submodules` is optional here. Run it anyway if
+> you also want to test the real-hardware code path.
+
 ### 2. Install Emulator Dependencies
 
 Install the emulator-specific requirements:
@@ -58,12 +63,13 @@ pip install -r requirements.txt
 
 ### 1. Emulator Configuration File
 
-The emulator uses `emulator_config.json` for configuration. Here's the default configuration:
+The emulator uses `emulator_config.json` for configuration. Here's the
+default configuration as it ships in the repo:
 
 ```json
 {
     "pixel_outline": 0,
-    "pixel_size": 16,
+    "pixel_size": 5,
     "pixel_style": "square",
     "pixel_glow": 6,
     "display_adapter": "pygame",
@@ -90,7 +96,7 @@ The emulator uses `emulator_config.json` for configuration. Here's the default c
 | Option | Description | Default | Values |
 |--------|-------------|---------|--------|
 | `pixel_outline` | Pixel border thickness | 0 | 0-5 |
-| `pixel_size` | Size of each pixel | 16 | 8-64 |
+| `pixel_size` | Size of each pixel | 5 | 1-64 (8–16 is typical for testing) |
 | `pixel_style` | Pixel shape | "square" | "square", "circle" |
 | `pixel_glow` | Glow effect intensity | 6 | 0-20 |
 | `display_adapter` | Display backend | "pygame" | "pygame", "browser" |

docs/FONT_MANAGER.md

@@ -138,6 +138,27 @@ font = self.font_manager.resolve_font(
 
 ## For Plugin Developers
 
+> **Note**: plugins that ship their own fonts via a `"fonts"` block
+> in `manifest.json` are registered automatically during plugin load
+> (`src/plugin_system/plugin_manager.py` calls
+> `FontManager.register_plugin_fonts()`). The `plugin://…` source
+> URIs documented below are resolved relative to the plugin's
+> install directory.
+>
+> The **Fonts** tab in the web UI that lists detected
+> manager-registered fonts is still a **placeholder
+> implementation** — fonts that managers register through
+> `register_manager_font()` do not yet appear there. The
+> programmatic per-element override workflow described in
+> [Manual Font Overrides](#manual-font-overrides) below
+> (`set_override()` / `remove_override()` / the
+> `config/font_overrides.json` store) **does** work today and is
+> the supported way to override a font for an element until the
+> Fonts tab is wired up. If you can't wait and need a workaround
+> right now, you can also just load the font directly with PIL
+> (or `freetype-py` for BDF) inside your plugin's `manager.py`
+> and skip the override system entirely.
+
 ### Plugin Font Registration
 
 In your plugin's `manifest.json`:
@@ -359,5 +380,8 @@ self.font = self.font_manager.resolve_font(
 
 ## Example: Complete Manager Implementation
 
-See `test/font_manager_example.py` for a complete working example.
+For a working example of the font manager API in use, see
+`src/font_manager.py` itself and the bundled scoreboard base classes
+in `src/base_classes/` (e.g., `hockey.py`, `football.py`) which
+register and resolve fonts via the patterns documented above.
 

docs/GETTING_STARTED.md

@@ -0,0 +1,337 @@
+# Getting Started with LEDMatrix
+
+## Welcome
+
+This guide will help you set up your LEDMatrix display for the first time and get it running in under 30 minutes.
+
+---
+
+## Prerequisites
+
+**Hardware:**
+- Raspberry Pi (3, 4, or 5 recommended)
+- RGB LED Matrix panel (32x64 or 64x64)
+- Adafruit RGB Matrix HAT or similar
+- Power supply (5V, 4A minimum recommended)
+- MicroSD card (16GB minimum)
+
+**Network:**
+- WiFi network (or Ethernet cable)
+- Computer with web browser on same network
+
+---
+
+## Quick Start (5 Minutes)
+
+### 1. First Boot
+
+1. Insert the MicroSD card with LEDMatrix installed
+2. Connect the LED matrix to your Raspberry Pi
+3. Plug in the power supply
+4. Wait for the Pi to boot (about 60 seconds)
+
+**Expected Behavior:**
+- LED matrix will light up
+- Display will show default plugins (clock, weather, etc.)
+- Pi creates WiFi network "LEDMatrix-Setup" if not connected
+
+### 2. Connect to WiFi
+
+**If you see "LEDMatrix-Setup" WiFi network:**
+1. Connect your device to "LEDMatrix-Setup" (open network, no password)
+2. Open browser to: `http://192.168.4.1:5000`
+3. Navigate to the WiFi tab
+4. Click "Scan" to find your WiFi network
+5. Select your network, enter password
+6. Click "Connect"
+7. Wait for connection (LED matrix will show confirmation)
+
+**If already connected to WiFi:**
+1. Find your Pi's IP address (check your router, or run `hostname -I` on the Pi)
+2. Open browser to: `http://your-pi-ip:5000`
+
+### 3. Access the Web Interface
+
+Once connected, access the web interface:
+
+```
+http://your-pi-ip:5000
+```
+
+You should see:
+- Overview tab with system stats
+- Live display preview
+- Quick action buttons
+
+---
+
+## Initial Configuration (15 Minutes)
+
+### Step 1: Configure Display Hardware
+
+1. Open the **Display** tab
+2. Set your matrix configuration:
+   - **Rows**: 32 or 64 (match your hardware)
+   - **Columns**: commonly 64 or 96; the web UI accepts any integer
+     in the 16–128 range, but 64 and 96 are the values the bundled
+     panel hardware ships with
+   - **Chain Length**: Number of panels chained horizontally
+   - **Hardware Mapping**: usually `adafruit-hat-pwm` (with the PWM jumper
+     mod) or `adafruit-hat` (without). See the root README for the full list.
+   - **Brightness**: 70–90 is fine for indoor use
+3. Click **Save**
+4. From the **Overview** tab, click **Restart Display Service** to apply
+
+**Tip:** if the display shows garbage or nothing, the most common culprits
+are an incorrect `hardware_mapping`, a `gpio_slowdown` value that doesn't
+match your Pi model, or panels needing the E-line mod. See
+[TROUBLESHOOTING.md](TROUBLESHOOTING.md).
+
+### Step 2: Set Timezone and Location
+
+1. Open the **General** tab
+2. Set your timezone (e.g., `America/New_York`) and location
+3. Click **Save**
+
+Correct timezone ensures accurate time display, and location is used by
+weather and other location-aware plugins.
+
+### Step 3: Install Plugins
+
+1. Open the **Plugin Manager** tab
+2. Scroll to the **Plugin Store** section to browse available plugins
+3. Click **Install** on the plugins you want
+4. Wait for installation to finish — installed plugins appear in the
+   **Installed Plugins** section above and get their own tab in the second
+   nav row
+5. Toggle the plugin to enabled
+6. From **Overview**, click **Restart Display Service**
+
+You can also install community plugins straight from a GitHub URL using the
+**Install from GitHub** section further down the same tab — see
+[PLUGIN_STORE_GUIDE.md](PLUGIN_STORE_GUIDE.md) for details.
+
+### Step 4: Configure Plugins
+
+1. Each installed plugin gets its own tab in the second navigation row
+2. Open that plugin's tab to edit its settings (favorite teams, API keys,
+   update intervals, display duration, etc.)
+3. Click **Save**
+4. Restart the display service from **Overview** so the new settings take
+   effect
+
+**Example: Weather Plugin**
+- Set your location (city, state, country)
+- Add an API key from OpenWeatherMap (free signup) to
+  `config/config_secrets.json` or directly in the plugin's config screen
+- Set the update interval (300 seconds is reasonable)
+
+---
+
+## Testing Your Display
+
+### Run a single plugin on demand
+
+The fastest way to verify a plugin works without waiting for the rotation:
+
+1. Open the plugin's tab (second nav row)
+2. Scroll to **On-Demand Controls**
+3. Click **Run On-Demand** — the plugin runs immediately even if disabled
+4. Click **Stop On-Demand** to return to the normal rotation
+
+### Check the live preview and logs
+
+- The **Overview** tab shows a **Live Display Preview** that mirrors what's
+  on the matrix in real time — handy for debugging without looking at the
+  panel.
+- The **Logs** tab streams the display and web service logs. Look for
+  `ERROR` lines if something isn't working; normal operation just shows
+  `INFO` messages about plugin rotation.
+
+---
+
+## Common First-Time Issues
+
+### Display Not Showing Anything
+
+**Check:**
+1. Power supply connected and adequate (5V, 4A minimum)
+2. LED matrix connected to the bonnet/HAT correctly
+3. Display service running: `sudo systemctl status ledmatrix`
+4. Hardware configuration matches your matrix (rows/cols/chain length)
+
+**Fix:**
+1. Restart from the **Overview** tab → **Restart Display Service**
+2. Or via SSH: `sudo systemctl restart ledmatrix`
+
+### Web Interface Won't Load
+
+**Check:**
+1. Pi is connected to network: `ping your-pi-ip`
+2. Web service running: `sudo systemctl status ledmatrix-web`
+3. Correct port: the web UI listens on `:5000`
+4. Firewall not blocking port 5000
+
+**Fix:**
+1. Restart web service: `sudo systemctl restart ledmatrix-web`
+2. Check logs: `sudo journalctl -u ledmatrix-web -n 50`
+
+### Plugins Not Showing
+
+**Check:**
+1. Plugin is enabled (toggle on the **Plugin Manager** tab)
+2. Display service was restarted after enabling
+3. Plugin's display duration is non-zero
+4. No errors in the **Logs** tab for that plugin
+
+**Fix:**
+1. Enable the plugin from **Plugin Manager**
+2. Click **Restart Display Service** on **Overview**
+3. Check the **Logs** tab for plugin-specific errors
+
+### Weather Plugin Shows "No Data"
+
+**Check:**
+1. API key configured (OpenWeatherMap)
+2. Location is correct (city, state, country)
+3. Internet connection working
+
+**Fix:**
+1. Sign up at openweathermap.org (free)
+2. Add API key to config_secrets.json or plugin config
+3. Restart display
+
+---
+
+## Next Steps
+
+### Customize Your Display
+
+**Adjust display durations:**
+- Each plugin's tab has a **Display Duration (seconds)** field — set how
+  long that plugin stays on screen each rotation.
+
+**Organize plugin order:**
+- Use the **Plugin Manager** tab to enable/disable plugins. The display
+  cycles through enabled plugins in the order they appear.
+
+**Add more plugins:**
+- Check the **Plugin Store** section of **Plugin Manager** for new plugins.
+- Install community plugins straight from a GitHub URL via
+  **Install from GitHub** on the same tab.
+
+### Enable Advanced Features
+
+**Vegas Scroll Mode:**
+- Continuous scrolling ticker display
+- See [ADVANCED_FEATURES.md](ADVANCED_FEATURES.md) for details
+
+**On-Demand Display:**
+- Manually trigger specific plugins
+- Pin important information
+- See [ADVANCED_FEATURES.md](ADVANCED_FEATURES.md) for details
+
+**Background Services:**
+- Non-blocking data fetching
+- Faster plugin rotation
+- See [ADVANCED_FEATURES.md](ADVANCED_FEATURES.md) for details
+
+### Explore Documentation
+
+- [WEB_INTERFACE_GUIDE.md](WEB_INTERFACE_GUIDE.md) - Complete web interface guide
+- [WIFI_NETWORK_SETUP.md](WIFI_NETWORK_SETUP.md) - WiFi configuration details
+- [PLUGIN_STORE_GUIDE.md](PLUGIN_STORE_GUIDE.md) - Installing and managing plugins
+- [TROUBLESHOOTING.md](TROUBLESHOOTING.md) - Solving common issues
+- [ADVANCED_FEATURES.md](ADVANCED_FEATURES.md) - Advanced functionality
+
+### Join the Community
+
+- Report issues on GitHub
+- Share your custom plugins
+- Help others in discussions
+- Contribute improvements
+
+---
+
+## Quick Reference
+
+### Service Commands
+
+```bash
+# Check status
+sudo systemctl status ledmatrix
+sudo systemctl status ledmatrix-web
+
+# Restart services
+sudo systemctl restart ledmatrix
+sudo systemctl restart ledmatrix-web
+
+# View logs
+sudo journalctl -u ledmatrix -f
+sudo journalctl -u ledmatrix-web -f
+```
+
+### File Locations
+
+```
+/home/ledpi/LEDMatrix/
+├── config/
+│   ├── config.json           # Main configuration
+│   ├── config_secrets.json   # API keys and secrets
+│   └── wifi_config.json      # WiFi settings
+├── plugin-repos/             # Installed plugins (default location)
+├── cache/                    # Cached data
+└── web_interface/            # Web interface files
+```
+
+> The plugin install location is configurable via
+> `plugin_system.plugins_directory` in `config.json`. The default is
+> `plugin-repos/`. Plugin discovery (`PluginManager.discover_plugins()`)
+> only scans the configured directory — it does not fall back to
+> `plugins/`. However, the Plugin Store install/update path and the
+> web UI's schema loader do also probe `plugins/` so the dev symlinks
+> created by `scripts/dev/dev_plugin_setup.sh` keep working.
+
+### Web Interface
+
+```
+Main Interface: http://your-pi-ip:5000
+
+System tabs:
+- Overview          System stats, live preview, quick actions
+- General           Timezone, location, plugin-system settings
+- WiFi              Network selection and AP-mode setup
+- Schedule          Power and dim schedules
+- Display           Matrix hardware configuration
+- Config Editor     Raw config.json editor
+- Fonts             Upload and manage fonts
+- Logs              Real-time log viewing
+- Cache             Cached data inspection and cleanup
+- Operation History Recent service operations
+
+Plugin tabs (second row):
+- Plugin Manager    Browse the Plugin Store, install/enable plugins
+- <plugin-id>       One tab per installed plugin for its config
+```
+
+### WiFi Access Point
+
+```
+Network Name: LEDMatrix-Setup
+Password: (none - open network)
+URL when connected: http://192.168.4.1:5000
+```
+
+---
+
+## Congratulations!
+
+Your LEDMatrix display is now set up and running. Explore the web interface, try different plugins, and customize it to your liking.
+
+**Need Help?**
+- Check [TROUBLESHOOTING.md](TROUBLESHOOTING.md)
+- Review detailed guides for specific features
+- Report issues on GitHub
+- Ask questions in community discussions
+
+Enjoy your LED matrix display!

docs/HOW_TO_RUN_TESTS.md

@@ -13,7 +13,7 @@ Make sure you have the testing packages installed:
 pip install -r requirements.txt
 
 # Or install just the test dependencies
-pip install pytest pytest-cov pytest-mock pytest-timeout
+pip install pytest pytest-cov pytest-mock
 ```
 
 ### 2. Set Environment Variables
@@ -85,8 +85,14 @@ pytest -m slow
 # Run all tests in the test directory
 pytest test/
 
-# Run all integration tests
+# Run plugin tests only
-pytest test/integration/
+pytest test/plugins/
+
+# Run web interface tests only
+pytest test/web_interface/
+
+# Run web interface integration tests
+pytest test/web_interface/integration/
 ```
 
 ## Understanding Test Output
@@ -233,18 +239,39 @@ pytest --maxfail=3
 test/
 ├── conftest.py                          # Shared fixtures and configuration
 ├── test_display_controller.py           # Display controller tests
-├── test_plugin_system.py          # Plugin system tests
 ├── test_display_manager.py              # Display manager tests
-├── test_config_service.py         # Config service tests
+├── test_plugin_system.py                # Plugin system tests
+├── test_plugin_loader.py                # Plugin discovery/loading tests
+├── test_plugin_loading_failures.py      # Plugin failure-mode tests
 ├── test_cache_manager.py                # Cache manager tests
-├── test_font_manager.py           # Font manager tests
-├── test_error_handling.py         # Error handling tests
 ├── test_config_manager.py               # Config manager tests
-├── integration/                   # Integration tests
+├── test_config_service.py               # Config service tests
-│   ├── test_e2e.py               # End-to-end tests
+├── test_config_validation_edge_cases.py # Config edge cases
-│   └── test_plugin_integration.py # Plugin integration tests
+├── test_font_manager.py                 # Font manager tests
-├── test_error_scenarios.py        # Error scenario tests
+├── test_layout_manager.py               # Layout manager tests
-└── test_edge_cases.py             # Edge case tests
+├── test_text_helper.py                  # Text helper tests
+├── test_error_handling.py               # Error handling tests
+├── test_error_aggregator.py             # Error aggregation tests
+├── test_schema_manager.py               # Schema manager tests
+├── test_web_api.py                      # Web API tests
+├── test_nba_*.py                        # NBA-specific test suites
+├── plugins/                             # Per-plugin test suites
+│   ├── test_clock_simple.py
+│   ├── test_calendar.py
+│   ├── test_basketball_scoreboard.py
+│   ├── test_soccer_scoreboard.py
+│   ├── test_odds_ticker.py
+│   ├── test_text_display.py
+│   ├── test_visual_rendering.py
+│   └── test_plugin_base.py
+└── web_interface/
+    ├── test_config_manager_atomic.py
+    ├── test_state_reconciliation.py
+    ├── test_plugin_operation_queue.py
+    ├── test_dedup_unique_arrays.py
+    └── integration/                     # Web interface integration tests
+        ├── test_config_flows.py
+        └── test_plugin_operations.py
 ```
 
 ### Test Categories
@@ -309,11 +336,15 @@ pytest --cov=src --cov-report=html
 
 ## Continuous Integration
 
-Tests are configured to run automatically in CI/CD. The GitHub Actions workflow (`.github/workflows/tests.yml`) runs:
+The repo runs
-
+[`.github/workflows/security-audit.yml`](../.github/workflows/security-audit.yml)
-- All tests on multiple Python versions (3.10, 3.11, 3.12)
+(bandit + semgrep) on every push. A pytest CI workflow at
-- Coverage reporting
+`.github/workflows/tests.yml` is queued to land alongside this
-- Uploads coverage to Codecov (if configured)
+PR ([ChuckBuilds/LEDMatrix#307](https://github.com/ChuckBuilds/LEDMatrix/pull/307));
+the workflow file itself was held back from that PR because the
+push token lacked the GitHub `workflow` scope, so it needs to be
+committed separately by a maintainer. Once it's in, this section
+will be updated to describe what the job runs.
 
 ## Best Practices
 

docs/MIGRATION_GUIDE.md

@@ -88,8 +88,8 @@ If you encounter issues during migration:
 
 1. Check the [README.md](README.md) for current installation and usage instructions
 2. Review script README files:
-   - `scripts/install/README.md` - Installation scripts documentation
+   - [`scripts/install/README.md`](../scripts/install/README.md) - Installation scripts documentation
-   - `scripts/fix_perms/README.md` (if exists) - Permission scripts documentation
+   - [`scripts/fix_perms/README.md`](../scripts/fix_perms/README.md) - Permission scripts documentation
 3. Check system logs: `journalctl -u ledmatrix -f` or `journalctl -u ledmatrix-web -f`
 4. Review the troubleshooting section in the main README
 

docs/PLUGIN_API_REFERENCE.md

@@ -114,6 +114,95 @@ Get display duration for this plugin. Can be overridden for dynamic durations.
 
 Return plugin info for display in web UI. Override to provide additional state information.
 
+### Dynamic-duration hooks
+
+Plugins that render multi-step content (e.g. cycling through several games)
+can extend their display time until they've shown everything. To opt in,
+either set `dynamic_duration.enabled: true` in the plugin's config or
+override `supports_dynamic_duration()`.
+
+#### `supports_dynamic_duration() -> bool`
+
+Return `True` if this plugin should use dynamic durations. Default reads
+`config["dynamic_duration"]["enabled"]`.
+
+#### `get_dynamic_duration_cap() -> Optional[float]`
+
+Maximum number of seconds the controller will keep this plugin on screen
+in dynamic mode. Default reads
+`config["dynamic_duration"]["max_duration_seconds"]`.
+
+#### `is_cycle_complete() -> bool`
+
+Override this to return `True` only after the plugin has rendered all of
+its content for the current rotation. Default returns `True` immediately,
+which means a single `display()` call counts as a full cycle.
+
+#### `reset_cycle_state() -> None`
+
+Called by the controller before each new dynamic-duration session. Reset
+internal counters/iterators here.
+
+### Live priority hooks
+
+Live priority lets a plugin temporarily take over the rotation when it has
+urgent content (live games, breaking news). Enable by setting
+`live_priority: true` in the plugin's config and overriding
+`has_live_content()`.
+
+#### `has_live_priority() -> bool`
+
+Whether live priority is enabled in config (default reads
+`config["live_priority"]`).
+
+#### `has_live_content() -> bool`
+
+Override to return `True` when the plugin currently has urgent content.
+Default returns `False`.
+
+#### `get_live_modes() -> List[str]`
+
+List of display modes to show during a live takeover. Default returns the
+plugin's `display_modes` from its manifest.
+
+### Vegas scroll hooks
+
+Vegas mode shows multiple plugins as a single continuous scroll instead of
+rotating one at a time. Plugins control how their content appears via
+these hooks. See [ADVANCED_FEATURES.md](ADVANCED_FEATURES.md) for the user
+side of Vegas mode.
+
+#### `get_vegas_content() -> Optional[PIL.Image | List[PIL.Image] | None]`
+
+Return content to inject into the scroll. Multi-item plugins (sports,
+odds, news) should return a *list* of PIL Images so each item scrolls
+independently. Static plugins (clock, weather) can return a single image.
+Returning `None` falls back to capturing whatever `display()` produces.
+
+#### `get_vegas_content_type() -> str`
+
+`'multi'`, `'static'`, or `'none'`. Affects how Vegas mode treats the
+plugin. Default `'static'`.
+
+#### `get_vegas_display_mode() -> VegasDisplayMode`
+
+Returns one of `VegasDisplayMode.SCROLL`, `FIXED_SEGMENT`, or `STATIC`.
+Read from `config["vegas_mode"]` or override directly.
+
+#### `get_supported_vegas_modes() -> List[VegasDisplayMode]`
+
+The set of Vegas modes this plugin can render. Used by the UI to populate
+the mode selector for this plugin.
+
+#### `get_vegas_segment_width() -> Optional[int]`
+
+For `FIXED_SEGMENT` plugins, the width in pixels of the segment they
+occupy in the scroll. `None` lets the controller pick a default.
+
+> The full source for `BasePlugin` lives in
+> `src/plugin_system/base_plugin.py`. If a method here disagrees with the
+> source, the source wins — please open an issue or PR to fix the doc.
+
 ---
 
 ## Display Manager
@@ -228,23 +317,31 @@ date_str = self.display_manager.format_date_with_ordinal(datetime.now())
 
 ### Image Rendering
 
-#### `draw_image(image: PIL.Image, x: int, y: int) -> None`
+The display manager doesn't provide a dedicated `draw_image()` method.
+Instead, plugins paste directly onto the underlying PIL Image
+(`display_manager.image`), then call `update_display()` to push the buffer
+to the matrix.
 
-Draw a PIL Image object on the canvas.
-
-**Parameters**:
-- `image`: PIL Image object
-- `x` (int): X position (left edge)
-- `y` (int): Y position (top edge)
-
-**Example**:
 ```python
 from PIL import Image
-logo = Image.open("assets/logo.png")
+
-self.display_manager.draw_image(logo, x=10, y=10)
+logo = Image.open("assets/logo.png").convert("RGB")
+self.display_manager.image.paste(logo, (10, 10))
 self.display_manager.update_display()
 ```
 
+For transparency support, paste using a mask:
+
+```python
+icon = Image.open("assets/icon.png").convert("RGBA")
+self.display_manager.image.paste(icon, (5, 5), icon)
+self.display_manager.update_display()
+```
+
+This is the same pattern the bundled scoreboard base classes
+(`src/base_classes/baseball.py`, `basketball.py`, `football.py`,
+`hockey.py`) use, so it's the canonical way to render arbitrary images.
+
 ### Weather Icons
 
 #### `draw_weather_icon(condition: str, x: int, y: int, size: int = 16) -> None`
@@ -440,12 +537,23 @@ self.cache_manager.set("weather_data", {
 })
 ```
 
-#### `delete(key: str) -> None`
+#### `clear_cache(key: Optional[str] = None) -> None`
 
-Remove a specific cache entry.
+Remove a specific cache entry, or all cache entries when called without
+arguments.
 
 **Parameters**:
-- `key` (str): Cache key to delete
+- `key` (str, optional): Cache key to delete. If omitted, every cached
+  entry (memory + disk) is cleared.
+
+**Example**:
+```python
+# Drop one stale entry
+self.cache_manager.clear_cache("weather_data")
+
+# Nuke everything (rare — typically only used by maintenance tooling)
+self.cache_manager.clear_cache()
+```
 
 ### Advanced Methods
 

docs/PLUGIN_ARCHITECTURE_SPEC.md

@@ -1,5 +1,24 @@
 # LEDMatrix Plugin Architecture Specification
 
+> **Historical design document.** This spec was written *before* the
+> plugin system was built. Most of it is still architecturally
+> accurate, but specific details have drifted from the shipped
+> implementation:
+>
+> - Code paths reference `web_interface_v2.py`; the current web UI is
+>   `web_interface/app.py` with v3 Blueprint-based templates.
+> - The example Flask routes use `/api/plugins/*`; the real API
+>   blueprint is mounted at `/api/v3` (`web_interface/app.py:144`).
+> - The default plugin location is `plugin-repos/` (configurable via
+>   `plugin_system.plugins_directory`), not `./plugins/`.
+> - The "Migration Strategy" and "Implementation Roadmap" sections
+>   describe work that has now shipped.
+>
+> For the current system, see:
+> [PLUGIN_DEVELOPMENT_GUIDE.md](PLUGIN_DEVELOPMENT_GUIDE.md),
+> [PLUGIN_API_REFERENCE.md](PLUGIN_API_REFERENCE.md), and
+> [REST_API_REFERENCE.md](REST_API_REFERENCE.md).
+
 ## Executive Summary
 
 This document outlines the transformation of the LEDMatrix project into a modular, plugin-based architecture that enables user-created displays. The goal is to create a flexible, extensible system similar to Home Assistant Community Store (HACS) where users can discover, install, and manage custom display managers from GitHub repositories.
@@ -9,7 +28,7 @@ This document outlines the transformation of the LEDMatrix project into a modula
 1. **Gradual Migration**: Existing managers remain in core while new plugin infrastructure is built
 2. **Migration Required**: Breaking changes with migration tools provided
 3. **GitHub-Based Store**: Simple discovery system, packages served from GitHub repos
-4. **Plugin Location**: `./plugins/` directory in project root
+4. **Plugin Location**: `./plugins/` directory in project root *(actual default is now `plugin-repos/`)*
 
 ---
 

docs/PLUGIN_CONFIGURATION_GUIDE.md

@@ -184,37 +184,45 @@ plugin-repos/
 
 ```json
 {
+    "id": "my-plugin",
     "name": "My Plugin",
     "version": "1.0.0",
     "description": "Plugin description",
     "author": "Your Name",
+    "entry_point": "manager.py",
+    "class_name": "MyPlugin",
     "display_modes": ["my_plugin"],
-    "config_schema": {
+    "config_schema": "config_schema.json"
-        "type": "object",
-        "properties": {
-            "enabled": {"type": "boolean", "default": false},
-            "update_interval": {"type": "integer", "default": 3600}
-        }
-    }
 }
 ```
 
+The required fields the plugin loader will check for are `id`,
+`name`, `version`, `class_name`, and `display_modes`. `entry_point`
+defaults to `manager.py` if omitted. `config_schema` must be a
+**file path** (relative to the plugin directory) — the schema itself
+lives in a separate JSON file, not inline in the manifest. The
+`class_name` value must match the actual class defined in the entry
+point file **exactly** (case-sensitive, no spaces); otherwise the
+loader fails with `AttributeError` at load time.
+
 ### Plugin Manager Class
 
 ```python
 from src.plugin_system.base_plugin import BasePlugin
 
-class MyPluginManager(BasePlugin):
+class MyPlugin(BasePlugin):
-    def __init__(self, config, display_manager, cache_manager, font_manager):
+    def __init__(self, plugin_id, config, display_manager, cache_manager, plugin_manager):
-        super().__init__(config, display_manager, cache_manager, font_manager)
+        super().__init__(plugin_id, config, display_manager, cache_manager, plugin_manager)
-        self.enabled = config.get('enabled', False)
+        # self.config, self.display_manager, self.cache_manager,
+        # self.plugin_manager, self.logger, and self.enabled are
+        # all set up by BasePlugin.__init__.
 
     def update(self):
-        """Update plugin data"""
+        """Fetch/update data. Called based on update_interval."""
         pass
 
     def display(self, force_clear=False):
-        """Display plugin content"""
+        """Render plugin content to the LED matrix."""
         pass
     
     def get_duration(self):

docs/PLUGIN_CONFIGURATION_TABS.md

@@ -1,5 +1,15 @@
 # Plugin Configuration Tabs
 
+> **Status note:** this doc was written during the rollout of the
+> per-plugin configuration tab feature. The feature itself is shipped
+> and working in the current v3 web interface, but a few file paths
+> in the "Implementation Details" section below still reference the
+> pre-v3 file layout (`web_interface_v2.py`, `templates/index_v2.html`).
+> The current implementation lives in `web_interface/app.py`,
+> `web_interface/blueprints/api_v3.py`, and `web_interface/templates/v3/`.
+> The user-facing description (Overview, Features, Form Generation
+> Process) is still accurate.
+
 ## Overview
 
 Each installed plugin now gets its own dedicated configuration tab in the web interface. This provides a clean, organized way to configure plugins without cluttering the main Plugins management tab.
@@ -29,10 +39,14 @@ Each installed plugin now gets its own dedicated configuration tab in the web in
 3. Click **Save Configuration**
 4. Restart the display service to apply changes
 
-### Plugin Management vs Configuration
+### Plugin Manager vs Per-Plugin Configuration
 
-- **Plugins Tab**: Used for plugin management (install, enable/disable, update, uninstall)
+- **Plugin Manager tab** (second nav row): used for browsing the
-- **Plugin-Specific Tabs**: Used for configuring plugin behavior and settings
+  Plugin Store, installing plugins, toggling installed plugins on/off,
+  and updating/uninstalling them
+- **Per-plugin tabs** (one per installed plugin, also in the second
+  nav row): used for configuring that specific plugin's behavior and
+  settings via a form auto-generated from its `config_schema.json`
 
 ## For Plugin Developers
 
@@ -194,12 +208,12 @@ Renders as: Dropdown select
 
 ### Form Generation Process
 
-1. Web UI loads installed plugins via `/api/plugins/installed`
+1. Web UI loads installed plugins via `/api/v3/plugins/installed`
 2. For each plugin, the backend loads its `config_schema.json`
 3. Frontend generates a tab button with plugin name
 4. Frontend generates a form based on the JSON Schema
 5. Current config values from `config.json` are populated
-6. When saved, each field is sent to `/api/plugins/config` endpoint
+6. When saved, each field is sent to `/api/v3/plugins/config` endpoint
 
 ## Implementation Details
 
@@ -207,7 +221,7 @@ Renders as: Dropdown select
 
 **File**: `web_interface_v2.py`
 
-- Modified `/api/plugins/installed` endpoint to include `config_schema_data`
+- Modified `/api/v3/plugins/installed` endpoint to include `config_schema_data`
 - Loads each plugin's `config_schema.json` if it exists
 - Returns schema data along with plugin info
 
@@ -227,7 +241,7 @@ New Functions:
 ```
 Page Load
   → refreshPlugins()
-    → /api/plugins/installed
+    → /api/v3/plugins/installed
       → Returns plugins with config_schema_data
     → generatePluginTabs()
       → Creates tab buttons
@@ -241,7 +255,7 @@ User Saves
   → savePluginConfiguration()
     → Reads form data
     → Converts types per schema
-    → Sends to /api/plugins/config
+    → Sends to /api/v3/plugins/config
       → Updates config.json
     → Shows success notification
 ```

docs/PLUGIN_CONFIG_ARCHITECTURE.md

@@ -31,7 +31,7 @@
 ┌─────────────────────────────────────────────────────────────────┐
 │                      Flask Backend                               │
 │  ┌───────────────────────────────────────────────────────┐     │
-│  │         /api/plugins/installed                         │     │
+│  │         /api/v3/plugins/installed                         │     │
 │  │  • Discover plugins in plugins/ directory              │     │
 │  │  • Load manifest.json for each plugin                  │     │
 │  │  • Load config_schema.json if exists                   │     │
@@ -40,7 +40,7 @@
 │  └───────────────────────────────────────────────────────┘     │
 │                                                                   │
 │  ┌───────────────────────────────────────────────────────┐     │
-│  │         /api/plugins/config                            │     │
+│  │         /api/v3/plugins/config                            │     │
 │  │  • Receive key-value pair                              │     │
 │  │  • Update config.json                                  │     │
 │  │  • Return success/error                                │     │
@@ -88,7 +88,7 @@ DOMContentLoaded Event
 refreshPlugins()
          │
          ▼
-GET /api/plugins/installed
+GET /api/v3/plugins/installed
          │
          ├─→ For each plugin directory:
          │   ├─→ Read manifest.json
@@ -146,7 +146,7 @@ savePluginConfiguration(pluginId)
          │   │   • array: split(',')
          │   │   • string: as-is
          │   │
-         │   └─→ POST /api/plugins/config
+         │   └─→ POST /api/v3/plugins/config
          │       {
          │         plugin_id: "hello-world",
          │         key: "message",
@@ -174,7 +174,7 @@ Refresh Plugins
 Window Load
   └── DOMContentLoaded
       └── refreshPlugins()
-          ├── fetch('/api/plugins/installed')
+          ├── fetch('/api/v3/plugins/installed')
           ├── renderInstalledPlugins(plugins)
           └── generatePluginTabs(plugins)
               └── For each plugin:
@@ -198,19 +198,19 @@ User Interactions
   │   ├── Process form data
   │   ├── Convert types per schema
   │   └── For each field:
-  │       └── POST /api/plugins/config
+  │       └── POST /api/v3/plugins/config
   │
   └── resetPluginConfig(pluginId)
       ├── Get schema defaults
       └── For each field:
-          └── POST /api/plugins/config
+          └── POST /api/v3/plugins/config
 ```
 
 ### Backend (Python)
 
 ```
 Flask Routes
-  ├── /api/plugins/installed (GET)
+  ├── /api/v3/plugins/installed (GET)
   │   └── api_plugins_installed()
   │       ├── PluginManager.discover_plugins()
   │       ├── For each plugin:
@@ -219,7 +219,7 @@ Flask Routes
   │       │   └── Load config from config.json
   │       └── Return JSON response
   │
-  └── /api/plugins/config (POST)
+  └── /api/v3/plugins/config (POST)
       └── api_plugin_config()
           ├── Parse request JSON
           ├── Load current config
@@ -279,7 +279,7 @@ LEDMatrix/
 ### 3. Individual Config Updates
 
 **Why**: Simplifies backend API  
-**How**: Each field saved separately via `/api/plugins/config`  
+**How**: Each field saved separately via `/api/v3/plugins/config`  
 **Benefit**: Atomic updates, easier error handling
 
 ### 4. Type Conversion in Frontend

docs/PLUGIN_CONFIG_QUICK_START.md

@@ -4,13 +4,14 @@
 
 ### For Users
 
-1. Open the web interface: `http://your-pi-ip:5001`
+1. Open the web interface: `http://your-pi-ip:5000`
-2. Go to the **Plugin Store** tab
+2. Open the **Plugin Manager** tab
-3. Install a plugin (e.g., "Hello World")
+3. Find a plugin in the **Plugin Store** section (e.g., "Hello World")
-4. Notice a new tab appears with the plugin's name
+   and click **Install**
-5. Click on the plugin's tab to configure it
+4. Notice a new tab appears in the second nav row with the plugin's name
-6. Modify settings and click **Save Configuration**
+5. Click that tab to configure the plugin
-7. Restart the display to see changes
+6. Modify settings and click **Save**
+7. From **Overview**, click **Restart Display Service** to see changes
 
 That's it! Each installed plugin automatically gets its own configuration tab.
 
@@ -171,9 +172,11 @@ User enters: `255, 0, 0`
 ### For Users
 
 1. **Reset Anytime**: Use "Reset to Defaults" to restore original settings
-2. **Navigate Back**: Click "Back to Plugin Management" to return to Plugins tab
+2. **Navigate Back**: Switch to the **Plugin Manager** tab to see the
+   full list of installed plugins
 3. **Check Help Text**: Each field has a description explaining what it does
-4. **Restart Required**: Remember to restart the display after saving
+4. **Restart Required**: Remember to restart the display service from
+   **Overview** after saving
 
 ### For Developers
 
@@ -206,8 +209,10 @@ User enters: `255, 0, 0`
 ## 📚 Next Steps
 
 - Read the full documentation: [PLUGIN_CONFIGURATION_TABS.md](PLUGIN_CONFIGURATION_TABS.md)
-- Check implementation details: [PLUGIN_CONFIG_TABS_SUMMARY.md](PLUGIN_CONFIG_TABS_SUMMARY.md)
+- Check the configuration architecture: [PLUGIN_CONFIG_ARCHITECTURE.md](PLUGIN_CONFIG_ARCHITECTURE.md)
-- Browse example plugins: `plugins/hello-world/`, `plugins/clock-simple/`
+- Browse example plugins in the
+  [ledmatrix-plugins](https://github.com/ChuckBuilds/ledmatrix-plugins)
+  repo, especially `plugins/hello-world/` and `plugins/clock-simple/`
 - Join the community for help and suggestions
 
 ## 🎉 That's It!

docs/PLUGIN_CUSTOM_ICONS_FEATURE.md

@@ -1,4 +1,12 @@
-# ✅ Plugin Custom Icons Feature - Complete
+# Plugin Custom Icons Feature
+
+> **Note:** this doc was originally written against the v2 web
+> interface. The v3 web interface now honors the same `icon` field
+> in `manifest.json` — the API passes it through at
+> `web_interface/blueprints/api_v3.py` and the three plugin-tab
+> render sites in `web_interface/templates/v3/base.html` read it
+> with a `fas fa-puzzle-piece` fallback. The guidance below still
+> applies; only the referenced template/helper names differ.
 
 ## What Was Implemented
 
@@ -304,7 +312,7 @@ Result: `[logo] Company Metrics` tab
 
 To test custom icons:
 
-1. **Open web interface** at `http://your-pi:5001`
+1. **Open web interface** at `http://your-pi-ip:5000`
 2. **Check installed plugins**:
    - Hello World should show 👋
    - Clock Simple should show 🕐

docs/PLUGIN_DEPENDENCY_GUIDE.md

@@ -37,7 +37,7 @@ sudo systemctl start ledmatrix-web
 
 ### ✅ Scenario 2: Web Interface Plugin Installation
 
-**What:** Installing/enabling plugins via web interface at `http://pi-ip:5001`
+**What:** Installing/enabling plugins via web interface at `http://pi-ip:5000`
 
 - **Web service runs as:** root (ledmatrix-web.service)
 - **Installs to:** System-wide

docs/PLUGIN_DEPENDENCY_TROUBLESHOOTING.md

@@ -77,10 +77,12 @@ sudo chmod -R 755 /root/.cache
 
 The web interface handles dependency installation correctly in the service context:
 
-1. Access the web interface (usually http://ledpi:8080)
+1. Access the web interface (`http://ledpi:5000` or `http://your-pi-ip:5000`)
-2. Navigate to Plugin Store or Plugin Management
+2. Open the **Plugin Manager** tab (use the **Plugin Store** section to
-3. Install plugins through the web UI
+   find the plugin, or **Install from GitHub**)
-4. The system will automatically handle dependencies
+3. Install the plugin through the web UI
+4. The system automatically handles dependency installation in the
+   service context (which has the right permissions)
 
 ## Prevention
 

docs/PLUGIN_DEVELOPMENT_GUIDE.md

@@ -12,6 +12,21 @@ When developing plugins in separate repositories, you need a way to:
 
 The solution uses **symbolic links** to connect plugin repositories to the `plugins/` directory, combined with a helper script to manage the linking process.
 
+> **Plugin directory note:** the dev workflow described here puts
+> symlinks in `plugins/`. The plugin loader's *production* default is
+> `plugin-repos/` (set by `plugin_system.plugins_directory` in
+> `config.json`). Importantly, the main discovery path
+> (`PluginManager.discover_plugins()`) only scans the configured
+> directory — it does **not** fall back to `plugins/`. Two narrower
+> paths do: the Plugin Store install/update logic in `store_manager.py`,
+> and `schema_manager.get_schema_path()` (which the web UI form
+> generator uses to find `config_schema.json`). That's why plugins
+> installed via the Plugin Store still work even with symlinks in
+> `plugins/`, but your own dev plugin won't appear in the rotation
+> until you either move it to `plugin-repos/` or change
+> `plugin_system.plugins_directory` to `plugins` in the General tab
+> of the web UI. The latter is the smoother dev setup.
+
 ## Quick Start
 
 ### 1. Link a Plugin from GitHub
@@ -466,7 +481,9 @@ When developing plugins, you'll need to use the APIs provided by the LEDMatrix s
 
 **Display Manager** (`self.display_manager`):
 - `clear()`, `update_display()` - Core display operations
-- `draw_text()`, `draw_image()` - Rendering methods
+- `draw_text()` - Text rendering. For images, paste directly onto
+  `display_manager.image` (a PIL Image) and call `update_display()`;
+  there is no `draw_image()` helper method.
 - `draw_weather_icon()`, `draw_sun()`, `draw_cloud()` - Weather icons
 - `get_text_width()`, `get_font_height()` - Text utilities
 - `set_scrolling_state()`, `defer_update()` - Scrolling state management

docs/PLUGIN_ERROR_HANDLING.md

@@ -0,0 +1,243 @@
+# Plugin Error Handling Guide
+
+This guide covers best practices for error handling in LEDMatrix plugins.
+
+## Custom Exception Hierarchy
+
+LEDMatrix provides typed exceptions for different error categories. Use these instead of generic `Exception`:
+
+```python
+from src.exceptions import PluginError, ConfigError, CacheError, DisplayError
+
+# Plugin-related errors
+raise PluginError("Failed to fetch data", plugin_id=self.plugin_id, context={"api": "ESPN"})
+
+# Configuration errors
+raise ConfigError("Invalid API key format", field="api_key")
+
+# Cache errors
+raise CacheError("Cache write failed", cache_key="game_data")
+
+# Display errors
+raise DisplayError("Failed to render", display_mode="live")
+```
+
+### Exception Context
+
+All LEDMatrix exceptions support a `context` dict for additional debugging info:
+
+```python
+raise PluginError(
+    "API request failed",
+    plugin_id=self.plugin_id,
+    context={
+        "url": api_url,
+        "status_code": response.status_code,
+        "retry_count": 3
+    }
+)
+```
+
+## Logging Best Practices
+
+### Use the Plugin Logger
+
+Every plugin has access to `self.logger`:
+
+```python
+class MyPlugin(BasePlugin):
+    def update(self):
+        self.logger.info("Starting data fetch")
+        self.logger.debug("API URL: %s", api_url)
+        self.logger.warning("Rate limit approaching")
+        self.logger.error("API request failed", exc_info=True)
+```
+
+### Log Levels
+
+- **DEBUG**: Detailed info for troubleshooting (API URLs, parsed data)
+- **INFO**: Normal operation milestones (plugin loaded, data fetched)
+- **WARNING**: Recoverable issues (rate limits, cache miss, fallback used)
+- **ERROR**: Failures that need attention (API down, display error)
+
+### Include exc_info for Exceptions
+
+```python
+try:
+    response = requests.get(url)
+except requests.RequestException as e:
+    self.logger.error("API request failed: %s", e, exc_info=True)
+```
+
+## Error Handling Patterns
+
+### Never Use Bare except
+
+```python
+# BAD - swallows all errors including KeyboardInterrupt
+try:
+    self.fetch_data()
+except:
+    pass
+
+# GOOD - catch specific exceptions
+try:
+    self.fetch_data()
+except requests.RequestException as e:
+    self.logger.warning("Network error, using cached data: %s", e)
+    self.data = self.get_cached_data()
+```
+
+### Graceful Degradation
+
+```python
+def update(self):
+    try:
+        self.data = self.fetch_live_data()
+    except requests.RequestException as e:
+        self.logger.warning("Live data unavailable: %s", e)
+        # Fall back to cache
+        cached = self.cache_manager.get(self.cache_key)
+        if cached:
+            self.logger.info("Using cached data")
+            self.data = cached
+        else:
+            self.logger.error("No cached data available")
+            self.data = None
+```
+
+### Validate Configuration Early
+
+```python
+def validate_config(self) -> bool:
+    """Validate configuration at load time."""
+    api_key = self.config.get("api_key")
+    if not api_key:
+        self.logger.error("api_key is required but not configured")
+        return False
+
+    if not isinstance(api_key, str) or len(api_key) < 10:
+        self.logger.error("api_key appears to be invalid")
+        return False
+
+    return True
+```
+
+### Handle Display Errors
+
+```python
+def display(self, force_clear: bool = False) -> bool:
+    if not self.data:
+        if force_clear:
+            self.display_manager.clear()
+            self.display_manager.update_display()
+        return False
+
+    try:
+        self._render_content()
+        return True
+    except Exception as e:
+        self.logger.error("Display error: %s", e, exc_info=True)
+        # Clear display on error to prevent stale content
+        self.display_manager.clear()
+        self.display_manager.update_display()
+        return False
+```
+
+## Error Aggregation
+
+LEDMatrix automatically tracks plugin errors. Access error data via the API:
+
+```bash
+# Get error summary
+curl http://localhost:5000/api/v3/errors/summary
+
+# Get plugin-specific health
+curl http://localhost:5000/api/v3/errors/plugin/my-plugin
+
+# Clear old errors
+curl -X POST http://localhost:5000/api/v3/errors/clear
+```
+
+### Error Patterns
+
+When the same error occurs repeatedly (5+ times in 60 minutes), it's detected as a pattern and logged as a warning. This helps identify systemic issues.
+
+## Common Error Scenarios
+
+### API Rate Limiting
+
+```python
+def fetch_data(self):
+    try:
+        response = requests.get(self.api_url)
+        if response.status_code == 429:
+            retry_after = int(response.headers.get("Retry-After", 60))
+            self.logger.warning("Rate limited, retry after %ds", retry_after)
+            self._rate_limited_until = time.time() + retry_after
+            return None
+        response.raise_for_status()
+        return response.json()
+    except requests.RequestException as e:
+        self.logger.error("API error: %s", e)
+        return None
+```
+
+### Timeout Handling
+
+```python
+def fetch_data(self):
+    try:
+        response = requests.get(self.api_url, timeout=10)
+        return response.json()
+    except requests.Timeout:
+        self.logger.warning("Request timed out, will retry next update")
+        return None
+    except requests.RequestException as e:
+        self.logger.error("Request failed: %s", e)
+        return None
+```
+
+### Missing Data Gracefully
+
+```python
+def get_team_logo(self, team_id):
+    logo_path = self.logos_dir / f"{team_id}.png"
+    if not logo_path.exists():
+        self.logger.debug("Logo not found for team %s, using default", team_id)
+        return self.default_logo
+    return Image.open(logo_path)
+```
+
+## Testing Error Handling
+
+```python
+def test_handles_api_error(mock_requests):
+    """Test plugin handles API errors gracefully."""
+    mock_requests.get.side_effect = requests.RequestException("Network error")
+
+    plugin = MyPlugin(...)
+    plugin.update()
+
+    # Should not raise, should log warning, should have no data
+    assert plugin.data is None
+
+def test_handles_invalid_json(mock_requests):
+    """Test plugin handles invalid JSON response."""
+    mock_requests.get.return_value.json.side_effect = ValueError("Invalid JSON")
+
+    plugin = MyPlugin(...)
+    plugin.update()
+
+    assert plugin.data is None
+```
+
+## Checklist
+
+- [ ] No bare `except:` clauses
+- [ ] All exceptions logged with appropriate level
+- [ ] `exc_info=True` for error-level logs
+- [ ] Graceful degradation with cache fallbacks
+- [ ] Configuration validated in `validate_config()`
+- [ ] Display clears on error to prevent stale content
+- [ ] Timeouts configured for all network requests

docs/PLUGIN_IMPLEMENTATION_SUMMARY.md

@@ -1,5 +1,11 @@
 # LEDMatrix Plugin System - Implementation Summary
 
+> **Status note:** this is a high-level summary written during the
+> initial plugin system rollout. Most of it is accurate, but a few
+> sections describe features that are aspirational or only partially
+> implemented (per-plugin virtual envs, resource limits, registry
+> manager). Drift from current reality is called out inline.
+
 This document provides a comprehensive overview of the plugin architecture implementation, consolidating details from multiple plugin-related implementation summaries.
 
 ## Executive Summary
@@ -14,16 +20,25 @@ The LEDMatrix plugin system transforms the project into a modular, extensible pl
 LEDMatrix/
 ├── src/plugin_system/
 │   ├── base_plugin.py          # Plugin interface contract
+│   ├── plugin_loader.py        # Discovery + dynamic import
 │   ├── plugin_manager.py       # Lifecycle management
-│   ├── store_manager.py        # GitHub integration
+│   ├── store_manager.py        # GitHub install / store integration
-│   └── registry_manager.py     # Plugin discovery
+│   ├── schema_manager.py       # Config schema validation
-├── plugins/                    # User-installed plugins
+│   ├── health_monitor.py       # Plugin health metrics
+│   ├── operation_queue.py      # Async install/update operations
+│   └── state_manager.py        # Persistent plugin state
+├── plugin-repos/               # Default plugin install location
 │   ├── football-scoreboard/
 │   ├── ledmatrix-music/
 │   └── ledmatrix-stocks/
 └── config/config.json          # Plugin configurations
 ```
 
+> Earlier drafts of this doc referenced `registry_manager.py`. It was
+> never created — discovery happens in `plugin_loader.py`. The earlier
+> default plugin location of `plugins/` has been replaced with
+> `plugin-repos/` (see `config/config.template.json:130`).
+
 ### Key Design Decisions
 
 ✅ **Gradual Migration**: Plugin system added alongside existing managers
@@ -77,14 +92,26 @@ LEDMatrix/
 - **Fallback System**: Default icons when custom ones unavailable
 
 #### Dependency Management
-- **Requirements.txt**: Per-plugin dependencies
+- **Requirements.txt**: Per-plugin dependencies, installed system-wide
-- **Virtual Environments**: Isolated dependency management
+  via pip on first plugin load
-- **Version Pinning**: Explicit version constraints
+- **Version Pinning**: Standard pip version constraints in
+  `requirements.txt`
 
-#### Permission System
+> Earlier plans called for per-plugin virtual environments. That isn't
-- **File Access Control**: Configurable file system permissions
+> implemented — plugin Python deps install into the system Python
-- **Network Access**: Controlled API access
+> environment (or whatever environment the LEDMatrix service is using).
-- **Resource Limits**: CPU and memory constraints
+> Conflicting versions across plugins are not auto-resolved.
+
+#### Health monitoring
+- **Resource Monitor** (`src/plugin_system/resource_monitor.py`): tracks
+  CPU and memory metrics per plugin and warns about slow plugins
+- **Health Monitor** (`src/plugin_system/health_monitor.py`): tracks
+  plugin failures and last-success timestamps
+
+> Earlier plans called for hard CPU/memory limits and a sandboxed
+> permission system. Neither is implemented. Plugins run in the same
+> process as the display loop with full file-system and network access
+> — review third-party plugin code before installing.
 
 ## Plugin Development
 

docs/PLUGIN_QUICK_REFERENCE.md

@@ -2,14 +2,20 @@
 
 ## Overview
 
-Transform LEDMatrix into a modular, plugin-based system where users can create, share, and install custom displays via a GitHub-based store (similar to HACS for Home Assistant).
+LEDMatrix is a modular, plugin-based system where users create, share,
+and install custom displays via a GitHub-based store (similar in spirit
+to HACS for Home Assistant). This page is a quick reference; for the
+full design see [PLUGIN_ARCHITECTURE_SPEC.md](PLUGIN_ARCHITECTURE_SPEC.md)
+and [PLUGIN_DEVELOPMENT_GUIDE.md](PLUGIN_DEVELOPMENT_GUIDE.md).
 
 ## Key Decisions
 
-✅ **Gradual Migration**: Existing managers stay, plugins added alongside  
+✅ **Plugin-First**: All display features (calendar excepted) are now plugins
-✅ **Migration Required**: Breaking changes in v3.0, tools provided  
+✅ **GitHub Store**: Discovery from `ledmatrix-plugins` registry plus
-✅ **GitHub Store**: Simple discovery, packages from repos  
+   any GitHub URL
-✅ **Plugin Location**: `./plugins/` directory  
+✅ **Plugin Location**: configured by `plugin_system.plugins_directory`
+   in `config.json` (default `plugin-repos/`; the loader also searches
+   `plugins/` as a fallback)
 
 ## File Structure
 
@@ -19,15 +25,16 @@ LEDMatrix/
 │   └── plugin_system/
 │       ├── base_plugin.py          # Plugin interface
 │       ├── plugin_manager.py       # Load/unload plugins
+│       ├── plugin_loader.py        # Discovery + dynamic import
 │       └── store_manager.py        # Install from GitHub
-├── plugins/
+├── plugin-repos/                   # Default plugin install location
 │   ├── clock-simple/
 │   │   ├── manifest.json           # Metadata
 │   │   ├── manager.py              # Main plugin class
 │   │   ├── requirements.txt        # Dependencies
 │   │   ├── config_schema.json      # Validation
 │   │   └── README.md
-│   └── nhl-scores/
+│   └── hockey-scoreboard/
 │       └── ... (same structure)
 └── config/config.json               # Plugin configs
 ```
@@ -109,100 +116,45 @@ git push origin v1.0.0
 
 ### Web UI
 
-1. **Browse Store**: Plugin Store tab → Search/filter
+1. **Browse Store**: Plugin Manager tab → Plugin Store section → Search/filter
-2. **Install**: Click "Install" button
+2. **Install**: Click **Install** in the plugin's row
-3. **Configure**: Plugin Manager → Click ⚙️ Configure
+3. **Configure**: open the plugin's tab in the second nav row
-4. **Enable/Disable**: Toggle switch
+4. **Enable/Disable**: toggle switch in the **Installed Plugins** list
-5. **Reorder**: Drag and drop in rotation list
+5. **Reorder**: order is set by the position in `display_modes` /
+   plugin order; rearranging via drag-and-drop is not yet supported
 
-### API
+### REST API
 
-```python
+The API is mounted at `/api/v3` (`web_interface/app.py:144`).
-# Install plugin
-POST /api/plugins/install
-{"plugin_id": "my-plugin"}
-
-# Install from custom URL
-POST /api/plugins/install-from-url
-{"repo_url": "https://github.com/User/plugin"}
-
-# List installed
-GET /api/plugins/installed
-
-# Toggle
-POST /api/plugins/toggle
-{"plugin_id": "my-plugin", "enabled": true}
-```
-
-### Command Line
-
-```python
-from src.plugin_system.store_manager import PluginStoreManager
-
-store = PluginStoreManager()
-
-# Install
-store.install_plugin('nhl-scores')
-
-# Install from URL
-store.install_from_url('https://github.com/User/plugin')
-
-# Update
-store.update_plugin('nhl-scores')
-
-# Uninstall
-store.uninstall_plugin('nhl-scores')
-```
-
-## Migration Path
-
-### Phase 1: v2.0.0 (Plugin Infrastructure)
-- Plugin system alongside existing managers
-- 100% backward compatible
-- Web UI shows plugin store
-
-### Phase 2: v2.1.0 (Example Plugins)
-- Reference plugins created
-- Migration examples
-- Developer docs
-
-### Phase 3: v2.2.0 (Migration Tools)
-- Auto-migration script
-- Config converter
-- Testing tools
-
-### Phase 4: v2.5.0 (Deprecation)
-- Warnings on legacy managers
-- Migration guide
-- 95% backward compatible
-
-### Phase 5: v3.0.0 (Plugin-Only)
-- Legacy managers removed from core
-- Packaged as official plugins
-- **Breaking change - migration required**
-
-## Quick Migration
 
 ```bash
-# 1. Backup
+# Install plugin from the registry
-cp config/config.json config/config.json.backup
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/install \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "hockey-scoreboard"}'
 
-# 2. Run migration
+# Install from custom URL
-python3 scripts/migrate_to_plugins.py
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/install-from-url \
+  -H "Content-Type: application/json" \
+  -d '{"repo_url": "https://github.com/User/plugin"}'
 
-# 3. Review
+# List installed
-cat config/config.json.migrated
+curl http://your-pi-ip:5000/api/v3/plugins/installed
 
-# 4. Apply
+# Toggle
-mv config/config.json.migrated config/config.json
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/toggle \
-
+  -H "Content-Type: application/json" \
-# 5. Restart
+  -d '{"plugin_id": "hockey-scoreboard", "enabled": true}'
-sudo systemctl restart ledmatrix
 ```
 
+See [REST_API_REFERENCE.md](REST_API_REFERENCE.md) for the full list.
+
 ## Plugin Registry Structure
 
-**ChuckBuilds/ledmatrix-plugin-registry/plugins.json**:
+The official registry lives at
+[`ChuckBuilds/ledmatrix-plugins`](https://github.com/ChuckBuilds/ledmatrix-plugins).
+The Plugin Store reads `plugins.json` at the root of that repo, which
+follows this shape:
 ```json
 {
   "plugins": [
@@ -245,42 +197,30 @@ sudo systemctl restart ledmatrix
 - ✅ Community handles custom displays
 - ✅ Easier to review changes
 
-## What's Missing?
+## Known Limitations
 
-This specification covers the technical architecture. Additional considerations:
+The plugin system is shipped and stable, but some things are still
+intentionally simple:
 
-1. **Sandboxing**: Current design has no isolation (future enhancement)
+1. **Sandboxing**: plugins run in the same process as the display loop;
-2. **Resource Limits**: No CPU/memory limits per plugin (future)
+   there is no isolation. Review code before installing third-party
-3. **Plugin Ratings**: Registry needs rating/review system
+   plugins.
-4. **Auto-Updates**: Manual update only (could add auto-update)
+2. **Resource limits**: there's a resource monitor that warns about
-5. **Dependency Conflicts**: No automatic resolution
+   slow plugins, but no hard CPU/memory caps.
-6. **Version Pinning**: Limited version constraint checking
+3. **Plugin ratings**: not yet — the Plugin Store shows version,
-7. **Plugin Testing**: No automated testing framework
+   author, and category but no community rating system.
-8. **Marketplace**: No paid plugins (all free/open source)
+4. **Auto-updates**: manual via the Plugin Manager tab; no automatic
-
+   background updates.
-## Next Steps
+5. **Dependency conflicts**: each plugin's `requirements.txt` is
-
+   installed via pip; conflicting versions across plugins are not
-1. ✅ Review this specification
+   resolved automatically.
-2. Start Phase 1 implementation
+6. **Plugin testing framework**: see
-3. Create first 3-4 example plugins
+   [HOW_TO_RUN_TESTS.md](HOW_TO_RUN_TESTS.md) and
-4. Set up plugin registry repo
+   [DEV_PREVIEW.md](DEV_PREVIEW.md) — there are tools, but no
-5. Build web UI components
+   mandatory test gate.
-6. Test on Pi hardware
-7. Release v2.0.0 alpha
-
-## Questions to Resolve
-
-Before implementing, consider:
-
-1. Should we support plugin dependencies (plugin A requires plugin B)?
-2. How to handle breaking changes in core display_manager API?
-3. Should plugins be able to add new web UI pages?
-4. What about plugins that need hardware beyond LED matrix?
-5. How to prevent malicious plugins?
-6. Should there be plugin quotas (max API calls, etc.)?
-7. How to handle plugin conflicts (two clocks competing)?
 
 ---
 
-**See PLUGIN_ARCHITECTURE_SPEC.md for full details**
+**See [PLUGIN_ARCHITECTURE_SPEC.md](PLUGIN_ARCHITECTURE_SPEC.md) for the
+full architectural specification.**
 

docs/PLUGIN_REGISTRY_SETUP_GUIDE.md

@@ -95,14 +95,14 @@ Official plugin registry for [LEDMatrix](https://github.com/ChuckBuilds/LEDMatri
 
 All plugins can be installed through the LEDMatrix web interface:
 
-1. Open web interface (http://your-pi-ip:5050)
+1. Open web interface (http://your-pi-ip:5000)
-2. Go to Plugin Store tab
+2. Open the **Plugin Manager** tab
-3. Browse or search for plugins
+3. Browse or search the **Plugin Store** section
-4. Click Install
+4. Click **Install**
 
 Or via API:
 ```bash
-curl -X POST http://your-pi-ip:5050/api/plugins/install \
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/install \
   -d '{"plugin_id": "clock-simple"}'
 ```
 
@@ -152,7 +152,7 @@ Before submitting, ensure your plugin:
 1. **Test Your Plugin**
    ```bash
    # Install via URL on your Pi
-   curl -X POST http://your-pi:5050/api/plugins/install-from-url \
+   curl -X POST http://your-pi:5000/api/v3/plugins/install-from-url \
      -d '{"repo_url": "https://github.com/you/ledmatrix-your-plugin"}'
    ```
 
@@ -311,7 +311,7 @@ git push
 # 1. Receive PR on ledmatrix-plugins repo
 # 2. Review using VERIFICATION.md checklist
 # 3. Test installation:
-curl -X POST http://pi:5050/api/plugins/install-from-url \
+curl -X POST http://pi:5000/api/v3/plugins/install-from-url \
   -d '{"repo_url": "https://github.com/contributor/plugin"}'
 
 # 4. If approved, merge PR

docs/PLUGIN_STORE_GUIDE.md

@@ -0,0 +1,493 @@
+# Plugin Store Guide
+
+## Overview
+
+The LEDMatrix Plugin Store allows you to discover, install, and manage display plugins for your LED matrix. Install curated plugins from the official registry or add custom plugins directly from any GitHub repository.
+
+---
+
+## Quick Reference
+
+### Install from Store
+```bash
+# Web UI: Plugin Store → Search → Click Install
+# API:
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/install \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "clock-simple"}'
+```
+
+### Install from GitHub URL
+```bash
+# Web UI: Plugin Store → "Install from URL" → Paste URL
+# API:
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/install-from-url \
+  -H "Content-Type: application/json" \
+  -d '{"repo_url": "https://github.com/user/ledmatrix-plugin"}'
+```
+
+### Manage Plugins
+```bash
+# List installed
+curl "http://your-pi-ip:5000/api/v3/plugins/installed"
+
+# Enable/disable
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/toggle \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "clock-simple", "enabled": true}'
+
+# Update
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/update \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "clock-simple"}'
+
+# Uninstall
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/uninstall \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "clock-simple"}'
+```
+
+---
+
+## Installation Methods
+
+### Method 1: From Official Plugin Store (Recommended)
+
+The official plugin store contains curated, verified plugins that have been reviewed by maintainers.
+
+**Via Web Interface:**
+1. Open the web interface at http://your-pi-ip:5000
+2. Navigate to the "Plugin Store" tab
+3. Browse or search for plugins
+4. Click "Install" on the desired plugin
+5. Wait for installation to complete
+6. Restart the display to activate the plugin
+
+**Via REST API:**
+```bash
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/install \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "clock-simple"}'
+```
+
+**Via Python:**
+```python
+from src.plugin_system.store_manager import PluginStoreManager
+
+store = PluginStoreManager()
+success = store.install_plugin('clock-simple')
+if success:
+    print("Plugin installed!")
+```
+
+### Method 2: From Custom GitHub URL
+
+Install any plugin directly from a GitHub repository, even if it's not in the official store. This method is useful for:
+- Testing your own plugins during development
+- Installing community plugins before they're in the official store
+- Using private plugins
+- Sharing plugins with specific users
+
+**Via Web Interface:**
+1. Open the web interface
+2. Navigate to the "Plugin Store" tab
+3. Find the "Install from URL" section
+4. Paste the GitHub repository URL (e.g., `https://github.com/user/ledmatrix-my-plugin`)
+5. Click "Install from URL"
+6. Review the warning about unverified plugins
+7. Confirm installation
+8. Wait for installation to complete
+9. Restart the display
+
+**Via REST API:**
+```bash
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/install-from-url \
+  -H "Content-Type: application/json" \
+  -d '{"repo_url": "https://github.com/user/ledmatrix-my-plugin"}'
+```
+
+**Via Python:**
+```python
+from src.plugin_system.store_manager import PluginStoreManager
+
+store = PluginStoreManager()
+result = store.install_from_url('https://github.com/user/ledmatrix-my-plugin')
+
+if result['success']:
+    print(f"Installed: {result['plugin_id']}")
+else:
+    print(f"Error: {result['error']}")
+```
+
+---
+
+## Searching for Plugins
+
+**Via Web Interface:**
+- Use the search bar to search by name, description, or author
+- Filter by category (sports, weather, time, finance, etc.)
+- Click on tags to filter by specific tags
+
+**Via REST API:**
+```bash
+# Search by query
+curl "http://your-pi-ip:5000/api/v3/plugins/store/search?q=hockey"
+
+# Filter by category
+curl "http://your-pi-ip:5000/api/v3/plugins/store/search?category=sports"
+
+# Filter by tags
+curl "http://your-pi-ip:5000/api/v3/plugins/store/search?tags=nhl&tags=hockey"
+```
+
+**Via Python:**
+```python
+from src.plugin_system.store_manager import PluginStoreManager
+
+store = PluginStoreManager()
+
+# Search by query
+results = store.search_plugins(query="hockey")
+
+# Filter by category
+results = store.search_plugins(category="sports")
+
+# Filter by tags
+results = store.search_plugins(tags=["nhl", "hockey"])
+```
+
+---
+
+## Managing Installed Plugins
+
+### List Installed Plugins
+
+**Via Web Interface:**
+- Navigate to the "Plugin Manager" tab
+- View all installed plugins with their status
+
+**Via REST API:**
+```bash
+curl "http://your-pi-ip:5000/api/v3/plugins/installed"
+```
+
+**Via Python:**
+```python
+from src.plugin_system.store_manager import PluginStoreManager
+
+store = PluginStoreManager()
+installed = store.list_installed_plugins()
+
+for plugin_id in installed:
+    info = store.get_installed_plugin_info(plugin_id)
+    print(f"{info['name']} (Last updated: {info.get('last_updated', 'unknown')})")
+```
+
+### Enable/Disable Plugins
+
+**Via Web Interface:**
+1. Navigate to the "Plugin Manager" tab
+2. Use the toggle switch next to each plugin
+3. Restart the display to apply changes
+
+**Via REST API:**
+```bash
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/toggle \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "clock-simple", "enabled": true}'
+```
+
+### Update Plugins
+
+**Via Web Interface:**
+1. Navigate to the "Plugin Manager" tab
+2. Click the "Update" button next to the plugin
+3. Wait for the update to complete
+4. Restart the display
+
+**Via REST API:**
+```bash
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/update \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "clock-simple"}'
+```
+
+**Via Python:**
+```python
+from src.plugin_system.store_manager import PluginStoreManager
+
+store = PluginStoreManager()
+success = store.update_plugin('clock-simple')
+```
+
+### Uninstall Plugins
+
+**Via Web Interface:**
+1. Navigate to the "Plugin Manager" tab
+2. Click the "Uninstall" button next to the plugin
+3. Confirm removal
+4. Restart the display
+
+**Via REST API:**
+```bash
+curl -X POST http://your-pi-ip:5000/api/v3/plugins/uninstall \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "clock-simple"}'
+```
+
+**Via Python:**
+```python
+from src.plugin_system.store_manager import PluginStoreManager
+
+store = PluginStoreManager()
+success = store.uninstall_plugin('clock-simple')
+```
+
+---
+
+## Configuring Plugins
+
+Each plugin can have its own configuration in `config/config.json`:
+
+```json
+{
+  "clock-simple": {
+    "enabled": true,
+    "display_duration": 15,
+    "color": [255, 255, 255],
+    "time_format": "12h"
+  },
+  "nhl-scores": {
+    "enabled": true,
+    "favorite_teams": ["TBL", "FLA"],
+    "show_favorite_teams_only": true
+  }
+}
+```
+
+**Via Web Interface:**
+1. Navigate to the "Plugin Manager" tab
+2. Click the Configure (⚙️) button next to the plugin
+3. Edit the configuration in the form
+4. Save changes
+5. Restart the display to apply changes
+
+---
+
+## Safety and Security
+
+### Verified vs Unverified Plugins
+
+- **Verified Plugins**: Reviewed by maintainers, follow best practices, no known security issues
+- **Unverified Plugins**: User-contributed, not reviewed, install at your own risk
+
+When installing from a custom GitHub URL, you'll see a warning about installing an unverified plugin. The plugin will have access to your display manager, cache manager, configuration files, and network access.
+
+### Best Practices
+
+1. Only install plugins from trusted sources
+2. Review plugin code before installing (click "View on GitHub")
+3. Keep plugins updated for security patches
+4. Report suspicious plugins to maintainers
+
+---
+
+## Troubleshooting
+
+### Plugin Won't Install
+
+**Problem:** Installation fails with "Failed to clone or download repository"
+
+**Solutions:**
+- Check that git is installed: `which git`
+- Verify the GitHub URL is correct
+- Check your internet connection
+- The system will automatically try ZIP download as fallback
+
+### Plugin Won't Load
+
+**Problem:** Plugin installed but doesn't appear in rotation
+
+**Solutions:**
+1. Check that the plugin is enabled in config: `"enabled": true`
+2. Verify manifest.json exists and is valid
+3. Check logs for errors: `sudo journalctl -u ledmatrix -f`
+4. Restart the display service: `sudo systemctl restart ledmatrix`
+
+### Dependencies Failed
+
+**Problem:** "Error installing dependencies" message
+
+**Solutions:**
+- Check that pip3 is installed
+- Manually install: `pip3 install --break-system-packages -r plugins/plugin-id/requirements.txt`
+- Check for conflicting package versions
+
+### Plugin Shows Errors
+
+**Problem:** Plugin loads but shows error message on display
+
+**Solutions:**
+1. Check that the plugin configuration is correct
+2. Verify API keys are set (if the plugin requires them)
+3. Check plugin logs: `sudo journalctl -u ledmatrix -f | grep plugin-id`
+4. Report the issue to the plugin developer on GitHub
+
+---
+
+## API Reference
+
+All API endpoints return JSON with this structure:
+
+```json
+{
+  "status": "success" | "error",
+  "message": "Human-readable message",
+  "data": { ... }
+}
+```
+
+### Endpoints
+
+| Method | Endpoint | Description |
+|--------|----------|-------------|
+| GET | `/api/v3/plugins/store/list` | List all plugins in store |
+| GET | `/api/v3/plugins/store/search` | Search for plugins |
+| GET | `/api/v3/plugins/installed` | List installed plugins |
+| POST | `/api/v3/plugins/install` | Install from registry |
+| POST | `/api/v3/plugins/install-from-url` | Install from GitHub URL |
+| POST | `/api/v3/plugins/uninstall` | Uninstall plugin |
+| POST | `/api/v3/plugins/update` | Update plugin |
+| POST | `/api/v3/plugins/toggle` | Enable/disable plugin |
+| POST | `/api/v3/plugins/config` | Update plugin config |
+
+---
+
+## Examples
+
+### Example 1: Install Clock Plugin
+
+```bash
+# Install
+curl -X POST http://192.168.1.100:5000/api/v3/plugins/install \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "clock-simple"}'
+
+# Configure in config/config.json
+{
+  "clock-simple": {
+    "enabled": true,
+    "display_duration": 20,
+    "time_format": "24h"
+  }
+}
+
+# Restart display
+sudo systemctl restart ledmatrix
+```
+
+### Example 2: Install Custom Plugin from GitHub
+
+```bash
+# Install your own plugin during development
+curl -X POST http://192.168.1.100:5000/api/v3/plugins/install-from-url \
+  -H "Content-Type: application/json" \
+  -d '{"repo_url": "https://github.com/myusername/ledmatrix-my-custom-plugin"}'
+
+# Enable it
+curl -X POST http://192.168.1.100:5000/api/v3/plugins/toggle \
+  -H "Content-Type: application/json" \
+  -d '{"plugin_id": "my-custom-plugin", "enabled": true}'
+
+# Restart
+sudo systemctl restart ledmatrix
+```
+
+### Example 3: Share Plugin with Others
+
+As a plugin developer, you can share your plugin with others even before it's in the official store:
+
+1. Push your plugin to GitHub: `https://github.com/yourusername/ledmatrix-awesome-plugin`
+2. Share the URL with users
+3. Users install via:
+   - Open the LEDMatrix web interface
+   - Click "Plugin Store" tab
+   - Scroll to "Install from URL"
+   - Paste the URL
+   - Click "Install from URL"
+
+---
+
+## Command-Line Usage
+
+For advanced users, manage plugins via command line:
+
+```bash
+# Install from registry
+python3 -c "
+from src.plugin_system.store_manager import PluginStoreManager
+store = PluginStoreManager()
+store.install_plugin('clock-simple')
+"
+
+# Install from URL
+python3 -c "
+from src.plugin_system.store_manager import PluginStoreManager
+store = PluginStoreManager()
+result = store.install_from_url('https://github.com/user/plugin')
+print(result)
+"
+
+# List installed
+python3 -c "
+from src.plugin_system.store_manager import PluginStoreManager
+store = PluginStoreManager()
+for plugin_id in store.list_installed_plugins():
+    info = store.get_installed_plugin_info(plugin_id)
+    print(f'{plugin_id}: {info[\"name\"]} (Last updated: {info.get(\"last_updated\", \"unknown\")})')
+"
+
+# Uninstall
+python3 -c "
+from src.plugin_system.store_manager import PluginStoreManager
+store = PluginStoreManager()
+store.uninstall_plugin('clock-simple')
+"
+```
+
+---
+
+## FAQ
+
+**Q: Do I need to restart the display after installing a plugin?**
+A: Yes, plugins are loaded when the display controller starts.
+
+**Q: Can I install plugins while the display is running?**
+A: Yes, you can install anytime, but you must restart the display to load them.
+
+**Q: What happens if I install a plugin with the same ID as an existing one?**
+A: The existing copy will be replaced with the latest code from the repository.
+
+**Q: Can I install multiple versions of the same plugin?**
+A: No, each plugin ID maps to a single checkout of the repository's default branch.
+
+**Q: How do I update all plugins at once?**
+A: Currently, you need to update each plugin individually. Bulk update is planned for a future release.
+
+**Q: Can plugins access my API keys from config_secrets.json?**
+A: Yes, if a plugin needs API keys, it can access them like core managers do.
+
+**Q: How much disk space do plugins use?**
+A: Most plugins are small (1-5MB). Check individual plugin documentation for specific requirements.
+
+**Q: Can I create my own plugin?**
+A: Yes! See [PLUGIN_DEVELOPMENT.md](PLUGIN_DEVELOPMENT.md) for instructions.
+
+---
+
+## Related Documentation
+
+- [PLUGIN_DEVELOPMENT.md](PLUGIN_DEVELOPMENT.md) - Create your own plugins
+- [PLUGIN_API_REFERENCE.md](PLUGIN_API_REFERENCE.md) - Plugin API documentation
+- [PLUGIN_ARCHITECTURE.md](PLUGIN_ARCHITECTURE.md) - Plugin system architecture
+- [REST_API_REFERENCE.md](REST_API_REFERENCE.md) - Complete REST API reference

docs/README.md

@@ -1,177 +1,84 @@
 # LEDMatrix Documentation
 
-Welcome to the LEDMatrix documentation! This directory contains comprehensive guides, specifications, and reference materials for the LEDMatrix project.
+This directory contains guides, references, and architectural notes for the
+LEDMatrix project. If you are setting up a Pi for the first time, start with
+the [project root README](../README.md) — it covers hardware, OS imaging, and
+the one-shot installer. The pages here go deeper.
 
-## 📚 Documentation Overview
+## I'm a new user
 
-This documentation has been consolidated and organized to reduce redundancy while maintaining comprehensive coverage. Recent improvements include complete API references, enhanced plugin development guides, and better organization for both end users and developers.
+1. [GETTING_STARTED.md](GETTING_STARTED.md) — first-time setup walkthrough
+2. [WEB_INTERFACE_GUIDE.md](WEB_INTERFACE_GUIDE.md) — using the web UI
+3. [PLUGIN_STORE_GUIDE.md](PLUGIN_STORE_GUIDE.md) — installing and managing plugins
+4. [WIFI_NETWORK_SETUP.md](WIFI_NETWORK_SETUP.md) — WiFi and AP-mode setup
+5. [TROUBLESHOOTING.md](TROUBLESHOOTING.md) — common issues and fixes
+6. [SSH_UNAVAILABLE_AFTER_INSTALL.md](SSH_UNAVAILABLE_AFTER_INSTALL.md) — recovering SSH after install
+7. [CONFIG_DEBUGGING.md](CONFIG_DEBUGGING.md) — diagnosing config problems
 
-## 📖 Quick Start
+## I want to write a plugin
 
-### For New Users
+Start here:
-1. **Installation**: Follow the main [README.md](../README.md) in the project root
-2. **First Setup**: Run `first_time_install.sh` for initial configuration
-3. **Basic Usage**: See [TROUBLESHOOTING_QUICK_START.md](TROUBLESHOOTING_QUICK_START.md) for common issues
 
-### For Developers
+1. [PLUGIN_DEVELOPMENT_GUIDE.md](PLUGIN_DEVELOPMENT_GUIDE.md) — end-to-end workflow
-1. **Plugin System**: Read [PLUGIN_QUICK_REFERENCE.md](PLUGIN_QUICK_REFERENCE.md) for an overview
+2. [PLUGIN_QUICK_REFERENCE.md](PLUGIN_QUICK_REFERENCE.md) — cheat sheet
-2. **Plugin Development**: See [PLUGIN_DEVELOPMENT_GUIDE.md](PLUGIN_DEVELOPMENT_GUIDE.md) for development workflow
+3. [PLUGIN_API_REFERENCE.md](PLUGIN_API_REFERENCE.md) — display, cache, and plugin-manager APIs
-3. **API Reference**: Check [PLUGIN_API_REFERENCE.md](PLUGIN_API_REFERENCE.md) for available methods
+4. [PLUGIN_ERROR_HANDLING.md](PLUGIN_ERROR_HANDLING.md) — error-handling patterns
-4. **Configuration**: Check [PLUGIN_CONFIGURATION_GUIDE.md](PLUGIN_CONFIGURATION_GUIDE.md)
+5. [DEV_PREVIEW.md](DEV_PREVIEW.md) — preview plugins on your dev machine without a Pi
+6. [EMULATOR_SETUP_GUIDE.md](EMULATOR_SETUP_GUIDE.md) — running the matrix emulator
 
-### For API Integration
+Going deeper:
-1. **REST API**: See [API_REFERENCE.md](API_REFERENCE.md) for all web interface endpoints
-2. **Plugin API**: See [PLUGIN_API_REFERENCE.md](PLUGIN_API_REFERENCE.md) for plugin developer APIs
-3. **Quick Reference**: See [DEVELOPER_QUICK_REFERENCE.md](DEVELOPER_QUICK_REFERENCE.md) for common tasks
 
-## 📋 Documentation Categories
+- [ADVANCED_PLUGIN_DEVELOPMENT.md](ADVANCED_PLUGIN_DEVELOPMENT.md) — advanced patterns
+- [PLUGIN_ARCHITECTURE_SPEC.md](PLUGIN_ARCHITECTURE_SPEC.md) — full plugin-system spec
+- [PLUGIN_DEPENDENCY_GUIDE.md](PLUGIN_DEPENDENCY_GUIDE.md) /
+  [PLUGIN_DEPENDENCY_TROUBLESHOOTING.md](PLUGIN_DEPENDENCY_TROUBLESHOOTING.md)
+- [PLUGIN_WEB_UI_ACTIONS.md](PLUGIN_WEB_UI_ACTIONS.md) (+ [example JSON](PLUGIN_WEB_UI_ACTIONS_EXAMPLE.json))
+- [PLUGIN_CUSTOM_ICONS.md](PLUGIN_CUSTOM_ICONS.md) /
+  [PLUGIN_CUSTOM_ICONS_FEATURE.md](PLUGIN_CUSTOM_ICONS_FEATURE.md)
+- [PLUGIN_REGISTRY_SETUP_GUIDE.md](PLUGIN_REGISTRY_SETUP_GUIDE.md) (+ [registry template](plugin_registry_template.json))
+- [STARLARK_APPS_GUIDE.md](STARLARK_APPS_GUIDE.md) — Starlark-based mini-apps
+- [widget-guide.md](widget-guide.md) — widget development
 
-### 🚀 Getting Started & Setup
+## Configuring plugins
-- [EMULATOR_SETUP_GUIDE.md](EMULATOR_SETUP_GUIDE.md) - Set up development environment with emulator
-- [TRIXIE_UPGRADE_GUIDE.md](TRIXIE_UPGRADE_GUIDE.md) - Upgrade to Raspbian OS 13 "Trixie"
-- [TROUBLESHOOTING_QUICK_START.md](TROUBLESHOOTING_QUICK_START.md) - Common issues and solutions
 
-### 🏗️ Architecture & Design
+- [PLUGIN_CONFIG_QUICK_START.md](PLUGIN_CONFIG_QUICK_START.md) — minimal config you need
-- [PLUGIN_ARCHITECTURE_SPEC.md](PLUGIN_ARCHITECTURE_SPEC.md) - Complete plugin system specification
+- [PLUGIN_CONFIGURATION_GUIDE.md](PLUGIN_CONFIGURATION_GUIDE.md) — schema design
-- [PLUGIN_IMPLEMENTATION_SUMMARY.md](PLUGIN_IMPLEMENTATION_SUMMARY.md) - Plugin system implementation details
+- [PLUGIN_CONFIGURATION_TABS.md](PLUGIN_CONFIGURATION_TABS.md) — multi-tab UI configs
-- [FEATURE_IMPLEMENTATION_SUMMARY.md](FEATURE_IMPLEMENTATION_SUMMARY.md) - Major feature implementations
+- [PLUGIN_CONFIG_ARCHITECTURE.md](PLUGIN_CONFIG_ARCHITECTURE.md) — how the config system works
-- [NESTED_CONFIG_SCHEMAS.md](NESTED_CONFIG_SCHEMAS.md) - Configuration schema design
+- [PLUGIN_CONFIG_CORE_PROPERTIES.md](PLUGIN_CONFIG_CORE_PROPERTIES.md) — properties every plugin honors
-- [NESTED_SCHEMA_IMPLEMENTATION.md](NESTED_SCHEMA_IMPLEMENTATION.md) - Schema implementation details
-- [NESTED_SCHEMA_VISUAL_COMPARISON.md](NESTED_SCHEMA_VISUAL_COMPARISON.md) - Schema comparison visuals
 
-### ⚙️ Configuration & Management
+## Advanced features
-- [PLUGIN_CONFIGURATION_GUIDE.md](PLUGIN_CONFIGURATION_GUIDE.md) - Complete plugin configuration guide
-- [PLUGIN_CONFIGURATION_TABS.md](PLUGIN_CONFIGURATION_TABS.md) - Configuration tabs feature
-- [PLUGIN_CONFIG_QUICK_START.md](PLUGIN_CONFIG_QUICK_START.md) - Quick configuration guide
 
-### 🔌 Plugin Development
+- [ADVANCED_FEATURES.md](ADVANCED_FEATURES.md) — Vegas scroll, on-demand display,
-- [PLUGIN_DEVELOPMENT_GUIDE.md](PLUGIN_DEVELOPMENT_GUIDE.md) - Complete plugin development guide
+  cache management, background services, permissions
-- [PLUGIN_QUICK_REFERENCE.md](PLUGIN_QUICK_REFERENCE.md) - Plugin development quick reference
+- [FONT_MANAGER.md](FONT_MANAGER.md) — font system
-- [PLUGIN_API_REFERENCE.md](PLUGIN_API_REFERENCE.md) - Complete API reference for plugin developers
-- [ADVANCED_PLUGIN_DEVELOPMENT.md](ADVANCED_PLUGIN_DEVELOPMENT.md) - Advanced patterns and examples
-- [PLUGIN_REGISTRY_SETUP_GUIDE.md](PLUGIN_REGISTRY_SETUP_GUIDE.md) - Setting up plugin registry
-- [PLUGIN_DEPENDENCY_GUIDE.md](PLUGIN_DEPENDENCY_GUIDE.md) - Managing plugin dependencies
-- [PLUGIN_DEPENDENCY_TROUBLESHOOTING.md](PLUGIN_DEPENDENCY_TROUBLESHOOTING.md) - Dependency troubleshooting
 
-### 🎮 Plugin Features
+## Reference
-- [ON_DEMAND_DISPLAY_QUICK_START.md](ON_DEMAND_DISPLAY_QUICK_START.md) - Manual display triggering
-- [PLUGIN_LIVE_PRIORITY_QUICK_START.md](PLUGIN_LIVE_PRIORITY_QUICK_START.md) - Live content priority
-- [PLUGIN_LIVE_PRIORITY_API.md](PLUGIN_LIVE_PRIORITY_API.md) - Live priority API reference
-- [PLUGIN_CUSTOM_ICONS_FEATURE.md](PLUGIN_CUSTOM_ICONS_FEATURE.md) - Custom plugin icons
-- [PLUGIN_DISPATCH_IMPLEMENTATION.md](PLUGIN_DISPATCH_IMPLEMENTATION.md) - Plugin dispatch system
-- [PLUGIN_TABS_FEATURE_COMPLETE.md](PLUGIN_TABS_FEATURE_COMPLETE.md) - Plugin tabs feature
 
-### 📡 API Reference
+- [REST_API_REFERENCE.md](REST_API_REFERENCE.md) — all web-interface HTTP endpoints
-- [API_REFERENCE.md](API_REFERENCE.md) - Complete REST API documentation for web interface
+- [PLUGIN_API_REFERENCE.md](PLUGIN_API_REFERENCE.md) — Python APIs available to plugins
-- [PLUGIN_API_REFERENCE.md](PLUGIN_API_REFERENCE.md) - Plugin developer API reference (Display Manager, Cache Manager, Plugin Manager)
+- [DEVELOPER_QUICK_REFERENCE.md](DEVELOPER_QUICK_REFERENCE.md) — common dev tasks
-- [DEVELOPER_QUICK_REFERENCE.md](DEVELOPER_QUICK_REFERENCE.md) - Quick reference for common developer tasks
+- [PLUGIN_IMPLEMENTATION_SUMMARY.md](PLUGIN_IMPLEMENTATION_SUMMARY.md) — what the plugin system actually does
-- [ON_DEMAND_DISPLAY_API.md](ON_DEMAND_DISPLAY_API.md) - On-demand display API reference
 
-### 🛠️ Development & Tools
+## Contributing to LEDMatrix itself
-- [BACKGROUND_SERVICE_README.md](BACKGROUND_SERVICE_README.md) - Background service architecture
-- [FONT_MANAGER_USAGE.md](FONT_MANAGER_USAGE.md) - Font management system
 
-### 🔍 Analysis & Compatibility
+- [DEVELOPMENT.md](DEVELOPMENT.md) — environment setup
-- [RASPBIAN_TRIXIE_COMPATIBILITY_ANALYSIS.md](RASPBIAN_TRIXIE_COMPATIBILITY_ANALYSIS.md) - Detailed Trixie compatibility analysis
+- [HOW_TO_RUN_TESTS.md](HOW_TO_RUN_TESTS.md) — running the test suite
-- [CONFIGURATION_CLEANUP_SUMMARY.md](CONFIGURATION_CLEANUP_SUMMARY.md) - Configuration cleanup details
+- [MULTI_ROOT_WORKSPACE_SETUP.md](MULTI_ROOT_WORKSPACE_SETUP.md) — multi-repo workspace
-- [football_plugin_comparison.md](football_plugin_comparison.md) - Football plugin analysis
+- [MIGRATION_GUIDE.md](MIGRATION_GUIDE.md) — breaking changes between releases
 
-### 📊 Utility & Scripts
+## Archive
-- [README_broadcast_logo_analyzer.md](README_broadcast_logo_analyzer.md) - Broadcast logo analysis tool
-- [README_soccer_logos.md](README_soccer_logos.md) - Soccer logo management
-- [WEB_INTERFACE_TROUBLESHOOTING.md](WEB_INTERFACE_TROUBLESHOOTING.md) - Web interface troubleshooting
 
-## 🔄 Migration & Updates
+`docs/archive/` holds older guides that have been superseded or describe
+features that have been removed. They are kept for historical context and
+git history but should not be relied on.
 
-### Recent Consolidations (October 2025)
+## Contributing to the docs
-- **Implementation Summaries**: Consolidated 7 separate implementation summaries into 2 comprehensive guides:
-  - `FEATURE_IMPLEMENTATION_SUMMARY.md` (AP Top 25, Plugin System, Configuration, Web Interface, Trixie Compatibility)
-  - `PLUGIN_IMPLEMENTATION_SUMMARY.md` (Plugin system technical details)
-- **Trixie Documentation**: Merged 4 Trixie-related documents into `TRIXIE_UPGRADE_GUIDE.md`
-- **Removed Redundancy**: Eliminated duplicate documents and outdated debug guides
-- **Total Reduction**: 53 → 39 documents (26% reduction)
 
-### Migration Notes
+- Markdown only, professional tone, minimal emoji.
-- Old implementation summary documents have been consolidated
+- Prefer adding to an existing page over creating a new one. If you add a
-- Trixie upgrade information is now centralized in one guide
+  new page, link it from this index in the section it belongs to.
-- Deprecated manager documentation has been removed (no longer applicable)
+- If a page becomes obsolete, move it to `docs/archive/` rather than
-- Very specific debug documents have been archived or removed
+  deleting it, so links don't rot.
-
+- Keep examples runnable — paths, commands, and config keys here should
-## 🎯 Key Resources by Use Case
+  match what's actually in the repo.
-
-### I'm new to LEDMatrix
-1. [Main README](../README.md) - Installation and setup
-2. [EMULATOR_SETUP_GUIDE.md](EMULATOR_SETUP_GUIDE.md) - Development environment
-3. [PLUGIN_QUICK_REFERENCE.md](PLUGIN_QUICK_REFERENCE.md) - Understanding the system
-
-### I want to create a plugin
-1. [PLUGIN_DEVELOPMENT_GUIDE.md](PLUGIN_DEVELOPMENT_GUIDE.md) - Complete development guide
-2. [PLUGIN_API_REFERENCE.md](PLUGIN_API_REFERENCE.md) - Available methods and APIs
-3. [ADVANCED_PLUGIN_DEVELOPMENT.md](ADVANCED_PLUGIN_DEVELOPMENT.md) - Advanced patterns and examples
-4. [PLUGIN_CONFIGURATION_GUIDE.md](PLUGIN_CONFIGURATION_GUIDE.md) - Configuration setup
-5. [PLUGIN_ARCHITECTURE_SPEC.md](PLUGIN_ARCHITECTURE_SPEC.md) - Complete specification
-
-### I want to upgrade to Trixie
-1. [TRIXIE_UPGRADE_GUIDE.md](TRIXIE_UPGRADE_GUIDE.md) - Complete upgrade guide
-2. [RASPBIAN_TRIXIE_COMPATIBILITY_ANALYSIS.md](RASPBIAN_TRIXIE_COMPATIBILITY_ANALYSIS.md) - Technical details
-
-### I need to troubleshoot an issue
-1. [TROUBLESHOOTING_QUICK_START.md](TROUBLESHOOTING_QUICK_START.md) - Common issues
-2. [WEB_INTERFACE_TROUBLESHOOTING.md](WEB_INTERFACE_TROUBLESHOOTING.md) - Web interface problems
-3. [PLUGIN_DEPENDENCY_TROUBLESHOOTING.md](PLUGIN_DEPENDENCY_TROUBLESHOOTING.md) - Dependency issues
-
-### I want to understand the architecture
-1. [PLUGIN_ARCHITECTURE_SPEC.md](PLUGIN_ARCHITECTURE_SPEC.md) - System architecture
-2. [FEATURE_IMPLEMENTATION_SUMMARY.md](FEATURE_IMPLEMENTATION_SUMMARY.md) - Feature overview
-3. [PLUGIN_IMPLEMENTATION_SUMMARY.md](PLUGIN_IMPLEMENTATION_SUMMARY.md) - Implementation details
-
-## 📝 Contributing to Documentation
-
-### Documentation Standards
-- Use Markdown format with consistent headers
-- Include code examples where helpful
-- Provide both quick start and detailed reference sections
-- Keep implementation summaries focused on what was built, not how to use
-
-### Adding New Documentation
-1. Place in appropriate category (see sections above)
-2. Update this README.md with the new document
-3. Follow naming conventions (FEATURE_NAME.md)
-4. Consider if content should be consolidated with existing docs
-
-### Consolidation Guidelines
-- **Implementation Summaries**: Consolidate into feature-specific summaries
-- **Quick References**: Keep if they provide unique value, otherwise merge
-- **Debug Documents**: Remove after issues are resolved
-- **Migration Guides**: Consolidate when migrations are complete
-
-## 🔗 Related Documentation
-
-- [Main Project README](../README.md) - Installation and basic usage
-- [Web Interface README](../web_interface/README.md) - Web interface details
-- [LEDMatrix Wiki](../LEDMatrix.wiki/) - Extended documentation and guides
-- [GitHub Issues](https://github.com/ChuckBuilds/LEDMatrix/issues) - Bug reports and feature requests
-- [GitHub Discussions](https://github.com/ChuckBuilds/LEDMatrix/discussions) - Community support
-
-## 📊 Documentation Statistics
-
-- **Total Documents**: ~35 (after consolidation)
-- **Categories**: 8 major sections (including new API Reference section)
-- **Primary Languages**: English
-- **Format**: Markdown (.md)
-- **Last Update**: December 2025
-- **Coverage**: Installation, development, troubleshooting, architecture, API references
-
-### Recent Improvements (December 2025)
-- ✅ Complete REST API documentation (50+ endpoints)
-- ✅ Complete Plugin API reference (Display Manager, Cache Manager, Plugin Manager)
-- ✅ Advanced plugin development guide with examples
-- ✅ Consolidated plugin configuration documentation
-- ✅ Developer quick reference guide
-- ✅ Better organization for end users and developers
-
----
-
-*This documentation index was last updated: December 2025*
-
-*For questions or suggestions about the documentation, please open an issue or start a discussion on GitHub.*

docs/REST_API_REFERENCE.md

@@ -24,6 +24,17 @@ All endpoints return JSON responses with a standard format:
 - [Cache](#cache)
 - [WiFi](#wifi)
 - [Streams](#streams)
+- [Logs](#logs)
+- [Error tracking](#error-tracking)
+- [Health](#health)
+- [Schedule (dim/power)](#schedule-dimpower)
+- [Plugin-specific endpoints](#plugin-specific-endpoints)
+- [Starlark Apps](#starlark-apps)
+
+> The API blueprint is mounted at `/api/v3` (`web_interface/app.py:144`).
+> SSE stream endpoints (`/api/v3/stream/*`) are defined directly on the
+> Flask app at `app.py:607-615`. There are about 92 routes total — see
+> `web_interface/blueprints/api_v3.py` for the canonical list.
 
 ---
 
@@ -1201,10 +1212,16 @@ Upload a custom font file.
 
 ### Delete Font
 
-**DELETE** `/api/v3/fonts/delete/<font_family>`
+**DELETE** `/api/v3/fonts/<font_family>`
 
 Delete an uploaded font.
 
+### Font Preview
+
+**GET** `/api/v3/fonts/preview?family=<font_family>&text=<sample>`
+
+Render a small preview image of a font for use in the web UI font picker.
+
 ---
 
 ## Cache
@@ -1439,6 +1456,130 @@ Get recent log entries.
 
 ---
 
+## Error tracking
+
+### Get Error Summary
+
+**GET** `/api/v3/errors/summary`
+
+Aggregated counts of recent errors across all plugins and core
+components, used by the web UI's error indicator.
+
+### Get Plugin Errors
+
+**GET** `/api/v3/errors/plugin/<plugin_id>`
+
+Recent errors for a specific plugin.
+
+### Clear Errors
+
+**POST** `/api/v3/errors/clear`
+
+Clear the in-memory error aggregator.
+
+---
+
+## Health
+
+### Health Check
+
+**GET** `/api/v3/health`
+
+Lightweight liveness check used by the WiFi monitor and external
+monitoring tools.
+
+---
+
+## Schedule (dim/power)
+
+### Get Dim Schedule
+
+**GET** `/api/v3/config/dim-schedule`
+
+Read the dim/power schedule that automatically reduces brightness or
+turns the display off at configured times.
+
+### Update Dim Schedule
+
+**POST** `/api/v3/config/dim-schedule`
+
+Update the dim schedule. Body matches the structure returned by GET.
+
+---
+
+## Plugin-specific endpoints
+
+A handful of endpoints belong to individual built-in or shipped plugins.
+
+### Calendar
+
+**GET** `/api/v3/plugins/calendar/list-calendars`
+
+List the calendars available on the authenticated Google account.
+Used by the calendar plugin's config UI.
+
+### Of The Day
+
+**POST** `/api/v3/plugins/of-the-day/json/upload`
+
+Upload a JSON data file for the Of-The-Day plugin's category data.
+
+**POST** `/api/v3/plugins/of-the-day/json/delete`
+
+Delete a previously uploaded Of-The-Day data file.
+
+### Plugin Static Assets
+
+**GET** `/api/v3/plugins/<plugin_id>/static/<path:file_path>`
+
+Serve a static asset (image, font, etc.) from a plugin's directory.
+Used internally by the web UI to render plugin previews and icons.
+
+---
+
+## Starlark Apps
+
+The Starlark plugin lets you run [Tronbyt](https://github.com/tronbyt/apps)
+Starlark apps on the matrix. These endpoints expose its UI.
+
+### Status
+
+**GET** `/api/v3/starlark/status`
+
+Returns whether the Pixlet binary is installed and the Starlark plugin
+is operational.
+
+### Install Pixlet
+
+**POST** `/api/v3/starlark/install-pixlet`
+
+Download and install the Pixlet binary on the Pi.
+
+### Apps
+
+**GET** `/api/v3/starlark/apps` — list installed Starlark apps
+**GET** `/api/v3/starlark/apps/<app_id>` — get app details
+**DELETE** `/api/v3/starlark/apps/<app_id>` — uninstall an app
+**GET** `/api/v3/starlark/apps/<app_id>/config` — get app config schema
+**PUT** `/api/v3/starlark/apps/<app_id>/config` — update app config
+**POST** `/api/v3/starlark/apps/<app_id>/render` — render app to a frame
+**POST** `/api/v3/starlark/apps/<app_id>/toggle` — enable/disable app
+
+### Repository (Tronbyt community apps)
+
+**GET** `/api/v3/starlark/repository/categories` — browse categories
+**GET** `/api/v3/starlark/repository/browse?category=<cat>` — browse apps
+**POST** `/api/v3/starlark/repository/install` — install an app from the
+community repository
+
+### Upload custom app
+
+**POST** `/api/v3/starlark/upload`
+
+Upload a custom Starlark `.star` file as a new app.
+
+---
+
 ## Error Responses
 
 All endpoints may return error responses in the following format:

docs/SSH_UNAVAILABLE_AFTER_INSTALL.md

@@ -54,7 +54,7 @@ If the script reboots the Pi (which it recommends), network services may restart
    # Connect to your WiFi network (replace with your SSID and password)
    sudo nmcli device wifi connect "YourWiFiSSID" password "YourPassword"
    
-   # Or use the web interface at http://192.168.4.1:5001
+   # Or use the web interface at http://192.168.4.1:5000
    # Navigate to WiFi tab and connect to your network
    ```
 
@@ -177,9 +177,9 @@ sudo systemctl restart NetworkManager
 
 Even if SSH is unavailable, you can access the web interface:
 
-1. **Via AP Mode**: Connect to **LEDMatrix-Setup** network and visit `http://192.168.4.1:5001`
+1. **Via AP Mode**: Connect to **LEDMatrix-Setup** network and visit `http://192.168.4.1:5000`
-2. **Via WiFi**: If WiFi is connected, visit `http://<pi-ip-address>:5001`
+2. **Via WiFi**: If WiFi is connected, visit `http://<pi-ip-address>:5000`
-3. **Via Ethernet**: Visit `http://<pi-ip-address>:5001`
+3. **Via Ethernet**: Visit `http://<pi-ip-address>:5000`
 
 The web interface allows you to:
 - Configure WiFi connections

docs/STARLARK_APPS_GUIDE.md

@@ -0,0 +1,500 @@
+# Starlark Apps Guide
+
+## Overview
+
+The Starlark Apps plugin for LEDMatrix enables you to run **Tidbyt/Tronbyte community apps** on your LED matrix display without modification. This integration allows you to access hundreds of pre-built widgets and apps from the vibrant Tidbyt community ecosystem.
+
+## Important: Third-Party Content
+
+**⚠️ Apps are NOT managed by the LEDMatrix project**
+
+- Starlark apps are developed and maintained by the **Tidbyt/Tronbyte community**
+- LEDMatrix provides the runtime environment but does **not** create, maintain, or support these apps
+- All apps originate from the [Tronbyte Apps Repository](https://github.com/tronbyt/apps)
+- App quality, functionality, and security are the responsibility of individual app authors
+- LEDMatrix is not affiliated with Tidbyt Inc. or the Tronbyte project
+
+## What is Starlark?
+
+[Starlark](https://github.com/bazelbuild/starlark) is a Python-like language originally developed by Google for the Bazel build system. Tidbyt adopted Starlark for building LED display apps because it's:
+
+- **Sandboxed**: Apps run in a safe, restricted environment
+- **Simple**: Python-like syntax that's easy to learn
+- **Deterministic**: Apps produce consistent output
+- **Fast**: Compiled and optimized for performance
+
+## How It Works
+
+### Architecture
+
+```text
+┌─────────────────────────────────────────────────────────┐
+│                    LEDMatrix System                      │
+│  ┌────────────────────────────────────────────────────┐ │
+│  │         Starlark Apps Plugin (manager.py)          │ │
+│  │  • Manages app lifecycle (install/uninstall)       │ │
+│  │  • Handles app configuration                       │ │
+│  │  • Schedules app rendering                         │ │
+│  └─────────────────┬──────────────────────────────────┘ │
+│                    │                                     │
+│  ┌─────────────────▼──────────────────────────────────┐ │
+│  │      Pixlet Renderer (pixlet_renderer.py)          │ │
+│  │  • Executes .star files using Pixlet CLI           │ │
+│  │  • Extracts configuration schemas                  │ │
+│  │  • Outputs WebP animations                         │ │
+│  └─────────────────┬──────────────────────────────────┘ │
+│                    │                                     │
+│  ┌─────────────────▼──────────────────────────────────┐ │
+│  │      Frame Extractor (frame_extractor.py)          │ │
+│  │  • Decodes WebP animations into frames             │ │
+│  │  • Scales/centers output for display size          │ │
+│  │  • Manages frame timing                            │ │
+│  └─────────────────┬──────────────────────────────────┘ │
+│                    │                                     │
+│  ┌─────────────────▼──────────────────────────────────┐ │
+│  │            LED Matrix Display                       │ │
+│  │  • Renders final output to physical display        │ │
+│  └────────────────────────────────────────────────────┘ │
+└─────────────────────────────────────────────────────────┘
+
+                    ▲
+                    │
+         Downloads apps from
+                    │
+┌───────────────────┴─────────────────────────────────────┐
+│         Tronbyte Apps Repository (GitHub)                │
+│  • 974+ community-built apps                             │
+│  • Weather, sports, stocks, games, clocks, etc.          │
+│  • https://github.com/tronbyt/apps                       │
+└──────────────────────────────────────────────────────────┘
+```
+
+### Rendering Pipeline
+
+1. **User installs app** from the Tronbyte repository via web UI
+2. **Plugin downloads** the `.star` file (and any assets like images/fonts)
+3. **Schema extraction** parses configuration options from the `.star` source
+4. **User configures** the app through the web UI (timezone, location, API keys, etc.)
+5. **Pixlet renders** the app with user config → produces WebP animation
+6. **Frame extraction** decodes WebP → individual PIL Image frames
+7. **Display scaling** adapts 64x32 Tidbyt output to your matrix size
+8. **Rotation** cycles through your installed apps based on schedule
+
+## Getting Started
+
+### 1. Install Pixlet
+
+Pixlet is the rendering engine that executes Starlark apps. The plugin will attempt to use:
+
+1. **Bundled binary** (recommended): Downloaded to `bin/pixlet/pixlet-{platform}-{arch}`
+2. **System installation**: If `pixlet` is available in your PATH
+
+#### Auto-Install via Web UI
+
+Navigate to: **Plugin Manager → Starlark Apps tab (in the second nav row) → Status → Install Pixlet**
+
+This runs the bundled installation script which downloads the appropriate binary for your platform.
+
+#### Manual Installation
+
+```bash
+cd /path/to/LEDMatrix
+bash scripts/download_pixlet.sh
+```
+
+Verify installation:
+```bash
+./bin/pixlet/pixlet-linux-amd64 version
+# Pixlet 0.50.2 (or later)
+```
+
+### 2. Enable the Starlark Apps Plugin
+
+1. Open the web UI (`http://your-pi-ip:5000`)
+2. Open the **Plugin Manager** tab
+3. Find **Starlark Apps** in the **Installed Plugins** list
+4. Enable the plugin (it then gets its own tab in the second nav row)
+5. Configure settings:
+   - **Magnify**: Auto-calculated based on your display size (or set manually)
+   - **Render Interval**: How often apps re-render (default: 300s)
+   - **Display Duration**: How long each app shows (default: 15s)
+   - **Cache Output**: Enable to reduce re-rendering (recommended)
+
+### 3. Browse and Install Apps
+
+1. Navigate to **Plugin Manager → Starlark Apps tab (in the second nav row) → App Store**
+2. Browse available apps (974+ options)
+3. Filter by category: Weather, Sports, Finance, Games, Clocks, etc.
+4. Click **Install** on desired apps
+5. Configure each app:
+   - Set location/timezone
+   - Enter API keys if required
+   - Customize display preferences
+
+### 4. Configure Apps
+
+Each app may have different configuration options:
+
+#### Common Configuration Types
+
+- **Location** (lat/lng/timezone): For weather, clocks, transit
+- **API Keys**: For services like weather, stocks, sports scores
+- **Display Preferences**: Colors, units, layouts
+- **Dropdown Options**: Team selections, language, themes
+- **Toggles**: Enable/disable features
+
+Configuration is stored in `starlark-apps/{app-id}/config.json` and persists across app updates.
+
+## App Sources and Categories
+
+All apps are sourced from the [Tronbyte Apps Repository](https://github.com/tronbyt/apps). Popular categories include:
+
+### 🌤️ Weather
+- Analog Clock (with weather)
+- Current Weather
+- Weather Forecast
+- Air Quality Index
+
+### 🏈 Sports
+- NFL Scores
+- NBA Scores
+- MLB Scores
+- NHL Scores
+- Soccer/Football Scores
+- Formula 1 Results
+
+### 💰 Finance
+- Stock Tickers
+- Cryptocurrency Prices
+- Market Indices
+
+### 🎮 Games & Fun
+- Conway's Game of Life
+- Pong
+- Nyan Cat
+- Retro Animations
+
+### 🕐 Clocks
+- Analog Clock
+- Fuzzy Clock
+- Binary Clock
+- Word Clock
+
+### 📰 Information
+- News Headlines
+- RSS Feeds
+- GitHub Activity
+- Reddit Feed
+
+### 🚌 Transit & Travel
+- Transit Arrivals
+- Flight Tracker
+- Train Schedules
+
+## Display Size Compatibility
+
+Tronbyte/Tidbyt apps are designed for **64×32 displays**. LEDMatrix automatically adapts content for different display sizes:
+
+### Magnification
+
+The plugin calculates optimal magnification based on your display:
+
+```text
+magnify = floor(min(display_width / 64, display_height / 32))
+```
+
+Examples:
+- **64×32**: magnify = 1 (native, pixel-perfect)
+- **128×64**: magnify = 2 (2x scaling, crisp)
+- **192×64**: magnify = 2 (2x + horizontal centering)
+- **256×64**: magnify = 2 (2x + centering)
+
+### Scaling Modes
+
+**Config → Starlark Apps → Scale Method:**
+- `nearest` (default): Sharp pixels, retro look
+- `bilinear`: Smooth scaling, slight blur
+- `bicubic`: Higher quality smooth scaling
+- `lanczos`: Best quality, most processing
+
+**Center vs Scale:**
+- `scale_output=true`: Stretch to fill display (may distort aspect ratio)
+- `center_small_output=true`: Center output without stretching (preserves aspect ratio)
+
+## Configuration Schema Extraction
+
+LEDMatrix automatically extracts configuration schemas from Starlark apps by parsing the `get_schema()` function in the `.star` source code.
+
+### Supported Field Types
+
+| Starlark Type | Web UI Rendering |
+|--------------|------------------|
+| `schema.Location` | Lat/Lng/Timezone picker |
+| `schema.Text` | Text input field |
+| `schema.Toggle` | Checkbox/switch |
+| `schema.Dropdown` | Select dropdown |
+| `schema.Color` | Color picker |
+| `schema.DateTime` | Date/time picker |
+| `schema.OAuth2` | Warning message (not supported) |
+| `schema.PhotoSelect` | Warning message (not supported) |
+| `schema.LocationBased` | Text fallback with note |
+| `schema.Typeahead` | Text fallback with note |
+
+### Schema Coverage
+
+- **90-95%** of apps: Full schema support
+- **5%**: Partial extraction (complex/dynamic schemas)
+- **<1%**: No schema (apps without configuration)
+
+Apps without extracted schemas can still run with default settings.
+
+## File Structure
+
+```text
+LEDMatrix/
+├── plugin-repos/starlark-apps/     # Plugin source code
+│   ├── manager.py                  # Main plugin logic
+│   ├── pixlet_renderer.py          # Pixlet CLI wrapper
+│   ├── frame_extractor.py          # WebP decoder
+│   ├── tronbyte_repository.py      # GitHub API client
+│   └── requirements.txt            # Python dependencies
+│
+├── starlark-apps/                  # Installed apps (user data)
+│   ├── manifest.json               # App registry
+│   │
+│   └── analogclock/                # Example app
+│       ├── analogclock.star        # Starlark source
+│       ├── config.json             # User configuration
+│       ├── schema.json             # Extracted schema
+│       ├── cached_render.webp      # Rendered output cache
+│       └── images/                 # App assets (if any)
+│           ├── hour_hand.png
+│           └── minute_hand.png
+│
+├── bin/pixlet/                     # Pixlet binaries
+│   ├── pixlet-linux-amd64
+│   ├── pixlet-linux-arm64
+│   └── pixlet-darwin-arm64
+│
+└── scripts/
+    └── download_pixlet.sh          # Pixlet installer
+```
+
+## API Keys and External Services
+
+Many apps require API keys for external services:
+
+### Common API Services
+
+- **Weather**: OpenWeatherMap, Weather.gov, Dark Sky
+- **Sports**: ESPN, The Sports DB, SportsData.io
+- **Finance**: Alpha Vantage, CoinGecko, Yahoo Finance
+- **Transit**: TransitLand, NextBus, local transit APIs
+- **News**: NewsAPI, Reddit, RSS feeds
+
+### Security Note
+
+- API keys are stored in `config.json` files on disk
+- The LEDMatrix web interface does NOT encrypt API keys
+- Ensure your Raspberry Pi is on a trusted network
+- Use read-only or limited-scope API keys when possible
+- **Never commit `starlark-apps/*/config.json` to version control**
+
+## Troubleshooting
+
+### Pixlet Not Found
+
+**Symptom**: "Pixlet binary not found" error
+
+**Solutions**:
+1. Run auto-installer: **Plugin Manager → Starlark Apps tab (in the second nav row) → Install Pixlet**
+2. Manual install: `bash scripts/download_pixlet.sh`
+3. Check permissions: `chmod +x bin/pixlet/pixlet-*`
+4. Verify architecture: `uname -m` matches binary name
+
+### App Fails to Render
+
+**Symptom**: "Rendering failed" error in logs
+
+**Solutions**:
+1. Check logs: `journalctl -u ledmatrix | grep -i pixlet`
+2. Verify config: Ensure all required fields are filled
+3. Test manually: `./bin/pixlet/pixlet-linux-amd64 render starlark-apps/{app-id}/{app-id}.star`
+4. Missing assets: Some apps need images/fonts that may fail to download
+5. API issues: Check API keys and rate limits
+
+### Schema Not Extracted
+
+**Symptom**: App installs but shows no configuration options
+
+**Solutions**:
+1. App may not have a `get_schema()` function (normal for some apps)
+2. Schema extraction failed: Check logs for parse errors
+3. Manual config: Edit `starlark-apps/{app-id}/config.json` directly
+4. Report issue: File bug with app details at LEDMatrix GitHub
+
+### Apps Show Distorted/Wrong Size
+
+**Symptom**: Content appears stretched, squished, or cropped
+
+**Solutions**:
+1. Check magnify setting: **Plugin Manager → Starlark Apps tab (in the second nav row) → Config**
+2. Try `center_small_output=true` to preserve aspect ratio
+3. Adjust `magnify` manually (1-8) for your display size
+4. Some apps assume 64×32 - may not scale perfectly to all sizes
+
+### App Shows Outdated Data
+
+**Symptom**: Weather, sports scores, etc. don't update
+
+**Solutions**:
+1. Check render interval: **App Config → Render Interval** (300s default)
+2. Force re-render: **Plugin Manager → Starlark Apps tab (in the second nav row) → {App} → Render Now**
+3. Clear cache: Restart LEDMatrix service
+4. API rate limits: Some services throttle requests
+5. Check app logs for API errors
+
+## Performance Considerations
+
+### Render Intervals
+
+- Apps re-render on a schedule (default: 300s = 5 minutes)
+- Lower intervals = more CPU/API usage
+- Recommended minimums:
+  - Static content (clocks): 30-60s
+  - Weather: 300s (5min)
+  - Sports scores: 60-120s
+  - Stock tickers: 60s
+
+### Caching
+
+Enable caching to reduce CPU load:
+- `cache_rendered_output=true` (recommended)
+- `cache_ttl=300` (5 minutes)
+
+Cached WebP files are stored in `starlark-apps/{app-id}/cached_render.webp`
+
+### Display Rotation
+
+Balance number of enabled apps with display duration:
+- 5 apps × 15s = 75s full cycle
+- 20 apps × 15s = 300s (5 min) cycle
+
+Long cycles may cause apps to render before being displayed.
+
+## Limitations
+
+### Unsupported Features
+
+- **OAuth2 Authentication**: Apps requiring OAuth login won't work
+- **PhotoSelect**: Image upload from mobile device not supported
+- **Push Notifications**: Apps can't receive real-time events
+- **Background Jobs**: No persistent background tasks
+
+### API Rate Limits
+
+Many apps use free API tiers with rate limits:
+- Rendering too frequently may exceed limits
+- Use appropriate `render_interval` settings
+- Consider paid API tiers for heavy usage
+
+### Display Size Constraints
+
+Apps designed for 64×32 may not utilize larger displays fully:
+- Content may appear small on 128×64+ displays
+- Magnification helps but doesn't add detail
+- Some apps hard-code 64×32 dimensions
+
+## Advanced Usage
+
+### Manual App Installation
+
+Upload custom `.star` files:
+1. Navigate to **Starlark Apps → Upload**
+2. Select `.star` file from disk
+3. Configure app ID and metadata
+4. Set render/display timing
+
+### Custom App Development
+
+While LEDMatrix runs Tronbyte apps, you can also create your own:
+
+1. **Learn Starlark**: [Tidbyt Developer Docs](https://tidbyt.dev/)
+2. **Write `.star` file**: Use Pixlet APIs for rendering
+3. **Test locally**: `pixlet render myapp.star`
+4. **Upload**: Use LEDMatrix web UI to install
+5. **Share**: Contribute to [Tronbyte Apps](https://github.com/tronbyt/apps) repo
+
+### Configuration Reference
+
+**Plugin Config** (`config/config.json` → `plugins.starlark-apps`):
+
+```json
+{
+  "enabled": true,
+  "magnify": 0,                    // 0 = auto, 1-8 = manual
+  "render_timeout": 30,            // Max seconds for Pixlet render
+  "cache_rendered_output": true,   // Cache WebP files
+  "cache_ttl": 300,                // Cache duration (seconds)
+  "scale_output": true,            // Scale to display size
+  "scale_method": "nearest",       // nearest|bilinear|bicubic|lanczos
+  "center_small_output": false,    // Center instead of scale
+  "default_frame_delay": 50,       // Frame timing (ms)
+  "max_frames": null,              // Limit frames (null = unlimited)
+  "auto_refresh_apps": true        // Auto re-render on interval
+}
+```
+
+**App Config** (`starlark-apps/{app-id}/config.json`):
+
+```json
+{
+  "location": "{\"lat\":\"40.7128\",\"lng\":\"-74.0060\",\"timezone\":\"America/New_York\"}",
+  "units": "imperial",
+  "api_key": "your-api-key-here",
+  "render_interval": 300,          // App-specific override
+  "display_duration": 15           // App-specific override
+}
+```
+
+## Resources
+
+### Official Documentation
+
+- **Tidbyt Developer Docs**: https://tidbyt.dev/
+- **Starlark Language**: https://github.com/bazelbuild/starlark
+- **Pixlet Repository**: https://github.com/tidbyt/pixlet
+- **Tronbyte Apps**: https://github.com/tronbyt/apps
+
+### LEDMatrix Documentation
+
+- [Plugin Development Guide](PLUGIN_DEVELOPMENT_GUIDE.md)
+- [REST API Reference](REST_API_REFERENCE.md)
+- [Troubleshooting Guide](TROUBLESHOOTING.md)
+
+### Community
+
+- **Tidbyt Community**: https://discuss.tidbyt.com/
+- **Tronbyte Apps Issues**: https://github.com/tronbyt/apps/issues
+- **LEDMatrix Issues**: https://github.com/ChuckBuilds/LEDMatrix/issues
+
+## License and Legal
+
+- **LEDMatrix**: MIT License (see project root)
+- **Starlark Apps Plugin**: MIT License (part of LEDMatrix)
+- **Pixlet**: Apache 2.0 License (Tidbyt Inc.)
+- **Tronbyte Apps**: Various licenses (see individual app headers)
+- **Starlark Language**: Apache 2.0 License (Google/Bazel)
+
+**Disclaimer**: LEDMatrix is an independent project and is not affiliated with, endorsed by, or sponsored by Tidbyt Inc. The Starlark Apps plugin enables interoperability with Tidbyt's open-source ecosystem but does not imply any official relationship.
+
+## Support
+
+For issues with:
+- **LEDMatrix integration**: File issues at [LEDMatrix GitHub](https://github.com/ChuckBuilds/LEDMatrix/issues)
+- **Specific apps**: File issues at [Tronbyte Apps](https://github.com/tronbyt/apps/issues)
+- **Pixlet rendering**: File issues at [Pixlet Repository](https://github.com/tidbyt/pixlet/issues)
+
+---
+
+**Ready to get started?** Install the Starlark Apps plugin and explore 974+ community apps! 🎨

docs/TROUBLESHOOTING.md

@@ -0,0 +1,916 @@
+# Troubleshooting Guide
+
+## Quick Diagnosis Steps
+
+Run these checks first to quickly identify common issues:
+
+### 1. Check Service Status
+
+```bash
+# Check all LEDMatrix services
+sudo systemctl status ledmatrix
+sudo systemctl status ledmatrix-web
+sudo systemctl status ledmatrix-wifi-monitor
+
+# Check AP mode services (if using WiFi)
+sudo systemctl status hostapd
+sudo systemctl status dnsmasq
+```
+
+**Note:** Look for `active (running)` status and check for error messages in the output.
+
+### 2. View Service Logs
+
+**IMPORTANT:** The web service logs to **syslog**, NOT stdout. Use `journalctl` to view logs:
+
+```bash
+# View all recent logs
+sudo journalctl -u ledmatrix -n 50
+sudo journalctl -u ledmatrix-web -n 50
+
+# Follow logs in real-time
+sudo journalctl -u ledmatrix -f
+
+# View logs from last hour
+sudo journalctl -u ledmatrix-web --since "1 hour ago"
+
+# Filter for errors only
+sudo journalctl -u ledmatrix -p err
+```
+
+### 3. Run Diagnostic Scripts
+
+```bash
+# Web interface diagnostics
+bash scripts/diagnose_web_interface.sh
+
+# WiFi setup verification
+./scripts/verify_wifi_setup.sh
+
+# Captive portal troubleshooting
+./scripts/troubleshoot_captive_portal.sh
+```
+
+> Weather is provided by the `ledmatrix-weather` plugin (installed via the
+> Plugin Store). To troubleshoot weather, check that plugin's tab in the
+> web UI for its API key and recent error messages, then watch the
+> **Logs** tab.
+
+### 4. Check Configuration
+
+```bash
+# Verify web interface autostart
+cat config/config.json | grep web_display_autostart
+
+# Check plugin enabled status
+cat config/config.json | grep -A 2 "plugin-id"
+
+# Verify API keys present
+ls -l config/config_secrets.json
+```
+
+### 5. Test Manual Startup
+
+```bash
+# Test web interface manually
+python3 web_interface/start.py
+
+# If it works manually but not as a service, check systemd service file
+```
+
+---
+
+## Common Issues by Category
+
+### Web Interface & Service Issues
+
+#### Service Not Running/Starting
+
+**Symptoms:**
+- Cannot access web interface at http://your-pi-ip:5000
+- `systemctl status ledmatrix-web` shows `inactive (dead)`
+
+**Solutions:**
+
+1. **Start the service:**
+   ```bash
+   sudo systemctl start ledmatrix-web
+   ```
+
+2. **Enable on boot:**
+   ```bash
+   sudo systemctl enable ledmatrix-web
+   ```
+
+3. **Check why it failed:**
+   ```bash
+   sudo journalctl -u ledmatrix-web -n 50
+   ```
+
+#### web_display_autostart is False
+
+**Symptoms:**
+- Service exists but web interface doesn't start automatically
+- Logs show service starting but nothing happens
+
+**Solution:**
+
+```bash
+# Edit config.json
+nano config/config.json
+
+# Set web_display_autostart to true
+{
+  "web_display_autostart": true,
+  ...
+}
+
+# Restart service
+sudo systemctl restart ledmatrix-web
+```
+
+#### Import or Dependency Errors
+
+**Symptoms:**
+- Logs show `ModuleNotFoundError` or `ImportError`
+- Service fails to start with Python errors
+
+**Solutions:**
+
+1. **Install dependencies:**
+   ```bash
+   pip3 install --break-system-packages -r requirements.txt
+   pip3 install --break-system-packages -r web_interface/requirements.txt
+   ```
+
+2. **Test imports step-by-step:**
+   ```bash
+   python3 -c "from src.config_manager import ConfigManager; print('OK')"
+   python3 -c "from src.plugin_system.plugin_manager import PluginManager; print('OK')"
+   python3 -c "from web_interface.app import app; print('OK')"
+   ```
+
+3. **Check Python path:**
+   ```bash
+   python3 -c "import sys; print(sys.path)"
+   ```
+
+#### Port Already in Use
+
+**Symptoms:**
+- Error: `Address already in use`
+- Service fails to bind to port 5000
+
+**Solutions:**
+
+1. **Check what's using the port:**
+   ```bash
+   sudo lsof -i :5000
+   ```
+
+2. **Kill the conflicting process:**
+   ```bash
+   sudo kill -9 <PID>
+   ```
+
+3. **Or change the port in start.py:**
+   ```python
+   app.run(host='0.0.0.0', port=5051)
+   ```
+
+#### Permission Issues
+
+**Symptoms:**
+- `Permission denied` errors in logs
+- Cannot read/write configuration files
+
+**Solutions:**
+
+```bash
+# Fix ownership of LEDMatrix directory
+sudo chown -R ledpi:ledpi /home/ledpi/LEDMatrix
+
+# Fix config file permissions
+sudo chmod 644 config/config.json
+sudo chmod 640 config/config_secrets.json
+
+# Verify service runs as correct user
+sudo systemctl cat ledmatrix-web | grep User
+```
+
+#### Flask/Blueprint Import Errors
+
+**Symptoms:**
+- `ImportError: cannot import name 'app'`
+- `ModuleNotFoundError: No module named 'blueprints'`
+
+**Solutions:**
+
+1. **Verify file structure:**
+   ```bash
+   ls -l web_interface/app.py
+   ls -l web_interface/blueprints/api_v3.py
+   ls -l web_interface/blueprints/pages_v3.py
+   ```
+
+2. **Check for __init__.py files:**
+   ```bash
+   ls -l web_interface/__init__.py
+   ls -l web_interface/blueprints/__init__.py
+   ```
+
+3. **Test import manually:**
+   ```bash
+   cd /home/ledpi/LEDMatrix
+   python3 -c "from web_interface.app import app"
+   ```
+
+---
+
+### WiFi & AP Mode Issues
+
+#### AP Mode Not Activating
+
+**Symptoms:**
+- WiFi disconnected but AP mode doesn't start
+- Cannot find "LEDMatrix-Setup" network
+
+**Solutions:**
+
+1. **Check auto-enable setting:**
+   ```bash
+   cat config/wifi_config.json | grep auto_enable_ap_mode
+   # Should show: "auto_enable_ap_mode": true
+   ```
+
+2. **Verify WiFi monitor service is running:**
+   ```bash
+   sudo systemctl status ledmatrix-wifi-monitor
+   ```
+
+3. **Wait for grace period (90 seconds):**
+   - AP mode requires 3 consecutive disconnected checks at 30-second intervals
+   - Total wait time: 90 seconds after WiFi disconnects
+
+4. **Check if Ethernet is connected:**
+   ```bash
+   nmcli device status
+   # If Ethernet is connected, AP mode won't activate
+   ```
+
+5. **Check required services:**
+   ```bash
+   sudo systemctl status hostapd
+   sudo systemctl status dnsmasq
+   ```
+
+6. **Manually enable AP mode:**
+   ```bash
+   # Via API
+   curl -X POST http://localhost:5000/api/wifi/ap/enable
+
+   # Via Python
+   python3 -c "
+   from src.wifi_manager import WiFiManager
+   wm = WiFiManager()
+   wm.enable_ap_mode()
+   "
+   ```
+
+#### Cannot Connect to AP Mode / Connection Refused
+
+**Symptoms:**
+- Can see "LEDMatrix-Setup" network but can't connect to web interface
+- Browser shows "Connection Refused" or "Can't connect to server"
+- AP mode active but web interface not accessible
+
+**Solutions:**
+
+1. **Verify web server is running:**
+   ```bash
+   sudo systemctl status ledmatrix-web
+   # Should be active (running)
+   ```
+
+2. **Use correct IP address and port:**
+   - Correct: `http://192.168.4.1:5000`
+   - NOT: `http://192.168.4.1` (port 80 — nothing listens there)
+
+3. **Check wlan0 has correct IP:**
+   ```bash
+   ip addr show wlan0
+   # Should show: inet 192.168.4.1/24
+   ```
+
+4. **Verify hostapd and dnsmasq are running:**
+   ```bash
+   sudo systemctl status hostapd
+   sudo systemctl status dnsmasq
+   ```
+
+5. **Test from the Pi itself:**
+   ```bash
+   curl http://192.168.4.1:5000
+   # Should return HTML
+   ```
+
+#### DNS Resolution Failures
+
+**Symptoms:**
+- Captive portal doesn't redirect automatically
+- DNS lookups fail when connected to AP mode
+
+**Solutions:**
+
+1. **Check dnsmasq status:**
+   ```bash
+   sudo systemctl status dnsmasq
+   sudo journalctl -u dnsmasq -n 20
+   ```
+
+2. **Verify DNS configuration:**
+   ```bash
+   cat /etc/dnsmasq.conf | grep -v "^#" | grep -v "^$"
+   ```
+
+3. **Test DNS resolution:**
+   ```bash
+   nslookup captive.apple.com
+   # Should resolve to 192.168.4.1 when in AP mode
+   ```
+
+4. **Manual captive portal testing:**
+   - Try these URLs manually:
+     - `http://192.168.4.1:5000`
+     - `http://captive.apple.com`
+     - `http://connectivitycheck.gstatic.com/generate_204`
+
+#### Firewall Blocking Port 5000
+
+**Symptoms:**
+- Services running but cannot connect
+- Works from Pi but not from other devices
+
+**Solutions:**
+
+1. **Check UFW status:**
+   ```bash
+   sudo ufw status
+   ```
+
+2. **Allow port 5000:**
+   ```bash
+   sudo ufw allow 5000/tcp
+   ```
+
+3. **Check iptables:**
+   ```bash
+   sudo iptables -L -n
+   ```
+
+4. **Temporarily disable firewall to test:**
+   ```bash
+   sudo ufw disable
+   # Test if it works, then re-enable and add rule
+   sudo ufw enable
+   sudo ufw allow 5000/tcp
+   ```
+
+---
+
+### Plugin Issues
+
+#### Plugin Not Enabled
+
+**Symptoms:**
+- Plugin installed but doesn't appear in rotation
+- Plugin shows in web interface but is greyed out
+
+**Solutions:**
+
+1. **Enable in configuration:**
+   ```json
+   {
+     "plugin-id": {
+       "enabled": true,
+       ...
+     }
+   }
+   ```
+
+2. **Restart display:**
+   ```bash
+   sudo systemctl restart ledmatrix
+   ```
+
+3. **Verify in web interface:**
+   - Open the **Plugin Manager** tab
+   - Toggle the plugin switch to enable
+   - From **Overview**, click **Restart Display Service**
+
+#### Plugin Not Loading
+
+**Symptoms:**
+- Plugin enabled but not showing
+- Errors in logs about plugin
+
+**Solutions:**
+
+1. **Check plugin directory exists:**
+   ```bash
+   ls -ld plugins/plugin-id/
+   ```
+
+2. **Verify manifest.json:**
+   ```bash
+   cat plugins/plugin-id/manifest.json
+   # Verify all required fields present
+   ```
+
+3. **Check dependencies installed:**
+   ```bash
+   if [ -f plugins/plugin-id/requirements.txt ]; then
+     pip3 install --break-system-packages -r plugins/plugin-id/requirements.txt
+   fi
+   ```
+
+4. **Check logs for plugin errors:**
+   ```bash
+   sudo journalctl -u ledmatrix -f | grep plugin-id
+   ```
+
+5. **Test plugin import:**
+   ```bash
+   python3 -c "
+   import sys
+   sys.path.insert(0, 'plugins/plugin-id')
+   from manager import PluginClass
+   print('Plugin imports successfully')
+   "
+   ```
+
+#### Stale Cache Data
+
+**Symptoms:**
+- Plugin shows old data
+- Data doesn't update even after restarting
+- Clearing cache in web interface doesn't help
+
+**Solutions:**
+
+1. **Manual cache clearing:**
+   ```bash
+   # Remove plugin-specific cache
+   rm -rf cache/plugin-id*
+
+   # Or remove all cache
+   rm -rf cache/*
+
+   # Restart display
+   sudo systemctl restart ledmatrix
+   ```
+
+2. **Check cache permissions:**
+   ```bash
+   ls -ld cache/
+   sudo chown -R ledpi:ledpi cache/
+   ```
+
+---
+
+### Weather Plugin Specific Issues
+
+#### Missing or Invalid API Key
+
+**Symptoms:**
+- "No Weather Data" message on display
+- Logs show API authentication errors
+
+**Solutions:**
+
+1. **Get OpenWeatherMap API key:**
+   - Sign up at https://openweathermap.org/api
+   - Free tier: 1,000 calls/day, 60 calls/minute
+   - Copy your API key
+
+2. **Add to config_secrets.json (recommended):**
+   ```json
+   {
+     "openweathermap_api_key": "your-api-key-here"
+   }
+   ```
+
+3. **Or add to config.json:**
+   ```json
+   {
+     "ledmatrix-weather": {
+       "enabled": true,
+       "openweathermap_api_key": "your-api-key-here",
+       ...
+     }
+   }
+   ```
+
+4. **Secure the API key file:**
+   ```bash
+   chmod 640 config/config_secrets.json
+   ```
+
+5. **Restart display:**
+   ```bash
+   sudo systemctl restart ledmatrix
+   ```
+
+#### API Rate Limits Exceeded
+
+**Symptoms:**
+- Weather works initially then stops
+- Logs show HTTP 429 errors (Too Many Requests)
+- Error message: "Rate limit exceeded"
+
+**Solutions:**
+
+1. **Increase update interval:**
+   ```json
+   {
+     "ledmatrix-weather": {
+       "update_interval": 300,
+       ...
+     }
+   }
+   ```
+   **Note:** Minimum recommended: 300 seconds (5 minutes)
+
+2. **Check current rate limit usage:**
+   - OpenWeatherMap free tier: 1,000 calls/day, 60 calls/minute
+   - With 300s interval: 288 calls/day (well within limits)
+
+3. **Monitor API calls:**
+   ```bash
+   sudo journalctl -u ledmatrix -f | grep "openweathermap"
+   ```
+
+#### Invalid Location Configuration
+
+**Symptoms:**
+- "No Weather Data" message
+- Logs show location not found errors
+
+**Solutions:**
+
+1. **Use correct location format:**
+   ```json
+   {
+     "ledmatrix-weather": {
+       "city": "Tampa",
+       "state": "FL",
+       "country": "US"
+     }
+   }
+   ```
+
+2. **Use ISO country codes:**
+   - US = United States
+   - GB = United Kingdom
+   - CA = Canada
+   - etc.
+
+3. **Test API call manually:**
+   ```bash
+   API_KEY="your-key-here"
+   curl "http://api.openweathermap.org/data/2.5/weather?q=Tampa,FL,US&appid=${API_KEY}"
+   ```
+
+#### Network Connectivity to OpenWeatherMap
+
+**Symptoms:**
+- Other internet features work
+- Weather specifically fails
+- Connection timeout errors
+
+**Solutions:**
+
+1. **Test connectivity:**
+   ```bash
+   ping api.openweathermap.org
+   ```
+
+2. **Test DNS resolution:**
+   ```bash
+   nslookup api.openweathermap.org
+   ```
+
+3. **Test API endpoint:**
+   ```bash
+   curl -I https://api.openweathermap.org
+   # Should return HTTP 200 or 301
+   ```
+
+4. **Check firewall:**
+   ```bash
+   # Ensure HTTPS (443) is allowed for outbound connections
+   sudo ufw status
+   ```
+
+---
+
+## Diagnostic Commands Reference
+
+### Service Commands
+
+```bash
+# Check status
+sudo systemctl status ledmatrix
+sudo systemctl status ledmatrix-web
+sudo systemctl status ledmatrix-wifi-monitor
+
+# Start service
+sudo systemctl start <service-name>
+
+# Stop service
+sudo systemctl stop <service-name>
+
+# Restart service
+sudo systemctl restart <service-name>
+
+# Enable on boot
+sudo systemctl enable <service-name>
+
+# Disable on boot
+sudo systemctl disable <service-name>
+
+# View service file
+sudo systemctl cat <service-name>
+
+# Reload systemd after editing service files
+sudo systemctl daemon-reload
+```
+
+### Log Viewing Commands
+
+```bash
+# View recent logs (last 50 lines)
+sudo journalctl -u ledmatrix -n 50
+
+# Follow logs in real-time
+sudo journalctl -u ledmatrix -f
+
+# View logs from specific time
+sudo journalctl -u ledmatrix --since "1 hour ago"
+sudo journalctl -u ledmatrix --since "2024-01-01 10:00:00"
+
+# View logs until specific time
+sudo journalctl -u ledmatrix --until "2024-01-01 12:00:00"
+
+# Filter by priority (errors only)
+sudo journalctl -u ledmatrix -p err
+
+# Filter by priority (warnings and errors)
+sudo journalctl -u ledmatrix -p warning
+
+# Search logs for specific text
+sudo journalctl -u ledmatrix | grep "error"
+sudo journalctl -u ledmatrix | grep -i "plugin"
+
+# View logs for multiple services
+sudo journalctl -u ledmatrix -u ledmatrix-web -n 50
+
+# Export logs to file
+sudo journalctl -u ledmatrix > ledmatrix.log
+```
+
+### Network Testing Commands
+
+```bash
+# Test connectivity
+ping -c 4 8.8.8.8
+ping -c 4 api.openweathermap.org
+
+# Test DNS resolution
+nslookup api.openweathermap.org
+dig api.openweathermap.org
+
+# Test HTTP endpoint
+curl -I http://your-pi-ip:5000
+curl http://192.168.4.1:5000
+
+# Check listening ports
+sudo lsof -i :5000
+sudo netstat -tuln | grep 5000
+
+# Check network interfaces
+ip addr show
+nmcli device status
+```
+
+### File/Directory Verification
+
+```bash
+# Check file exists
+ls -l config/config.json
+ls -l plugins/plugin-id/manifest.json
+
+# Check directory structure
+ls -la web_interface/
+ls -la plugins/
+
+# Check file permissions
+ls -l config/config_secrets.json
+
+# Check file contents
+cat config/config.json | jq .
+cat config/wifi_config.json | grep auto_enable
+```
+
+### Python Import Testing
+
+```bash
+# Test core imports
+python3 -c "from src.config_manager import ConfigManager; print('OK')"
+python3 -c "from src.plugin_system.plugin_manager import PluginManager; print('OK')"
+python3 -c "from src.display_manager import DisplayManager; print('OK')"
+
+# Test web interface imports
+python3 -c "from web_interface.app import app; print('OK')"
+python3 -c "from web_interface.blueprints.api_v3 import api_v3; print('OK')"
+
+# Test WiFi manager
+python3 -c "from src.wifi_manager import WiFiManager; print('OK')"
+
+# Test plugin import
+python3 -c "
+import sys
+sys.path.insert(0, 'plugins/plugin-id')
+from manager import PluginClass
+print('Plugin imports OK')
+"
+```
+
+---
+
+## Service File Template
+
+If your systemd service file is corrupted or missing, use this template:
+
+```ini
+[Unit]
+Description=LEDMatrix Web Interface
+After=network.target
+
+[Service]
+Type=simple
+User=ledpi
+Group=ledpi
+WorkingDirectory=/home/ledpi/LEDMatrix
+Environment="PYTHONUNBUFFERED=1"
+ExecStart=/usr/bin/python3 /home/ledpi/LEDMatrix/web_interface/start.py
+Restart=on-failure
+RestartSec=5s
+StandardOutput=journal
+StandardError=journal
+SyslogIdentifier=ledmatrix-web
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Save to `/etc/systemd/system/ledmatrix-web.service` and run:
+
+```bash
+sudo systemctl daemon-reload
+sudo systemctl enable ledmatrix-web
+sudo systemctl start ledmatrix-web
+```
+
+---
+
+## Complete Diagnostic Script
+
+Run this script for comprehensive diagnostics:
+
+```bash
+#!/bin/bash
+
+echo "=== LEDMatrix Diagnostic Report ==="
+echo ""
+
+echo "1. Service Status:"
+systemctl status ledmatrix --no-pager -n 5
+systemctl status ledmatrix-web --no-pager -n 5
+echo ""
+
+echo "2. Recent Logs:"
+journalctl -u ledmatrix -n 20 --no-pager
+echo ""
+
+echo "3. Configuration:"
+cat config/config.json | grep -E "(web_display_autostart|enabled)"
+echo ""
+
+echo "4. Network Status:"
+ip addr show | grep -E "(wlan|eth|inet )"
+curl -s http://localhost:5000 > /dev/null && echo "Web interface: OK" || echo "Web interface: FAILED"
+echo ""
+
+echo "5. File Structure:"
+ls -la web_interface/ | head -10
+ls -la plugins/ | head -10
+echo ""
+
+echo "6. Python Imports:"
+python3 -c "from src.config_manager import ConfigManager" && echo "ConfigManager: OK" || echo "ConfigManager: FAILED"
+python3 -c "from web_interface.app import app" && echo "Web app: OK" || echo "Web app: FAILED"
+echo ""
+
+echo "=== End Diagnostic Report ==="
+```
+
+---
+
+## Success Indicators
+
+A properly functioning system should show:
+
+1. **Services Running:**
+   ```
+   ● ledmatrix.service - active (running)
+   ● ledmatrix-web.service - active (running)
+   ```
+
+2. **Web Interface Accessible:**
+   - Navigate to http://your-pi-ip:5000
+   - Page loads successfully
+   - Display preview visible
+
+3. **Logs Show Normal Operation:**
+   ```
+   INFO: Web interface started on port 5000
+   INFO: Loaded X plugins
+   INFO: Display rotation active
+   ```
+
+4. **Process Listening on Port:**
+   ```bash
+   $ sudo lsof -i :5000
+   COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
+   python3  1234 ledpi  3u   IPv4  12345      0t0  TCP *:5000 (LISTEN)
+   ```
+
+5. **Plugins Loading:**
+   - Logs show plugin initialization
+   - Plugins appear in web interface
+   - Display cycles through enabled plugins
+
+---
+
+## Emergency Recovery
+
+If the system is completely broken:
+
+### 1. Git Rollback
+
+```bash
+# View recent commits
+git log --oneline -10
+
+# Rollback to previous commit
+git reset --hard HEAD~1
+
+# Or rollback to specific commit
+git reset --hard <commit-hash>
+
+# Restart all services
+sudo systemctl restart ledmatrix
+sudo systemctl restart ledmatrix-web
+```
+
+### 2. Fresh Service Installation
+
+```bash
+# Reinstall WiFi monitor
+sudo ./scripts/install/install_wifi_monitor.sh
+
+# Recreate service files from templates
+sudo cp templates/ledmatrix.service /etc/systemd/system/
+sudo cp templates/ledmatrix-web.service /etc/systemd/system/
+
+# Reload and restart
+sudo systemctl daemon-reload
+sudo systemctl restart ledmatrix ledmatrix-web
+```
+
+### 3. Full System Reboot
+
+```bash
+# As a last resort
+sudo reboot
+```
+
+---
+
+## Related Documentation
+
+- [WEB_INTERFACE_GUIDE.md](WEB_INTERFACE_GUIDE.md) - Web interface usage
+- [WIFI_NETWORK_SETUP.md](WIFI_NETWORK_SETUP.md) - WiFi configuration
+- [PLUGIN_STORE_GUIDE.md](PLUGIN_STORE_GUIDE.md) - Plugin installation
+- [REST_API_REFERENCE.md](REST_API_REFERENCE.md) - API documentation

docs/WEB_INTERFACE_GUIDE.md

@@ -0,0 +1,415 @@
+# Web Interface Guide
+
+## Overview
+
+The LEDMatrix web interface provides a complete control panel for managing your LED matrix display. Access all features through a modern, responsive web interface that works on desktop, tablet, and mobile devices.
+
+---
+
+## Quick Start
+
+### Accessing the Interface
+
+1. Find your Raspberry Pi's IP address:
+   ```bash
+   hostname -I
+   ```
+
+2. Open a web browser and navigate to:
+   ```
+   http://your-pi-ip:5000
+   ```
+
+3. The interface will load with the Overview tab displaying system stats and a live display preview.
+
+**Note:** If the interface doesn't load, verify the web service is running:
+```bash
+sudo systemctl status ledmatrix-web
+```
+
+---
+
+## Navigation
+
+The interface uses a two-row tab layout. The system tabs are always
+present:
+
+- **Overview** — System stats, quick actions, live display preview
+- **General** — Timezone, location, plugin-system settings
+- **WiFi** — Network selection and AP-mode setup
+- **Schedule** — Power and dim schedules
+- **Display** — Matrix hardware configuration (rows, cols, hardware
+  mapping, GPIO slowdown, brightness, PWM)
+- **Config Editor** — Raw `config.json` editor with validation
+- **Fonts** — Upload and manage fonts
+- **Logs** — Real-time log streaming
+- **Cache** — Cached data inspection and cleanup
+- **Operation History** — Recent service operations
+
+A second nav row holds plugin tabs:
+
+- **Plugin Manager** — browse the **Plugin Store** section, install
+  plugins from GitHub, enable/disable installed plugins
+- **<plugin-id>** — one tab per installed plugin for its own
+  configuration form (auto-generated from the plugin's
+  `config_schema.json`)
+
+---
+
+## Features and Usage
+
+### Overview Tab
+
+The Overview tab provides at-a-glance information and quick actions:
+
+**System Stats:**
+- CPU usage and temperature
+- Memory usage
+- Disk usage
+- Network status
+
+**Quick Actions** (verified in `web_interface/templates/v3/partials/overview.html`):
+- **Start Display** / **Stop Display** — control the display service
+- **Restart Display Service** — apply configuration changes
+- **Restart Web Service** — restart the web UI itself
+- **Update Code** — `git pull` the latest version (stashes local changes)
+- **Reboot System** / **Shutdown System** — confirm-gated power controls
+
+**Display Preview:**
+- Live preview of what's currently shown on the LED matrix
+- Updates in real-time
+- Useful for remote monitoring
+
+### General Tab
+
+Configure basic system settings:
+
+- **Timezone** — used by all time/date displays
+- **Location** — city/state/country for weather and other location-aware
+  plugins
+- **Plugin System Settings** — including the `plugins_directory` (default
+  `plugin-repos/`) used by the plugin loader
+- **Autostart** options for the display service
+
+Click **Save** to write changes to `config/config.json`. Most changes
+require a display service restart from **Overview**.
+
+### Display Tab
+
+Configure your LED matrix hardware:
+
+**Matrix configuration:**
+- `rows` — LED rows (typically 32 or 64)
+- `cols` — LED columns (typically 64 or 96)
+- `chain_length` — number of horizontally chained panels
+- `parallel` — number of parallel chains
+- `hardware_mapping` — `adafruit-hat-pwm` (with PWM jumper mod),
+  `adafruit-hat` (without), `regular`, or `regular-pi1`
+- `gpio_slowdown` — must match your Pi model (3 for Pi 3, 4 for Pi 4, etc.)
+- `brightness` — 0–100%
+- `pwm_bits`, `pwm_lsb_nanoseconds`, `pwm_dither_bits` — PWM tuning
+- Dynamic Duration — global cap for plugins that extend their display
+  time based on content
+
+Changes require **Restart Display Service** from the Overview tab.
+
+### Plugin Manager Tab
+
+The Plugin Manager has three main sections:
+
+1. **Installed Plugins** — toggle installed plugins on/off, see version
+   info. Each installed plugin also gets its own tab in the second nav
+   row for its configuration form.
+2. **Plugin Store** — browse plugins from the official
+   `ledmatrix-plugins` registry. Click **Install** to fetch and
+   install. Filter by category and search.
+3. **Install from GitHub** — install third-party plugins by pasting a
+   GitHub repository URL. **Install Single Plugin** for a single-plugin
+   repo, **Load Registry** for a multi-plugin monorepo.
+
+When a plugin is installed and enabled:
+- A new tab for that plugin appears in the second nav row
+- Open the tab to edit its config (auto-generated form from
+  `config_schema.json`)
+- The tab also exposes **Run On-Demand** / **Stop On-Demand** controls
+  to render that plugin immediately, even if it's disabled in the
+  rotation
+
+### Per-plugin Configuration Tabs
+
+Each installed plugin has its own tab in the second nav row. The form
+fields are auto-generated from the plugin's `config_schema.json`, so
+options always match the plugin's current code.
+
+To temporarily run a plugin outside the normal rotation, use the
+**Run On-Demand** / **Stop On-Demand** buttons inside its tab. This
+works even when the plugin is disabled.
+
+### Fonts Tab
+
+Manage fonts for your display:
+
+**Upload Fonts:**
+- Drag and drop font files (.ttf, .otf, .bdf)
+- Upload multiple files at once
+- Progress indicator shows upload status
+
+**Font Catalog:**
+- View all available fonts
+- See font previews
+- Check font sizes and styles
+
+**Plugin Font Overrides:**
+- Set custom fonts for specific plugins
+- Override default font choices
+- Preview font changes
+
+**Delete Fonts:**
+- Remove unused fonts
+- Free up disk space
+
+### Logs Tab
+
+View real-time system logs:
+
+**Log Viewer:**
+- Streaming logs from the display service
+- Auto-scroll to latest entries
+- Timestamps for each log entry
+
+**Filtering:**
+- Filter by log level (INFO, WARNING, ERROR)
+- Search for specific text
+- Filter by plugin or component
+
+**Actions:**
+- **Clear**: Clear the current view
+- **Download**: Download logs for offline analysis
+- **Pause**: Pause auto-scrolling
+
+---
+
+## Common Tasks
+
+### Changing Display Brightness
+
+1. Open the **Display** tab
+2. Adjust the **Brightness** slider (0–100)
+3. Click **Save**
+4. Click **Restart Display Service** on the **Overview** tab
+
+### Installing a New Plugin
+
+1. Open the **Plugin Manager** tab
+2. Scroll to the **Plugin Store** section and browse or search
+3. Click **Install** next to the plugin
+4. Toggle the plugin on in **Installed Plugins**
+5. Click **Restart Display Service** on **Overview**
+
+### Configuring a Plugin
+
+1. Open the plugin's tab in the second nav row (each installed plugin
+   has its own tab)
+2. Edit the auto-generated form
+3. Click **Save**
+4. Restart the display service from **Overview**
+
+### Setting Favorite Sports Teams
+
+Sports favorites live in the relevant plugin's tab — there is no
+separate "Sports Configuration" tab. For example:
+
+1. Install **Hockey Scoreboard** from **Plugin Manager → Plugin Store**
+2. Open the **Hockey Scoreboard** tab in the second nav row
+3. Add your favorites under `favorite_teams.<league>` (e.g.
+   `favorite_teams.nhl`)
+4. Click **Save** and restart the display service
+
+### Troubleshooting Display Issues
+
+1. Navigate to the **Logs** tab
+2. Look for ERROR or WARNING messages
+3. Filter by the problematic plugin or component
+4. Check the error message for clues
+5. See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for common solutions
+
+---
+
+## Real-Time Features
+
+The web interface uses Server-Sent Events (SSE) for real-time updates:
+
+**Live Updates:**
+- System stats refresh automatically every few seconds
+- Display preview updates in real-time
+- Logs stream continuously
+- No page refresh required
+
+**Performance:**
+- Minimal bandwidth usage
+- Server-side rendering for fast load times
+- Progressive enhancement - works without JavaScript
+
+---
+
+## Mobile Access
+
+The interface is fully responsive and works on mobile devices:
+
+**Mobile Features:**
+- Touch-friendly interface
+- Responsive layout adapts to screen size
+- All features available on mobile
+
+**Tips for Mobile:**
+- Use landscape mode for better visibility
+- Pinch to zoom on display preview
+
+---
+
+## Keyboard Shortcuts
+
+Use keyboard shortcuts for faster navigation:
+
+- **Tab**: Navigate between form fields
+- **Enter**: Submit forms
+- **Esc**: Close modals
+- **Ctrl+F**: Search in logs
+
+---
+
+## API Access
+
+The web interface is built on a REST API that you can access programmatically:
+
+**API Base URL:**
+```
+http://your-pi-ip:5000/api/v3
+```
+
+The API blueprint mounts at `/api/v3` (see
+`web_interface/app.py:144`). All endpoints below are relative to that
+base.
+
+**Common Endpoints:**
+- `GET /api/v3/config/main` — Get main configuration
+- `POST /api/v3/config/main` — Update main configuration
+- `GET /api/v3/system/status` — Get system status
+- `POST /api/v3/system/action` — Control display (start/stop/restart, reboot, etc.)
+- `GET /api/v3/plugins/installed` — List installed plugins
+- `POST /api/v3/plugins/install` — Install a plugin from the store
+- `POST /api/v3/plugins/install-from-url` — Install a plugin from a GitHub URL
+
+**Note:** See [REST_API_REFERENCE.md](REST_API_REFERENCE.md) for complete API documentation.
+
+---
+
+## Troubleshooting
+
+### Interface Won't Load
+
+**Problem:** Browser shows "Unable to connect" or "Connection refused"
+
+**Solutions:**
+1. Verify the web service is running:
+   ```bash
+   sudo systemctl status ledmatrix-web
+   ```
+
+2. Start the service if stopped:
+   ```bash
+   sudo systemctl start ledmatrix-web
+   ```
+
+3. Check that port 5000 is not blocked by firewall
+4. Verify the Pi's IP address is correct
+
+### Changes Not Applying
+
+**Problem:** Configuration changes don't take effect
+
+**Solutions:**
+1. Ensure you clicked "Save Configuration"
+2. Restart the display service for changes to apply:
+   ```bash
+   sudo systemctl restart ledmatrix
+   ```
+3. Check logs for error messages
+
+### Display Preview Not Updating
+
+**Problem:** Display preview shows old content or doesn't update
+
+**Solutions:**
+1. Refresh the browser page (F5)
+2. Check that the display service is running
+3. Verify SSE streams are working (check browser console)
+
+### Plugin Configuration Not Saving
+
+**Problem:** Plugin settings revert after restart
+
+**Solutions:**
+1. Check file permissions on `config/config.json`:
+   ```bash
+   ls -l config/config.json
+   ```
+2. Ensure the web service has write permissions
+3. Check logs for permission errors
+
+---
+
+## Security Considerations
+
+**Network Access:**
+- The interface is accessible to anyone on your local network
+- No authentication is currently implemented
+- Recommended for trusted networks only
+
+**Best Practices:**
+1. Run on a private network (not exposed to internet)
+2. Use a firewall to restrict access if needed
+3. Consider VPN access for remote control
+4. Keep the system updated
+
+---
+
+## Technical Details
+
+### Architecture
+
+The web interface uses modern web technologies:
+
+- **Backend:** Flask with Blueprint-based modular design
+- **Frontend:** HTMX for dynamic content, Alpine.js for reactive components
+- **Styling:** Tailwind CSS for responsive design
+- **Real-Time:** Server-Sent Events (SSE) for live updates
+
+### File Locations
+
+**Configuration:**
+- Main config: `/config/config.json`
+- Secrets: `/config/config_secrets.json`
+- WiFi config: `/config/wifi_config.json`
+
+**Logs:**
+- Display service: `sudo journalctl -u ledmatrix -f`
+- Web service: `sudo journalctl -u ledmatrix-web -f`
+
+**Plugins:**
+- Plugin directory: configurable via
+  `plugin_system.plugins_directory` in `config.json` (default
+  `plugin-repos/`). Main plugin discovery only scans this directory;
+  the Plugin Store install flow and the schema loader additionally
+  probe `plugins/` so dev symlinks created by
+  `scripts/dev/dev_plugin_setup.sh` keep working.
+- Plugin config: `/config/config.json` (per-plugin sections)
+
+---
+
+## Related Documentation
+
+- [PLUGIN_STORE_GUIDE.md](PLUGIN_STORE_GUIDE.md) - Installing and managing plugins
+- [REST_API_REFERENCE.md](REST_API_REFERENCE.md) - Complete REST API documentation
+- [TROUBLESHOOTING.md](TROUBLESHOOTING.md) - Troubleshooting common issues
+- [FONT_MANAGER.md](FONT_MANAGER.md) - Font management details

docs/WIFI_NETWORK_SETUP.md

@@ -0,0 +1,636 @@
+# WiFi Network Setup Guide
+
+## Overview
+
+The LEDMatrix WiFi system provides automatic network configuration with intelligent failover to Access Point (AP) mode. When your Raspberry Pi loses network connectivity, it automatically creates a WiFi access point for easy configuration—ensuring you can always connect to your device.
+
+### Key Features
+
+- **Automatic AP Mode**: Creates a WiFi access point when network connection is lost
+- **Intelligent Failover**: Only activates after a grace period to prevent false positives
+- **Dual Connectivity**: Supports both WiFi and Ethernet with automatic priority management
+- **Web Interface**: Configure WiFi through an easy-to-use web interface
+- **Network Scanning**: Scan and connect to available WiFi networks
+- **Secure Storage**: WiFi credentials stored securely
+
+---
+
+## Quick Start
+
+### Accessing WiFi Setup
+
+**If not connected to WiFi:**
+1. Wait 90 seconds after boot (AP mode activation grace period)
+2. Connect to WiFi network **LEDMatrix-Setup** (default password
+   `ledmatrix123` — change it in `config/wifi_config.json` if you want
+   an open network or a different password)
+3. Open browser to: `http://192.168.4.1:5000`
+4. Open the **WiFi** tab
+5. Scan, select your network, and connect
+
+**If already connected:**
+1. Open browser to: `http://your-pi-ip:5000`
+2. Navigate to the WiFi tab
+3. Configure as needed
+
+---
+
+## Installation
+
+### Prerequisites
+
+The following packages are required:
+- **hostapd** - Access point software
+- **dnsmasq** - DHCP server for AP mode
+- **NetworkManager** - WiFi management
+
+### Install WiFi Monitor Service
+
+```bash
+cd /home/ledpi/LEDMatrix
+sudo ./scripts/install/install_wifi_monitor.sh
+```
+
+This script will:
+- Check for required packages and offer to install them
+- Create the systemd service file
+- Enable and start the WiFi monitor service
+- Configure the service to start on boot
+
+### Verify Installation
+
+```bash
+# Check service status
+sudo systemctl status ledmatrix-wifi-monitor
+
+# Run verification script
+./scripts/verify_wifi_setup.sh
+```
+
+---
+
+## Configuration
+
+### Configuration File
+
+WiFi settings are stored in `config/wifi_config.json`:
+
+```json
+{
+  "ap_ssid": "LEDMatrix-Setup",
+  "ap_password": "ledmatrix123",
+  "ap_channel": 7,
+  "auto_enable_ap_mode": true,
+  "saved_networks": [
+    {
+      "ssid": "YourNetwork",
+      "password": "your-password",
+      "saved_at": 1234567890.0
+    }
+  ]
+}
+```
+
+### Configuration Options
+
+| Setting | Default | Description |
+|---------|---------|-------------|
+| `ap_ssid` | `LEDMatrix-Setup` | Network name broadcast in AP mode |
+| `ap_password` | `ledmatrix123` | AP password. Set to `""` to make the network open (no password). |
+| `ap_channel` | `7` | WiFi channel (1, 6, or 11 are non-overlapping) |
+| `auto_enable_ap_mode` | `true` | Automatically enable AP mode when both WiFi and Ethernet are disconnected |
+| `saved_networks` | `[]` | Array of saved WiFi credentials |
+
+### Auto-Enable AP Mode Behavior
+
+**When enabled (`true` - recommended):**
+- AP mode activates automatically after 90-second grace period
+- Only when both WiFi AND Ethernet are disconnected
+- Automatically disables when either WiFi or Ethernet connects
+- Best for portable devices or unreliable network environments
+
+**When disabled (`false`):**
+- AP mode must be manually enabled through web interface
+- Prevents unnecessary AP activation
+- Best for devices with stable network connections
+
+---
+
+## Using WiFi Setup
+
+### Connecting to a WiFi Network
+
+**Via Web Interface:**
+1. Navigate to the **WiFi** tab
+2. Click **Scan** to search for networks
+3. Select a network from the dropdown (or enter SSID manually)
+4. Enter the WiFi password (leave empty for open networks)
+5. Click **Connect**
+6. System will attempt connection
+7. AP mode automatically disables once connected
+
+**Via API:**
+```bash
+# Scan for networks
+curl "http://your-pi-ip:5000/api/v3/wifi/scan"
+
+# Connect to network
+curl -X POST http://your-pi-ip:5000/api/v3/wifi/connect \
+  -H "Content-Type: application/json" \
+  -d '{"ssid": "YourNetwork", "password": "your-password"}'
+```
+
+### Manual AP Mode Control
+
+**Via Web Interface:**
+- **Enable AP Mode**: Click "Enable AP Mode" button (only when WiFi/Ethernet disconnected)
+- **Disable AP Mode**: Click "Disable AP Mode" button (when AP is active)
+
+**Via API:**
+```bash
+# Enable AP mode
+curl -X POST http://your-pi-ip:5000/api/v3/wifi/ap/enable
+
+# Disable AP mode
+curl -X POST http://your-pi-ip:5000/api/v3/wifi/ap/disable
+```
+
+**Note:** Manual enable still requires both WiFi and Ethernet to be disconnected.
+
+---
+
+## Understanding AP Mode Failover
+
+### How the Grace Period Works
+
+The system uses a **grace period mechanism** to prevent false positives from temporary network hiccups:
+
+```
+Check Interval: 30 seconds (default)
+Required Checks: 3 consecutive
+Grace Period: 90 seconds total
+```
+
+**Timeline Example:**
+```
+Time 0s:   WiFi disconnects
+Time 30s:  Check 1 - Disconnected (counter = 1)
+Time 60s:  Check 2 - Disconnected (counter = 2)
+Time 90s:  Check 3 - Disconnected (counter = 3) → AP MODE ENABLED
+```
+
+If WiFi or Ethernet reconnects at any point, the counter resets to 0.
+
+### Why Grace Period is Important
+
+Without a grace period, AP mode would activate during:
+- Brief network hiccups
+- Router reboots
+- Temporary signal interference
+- NetworkManager reconnection attempts
+
+The 90-second grace period ensures AP mode only activates during **sustained disconnection**.
+
+### Connection Priority
+
+The system checks connections in this order:
+1. **WiFi Connection** (highest priority)
+2. **Ethernet Connection** (fallback)
+3. **AP Mode** (last resort - only when both WiFi and Ethernet disconnected)
+
+### Behavior Summary
+
+| WiFi Status | Ethernet Status | Auto-Enable | AP Mode Behavior |
+|-------------|-----------------|-------------|------------------|
+| Any | Any | `false` | Manual enable only |
+| Connected | Any | `true` | Disabled |
+| Disconnected | Connected | `true` | Disabled (Ethernet available) |
+| Disconnected | Disconnected | `true` | Auto-enabled after 90s |
+
+---
+
+## Access Point Configuration
+
+### AP Mode Settings
+
+- **SSID**: `LEDMatrix-Setup` (configurable via `ap_ssid`)
+- **Network**: WPA2, default password `ledmatrix123` (configurable via
+  `ap_password` — set to `""` for an open network)
+- **IP Address**: 192.168.4.1
+- **DHCP Range**: 192.168.4.2 – 192.168.4.20
+- **Channel**: 7 (configurable via `ap_channel`)
+
+### Accessing Services in AP Mode
+
+When AP mode is active:
+- Web Interface: `http://192.168.4.1:5000`
+- SSH: `ssh ledpi@192.168.4.1`
+- Captive portal may automatically redirect browsers
+
+---
+
+## Best Practices
+
+### Security Recommendations
+
+**1. Change AP Password (Optional):**
+```json
+{
+  "ap_password": "your-strong-password"
+}
+```
+
+**Note:** The default password is `ledmatrix123` for easy initial
+setup. Change it for any deployment in a public area, or set
+`ap_password` to `""` if you specifically want an open network.
+
+**2. Use Non-Overlapping WiFi Channels:**
+- Channels 1, 6, 11 are non-overlapping (2.4GHz)
+- Choose a channel that doesn't conflict with your primary network
+- Example: If primary uses channel 1, use channel 11 for AP mode
+
+**3. Secure WiFi Credentials:**
+```bash
+sudo chmod 600 config/wifi_config.json
+```
+
+### Network Configuration Tips
+
+**Save Multiple Networks:**
+```json
+{
+  "saved_networks": [
+    {
+      "ssid": "Home-Network",
+      "password": "home-password"
+    },
+    {
+      "ssid": "Office-Network",
+      "password": "office-password"
+    }
+  ]
+}
+```
+
+**Adjust Check Interval:**
+
+Edit the systemd service file to change grace period:
+```bash
+sudo systemctl edit ledmatrix-wifi-monitor
+```
+
+Add:
+```ini
+[Service]
+ExecStart=
+ExecStart=/usr/bin/python3 /path/to/LEDMatrix/scripts/utils/wifi_monitor_daemon.py --interval 20
+```
+
+**Note:** Interval affects grace period:
+- 20-second interval = 60-second grace period (3 × 20)
+- 30-second interval = 90-second grace period (3 × 30) ← Default
+- 60-second interval = 180-second grace period (3 × 60)
+
+---
+
+## Configuration Scenarios
+
+### Scenario 1: Portable Device with Auto-Failover (Recommended)
+
+**Use Case:** Device may lose WiFi connection
+
+**Configuration:**
+```json
+{
+  "auto_enable_ap_mode": true
+}
+```
+
+**Behavior:**
+- AP mode activates automatically after 90 seconds of disconnection
+- Always provides a way to connect
+- Best for devices that move or have unreliable WiFi
+
+### Scenario 2: Stable Network Connection
+
+**Use Case:** Ethernet or reliable WiFi connection
+
+**Configuration:**
+```json
+{
+  "auto_enable_ap_mode": false
+}
+```
+
+**Behavior:**
+- AP mode must be manually enabled
+- Prevents unnecessary activation
+- Best for stationary devices with stable connections
+
+### Scenario 3: Ethernet Primary with WiFi Backup
+
+**Use Case:** Primary Ethernet, WiFi as backup
+
+**Configuration:**
+```json
+{
+  "auto_enable_ap_mode": true
+}
+```
+
+**Behavior:**
+- Ethernet connection prevents AP mode activation
+- If Ethernet disconnects, WiFi is attempted
+- If both disconnect, AP mode activates after grace period
+- Best for devices with both Ethernet and WiFi
+
+---
+
+## Troubleshooting
+
+### AP Mode Not Activating
+
+**Check 1: Auto-Enable Setting**
+```bash
+cat config/wifi_config.json | grep auto_enable_ap_mode
+```
+Should show `"auto_enable_ap_mode": true`
+
+**Check 2: Service Status**
+```bash
+sudo systemctl status ledmatrix-wifi-monitor
+```
+Service should be `active (running)`
+
+**Check 3: Grace Period**
+- Wait at least 90 seconds after disconnection
+- Check logs: `sudo journalctl -u ledmatrix-wifi-monitor -f`
+
+**Check 4: Ethernet Connection**
+- If Ethernet is connected, AP mode won't activate
+- Verify: `nmcli device status`
+- Disconnect Ethernet to test AP mode
+
+**Check 5: Required Packages**
+```bash
+# Verify hostapd is installed
+which hostapd
+
+# Verify dnsmasq is installed
+which dnsmasq
+```
+
+### Cannot Access AP Mode
+
+**Check 1: AP Mode Active**
+```bash
+sudo systemctl status hostapd
+sudo systemctl status dnsmasq
+```
+Both should be running
+
+**Check 2: Network Interface**
+```bash
+ip addr show wlan0
+```
+Should show IP `192.168.4.1`
+
+**Check 3: WiFi Interface Available**
+```bash
+ip link show wlan0
+```
+Interface should exist
+
+**Check 4: Try Manual Enable**
+- Use web interface: WiFi tab → Enable AP Mode
+- Or via API: `curl -X POST http://localhost:5000/api/v3/wifi/ap/enable`
+
+### Cannot Connect to WiFi Network
+
+**Check 1: Verify Credentials**
+- Ensure SSID and password are correct
+- Check for hidden networks (manual SSID entry required)
+
+**Check 2: Check Logs**
+```bash
+# WiFi monitor logs
+sudo journalctl -u ledmatrix-wifi-monitor -f
+
+# NetworkManager logs
+sudo journalctl -u NetworkManager -n 50
+```
+
+**Check 3: Network Compatibility**
+- Verify network is 2.4GHz (5GHz may not be supported on all Pi models)
+- Check if network requires special authentication
+
+### AP Mode Not Disabling After WiFi Connect
+
+**Check 1: WiFi Connection Status**
+```bash
+nmcli device status
+```
+
+**Check 2: Manually Disable**
+- Use web interface: WiFi tab → Disable AP Mode
+- Or restart service: `sudo systemctl restart ledmatrix-wifi-monitor`
+
+**Check 3: Check Logs**
+```bash
+sudo journalctl -u ledmatrix-wifi-monitor -n 50
+```
+
+### AP Mode Activating Unexpectedly
+
+**Check 1: Network Stability**
+- Verify WiFi connection is stable
+- Check router status
+- Check signal strength
+
+**Check 2: Disable Auto-Enable**
+```bash
+nano config/wifi_config.json
+# Change: "auto_enable_ap_mode": false
+sudo systemctl restart ledmatrix-wifi-monitor
+```
+
+**Check 3: Increase Grace Period**
+- Edit service file to increase check interval
+- Longer interval = longer grace period
+- See "Best Practices" section above
+
+---
+
+## Monitoring and Diagnostics
+
+### Check WiFi Status
+
+**Via Python:**
+```python
+from src.wifi_manager import WiFiManager
+
+wm = WiFiManager()
+status = wm.get_wifi_status()
+
+print(f'Connected: {status.connected}')
+print(f'SSID: {status.ssid}')
+print(f'IP Address: {status.ip_address}')
+print(f'AP Mode Active: {status.ap_mode_active}')
+print(f'Auto-Enable: {wm.config.get("auto_enable_ap_mode", False)}')
+```
+
+**Via NetworkManager:**
+```bash
+# View device status
+nmcli device status
+
+# View connections
+nmcli connection show
+
+# View available WiFi networks
+nmcli device wifi list
+```
+
+### View Service Logs
+
+```bash
+# Real-time logs
+sudo journalctl -u ledmatrix-wifi-monitor -f
+
+# Recent logs (last 50 lines)
+sudo journalctl -u ledmatrix-wifi-monitor -n 50
+
+# Logs from specific time
+sudo journalctl -u ledmatrix-wifi-monitor --since "1 hour ago"
+```
+
+### Run Verification Script
+
+```bash
+cd /home/ledpi/LEDMatrix
+./scripts/verify_wifi_setup.sh
+```
+
+Checks:
+- Required packages installed
+- WiFi monitor service running
+- Configuration files valid
+- WiFi interface available
+- Current connection status
+- AP mode status
+
+---
+
+## Service Management
+
+### Useful Commands
+
+```bash
+# Check service status
+sudo systemctl status ledmatrix-wifi-monitor
+
+# Start the service
+sudo systemctl start ledmatrix-wifi-monitor
+
+# Stop the service
+sudo systemctl stop ledmatrix-wifi-monitor
+
+# Restart the service
+sudo systemctl restart ledmatrix-wifi-monitor
+
+# View logs
+sudo journalctl -u ledmatrix-wifi-monitor -f
+
+# Disable service from starting on boot
+sudo systemctl disable ledmatrix-wifi-monitor
+
+# Enable service to start on boot
+sudo systemctl enable ledmatrix-wifi-monitor
+```
+
+---
+
+## API Reference
+
+The WiFi setup feature exposes the following API endpoints:
+
+| Method | Endpoint | Description |
+|--------|----------|-------------|
+| GET | `/api/v3/wifi/status` | Get current WiFi connection status |
+| GET | `/api/v3/wifi/scan` | Scan for available WiFi networks |
+| POST | `/api/v3/wifi/connect` | Connect to a WiFi network |
+| POST | `/api/v3/wifi/ap/enable` | Enable access point mode |
+| POST | `/api/v3/wifi/ap/disable` | Disable access point mode |
+| GET | `/api/v3/wifi/ap/auto-enable` | Get auto-enable setting |
+| POST | `/api/v3/wifi/ap/auto-enable` | Set auto-enable setting |
+
+### Example Usage
+
+```bash
+# Get WiFi status
+curl "http://your-pi-ip:5000/api/v3/wifi/status"
+
+# Scan for networks
+curl "http://your-pi-ip:5000/api/v3/wifi/scan"
+
+# Connect to network
+curl -X POST http://your-pi-ip:5000/api/v3/wifi/connect \
+  -H "Content-Type: application/json" \
+  -d '{"ssid": "MyNetwork", "password": "mypassword"}'
+
+# Enable AP mode
+curl -X POST http://your-pi-ip:5000/api/v3/wifi/ap/enable
+
+# Check auto-enable setting
+curl "http://your-pi-ip:5000/api/v3/wifi/ap/auto-enable"
+
+# Set auto-enable
+curl -X POST http://your-pi-ip:5000/api/v3/wifi/ap/auto-enable \
+  -H "Content-Type: application/json" \
+  -d '{"auto_enable_ap_mode": true}'
+```
+
+---
+
+## Technical Details
+
+### WiFi Monitor Daemon
+
+The WiFi monitor daemon (`wifi_monitor_daemon.py`) runs as a background service that:
+
+1. Checks WiFi and Ethernet connection status every 30 seconds (configurable)
+2. Maintains disconnected check counter for grace period
+3. Automatically enables AP mode when:
+   - `auto_enable_ap_mode` is enabled AND
+   - Both WiFi and Ethernet disconnected AND
+   - Grace period elapsed (3 consecutive checks)
+4. Automatically disables AP mode when WiFi or Ethernet connects
+5. Logs all state changes
+
+### WiFi Detection Methods
+
+The WiFi manager tries multiple methods:
+
+1. **NetworkManager (nmcli)** - Preferred method
+2. **iwconfig** - Fallback for systems without NetworkManager
+
+### Network Scanning Methods
+
+1. **nmcli** - Fast, preferred method
+2. **iwlist** - Fallback for older systems
+
+### Access Point Implementation
+
+- Uses `hostapd` for WiFi access point functionality
+- Uses `dnsmasq` for DHCP and DNS services
+- Configures wlan0 interface with IP 192.168.4.1
+- Provides DHCP range: 192.168.4.2-20
+- Captive portal with DNS redirection
+
+---
+
+## Related Documentation
+
+- [WEB_INTERFACE_GUIDE.md](WEB_INTERFACE_GUIDE.md) - Using the web interface
+- [TROUBLESHOOTING.md](TROUBLESHOOTING.md) - General troubleshooting
+- [GETTING_STARTED.md](GETTING_STARTED.md) - Initial setup guide