There are 3 cases:
-- hui-element with card-mod using config.entity - works OK, style is applied;
-- mod-card contains hui-element; card-mod is defined on the mod-card's level - works OK, style is applied;
-- same as above; card-mod using config.entity - does NOT work, style is NOT applied, there is an error:
Why placing hui-element inside mod-card?
Assume I need a conventional toggle-row (or input_select, or slider) with some settings & card-mod in MANY places.
Then I create a decluttering-card with hui-element containing a conventional row.
Since I need to specify card-mod and decluttering-card does not contain a ha-card, I have to insert hui-element inside mod-card.
Here is a principal scheme:
So, using config.entity causing an error & a whole card-mod breaks if hui-element is inside mod-card.
I guess this change happened recently (starting from this year).
Error messages from the browser console:
See above.
By putting an X in the boxes ([]) below, I indicate that I:
[] Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.
My Home Assistant version: 2022.9.4
My lovelace configuration method (GUI or yaml): yaml/storage
What I am doing: Placed
hui-element
card insidemod-card
, then trying to useconfig-entity
in card-mod.Consider this example:
hui-element
with card-mod usingconfig.entity
- works OK, style is applied; --mod-card
containshui-element
; card-mod is defined on themod-card
's level - works OK, style is applied; -- same as above; card-mod usingconfig.entity
- does NOT work, style is NOT applied, there is an error:Why placing
hui-element
insidemod-card
? Assume I need a conventional toggle-row (or input_select, or slider) with some settings & card-mod in MANY places. Then I create adecluttering-card
withhui-element
containing a conventional row. Since I need to specify card-mod anddecluttering-card
does not contain aha-card
, I have to inserthui-element
insidemod-card
. Here is a principal scheme:So, using
config.entity
causing an error & a whole card-mod breaks ifhui-element
is insidemod-card
. I guess this change happened recently (starting from this year).Error messages from the browser console: See above.
By putting an X in the boxes ([]) below, I indicate that I:
[x] Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
[x] Have made sure I am using the latest version of the plugin.
[x] Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.
[] Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.