My window macro looks as follows. It starts with the descriptive title:
Code: Select all
OpenAtriumWindow_half
CloseAtriumWindows
delay (60000 ms)
OpenAtriumWindows
delay (20000 ms)
StopAtriumWindows
I think your suggestion would work. Definitely in the short term.
But I rather call it a work-around, because it can end up in many scenes, that may be awkward to maintain. A sequence of appliances to power on/off can become considerably longer.
Your second question is a realistic scenario indeed. My present thinking is that the initial call should be abandoned. I can imagine people push the wrong button, and want to correct an action asap.
Side note: I am not really in a hurry with this functionality. At the moment I am encountering sofar unexplained "hangs" of the system that force me to reinstall every other day. Son't know if it is the harware, ambient temperature, or running some of the modules together. What I observe is that after restart of Pi, startup of HA becomes increasingly slower, until it finally halts. I may come back on that in a different thread.