Routines and saved fast paths

A routine is a saved sequence you trigger with a phrase, the Test button, or a webhook. A fast path maps a phrase or alias to a specific tool or device action. A scheduled task instead runs at a time; a monitor checks a condition.

Create and test a routine

  1. Open Routines beside Tasks in the sidebar, or Menu → Routines on mobile. Tasks → Open routines and Learn → Manage routines also open it.
  2. Choose + New routine, give it an ID and trigger phrase, then add actions. The ID is a slug; use the trigger phrase for the words you want to say.
  3. For HA Device, search by device or room and choose a supported control. Existing service calls remain available in the advanced editor.
  4. Set Target device if the routine should speak or play audio on a particular voice device, especially for Test or webhook triggers.
  5. Save, then choose Test. Test executes the saved actions, so start with actions you are ready to run. Check the actual result.

You can also ask “When I say goodnight, turn off the lights.” A paired voice device is only needed for audio actions; HA calls and waits can be tested without one. Saved routines can be edited or deleted from the same view.

Add a wait

Choose + Add action → Wait and enter seconds, minutes, or hours, from 1 second to 24 hours per wait. OE runs the earlier actions, schedules the remaining sequence, and releases the voice device for other requests.

Waiting runs appear in Tasks → Schedules as Continue routine: …. Delete that scheduled continuation to cancel it. Each trigger starts its own run with a snapshot of the remaining actions: changing or deleting the routine does not cancel already waiting runs.

Waits survive closing the browser and restarting OE. An overdue continuation runs after OE starts again; HA must be reachable when its action runs. Prompt actions run after the other actions and waits; if there are several prompts, the last prompt wins.

Webhook and Home Assistant triggers

Open the saved routine’s editor and copy its Webhook URL. An HTTP POST to that URL runs the routine. The URL grants permission to trigger it, so keep it private. Regen revokes the previous URL/token.

For example, an NFC automation on your phone can POST to that URL. The phone must be able to reach OE. A private connection is enough for your own phone; public access is only needed for callers outside that network. A webhook has no originating voice device, so select a Target device for audio.

Home Assistant can also trigger the same routine through its event connection; see Trigger a routine from Home Assistant.

Saved fast paths

Open Routines → Saved fast paths to review and delete saved device phrases, device aliases, and learned tool phrases. Ask the assistant to save a precise mapping, for example “When I say check the deals, run my store skill,” or ask it to forget a phrase.

A saved device phrase targets an exact device and action. Saving it does not operate the device. If that action fails, OE reports the failure rather than trying a different device. A matching routine takes priority over ordinary HA commands. Phrases that conflict with built-in requests fall back to normal routing. Local routing can avoid an extra model call; the invoked tool can still contact its own external service.

Common problems

  • Save fails: fix the field named in the error, such as a missing HA scene or an ambient file that has been removed.
  • The old sequence still runs: cancel its waiting continuation separately.
  • A phrase selects the wrong action: inspect overlaps in Saved fast paths.
  • Audio is missing: confirm the routine’s target is online and TTS works.
This site uses Just the Docs, a documentation theme for Jekyll.