flash-displays

name: Flash Display description: Flash EspControl display firmware from this repository using ESPHome. Use when the user invokes /flash-displays with no extra display name, or asks to flash, reflash, update, or upload firmware to all known displays in sequence, or to a specific display such as 7inch, 7-inch P4, 10inch, 10-inch P4, P4-86, 4.3-inch P4, 4-inch P4, or 4-inch S3, over an explicitly supplied OTA target or USB.

Flash Displays

Overview

Use the local development ESPHome configs to flash the known EspControl displays. If the user invokes /flash-displays with no additional display name or target, assume they mean all displays. Flash one requested display, or flash all displays in the fixed order below. Use OTA with the default hard-coded target unless the user provides a different target; use USB only when the user explicitly asks for USB.

Device Map

All screens can also be flashed over USB when explicitly requested. Use the selected screen's config directory and the local serial target, normally /dev/cu.usbmodem201301.

If the user says only 4inch or 4-inch, ask whether they mean the 4-inch P4 screen or the 4-inch S3 screen.

For /flash-displays with no extra target, or for all, flash in this sequence by default over OTA using the default targets above:

1. 7-inch P4.
2. 10-inch P4.
3. 4-inch P4 / P4-86.
4. 4.3-inch P4.
5. 4-inch S3.

YAML Selection

Use dev.yaml by default. If the user names another YAML file, use that file instead.

• If the user explicitly says dev, dev file, or dev.yaml, use dev.yaml instead.
• If the user gives a bare filename such as esphome.yaml, resolve it inside the selected display's config directory.
• If the user gives a repo-relative path such as devices/guition-esp32-p4-jc8012p4a1/esphome.yaml, resolve it from the repository root.
• Only use YAML files inside this repository. If the selected file does not exist, ask for the correct file instead of guessing.
• Do not create, copy, commit, or print secrets.yaml. YAML files may reference !secret wifi_ssid and !secret wifi_password, but the secrets file itself must stay local and uncommitted.

Workflow

1. Confirm the repository state:
   • Run git status --short --branch.
   • Use main as the source. If not on main, switch only when it is safe and there are no blocking local changes; otherwise explain the issue.
   • If the worktree is dirty, do not revert or commit unrelated changes. Tell the user the flash will use the current local checkout as-is.
   • If the worktree is clean, run git pull --ff-only before flashing.
2. Resolve the requested display names from the device map. If the user invoked /flash-displays without naming a display, resolve it as all. If the request is ambiguous, ask one short clarification.
3. Resolve the YAML file from the user's request. If none is provided, use dev.yaml.
4. Resolve OTA targets from an explicit user-supplied target first, then from the device's default hard-coded target. If a needed OTA target is missing, ask for that target or ask whether to use USB.
5. If the user says USB, over USB, use USB, local, or similar, use USB for the selected display instead of OTA.
   • For a single display, use that display's config directory and the USB target.
   • For all over USB, flash the displays in the normal all-display sequence, but ask the user to connect the correct display before each USB flash if the connected device is not clearly identifiable.
6. For OTA targets, check reachability first with ping -c 2 -W 1000 <target>.
7. For USB flashing:
   • List ports with ls -1 /dev/cu.*.
   • Prefer /dev/cu.usbmodem201301 when present.
   • If that port is missing and exactly one obvious /dev/cu.usbmodem* port exists, use it.
   • If no clear USB modem port exists, ask the user to connect the display or choose the port.
8. Flash each selected display with the command below, running displays sequentially. Do not run multiple flashes in parallel.
9. After each OTA flash, ping the target again. A first ping may fail during reboot; retry once after a short delay before reporting a problem.
10. Do not commit or push for flashing alone. Commit/push only if this skill or other source files were intentionally changed as part of the user request.

Commands

Use this substitution so ESPHome builds from the local repository checkout:

esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run <yaml-file> --device <target> --no-logs

Run from the appropriate config directory:

# 7-inch P4 over OTA
cd /Users/jtenniswood/Git/espcontrol/devices/guition-esp32-p4-jc1060p470
esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run dev.yaml --device 192.168.6.102 --no-logs

# 7-inch P4 over USB, only when explicitly requested
cd /Users/jtenniswood/Git/espcontrol/devices/guition-esp32-p4-jc1060p470
esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run dev.yaml --device /dev/cu.usbmodem201301 --no-logs

# 10-inch P4 over OTA
cd /Users/jtenniswood/Git/espcontrol/devices/guition-esp32-p4-jc8012p4a1
esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run dev.yaml --device 192.168.6.103 --no-logs

# 10-inch P4 over USB, only when explicitly requested
cd /Users/jtenniswood/Git/espcontrol/devices/guition-esp32-p4-jc8012p4a1
esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run dev.yaml --device /dev/cu.usbmodem201301 --no-logs

# 4-inch P4 / P4-86 over OTA
cd /Users/jtenniswood/Git/espcontrol/devices/esp32-p4-86
esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run dev.yaml --device 192.168.10.52 --no-logs

# 4-inch P4 / P4-86 over USB, only when explicitly requested
cd /Users/jtenniswood/Git/espcontrol/devices/esp32-p4-86
esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run dev.yaml --device /dev/cu.usbmodem201301 --no-logs

# 4.3-inch P4 over OTA
cd /Users/jtenniswood/Git/espcontrol/devices/guition-esp32-p4-jc4880p443
esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run dev.yaml --device 192.168.6.101 --no-logs

# 4.3-inch P4 over USB, only when explicitly requested
cd /Users/jtenniswood/Git/espcontrol/devices/guition-esp32-p4-jc4880p443
esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run dev.yaml --device /dev/cu.usbmodem201301 --no-logs

# 4-inch S3 over OTA
cd /Users/jtenniswood/Git/espcontrol/devices/guition-esp32-s3-4848s040
esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run dev.yaml --device 192.168.10.226 --no-logs

# 4-inch S3 over USB, only when explicitly requested
cd /Users/jtenniswood/Git/espcontrol/devices/guition-esp32-s3-4848s040
esphome -s espcontrol_component_url file:///Users/jtenniswood/Git/espcontrol run dev.yaml --device /dev/cu.usbmodem201301 --no-logs

Reporting

Keep user updates concise:

• Say which display is currently compiling/uploading.
• Mention known ESPHome warnings only if they affect the result; framework, platform, GPIO19/GPIO20, and MIPI narrowing warnings are normally non-blocking.
• Final response: list each requested display as flashed successfully, or clearly identify the display that failed and the blocking symptom.