Dev log · Jun 2026 · draft sample post

Building the light module

One module powers the whole catalog — so getting it right is the highest-leverage thing I do. Here's how the electronics came together as three small boards.

HERO — light module on the bench, boards visible · 16:9 · 1600×900

Every gadz.tech product — the lamp today, the shelf next — is built on a single light module: twelve accent LEDs for color and ambience, plus one 4-watt LED for real task light. Designing, sourcing, and writing firmware for one module instead of many is the whole trick. Every improvement here improves the entire catalog at once. draft copy

Three boards, one job

Rather than cram everything onto one crowded PCB, the module splits into three: an LED board, an MCU/power board, and a thin skin board. It keeps each board simple to manufacture and lets the turnkey assembler populate them without bespoke handling.

DIAGRAM — three-board architecture (LED / MCU-power / skin) · 3:2 · 1400×933
The constraint that shaped it: an ESP32 running WLED-compatible firmware, so nothing here locks the customer into us.

Why WLED underneath

The controller is ESP32-class and stays compatible with vanilla WLED — a mature, open base with a real community and integrations into Home Assistant, Alexa, and Google. We add a design layer on top; the open layer is what guarantees the product keeps working for decades.

PHOTO — populated boards, macro · 16:9 · 1600×900

What's next

The exploded view — every part to design spec, boards rendered — is the next milestone, and it'll headline the lamp page. After that: measured finishing yields and a real cost-down pass on the electronics. draft copy

← Back to the dev log