#Questions and Issues with Automation->Script Workflows.

1 messages · Page 1 of 1 (latest)

royal arch
#

My automations and scrips were a mess for a long time, I had some functionality happening fully in automations and other automations triggering scripts that had the functionality.
A few weeks ago I had the idea to consolidate my setup so that it was consistent. I used the VS-Code Addon to download the yml files for my automations, scenes and scripts and then put them in to Claude to restructure them.
This mostly worked, although a few are having issues, possibly due to missing devices in their flows, andso I'm not sure if I've over-complicated the whole thing; so I'm looking for a second opinion. I'm not sure if I'm bordering, or am actually in, the land of templating.
Attached are my current yml files. What I'm trying to do is have my:

  • automations be purely for triggers with no logic of what actions actually get performed
  • scripts be the logic of which checks need to be performed (although this may be better in the automation?) and be where the actions get performed
  • scenes be where I tell scripts which state a device should be in, like a blind being at 50% or a light being at 15%
    I'm happy to provide screenshots or any other information if helpful.
📎 automations.yaml 📎 scenes.yaml 📎 scripts.yaml
vale bough
#

I don't think that's a great approach... For starters, you already miss "triggered by" for your automations and can't access other trigger variables as well. And it's quite some extra work to always make an automation and a script. Which probably turn out very specific so are hard to reuse.

So in my opinion you're better of having most in automations and just make s script for stuff you want to recycle in multiple places

royal arch