This is just understanding yaml and it’s format. Once you fully understand how lists and dictionarys work in yaml, you’ll know where/how to use the > and templates. I’m sure there is some yaml tutorials out there that will help you guys more that I can.
sometimes its not just Yaml though, but also HA behaving unexpectedly, as I am experiencing with my other quest right now, using the templated time trigger. Perfect Yaml, even the config check accepts it, and even at startup, no error os thrown.
Well that’s cause you can’t template in that field. Good rule of thumb, if the word “template” isn’t in the field or in the parent field, you won’t be able to use templates. Also, you can’t simply add the word template and expect it to work, it wont. You can only place templates into template designated fields.
sure, I understand, read the docs etc. still feels unexpected, given the many people asking for that. Maybe an extra + on the feature request would help.
templated time trigger, or time trigger template. doesn’t get better than that.
oof, variable time triggers would be very hard to implement because the time determines when automations will trigger. Templates resolve after a trigger/change has occurred. So you’re in a “which comes first, chicken or egg” scenario.
because of the fact the template has to be evaluated first, and needs a time cycle for that, things become flakey? That would be too bad really, looks so attractive.
I would have thought that talking machine language these 2 would have been identical, merely using another representation.
Seems I would be forced to use @123’s suggestion for a timer after all…
What happens when you change the time? That’s the problem. Yeah the configuration may look the same, but when the timing changes realtime what comes first?