YAML override cells and look

[MaxGramser]

Moved from #63, originally opened by @govido.

What would you like to add

I tested the new jc3248w535 board, which works great.
But I wanted to get rid of the wasted space on the small screen on the edges, but there is currently no way to change the standard.yaml to the compact.yaml as it will create duplicate errors when the package gets added in override yaml. Same for the cells 4.yaml if you want to try 6 instead of 4 tiles.
Can the logic be changed to substitutions that load the individual packages? These can be overwritten easily.
That way advanced users can create compact dashboards with different sizes and compacter layouts.

In my case I want to use the screen on my office desk, for this the text can be smaller and I want to use more buttons, like a little stream deck, but for HA stuff.

I created a local file with compact view and 6 tiles which works great, but I would like to use the offical config with tweaks available if needed in the override, like DPI, rows, columns, compact or standard and different amount of cells.

How this relates to Home Assistant

Make buttons larger and smaller for HA control from walls at a distance or get more details when used up close on a desk. Not only depending on fixed display hardware alone, but the actual use case, if needed.

Pictures, mockups, or examples

The editor updates fine, but the screen won't show more than 4 tiles on one page, as the 4.yaml is hardcoded.

current yaml override

substitutions:
  GRID_COLS: "3"
  GRID_ROWS: "2"
  DISPLAY_DPI: "130"

Before submitting

• I searched the existing issues and this has not already been requested

[MaxGramser]

This request and its replies have moved to the Tessera wishlist.

Please continue there and upvote the wish if you would use it. Sign in with your GitHub account to vote, reply or add examples. More votes help set priorities, including support for new ESP boards and displays.

The original authors, dates, comments and image links have been preserved. This GitHub thread is kept as an archive. GitHub Issues are now for bugs in existing functionality; closing this thread does not mean the request was rejected or implemented. Its current status is on the website.

---

Got a screen running? Tell others which board you have and what works on the Tessera website. It helps everyone pick a screen that works.

Want me to keep building? Consider supporting monthly or buying me a coffee, much appreciated!