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>
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.