Features Wishlist
YAML override cells and look
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
Discussion 2
Add a commentThanks for trying the JC3248W535 and for the clear write-up. You can do this today from the screen's Override YAML, without a copy of the whole package.
Why adding
looks/compact.yamlorcells/6.yamlfails: ESPHome joins the lists of every package, so a second look or cells file brings the same fonts and cards a second time, with the same ids. The board file already includesstandard.yamlandcells/4.yaml, and an override can't take a package away. What an override can do is set substitutions and add widgets, and that is enough for all three things you want.1. The grid.
GRID_COLS: "3"andGRID_ROWS: "2", as you have. Standing up stays 1 x 3.2. Six cards instead of four. The board brings four cards. The override adds cards 5 and 6, exactly as
packages/cells/6.yamlhas them, and replacesBIND_CELLS, the line that hands the cards to the firmware, with the six-card version.3. The compact look. A look is only a list of sizes, so the override states them itself. The numbers below are what
looks/compact.yamlworks out on this board's density (164.8 dpi). They are plain numbers on purpose: a size written as a formula in the override (${ ... }) comes out as 0 in the other files that use it, and you get invisible tiles. Want it smaller or larger? Change the numbers themselves.You can drop
DISPLAY_DPI: "130". The numbers below no longer depend on it, and the firmware uses it as the real density of the glass for the sizes it works out on the screen.The whole Override YAML (More → Override YAML), then Install
Two things to know:
WIDE_NAME_FONT: "label"keeps the normal one). Everything else is the same as a compact build with six cards.BIND_CELLSand the card ids are internals, not part of what an override is promised to keep. If a later update changes them, the build will say so, and removing the override (or updating it) brings the screen back.I haven't really tested this on a screen yet. ESPHome reads it without complaint against the current package, and the result matches a build with the compact look and six cards in the board file itself, so in principle it should work. I'm curious what you run into, so let me know how it goes.
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.
Like my work? Consider buying me a coffee, much appreciated!
Original on GitHub
Thanks @govido! This is better suited to a discussion than an issue, so I moved it here: https://github.com/MaxGramser/homeassistant_espscreen/discussions/108
Please continue the conversation there. I'm closing this issue to keep the tracker for bugs and concrete board requests.
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.
Like my work? Consider buying me a coffee, much appreciated!
Original on GitHub