Philips Hue + Tevyr

Drive Philips Hue lights and scenes from any Tevyr macro — switch scenes between sessions, dim during keynotes, flash a lamp on overrun, blackout on critical alerts. Hue's Remote API bridges via Philips' cloud, so no LAN tunnel required.

What's Philips Hue?

Philips Hue is the most ubiquitous smart-light platform. Hue lights connect to a local bridge; the bridge talks to Philips' cloud; Philips' cloud exposes the Remote API at api.meethue.com. Tevyr uses the Remote API so you don't need to expose your bridge to the internet yourself. Learn more at meethue.com.

No tunnel required

Unlike WLED, Hue's Remote API is cloud-bridged. Tevyr → api.meethue.com → Philips' cloud → your bridge → your lights. You don't need a Cloudflare Tunnel or any LAN exposure. This is the cloud-friendly lighting option for events without a network team.

#What you can do

Switch a scene on session change

Each session gets its own Hue scene — 'Concentrate' for keynotes, 'Relax' for Q&A, 'Energize' for upbeat segments. Macro fires the scene change on session lifecycle.

Flash a lamp during overruns

When the timer overruns, flash a single accent lamp red. Less visually disruptive than full-venue color changes, still gets the speaker's attention.

Ramp brightness for walk-in

Drop venue brightness when the first session starts; ramp back up at the event end. Hue's smooth transitions look like a real lighting board.

Blackout button

On critical failures, set every light to off in one macro step. Macro-driven 'go dark' faster than scrambling for a manual switch.

#Prerequisites

Tevyr Starter plan or above — Free plan ships 0 integration connections
Philips Hue bridge + lights on your local network (one-time setup with the Hue app)
A Philips Hue developer account at developers.meethue.com
A Remote API access token captured via the authorize flow

#One-time setup

#1. Register a Hue developer app

Sign up at developers.meethue.com
Click My apps → Add new Remote Hue API app
Fill the form (App name, Application description, Callback URL)
Note the AppId, ClientId, and ClientSecret — you'll need them for the authorize flow

#2. Run the authorize flow

Follow Philips' Remote API Quick Start Guide. The short version:

Send the user to https://api.meethue.com/v2/oauth2/authorize?clientid=<your-client-id>&response_type=code&state=anything
Capture the code from the callback
Exchange the code for an access token via the token endpoint
Capture the bearer token

This is more work than the typical paste-a-key flow, because Philips wants a proper OAuth dance. Tevyr's first-class OAuth handling for Hue is on the roadmap (Phase 5) — until then, run the flow manually once and paste the resulting bearer token.

#3. Add the connection in Tevyr

Settings → Integrations → Add new → Philips Hue
Paste the bearer token, name the connection (e.g. "Hue — main room"), click Save
Click Test — Tevyr calls /route/clip/v2/resource/bridge (read-only, no lights touched) and shows a green toast with the bridge list on success

#4. Find your bridge ID and light/group IDs

Once the connection tests green, you need the IDs to address specific lights:

Bridge ID: returned in the test response and visible in your Hue developer dashboard
Light IDs / Group IDs: hit https://api.meethue.com/bridge/<bridge_id>/lights (with your bearer token) to enumerate. Note the numeric ID of each light you want to control. Group 0 is "all lights" — handy for venue-wide effects

#Recipes

Drag flow.http_request, pick your Hue connection.

#Recipe 1 — Activate the "Concentrate" scene on session start

Trigger: lifecycle event on_session_start. Action: Activate scene.

Field	Value
Bridge ID	(your bridge ID)
Group / room ID	`0` (all lights) or a specific room ID
Scene ID	(the scene's ID from the Hue app — find via `/bridge/<bridge_id>/scenes`)

#Recipe 2 — Blackout on critical alert

Action: Set light state.

Field	Value
Bridge ID	(your bridge ID)
Light ID	(e.g. `0` for all-lights, or specific light)
On	`false`

#Recipe 3 — Dim during Q&A

Action: Set light state.

Field	Value
Bridge ID	(your bridge ID)
Light ID	(specific light)
Brightness	`25` (out of 254 — about 10%)

#Recipe 4 — Flash a lamp red on overrun

Trigger: on_timer_overrun. Action: Set light state.

Field	Value
Bridge ID	(your bridge ID)
Light ID	(accent lamp ID)
On	`true`
Brightness	`254`
Hue	`0` (red)
Saturation	`254` (fully saturated)

Chain a flow.wait_ms step then a second Set light state call to revert to a calmer state.

#Troubleshooting

#`401 unauthorized`

The Remote API token expired. Hue's remote tokens have a finite life — re-run the authorize flow on the Philips developer dashboard and paste the new token via Edit on the Tevyr connection.

#`404 not found` on a light or group

Wrong bridge ID or wrong light/group ID. Re-enumerate via https://api.meethue.com/bridge/<bridge_id>/lights (or /groups) to confirm the IDs are still valid — Hue can reshuffle IDs if a light is removed and re-paired.

#A light doesn't respond, but other lights do

Open the Hue app first and confirm the light is responding to manual control — if not, the issue is upstream (power, pairing, ZigBee mesh)
If the Hue app works but the API doesn't, re-pair the light in the Hue app to force a fresh ID assignment

#"I want OAuth instead of paste-a-token"

First-class OAuth for Hue is on the roadmap (Phase 5). Slack is the only OAuth-backed integration shipped today. Until Hue OAuth lands, you'll need to re-run the authorize flow whenever the token expires.

#Context variables

Hue's action fields are mostly numeric (bridge ID, light ID, brightness, hue, saturation). The scene ID and bridge/light ID fields support {{ctx.*}} interpolation if you want them dynamic. See the full context-variable reference in the Macros guide.

#Triggered by webhook events

Hue can be fired automatically from any webhook event — e.g. switch to a red scene on timer.critical. When creating a webhook, pick Integration mode and select your Hue connection.

Macros — chain Hue scene changes with timer warnings + on-air indicators
Integrations overview — other tools you can wire alongside Hue
WLED guide — LAN-side lighting alternative for non-Hue LED setups
Webhooks — for "Hue → Tevyr" direction (motion sensor triggers a macro)