I’m writing a script to map my house with my Xiaomi vacuum by sending app_go_target commands.
I have to wait the vacuum status go to idle before sending the next app_go_target command with a wait_template instruction.
But I notice the wait condition is immediately true as it seems the vacuum take time to change is state. Currently I add a delay instruction as workaround but I search a cleaner way to do that.
Do you know if there is any way to detect in a template a rising or falling edge on status or attributes ?
Old message
Your link is a trigger that can’t be directly used in my case. when asking in 2019.
But recently we have a new instruction wait_for_trigger which associated by the trigger you have referenced will allow to cover the initial need.