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>

This commit is contained in:

Max Gramser

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

parent 87b2082f81

commit 8a587303d7

12 changed files with 694 additions and 4 deletions

									
										screen_manager/app/core.py
									
		+1
		
												View File
												
				@@ -1163,6 +1163,7 @@ packages:

				    ref: {REFS[board]}

				    files: [packages/{board}.yaml]

				    refresh: 0s

				  local_overrides: !include {name}.local.yaml

				api:

				  encryption: