Yes this is correct except for the xxxx part, I just removed some information there. The automation itself runs when triggered, but not the scripts which are supposed to trigger.
So what makes you say the automation runs, but not the script it calls? I.e., what do you see that leads you to believe the automation triggered, and at the same time, what do you see that indicates one of the scripts did not get called? FWIW, I don’t see anything wrong with your automation, at least syntactically. Have you tried triggering the automation manually to see if one of the scripts runs? Have you tried starting the scripts manually to see if they do what you expect?
I can see in the logbook that the automation is triggered and I can trigger the script manually and everything works. But when the automation is triggered none of the scripts actually runs.
Ok, thanks. Hmm, very interesting. So one thing I’m not sure about is, will it say the automation runs, even if the conditions evaluate to false??? Going on the assumption that it does (although I had assumed the opposite), how about temporarily removing or commenting out the conditions of the automation? If you do that, does it work? If so, then apparently none of the conditions are evaluating to true. If it still doesn’t work, then I’m stumped. (Or, I know, probably a stupid question, but is the automation on?)