-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: 'options:' doesn't work when I use 'template:' as filter #247
Comments
Check out this post, seems to work: https://community.home-assistant.io/t/auto-entities-automatically-fill-cards-with-entities/147801/511?u=asnnetworks |
Unfortunately not for Edit: I need it for something like this:
|
|
As you can see I doesn't register this issue. I try suggested solution and report result with my config. |
It would be really nice to be able to use |
I am not a creator of this great
Now you are asking about "use options along with a template". Moreover, the template may create TWO or more absolutely different types of objects - suppose, the generated list contains 10 pairs "entity-row + history-graph". Then how |
Fair points. I would expect that for That would behave consistently with how
My understanding, is that the list result from a template, still gets passed to the If you have multiple types of objects returned by a template, then absolutely you'd have to take manual control if you didn't want the |
I actually may be misunderstanding a piece of how template works. I don't think that it passes to the |
Imho using any options in any combinations should be at least harmless. |
I am not following you. There are 2 different ways to filter:
They cannot be combined. They may only be used to create a large list - part of it is created by |
You're right, I did some more digging. I was thinking that template was handled differently when it was rendered, but I'm seeing that it's not. Then yes, my vote would still be to make |
This is my current
This would be much nicer, in my opinion. But not necessary.
|
fully agree with this, I have exactly the same case... |
Copy that. I just want to show a secondary information for all my listed entities filtered by a template. Currently IMPOSSIBLE without going way deeper into templating which adds a lot of unneeded complexity. Would really prefer to see auto-entities allowing
Here the options is just ignored / not applied... 😞 |
If you're using the template filter you will have to add all options via the template. |
Could you please give an example of how to apply these options (working for include filter) to template filter? It overrides the icon depending on entity_id and its color depending on the state.
I guess it should be added to entity's attributes, but have no idea how. |
Excellent, thank you! |
I'd like to have the possibility to add 'options:' to the entities list when I filtered them using a template.
For example:
When I use the syntax with
filter: include: ...
thanoptions:
work fine as expected. But I couldn't find a way to add 'options:' to a template section.Would be great to have that.
The text was updated successfully, but these errors were encountered: