My Home Assistant version: 0.XX.X
2023.1.6
My lovelace configuration method (GUI or yaml):
Yaml
What I am doing:
styling (mod-card) a custom:swipe-card
What I expected to happen:
have swipe card show all defined cards
What happened instead:
using mod-card (even without any styling at all) causes the following pattern consistently
row 1: V | X | V | V
row 2: V | V | V | X | X
row 3: V | V | V | V
row 4: X | V | V | V
where X stands for a non displayed card.
Minimal steps to reproduce:
# The least amount of code possible to reproduce my error
- type: custom:mod-card
card:
type: custom:swipe-card
cards:
- type: custom:button-card
- type: custom:button-card
- type: custom:button-card
- type: custom:button-card
# End of code
Error messages from the browser console:
No errors at all
as if this isnt strange enough, I accidentally discovered I can make these individual (custom:button-card) cards appear, by adding some additional styling.
- type: custom:button-card
entity: switch.espresso_keuken
template: plattegrond
variables:
path: /ui-sub-views/keuken
picture: keuken_detail_klein.jpg
tooltip: Keuken
#fake style so mod-card does not take out this card......
# styles:
# card:
# - border-top: >
# [[[ return (states['binary_sensor.laundry_sensor_motion'].state == 'on')
# ? 'none' : 'none'; ]]]
This styling in itself is again very peculiar, because changing aspects inside that template (entity, return, state) can make it work or not work. No logic found just yet
also, I tried to take out the 5th card in the 2nd row , thinking it might have been asymmetrical, but that has no consequence.
By putting an X in the boxes ([]) below, I indicate that I:
[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.
For a more elaborate description I've made a community post.
My Home Assistant version: 0.XX.X 2023.1.6 My lovelace configuration method (GUI or yaml): Yaml What I am doing:
styling (mod-card) a custom:swipe-card
What I expected to happen: have swipe card show all defined cards
What happened instead:
using mod-card (even without any styling at all) causes the following pattern consistently row 1: V | X | V | V row 2: V | V | V | X | X row 3: V | V | V | V row 4: X | V | V | V
where X stands for a non displayed card.
Minimal steps to reproduce:
Error messages from the browser console:
No errors at all
as if this isnt strange enough, I accidentally discovered I can make these individual (custom:button-card) cards appear, by adding some additional styling.
This styling in itself is again very peculiar, because changing aspects inside that template (entity, return, state) can make it work or not work. No logic found just yet
also, I tried to take out the 5th card in the 2nd row , thinking it might have been asymmetrical, but that has no consequence.
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.
For a more elaborate description I've made a community post.