Files
Max Gramser 3b15e7f7a3 Build the screens with ESPHome 2026.9 and keep its build memory in the app's own storage, give the CYD 94 KB more room, and stop a timer from counting one second too many (0.2.89)
The add-on ships ESPHome 2026.9.0: it builds an ESP32 with ESP-IDF itself
and keeps a compiler cache. firmware.py gives the CLI its own storage in
/data (ESPHOME_DATA_DIR /data/esphome, which the ESPHome Device Builder no
longer wipes on start; ESP-IDF and ccache in /data/idf, at most 1 GB;
compilers limited to the core count as PlatformIO ran them), removes the
unused PlatformIO once before the first ESP-IDF build, and leaves the new
folders out of backups.

Firmware 0.2.75: assertion_level SILENT in every board's esp32 block, the
core logs from INFO, and clock_parts() in runtime_model.h replaces sscanf.
timer_left() caps a running timer at its duration (the screen's clock runs
up to a second behind Home Assistant's). The packages keep min_version
2026.6.2, the top-level online_image and OTA passwords for new screens, so
an add-on or Device Builder that isn't updated yet keeps building every
screen; CI now builds both boards with the add-on's ESPHome and with
min_version. ESP-IDF's error names stay on, and build_flags stay under
platformio_options, because ESPHome 2026.9's LVGL reads only those.

tools/check.sh: 478 Python tests, 19/19 C++, editor; --firmware PASS with
ESPHome 2026.6.2 (CYD 87.7 %), 2026.8.1 (88.3 %) and 2026.9.0 (86.4 %,
was 91.5 %). Both bench screens OTA'd and watched for half an hour;
ESP Screens as a local add-on on the Yellow built both profiles
(CYD 1,037 s first build, 41 s unchanged). Details:
docs/TEST_RESULTS_0289.md.

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

3.5 KiB
Raw Permalink Blame History

Troubleshooting

Symptom Check first
No USB port Data cable, a different USB port, board power; compare python -m serial.tools.list_ports before/after connecting. Install the USB chip vendor's driver if needed.
Permission denied on Linux Access to the serial device group (often dialout); log in again after a group change.
Port busy Stop ESPHome logs, the IDE monitor, and other serial readers. One reader at a time.
Upload keeps connecting Check the correct board/port. Hold BOOT while connecting and release afterward if the board requires it.
ESPHome Web shows no port or can't connect (Download) Chrome or Edge on a computer; Safari, Firefox and phones can't reach USB. A data cable, and the driver for the board's USB chip if the computer asks for one (CH340 on most CYDs). Hold BOOT while choosing the port if it keeps failing to connect.
Build fails ESPHome 2026.6.2 or newer with a Python it supports (the app's 2026.9.0 needs 3.12–3.14); the full unpacked folder, local fonts/components present, internet, and disk space. Save the first real error from the build log.
White/black or wrongly rotated image Check the ILI9341 + XPT2046 variant. Don't blindly copy the pins, rotation, or SPI settings from a different CYD model.
No measurement screen The upload must be complete, not just the build. Flash with -s CALIBRATION_ON_BOOT true. Look for USB calibration ready in the USB logs; a normal boot shows no crosshairs.
No measurements Five crosshairs visible, other log reader closed, correct port. Press Enter in the wizard first, then tap the requested point three times, releasing in between.
Tap jumps to a different spot Check the independent verify, your own calibration.yaml, and a fixed orientation. Don't use the same taps to both fit and verify.
Fit reports spread/error Measure again following the prompts. Don't fix unstable ADC readings by raising the tolerance; check power, cable, and touch hardware.
Duplicate HA action Check both the touch logs and your HA automations: an automation that reacts to the same entity can repeat or undo what the tile did.
Wi-Fi doesn't connect 2.4GHz, correct local secrets, network range. USB calibration doesn't need HA.
HA doesn't see the board Manually use the IP from the logs; port 6053 reachable, correct encryption key, no guest network isolation.
Status works but action doesn't Check the HA option for allowed device actions, the real entity ID, and a supported action.
Vacuum/climate partly usable Supported modes/attributes differ per integration; test the same action in Home Assistant first.
Wrong pagination Tiles keep the slot you gave them in ESP Screens: six per page, up to eight pages, and a Save & send applies it without a reflash. The page buttons hide on a screen with one page, and Page buttons off hides them everywhere; then only swiping and Go to page tiles change the page, and the editor warns about a page nothing leads to. Firmware older than 0.2.26 packs the tiles in order instead.
Freeze/reset Keep the USB log, check the reset reason/power, and run the render test. Note the action and time.

For a USB log (stop other readers):

python diagnostics/capture_serial.py --port <USB_PORT> --seconds 120

The docs/TEST_RESULTS_*.md files describe tests on the owner's own boards. Their measurements are not calibration for a new board. Start at README.md, keep a working local configuration, and change one cause at a time.