Philips Hue

Before you start

A Philips Hue account that owns the bridge you want to control — your normal Hue app account works.
Admin access on the Neowit organization.
The bridge must be online and paired with Philips's cloud. The integration talks to the remote Hue API (api.meethue.com), not to your local network — if you've only ever used the bridge over LAN, enable remote access inside the Hue app first.

Connect Philips Hue

In the left navigation, open Settings → Integrations.
Click Add integration and pick Philips Hue.
On the Neowit form, click Connect to Philips Hue. You're redirected to Philips's authorization page.
Sign in with the Hue account that owns the bridge, and approve Neowit's access.
You land back in Neowit. A "Philips Hue integration connected successfully!" toast confirms, and the new integration shows a Connected status.

If the redirect fails before you reach Philips, the form shows "Failed to start OAuth flow. Please try again." — just retry from step 3.

[SCREENSHOT] The Integrations settings page showing a Philips Hue card with a teal "Connected" badge, the bridge's name below it, and a Synchronize button on the right.

Running your own Hue developer app? Expand Or configure manually on the connect form to paste your own Application Key, Access Token, and Refresh Token, then click Save manually. Most organizations won't need this — it's for Hue developers who already have their own app registered at https://developers.meethue.com.

How lights appear in the picker

Every 5 minutes, Neowit polls your Hue bridge and refreshes the device list.
New or renamed lights show up on the next poll — usually within 5 minutes, but occasionally longer if Hue's metadata endpoint returns cached data.
To force an immediate refresh, open the integration from Settings → Integrations and click Synchronize.
Only individual lights are surfaced. Hue rooms, zones, and scenes are not controllable through Neowit today.

Control a light

Use the Set Light action in your workflow. All fields (device, on/off, brightness, color temperature, color XY) and its output are documented in Actions — Set Light.

To pick the target light dynamically — for example, based on a trigger's space — use the three-mode picker on the Device field. See References and templates.

What Hue actions can (and can't) do

Today:

On / off, brightness, color temperature, and color XY on individual lights.
One light per action. Chain multiple Set Light nodes to control several lights in sequence.

Not yet supported:

Triggers on Hue events (motion, light state changes, button presses).
Scenes, rooms, or zones — only individual lights.
Transition times and effects (fade, breathe, sunrise/sunset).
Reading current state — you can't build a condition like "if the light is on".
Batch or parallel updates — each Set Light is one HTTP call, executed one after the other.

When Hue stops working

Most problems show up as a red badge on the integration card in Settings → Integrations.

Bad credentials — the OAuth tokens were revoked or have otherwise gone stale. Open the integration, click Connect to Philips Hue again, and re-authorize.
Unable to connect — the Hue cloud API was unreachable during the last sync. Wait a few minutes and try Synchronize; if it persists, check Hue's status page.

Action-side errors show up in the execution's Logs panel:

"Not authenticated" — the integration is disconnected or the manual-token config is incomplete. Reconnect.
"Device not found" — the light was removed from the bridge after Neowit cached it. Click Synchronize, then re-pick the light in the workflow.
"Device does not have a light service" — the picker let you pick a motion sensor or another non-light device. Choose an actual bulb.
"Failed to update light: …" — a network or cloud-side error. Usually transient; retry the workflow.

See Integration disconnected for the general recovery flow.