Open Kzmi92 opened 1 year ago
Unfortunately, the secondary_info
option will only work on entity rows, for example, those inside an entities
card. It's not a defined behaviour on cards so there's no way of telling where to put the secondary info, whereas, all entity rows that inherit from generic-entity-row
have a slot for secondary info.
You may be able to get what you need done with the template card https://github.com/piitaya/lovelace-mushroom/blob/main/docs/cards/template.md
Unfortunately, the
secondary_info
option will only work on entity rows, for example, those inside anentities
card. It's not a defined behaviour on cards so there's no way of telling where to put the secondary info, whereas, all entity rows that inherit fromgeneric-entity-row
have a slot for secondary info.You may be able to get what you need done with the template card https://github.com/piitaya/lovelace-mushroom/blob/main/docs/cards/template.md
The answer was just under my nose all this time, I even created custom combined sensors to display the value of 2 sensors on one line.
Thanks so much!
The problem
I can't seem to get this working with any single entity card, default lovelace or mushroom.
I'm trying to display a card that acts as a button for lights in the room. Below the icon, I would like to show the room temperature, but whenever I try to add my temperature sensor as secondary I get this error: Key "secondary_info" is not expected or supported by the visual editor.
I've tried all secondary info objectThomas Lovén's templates or Jinja2 templates, but none seem to work. When copy pasting an example from GitHub, it does work, so the integration seems to be installed and working correctly.
Is this intended to not work or am I missing something?
What version of Canary has the issue?
0.4.0
What version of Home Assistant are you running?
Home Assistant 2023.2.5
What version of the Frontend are you running?
Frontend-versie: 20230202.0 - latest
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
No response