Use current entity in state card conditions

[piitaya]

Proposed change

Adds a "Current entity" option to the entity picker in state and numeric state visibility conditions. It shows up when editing a condition on a card that has a main entity (tile, entity, light, thermostat, entity badge, entity heading badge...). Selecting it makes the condition use whatever entity the card is bound to.

On the map card, the state picker in conditions now autocompletes from the entities configured on the card instead of a static list.

Screenshots

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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to backend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• There is no commented out code in this PR.
• I have followed the perfect PR recommendations
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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

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

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[timmo001]

Not sure if we need the extra dropdown here, wouldn't it be better to just automatically pick the entity and let the user change the option naturally? This adds an additional step that isnt necessary IMO

[timmo001]

Also merge conflicts to resolve

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[piitaya]

@timmo001 Yeah, It can be an extra item at the beginning of the list of entity picker. I'll check that 🙂 And if selected, it set entity to undefined.

[timmo001]

Much better, I still think the entity could just auto set on add (and maybe prioritise the entity to the top of the list) but this is more descriptive of a "default" value to show as "Current entity"

Also a huge timesaver if you like to set visibility based on available state etc. for cards

[piitaya]

@timmo001 I like that we have 2 items in the list : one that set undefined and the other that set the entity id. Otherwise it's confusing.

Allowing undefined instead of auto-set the entity also improve the yaml usage.

[timmo001]

Yeah makes sense, it doesnt dupe when searching so its good there too