An audio-reactive lighting controller for a modular synth case: touchscreen, WS2812 strips, Home Assistant.
Loading README and project media…
An audio-reactive lighting controller for a modular synth case. A 3.5" touchscreen on the front panel, WS2812 strips behind the rails, and a spectrum analyser listening to the case's output — so the lights move with whatever you're patching. Control it from the screen, from a browser, or from Home Assistant.

https://github.com/user-attachments/assets/42361cac-358a-4347-8153-37f31353e51d

| Colour | Effects | VU |
|---|---|---|
![]() | ![]() | ![]() |
| VU Meter | Waterfall | Aurora | Bloom | Rings |
|---|---|---|---|---|
![]() | ![]() | ![]() | ![]() | ![]() |
Everything sits behind a 3D-printed panel: the board, and a scrap of protoboard carrying an MSGEQ7
and a handful of passives. There's no custom PCB to order. The panel's CAD and printable files are
in hardware/printed/ — four parts as STLs, a STEP and the Fusion source.
Standard slicer defaults; only the plug cover needs supports.

| Part | Qty | Notes |
|---|---|---|
| WT32-SC01 Plus | 1 | ESP32-S3, 8 MB flash, QSPI PSRAM, 3.5" 320×480 ST7796 touchscreen |
| MSGEQ7 | 1 | Seven-band graphic equaliser, DIP-8. A socket is worth it |
| WS2812 / WS2812B strips | — | Equal-length strips on one data line. The builds here are 5 × 29 and 3 × 29 LEDs |
| A10k potentiometer | 1 | Front-panel input attenuator (audio taper) |
| 3.5 mm jack | 1 | Audio in |
| 22 kΩ, 330 Ω resistors | 1 each | Audio input; WS2812 data line |
| 200 kΩ resistor | 1 | MSGEQ7 clock |
| 0.01 µF, 33 pF, 2 × 0.1 µF | MSGEQ7 input, clock and decoupling | |
| 1000 µF electrolytic, 6.3 V+ | 1 | Across 5 V at the LED terminal |
| Screw terminals, 2- and 3-way | 1 each | 5 V input; LED output |
| 10-pin IDC header | 1 | Eurorack bus power (optional, see below) |
| Protoboard, hook-up wire, JST connectors | ||
| 3D-printed parts | 4 | Panel, LED holder and two covers: hardware/printed/ |
| 5 V supply for the strips | 1 | Roughly 60 mA per LED at full white. Separate from the case's Eurorack supply |
Everything connects to the board's Extended IO header, which also carries +5 V and GND. These are the only GPIOs the WT32-SC01 Plus breaks out; the rest drive the display and touch.
| Header pin | GPIO | Connect to |
|---|---|---|
| EXT_IO1 | 10 | WS2812 data, through the 330 Ω resistor |
| EXT_IO3 | 12 | MSGEQ7 OUT (pin 3) |
| EXT_IO4 | 13 | MSGEQ7 STROBE (pin 4) |
| EXT_IO6 | 21 | MSGEQ7 RESET (pin 7) |
| EXT_IO2, EXT_IO5 | 11, 14 | free |

