Why led-ticker?
led-ticker is the batteries-included info-display layer for large HUB75 signs on a Raspberry Pi — the higher-level layer above the rpi-rgb-led-matrix driver, fully open and self-hosted. Most “LED matrix” tools solve a different problem. This page says which is which so you can pick the right one.
Is led-ticker right for you?
Section titled “Is led-ticker right for you?”How the tools compare
Section titled “How the tools compare”| Axis | led-ticker | rpi-rgb-led-matrix | WLED | Tidbyt / tronbyt | AWTRIX3 |
|---|---|---|---|---|---|
| Hardware | HUB75 panels | HUB75 panels | Addressable WS2812 | 64×32 appliance | 32×8 (Ulanzi) |
| Compute | Raspberry Pi | Raspberry Pi | ESP32 | Appliance / Pi | ESP32 |
| Scale | Large, custom (256×64+) | Large | Strips / small matrices | Tiny, fixed | Tiny, fixed |
| Primary use | Info feeds / signage | (you build it) | Effects / ambient art | Glanceable apps | Clock / notifier |
| Content model | Declarative TOML + plugins | Write your own code | Web UI (push strings in) | App store (Pixlet) | Web UI + HA/MQTT |
| Architecture | Self-contained on the Pi | Library you call | Self-contained; you feed text | tronbyt needs a self-hosted server; Tidbyt needs its cloud | Needs Home Assistant / MQTT to feed it |
| Open / self-hosted | Fully open, no cloud | Open library | Open | tronbyt open / Tidbyt closed+cloud | Open firmware |
| Cost band | ~$150+ | ~$150+ | ~$30+ | ~$199 / DIY | ~$50 |
The alternatives in their own right
Section titled “The alternatives in their own right”rpi-rgb-led-matrix
Section titled “rpi-rgb-led-matrix”The canonical low-level HUB75 driver that led-ticker builds on — think of it as the layer below, not a rival.1 It gives you full control over every pixel in C++ or Python, which is exactly right if you want to write your own rendering engine. led-ticker is the batteries-included layer on top so you don’t have to: declarative config, a plugin system for live data feeds, transitions, fonts, and emoji all come included.
WLED is a widely-used platform for addressable LEDs — animated effects, a friendly web UI, and a large community.2 It is built for WS2812-style addressable strips and panels, not HUB75 (a newer, secondary path for WLED), and its text rendering works by pushing strings in rather than fetching and updating data feeds on its own. Pick WLED for ambient lighting and effects; pick led-ticker for a data-driven info sign that manages its own content.
Tidbyt / tronbyt
Section titled “Tidbyt / tronbyt”Tidbyt is a polished small 64×32 appliance with an app-store model (Pixlet apps); tronbyt is the open, self-hosted way to keep one running cloud-free.3 Both are a great fit for a tiny finished desk gadget. Tidbyt’s future is uncertain and the device depends on a cloud backend; tronbyt requires running its own server. If you want a large, custom, fully self-contained sign that fetches its own feeds without a separate backend, led-ticker is the better fit.
AWTRIX3
Section titled “AWTRIX3”AWTRIX3 turns a ~$50 Ulanzi TC001 (ESP32, 32×8 pixel matrix) into a capable clock and notifier with Home Assistant / MQTT-native integration.4 The device itself holds no logic — dynamic content is pushed to it from Home Assistant, MQTT, or a home server. Pick it for a cheap smart-home glance display; pick led-ticker for a large standalone sign that fetches and rotates its own content with no external backend.
Where led-ticker fits
Section titled “Where led-ticker fits”led-ticker’s sweet spot is large, bright, multi-panel HUB75 signs that drive their own news, weather, crypto, sports, and calendar feeds from a TOML config — fully open, self-hosted, no cloud, no smart-home backend, no subscription. If that matches what you’re building, start with Getting started or jump straight to building your own sign.
One capability that sets led-ticker apart is inline value tokens: drop a :weather.nyc: or :clock.now: token into any widget’s text and it resolves to a live, self-updating value — so a single scrolling message can read NYC: 72°F Sunny · 9:01 AM, each piece refreshing on its own. Live data isn’t confined to dedicated widgets; it composes into ordinary text anywhere on the sign.
Common questions
Section titled “Common questions”Does led-ticker run on a Raspberry Pi 5?
Section titled “Does led-ticker run on a Raspberry Pi 5?”Yes — and on the Pi 4. One build runs on both: the underlying rpi-rgb-led-matrix driver detects the board at runtime and selects the matching GPIO backend (BCM2711 on the Pi 4, RP1 on the Pi 5). The hardware pages cover the small per-board tuning each one wants.
Do I need to know Python to use it?
Section titled “Do I need to know Python to use it?”No. You describe what the sign shows in a TOML config file — sections, widgets, transitions — and no code runs that you wrote. Python only enters the picture if you want to write a plugin to add a new widget or live-data source.
Can I try it without buying any hardware?
Section titled “Can I try it without buying any hardware?”Yes. The same engine runs against a software stub and renders a config to a GIF on your laptop, so you can build and preview a whole sign before buying a single panel. The Getting started page walks through the no-hardware path.
Can led-ticker replace a Tidbyt?
Section titled “Can led-ticker replace a Tidbyt?”It depends on the sign you want. For a small, finished desk appliance with an app-store experience, a Tidbyt — or tronbyt to self-host one cloud-free — is the better buy. led-ticker is the better fit when you want a large, custom, multi-panel sign that fetches and rotates its own feeds with no separate backend or subscription.
How much does it cost to build a sign?
Section titled “How much does it cost to build a sign?”A reference build lands in the low hundreds of dollars, mostly the HUB75 panels and the Raspberry Pi driving them. The hardware pages list the exact parts for the small (160×16) and big (256×64) reference builds so you can price your own before committing.
Comparisons reflect the landscape as of mid-2026.