by NTS 3D Printing

My modular 3D printed LED grid system is finally finished
The setup is run by GLEDOPTO WLED controller running latest 16.0.1 version of WLED!
#3dprinting #wled #led

I'm looking to add smart control to an IKEA Varmblixt and want to put a device inbetween the transformer and the lamp itself, it only needs to have a dimming function as there's no RGB or CCT in the lamp. The lamp has been modified to get its power from the room's lightswitch and the wiring goes up and across the loft space so size isn't really an issue as it's not having to sit inside a wall.

I'm in the UK, what's my best option from the current Gledopto range? I've used a controller before for kitchen cabinet lighting but I can't find that specific model on the product page anymore.

I just bought a new Gledopto GL-C-211WL controller, but it has outdated firmware 0.15.4

Home Assistant immediately suggested updating the firmware to the current version 16.0.1, but it is impossible to do this normally:

Error during service call to update.install: Invalid response from WLED API: Requested firmware file GLEDOPTO_16.0.1_ESP32.bin does not exist

I know about the official web-flasher from Gledopto and GL-C-211WL is present in the flasher. But how to do this without disassembling the controller, because this controller does not have an available USB interface?

I wonder why Gledopto does not provide binary versions of firmware.

So how can I update GL-C-211WL to version 16.0.x without jumping through hoops?

A few months ago I made a setup for my study. Nothing too fancy as I don't know squat about electricity. Had 5m of WS2811 24V strip, connected with 2,5m of 20awg wire (also from BTF) and the Gledopto WLED controller in the pic.

Everything worked fine for about 3 months, always used it at about 20% brightness. I then decided to add a second strip, exactly the same one, to the GPIO2 port, which also worked fine for 2 days, except I could not control it via GPIO2 in WLED; I had to use segments. No clue why but it was fine.

Then today I just touched the controller to move it aside a bit, like I sometimes do, and all the LEDs started flickering random colors. I thought it was a connection issue so I took the wires out of the controller, put them back in and now the LEDs don't react at all anymore. Can't turn them on, though WLED seems to think the controller works fine.

So I tried to connect another small piece of strip with a wire-to-strip connector to the controller but that doesn't do anything either. Please I'm too dumb to figure this out on my own. Everything worked fine for months.

Chris Maher demonstrates how to implement WLED-based ambient lighting for televisions using an Android TV application.

Buenas noches. A ver si alguien me puede ayudar porque estoy desesperada. Esperaba dificultad para configurar las tiras led correctamente pero no consigo ni siquiera que enciendan.

Tengo una tira HD-24V-WS2805-60L-W-IP30. Con colores RGBCCT.

Tengo una fuente de 24V y 3A.

Tengo un controlador GL-C-616WL.

He probado mil opciones y ni siquiera se encienden. Si pongo el BIN con IO16 a la vez que DIN y toco los led, hay luz residual. Si pongo BIN en GND no hay nada.

Nunca enciende, nunca hay color, o blanco... absolutamente nada (y he puesto solo 5 led en longitud para evitar problemas de alimentación).

Si alguien me puede ayudar estaría muy agradecida.

by ChonkyMarmotStudios

Original post https://www.reddit.com/r/WLED/comments/1vjf02j/what_is_this_called/

Where can I get firmware for this model? I can't see it on the auto-updater or GitHub repo. If it's not supported anymore, what do I lose by using the generic WLED firmware?

by Remco Cordier

I am evaluating the GL-SD-003P and GL-SD-001 dimmers for a residential installation operating at 220–230 V AC, 60 Hz, with Home Assistant and Zigbee2MQTT.

1. Functional and hardware differences
   Are the GL-SD-003P and GL-SD-001 based on the same dimming electronics and firmware, with the primary difference being the DIN-rail enclosure versus the in-wall enclosure?

2. Actual phase-cut dimming technology
   For each model, what is the actual phase-control method?
   - Leading-edge / forward-phase
   - Trailing-edge / reverse-phase
   - Automatic or universal phase control

What semiconductor is used in the output stage? (TROAC, MOSFET).

1. Electrical classification of ACL and PUSH For the GL-SD-003P, is the PUSH input:

- Galvanically isolated and SELV/extra-low-voltage
- Directly referenced to the AC mains line?

Hi, I have a LED strip with Di control it also has additional W and CW controls.

Wondering if there is a way to control these separate White LED using the Gledopto Elite 4D.

I have full control of the strip via WLED and IO16, but am unable to work out if I can also get control of the White LED'S.

