OR + AND conditions for Conditional Card

Feature Requests
63

i think this feature never comes, the request 4 years old ^^

+1!!!

64

Itā€™s start to change but OR still missingā€¦

65

+1!!

Trying to make a button only appear if a device is on - issue is, the device has many different reported states when on so, setting an OR list would solve this.

Now Iā€™m going to have to make a separate automation and helper boolean switch that will turn on off depending on the states of the device. Then have the conditional card reference the boolean switch to see if it should be visible or not.

Seems to be a lot of requests for this going back 4 years now.

66

+1

Just adding to this request since I have tons of Miflora plant sensors around the flat/balcony where I want to keep track of moisture AND battery level, so either of them under a certain threshold should bring up Olenā€™s flower card.

67

For that you could avoid the or with the use of state_not, provided you are able to list all the other states.

68

+1 for ā€˜orā€™
(or better yet, template conditions)

69

+1 for or too from my- The only workaround is now a helper, that simulates the OR and is then the condition in the conditional Card. It would be much easier with an OR ā€¦ or better template condition).

70

I wonder, why the latest improvements in this card added/rebuild further options instead of switching to existing condition schema? Just tested it again and do not see the benefit here. But most probably I only miss it.

71

I canā€™t believe OR still isnā€™t available here. A respectful request for it here!

1 Like
72

+1 miss this a lot!

1 Like
73

+1 from me - want to show a header if any motion sensor has motion detected

1 Like
74

+1 want to show a button if weather warnings from different sources exist. Couldnā€™t believe it couldnā€™t be done easily!

75

Guys. Please check the conditional card once again.

76

I am a newer user to HA, and I fully expected the Conditional card would have a switch to make the condition list ALL or ANY when I tried to use it the first time, as that is how I have seen that designed in other interfaces.

Making a helper is pretty easy, but it still wont work for me: I wanted to group ā€˜update.ā€™ (not ā€˜sensor.ā€™) entities, and that is not supported either.

I guess I am stuck waiting for either of these functions to be implemented, unless there is another way.

77

You can make template binary_sensors that replicate the functionality you want for the time being.

If you need help with that, I can assist, but please make a separate thread.

Also, old school groups (YAML only) have the ability to do this as well.

1 Like
78

Just bumping into this topic and seeing there are still recent requests to add it. But isnā€™t this already implemented?

I see an OR condition in the dropdown at the bottom. After playing around with it a bit, it seems to work just fine?

This is on Home Assistant Core 2023.12.3 , not sure when it got added.

image
image998Ɨ566 23.8 KB

2 Likes
79

Closed as implemented in 2023.12.

e.g.

  - type: conditional
    conditions:
      - condition: or
        conditions:
          - condition: state
            entity: binary_sensor.co_alert
            state: 'on'
          - condition: state
            entity: binary_sensor.rookmelder
            state: 'on'
13 Likes