Turn off lights at close

What this workflow does

• A schedule trigger fires at 19:00 local time on weekdays.
• The workflow sends "off" to each Hue light you've listed.
• Because the schedule is weekday-only, nothing runs on Saturdays or Sundays.

Simple template for any "do X on a clock" automation.

[SCREENSHOT] The finished workflow on the canvas: a Schedule trigger node connected to a chain of three Set Light action nodes, each labelled with its target bulb (Office — Reception, Office — Meeting room, Office — Open plan).

Prerequisites

• Workflows enabled for your organization. See Enable workflows for your org.
• Philips Hue connected and its lights visible in Neowit.
• A list of the lights you want to turn off — it helps to walk the office and confirm the bulb names match what you see in the Hue app.

Build it

1. Create the workflow

From the Workflows list click New workflow, name it Lights off at close, and open the editor.

2. Add the schedule trigger

1. Click Add node, scroll to Triggers, and pick Schedule.
2. In the node's settings, set the schedule type to Weekly.
3. Fill in:
   • Timezone — your office's IANA timezone, e.g. Europe/Oslo. Get this right or the trigger fires at the wrong local time.
   • Weeks — 1 (every week).
   • Trigger on days of week — tick Monday through Friday; leave Saturday and Sunday unchecked.
   • Trigger at hour — 19.
   • Trigger at minute — 0.

3. Add a Set Light action per bulb

1. Click Add node, scroll to Actions, and pick Set Light.
2. On the new node, pick the first bulb in the Device dropdown.
3. Set On to false. Leave brightness, color temperature, and color XY blank — you're not changing them.
4. Wire an edge from the Schedule trigger's output to this Set Light's input.

Repeat steps 1–4 for each additional bulb, wiring them in sequence: Schedule → Set Light A → Set Light B → … Actions run one at a time, in the order the edges connect them.

4. Test the run

1. Click Run workflow in the toolbar.
2. The Schedule trigger opens with an empty JSON payload. Schedules don't carry data, so leave it as {} and click Run.
3. The Logs panel shows each Set Light task going green (or red with an error). The real bulbs switch off within a few seconds.

Heads up: this is a real run — your lights actually go off. Pick an evening test window, or swap in a desk lamp while you're iterating.

5. Enable it

Click Save. In the dialog, turn on Enabled, add a short commit message ("First pass — weekday close at 19:00" works), and save. From the next weekday at 19:00 the schedule fires automatically. For the full Save flow see Publishing and versions.

Variations

• Skip holidays. There's no built-in holiday condition. The simplest workaround is to open the workflow the afternoon before a holiday, flip Enabled off, and flip it back on after. Nothing is lost — the definition and execution history stay intact.
• Different time per day. Chain a Time Of Day condition after the Schedule trigger to narrow the window further, or build a separate workflow per schedule.
• Turn on lights at open. Clone this workflow, change the schedule to 07:30, and set each Set Light's On to true. Add a brightness value if you want a soft start.
• Multiple sites. A single schedule trigger targets one timezone. For multi-site offices, build one workflow per site.

When it doesn't fire

If a weekday evening rolls around and the lights stay on:

1. Check the workflow is Enabled. The toggle lives in the Save Workflow dialog — a disabled workflow never receives schedule triggers.
2. Check the Executions tab. If a run is listed but red, open it to see which Set Light failed — see Philips Hue — When Hue stops working.
3. If there's no execution at all, double-check the trigger's timezone and weekday settings. 19:00 UTC is not 19:00 in Oslo.
4. See Workflow didn't run for more diagnostics.

Related

• Philips Hue
• Triggers
• Schedule a daily report