General Community

Guition JC1060P470C-I-W-Y 7" working with Tessera | V2 LCD and ESP32-P4 v3.2

a1cadd

I had trouble getting this screen working with Tessera. Here’s what fixed it for me, in case it helps someone with the same board.

My Guition JC1060P470C-I-W-Y is a 7-inch, 1024 × 600 panel. esptool identified its ESP32-P4 as revision v3.2. The first image flashed and verified but stayed blank. Its bootloader and application headers supported silicon only through v1.99. Rebuilding for v3.x got the board onto Wi-Fi. With the original LCD profile the panel lit up with a vertical band and occasional pulsing. Switching to the V2 LCD profile brought up the Tessera startup screen, and the ESPHome API reconnected after the OTA update.

The LCD profile and chip revision are separate. Check the panel label when available and use esptool for the chip revision. My rebuilt bootloader and app advertised v3.1–v3.99. For an enrolled device, keep its existing identity, Wi-Fi, API key and OTA credentials and merge the changes into its existing YAML. For a first install, build a factory image and flash over USB. Holding BOOT, tapping RESET and releasing BOOT entered download mode on my board. Tap RESET alone after the write is verified if the board stays in download mode.

guition-7in-v2.yaml

substitutions:
  DEVICE_NAME: "guition-7in-v2"
  DEVICE_FRIENDLY_NAME: "Guition 7-inch Display"
  LANGUAGE: "en-GB"
  LVGL_ROTATION: "0"
  GRID_COLS_PORTRAIT: "3"

esphome:
  name: "${DEVICE_NAME}"
  friendly_name: "${DEVICE_FRIENDLY_NAME}"

packages:
  display:
    url: https://github.com/MaxGramser/homeassistant_espscreen
    ref: main
    files: [packages/jc1060p470v2.yaml]
    refresh: 0s

esp32:
  framework:
    sdkconfig_options:
      CONFIG_ESP32P4_SELECTS_REV_LESS_V3: "n"
      CONFIG_ESP32P4_REV_MIN_301: "y"

api:
  encryption:
    key: !secret guition_7in_v2_api_key

ota:
  - platform: esphome
    password: !secret guition_7in_v2_ota_password

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  power_save_mode: none
  ap:
    ssid: "Guition Setup"
    password: !secret guition_7in_v2_fallback_ap_password

captive_portal:

secrets.example.yaml

Merge these entries into your private secrets.yaml. Use a unique 32-byte base64 API encryption key and a fallback AP password of 8–63 characters.

wifi_ssid: "REPLACE_WITH_WIFI_SSID"
wifi_password: "REPLACE_WITH_WIFI_PASSWORD"
guition_7in_v2_api_key: "REPLACE_WITH_BASE64_API_KEY"
guition_7in_v2_ota_password: "REPLACE_WITH_UNIQUE_OTA_PASSWORD"
guition_7in_v2_fallback_ap_password: "REPLACE_WITH_FALLBACK_AP_PASSWORD"

The sanitized example reproduces the settings used on my board and still needs your local values before building. A separate C6 recovery test was part of my troubleshooting, so this does not establish whether other units need a C6 update.

Tessera’s Guition 7-inch guide

Discussion 11

Add a comment
smartie24

· Edited

Hi a1cadd you are a live saver, i have spent 3 days trying to get rid of the blank screen and no wifi, using your yaml file i now have a light up screen and conected to wifi, but i still cannot get Tessera to load screens, its connected to wifi and says getting ready but been like that for ages, i will leave it on for longer and see

thanks again

edit sorted thank you very much

a1cadd

I've since learnt the model I have of this display is V3

GP-Hotstepper

JC1060P470C-I-W-Y (ESP32-P4 rev 3.2) build fails with ESPHome 2026.10.2

Hi,

I'm trying to get a Guition JC1060P470C-I-W-Y working with Tessera.

