Files
homeassistant_espscreen/screen_manager
Max Gramser fcdea12c44 Keep every screen's Wi-Fi awake from the shared core, so Home Assistant's messages no longer wait for the router's next beacon (0.2.88)
packages/core.yaml sets wifi: power_save_mode: none. ESPHome merges it
under the screen's own wifi: block, which keeps the network, the password
and the hotspot, and the screen's own YAML still wins on the mode. The
YAML ESP Screens writes has had the line since app 0.2.24; screens with
an older or hand-written YAML ran ESPHome's ESP32 default light, and
their messages from Home Assistant waited 76-117 ms on the bench.

esphome config on the bench screens' Device Builder YAMLs: NONE for both
without a line of their own, LIGHT when the YAML says light. The bench
Guition, flashed from its Device Builder YAML: ping 15 ms average instead
of 117 ms. tools/check.sh: 474 Python tests (a new one keeps the core's
wifi: block to this one key), 19/19 C++, editor; firmware unchanged in
size (CYD 1,678,816 B, 91.5 %; Guition 2,055,280 B), since the checkout
profiles already had the line.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-19 09:06:53 +02:00
..

ESP Screen Manager

Thank you! I work on this project with a lot of love, and every bit of support helps. I truly love the Home Assistant community.

Buy me a coffee

Find your Home Assistant entities, arrange up to 48 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.

A Guition 4-inch screen with tiles from Home Assistant ESP Screen Manager in Home Assistant: the screens, the top bar and the tiles of the selected screen

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.