Hello Atlantir,
- First learn to search for answers. Tips on Searching for Answers & Duplicate Topics in the Forum
- Also lots of help subjects in the Cookbook
- Automation writing: Understanding automations - Home Assistant
So the right way to write a Blueprint, (well let’s call it best practice and the method suggested in the docs), is to write an automation or script that does a simplified version of that you want first, then add the blueprint magic sauce. Getting the logic working is not always easy, and becomes obfuscated in all that variable substitution stuff, making everything frustrating.
Get what you want working with sample entities instead of !inputs, then make the blueprint out of that by adding the !inputs and variables and such. Try to avoid device triggers and selectors. You can make them work, but people tend to struggle with those when dealing with them outside of the GUI editor context.