My hardware:

  • Guition JC1060P470C-I-W-Y (SKU:10153004-V3 (2643)
  • 7" 1024x600 display
  • ESP32-P4 revision v3.2 (Chip Revision 302)

esptool.js detects the device correctly:

ESP32-P4

Chip Revision: 302

Chip is ESP32-P4 (revision v3.2)

I followed the instructions from this discussion and added:

esp32:
  framework:
    sdkconfig_options:
      CONFIG_ESP32P4_SELECTS_REV_LESS_V3: "n"
      CONFIG_ESP32P4_REV_MIN_301: "y"

The build now proceeds much further, but fails during compilation of esp_audio_stack.

Environment:

  • ESPHome 2026.10.2
  • Tessera screens-v0.4.98
  • package: packages/jc1060p470v2.yaml

Compiler errors include:

audio_core_ring_buffer_caps.h:207:28:

error: invalid use of non-static member function

audio_core_ring_buffer_caps.h:218:43:

error: invalid use of non-static member function

audio_core_ring_buffer_caps.h:222:33:

error: invalid use of non-static member function

The failure appears to be related to:

esphome/components/esp_audio_stack

and references:

RingBuffer::handle() const

Has anyone successfully built the P4 v3.2 configuration with ESPHome 2026.10.2, or is there currently a compatibility issue between the current ESPHome version and Tessera's esp_audio_stack?

Thanks!

Photo64

I had the same issue yesterday trying to update to the latest version so I had to leave it at 0.60.0. I am assuming it's because this display is building from v2 and we're still waiting on an update for the v3 displays.

smartie24

· Edited

here is my yaml i followed a1cadd post above

# Keep this file safe: it contains the unique keys for this screen.
# Wi-Fi comes from the secrets.yaml of ESPHome Device Builder.
substitutions:
  DEVICE_NAME: "main-house"
  DEVICE_FRIENDLY_NAME: "main-house"
  LANGUAGE: "en-GB"
  SWIPE_PAGES_DEFAULT: "1"
  GITHUB_REF: "screens-v0.4.98"
  LVGL_ROTATION: "0"
  GRID_COLS_PORTRAIT: "3"
  
esphome:
  name: "${DEVICE_NAME}"
  friendly_name: "${DEVICE_FRIENDLY_NAME}"

packages:
  display:
    url: https://github.com/MaxGramser/homeassistant_espscreen
    ref: screens-v0.4.98
    files: [packages/jc1060p470v2.yaml]
    refresh: 0s
  local_overrides: !include main-house.local.yaml

esp32:
  framework:
    sdkconfig_options:
      CONFIG_ESP32P4_SELECTS_REV_LESS_V3: "n"
      CONFIG_ESP32P4_REV_MIN_301: "y"

 

api:
  encryption:
    key: "key here ="
ota:
  - platform: esphome
    encryption:
    
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  power_save_mode: none
  ap:
    ssid: "Guition Setup"
    password: !secret guition_7in_v2_fallback_ap_password
    
captive_portal:
  
#web_server:
#  port: 80
#  version: 2
  
Photo64

Just to confirm, this allowed you to upgrade to 0.61.0? Are you able to use the Voice Assistant plugin? I see there are open issues for adding this to v3. If you are able to load the plugin I consider trying this but might just wait if not.

smartie24

Didn’t see the ver 61 so updating now and will report back when finished. I don’t use voice yet

smartie24

My 4x3 screen updated to version 61. But my 7 in built but failed to upload

a1cadd

I have voice assistant setup in HA and have not been able to add voice or sound to the display. @Photo64 I am holding at 0.60.0

GP-Hotstepper

Hello.

Yesterday I was able to compile and run the V3 display after the Tessera Update. My Config:

  • Teserra 0.4.99 (Firmware 0.62.0)
  • ESP Home 2026.10.2

Compiled with ESP-Home

Here my YAML Code:

# Board: Generic ESP32-P4 Board (rev3) (Generic)
# Definition: definitions/boards/generic-esp32p4-r3/manifest.yaml

# Keep this file safe: it contains the unique keys for this screen.
# Wi-Fi comes from the secrets.yaml of ESPHome Device Builder.
substitutions:
  DEVICE_NAME: "v3-display"
  DEVICE_FRIENDLY_NAME: "v3-display"
  LANGUAGE: "de"
  SWIPE_PAGES_DEFAULT: "1"
  GITHUB_REF: "screens-v0.4.99"

esphome:
  name: "v3-display"
  friendly_name: "v3-display"
  
packages:
  display:
    url: https://github.com/MaxGramser/homeassistant_espscreen
    ref: main
    files: [packages/jc1060p470v2.yaml]
    refresh: 0s
    
esp32:
  variant: esp32p4
  flash_size: 16MB
  framework:
    sdkconfig_options:
      CONFIG_ESP32P4_SELECTS_REV_LESS_V3: "n"
      CONFIG_ESP32P4_REV_MIN_301: "y"
      
api:
  encryption:
    key: "<Your Key here>"
ota:
  - platform: esphome
    password: "<Your Password here>"
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  power_save_mode: none
  ap:
    ssid: "Tessera-v3-display"
    password: "<your password here>"
captive_portal:

logger:

The display booted fine and is running with Tessera.

No voice assistant setup tested.

Photo64

Unfortunately following your example yaml code it didn't work for me, it reverted back to 0.60.0

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.