Files

T

Max Gramser 8a587303d7 Give each screen its own YAML override that survives updates (0.2.61)

Override YAML on a screen edits <name>.local.yaml, a package loaded after
the shared board package. New profiles get an empty one; an existing
profile is attached on the first save without reformatting the file. The
editor validates YAML, refuses the managed sections and substitutions,
and Save & check runs ESPHome's full validation of the complete profile.

The example uses !extend: ESPHome appends package lists instead of
merging them by id, so a bare id added a second display without a
platform and failed the build. An override is 12 KB at most and a
too-large body answers as JSON instead of a bare 413. The sidecar is
written before the profile includes it, and a symlinked sidecar is
refused. Firmware stays 0.2.52.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-09-17 08:23:13 +02:00

app

Give each screen its own YAML override that survives updates (0.2.61)

2026-09-17 08:23:13 +02:00

CHANGELOG.md

Give each screen its own YAML override that survives updates (0.2.61)

2026-09-17 08:23:13 +02:00

config.yaml

Give each screen its own YAML override that survives updates (0.2.61)

2026-09-17 08:23:13 +02:00

Dockerfile

Add rich runtime tiles and integrated ESPHome firmware management

2026-09-12 15:41:54 +02:00

DOCS.md

Give each screen its own YAML override that survives updates (0.2.61)

2026-09-17 08:23:13 +02:00

README.md

Show the screens and ESP Screens in the README; firmware 0.2.35 to test updates (0.2.41)

2026-09-15 08:08:38 +02:00

README.md

ESP Screen Manager

Find your Home Assistant entities, arrange up to twenty tiles, and push changes to a CYD or Guition screen without reflashing. Includes installation help, a unique per-device YAML, and support for multiple screens.

Open the web interface after installation. See Documentation for the first flash. The app uses Home Assistant Ingress and needs no login or token of its own. More screenshots are in the project README.