Closed akasma74 closed 4 years ago
Yes. That's what the template-entity-row does. I will not expand it with this feature.
@thomasloven you're the owner of this component and can do waht you think is right but don't you think things like that should be reflected in the documentation? I chose this component consodering its ability to hide itself conditionally and then spent some of time trying to make it work. I've learnt something and I'm not complaining, but I believe there were and will be many others goint this route.
The thing is that would require special cases for every type of entity row, and that's an effort I'm not ready to put into this. The conditional hiding is not the main feature of this row - that's to display the value of a template.
Maybe try this instead?
The thing is that would require special cases for every type of entity row, and that's an effort I'm not ready to put into this.
I agree.
The conditional hiding is not the main feature of this row - that's to display the value of a template.
I understand it but wanted to use that feature is it's there
Maybe try this instead?
well, I didn't want to create a complex layout out of multiple horizontal/vertical stacks.
currently I use exactly that card and it looks huge so I'll need to apply card-mod to reduce space between elements - I presume it would be neater using this entity_row.
That link wasn't for the conditional card, but for the conditional entity-row, which was added in 0.105 or 0.106, I think.
It's not templateable, though, but I may create another entity row for that at some point... unless someone else does first.
That link wasn't for the conditional card, but for the conditional entity-row, which was added in 0.105 or 0.106, I think.
Yes, I remember that. My bad. Looked at it and that's almost exactly what I need, just tried.
Cannot use it as there is a glitch - look at the first slider
It's not templateable, though, but I may create another entity row for that at some point... unless someone else does first.
That would be great if you could, I believe there are many use cases which require entity-row rather than card.
In my particular case no templating was needed to hide an entity based on state of another entity.
I accomplished it by using your card-mod to add display: none;
to those input_number
s, here's how it looks
Thanks again for explaining the situation and following up, really appreciate it!
HA: 0.106.6 This component: 1.1.0 Browser: Safari, Chrome OS X 10.11.6
When I use this entity row for
input_number
, I get a read-only representation of it regardless of itsmode
. Here is my config: