I’ve been pulling my hair out trying to get this thing to work - I have two of them so I’ve hopefully ruled out hardware failure (both exhibit same behavior).
I’ve tried several code samples using both a D1 Mini as well as a regular esp32dev board with the same results.
This in the logs over and over:
[20:12:12][W][component:237]: Component display took a long time for an operation (134 ms).
[20:12:12][W][component:238]: Components should block for at most 30 ms.
I’ve hunted around and it seems only one other topic with this issue which is unresolved. Any ideas to steer me in the right direction here? I haven’t even begun to try to worry about what I want to display yet, just trying to get the thing working. Below is the YAML I’m using on the full esp32dev board:
I did also on a whim try setting the model to 4.20in-bV2 and get an additional line in the output:
[20:24:43][E][waveshare_epaper:159]: Timeout while displaying image!
[20:24:43][W][component:237]: Component display took a long time for an operation (1165 ms).
[20:24:43][W][component:238]: Components should block for at most 30 ms.
As I continue to dig looking at the ESPHome repository for these displays I notice it’s been quite some time since anything was updated: GitHub - soonuse/epd-library-arduino: Arduino libraries for Waveshare e-paper series I noticed an issue asking if partial refresh could be added to the support for the 4.2" screen (which it definitely does say it supports in the documentation).
I’m a bit above my depth here but is it feasible we’re starting to see some newer iterations of these displays that require updates?
The lines from your logs are just warnings and I think many components are hit with this warning even though it is impossible to get these solved. An e-ink takes the time an e-ink takes update.