OR + AND conditions for Conditional Card

Feature Requests
42

While OR future is not yet available to condition cards, there is a work around to get this functionality :partying_face: Basically all you need to do is to make a binary sensor by putting the below code in your configuration.yaml file

template:		 
  - binary_sensor:
      - name: trash_collection
        state: >
          {{ is_state('sensor.trash_collection', '2')
             or is_state('sensor.recycling_collection', '2') }}

After that you will be able to use binary sensor to in conditional card to make it appear/disappear. Below will be your conditional card.

type: conditional
conditions:
  - entity: binary_sensor.trash_collection
    state_not: '2'
card:
  color: var(--primary-color)
  color_type: label-card
  name: Trash/Recycling
  type: custom:button-card
43

Your solution is great, but it was already mentioned as a solution in the very beginning of this thread two years ago.

I want to highlight that this thread is about making it clear to HA devs that we would appreciate having native support for more complex conditionals without requiring setting up a binary template sensor.

8 Likes
44

Same use-case here.

46

Check out the response from @ASNNetworks above. You just have to set it to state_not. Everything is working perfectly for me now!

47

Still not enough I think. I want to display a card if any one of my alerts is not idle (can also be on or off):
( x != idle OR y != idle OR z != idle )
If I only can use AND instead of OR I would need to negate the whole expression:
!( x = idle AND y = idle AND z = idle )
But the condition card doesn’t support to negate the whole expression.

48

+1 here.
I just went to set up a conditional card with an OR condition, and found out it wasn’t available.
I have no problems doing a workaround, but this should be something native on the card.

2 Likes
49

Five years on and still no OR? Anyone know of a workaround?

50

Try with lovelace-state-switch from HACS

51

+1 - simple use case: Include a testing flag with every conditional, so that I can easily turn on all conditionals. I am using a whole lot of conditional to only show problems/infos/warnings and this would be helpful for testing

52

+1 for the or feature.

I’ve tried all variations so far mentioned above.

I have multiple entities I want to monitor and jus have one conditional card if any are not what they should be. Some entities would normally show connected, on, available or whatever else and the opposite when something is wrong.

3 years + on. Any chance this could be addressed :slight_smile:

53

calculating 2023 - 2019 = 5. okay. that is some creative expression. 4 full years until now.

but i need that feature too.

Weather warning and advance weather warning should be all in one card. but i cant

2 Likes
54

+1

This would come in handy right now.

55

oh yes, this function would be really necessary.

56

Yes please!

57

I solved this using Switch helper “input_boolean” and automation script with various conditions switching the helper. Helper can be used as condition in Conditional Card


58

I think template support for the condition in the card would be the ultimate solution. Any complex criteria can be defined then.

59

Thanks for pointing that card, going to give that a try :+1:

60

You can define any complex criteria using automation script - any variation of condition. Input_boolean is just middle man to show or hide the card. And you still can use entity filter card. In my use I am able to set to show card in case of any water sensor is not “off” and only “not_off” sensors are shown. So it includes also “unavailable”, “on”, “unknown” situations.

61

Yes I can confirm this card basically is what the condition card should be :blush:

62

Not sure why nobody mentioned it before. Easiest workaround is to define a helper with “group”.
Within the group settings you have the option to set “all entities” (yes/no). With this option you can model the OR condition. All you need to do then is to add the helper as a condition and you got the OR modelled.

However: still +1 obviously, as every work around is just not the same as the actual work :slight_smile: