Thanks, that actually was it!
With Font Awesome icons it is working!!!
1 Like
Any thoughts as to why the secondary_info is not working here? The icon is working fine, but I donāt see the secondary_info.
- type: 'custom:config-template-card'
config:
type: 'custom:hui-entities-card'
title: Investments
show_header_toggle: false
entities:
- type: custom:card-modder
style:
--paper-item-icon-color: "${var state = parseFloat(states['sensor.portfoliochange2'].state);
state <= 0 ? 'rgb(194, 39, 45)' : 'rgb(37, 145, 60)'}"
card:
type: custom:hui-sensor-entity-row
entity: sensor.pc_investment
secondary_info: "${states['sensor.portfoliochange2'].state}"
icon: "${parseFloat(states['sensor.portfoliochange2'].state) > 0 ? 'mdi:arrow-up-bold-circle' : 'mdi:arrow-down-bold-circle' }"
If you are using the built-in āhuiā entity rows, secondary-info can only be in (entity_id, last_changed). You can override with custom values if you switch the type to this:
2 Likes
That was actually the icon not being part of HA!
But I found something new, it does look like it is in conflict with HA border/shadow functionality maybe?
This is with the templatable config card:
This is without:
Check the bottom right corner on each ātemperature boxā
secondary_info is restricted to entity-id , last-changed
EDIT: I see @MizterB beat me to the answer 
And even has a better solution! Thanks!
Iām not seeing the differences. Can you perhaps highlight what youāre referencing?
Edit: I THINK I see it nowā¦I really need a better monitor 
Post on the repo with your full configuration of both, please, and confirm the differences. Thanks.
Sorry to disappeoint but no, I tried A LOT using the custom-secondaryinfo but it doesnāt seems to work!
I will post an example soon
Will do in few mins
Edit: Done
Okay actually I was wrong, I managed to make it work 
But I need some help please ^^
secondary_info: "${'OnePlus 5 Battery: ' + states['sensor.andrea_oneplus5_battery'].state + '% -' + states['binary_sensor.andrea_oneplus5_charging'].state === 'true' ? 'Charging' : 'Not Charging'}"
It always return āNot chargingā
Thanks
New entities option fixed the hold_action for me, thanks.
1 Like
That makes sense I think if you have a busy system. The template card is re-instatiating the card each time there is a state change if not restricted by the entities option. So the card could have been āgoneā while you held it.
Well that question opens up a whole can of worms.
I donāt even know what a hui-sensor-entity-row is except by experimentation and by inferring from the contents of this post.
I can find no reference to anything hui anywhere and I did ask the question recently and was told,
in order to
So to me they are some undocumented āmagicā.
Which all means that I have no idea why this config-template-card needs to use them or what syntax and options are available to use them natively.
So, cutting to the chase, to answer your question, I donāt know. But I have tried the following with the results shown. (Interestingly neither appears as a ācardā unless of course they default to a transparent background).
- type: custom:hui-sensor-entity-row
entity: sensor.bakerloo
secondary_info: last-changed
style:
--primary-text-color: yellow
- type: custom:hui-sensor-entity-row
entity: sensor.bakerloo
secondary_info: last-changed
A binary sensor has a state on or off. Your code has true which it will never have so thatās why itās always showing āNot chargingā.
2 Likes
ALL core cards/row/elements have a prefix/suffix that follows this convention:
hui-<card/row/element name>-<type card/row/element>
e.g.
hui-shopping-list-card
hui-sensor-entity-row
You can look in the create files here: https://github.com/home-assistant/home-assistant-polymer/tree/dev/src/panels/lovelace/common
1 Like
Thatās a good point, thanks!
But, why the first part of the text is not beinbg show?
My plan was to have an output like:
OnePlus 5: 85% - Charging/Not Charging
But it is showing only the final part, beside the wrong binary_sensor value
EDIT: Tested with āonā, it still only say āNot Chargingā
Had some fun, used this card to do a temperature-based color weather icon with pop-up forecast and weather map (browser-commander), thanks again for this great card!!
- type: state-icon
entity: sensor.dark_sky_minutely_summary
tap_action:
action: none
service: python_script.browser_cmd
service_data:
cmd: 'popup'
data: 'weather'
hold_action:
action: call-service
service: python_script.browser_cmd
service_data:
cmd: 'popup'
data: 'weathermap'
style:
top: 50%
left: 50%
height: auto
width: 2.6vw
background-color: "${var colors=['#442299','#3b0cbd','#3311bb','#4444dd','#e6ffff','#ccffff','#ffffff','#11aabb','#12bdb9',
'#22ccaa','#69d025','#aacc22','#d0c310','#ccbb33','#feae2d','#ff9933','#ff6644','#ff4422',
'#ff3311','#ee1100','#f80c12'];
var temp=parseInt((parseInt(states['sensor.dark_sky_temperature'].state)-10)/(70/20));
if (20>=temp>=0) colors[temp];else if (temp<0) colors[0];else colors[20]}"
border-radius: 100%
1 Like
Introducing Variables
You can now use the new variables configuration to create a list of reusable variables to hopefully help clean up your templates. See the updated docs on the repo for an example.
Have fun templating!
3 Likes
Further to my previous answer it doesnāt look like I can. I had guessed I would be able to, following the example given above by @arsaboo where he,
and changes the colour behind an icon:
If the answer is not too complex for this post, why can paper-item-icon-color be defined but not primary-text-color and is there any way to discover that information?
Should I change config to card? Seems like it would be more consistent with other cards.
- Keep
config - Breaking change to use
card
0 voters
2 quick questions on the new variables option:
-
whatās the scope of these declared variables? I have picture-elements card under config, will all cards inside that picture-elements āseeā the variables?
[Edit: Tested, all cards under config āseeā the variables] -
Is it possible to declare constants in variables option? Like:
type: 'custom:config-template-card' variables: - states['light.bed_light'].state - ('red') [Edit: Works, vars[1] will show 'red', thanks to Ian!! ]
TIA