Files
LEDMatrix/docs/STARLARK_APPS_GUIDE.md
ChuckandClaude Opus 5.5 3967a6cffc fix(security): re-harden root sudo helpers; installer fixes; ARCHITECTURE and PERMISSIONS docs (#640)
* docs: add ARCHITECTURE and PERMISSIONS guides

ARCHITECTURE.md maps the processes, the state the display and web
services share through the cache, the display loop, the plugin system,
the web UI and the update path, with links into the code and a
where-to-start table.

PERMISSIONS.md lists who owns what after install, both sudoers files
(and why iptables is not granted), the polkit rule, and which
scripts/fix_perms script to run as which user.

Both are linked from the docs index, along with the MQTT bridge README
and src/common/README.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: correct stale setup, service and troubleshooting claims

- README: quick actions run systemctl on ledmatrix.service (run.py), not
  display_controller.py; use_short_date_format has no effect; the
  installer uses system pip with --break-system-packages, not a venv.
- CONFIG_DEBUGGING: LEDMATRIX_DEBUG must be "true"; logs are in journald.
- GETTING_STARTED, WEB_INTERFACE_GUIDE, TROUBLESHOOTING: enabling a
  plugin, plugin settings, brightness and Vegas settings apply without a
  restart; matrix hardware settings still need one.
- TROUBLESHOOTING: install dependencies with sudo so the root service
  sees them; point permission problems at PERMISSIONS.md instead of a
  project-wide chown.
- ADVANCED_FEATURES: real BackgroundDataService stats keys; Vegas hooks
  return VegasDisplayMode and None falls back to capture; cache files
  are 0660; fix_web_permissions.sh runs as the web user and does not
  touch sudoers.
- STARLARK_APPS_GUIDE: only the linux-arm64 pixlet binary is downloaded.
- HOW_TO_RUN_TESTS: test class examples that exist.
- CLAUDE.md: PluginStoreManager, plugin_dirs.py, monorepo installs via
  the Trees API with ZIP fallback, requirements.txt is optional.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: mark deprecated plugin APIs and state manifest fields once

Methods @deprecated("3.7.0") (the set pinned in test_deprecation.py)
were shown as current API in the quick reference, API reference,
advanced guide, development guide and FONT_MANAGER. Each is now marked
deprecated with its replacement. FONT_MANAGER is rewritten around the
current API; the override editor is gone and override methods are
deprecated.

Required manifest fields were stated three different ways. The API
reference now has one section: the 7 schema-required fields, the 4 the
store refuses without, class_name for the loader, and the 8 to set.
The other guides link to it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: document every src/common module and every widget

- src/common/README.md covered 7 of 17 modules. It now has a table of
  all of them (purpose, whether plugins import it, release to floor
  on), a short entry each, and logging advice that matches the code.
- SPORTS_UNIFICATION listed two shared modules and called
  sports_helpers the first; it now lists all six.
- The widgets README lists all 28 registered widgets plus the support
  files, and absorbs the parts that only docs/widget-guide.md had
  (x-options.labels, x-advanced, x-display hidden, plugin-file-manager).
  docs/widget-guide.md is now a pointer to it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(security): fix_web_permissions.sh re-hardens the root sudo helpers

The script chowns the whole project to the web user. That included
scripts/fix_perms/safe_plugin_rm.sh and safe_pip_install.sh -- the two
helpers /etc/sudoers.d/ledmatrix_web lets the web user run as root -- so
running it turned both into a root shell for whoever can edit them. It
also re-grouped config_secrets.json away from ledmatrix.

After the chown it now does what first_time_install.sh's Steps 11 and
11.1 do: helpers back to root:root 755, and config_secrets.json back to
the web unit's User=:ledmatrix 640. Each step is non-fatal and prints the
manual command if it fails.

Also fixes what the script and its docs claimed: it never configured
sudoers, its closing hint pointed at ./configure_web_sudo.sh (wrong
path), and the README and ADVANCED_FEATURES.md said to run it with sudo,
which it refuses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(security): validate and harden every sudoers drop-in the scripts write

configure_wifi_permissions.sh copied its rules into
/etc/sudoers.d/ledmatrix_wifi without `visudo -c`. A malformed drop-in
makes sudo refuse every command for every user, which on a headless Pi
leaves no way back in. It now checks first and leaves the installed file
alone when the rules do not parse, as the other two writers do. (It
already used mktemp, so that part of the review did not apply.)

It also grants the two literal commands wifi_manager.py runs for
NetworkManager's shared-mode dnsmasq drop-in -- `cp
/tmp/ledmatrix-nm-dnsmasq.conf .../dnsmasq-shared.d/ledmatrix-captive.conf`
and `rm -f` of that file. The directory's mkdir was granted, the file was
not. Both are pinned in test_sudo_allowlist_covers_calls.py.

configure_web_sudo.sh wrote its rules to /tmp/ledmatrix_web_sudoers_$$,
a predictable name in a world-writable directory; it now uses mktemp with
an EXIT trap, as first_time_install.sh does. It sets mode 440 on the
installed file instead of leaving the temp file's mode, and finds visudo
in /usr/sbin when that is not on the user's PATH, which skipped the
check silently.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(install): escape the project path in the DNS-fix and MQTT unit renderers

install_dns_fix.sh and install_mqtt_bridge.sh substituted
__PROJECT_ROOT_DIR__ with the raw path, while the other three renderers
go through sed_escape_replacement from lib_systemd_render.sh. A checkout
under a path containing `&`, `\` or `|` rendered a corrupted unit from
these two only. Both now source the helper and use it, and a test checks
that every placeholder substitution in scripts/install uses an escaped
value.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(install): stop the installer scripts reporting things that are not true

- first_time_install.sh printed "Password: ledmatrix123" for the setup
  access point. wifi_manager creates it as an open network ("No
  password" on the panel), so it now says so.
- Step 10.1 printed "✓ WiFi management permissions configured" straight
  after its own failure message; install_wifi_monitor.sh printed
  "✓ Package installation completed" after a failed apt install. The
  tick now only follows success.
- Step 7 printed "Web dependencies already installed ... in Step 5" in
  the one branch that runs because Step 5 did not install them, then
  created .web_deps_installed on that basis. It now warns and leaves the
  marker off so the next run retries, as the comment below it intends.
- check_system_compatibility.sh called Debian 12 Bookworm "full
  compatibility confirmed" while first_time_install.sh refuses anything
  but Debian 13. Bookworm, older Debian and non-Debian systems are now
  errors. Its counters used ((X++)), which under `set -e` exits the
  script at the first warning or error (the expression is 0), so the
  check never reached its summary on any system with one.
- configure_web_sudo.sh and configure_wifi_permissions.sh finished by
  testing `sudo -n test -f ...` and `sudo -n nmcli device status`,
  neither of which is granted, so they always reported a failure. They
  now ask `sudo -n -l` about commands the new rules do grant, which
  checks the rule without running anything.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(install): print the completion summary before rebooting

With -y -- and so for every one-shot `curl | bash` install, which always
passes -y -- first_time_install.sh ran `reboot` about 180 lines before
its "Installation Complete / Web UI Access" summary. reboot returns at
once, so the summary printed while the Pi was going down and the SSH
session usually dropped before the web UI address could be read.

The reboot block moves, unchanged, to the very end of the script. The
interactive prompt now also follows the summary. Because the summary now
runs before the -y reboot, its one command that could fail under
`set -Eeuo pipefail` (the SSID lookup, when nmcli reports a connected
device but no active network line) gets `|| true`; a missing SSID was
already handled as "SSID unknown".

one-shot-install.sh prints its "Next steps" after the installer returns,
by which time the reboot is under way, so it now says so, and README's
Quick Install mentions the automatic reboot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(scripts): correct wrong comments and messages, drop dead code

No behaviour change except the output text noted below.

- 2775 is setgid, not the sticky bit (first_time_install.sh Step 3.1,
  fix_plugin_permissions.sh), and root needs no "PWM hardware access"
  to plugin files.
- The 777 comments in first_time_install.sh Step 3's fallback and
  fix_assets_permissions.sh said root needs it to write. Root ignores
  mode bits; the comments now say what 777 actually opens. The 777
  itself is unchanged.
- apt_remove ends in `|| true`, so Step 12's "Some packages could not be
  removed" branch could never run; it is gone and the helper stays
  non-fatal.
- detect_web_service_user's comment named Step 8 for the web unit
  (install_service.sh installs it in Step 7.5) and now says which
  branch actually runs.
- Step 5 described an "already installed" check that does not exist;
  the ACTUAL_USER comment described the re-exec backwards.
- on_error printed a literal "\n" before "Common fixes:".
- Dead code: one-shot-install.sh's uncalled fix_tmp_permissions,
  LEDMATRIX_ELEVATED=1 (never read) on the sudo re-exec, and
  configure_web_sudo.sh's unused PYTHON_PATH, which also made a missing
  python3 fatal for rules that never mention it.
- start_display.sh / stop_display.sh said "for user: <you>"; the
  service runs as root.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor(fix_perms): fix_cache_permissions.sh uses setup_cache.sh's model

There were two models for /var/cache/ledmatrix. setup_cache.sh (the
installer's Step 2) and install_web_service.sh share it through the
ledmatrix group: root:ledmatrix, 2775, files 660, which is also what
DiskCache relies on to give files the directory's group.
fix_cache_permissions.sh instead made it 777 and re-grouped it to the
invoking user's group, undoing that.

It now runs setup_cache.sh for /var/cache/ledmatrix and keeps its own
handling of ~/.ledmatrix_cache. Dropped: /var/cache/ledmatrix/
placeholder_logos (nothing reads it) and the checks against the
`daemon` user (no service runs as daemon).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* ci: pin actions/checkout in the Claude workflows, drop template comments

claude.yml and claude-code-review.yml used actions/checkout@v4 while
test.yml and release-version-check.yml pin the v4.2.2 commit SHA; they
now pin the same SHA. The commented-out starter-template settings
(prompt, claude_args, paths, author filter) are removed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(scripts): index every script and list removal candidates

New scripts/README.md gives one line per top-level script and scripts
directory, marked keep, dev-only or diagnostic, and lists the eight
scripts nothing in the repo refers to as candidates for removal (kept
for now). The install, utils and dev READMEs now list the files they
were missing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test: tighten two checks that mutation testing showed were too loose

- The wifi sudoers check matched `visudo -c -f "$TEMP_SUDOERS"` in the
  error report too, so replacing the check with `if false` still passed.
  It now requires the command as the condition.
- The summary test never had the setup access point up, so reinstating
  the bogus "Password: ledmatrix123" line went unnoticed. A case with
  hostapd active now checks the AP is described as open.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(permissions): describe the repaired fix_perms scripts and new WiFi grants

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(changelog): docs-scripts

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-24 17:31:41 -04:00

20 KiB
Raw Permalink Blame History

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
  • 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 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

┌─────────────────────────────────────────────────────────┐
│                    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

cd /path/to/LEDMatrix
bash scripts/download_pixlet.sh

The script downloads only the Linux ARM64 build (Raspberry Pi OS 64-bit), from the tronbyt/pixlet releases, to bin/pixlet/pixlet-linux-arm64. On any other platform (32-bit Pi OS, x86_64, macOS), put a pixlet binary on your PATH, or set the plugin's pixlet_path, or place it in bin/pixlet/ under the name _find_pixlet_binary() looks for (web_interface/blueprints/api_v3/__init__.py).

Verify installation:

./bin/pixlet/pixlet-linux-arm64 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 (optional: blank uses this device's location)
    • 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. Left blank, the app renders at this device's location (City / State / Country under General settings). If no city is set there, or the city can't be looked up (no match, or the geocoder is unreachable -- retried after 30 minutes), the app gets no location and falls back to its author's hard-coded default, usually San Francisco. Fill it in only to point one app somewhere else.
  • 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. 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:

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

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 binary
│   └── pixlet-linux-arm64          # the only one download_pixlet.sh fetches
│
└── 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-arm64 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
  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 repo

Configuration Reference

Plugin Config (config/config.json → plugins.starlark-apps):

{
  "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):

{
  "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

LEDMatrix Documentation

Community

  • 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:


Ready to get started? Install the Starlark Apps plugin and explore 974+ community apps! 🎨