You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when using a template on the attributes of the binary_sensor.knmi_zon, there are 2 issue, of whihc 1 is really of importance since it impacts use of that attribute:
The attribute really should only contain the value, so we can use it in other Dashboard cards, or even template/automation logic
please consider taking out the unit of the state of the attribute.
compare Buienradar entity for that:
secondary suggestion: consider the attributes names to use underscores and lower characters only. Frontend takes care f showing those correctly, but it would be following HA design better to be able to use:
I agree it makes sense for automations/graphs that the unit is omitted for state attributes.
Be aware that in your example, comparing Buienradar, you're comparing a state with an attribute (unit_of_measurement) to something that is called extra_state_attributes, used by this integration.
I'm not sure if I want to rename the attributes (underscore), as that would be a breaking change. There are also built-in integrations that have spaces in attribute names, so I don't think it's really an issue.
Did you read the instructions?
The request
when using a template on the attributes of the binary_sensor.knmi_zon, there are 2 issue, of whihc 1 is really of importance since it impacts use of that attribute:
contains the unit %, which is not as it should.
The attribute really should only contain the value, so we can use it in other Dashboard cards, or even template/automation logic
please consider taking out the unit of the state of the attribute.
compare Buienradar entity for that:
secondary suggestion: consider the attributes names to use underscores and lower characters only. Frontend takes care f showing those correctly, but it would be following HA design better to be able to use:
thanks for considering
Additional information
this is an example of a config that wont show:
or eg the bar card:
which seemingly shows the correct attribute, but not the graph nor the color... because the value is not as it is expected to be,
The text was updated successfully, but these errors were encountered: