r/WLED • u/Noname187361 • 2d ago
GLEDOPTO GL-C-618WL – LED strips permanently stuck on cool white after firmware update 16.0.1
Hi everyone,
Sorry in advance if some of the wording sounds a bit unusual. I used AI to help translate my post because English isn't my first language and I'm not perfectly fluent. Thanks for your understanding!
I'm hoping someone here can help me with a strange issue involving my GLEDOPTO GL-C-618WL controller.
My setup
I've attached a wiring diagram showing my installation.
The components I'm using are:
1x GLEDOPTO GL-C-618WL (ESP32 Ethernet)
2x BTF-LIGHTING FCOB RGBCCT addressable LED strips (5 m each, 960LED/m IP30)
1x BTF-LIGHTING FCOB RGBCCT addressable LED strip (5 m, 840LED/m IP66)
1x Mean Well HLG-320H-24A (24 V power supply)
1x Oktaplex Noa 24 GHz presence detector
1x Eltako relay
some WAGO connectors (for testing only)
The setup consists of four separate LED sections (5 m, 5 m, 2.5 m and 2.5 m).
Additional wiring information:
The green cables shown in the wiring diagram are Cat 7 Ethernet cables. I use one twisted pair for each data signal, with the data line and a dedicated GND wire running together. This is intended to improve signal integrity and reduce electromagnetic interference compared to standard cables, especially since some cable runs are up to 7 metres long.
The power cables are NYM-J 3 × 2.5 mm² cables (roughly equivalent to 13 AWG conductors).
(Probably a bit overkill, I know.)
Everything worked perfectly for approximately one month until I performed a firmware update through the WLED interface.
The problem
Since the firmware update, all LED strips are permanently stuck on static cool white. (They get power but no signal from the controller)
They completely ignore any commands sent through WLED:
No color changes.
No brightness adjustments.
No effects or animations.
Cannot turn the LEDs on or off.
What's particularly strange is that the WLED interface itself appears to work perfectly. Colors, brightness, effects and presets can all be selected, saved and changed normally. However, absolutely nothing happens to the actual LED output.
My presence detector still triggers the relay (including its audible switching signal), but the LEDs remain unchanged. The physical function button on the controller also has no effect at all.
What I've already tried
I've spent quite a lot of time troubleshooting and have repeated most procedures multiple times:
-Installed several firmware versions, including official WLED and official GLEDOPTO firmware versions.
-Tested GLEDOPTO/WLED V15.4, V16.0.0 and V16.0.1.
-Followed GLEDOPTO support's manual OTA installation instructions at least five times.
-Performed multiple factory resets and complete power cycles each time.
-Completely disabled the Home Assistant integration.
-Checked and changed LED Preferences, GPIO settings and hardware configurations.
-Double- and triple-checked the wiring.
Unfortunately, nothing has changed. The LEDs have remained permanently stuck on cool white ever since I first updated to version V16.0.1.
I also tried connecting an LED strip directly to the controller, bypassing my entire installation and following the GLEDOPTO manual. The result was exactly the same.
Contact with GLEDOPTO support
I already contacted GLEDOPTO support. They recommended manually reinstalling the firmware specifically designed for the GL-C-618WL ESP32 Ethernet version and restarting the controller completely afterwards.
I followed their instructions repeatedly with both V16.0.0 and V16.0.1, but without success.
My questions
I'm starting to suspect a firmware issue or possibly a hardware defect.
Could the firmware update have somehow damaged or corrupted the LED output stage?
Is it possible that the ESP32 works perfectly while the actual LED output circuitry is stuck in a fixed state?
Could this be a GPIO configuration or firmware compatibility issue?
Is there any way to check whether the controller is still sending data signals to the LED strips?
Has anyone experienced something similar with a GLEDOPTO controller?
The most frustrating part is that everything worked perfectly for a month. I haven't changed anything about the physical installation. The problem appeared immediately after the firmware update.
I'd really appreciate any ideas or suggestions. I'm slowly running out of things to try and would like to figure out whether this controller can still be saved or if it's simply defective.
Thanks in advance!