Yes, really. I had a look at the source code to see how hard it would be to add a wildcard and got somewhat surprised to find it already there.
@Burningstone you currently cannot leave out to if using for, the YAML will be marked as invalid.
1 Like
So then this functionality already exists (not 100% to what OP wants, but close). I think we just need to update the docs. Maybe add a ‘wildcard’ section, and then have a link on each property that supports wildcards.
2 Likes
Ah, ok, I’m mainly using AppDaemon for automations and there no “to” state is required, so I thought maybe it’s the same for Hone Assistant.
Two PRs open to address things discussed in this topic:
That is great news @frenck
From what I can read in the PR we will still be able to do the to: “*”
We should still have that documented so it becomes clear where the “*” is allowed in triggers in addition to the two PRs. Not any additional code change. Just documentation change to what is already in the code.
I could do a PR just on the docu change but I am not sure if the “*” is only allowed in to: or it needs to be added additional places in the docu
There is no reason to… as leaving them out results in the same.