My new homelab went into a 12U Lanberg rack cabinet next to my desk. The cabinet takes two exhaust fans in the top, and they had to be quiet enough to work beside. While looking for silent fans I found the be quiet! Light Wings, which also have RGB lighting, and I wondered why server racks so rarely have any lighting.
I pictured a black rack with silver hardware and white light. Nothing on sale did that, so I spent a few weeks finding out if it could be built. It took many nights and about 30 wires. A temperature sensor now sets the fan speed, and each section of the rack has a separate light.
Some links in this post are affiliate links. I may earn a small commission at no extra cost to you.
Requirements
Fans like the Light Wings are made to plug into a PC motherboard. This rack has no PC, and I didn't want its cooling to depend on any of the hardware inside it. I found standalone controllers that set fan speed from a temperature sensor, but none of them drove RGB. I also wanted two LED strips, and all of it had to run without a PC: temperature reading, fan speed and fan color.
While choosing LEDs I found Quindor's channel, where he showed his QuinLED-Dig-Quad. The board drives up to five LED channels and has a temperature sensor, Ethernet and an ESP32 on board. The ESP32, a small microcontroller, can also drive PWM fans, where the width of a pulse sets the speed.
I sit close to the rack, so the strips had to hide individual diodes and be addressable, meaning each group of LEDs can have a different color. I chose BTF-Lighting RGBW FCOB strips at 768 LEDs per meter. FCOB strips put the LEDs under one continuous coating, so they show a line of light instead of dots, and RGBW adds a white channel, which gives a cleaner white than mixing red, green and blue.
WLED or ESPHome
For addressable LEDs I'd normally use WLED, but its fan support is a usermod with limited control. ESPHome has native components for lights and fans, runs automations on the device and sends sensor data and controls to Home Assistant. With some help from AI I mapped the QuinLED's GPIO pins in the config.
The config is called kage-controller.yaml. Kage is Japanese for shadow. I was learning Japanese at the time, and the name fit the black cabinet.
Component | Price (approx.) |
|---|---|
~€50 | |
~€50 | |
BTF-Lighting FCOB RGBW strips, 2× 62cm (BTF-Lighting) | ~€25 |
Mean Well HDR-30-12 (12V DIN rail PSU) | ~€20 |
Mean Well HDR-30-5 (5V DIN rail PSU) | ~€15 |
19” rack DIN rail | ~€30 |
€10 | |
Total | ~€200 / ~$230 |
Also used: the Xiaomi Mijia Electric Precision Screwdriver.
Mounting everything on a DIN rail
I stripped, soldered and crimped about 30 wires: power from both supplies, ground, the LED strips, the fan ARGB (addressable RGB, driven by a data wire) and the fan PWM. I didn't want the electronics lying on the rack floor or zip tied to a shelf, so I mounted them on a cheap 19-inch DIN rail, a metal rail that electrical parts clip onto and that fits the rack.
I also had a 3D printed case to clip the controller onto the rail. It made installation harder and covered the ESP32's GPIO headers, so I took most of it apart and kept only the base that mounts on the rail.
Wiring the bench test
For the bench test I mounted the QuinLED, a WAGO DIN adapter and both power supplies on the rail. The controller runs on 12V from the larger supply, the Mean Well HDR-30-12. The fan ARGB runs on 5V, so a second supply, the HDR-30-5, feeds both fans through WAGO connectors on the adapter.
Each fan has two cables. The ARGB cable sends data to a separate controller channel and power to the 5V WAGO. The four-wire motor cable carries power and ground to the 12V terminals, plus PWM and a tacho wire that pulses as the fan turns. I removed the Ethernet module to reach the pins for those two.
Function | GPIO | QuinLED pin |
|---|---|---|
LED strip left data | GPIO4 | LED4 |
LED strip right data | GPIO16 | LED1 |
Fan left ARGB data | GPIO1 | LED3 |
Fan right ARGB data | GPIO3 | LED2 |
Fan left PWM | GPIO15 | Q1 |
Fan right PWM | GPIO2 | Q3 |
Fan left tacho | GPIO12 | Q2 |
Fan right tacho | GPIO32 | Q4 |
Temperature sensor | GPIO13 | onboard |
The fan ARGB channels sit on GPIO1 and GPIO3, which are also the ESP32's serial pins. My config keeps the logger on at 115200 baud and both fan lights work. If one flickers or stays dark on your board, baud_rate: 0 under logger: frees the pins.
Fan lights wired to 12V
In the first test I wired the fan ARGB power to the 12V terminals instead of the 5V WAGO. The LEDs in both fans died when I switched it on. The motors run on a separate circuit and kept spinning. I ordered two replacement fans and spent two more nights redoing all 17 wires. Check every voltage before you connect anything.
Back on the bench with the replacement fans, Home Assistant found the controller through the ESPHome add-on. I set a different color on each fan and strip, ran the effects, and changed the target temperature by hand: the fans ramped up and their color shifted.
PID fan control
The cooling uses ESPHome's PID climate component. A PID controller (proportional, integral, derivative) sets its output from how far the temperature is from the target, how long it has been off, and how fast it is changing.
climate:
- platform: pid
name: "Kage Cooling PID"
sensor: kage_temp
default_target_temperature: 25.0
cool_output: both_fans_output
control_parameters:
kp: 0.25
ki: 0.002
kd: 0.02
deadband_parameters:
threshold_high: 1.0
threshold_low: -1.0
The deadband is a 1°C window on either side of the target where the fan speed isn't adjusted. The config defaults to 25°C and I set the target to 30°C in Home Assistant, which the device keeps after a restart. Both fans share one PWM signal at 25 kHz, above the range of hearing. If the temperature sensor stops reporting, a check every 30 seconds sets both fans to 100%.
The fan lights use the same fan speed value. Up to 40% they show a default color, white unless I set another one from Home Assistant. From 40% to 70% they go from blue to orange, and above 70% from orange to red. Picking an effect pauses this until the lights go back to Default.
My first config multiplied the tacho count by 30, and Home Assistant showed RPM values 60 times too high. The pulse counter already reports pulses per minute and these fans give two pulses per rotation, so the right filter is multiply: 0.5.
Installing in the rack
I wrapped the loose wires in cable sleeves before the install. The fans went in the top and the strips went into aluminium diffusers on both sides. Even with FCOB strips the diffuser maximizes the effect. The DIN rail went in with the same connections as on the bench, plus Ethernet.
The UPS (uninterruptible power supply) went in first. Its lead-acid batteries make it the heaviest part of the rack, and quite possibly one of the heaviest objects ever made. It also powers the two supplies. The cover that came with the DIN rail looked like a mailbox slot, so I replaced it with a perforated cover, trimmed it to fit and sprayed it silver to match the rack.
Coil whine and badly aimed strips
After a while I heard coil whine, a high tone from vibrating parts inside a power supply. The fans had been silent, so it had to be the supply. I swapped the Mean Well HDR-60-12, which was much bigger than this load needs, for the HDR-30-12 and the whine stopped.
The strips mostly lit the sides of the equipment instead of the front. The VHB tape I used, a double-sided foam tape, made them hard to remove, and I had to open the side and top of the cabinet to reach them. I moved both strips toward the front, and the light now falls where I wanted it.
One light per rack unit
After three months I was still changing the config, and the latest change is lighting per rack unit. The strips are addressed in groups of 48 LEDs, one chip per group, so at 768 LEDs per meter a 62cm strip has 10 groups for 12 rack units. Each section of the rack is a partition light, a light built from a range of groups, and it takes the same groups on both strips. Each section shows up in Home Assistant as a normal light:
- platform: partition
name: "Rack U7 NUCs"
id: rack_u7
segments:
- id: led_strip_left
from: 4
to: 4
- id: led_strip_right
from: 4
to: 4
One group covers about 6.2cm and a rack unit is 4.45cm, so the sections don't line up. I split the rack into six sections by device, such as the patch panel in U1, the NUCs in U7 and the UPS in U10 to U12. The full mapping is in the config comments. A Rack Master Lights switch turns everything on or off, and the Lighting Effect select runs effects across the full strips, because partition lights have no effects of their own.
Result
I barely hear the Light Wings, maybe only at full speed. It was overkill for the hours I put in. The rack sits next to my desk, so I wanted quiet cooling.
The files are in nightlyventures/configs: kage-controller.yaml, a README, and secrets.yaml.example for the API key and IP addresses. If you've built something similar, I'd like to hear about it in the comments.
The config is tested on ESPHome 2026.9. ESPHome has deprecated neopixelbus on ESP32 in favor of esp32_rmt_led_strip and plans to remove it in 2027.1, so the four fan and strip lights will move to the new component.
Updated September 2026: per-rack-unit lights now use partition lights with a master switch, the RPM filter is fixed, the wiring table matches the config, and the config is on GitHub.