The MSGEQ7 circuit is the datasheet's Typical Application, unchanged: 22 kΩ and 0.01 µF into IN,
0.1 µF on VDD, another 0.1 µF on pin 6 (the chip's internal 2.5 V reference), and the clock set by
200 kΩ from CKIN up to VDD with 33 pF from CKIN down to ground. Full schematic:
hardware/rackglow.pdf, editable in KiCad as
hardware/rackglow.kicad_sch.
Audio in. The jack takes a Eurorack-level signal — an FX send, in this build — which is around 10 Vpp, while the MSGEQ7 wants roughly 0.1–0.3 Vpp. The front-panel pot does that attenuation: turn it up until the loudest passage just reaches the top band without pinning, then back off slightly. Line level works too, with the pot further up.
Power. The panel and the strips are fed separately — the panel draws very little, the strips draw a lot.
| Feeds | Notes | |
|---|---|---|
| J3 · Eurorack 10-pin bus header | the panel | +5 V and GND from the case's bus board |
| J4 · 5 V screw terminal | the panel, the strips, or both | An external supply |
⚠ Don't run the strips from a Eurorack 5 V rail. 145 LEDs at full white can ask for several amps, far more than those rails are built for. Give the strips their own 5 V supply, sized for roughly 60 mA per LED at full white, and share ground with the board.
What that looks like if you get it wrong: oscillator pitch drifting as you turn the lights up. The strips load the rail, the rail sags, and everything running off it goes with it. That symptom is what put the second supply in this build — and it reads as a synth fault, not a lighting one.
The reference build uses two supplies: the case's Eurorack bus powers the panel through J3, and a second 5 V supply drives the LED strips alone. One supply through J4 works too, if it is sized for the strips plus the board.

Strip layout. Strips are daisy-chained on the one data line and treated as equal-length rows. Alternate strips run in opposite directions (serpentine), which is how they chain naturally behind a rail. Set the strip count and LEDs per strip under LED Config in the web UI.

Rackglow-Setup
(password rackglow123).192.168.4.1.http://rackglow.local (or the IP address shown on the screen) and set the strip
layout under LED Config.Download firmware.bin from the latest release
and upload it at http://rackglow.local/update. Settings are kept.
| Controls | Audio Reactive |
|---|---|
![]() | ![]() |
LED Config holds the strip layout, the screensaver and the Home Assistant settings, plus a screenshot tool for the panel.
| Screensaver + Home Assistant | LED strips |
|---|---|
![]() | ![]() |
http://rackglow.local/logs shows the device log — the first place to look when something isn't
working.
Rackglow talks to Home Assistant over MQTT and announces itself using MQTT discovery. You need an MQTT broker; if you don't already run one, use the Mosquitto broker app (formerly add-on).
In Home Assistant go to Settings → Apps, install Mosquitto broker and start it. Home Assistant offers to set up the MQTT integration once it's running — accept it.

Give Rackglow its own broker login rather than a Home Assistant user. Rackglow stores the password on the device, and a broker-only login can't be used to sign in to Home Assistant itself.
Open the Mosquitto broker's Configuration tab.
Under Logins click Add, enter a username (e.g. rackglow) and a password, and click
Add.

Scroll to the bottom of the Options card and click its Save — it's the button at the end of that card, not the one under Network. Accept the offer to restart the broker.

In Rackglow's web UI open LED Config → Home Assistant MQTT, set Enabled to On and enter:
| Field | Value |
|---|---|
| Broker Host | Your Home Assistant's IP address (e.g. 192.168.1.20) |
| Port | 1883 |
| Username / Password | The login from step 2 |
Save. Within a few seconds Rackglow appears under Settings → Devices & services → MQTT:

| Colour | Effects |
|---|---|
![]() | ![]() |
| Entity | What it does |
|---|---|
light.rackglow_leds | On/off, brightness, colour, and every effect by name |
switch.rackglow_vu_mode | Brightness follows the audio level |
switch.rackglow_screen_sleep | Screen fully off. Tapping the screen wakes it and turns this back off |
Not connecting? http://rackglow.local/logs says why: username or password rejected,
cannot reach (wrong host or port), or a hostname that won't resolve. Use the IP address rather
than homeassistant.local.
Built with PlatformIO on the Arduino framework (the pioarduino platform,
pinned in platformio.ini). You also need Node.js 20+, because the web UI is
built during the firmware build.
pio run -t upload
build_web.py runs Vite, gzips the bundle and
compiles it into the binary, so there's no filesystem to upload and a firmware update always
carries the matching UI.cd web_src && ESP32_HOST=192.168.x.x npm run dev serves the Vue source
locally and proxies to a running device. Use the IP: Vite can't resolve rackglow.local.GPIO 10 is the only ADC1 pin on the Extended IO header. ADC2 (GPIO 11–20) is unreliable while WiFi is active, which is why the MSGEQ7's analog read on GPIO 12 pauses during an OTA update. A different analog audio input needs GPIO 10 (moving the LED data elsewhere) or an I2S ADC — retiring the MSGEQ7 frees GPIO 12, 13 and 21, enough for I2S.
MIT — see LICENSE. Third-party components and their licences are listed in THIRD-PARTY-NOTICES.md.
Made by DIY Doohickeys.