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

Use of separate entities for charging state at card config level #314

Closed
CDRX2 opened this issue Aug 23, 2021 · 4 comments
Closed

Use of separate entities for charging state at card config level #314

CDRX2 opened this issue Aug 23, 2021 · 4 comments
Labels
enhancement New feature or request
Milestone

Comments

@CDRX2
Copy link

CDRX2 commented Aug 23, 2021

Using a secondary entity for charging state is already possible at the individual entity level. However, this feature is not yet applicable at a card config level.

I suppose having something similar to the filter function but for charging state could be a possible approach.

@CDRX2 CDRX2 added the enhancement New feature or request label Aug 23, 2021
@maxwroc
Copy link
Owner

maxwroc commented Dec 20, 2021

please provide an example how you would see such configuration

@CDRX2
Copy link
Author

CDRX2 commented Dec 20, 2021

I would imagine something like this:

charging_filter:
  include: # filters for auto-adding charging states
    - name: entity_id # entities which id ends with "_is_charging"
      value: "*_is_charging"

@maxwroc maxwroc added this to the v3.0 milestone Jan 3, 2022
@bcutter
Copy link

bcutter commented Jan 23, 2022

Exactly what I'm looking for. Please have a look at https://community.home-assistant.io/t/lovelace-battery-state-card/191535/157 for potential additional/helpful information.

@maxwroc maxwroc modified the milestone: v3.0 Oct 21, 2023
@maxwroc
Copy link
Owner

maxwroc commented Oct 21, 2023

Closing as a dupe of #365

@maxwroc maxwroc closed this as completed Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants