WTH I can't easy simulate automations?

Month of "What the heck?!"
1

Ok I made my nice automations, but edge cases are always difficult to test.
Sure I can go to developer tools and set special states, but I need to switch many windows and find things around. I have hundreds of devices and dozens integrations, not easy to check everything.

In the automation view I now have the lovely traces view, where I can see how things are going, why not adding a simulation mode where I can easily Change triggers and states used in that single automation, and see how it behaves.

We want to go ever more pro? I can set different values for the states and save them together with the automation, so if I edit it in the future I can still quickly check that everything works. Without having to wait that day when the temperature reached X degrees, the sun is doing something strange and one entity is not available for some reason.

We can call it unit tests for automations?

2

There’s a similar suggestion over here: WTH I can’t test the trigger of the automation?

2 Likes
3

Kind of a heavy ask here.

Traces are very nice for debugging, but I can debug only cases that have happened. But sometimes I want to debug some situation that rarely happens. Say I want a certain action to happen when my camera detects a dog, Right now I need a literal dog in front to my camera to check if my automation works correctly. I want to inject an arbitrary fake YAML as a trigger for automation in the same way I can change the state and attributes.