Hi it would be nice to have buttons to manually activate triggers from the automations Dashboard while testing new Automation is out. Possibly with variables that can be set. Like a test environment.
Each automation’s overflow menu contains a Run command. It executes the automation’s action.
If you want more control over testing the automation, go to Developer Tools > Services and select Automation: Trigger. It allows you to specify whether the automation’s condition is included/excluded from the test (“Skip condition”).
For more information, refer to Testing your automation
NOTE
A more realistic test is to exercise the automation’s actual trigger section (because none of the above do that). For example, if it contains a State Trigger monitoring binary_sensor.door, you can go to Developer Tools > States and use it to force the binary_sensor’s state to on (thereby triggering the automation’s State Trigger).
FYI, you can set entity state manually under ‘Dev Tools → States → Set state’.
Hi I understand that I can run the automations from the menu and activate via the dev tools ( didn’t think about using states) but if they were available in the automations page then I wouldn’t need two windows to trigger and another to monitor. Thought it would be useful to be all be on 1 page
Previous versions of Home Assistant displayed a “Run Actions” button next to each automation in the Automations list. It’s now in the overflow menu.
In the four years that I’ve been using Home Assistant, I rarely ever used the “Run” button to test an automation. It only tests the action, not the condition, and will produce an error if the automation references the trigger variable anywhere in its action (refer to the documentation link I posted above). It’s only good for confirming action works for very simple automations. All this to say it’s the bare minimum for testing an automation thereby making it far less useful than one may assume it is.