Files
homeassistant_espscreen/screen_manager/config.yaml
T
Xandrossian da28d19961
CI / checks (push) Waiting to run
CI / firmware (add-on) (push) Blocked by required conditions
CI / firmware (min_version) (push) Blocked by required conditions
Bring the Elecrow's GT911 out of reset through the V3.0's PCA9557 (0.2.95, firmware 0.2.81)
A unit's touch never answered: "touchscreen is marked FAILED: Calibration error" at setup, the GT911 still in reset
behind the PCA9557 (I2C 0x18) of the V3.0 board. The board file declares the expander as ESPHome's pca9554 (the same
register map) and hands the GT911 driver its reset (IO0) and interrupt (IO1) pins on it, so the driver runs Elecrow's
own sequence: reset low with the interrupt line low, reset high, 56 ms, address 0x5D. A V2.0 without the expander boots
its GT911 by the pull-up as before. The bus is scanned at boot for the log.
2026-09-21 12:54:18 -07:00

33 lines
882 B
YAML

name: ESP Screen Manager
version: "0.2.95"
slug: esp_screen_manager
description: Choose tiles for your CYD and Guition touchscreen, without reflashing.
url: https://gittea.trippedonmy.name/Xandrossian/homeassistant_espscreen
arch: [aarch64, amd64]
startup: application
boot: auto
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 (firmware.py build_env); retain screens.json and user configuration.
backup_exclude:
- '*/build/'
- '*/esphome/'
- '*/idf/'
- '*/platformio/'