Max Gramser
da20782d3d
Every screen gets two template buttons, Wake and Sleep, for automations (button.press on button.<screen>_wake / _sleep). Wake does what a tap does: a dimmed screen runs wake_display, a screen that is on only restarts the standby count. Sleep dims right away through dim_display, also with Auto standby off, and closes an alert that is up (reported as remote); it is ignored during a touch calibration. A new non-restored flag, sleep_requested, keeps that standby in place: dim_display dims with standby off, and apply_screen_settings, which runs every minute, no longer wakes such a screen. wake_display clears it (a tap, Wake, an alert), and so does the Auto standby switch when it really turns standby off. Nothing is saved, so the buttons cost no flash writes and may run on every motion. The Claude skill, README, add-on docs and RELEASING describe both buttons. Checked on host builds of both boards over the native API, 24 checks each (timer, Sleep with Auto standby off across a minute tick, alert, calibration), and with ESP32 builds of both Easy profiles (+336 B RAM). Firmware 0.2.45. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
27 lines
626 B
YAML
27 lines
626 B
YAML
name: ESP Screen Manager
|
|
version: "0.2.53"
|
|
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/'
|