Sequences, Settings and Audio only show in Edit mode. On wide screens the Edit
mode actions and Run mode move into the Menu.
Edit device gets a Groups checklist. The Devices list and Edit device group
show names without addresses, and every device in Edit device group, in the
group or in the list to add from, gets an Identify button.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
API.md now documents what the firmware serves: groups, combined
brightness, beat-driven sequences, import/export, /api/audio, patterns
over ESP-NOW, outputs, /ws, driver OTA, and how API calls become driver
messages and group commands. The user guide follows the current UI; the
in-app audio help describes the microphone instead of input devices.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tools/driver_ota.py (make ota-drivers) pushes the driver's .py files
through the controller, one file per POST /drivers/ota/file. Drivers
skip files they already have, and the rest are committed together.
- one target: acked unicast, two chunks in flight
- several targets: each file is broadcast once, then each driver is
asked for its missing chunks and repaired by unicast
- rel: rel_send_seq, rel_wait and rel_send_wait, plus a callback for
the drivers' 0x26 status replies
- commands are retried, because status replies are not acked
- broadcast chunks are paced 50 ms apart: faster broadcast left C3
drivers unable to receive until reset
- bench results in docs/BENCH_TEST.md, endpoints in docs/API.md
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The ESP-IDF project, docs, tools, tests and web UI move from v2/ to the
root, and the Makefile, README, build scripts and test runner drop the
v2/ prefix.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Move the web assets and templates under v2/web, drop the old src/, lib/
and scripts, and update firmware, tools, docs and db files. Add the audio
page, LED test scripts and VPN autoconnect script.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Add src/engine, modelled on technicalkiwi/portal's player and sequence runner:
- Pixel generator: runs the unchanged led-driver patterns under CPython
(utime shim + NeoPixel-like buffer) on a per-zone render thread and
streams frames to pixel outputs, with keepalive for static frames.
- Output drivers: DDP, Art-Net (ArtDMX/ArtSync), sACN/E1.31, USB-DMX
(Enttec Pro / Open DMX), plus an ESP32 preset output that reuses the
existing preset + select delivery path. Registry in db/output.json,
CRUD and test pattern at /outputs.
- Sequencer: timed preset chains per zone (portal step shape), deadline
scheduling, loop/repeat, resume after restart; legacy sequence records
are migrated. Zone play/stop, sequence and scene play/stop endpoints.
- CLI (python -m engine.cli), Outputs and Sequences modals, preset tiles
drive pixel outputs, API/README docs, engine test suite.
ESP32 firmware is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Serve GET /settings as JSON by removing duplicate HTML route (use /settings/page for the standalone UI).
- Save global_brightness via PUT; broadcast to connected drivers; push saved level when outbound WS connects.
- Zones UI loads brightness from GET /settings only (no localStorage).
- Bump led-driver submodule for settings.save on brightness with save flag.
- Extend API doc and endpoint tests for global_brightness.
Co-authored-by: Cursor <cursoragent@cursor.com>