General Community

Guition 10.1" P4 (JC8012P4A1 V3): constant restarts and OTA failing with "Connection reset by peer". Fixed by updating the ESP32-C6 Wi-Fi co-processor

daneverest

Versions: Tessera Screen Manager add-on 0.4.97, screen firmware 0.60.0, ESPHome 2026.9.0. ESP-Hosted host 2.12.12 on the P4.

Symptoms

  • The screen restarted every 1 to 3 minutes, about 400 times in a week, and kept dropping off the network (Retrying screen sync (TimeoutError), Errno 113).
  • Every OTA update failed on the first chunk with Connection reset by peer. One attempt took the screen's network down completely until it was power-cycled.
  • Wi-Fi signal was strong (around βˆ’35 dBm), so signal wasn't the cause.

The tell

The Wi-Fi co-processor sensor read ESP-Hosted unknown (host 2.12.12). "unknown" means the ESP32-C6 is still on its factory firmware, which is too old to report a version. The link between the P4 and the C6 was unreliable, so anything big over the network failed, OTA in particular.

Fix

  1. Download ESPHome's official ESP-Hosted build for the C6, choosing the version that matches the host (2.12.12 here). It's in the esp32c6.json manifest at https://esphome.github.io/esp-hosted-firmware/. Check the file's SHA-256 against the manifest.
  2. Put the .bin in your esphome/ folder. I used the File editor add-on.
  3. Add an esp32_hosted update entry to <screen>.local.yaml (block below). Tessera includes this file in every build and never overwrites it. Run Check on Tessera's Firmware & USB page.
  4. Flash the P4 over USB, because OTA won't work until the C6 is fixed. Use Tessera β†’ Firmware & USB β†’ your screen's existing yaml β†’ Install from this browser. This needs Chrome or Edge, which can reach USB ports. Use the screen's existing yaml so the API encryption key stays the same.
  5. In Home Assistant, reload the device in the ESPHome integration so the new entity appears. Then press Install on the Wi-Fi co-processor firmware update entity. The P4 passes the firmware to the C6 over their internal link, which takes about 6 minutes, then the screen restarts by itself. Keep it powered and leave it alone while that happens.
  6. The sensor should now read ESP-Hosted 2.12.12 (host 2.12.12), and OTA works again. My first Tessera OTA build afterwards went through, and the local.yaml entry survived it.
# <screen>.local.yaml
# Lets Home Assistant update the ESP32-C6 Wi-Fi co-processor.
# Embedded: the C6 firmware is built into the P4's firmware and sent over
# the internal link, so nothing downloads over Wi-Fi.
# Official build: https://esphome.github.io/esp-hosted-firmware/ (v2.12.12)
update:
  - platform: esp32_hosted
    name: "Wi-Fi co-processor firmware"
    type: embedded
    path: esp32c6-hosted-2.12.12.bin   # relative to this yaml, in esphome/
    sha256: bad97ce81e7fcf5f3365898f633b80941ae863db9c754d87a78f89c8f61f2e94

⚠️ Warning: If the C6 update is interrupted, the Wi-Fi chip can get stuck restarting, and the screen won't join Wi-Fi. The P4 can still be reflashed over USB. Reflashing the C6 directly means opening the case to reach its pins, which is why step 5 says to keep the screen powered.

Also worth knowing

With three live map tiles on the screen, the pressure sensor read (the main loop held up) just before each restart, and Tessera logged rebooted after a crash: Abort. Taking the map tiles off was part of my fix.

Since the C6 update I've put one live map tile back, and the screen has stayed up for 9+ hours with no restarts and no stalls. So the broken Wi-Fi link may have been making the load problem worse.

If you see restarts, take live tiles and plugins off first, then add them back one at a time.

Discussion 0

Add a comment

Start the conversation

Share an example, ask a question or explain how you would use this.

Add your thoughts, a screenshot or a useful link.

Markdown & basic HTML
Paste or drop images Β· URLs on their own line become previews0 / 10,000
Create your account to join in

We need a verified email address to reach you about your contribution. Your address stays private.

Continue with GitHub

Your draft stays in this tab. Return here after verification.