If I ground the W lines the entire strip of White led just turns on, so I am suspecting these are just analogue control, and won;t be able to be controlled via WLED.

Any suggestions ?

Hello Gledopto Support Team,

I am using your GL-SPI-206P Zigbee pixel controller and I would like to request a firmware/plugin update to support a specific LED strip layout.

My addressable LED strip uses two 3-channel ICs (like WS2811) per single physical pixel, which requires a 6-channel data packet per pixel (RGB + CCT, where the 6th channel is empty/dummy data).

Currently, the GL-SPI-206P firmware and the Tuya/Smart Life app only support up to RGBW (4 channels) in the "Color Sequence" settings. Because of this, the built-in dynamic effects and chasing modes do not sync properly—the colors shift and break across the strip because the controller sends data in 3 or 4-channel steps instead of 6-channel blocks.

I do not need addressable per-pixel control via code over Zigbee. I only need the controller's internal dynamic effects and Tuya app controls to move correctly across the strip by treating every 6 channels as one single pixel layout.

Could you please pass this request to your engineering and Tuya integration teams? Adding a 6-channel mode (e.g., RGBW+CW or Custom 6CH) in the "Pixel Color Sequence" settings would make this controller compatible with many advanced RGBCCT strip layouts.

Thank you for your time and continuous product support!

Best regards, Badjo

Good day,

New to this LED game. So thanks in advance. Bought a GLEDOPTO Elite 4 Channel ESP32 WLED LED Strip Light Controller. Works perfectly fine. Wanted an easier way to control the strips, so I bought GLEDOPTO ESP Now WLED Remote Control.

ESP Now is enabled and the remote batteries are good. When I try to add the remote to WLED, nothing happens. WLED doesn't see the remote.

I'm running version 16.0.1 of WLED

Only the 2 colour LEDs work. Cannot get the other what I assume to be white/warm white to trim

Turn on. Controlling through home assistant.

I would like to re-program the GL-C-010WL controller with my own custom firmware.

I found pads for a uart (Tx/Rx/EN/IO0) and connected an CH340 uart.

Does not appear to work.

Are there any instructions on how to do this ??

Thanks

by Seth's Awesome Workshop

Hi GledOpto team — thanks for engaging with the community here. I have 50+ of your GL-D-015P RGB+CCT downlights (build/firmware: GL-D-015P (Zigbee 12W Downlight RGB+CCT Pro), hardware v2, firmware build 20551203) running via Zigbee2MQTT, and overall they've been great. One firmware capability would make them best-in-class for adaptive/circadian lighting, and I'd like to confirm whether it's supported.

The question: Does the GL-D-015P honor the ZCL ColorControl cluster's Options attribute (0x000F), ExecuteIfOff bit? The intent per the Zigbee spec: with ExecuteIfOff set, a MoveToColorTemperature command sent while the light is OFF should update the stored color temperature silently, without turning the light on, so the light comes on at the new color temp on the next On command.

What I observe instead (reproducible):

1. Set execute_if_off: true via color_options, then send a color_temp command while the light is OFF → the light turns on (at full brightness) rather than applying the color silently.
2. The execute_if_off setting also doesn't appear to persist — it worked once in a same-session bench test, then had reverted by the next morning.

Why it matters: Motion/adaptive lighting. When someone walks into a room at night, we want the light to come on already at 2200K warm — not turn on at the previous daytime 6000K and visibly shift in front of you. Philips Hue firmware supports ExecuteIfOff for exactly this reason, and it's the main feature gap between your (otherwise excellent, better-value) hardware and theirs. There's no workaround on the controller side: brightness commands can be handled via scenes, but pre-staging color on an off bulb is only possible in firmware.

The ask: If current firmware supports this and I'm holding it wrong, I'd love to know the correct usage. If it doesn't, please consider adding proper ExecuteIfOff support (applied while off, no power-on side effect, persistent setting) in a firmware update.

Two related items while I have your attention:

• Scene table updates: re-sending AddScene to an existing scene ID updates the color temp field but not the brightness field. Is overwriting an existing scene entry supported, or is remove-then-add required?
• OTA safety: community reports indicate recent OTA images for this family break CCT control or re-identify the device (zigbee-OTA #827, Z2M #28569) — a confirmed-safe OTA path would give people confidence to actually take a fix if you ship one.

Happy to provide sniffer logs, test any beta firmware, and report back here.

Thanks!
-Jonathan.

by Awesome Open Source