19fea0b0a13b36eaa77b74bf1e9aefd05ca540c4
POST /devices/ping broadcasts an ESP-NOW PING_REQ, collects the drivers' PING_RSP for timeout_s and registers or renames the ones that answer. A reply also counts as the driver being heard, so group updates go to it again. POST /devices/groups sends every ESP-NOW driver its groups and reports the acks. The devices modal gets the Ping drivers and Update groups buttons from main, with per-driver ping dots. UI files are now served with Cache-Control: no-cache and the firmware build hash as ETag, so a browser picks up a new UI right after an update instead of a day later. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 withPUT /db/<name>.
Docs
- API reference:
docs/API.md - User guide:
docs/help.md(scripts/build_help_pdf.shregeneratesdocs/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"}
]}'
Languages
Python
59.2%
JavaScript
29.6%
HTML
6.5%
CSS
3.6%
Shell
0.9%
Other
0.2%