As I have worked on my automations in the new Automation UI (Absolutely love the changes in 2022.9!), I often find that I need to test a condition (which requires going to the dev tools panel and writing a template or something).
It would be really nice to have an option to test a condition or trigger (maybe with a couple of input options such as allowing you to input a trigger id or something) similar to how the actions can be run in the automation creator
There is a service to trigger the automation where you can optionally also take the conditions into account.
To test the trigger you can use developer tools > states and set the state you look for in the trigger
Yes, but this should be built into the automation creator… that is what my suggestion is
You are right about the conditions, I totally missed that those were added. But one thing that I still would like is the ability to test triggers with input data and everything built into the automation creator
If the automation triggers when it is open, you’ll see a bar and you can view the trigger data.
But the trigger itself is an event, not a state which can be checked, so you can’t test it like a condition
I know that… this is why I am posting in WTH… we SHOULD be able to test triggers and give the test trigger event data
But how do you see that? What do you actually want to test?
Well specifically when there is something like a trigger id involved in the trigger, I’d like to be able to select the 3 dots on the trigger and click run trigger. This would then create a test trigger event with data corresponding to what would trigger the event as written. I understand that this couldn’t really work with states, but this definitely would work with something like trigger id’s
1 Like
trigger id is quite easy, just add an additional trigger on a state change of an input boolean and give it the same trigger id.
All the other trigger variables depend on the trigger platform.
Was about to suggest the same - the option to trigger directly from the action menu to check whether the automation runs as expected (especially when handling multiple triggers with different branches in one automation).
Having to define a separate boolean and then manipulating it is certainly viable but just so much more cumbersome …