* chore(scripts): delete unreferenced helper scripts None of these is referenced by an installer, systemd unit, CI workflow, test, the web UI or src/: - utils/cleanup_venv.sh removes venv_web_v2, which nothing creates - utils/clear_python_cache.sh hardcodes ~/LEDMatrix and a .webassets-cache nothing uses - install/migrate_config.sh only copies the template, which the installer and ConfigManager already do - install/debug_install.sh, debug/debug_web_manual.py - diagnose_web_ui.sh and verify_web_ui.sh overlap diagnose_web_interface.sh, which the docs point to - fix_internet_connectivity.sh is iptables-only (stale on nftables) - diagnose_plugin_permissions.sh, dev/validate_python.py - download_nba_logos.py + README_NBA_LOGOS.md: logo_downloader fetches logos on demand - setup_plugin_repos.py linked into the production plugin-repos/ dir; the dev workflow is scripts/dev/dev_plugin_setup.sh, and MULTI_ROOT_WORKSPACE_SETUP.md now uses it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(config): drop unused plugin_system flags and a dead unit comment - config.template.json: remove plugin_system.auto_discover, auto_load_enabled and development_mode. Nothing reads them; the web UI only stores them when a client sends them. ConfigManager's migration only adds template keys, so existing configs keep theirs unchanged. - config.template.json: re-indent vegas_scroll's live_* keys. - systemd/ledmatrix.service: remove the comment documenting LEDMATRIX_ON_DEMAND_PLUGIN / on_demand_env.conf; nothing reads either. - CONFIG_REFERENCE.md: say the legacy keys are no longer in the template. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: delete docs/archive and PLUGIN_IMPLEMENTATION_SUMMARY.md - docs/archive/: superseded guides; the repository history keeps them and no live doc links into the directory. The one open document in it, WEB_UI_AUDIT_2026-09.md, moves to docs/audits/ and is linked from the docs index. - PLUGIN_IMPLEMENTATION_SUMMARY.md invented usage statistics, called v2.0.0 current, listed shipped auto-updates as future work and documented a BasePlugin.get_config() that does not exist. - docs/README.md: drop both, and stop telling contributors to archive obsolete pages instead of deleting them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(plugin-api): fix extra_small_font size, cache metric key and scroll pacing example - PLUGIN_API_REFERENCE: extra_small_font loads at 7, not 6 (crisp_size snaps it, src/display_manager.py); get_cache_metrics() returns cache_hit_rate, not hit_rate (src/cache/cache_metrics.py). - ADVANCED_PLUGIN_DEVELOPMENT: the basic scrolling example slept in a loop and never passed frame_hold; use ScrollHelper + scroll_config.configure() and set_scrolling_state(True, frame_hold=...) as PLUGIN_API_REFERENCE does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(plugin-config): match the config tab, icon and web-action docs to the code - PLUGIN_CONFIG_QUICK_START / PLUGIN_CONFIGURATION_TABS / PLUGIN_CONFIGURATION_GUIDE: there is no "Reset to Defaults" button (the tab has Refresh, Update, Uninstall, Save Configuration); plugin config hot-reloads (ConfigService + on_config_change), so no restart; the schema is found by the fixed name config_schema.json, not a manifest config_schema field; the tab row is "Plugin Manager", not "Plugins"; forms are server-rendered from /v3/partials/plugin-config/<id>; the duration hook is get_display_duration()/display_duration; a class_name mismatch raises PluginError; the store requires id, name, class_name and display_modes (not version); plugin_system.debug/log_level do not exist (use run.py -d / LEDMATRIX_DEBUG). Drop "future" features that shipped. - PLUGIN_CONFIG_CORE_PROPERTIES: list all of CORE_PLUGIN_PROPERTIES, including skin, skin_options and the vegas_* tuning keys. - PLUGIN_CUSTOM_ICONS: icon is only a Font Awesome class (fallback fa-puzzle-piece); emoji/URL icons and getPluginIcon() never existed in v3. Note that /api/v3/plugins/installed currently omits icon. - PLUGIN_WEB_UI_ACTIONS (+ example JSON): success_message, error_message and step1_message are never read. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(store): describe the monorepo registry and the store UI as they are - PLUGIN_STORE_GUIDE: the Plugin Store is a section of the Plugin Manager tab; URL installs are "Install from GitHub" -> "Install Single Plugin"; bulk update exists (Check & Update All) plus opt-in weekly auto-update; PluginStoreManager() defaults to plugins/, so the Python examples pass plugin-repos; registry plugins are downloaded (GitHub API, ZIP fallback), not cloned; updates compare version with latest_version. - PLUGIN_REGISTRY_SETUP_GUIDE: replace the per-plugin-repo + tag walkthrough with a short page on the monorepo registry (plugin_path, latest_version, update_registry.py) that points at the monorepo's own SUBMISSION.md. Drops the reference to the deleted PLUGIN_IMPLEMENTATION_SUMMARY.md and setup_plugin_repos.py. - plugin_registry_template.json: use the real entry shape. - PLUGIN_QUICK_REFERENCE: automatic background updates exist (opt-in); registry example and publishing steps use the monorepo, not tags. - PLUGIN_DEVELOPMENT_GUIDE: tags/releases are not read by the store. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(readme): fix the Triple Bonnet mapping, install prerequisites and backup names - README: the Adafruit Triple Bonnet uses `regular` (3 outputs), not `regular-pi1` (1 output) -- src/matrix_support.py MAPPING_OUTPUTS, and the README's own hardware_mapping section; the template default mapping is adafruit-hat, the PWM mod switches it to adafruit-hat-pwm; manual install only needs git up front (first_time_install.sh installs python-dev-is-python3, cmake, ninja-build etc.; cython3/scons are not used); the Pi Zero 2 W is a supported low-memory board, consistent with PRODUCT.md, LOW_MEMORY_BOARDS.md and the installer's low-memory build; fix the "First_time_install.sh" spelling, an orphan "2." list item and the hello-world starter link (it lives in the plugins monorepo). - CONFIG_DEBUGGING: automatic backups are config/backups/config.json.backup.<YYYYMMDD_HHMMSS_ffffff> (five kept), not config_YYYYMMDD_HHMMSS.json. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(dev): correct the test-running and rgbmatrix build instructions - HOW_TO_RUN_TESTS: coverage is not collected by a plain pytest run and pytest.ini has no threshold; the only one is --cov-fail-under=52 in the core unit-test job of .github/workflows/test.yml, which runs the whole test/ tree (not an allowlist). Almost no tests carry markers, so -m integration / -m slow select nothing; drop them and -m unit as the quick check. Replace the hardcoded /home/chuck path. - DEVELOPMENT: the rgbmatrix package is built with pip install . from the submodule root (scikit-build-core + CMake + Ninja), as first_time_install.sh does; there is no make build-python / bindings/python step, and the build deps are python-dev-is-python3, cmake and ninja-build, not cython3/scons. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(wifi): the setup AP is open; auto-enable can be turned off without code changes - WIFI_NETWORK_SETUP / SSH_UNAVAILABLE_AFTER_INSTALL: both AP paths in src/wifi_manager.py create an open network and nothing reads ap_password, so drop the "ledmatrix123" password and the ap_password key/advice. - SSH_UNAVAILABLE_AFTER_INSTALL: disabling automatic AP mode does not need code changes -- auto_enable_ap_mode is a WiFi-tab toggle and POST /api/v3/wifi/ap/auto-enable; note the monitor daemon reads wifi_config.json at start, so restart it after changing the setting. Use the ledpi username and a relative install path like the other docs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(reference): add auto_update, drop drifted line numbers, fix UI and service details - CONFIG_REFERENCE: document the top-level auto_update.enabled key (read by web_interface/auto_update.py and src/auto_update_setup.py); replace drifted file:line references with function names; the template's dim_schedule mode is "global". - ADVANCED_FEATURES: core does not read a per-plugin background_service block (the sports plugins read their own), and priority is "higher number = higher priority" on FetchRequest but not used for ordering. - WEB_INTERFACE_GUIDE: the General tab toggle is "Web Display Autostart" (web interface service), brightness is 1-100, and config paths are relative to the LEDMatrix folder, not /config. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: drop references to code removed in #608 get_installed_plugin_info, WiFiManager's saved_networks and the six always-skipping plugin test files are deleted there. NetworkManager already remembers joined networks; LEDMatrix no longer stores WiFi passwords. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: don't link SKIN_SYSTEM.md from the core-properties page #615 deletes SKIN_SYSTEM.md; with this link, whichever of the two merged second would break test_doc_links. The skin/skin_options entries go when #615 removes the keys. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
15 KiB
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
-
Find your Raspberry Pi's IP address:
hostname -I -
Open a web browser and navigate to:
http://your-pi-ip:5000 -
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:
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) and Vegas Scroll Mode settings
- Rotation — drag-and-drop Rotation Order list and per-plugin Screen Durations
- Config Editor — Raw
config.jsoneditor with validation - Backup & Restore — back up and restore your configuration
- Fonts — Upload and manage fonts
- Logs — Real-time log streaming
- Cache — Cached data inspection and cleanup
- Operation History — Recent service operations
- Tools — system diagnostics, git & updates, Python dependencies, maintenance, power supply, network radio, services, and plugin health
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 pullthe 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(defaultplugin-repos/) used by the plugin loader - Web Display Autostart — whether the web interface service starts
with the system (
web_display_autostart) - Automatic updates — once a week, update LEDMatrix and every installed
plugin with a newer version. Off by default. Runs 2–5 AM local time when
possible, otherwise within a day of being due. The last result and next
check are shown under the toggle, and anything other than success raises a
banner on Overview.
- Checks first: the code update is skipped, with the reason shown, if
tracked files were edited locally (permission-only changes and edits under
plugins/orplugin-repos/don't count; the pull carries those across and puts them back), the checkout has local commits, a rebase/merge is in progress, the branch has no upstream, less than 300 MB is free, or the newest version already failed once. A failed fetch is retried the next day. - Health check and rollback: after pulling,
ledmatrix-update-verify.servicerestarts the services and checks that the web interface responds and the display (if it was running) stays up. If not — or if the new dependencies failed to install — it resets to the previous commit, reinstalls the previous dependencies and restarts again. A running display is restarted; a stopped one stays stopped. - Plugins update through the Plugin Store, which refuses versions that need a newer LEDMatrix and restores the old copy when an install fails. When the code changed, plugins wait until it passes its health check. Plugins are not health-checked after updating.
- Setup needs no SSH. Turning the toggle on restarts the display service,
which installs the health check (
ledmatrix-update-verify.pathand.service); the General tab shows when it is ready, or why setup failed. Until then only plugins update. New installs set it up during installation and can switch updates on withfirst_time_install.sh --enable-auto-update(orLEDMATRIX_AUTO_UPDATE=1, whichone-shot-install.shpasses through), or at the installer's prompt.
- Checks first: the code update is skipped, with the reason shown, if
tracked files were edited locally (permission-only changes and edits under
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 per panel (typically 32 or 64; even, at least 8 — the current rgbmatrix library rejects more than 64)cols— LED columns per panel (typically 64 or 96; at least 16)chain_length— number of horizontally chained panelsparallel— number of parallel chains (1–3)hardware_mapping—adafruit-hat-pwm(with PWM jumper mod),adafruit-hat(without),regular(direct wiring, and the Adafruit Triple LED Matrix Bonnet), orregular-pi1gpio_slowdown— depends on your Pi and panel (roughly 1–3 on a Pi 3, 2–4 on a Pi 4); raise it if rows jump or the image is garbagebrightness— 1–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
The collapsed Advanced Hardware & Display Options section holds multiplexing, panel type, row address type, scan mode, PWM tuning, the refresh-rate cap and hardware pulsing. Every field has a help tip, and the README's Display Settings section describes each one with its allowed range.
Vegas Scroll Mode: the Display tab also has a full Vegas Scroll Mode section — enable toggle, scroll speed, separator width, dynamic duration, and related settings — so you can configure Vegas mode entirely from the web UI without hand-editing JSON. See ADVANCED_FEATURES.md for what the options do.
Changes require Restart Display Service from the Overview tab.
Plugin Manager Tab
The Plugin Manager has three main sections:
- 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.
- Plugin Store — browse plugins from the official
ledmatrix-pluginsregistry. Click Install to fetch and install. Filter by category and search. - 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
Font Preview:
- Render sample text in any TTF/OTF font at a chosen size
Fonts used by a plugin are chosen in that plugin's own settings tab; the Fonts tab has no per-element override editor.
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:
- Refresh: Reload the log view
- Clear: Clear the current view
- Download: Download logs for offline analysis
- Auto-scroll checkbox: toggle automatic scrolling to the latest entries
Common Tasks
Changing Display Brightness
- Open the Display tab
- Adjust the Brightness slider (1–100)
- Click Save
- Click Restart Display Service on the Overview tab
Installing a New Plugin
- Open the Plugin Manager tab
- Scroll to the Plugin Store section and browse or search
- Click Install next to the plugin
- Toggle the plugin on in Installed Plugins
- Click Restart Display Service on Overview
Configuring a Plugin
- Open the plugin's tab in the second nav row (each installed plugin has its own tab)
- Edit the auto-generated form
- Click Save
- 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:
- Install Hockey Scoreboard from Plugin Manager → Plugin Store
- Open the Hockey Scoreboard tab in the second nav row
- Add your favorites under
favorite_teams.<league>(e.g.favorite_teams.nhl) - Click Save and restart the display service
Troubleshooting Display Issues
- Navigate to the Logs tab
- Look for ERROR or WARNING messages
- Filter by the problematic plugin or component
- Check the error message for clues
- See 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
- The UI is built on Alpine.js and HTMX, so JavaScript must be enabled in the browser
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
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 (web_interface/blueprints/api_v3/) is registered at
/api/v3 in web_interface/app.py.
Common Endpoints:
GET /api/v3/config/main— Get main configurationPOST /api/v3/config/main— Update main configurationGET /api/v3/system/status— Get system statusPOST /api/v3/system/action— Control display (start/stop/restart, reboot, etc.)GET /api/v3/plugins/installed— List installed pluginsPOST /api/v3/plugins/install— Install a plugin from the storePOST /api/v3/plugins/install-from-url— Install a plugin from a GitHub URL
Note: See REST_API_REFERENCE.md for complete API documentation.
Troubleshooting
Interface Won't Load
Problem: Browser shows "Unable to connect" or "Connection refused"
Solutions:
-
Verify the web service is running:
sudo systemctl status ledmatrix-web -
Start the service if stopped:
sudo systemctl start ledmatrix-web -
Check that port 5000 is not blocked by firewall
-
Verify the Pi's IP address is correct
Changes Not Applying
Problem: Configuration changes don't take effect
Solutions:
- Ensure you clicked "Save Configuration"
- Restart the display service for changes to apply:
sudo systemctl restart ledmatrix - Check logs for error messages
Display Preview Not Updating
Problem: Display preview shows old content or doesn't update
Solutions:
- Refresh the browser page (F5)
- Check that the display service is running
- Verify SSE streams are working (check browser console)
Plugin Configuration Not Saving
Problem: Plugin settings revert after restart
Solutions:
- Check file permissions on
config/config.json:ls -l config/config.json - Ensure the web service has write permissions
- 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:
- Run on a private network (not exposed to internet)
- Use a firewall to restrict access if needed
- Consider VPN access for remote control
- 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 (relative to the LEDMatrix folder, e.g. ~/LEDMatrix):
- 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_directoryinconfig.json(defaultplugin-repos/). Main plugin discovery only scans this directory; the Plugin Store install flow and the schema loader additionally probeplugins/so dev symlinks created byscripts/dev/dev_plugin_setup.shkeep working. - Plugin config:
config/config.json(per-plugin sections)
Related Documentation
- PLUGIN_STORE_GUIDE.md - Installing and managing plugins
- REST_API_REFERENCE.md - Complete REST API documentation
- TROUBLESHOOTING.md - Troubleshooting common issues
- FONT_MANAGER.md - Font management details