I am assuming you have custom cards occupying the sections with gaps?
If so, you need to modify the row height for those cards, especially if you are using the Sections dash. You can move to a Masonry dash or as Mariusthvdb mentioned, use a custom layout/stack card to control the Sections layout.
OK, I’ve just created an example for you. Took me 2 minutes with standard components:
What people would like is for sections to behave like masonry. But masonry limits people to 3 columns …
I’m sorry, but I think you misunderstand the whole point. People want to have section cards of different heights and THOSE to have no gaps under each other.
Otherwise we’re back to kung-fu of making all the cards the same size, which is unnecessary jumping through hoops.
I understand the entire point with this thread! I’d post a feature request via github.
OK, so (and I’m saying this as politely as possible, but it’s impossible to not sound sarcastic here) : why did you ask me to resize the thermostat card ?
I didn’t, I said the largest card.
Just a heads up, feature requests go here: home-assistant · Discussions · GitHub
Thanks. (extra chars to fit the minimum 10 chars)
Unfortunately when cards are containerized, there has to be limitations with both width and height. That is the source of your issue and would require modifying your dash format to include stack cards.
created a “feature request” for this:
yeah, its probably the reason I have no columns in my production views…
I have this as skeleton on all of those:
sections:
- cards:
and have no empty space between cards (‘gap’) anywhere. Admitted, I dont stretch the view on desktop to be ultra wide. I just want my views to be predictable, and identical on desktop and mobile, so there is but one way…
in my UI test dashboards I see this, even while using the compact mode. Of course this is hideous, and I still cant understand why this would be hailed as the ultimate UI for HA:
since this has been the foundation for a couple of years now, (and probably wont change) I suppose your best bet would still be using custom:layout-card I linked above
