Closed Mariusthvdb closed 2 years ago
deleted post above, because no longer an issue on that specific config
closing, made a few edits and the cards now remain within their outer boundaries.
adding the specific card type to the offending section ha-card.type-history-graph
:
- type: custom:hui-element
card_type: history-graph
card_mod:
style: |
ha-card.type-history-graph {
background: {{'green' if is_state('binary_sensor.family_home','on')
else '#636B75'}};
--secondary-text-color: {{'gold' if is_state('binary_sensor.family_home','on')
else 'black'}};
box-shadow: none;
margin: 0px -16px -16px -16px;
}
My Home Assistant version: 2021.11.5
My lovelace configuration method (GUI or yaml):
Yaml
What I am doing:
using a mod-card on a custom:hui-element for history-graph
What I expected to happen:
no error?
What happened instead:
Minimal steps to reproduce:
I understand the error (getting it because I use mod-card to encapsulate hui-elelement) but, but if I dont do that, and use the preferred method:
to widen the graph and lose the margins, the card shows fine only directly after the refresh, but overflows the outer card margins after a reload of that same page. This is consistent throughout the config on all core graphs cards.
Using the mod-card fixes it perfectly:
Error messages from the browser console:
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.
[X] 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.