Add filter options to entity and device selectors

[piitaya]

Breaking changes

Entity filters are now inside filter property but we can add backward compatibility.

Proposed change

• Add filter config for entity selector to allow array of filter.
• Add filter config for device selector to allow array of filter.
• Allow device_class list for entity filter config

It fixes somes issues :

• Include input_datetime domain and sensor domain with timestamp device class : Support for timestamp sensors in time trigger automation UI #15292
• Add multiple manufacturer and model for device if we extend this to devices : Add option for multiple models and manufacturers #15104

New schemas

interface EntitySelectorFilter {
  integration?: string;
  domain?: string | string[];
  device_class?: string | string[];
}

interface DeviceSelectorFilter {
  integration?: string;
  manufacturer?: string;
  model?: string;
}

export interface DeviceSelector {
  device: {
    filter?: DeviceSelectorFilter | DeviceSelectorFilter[];
    entity?: EntitySelectorFilter | EntitySelectorFilter[];
    multiple?: boolean;
     /** For backward compatilibity **/
    integration?: DeviceSelectorFilter["integration"];
    manufacturer?: DeviceSelectorFilter["manufacturer"];
    model?: DeviceSelectorFilter["model"];
  } | null;
}

export interface EntitySelector {
  entity: {
    multiple?: boolean;
    include_entities?: string[];
    exclude_entities?: string[];
    filter?: EntitySelectorFilter | EntitySelectorFilter[];
    /** For backward compatilibity **/
    integration?: EntitySelectorFilter["integration"];
    domain?: EntitySelectorFilter["domain"];
    device_class?: EntitySelectorFilter["device_class"];
  } | null;
}

Example

{
  entity: {
    filter: [
      { domain: "input_datetime" },
      { domain: "sensor", device_class: "timestamp" },
    ]
  }
}

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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request: Add documentation for entity and device filters home-assistant.io#26145

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

[bramkragten]

This needs updating to look at filter: https://github.com/home-assistant/frontend/pull/15302/files#diff-a53e33f869a5583dacb23f19dd48065fa89e75b6781effc14cf29289d91652f8R68

[bramkragten]

Can we rewrite the old schema to new schema instead, so the code only needs to handle the new config and not care about the old config.

So when we get

entity:
    domain: hue

We create

entity:
  filter:
    domain: hue