thomasloven / lovelace-layout-card

🔹 Get more control over the placement of lovelace cards.
MIT License
1.08k stars 127 forks source link

All cards in one column at first load of the dashboard #214

Open Kedryn opened 2 years ago

Kedryn commented 2 years ago

My Home Assistant version: 2022.09.X

Layout-card version (FROM BROWSER CONSOLE): 2.4.2

What I am doing: First load of the HA Dashboard

What I expected to happen: Everything in place where it should be

What happened instead: All cards are on one column in the middle of the screen An F5 does not fix the problem. Instead, if the layout is right, it put it back to one column only. Resizing the browser window to a point where the columns quantity should change (enlarging it or even shrinking it) does fix the layout

Minimal steps to reproduce: dunno

# The least ammount of code possible to reproduce my error
  - type: custom:layout-card
    layout_type: masonry
    layout:
      width: 300
      max_cols: 4
# End of code

Error messages from the browser console:


By putting an X in the boxes ([X]) below, I indicate that I:

nelmdog commented 2 years ago

On Home Assistant 2022.10.5 and lovelace-layout-card version 2.4.4 I too experience this behaviour, with refresh failing to resolve the issue. To get it to display the expected layout I found that switching to another dash and back again works.

Yohan-Janolin commented 1 year ago

I have this issue too. Clicking on "Modify dashboard" resolve the issue but it's quite annoying to do it every time

KyleStilkey commented 1 year ago

I have the same issue, on first load all panels are in 1 column but opening and closing the sidebar fixes this for me, bit annoying.

lennon101 commented 1 year ago

Same problem for me (version of OS and frontend listed below). Refreshing the webpage usually fixes the issue. I'm using mushroom cards in vertical/horizontal stacks for a lot of the dashboard settings. Here's a screenshot showing the issue:

Home Assistant 2023.7.1 Frontend 20230705.1 - latest

image

lennon101 commented 1 year ago

@thomasloven this issue has been open since Oct 7, 2022. Any movement on this or ideas on what is going wrong? Thanks!