Let's Control It

Hello everybody,

i use some Sonoff devices on Fhem and with EspEasy Version: v2.0-20180218. I want to thank everybody for this perfect part of firmware. Meanwhile there are some displays supported, but there is no E-Ink Display in the device list.

I am looking forward to use some like this: https://www.waveshare.com/product/7.5inch-e-paper-b.htm
with that controller: https://www.waveshare.com/e-paper-esp82 ... -board.htm

Do you think that this displays will be integrated in some version of EspEasy in the future?

I do remember there's some request open in GitHub but not sure about when/if ESPEasy will support those displays.
I think that using 6 GPIOs will limit a lot other devices and as well the memory needed for the bigger ones will be too high (as far as I understood).

I've already a few Waveshare e-ink displays here to implement support for.
So it is pending, but given the amount of work I cannot give you an estimate timeframe.

Note that the bigger screens also have more pixels.
More pixels means more memory needed for the frame buffer and memory is quite limited on the ESP8266.
So maybe the bigger screens can only be supported on the ESP32, which has about the same amount of memory my MSX2 had in 1988, which was a huge step compared to the 1983 MSX1
The difference between the ESP8266 and the ESP32 is about the same, when comparing memory.

Thank you for your answers!

Please tell me, if you reached something and good to hear that you try! For me is is not so important to have many Gpio´s left. I just want to drive such a display for showing some data like weather, or so.
That combined with the possibility to of WiFi and low power consumtion would make a nice weatherstation.... Besides, i like the technology!

It is indeed magnificent technology.
At my previous job, we had some measurement equipment (self made) which allowed focus at micron precision and a depth of field of 10 micron.
That gives you images like these (Kindle 3)

Supported in uPyEasy, since there's a micropython driver for it: https://github.com/dhallgb/eInk-micropython
Writing a plugin that uses the driver isn't that hard to do.
Actually almost all display types (oled,tft,e-ink) have micropython drivers...

@ TD-er: very impressive pic! Thx for sharing!
@ LisaM: The uPyEasy (you developed, right?) is today runnig on ESP32 but not ESP82 right? If so, it should not be a problem to run the display on that device!

Hello,
is there any update or activity on supporting e-ink / epaper displays? I've recenctly bought this waveshare ePaper driver board:
https://www.waveshare.com/e-paper-esp82 ... -board.htm
This is a simple ESP8266 board and waveshare ePaper displays can be connected directly. There is wiki for this driver board and source code for an Arduino project that turns this board into a webserver where an image file can be converted to b/w and uploaded to the display. Upload is using http and some POST requests
Maybe this board is also interensting for the ESPEasy.

It's on the Todo list but we need more sponsors so we can develop full time.

thanks for your fast reply.
Yes, it would be nice to have more time for so many projects
You should add a donation button on the main homepage, in the wiki its too hidden.
Thanks for your great software and support!

I know, plan to make a brand new home page that will make everything so much clearer. Thanks for the idea!

I'm waiting for this plugin too

so... where's "donation" button?

It's right above and below your post

is there some working plugin for e-ink?

is there now some working plugin for e-ink?

Sminter4 wrote: ↑19 Nov 2023, 21:08 is there now some working plugin for e-ink?

For e-ink/ePaper displays we have P096, that's still missing from the released documentation, but I have added documentation in a pending PR. That PR is intended to add some more display models (but I wasn't very successful yet in adding that, mostly because of the lack of documentation ).
The currently supported and working e-ink displays are:
- IL3897 (Lolin 250 x 122px)
- UC8151D (212 x 104px)
- SSD1680 (250 x 212px)
And when creating a Custom build with the proper #define, or using a MAX build:
- Waveshare 2.7" (264 x 176px)

NB: Don't expect displays with the matching resolution, but a different controller, to work as intended, these controllers are very picky about the initialization sequence, and without the technical documentation it's nearly impossible to get that right...

Sminter4 wrote: ↑19 Nov 2023, 21:08 is there now some working plugin for e-ink?

P096, which is included in the "display" build set (and the MAX builds of cours)

Ath wrote: ↑19 Nov 2023, 21:19 For e-ink/ePaper displays we have P096, that's still missing from the released documentation, but I have added documentation in a pending PR. That PR is intended to add some more display models (but I wasn't very successful yet in adding that, mostly because of the lack of documentation ).
The currently supported and working e-ink displays are:
- IL3897 (Lolin 250 x 122px)
- UC8151D (212 x 104px)
- SSD1680 (250 x 212px)
And when creating a Custom build with the proper #define, or using a MAX build:
- Waveshare 2.7" (264 x 176px)

NB: Don't expect displays with the matching resolution, but a different controller, to work as intended, these controllers are very picky about the initialization sequence, and without the technical documentation it's nearly impossible to get that right...

Hello, I'm looking for using a Waveshare 2,7" screen with a Wemos D1 Mini, I don't find any documentation on PR, for example where cabling SPI signals in GPIO ?
Have you got some example to send me ?
Thanks in advance, and many thanks for your great job !

Sylv_01 wrote: ↑27 Feb 2024, 15:07 Hello, I'm looking for using a Waveshare 2,7" screen with a Wemos D1 Mini, I don't find any documentation on PR, for example where cabling SPI signals in GPIO ?
Have you got some example to send me ?
Thanks in advance, and many thanks for your great job !

The connections on the e-Paper board are not that difficult to understand, IMHO. The standard SPI connections MISO, MOSI and CLK are shown on the Hardware page, but most displays only need MOSI -> DIN and CLK -> CLK, and the other required connections, RST, DC and CS are configured on the device configuration page (you can select any available GPIO). The BUSY pin isn't required (and doesn't seem to work well for some displays), so can be left at None.
VCC on the display should be connected to 3V3, and GND to GND, of course.

Hello, thanks for you reply !
Yesterday evening I have upload the "display" build into my Wemos, and have seen that all SPI bus are pinout availability, is great !
So I bought one of 2,7" e-ink display, now I will try to compile a extra build with P096 and P102 plugins together because I want to use a PZEM004-T with this kind of display (P102 plugin is already in "energy" build and P096 for e-ink is on "display" build...)