Building Automations with the Visual Editor
WoowTech ships with a point-and-click automation builder so you can wire up behaviors straight from the dashboard — no hand-written YAML required. The editor walks you through each piece of an automation in order: pick what starts it, layer on any optional checks, and finally describe what should happen.
What You'll Build in This Walkthrough
To make this guide reproducible for everyone, the example leans on the Random sensor integration. That helper emits a fresh number somewhere between 0 and 20 each time it refreshes, which means you can practice the entire flow even if you don't own a single piece of hardware yet.
Creating Your First Automation Step by Step
- Open Settings > Automations & scenes, then click the Create automation button tucked into the bottom-right of the screen.
- From the menu that appears, choose Create new automation to start from a blank slate.
- Now attach a starting event. Click Add trigger, type
numinto the search box, and pick Numeric state from the matches. - Fill in the trigger details:
- Point the Entity field at
sensor.random_sensor. - In the Above box, enter10. The automation will now fire whenever the sensor reports a reading larger than ten. - Scroll down to the Then do block and click Add action to describe the outcome. Choose the option that sends a persistent notification.
- Give that notification the text:
Sensor value greater than 10. - Click save, then type a clear, memorable name for the automation and save once more.
The instant you store it, the automation is live — anything you create or tweak through the interface takes effect immediately, with no reload required.
When UI Automations Don't Show Up
Built something in the editor but it never appears? Nine times out of ten the
culprit is that your main config file isn't pulling in the generated
automations. Confirm that configuration.yaml carries the following include
directive:
automation: !include automations.yaml
After adding it, reload your automations (or restart) and the entries you created in the editor should surface.
Where to Go Next
- The broader automation documentation digs into triggers, conditions, and actions in far more depth.
- Each integration's reference page lists the entities and services it exposes, which you can consult while filling in trigger and action fields.
Building Automations with the Visual Editor
WoowTech ships with a point-and-click automation builder so you can wire up behaviors straight from the dashboard — no hand-written YAML required. The editor walks you through each piece of an automation in order: pick what starts it, layer on any optional checks, and finally describe what should happen.
What You'll Build in This Walkthrough
To make this guide reproducible for everyone, the example leans on the Random sensor integration. That helper emits a fresh number somewhere between 0 and 20 each time it refreshes, which means you can practice the entire flow even if you don't own a single piece of hardware yet.
Creating Your First Automation Step by Step
- Open Settings > Automations & scenes, then click the Create automation button tucked into the bottom-right of the screen.
- From the menu that appears, choose Create new automation to start from a blank slate.
- Now attach a starting event. Click Add trigger, type
numinto the search box, and pick Numeric state from the matches. - Fill in the trigger details:
- Point the Entity field at
sensor.random_sensor. - In the Above box, enter10. The automation will now fire whenever the sensor reports a reading larger than ten. - Scroll down to the Then do block and click Add action to describe the outcome. Choose the option that sends a persistent notification.
- Give that notification the text:
Sensor value greater than 10. - Click save, then type a clear, memorable name for the automation and save once more.
The instant you store it, the automation is live — anything you create or tweak through the interface takes effect immediately, with no reload required.
When UI Automations Don't Show Up
Built something in the editor but it never appears? Nine times out of ten the
culprit is that your main config file isn't pulling in the generated
automations. Confirm that configuration.yaml carries the following include
directive:
automation: !include automations.yaml
After adding it, reload your automations (or restart) and the entries you created in the editor should surface.
Where to Go Next
- The broader automation documentation digs into triggers, conditions, and actions in far more depth.
- Each integration's reference page lists the entities and services it exposes, which you can consult while filling in trigger and action fields.