- led-simulator: the rig runs the C++ led-driver as WebAssembly (sim-driver/),
one single-threaded worker per bar, no cross-origin isolation needed. Rooms
(one JSON per room) with an on-page editor, and a pattern gallery. The
Python server, Pyodide boot and ring buffer are removed.
- sim-controller sim_rig.c: serves /sim/ from an embedded pack, the page's
WebSocket and the rooms/flash API. The desktop build embeds it too.
- bridge.c: a "browser" bridge kind that carries ESP-NOW frames to the page;
devices announced through it are marked sim.
- UI: Simulator in the Menu, split view with resize and pop-out, swipe
between controller and rig on phones; SIM/REAL badges in Devices.
- Fades: preset pushes and Wi-Fi driver bodies always carry fade and
beat_time, so "off" no longer inherits an earlier fade.
- Also the sequences-v2 work in progress: desktop port, bridge firmware,
serial bridge, Wi-Fi drivers, sequence timeline, audio and API changes.
- led-driver: ESP-NOW link, beat sync, control messages, sim hooks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Sequences v2, bridges and sim-controller changes from the working tree.
- Records the led-driver, led-tool and led-simulator commits above.
- Includes dmx-driver/ and graphify-out/.
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Settings gets a Driver tab (/settings/editor). It sends a driver its settings through PUT /devices/<id>, which now forwards name too, and runs the tools/driver_ota.py session from the browser. The firmware embeds the led-driver files and a manifest of their hashes, because crypto.subtle is unavailable over plain HTTP.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Profiles seed presets, a default zone and a palette, and clone with their
own copies; deleting a profile removes what it owned. Zones get the v1
list shape, set-current, current, clone and content-fragment. Devices are
keyed by MAC with v1 validation and identify. Patterns: definitions, OTA
file and manifest, upload, driver, and send over ESP-NOW (the led-driver
pattern sources are embedded in the firmware). Pixel outputs get v1
validation and a DDP/Art-Net/sACN test pattern. Sequences, palettes and
settings follow v1 replies and validation, and /ws forwards browser
messages to the drivers.
The resource handlers move out of api.c into res_*.c, patterns.c and
outputs.c. cJSON now allocates from PSRAM: the store had grown enough to
starve internal RAM and abort the mic at boot. /status reports
free_internal.
The Wi-Fi AP and led-tool routes are left out.
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>