8a587303d7
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>
27 lines
626 B
YAML
27 lines
626 B
YAML
name: ESP Screen Manager
|
|
version: "0.2.61"
|
|
slug: esp_screen_manager
|
|
description: Choose tiles for your CYD and Guition touchscreen, without reflashing.
|
|
url: https://github.com/MaxGramser/homeassistant_espscreen
|
|
arch: [aarch64, amd64]
|
|
startup: application
|
|
boot: auto
|
|
init: false
|
|
homeassistant_api: true
|
|
ingress: true
|
|
ingress_port: 8099
|
|
panel_icon: mdi:monitor-dashboard
|
|
panel_title: ESP Screens
|
|
panel_admin: true
|
|
options: {}
|
|
schema: {}
|
|
|
|
map:
|
|
- homeassistant_config:rw
|
|
uart: true
|
|
usb: true
|
|
# Reproducible compiler/download caches; retain screens.json and user configuration.
|
|
backup_exclude:
|
|
- '*/build/'
|
|
- '*/platformio/'
|