ESPHOME - Waveshare 7.5 inch E-Ink E-Paper Display

ESPHome
41

Okay. This raises multiple questions for me…

  1. Currently, I use the 7,5inv2alt verison as I know there has been a fix for the greasy picture. Is this implemented in V2 also?
  2. If there has been a fix for deep sleep in v2 and I use it, do I have to specify the sleep state? I once tried with kind of
deep_sleep:
  id: deep_sleep_1
  sleep_duration: 60s

But as a result, my display would never refresh its data. I am a bit lost here.

Edit: No, as soon as I switch to V7.50v2, I am back to the greasy picture…

42

I think when the waveshare people are talking about deepsleep, they mean the display itself (https://www.waveshare.com/wiki/1.54inch_e-Paper_Module_Manual#Precautions)

What you are using in your yaml is the deep sleep mode of the esp itself (Deep Sleep Component — ESPHome)

From what I found the deep sleep mode of the display needs to be part of the esphome code for the display, it’s nothing you can manually set if it wasnt taken into account by the esphome developer before.

43

Ah, I understand.
But if so, everyone should be running into this issue…
And I do not understand why the greasy display fix hasnt been implemented in all v7,5 models …

44

I also never got the logic behind some people not having issues, and some (including me) struggling forever. The time and financial effort just got too big for me over time, which is a dealbreaker when compared to the little happiness i got out of it. Occasionally when it “hits me” i get motivated again and give it another go, but for projects where i need reliability i either use the 2.9inch display or leds.

Who knows, maybe in January I’ll risk it and get myself a new 7.5er panel :slight_smile:

1 Like
45

Shouldn’t the sleep mode fix be implemented for all 75vsomething’s?

46

i dont see a reason why it shouldnt, so: yes

47

I am using the v2 waveshare 7.5 b+w screen with 7.50inV2alt driver, on an ESP32 WROOM D1 Mini.

It displays cleanly but the refresh is mad … you get multiple screen flashes (3 white, 3 inverted, then draw) each time.

Here are (hopefully) the relevant sections of config:

spi:
  clk_pin: 26
  mosi_pin: 22

display:
  - platform: waveshare_epaper
    id: epaper
    cs_pin: 21
    dc_pin: 17
    busy_pin: 16
    reset_pin: 18
    model: 7.50inV2alt
    rotation: 90°
    update_interval: never 
    reset_duration: 2ms 
…

Is this something I have caused by incorrect wiring or configuration or are we all waiting for better drivers?

48

I am wondering if my display borked itself. I have been using a LilyGo 7.5 display, with wave share_epaper display working great. Yesterday at 3:21 pm was the last update. When I check the logs I see it hang on spi device, then throw a watchdog trigger. Has anyone else seen this?

[08:19:33][D][spi_device:393]: mode 0, data_rate 2000kHz
[08:19:38]E (10911) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time:
[08:19:38]E (10911) task_wdt:  - loopTask (CPU 0)
[08:19:38]E (10911) task_wdt: Tasks currently running:
[08:19:38]E (10911) task_wdt: CPU 0: IDLE0
[08:19:38]E (10911) task_wdt: CPU 1: IDLE1
[08:19:38]E (10911) task_wdt: Aborting.
[08:19:38]E (10911) task_wdt: Print CPU 0 (current core) backtrace
49

just a bit of an update, I tried a wave share link driver board with ESP32, and I get the same error. I wonder if its an issue with ESPhome??