Files
homeassistant_espscreen/docs/TROUBLESHOOTING.md
T
Max Gramser 3e959b3df9 Put ESP Screens in English and keep layouts when entity IDs change (0.2.40)
Everything a user sees or reads is now English: both boards' labels,
status replies and logs, the ESP Screens editor and Alerts cheatsheet,
and the README and guides (docs/TILES.md, CALIBRATING.md, ACCEPTANCE.md
and TROUBLESHOOTING.md replace the Dutch file names). Labels follow
Home Assistant's own English names (Heat/Cool modes, Heating/Cooling
actions, Away, Returning to dock, weather conditions), dates use English
abbreviations and the top bar writes numbers the English way. Docs use
HA 2026.9's menu names (Settings -> Apps, App store, Settings -> Tools).
Unused legacy files (home-like.yaml, buttons.yaml, a.out) are removed.

Firmware 0.2.34 names its entities in English. Home Assistant registers
a renamed ESPHome entity under a new entity ID, so the inbox
text.<screen>_tegelinstellingen becomes text.<screen>_tile_settings and
the layout stored under the old ID would be lost. The manager now
recognises the screen by its device, during a run or after a restart,
and moves its layout and update history along; the Update button and
the nightly round follow the screen through the rename. Screens that
still run 0.2.33 or older keep working: both languages are matched.

Main is the only release branch from now on.

Tested on a Home Assistant Yellow (HA 2026.9.1) with both bench boards:
see docs/TEST_RESULTS_0240.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-15 02:08:43 +02:00

2.9 KiB
Raw 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.
Build fails Python 3.11–3.14 and ESPHome 2026.6.2; 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 HA automations. Don't use direct actions together with an automation on the action sensor for the same operation.
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, DIRECT_ACTIONS: "true", the real entity ID, and a supported action.
Vacuum/climate partly usable Supported modes/attributes differ per integration; see TILES.md and test the same action in HA first.
Wrong pagination TILE_COUNT is 1–10; hidden buttons up to six, two pages from seven on. Reflash after changing it.
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 existing CYD_STABILITY.md and TEST_RESULTS.md describe earlier investigation on one specific board. 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.