GUITION 1.8” 360x360 ESP32-S3-JC3636W518 Smart Display

GUITION 4" 480x480 ESP32-S3-4848S040 Smart Display with LVGL - ESPHome - Home Assistant Community (home-assistant.io)

Compared to 4848S040, it has added a microphone and magnetic QI wireless power supply, but uses the screen of st77916 QSPI. I have installed ESPHome, but I can control the backlight because the screen is not within ESPHome’s support range and I cannot make the screen work.

If it is supported by ESPHome, that would be great

1721190177415

-CNC casing
-The price is about $20

That is a really nice looking screen. My guess it more screens will start using this chip. Another user has requested a ESPhome driver for it.

Quad SPI AMOLED Displays — ESPHome
esp-iot-solution/components/display/lcd/esp_lcd_st77916 at master · espressif/esp-iot-solution (github.com)

Unfortunately, ESPHome does not have the QSPI-LCD component. Looking forward to adding it

There is no difference - the QSPI will work with either. The display driver does need to be ported.

I hope someone can contribute a driver program set

Can anybody put together a basic configuration based on what is known?

The issue is no ESPhome component for the display driver IC yet

ESPHome has QSPI BUS and adds two AMOLED display models. There is no LCD display model.

Quad SPI AMOLED Displays

1 Like

The QSPI bus can be defined as “quad” in the spi component and is separate from any display, at least I have used it to talk to a LCD display. The display driver for this LCD is what’s missing.

Example ESPhome-JC3248W535EN/jc3248w535-demo.yaml at 75b865516f7239915587f79866072da9fe74f3c8 · clowrey/ESPhome-JC3248W535EN · GitHub

Yeah the code is here but my C skills are not good enough. Does anybody have the skills to take a wack at adding this to ESPHome?

Its now natively supported by ESPhome component in DEV version :slight_smile: Thanks to Clyde for updating the QSPI to accept custom init code and renaming it.

Details and YAML here GitHub - clowrey/esphome-guition-360x360-jc3636w518: Guition 360x360 jc3636w518 ESPhome LCD dev board example


2 Likes

I acquired this Waveshare device, and it looks very similar:

However, I’ve had no luck using Clyde’s code for the screen. Am I off base here, or is there something beyond the ports that would need updating?

Thanks for any help.

That is a very different screen from a different manufacture. It does look like it has ST77916 display like the JC3636W518 but it’s on different pins.

Waveshare is good they give you all the pinout info right on the product page so you don’t need to go digging around the internet to find how everything is hooked up.

Well thanks. I wasn’t trying to hijack this thread, but this is the closest equivalent I could find with a working sample.

I presume by “ports” you mean the GPIO assignments.

So yes, in addition you will probably need a custom init sequence, which you would get by looking at the Waveshare demo code and converting to YAML.

You need to configure the correct display and touch GPIO in ESPHome
Then try custom init sequence and finally make it work. As Clyde said, you need to find these from the supplier’s example code. 3636W518 is the init sequence found in this way

Thanks guys. Still no luck. I started a new thread here: Waveshare ESP32-S3-LCD-1.85

1 Like

I’m fiddling with voice assistant on this device.
I see that the mic is detecting my commands.
But when it try to play the response, there is no sound:

[22:36:01][D][i2s_audio.speaker:111]: Starting Speaker
[22:36:01][D][i2s_audio.speaker:116]: Started Speaker
[22:36:01][D][voice_assistant:635]: Event Type: 98
[22:36:01][D][voice_assistant:779]: TTS stream start
[22:36:01][D][voice_assistant:635]: Event Type: 8
[22:36:01][D][voice_assistant:713]: Response URL: "http://172.16.40.101:8123/api/tts_proxy/S51f8KIGH4M5VxMnwQoxNg.wav"
[22:36:01][D][voice_assistant:511]: State changed from AWAITING_RESPONSE to STREAMING_RESPONSE
[22:36:01][D][voice_assistant:518]: Desired state set to STREAMING_RESPONSE
[22:36:01][D][voice_assistant:635]: Event Type: 2
[22:36:01][D][voice_assistant:727]: Assist Pipeline ended
[22:36:04][D][voice_assistant:635]: Event Type: 99
[22:36:04][D][voice_assistant:789]: TTS stream end
[22:36:04][D][voice_assistant:377]: End of audio stream received
[22:36:04][D][voice_assistant:511]: State changed from STREAMING_RESPONSE to RESPONSE_FINISHED
[22:36:04][D][voice_assistant:518]: Desired state set to RESPONSE_FINISHED
[22:36:04][D][i2s_audio.speaker:123]: Stopping Speaker
[22:36:04][D][i2s_audio.speaker:129]: Stopped Speaker

My speaker YAML:

i2s_audio:
  - id: i2s_in
    i2s_lrclk_pin: GPIO45
    i2s_bclk_pin: GPIO42
  - id: i2s_out
    i2s_lrclk_pin: GPIO16
    i2s_bclk_pin: GPIO18
    i2s_mclk_pin: GPIO21

microphone:
  - platform: i2s_audio
    id: i2s_microphone
    i2s_audio_id: i2s_in
    i2s_din_pin: GPIO46
    adc_type: external
    pdm: false
    channel: left
    sample_rate: 16000
    bits_per_sample: 32bit
speaker:
  - platform: i2s_audio
    id: i2s_speaker
    i2s_audio_id: i2s_out
    i2s_dout_pin: GPIO17
    dac_type: external
    channel: stereo

Anyone gotten the speaker to work on this one?

What kind of speaker are you using? You need a speaker with an external amplifier. Otherwise, the sound will be very low.

this yaml