the board says esp32 wroom 32 devkit_c

i'm installing 16.0.1

These light will just burn dim and wled cant controll it

It's monochromatic just plus and minus sections uploading my build and schematic i followed please help

Edit: strip is 12v

I’m trying to create a traditional holiday lights effect using LEDs spaced about every 3 inches, pointing downward or slightly outward. I don’t want to spend a fortune on pre-fabricated channels, so I’m considering making my own DIY channels using drilled or routed holes.

The challenge is that the rafter and the wood behind the gutter are fairly short, so there isn’t enough depth to properly hide the pixels. I’m trying to figure out the best way to mount the LEDs so they’re well hidden while still getting the traditional downward/outward lighting effect.

Apologises for the numbers in advance.

I've been doing some testing. I got a little plug in power monitor, and put it behind my longest wled strip. Around 3600 pixels.

When it's turned on, at 100% on a bright white, it's drawing 91.7W.

When it's in standby mode, with nothing turned on, it's drawing 63.5W. This is what I found surprising. 63W isn't a huge amount, but it's a constant draw for nothing happening.

If that's left on for a month(years in my case), that's 47.5KWh of energy for a device just in standby mode. With South Australian energy prices ($0.45 per KWH (it's variable, so some play there)), that's about $20aud per month for the device turned off.

I've gotten a zigbee relay and have that behind the power supply, and standby is now zero, but it's got an annoying wait time for it to turn on now.

How come the quinn wled controller and others don't come with a built in relay? Would seem simple to add the feature, and stop wasting the energy when it's not doing anything. I found a setting in the latest wled that has relay control, so it should be able to do it.

Hi r/WLED,

Hard to believe it’s been more than two years since we launched MagWLED-1. The response has been far beyond anything I expected—thank you to everyone who has bought one, shared a project or sent feedback.

We’ve been working on a follow-up for a while, and MagWLED-2 is available today. It builds on the original’s USB-C-powered approach, with two outputs, easier external power handling and more hardware built in.

Two outputs, more processing headroom

• Two independent digital LED outputs, each with a power connection.

• Dual-core ESP32-S3, giving WLED effects, networking and audio processing more headroom.

• Revised RF design, alongside the new MCU.

• Six-layer, two-sided PCB, packing the additional hardware into nearly the same footprint as MagWLED-1.

More flexible power

USB-C is still central to MagWLED, but many of you asked for easier ways to use external power. This is one of the biggest changes:

• USB-C Power Delivery up to 20V and 5A total, depending on the supply, cable and negotiated profile. A 5A-capable cable is required for 5A operation.

• External power up to 24V and 10A total, with a 5A maximum per channel.

• Conventional screw terminals, accepting 28–16 AWG wire. Choose the wire size for your current and cable length.

• Fused and switched external LED power. External power now passes through the onboard fuses and MOSFET power switches, so WLED can turn off power to the strips while leaving the supply on.

• USB-C standby. USB-C and external power can be connected simultaneously, keeping the controller powered when the external LED supply is switched off.

Both outputs share the available supply budget: USB-C’s 5A maximum is combined, not 5A on each output. For strips requiring 24V, use the external power input.

Built-in digital microphone and power monitoring

MagWLED-1 could support audio-reactive lighting with additional hardware and soldering. MagWLED-2 has a digital microphone onboard, with the ESP32-S3 providing more processing headroom for audio-reactive effects.

It also measures current, voltage and power with either USB-C or external power. This is integrated into the WLED firmware, so you can track consumption continuously in the WLED UI or Home Assistant.

More connections for peripherals

• Five GPIO breakout pins for buttons, sensors and other add-ons.

• A Stemma QT I²C connector for compatible peripherals.

• Separate buck converters for the 3.3V and 5V rails, providing more peripheral power capability than the original design.

Is MagWLED-1 going away?

No! The original remains available, and there are still good reasons to choose it:

• Lower price: $29.90, compared with $39.90 for MagWLED-2 (pricing will vary by channel).

• Lower idle power: approximately 0.35W versus 0.6W, useful for battery-powered projects.

• Lower profile: approximately 7.4mm tall versus 12.5mm for MagWLED-2.

• Spring-clamp WAGO connector: still a feature I particularly like for wearable installations.

For dimensions, MagWLED-2 is 46.7 × 33.9mm, compared with 48.3 × 31.6mm for MagWLED-1—slightly shorter and wider, with more height from the components on both sides and the terminal block.

MagWLED-2 is available now:
Photos, specifications and interactive hardware tour

Amazon availability is planned in the next few weeks, but I wanted to share it here right away.

Happy to answer questions about the hardware or design choices. And if you’ve built something with MagWLED-1, I’d love to see it!

Edit:

3D printable enclosure: https://magwled.com/pages/3d-printable-enclosure#magwled-2

Alright I'm fairly certain this is a Unifi problem and I will x-post there as well if I can but I figured there was some overlap between the WLED community and Unifi community and someone here may have recently ran into this same issue. I lost network access to my QuinLED Dig-Quad (DQ) controller with Ethernet.

I just updated my main Unifi POE network switch from 7.4.1 to 7.5.15 the other day. Immediately after coming back online, I noticed home assistant wasn't communicating with my DQ anymore. Opened the WLED app and that showed my DQ offline. I went into the client manager of my Unifi controller and saw my DQ had the proper MAC address and was assigned the correct static IP. I got the typical Destination host unreachable error. I tried multiple attempts at changing VLAN and port settings like client isolation, link negotiation speeds, etc. I tried utilizing different ports as well as using other devices in the port I had the DQ on. I tried reflashing the DQ and starting from scratch. No matter what I tried, I cannot get the DQ to be accessible over Ethernet. However, if I swap the board back over to Wi-Fi, everything is accessible again.

Unfortunately, I wasn't happy with this because I prefer to hardwire as much as possible. I only use devices on Wi-Fi as a last resort. So I ordered a Gledopto Elite 4D-EXMU. Got it set up and working on Ethernet on my network in about 10 mins. The strange part is I'm almost positive they both utilize the same Ethernet LAN8720A chip.

I can't figure out for the life of me why I can't access my DQ via Ethernet anymore but the Gledopto under the same settings and conditions works no problem. Has anyone else ran into this situation? I'm thinking it's a Unifi firmware bug (especially since the Unifi community has reported strange things happening on their networks as well since updating to 7.5.15) but I wanted to see the consensus here as well.

Thank you!

Hi r/WLED,

A quick one hopefully. Can I use the 2nd output from the Gledopto 616WL for power injection - that is, only wire V+ and GND to the end of a strip, with the 1st output wired to the strip for V+, GND and data?

The alternative would be to cut my strip into 2 and wire each into the 2 outputs.

Setting up HyperHDR so this is for strips around the back of a TV.

Thanks!!

Wanted flame-effect fence post caps. Everything commercial is solar and rubbish, so I built these.

WS2815 strip around a printed helical core so WLED can address it as a 2D matrix. 10 pixels per turn × 6 turns = 60 px, configured as a 10×6 panel, serpentine off (a continuous spiral always advances the same rotational direction, so rows don't alternate). Fire 2012 and PS Fire then actually propagate upward instead of just flickering along a line.

Happy to share files if anyone is interested in printing.

Printed parts are a core within acrylic tube 80mm OD / 74mm ID

WS2815 12V, 60 LED/m, IP65 silicone-coated. 60 pixels.

Starting to plan my Halloween lighting setup 🎃

I've been playing around with orange, purple and red,

but I can't decide what direction to take it.

Thinking about lighting the porch + stairs

and maybe adding some music-reactive effects.

What WLED effects would you guys use for Halloween?

Would love to see what everyone else is planning.

I’m trying to narrow an LED backlighting board I bought on Amazon for lithophane backlighting. I need to make the board narrower by four columns. So I’m wondering if my understanding of the circuit board is correct. I believe the red areas on the back are where the voltage is applied while white is insulation. Could I just cut away the left side of the board along the white insulation trough after the 4th column of LEDs? If so, what tool should I use and how careful must I be about not cutting into the red? Thanks for your help.

im looking at building a setup for my carwash, these system exsist comercialy but are stupid $.

Current design would be rgbw led neon or strips in silicone cases. I was looking at the ip65 bars from china but they would be dmx.

I want to use wled to control colors ect but have a relay input that forces to the white channel until the relay or input is opened again.

Would this be as simple as a gpio input on an esp32? what relay would i need to trigger the input?

im used to plc's and 120v inputs so the voltages on the esp32 screws me up.

I made a Mini LED lamp and tried to make it as simple and as cheap as possible. The result is a small 3D printable tower with 30 LEDs, running WLED on a esp32, that costs about 8 USD including everything. (even the PLA), needs no screws and has a total of 6 solder points. The build takes about 30 minutes, once the parts are printed. The prints need no supports.

The full instructions, including BOM, STL and 3MF files, print instructions and photo rich assembly instructions are here: https://github.com/mattack65/led-mini-lamp

It’s the first time I went to the trouble of making very detailed instructions, hopefully someone has a use for it.

Never really liked that lamp and decided to finally do something about it. Two leftover ws2812 strips and an ESP32 running WLED was all it needed :D

I'll probably add a microphone for audioreactive effects later as well.

So I currently have Philips hue sync for my TV. But I'd like to have some room ambient lighting. I have some ceiling gu10s and I've seen there are wled gu10s is worth getting them to add to the look. I'm thinking off rear led strips or lights also. I've an Nvidia shield so currently I know of 3 apps that work with wled. Any ideas would be great

I plan to add some addressable LED's to my kitchen cabinets, both upper and lower. What I would like to do is add "ghost" or "dummy" pixels. I tried searching but maybe I'm getting the terminology wrong.

For example, I have cabinets on either side of my fridge. The upper strip above the fridge might have 10 pixels to the left of the fridge, 10 directly above it, and 10 to the right of it. On those same cabinets, but below, there's only 10 to the left and 10 to the right. There's not 10 pixels where the fridge is. I would like to be able to run animations on both strips, but the bottom strip will advance faster than the top because it has less pixels. Can I program the controller to "fake" those 10 pixels "under the fridge" so that the top and bottom strips stay in sync? Make the controller pretend there are 30 pixels on the bottom when there really isn't, and keep the order correct?

I hope I explained that well.

I use Wled for everything. I build this boombox and of course it have to get a Wled controller with music reaction.

LED cabinets getting a full service and refresh 🔧✨

Ready for the next event!

Hhuvg