Conditions state_filter support

[elupus]

Proposed change

Support state_filter for conditional cards. This behaves the same as entity-filter.

I think eventually state and state_not should probably be removed, but that would be an ugly breaking change.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

type: conditional
conditions:
  - entity: button.broadlink_mini_loxjie_display
    state_filter:
      - operator: 'in'
        value:
          - unavailable
          - jlkas
card:
  type: button
  tap_action:
    action: toggle
  entity: switch.test1

Additional information

• Solves this feature request: Conditional Card Configuration does not allow greater and less than #9809
• Documentation update: Add mention of state_filter for notification home-assistant.io#21519

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[finder39]

I believe this is possible already, albeit in a slightly different syntax:

- type: conditional
  conditions:
  - entity: vacuum.roborock_vacuum_a19
    state: ["unavailable", "unknown", "docked"]

- or -

- type: conditional
  conditions:
  - entity: vacuum.roborock_vacuum_a19
    state_not: ["unavailable", "unknown", "docked"]

[Inrego]

From my testings, the above syntax for checking multiple states do not work.

[zsarnett]

Same

[elupus]

I didn't not merge all if states into a huge if a and b or c and d or e and f. Since that would make it unreadable.

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[elupus]

Had forgotten about this one. Will resolve reviews.

[jlsjonas]

@elupus friendly ping :) (would've helped me out today 😬 )
Are you still up to getting this one through? If not I'll see what I can do! (thanks either way!)

[erkr]

So pitty this is not delivered 🥲

[ildar170975]

Is this PR reviewed already?

[elupus]

Yes though, i have not tested it much after i resolved comments.

[FaberO42]

This one seems to be stuck?

[bramkragten]

We discussed this, and think this is not the way to go.

• You are now using a filtering syntax for a condition, which is a different usecase.
• We recently updated the syntax of condition card, when we added the screen condition
• We think the syntax should be similar to the conditions syntax we use for automations
  For example:

  - condition: state
    entity_id: sensor.weather_precip
    state: "rain"
  - condition: numeric_state
    entity_id: "sensor.temperature"
    below: 20

We agree state_not should be removed and replaced by the a not condition like we have in the automation conditions too. This will need a migration.

Therefor I am going to close this PR, thanks for willing to contribute and if you want to continue based on the above, feel free to open a new PR!