Tater Assistant Docs
Core profile

Automation Core

Visual event-to-action automation builder powered by Tater's shared rooms, integration devices, notifications, cameras, and voice destinations.

Automation engine v1.6.0 No required fields Internal runtime
Core role

What this core is for

Automation engine

Highlights

Behavior in the current codebase

  • Builds automations from the same integration categories, device actions, rooms, and aliases used throughout Tater.
  • Triggers include state changes, on/off and open/close transitions, motion, people, vehicles, animals, packages, faces, license plates, doorbells, text matches, connection changes, and numeric thresholds.
  • Actions can control devices or categories, send notifications, speak on satellites or announcement targets, and describe a camera image with Tater's vision model.
  • Reusable message fields expose event context without requiring users to hand-write integration-specific payloads.
  • Cooldowns, enable/disable controls, manual test runs, last-run state, and execution history make each rule observable from the Core UI.
Related Verbas

Direct core support

This runtime component mainly handles orchestration rather than exposing its own direct Verba target.

Settings

Configuration schema

This core declares a CORE_SETTINGS schema, but it does not currently require any explicit fields.

Automation builder

Build useful home flows without tying them to one provider

Automation Core consumes Tater's generic device registry, so the same rule shape can work with Home Assistant, Hue, Shelly, UniFi Protect, and future integrations.

DevicesEventsThresholds

Choose a trigger

Start with a device event or condition exposed by an enabled integration.

  • Pick a category and device from the shared catalog instead of entering provider-specific identifiers by hand.
  • Use event filters for camera detections or state filters for lights, doors, motion, connectivity, text, and numeric values.
  • A cooldown prevents repeated sensor chatter from firing the same actions too frequently.
Device controlTTSVision

Compose actions

One rule can control the home, speak, notify, or ask vision what a camera sees.

  • Control an individual device or a compatible room/category group using advertised integration actions.
  • Send a message through notifier portals or speak it on selected native satellites, stereo pairs, or announcement players.
  • Camera actions can capture a current image, generate a short description, then use that result in a notification or spoken announcement.
Back to cores Verbas Portals Tater Voice Cores Home