Max Gramser
66b1590184
GitHub issue #8: Home Assistant on a server or virtual machine is out of reach of the screen. New screen and Firmware & USB get a Download choice: ESP Screens builds the profile's firmware as always and offers ESPHome's factory image, which the owner flashes with ESPHome Web in Chrome or Edge. - Firmware: a download job compiles without uploading; only the image of the profile's latest successful build in this process is served, a new job withdraws it, and a build without a factory image fails. - USB on the Home Assistant machine stays first in both lists, also before a board is plugged in; Download and Later stay chosen once picked. - The not-yet-in-Home-Assistant card knows a downloaded screen. - The device name pattern is valid again under Chrome's v flag. - Docs: README, DOCS, EASY_SETUP, DOCKER, TROUBLESHOOTING. App only; firmware stays 0.2.58. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
32 lines
826 B
YAML
32 lines
826 B
YAML
name: ESP Screen Manager
|
|
version: "0.2.68"
|
|
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
|
|
# Camera images for Guition screens (docs/CAMERA.md): the screens load them from this port on the LAN.
|
|
ports:
|
|
8098/tcp: 8098
|
|
ports_description:
|
|
8098/tcp: Camera images for the screens (keep 8098)
|
|
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/'
|