I did some re-ordering of the cards. It seems that the order of the cards is the issue.
Note: These are all desktop screenshots, not tablet screenshots
This is the original layout and how i prefer it, but it cuts off the 4th button on the tablet version of the companion app.
Perhaps i can try putting these back in a grid layout or something…
update yeah, after putting these in a grid layout card that worked for displaying better on this specific screen, but nother for others. So I just have to keep moving stuff around and finding creative ways to get it to display correctly. I try to avoid stacking shit, but it is what it is…I consider this a functional flaw of HA. The sizing enforcements and card stacking and menu display options drive me absolutely fricking crazy.
These custom card containers are amazing though, thank you for your guidance and information out there and making it easy to follow.
The general rule I found is… On a tablet using companion app, If 4 buttons are in a container, the dashboard itself cannot exceed 3 card columns.
Have i mentioned how much i hate the display requirements of HA dashboards?
@shredder_guitarist, thanks for the appreciation.
Regarding card columns, I’ve noticed that on my PC I get 3 columns of cards but my tablets only get 2 columns in landscape and 1 column in portrait. It’s just the way the Home Assistant UI operates to handle different width screens.
@sajikur, I recommend using the developer tools in your web browser (F12 key) to examine the elements and the CSS they are applying. It’s very useful when things aren’t displaying as expected. There are many websites with instructions, but here is one at random that I didn’t read just to get you started: The Beginner’s Guide to Chrome Developer Tools
I’ve tried reading through this thread the best I could, but I’m stuck. I’m trying to make a container the size of the master suite in the original post. Can you plese provide the code used to make that?
@themanbornwithin, the “container” template I use will grow to contain whatever you put inside. I use a grid of 1 column inside the container, and it contains two grids (one for each row) each with two columns to contain the cards showing the entities.
Can someone please advise what I need to add to make the font smaller for state of my sensor?
i.e. the “dolby atmos” sensor state wording below TV Power (this shows the state of sensor.sonos_audio_input_format), I want the font size of just this smaller, not the name of the card.
I’m having a few problems though… the biggest of which is that for some reason the mini-media-player is running long even when I’ve set info to short. (see the Living section in the middle of the screenshot).
The second issue (possibly related) is that the text of the mini-media-player is not left justified inside the button-card even though it is everywhere else I’ve ever used it.
The last problem is a weird one. The bits that say “Living On” were already a button-card and used to show volume attribute instead of state using (state_display: ‘[[[ return entity.attributes.volume_level ]]]’). But now that I’ve embedded that button-card within your existing button-card container, I get a whopping big undefined reading attributes error if I try to retrieve that volume attribute.
@jfitzell, your last issue is caused by a quirk of nesting button cards where entity is the outermost card, if I remember correctly. I got bit by that at one point and worked around it by specifying a variable for the entity.
I don’t have any suggestions for the other issues other than using the browser’s developer console to manipulate the CSS in realtime and see if you find a combination that achieves the result you need.