The controller checks every route against the signed-in user's role, with levels none, view, control and edit per area. Guests get the permissions of a built-in guest role. Auth stays off until the first user exists; LED_ADMIN_USER and LED_ADMIN_PASSWORD create the first admin. Sessions are cookies, passwords are PBKDF2-SHA256, and logins lock per username after five failures. The simulator's WebSocket checks the view permission at handshake and per frame; /ws needs devices control. The web UI gets a sign-in button, a sign-in prompt on refused changes, and a users and roles screen. Also: the device build gets the bridge include path and forward type it was missing, Dockerfile.sim runs non-root, and Dockerfile.prod with docker-compose.prod.yml runs the controller on an internal network behind Caddy for HTTPS. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
sim-controller
The led-controller firmware (main/) built for ESP-IDF's linux target, so the whole rig runs on a
computer with no hardware:
sim-controller (http://localhost:8080) ──UDP 8766──▶ led-simulator ──▶ 16 × led-driver/src
◀── src_mac + packet ── ◀──
make sim # headless drivers (CPython), plus this controller
make sim-web # drivers in the browser at http://localhost:8765/, plus this controller
make test-sim # test/api against it, including test_rig_sim.py
- Same sources as the board, minus Ethernet, Wi-Fi, mic and firmware OTA (
components/sim:app_main,esp_timer, mic/OTA/littlefs stubs,driver/gpio.hand lwip socket headers). The beat clock ataudio_simulated_bpmstands in for the mic. - ESP-NOW goes through
main/bridge.c:dst_mac + packetto the simulator,src_mac + packetback. On the board the same bridge runs whensettings.bridgeis set. - The store is a directory:
LED_SIM_DB(defaultsim-controller/dataundermake sim). LED_SIM_HTTP_PORT(default 8080),LED_SIM_BRIDGE(default127.0.0.1:8766).- The binary runs on the host, not in Docker: rootless Docker's
--network hostis its own namespace.