Wiring an analog controller is genuinely simple — one supply in, your strips out, a few minutes of firmware. Here's the whole thing, start to finish. Setting up a different board? See the Mini or Deca guide.
One 12–48V supply into Power IN; each strip onto its own fused output. The LEDs glow the moment it's powered.
The Plus has five analog outputs and one digital output. Before you wire anything, sketch what each channel does. A common layout: two channels for a warm + cool white (tunable) run, two for another white zone, one for a single colour or a spare, and the digital output for a short addressable accent.
Channels are assigned in firmware, not hardware — so this is just a plan, and you can change it later in software.
Feed one DC supply into the Power IN + and – terminals. The whole board — and every output — runs from that single voltage, so match the supply to your strips: 24V supply for 24V strips, and so on. The Plus accepts anything from 12V to 48V.
Each analog strip gets its positive from a fused output + and its colour/white lines to the matching channel terminals. The colour-coded, labelled terminals make this hard to get wrong. Because every positive output is individually fused, a short on one strip blows that channel's fuse and leaves the rest running.
For a tunable-white run, wire warm white to one channel and cool white to the next. For RGB, use three channels; for RGBCCT, five.
For analog and tunable white, ESPHome gives you the cleanest Home Assistant control. QuinLED publishes a ready-made An-Penta-Plus ESPHome config — here are the real pins for a three-channel RGB strip, a tunable-white run, and the digital pixel output with its relay:
# An-Penta-Plus pins: ch1=33 ch2=32 ch3=12 ch4=4 ch5=2 · digital=5 · digital-relay=13 output: - { platform: ledc, pin: GPIO33, frequency: 20000 Hz, id: r } - { platform: ledc, pin: GPIO32, frequency: 20000 Hz, id: g } - { platform: ledc, pin: GPIO12, frequency: 20000 Hz, id: b } - { platform: ledc, pin: GPIO4, frequency: 20000 Hz, id: ww } - { platform: ledc, pin: GPIO2, frequency: 20000 Hz, id: cw } switch: # relay that powers the digital output - platform: gpio pin: GPIO13 name: "Digital power" restore_mode: ALWAYS_ON light: - platform: rgb name: "Accent" red: r green: g blue: b - platform: cwww name: "Cove white" cold_white: cw warm_white: ww cold_white_color_temperature: 6500 K warm_white_color_temperature: 2200 K - platform: esp32_rmt_led_strip # addressable pixels on the digital output pin: GPIO5 num_leds: 60 chipset: WS2812 rgb_order: GRB name: "Pixel accent"
Prefer presets, effects and a phone UI? Flash WLED instead (use v0.15-b3 or newer for the higher bit depth), then set the LED outputs to PWM RGB+CCT or the multi-white mode in WLED's settings. To install WLED — or update it later — use QuinLED's web flasher at install.quinled.info, which always has the newest An-Penta-ready build.
On ESPHome, Home Assistant auto-discovers the device — click Adopt and your white, CCT and RGB lights appear as proper light entities with brightness, colour-temperature and transition support, all over a local API. On WLED, add the official WLED integration and it's discovered the same way. No cloud, no account, no polling.
Wire the Plus over Ethernet for the lights you never want dropping off Wi-Fi.
Set your warm and cool white temperatures to match your strips (say 2200K and 6500K) so the tunable-white slider lands where you expect. Then the good part: save a few scenes in Home Assistant — a bright "cooking" preset, a warm "evening" one — and wire them to a button, a schedule or a motion sensor so the right light just happens.
That's it. One supply, your strips, a few minutes of config — and a controller that's been quietly running flicker-free at ~20 kHz the whole time.
The Plus FAQ covers flicker on camera, power sizing and injection, the digital output, Ethernet vs Wi-Fi, and ESPHome vs WLED. The full technical docs live on quinled.info.
