One RGB LED Is Enough When Its States Are Designed

A single status light can become confusing if color, blink and priority are not treated as a protocol.

The bench evidence for One RGB LED Is Enough When Its States Are Designed forced a narrower explanation than the original assumption. LOUP deliberately uses one top-front RGB status LED instead of a cluster of unrelated indicators.

The firmware needs a priority table so pairing, ringing, mute, error, charging or OTA states do not fight for the LED. Color and blink patterns should be few, documented and aligned with what the e-paper says rather than creating a second independent UI.

Verification included both the happy path and the failure path because a feature that works once is not yet a production contract. Evidence marker: single-rgb-led.

Indicator simplicity comes from state design, not from having fewer LEDs alone. For a voice product, that kind of boundary discipline matters because audio, signalling and hardware symptoms often look deceptively similar.

Project evidence

LOUP engineering marker: single-rgb-led. This note records the design or debugging lesson without publishing device credentials, private keys, customer data or manufacturing secrets.