Basement Lighting
Brighter, smarter lighting for the basement TV room — the comfiest room in the house, and the darkest. Partial-daylight basement with two small windows that let in very little natural light, and Seattle winters bring ~15½ hours of dark around the solstice, so the lights do all the work.
Status
Phase 1 done — backlight runs as a steady Warm Glow. Colour matching (HyperHDR) worked for Kodi but was too distracting for everyday viewing, so it’s switched off (systemctl disable --now hyperhdr@osmc; config kept, re-enable with enable --now). Oct 2026.
Goals
- More light. Two Hanaking LED torchieres today; add two more lights.
- One physical control to turn everything on (or into a “movie” mode).
- Home Assistant control of individual lights — dimming, scenes, automations.
- One thing at a time: TV backlight first.
- The lights must always come on. Nobody should ever be stuck in the dark because a server is down. Basic on/off/dim must work without Home Assistant (wall remote bound directly to the bulbs; lamp switches as the last resort).
The Room
Current lighting is two Hanaking LED torchieres (36W, 3600 lm each, integrated LED, 4 colour temps, stepless dimming, own remote). They’re not smart — no Wi-Fi/Zigbee/app.
Torchieres are a good fit for a basement: they bounce light off the ceiling for even fill. They stay as the main “all on” lights.
The AV chain everything below is built around:
Chromecast ─┐
├─► 5.0 receiver ─► HDMI ─► TCL 55" 6-Series
Kodi Pi 4 ──┘
- TV is 4K but never on Wi-Fi; everything runs 1080p, no HDR (TV upscales).
- Kodi Pi 4 is being reinstalled from LibreELEC to OSMC so it can also run HyperHDR (LibreELEC is a locked-down appliance OS; OSMC is Debian-based).
Phase 1 — TV Backlight (colour-matched)
A strip of addressable LEDs behind the TV that glows to match the edges of the picture (“Ambilight”). Doubles as plain dim bias lighting for regular TV, which is easier on the eyes in a dark room and makes the picture look higher-contrast.
How it works
Receiver ─► capture card (HDMI loop-out) ─► TV
│ USB
▼
Pi 4 (OSMC + HyperHDR) ──network──► SP805E (WLED) ─► LED strip
- The capture card sits between the receiver and the TV. It passes the picture straight through to the TV and sends a copy to the Pi over USB.
- HyperHDR on the Pi samples the edges of the frame and works out colours for each LED.
- It streams those colours over the network to the WLED controller, which drives the strip.
- When HyperHDR stops (TV off), WLED falls back to whatever Home Assistant last set — e.g. dim white or off.
Because the capture is after the receiver, it follows every source — Chromecast, Kodi, anything added later.
Parts
| Part | Notes |
|---|---|
| BENFEI USB-C capture card with 4K HDMI loop-out | Replaces a separate splitter. Driverless on Linux (UVC). May need a USB-C → USB-A 3.0 cable — plug into the Pi’s blue USB 3 port. |
| SP805E ESP32 controller, WLED pre-installed | Addressable (SPI) output, 6A per channel. Power via the VCC/GND screw terminals — the barrel jack is only rated 4A. |
| BTF-Lighting SK6812 RGBW strip | 5V, 60 LEDs/m, 5 m reel, IP30. Dedicated 4000K white chip for clean white. ~3.6 m used around the TV. |
| 5V 10A power brick | Ideally UL/ETL listed — it’s always plugged in behind the TV. |
| ~2 m 18 AWG red/black wire | Second power feed to the far end of the strip. |
Corners: no connectors — fold the strip at 45° for each 90° turn.
Wiring
5V 10A brick (DC cord cut, polarity confirmed with multimeter)
├─ pair 1 ─► SP805E VCC / GND
└─ pair 2 ─► far end of strip (spare power leads)
SP805E output ─► start of strip (5V / data / GND)
- Cut the DC cord only, never the AC side. Confirm + with a multimeter before connecting — reversed polarity kills the strip and controller instantly.
- Solder or ferrule the stripped ends before they go into screw terminals.
- Feeding power at both ends keeps brightness even along the strip.
Settings
- WLED: LED type SK6812 RGBW, auto-white Accurate, current limit ~5.5A. Give the controller a DHCP reservation. Check Wi-Fi signal on WLED’s info page — it’s 2.4 GHz only and it’s a basement.
- HyperHDR: LED output type WLED pointed at the controller’s IP. Capture at low resolution (only edge colours are needed). Set the LED layout to match where the strip starts and which way it runs.
- Home Assistant: WLED integration (on/off, brightness, white/colour), Hyperion integration (toggle colour-matching).
As built
- WLED 0.15.4 at
192.168.2.233, in Home Assistant aslight.wled. 232 LEDs on DATA1 (GPIO 16), SK6812 RGBW, current limit 5.5A. - Strip goes all the way around; the start (LED 0) is at the corner nearest the entertainment centre. Corner LEDs are folded and counted as part of the side:
| Side | LEDs (index) | Count |
|---|---|---|
| Right (up to top-right) | 0 → 40 | 40 |
| Top | 40 → 114 | 74 |
| Left | 114 → 157 | 43 |
| Bottom | 157 → 231 | 74 |
-
Presets: Aurora, Pacifica, Fireworks, Lava Lamp, Meteor Rain, TV White (6, dim white channel only), Warm Glow (7, warm white at ~10%, for casual viewing), playlist Show Off (10).
-
HyperHDR v21 on the Kodi Pi (
192.168.2.225, web UI:8090, JSON API:19444). OSMC is Debian 11, so it’s the genericHyperHDR-21.0.0.0-Linux-armv6l.deb(v22 needs a newer libc). Output: WLED192.168.2.233, 232 LEDs mapped as in the table above, brightness 100%, black-bar detection on. WLED has “force max brightness” turned on for live streams. -
⚠️ HyperHDR v21’s API
setconfigreplaces the whole config: sending one section resets the others to stored defaults. Always read the full config, change it, and send it all back together (or use the web UI).
Known risks
- TV depends on the Pi. The capture card’s loop-out is powered by the Pi’s USB. Pi always on → fine; Pi reboots → picture blips. If the Pi dies, plug the receiver’s HDMI straight into the TV.
- Copy-protected streams (Netflix etc. on the Chromecast) may capture as black — TV still shows the picture, the backlight just won’t follow. Test on arrival; buy with easy returns.
Steps
- Reinstall the Kodi Pi with OSMC; re-add Jellyfin; confirm playback.
- Order parts.
- Wire power, mount the strip, join WLED to Wi-Fi.
- Install HyperHDR on the Pi (
.debpackage), set up capture + LED layout. - Add WLED + Hyperion to Home Assistant; build a Movie scene.
Phase 2+ — Findings (Oct 19)
- Hanaking layout: one by the TV, one by the couch. Current movie habit: the TV-side one gets switched off and the couch-side one stays on. The room needs more light overall, so more lights are being bought anyway.
- The room has no built-in lights. Today: the 2 Hanakings sit on Fosmon 433 MHz plugs with a battery “wall switch” (the household habit to preserve: a switch on the wall).
- Because the Fosmon plugs work, the Hanakings do come back on after power is restored, so Zigbee plugs will work for them.
- Smart plugs can’t dim. They’re relays (on/off). The Hanakings’ dimming and tone are built into the lamp and only reachable via their own remote. Movie-mode options: (a) IR blaster (Broadlink RM4 Mini or ESPHome IR) if the remote is IR, (b) torchieres off in movie mode, couch lamps plus backlight provide the dim light, (c) replace the torchieres with E26 fixtures and Zigbee bulbs.
- Not decided yet. The Hanaking product listing says the remote is RF, so a plain IR blaster is out. RF frequency is unknown: if it’s 433 MHz, a Broadlink RM4 Pro might learn it; if it’s 2.4 GHz, it can’t be automated. There’s no FCC ID on the remote or the lamp base, and each lamp has its own remote. Assume 2.4 GHz and not automatable, which leaves (b) or (c). Next: trial movie mode with the torchieres off and an ordinary lamp behind the couch.
Remote and power tests (before or while parts arrive)
- IR or RF? Point the remote at a phone’s rear camera and press a button. A flickering purple dot means IR. To double-check, point it away from the lamp or cover its front: if it still works, it’s RF.
- IR: option (a) is possible later. ESPHome IR or a Broadlink RM4 Mini (~$20). The remote’s dim buttons are most likely steps up/down, not “go to 20%”, so movie mode would be “send down N times”.
- RF, 433 MHz: a Broadlink RM4 Pro can sometimes learn it. Stay with (b).
- RF, 2.4 GHz (needs pairing, no IR window): not practical to automate. Stay with (b), or (c) eventually.
- What comes back after a power cut? Set a torchiere to a low, warm setting, flip the Fosmon switch off then on. Does it return to that setting or to a default? Either works with plugs. This just tells you what “All on” will look like.
- Control layers: (1) everything down: lamp switches, plug buttons, backlight boots to Warm Glow; set Zigbee bulbs to power-on = on. (2) HA down: IKEA STYRBAR on the wall where the Fosmon switch is, bound directly to a Zigbee group for on/off/dim. (3) HA up: STYRBAR ◀ = Movie mode, ▶ = All on.
Phase 2 — Smart Plugs & Zigbee
The torchieres get on/off control via smart plugs.
- ThirdReality Gen3 Zigbee smart plug 4-pack — physical button, power metering, each plug extends the Zigbee mesh.
- Zigbee coordinator — SMLIGHT SLZB-06 (Ethernet/PoE, place it centrally; avoids USB passthrough into the Home Assistant container). Use HA’s built-in ZHA.
- Smart plugs only switch power — they can’t dim. The torchieres become on/off-only from HA.
Test first: does a torchiere come back on after power loss?Yes. The Fosmon plugs already depend on it.
Shopping list
| Item | Qty | Notes |
|---|---|---|
| SMLIGHT SLZB-06 | 1 | Needs a wired Ethernet drop. Power it with PoE, or with USB-C plus Ethernet if there’s no PoE port. Put it central, not in the rack corner. |
| ThirdReality Zigbee smart plug (Gen3) 4-pack | 1 | 2 for the torchieres, 2 spare as mesh repeaters toward the basement. Get the Zigbee listing, not the Matter one. |
| IKEA STYRBAR remote | 1 | Comes with a wall bracket and takes AAA batteries. |
| Couch lamps with E26 sockets | 2 | Shade or up-light. No built-in LED, no built-in dimmer. |
| Zigbee tunable-white E26 bulbs | 2 | IKEA TRÅDFRI or Hue White Ambiance. |
⚠️ IKEA is switching from Zigbee to Matter-over-Thread (KAJPLATS bulbs, BILRESA remote). Those are not Zigbee, and the SLZB-06 can’t talk to them. Check that each listing says Zigbee. If STYRBAR or TRÅDFRI are gone, a Hue Dimmer Switch and Hue bulbs both work with ZHA.
The existing Fosmon remote outlets are one-way 433 MHz with no state feedback — not worth integrating; keep them for dumb stuff.
Phase 3 — Two More Lights
- Put them behind or beside the couch, not beside the TV (lamps by the screen sit in your eyeline and reflect on it). Plug-in sconces or lamps aimed up or at the wall.
- Choose fixtures with standard E26 sockets and use Zigbee tunable-white bulbs (IKEA Tradfri ~$10, or Hue) — individually dimmable, warm↔cool, and they strengthen the mesh.
- Optional: Adaptive Lighting (HACS) to shift colour temp through the day — cooler/brighter daytime, warmer/dimmer evening — to stand in for the missing daylight.
- Optional: a Zigbee light sensor so lights only come on when the room is actually dark.
Phase 4 — The Switch
A Zigbee wireless remote stuck to the wall at the bottom of the stairs (IKEA RODRET/STYRBAR ~25) — no wiring. Buttons map to scenes:
| Scene | What it does |
|---|---|
| On | Everything full |
| Movie | Backlight Warm Glow, couch lamps ~10%, torchieres off |
| Off | Everything off |
Don’t put smart bulbs behind a wall switch that cuts their power — HA loses control when someone flips it.
Open Questions
- Room dimensions and ceiling height (to check total lumens).
- Window positions relative to TV — glare on sunny days may call for curtains.