We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem: Currently keys are "just" shown plain as they are in the database.
This leads to very uncomfortable reading as well as wrong values (because the timezone is not considered!) when it comes to dates/times.
Example:
type: conditional conditions: - entity: sensor.dwd_wetterwarnung_current_warning_level state_not: '0' card: type: custom:entity-attributes-card title: ❗ Wetterwarnung ❗ heading_name: ' ' heading_state: 'Aktuelle Warnung(en):' filter: include: - key: sensor.dwd_wetterwarnung_current_warning_level.warning_1_name name: ▶ - key: sensor.dwd_wetterwarnung_current_warning_level.warning_1_headline name: ' ' - key: sensor.dwd_wetterwarnung_current_warning_level.warning_1_description name: ' ' - key: sensor.dwd_wetterwarnung_current_warning_level.warning_1_start name: 'Von:' - key: sensor.dwd_wetterwarnung_current_warning_level.warning_1_end name: 'Bis:' - key: sensor.dwd_wetterwarnung_current_warning_level.warning_2_name name: ▶ - key: sensor.dwd_wetterwarnung_current_warning_level.warning_2_headline name: ' ' - key: sensor.dwd_wetterwarnung_current_warning_level.warning_2_description name: ' ' - key: sensor.dwd_wetterwarnung_current_warning_level.warning_2_start name: 'Von:' - key: sensor.dwd_wetterwarnung_current_warning_level.warning_2_end name: 'Bis:'
Very hard to read:
Proposal: Add out of the box formatting option for keys to handle the way date/time keys are shown.
Implementation example: See https://github.com/benct/lovelace-multiple-entity-row#formatting which is able to create perfectly readable output
The text was updated successfully, but these errors were encountered:
What do you think about this @iantrich ?
Sorry, something went wrong.
No branches or pull requests
Problem:
Currently keys are "just" shown plain as they are in the database.
This leads to very uncomfortable reading as well as wrong values (because the timezone is not considered!) when it comes to dates/times.
Example:
Very hard to read:
Proposal:
Add out of the box formatting option for keys to handle the way date/time keys are shown.
Implementation example:
See https://github.com/benct/lovelace-multiple-entity-row#formatting which is able to create perfectly readable output
The text was updated successfully, but these errors were encountered: