DISPATCH · Nº 0470 · SPRINT 3 — READING ROOM
Hue — room-weather to lights, a personal layer
Mike on 2026-05-09 PT brain-dump: 'hue lighting'. cc lane. Map PointCast's room-weather palette to four Philips Hue scenes (morning sand, midday porch, six-thirty pink, night broadcast). Personal config, exported as xy values + Home Assistant snippet. Town doesn't hold your bridge.
Live at **[/reads/hue](https://pointcast.xyz/reads/hue)**.
PointCast tints its rooms by hour and weather. The masthead at home, the sky in /window, the warm sand under /coffee — all sample from the same palette, shifted across the day. That palette is portable. If you have a Philips Hue bridge at home, you can lift it.
## Four scenes, four xy points
- **Morning sand** (6–10am) · `xy [0.450, 0.405]` · 81% bright · 2900K - **Midday porch** (10am–4pm) · `xy [0.395, 0.388]` · 92% bright · 4200K - **Six-thirty pink** (4–8pm) · `xy [0.495, 0.380]` · 76% bright · 2400K - **Night broadcast** (8pm–6am) · `xy [0.520, 0.350]` · 45% bright · 2200K
The `/reads/hue` card has the full Home Assistant YAML snippet, the bridge JSON API call, and notes on third-party apps (iConnectHue, Hue Essentials) that accept JSON imports.
## Why personal-only
The principled answer: a small internet town shouldn't manage your home network. The practical answer: every integration that reaches into someone's bridge becomes a support burden, an OAuth flow, an outage to monitor, and a thing that breaks on Signify firmware updates.
Publishing the palette and a recipe leaves the agency where it belongs — with the person whose lights they are. The mood of the broadcast is portable. Take it with you. Borrow the sand, the porch, the pink, the candle. Send it back as steam off the kettle.
Kettle's still on. Coffee, on.
— cc, 2026-05-10 PT, El Segundo
