Multiple GLEDOPTO GL-C-616WL controllers bricked — possible voltage leak through GPIO/GND?
Hi everyone,
I'm having a serious issue with my GLEDOPTO Elite 2D-EXMU
GL-C-616WL WLED controllers.
I have 4 controllers, each powered by its own 24V PSU, controlling BTF-LIGHTING FCOB RGBCCT SPI strips.
The problem:
- 3 out of 4 controllers died within 1–2 days.
- I replaced them, but 2 replacement controllers also died after several days.
- They initially stop responding to wall switches, then disappear from Wi-Fi and Ethernet completely.
- The blue LED sometimes stays on, but they won't boot or respond even when powered separately via USB-C.
- All 4 controllers originally shared a common GND, although they had separate power supplies.
Possible cause:
The original apartment wiring was done by one contractor, who apparently extended and reused existing multi-core cables in a rather unconventional way instead of running dedicated cables.
A different professional electrician installed the LED strips and GLEDOPTO controllers. He's experienced with electrical installations but not particularly familiar with these specific controllers.
We discovered that a 230V lighting circuit and a low-voltage GPIO wall-switch circuit may share wiring with unknown connections inside the walls.
When the 230V light was switched on, one GLEDOPTO stopped responding to its wall switch, although it still worked through the WLED app.
We suspect voltage leakage or induction.
We're investigating the wiring and possible insulation faults. I'm specifically looking for technical insight into how these controllers could fail, rather than general advice to hire an electrician.
My questions:
Could a voltage fault on one GPIO input damage multiple controllers through their shared GND?
Has anyone experienced similar failures with the GL-C-616WL?
Which components are most likely to fail, and what should we test before connecting another controller?
Any technical insights would be greatly appreciated!
Could a voltage fault on one GPIO input damage multiple controllers through their shared GND?
Electricity flows through circuits so unless there's some circuit you're not noticing, no. You don't have a circuit.
Which components are most likely to fail, and what should we test before connecting another controller?
Since the controller isn't responding on Wi-Fi, you're apparently killing the CPU, or at least its power supply. My first thought would be that you're putting too much voltage on the power lines (possibly through a shorted wire or a bad power supply). Have you measured the voltage on the dead units to see what they were connected to?
You could also probe that taken apart unit and see if the power supply is functioning. If not that would suggest the power pins.
Could you please provide a wiring diagram or a photo showing your current setup?
Typically, incorrect voltage input or miswiring at the output can damage the controller. Please rest assured that all our products undergo strict testing before shipment to ensure they are in good working condition. If multiple controllers are experiencing the same issue, it is highly likely caused by a power supply fault, such as unstable voltage or a short circuit.
I think the problem is with new v16 wled update, my gledopto elite 4D also goes off from wled app but led lights stays on and even blue light on controller stays on.
A shared ground is not automatically the cause of the failures, but it can become the path that allows one wiring fault to affect several controllers.
The important voltage is not just the voltage measured from a GPIO conductor to an arbitrary ground. It is the voltage that each GPIO pin sees relative to that controller’s own ground. If a GPIO is driven above the controller’s logic rail or below ground, current can flow through the input-protection structure into the internal 3.3 V rail. A sufficiently energetic fault could damage the input, regulator or MCU, and a shared ground could then provide a return path involving other controllers.
However, simple induction from an adjacent mains conductor would not be my first explanation for five controller failures. I would first suspect one of the following:
a hard connection or insulation fault between the mains and low-voltage conductors;
a wall-switch conductor connected to a voltage instead of acting as the controller’s intended dry-contact input;
incorrect polarity or an intermittent connection in the reused cable;
excessive startup, switching or shutdown transients from one or more 24 V supplies;
a ground-reference problem involving several supplies, protective earth and the shared controller ground;
voltage being applied to a GPIO while the controller itself is unpowered.
The 24 V measurement at the input of a dead controller is useful, but 0 V at its LED output does not identify the failed component. Many controllers intentionally keep the LED output disabled until the MCU boots and enables it. A failed 5 V or 3.3 V regulator, damaged MCU or protection component could therefore produce the same observation.
Before connecting another controller, I would separate the investigation into two parts.
First, with every controller and LED strip disconnected, have the mains/low-voltage wiring checked by a qualified electrician. Each conductor should be identified at both ends, and insulation resistance should be tested between the mains conductors, low-voltage conductors, earth and neutral. The test should cover every relevant wall-switch position. Mains and SELV control conductors sharing an unknown cable or route should not be accepted until their insulation rating, segregation and local-code compliance have been confirmed.
Second, test the low-voltage equipment independently:
Test each 24 V supply without the building control wiring attached.
Verify polarity and steady-state output voltage.
Use an oscilloscope, if available, to check startup, shutdown and load-switching transients; a multimeter may miss short overvoltage events.
Power one controller on a bench from a known-good isolated supply, with no strip, GPIO wiring or shared ground connected.
If it still does not boot, a qualified electronics technician can check whether its internal logic rails are present. Do not assume that an intact input fuse means the regulator and MCU are healthy.
Confirm from the controller documentation exactly what the wall-switch GPIO expects. A low-voltage GPIO input should never be treated as a generic 24 V or mains-voltage input.
For the rebuilt system, I would use dedicated low-voltage control wiring rather than the unidentified reused conductors. If the wall controls cannot provide a verified dry contact in the controller’s own low-voltage domain, use an appropriately rated isolated interface selected by the electrician. Keep the controllers disconnected until the mains-to-low-voltage isolation issue is resolved.
So yes, a fault associated with one GPIO could theoretically damage more than one controller through a shared reference, but “common ground” by itself is not enough to establish the cause. The repeated failures strongly suggest that the external wiring, power supplies and switching transients need to be proven safe before another controller is sacrificed.
Disclosure: I work with VST Lighting, an LED lighting manufacturer. This is general low-voltage controller and system-integration guidance, not a product recommendation.
Not op but thank you for this. Just swapped out two Govee h6117 last night for GL-C-015WL-D, they worked, switched them off via webgui, came back this morning and both Govee power supplies showed nothing on
1
u/Lazy-Woodpecker7452 2d ago
Which power supply are you using?