WTH does visibility for cards have so few conditions

Month of "What the heck?!"
1

Not sure if this has already been brought up.
However, I was so excited for the possibilities until I found out you can’t even have condition templates in the visibility for cards on a dashboard.

2

Why is there no option to use template conditions in the visibility tag or the conditional card, but is it available in automations?

1 Like
3

Duplicate from my part, I’m sorry. Yes I +1 this!

4

I would at minimum like to see a choice of and / or conditions. I don’t’ want to have to create binary sensors to trigger visibility.

5

This can be done already at this moment. Just very large;

visibility:
- condition: or
  conditions:
  - condition: and
    conditions:
    - condition: state
      entity: light.a
      state: "off"
    - condition: state
      entity: light.b
      state: "off"

  - condition: and
    conditions:
    - condition: state
      entity: light.c
      state: "off"
    - condition: state
      entity: light.d
      state: "off"
6

I’d also like to at the time condition. Like before or after 18 hours in stead of using a template hour sensor.

2 Likes
7

Templates would be great! Now i have to create a helper for every visibility that i want to use.

8 Likes
8

Has there been any update on this topic? I still haven’t found a way to use templates in visibility conditions.

1 Like
9

You can do this with a template helper, and then using that helper’s state in the visibility.

I +1 the feature request though, it’d still be nice to have it “in the same place” and to not pollute the entities, but it gets the job done.