jimmyandClaude Opus 5.5 e7f238aebc fix: stop group updates to silent drivers from starving zone play
Every acked unicast holds a pending slot for its whole retry run, so zone
and profile edits with drivers switched off filled the link and the next
zone play timed out (503). Group updates now go to a driver that has
failed three messages in a row at most once every 30 s; one that comes
back still gets its groups when it announces or resyncs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 10:38:51 +13:00
2025-04-15 10:14:46 +00:00

led-controller

ESP32-S3 controller for LED drivers: W5500 Ethernet, web UI, I2S microphone beat detection and an ESP-NOW link to the drivers. The firmware is C (ESP-IDF) at the repository root; see docs/BENCH_TEST.md for the bench tests.

Build and flash

make build            # minify the web UI from web/, then build the firmware (ESP-IDF in Docker)
make flash            # flash over USB
make ota HOST=<ip>    # update firmware (web UI included) over Ethernet, no USB (POST /ota)
make ota-drivers HOST=<ip> [MAC=..] [BROADCAST=1]   # push changed led-driver .py files over ESP-NOW
make monitor          # serial console
make test             # driver unit tests and the C/Python envelope cross-check

make lists every target. The web UI sources are in web/ (static/, templates/, audio.html).

Other directories

  • led-driver/ (submodule): MicroPython firmware for the ESP32 LED drivers.
  • led-tool/ (submodule): led-cli, configures drivers over serial and updates the controller over Ethernet (led-cli --ota HOST).
  • led-simulator/ (submodule), espnow-sender/: test helpers.
  • db/: stored zones, presets and devices, importable with PUT /db/<name>.

Docs

  • API reference: docs/API.md
  • User guide: docs/help.md (scripts/build_help_pdf.sh regenerates docs/help.pdf)
  • Specification: docs/SPECIFICATION.md

Network

The controller advertises <hostname>.local over mDNS (default led-controller, plus an _http._tcp service). Both settings below come from /settings and apply on reboot.

static_ips is a list of networks to try, in order, each time the Ethernet link comes up. The first entry whose gateway answers ARP is used; if none does (or the list is empty) the controller uses DHCP. netmask defaults to 255.255.255.0, dns to the gateway.

curl -X PUT http://led-controller.local/settings/settings -H 'Content-Type: application/json' -d '{
  "hostname": "stage",
  "static_ips": [
    {"ip": "192.168.1.50", "netmask": "255.255.255.0", "gw": "192.168.1.1"},
    {"ip": "10.0.0.50",    "netmask": "255.255.255.0", "gw": "10.0.0.1"}
  ]}'
S
Description
No description provided
Readme AGPL-3.0
11 MiB
0 Stars 1 Watchers 0 Forks
Languages
Python 59.2%
JavaScript 29.6%
HTML 6.5%
CSS 3.6%
Shell 0.9%
Other 0.2%