No reason to get that upset.
The request was to support your FR with five real world examples. You haven’t provided even one.
So can you even show only one example? Maybe that would help.
I’m a software engineer and since 2019 I’m in a big german HA support group. Do you expect that I copy 5 postings from people to prove that I’m right? This sound pretty silly to me.
And it seems that people want me to fight for that feature request. No, I don’t fight for it.
I already described the typical problem: somebody wanted to turn on the lights when it is dark and between 8:00 and 23:00. So he coded a trigger “sensor.light<100” and a condition “time between 8 and 23”. That never worked in the morning when it was still dark from the night.
Nobody should fight anybody.
I think we can all agree the problem exists: non-techie users are confused by the “trigger/event” notion.
Now what can be done about it.
Maybe new platforms that would combine conditions with an implicit 1 minute trigger that’d check them, a bit like the template trigger when now() is used?
We all know it can be done a dozen way, technically. It’s just a matter of creating a YAML idiom that can be understood by the many.
EDIT: We already have “condition” in actions and consitions, why not make it a trigger platform as well, with this implicit Time Pattern trigger? +1 for consistency…
1 Like
Time will tell if baseless claims convince the development team to permit this change.