Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Device Class Inclusion #881

Open
3 tasks done
klatka opened this issue Feb 9, 2025 · 0 comments
Open
3 tasks done

Support Device Class Inclusion #881

klatka opened this issue Feb 9, 2025 · 0 comments

Comments

@klatka
Copy link

klatka commented Feb 9, 2025

Checklist

  • I checked for similar existing requests (both open and closed) before posting.
  • My request is generic, other users may benefit from it too.
  • I will participate in further discussion about this feature and can test it (if requested) once it's done.

Proposal

Enhance the Scheduler Card by allowing device class-based inclusion, not just entity IDs, to simplify automation configuration and improve flexibility.

Problem Statement:
Currently, the Scheduler Card requires hardcoding entity IDs (wildcards are supported) for inclusion. However, Home Assistant’s entity ID system is inconsistent, making it difficult to manage dynamically changing devices. For example, adding new power outlets requires manually updating the configuration. Instead, allowing inclusion based on device_class (e.g., outlet) would ensure all relevant devices are automatically considered without requiring manual updates.

Proposed Solution:
Extend the current entity inclusion logic to support filtering devices by their device_class. This would enable users to include all devices of a certain type (e.g., all outlets) without specifying individual entity IDs.

Additional info

type: custom:scheduler-card
include:
  - climate
  - switch:
      device_class: outlet
  - sensor:
      device_class: temperature
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant