WLED TUI is a multi-device terminal UI for Linux, written in Bash, that controls WLED lights via the WLED JSON HTTP API.

WLED TUI provides a full-screen Bash TUI (tput/stty) for discovering and managing multiple WLED instances, switching between devices, and adjusting common WLED state such as power, brightness, presets, effects, palettes, segments, colors, and more.

• Multi-device support with quick switching and a per-device online/offline indicator.
• Bonjour/mDNS discovery using Avahi (avahi-browse), probing _wled._tcp first and falling back to _http._tcp with a /json/info probe.
• Manual device add, edit, and remove (host:port).
• Device cache stored in ~/.config/wledtui/devices.json (respects XDG_CONFIG_HOME).
• Status tab: power toggle and brightness adjustments.
• Presets tab: list and apply presets from /presets.json (fallback to /json/presets).
• Effects tab: list/apply effects; adjust speed or intensity per segment.
• Palettes tab: list/apply palettes per segment.
• Segments tab: toggle segment on/off, edit primary RGB color, and apply changes to all segments.
• Advanced tab: adjust transition time, toggle nightlight, toggle live mode, and reboot.
• Help overlay and footer key legend.
• Polling with backoff: selected device refreshes about every 2s, all devices about every 8s, with offline retry backoff up to 30s.
• Debug logging via WLEDTUI_DEBUG=1 to ~/.cache/wledtui/debug.log (respects XDG_CACHE_HOME).
• Optional smoke test mode (./wledtui --smoke HOST:PORT).

On startup, WLED TUI performs an mDNS/Bonjour scan using Avahi (avahi-browse) before drawing the UI, so the device list is populated immediately when the interface renders. Discovery requires:

• avahi-daemon running and reachable on the host.
• avahi-browse installed (typically provided by avahi-utils or avahi-tools).
• mDNS/Bonjour traffic allowed (UDP 5353); ensure your firewall and network allow multicast and that WLED devices are on the same L2/VLAN or an mDNS reflector is configured.

If no _wled._tcp services are found, WLED TUI falls back to _http._tcp and probes each candidate with /json/info to confirm it is a WLED device.

• Bash 5+
• curl
• jq
• avahi-browse + avahi-daemon (required for discovery)
• A terminal that supports standard ANSI escape sequences (works over SSH)

Keep it short—install the dependencies with your distro’s package manager:

# Debian/Ubuntu
sudo apt-get install -y bash curl jq avahi-utils

# Fedora
sudo dnf install -y bash curl jq avahi-tools

# Arch
sudo pacman -S bash curl jq avahi

chmod +x ./wledtui
./wledtui

Use the same key labels as the footer legend:

• ~/.config/wledtui/devices.json — cached devices (uses XDG_CONFIG_HOME if set).
• ~/.cache/wledtui/debug.log — debug logs when WLEDTUI_DEBUG=1 (uses XDG_CACHE_HOME if set).

• Discovery finds nothing:
  • Confirm avahi-daemon is running.
  • Ensure avahi-browse is installed and in $PATH.
  • Check firewall rules for UDP 5353 multicast.
  • If devices are on another VLAN/subnet, enable an mDNS reflector or move devices to the same L2 segment.
• Device shows offline / timeouts:
  • Verify the device IP/port in devices.json or re-add it.
  • WLED TUI uses short HTTP timeouts; intermittent Wi-Fi can cause temporary offline status and exponential backoff.
• Keys not working in some terminals:
  • Some terminals remap or delay escape sequences; try a different terminal or SSH client if arrow keys or Shift-Tab do not register correctly.

• Discovery relies on Avahi; without it, devices must be added manually.
• Only the WLED JSON HTTP API is supported (/json/state, /json/info, /json/effects, /json/palettes, /presets.json//json/presets).