Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

2.0.1/2 moves full card config based on individual mod

See original GitHub issue

My Home Assistant version: 0.XX.X 116.0

My lovelace configuration method (GUI or yaml):

yaml What I am doing:

  - type: entities
    title: System settings
    show_header_toggle: false
    style: |
      .card-header {color: var(--primary-color);font-weight: bold;}
    entities:
      - sensor.speedtest_download
      - type: custom:slider-entity-row
        entity: input_number.ha_delayed_startup
      - type: divider
      - entity: automation.update_available
        secondary_info: last-triggered
      - entity: automation.updater_notification
        secondary_info: last-triggered
      - type: divider
      - type: custom:hui-element
        card_type: markdown
        style: |
          .card-header {color: var(--primary-color);font-weight: bold;}
          ha-card {
            box-shadow: none;
            margin: -5px 15px 0px -15px;
          }
        title: Log tail
        content: >
          {{states('sensor.log_tail')}}

What I expected to happen:

show the above setup aligned (as it was up to 2.0.0)

What happened instead:

1 picture says it all:

Minimal steps to reproduce:

# The least ammount of code possible to reproduce my error
      - type: custom:hui-element
        card_type: markdown
        style: |
          .card-header {color: var(--primary-color);font-weight: bold;}
          ha-card {
            box-shadow: none;
            margin: -5px 15px 0px -15px;
          }

# End of code

couldnt really say, in the above code. Surely it is the style: with the margin settings. After having refreshed a few times, this sometimes goes way. And displays as it should (up to 2.0.0)

only to come back again unexpectedly. Have tested some more, and can conform it is the update from 2.0.0 to 2.0.1 causing this behavior. I’ll change the title of the issue accordingly

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.