OLED Display support

[rlust]

Checking to see if any display support is planned for the future?
I see great value in using OLED displays for non SONOFF devices, like WEMOS.

[Jason2866]

Should be possible with LiquidCrystal I2C but this lib needs space....
https://github.com/marcoschwartz/LiquidCrystal_I2C
or for OLED
https://github.com/adafruit/Adafruit_SSD1306

[arendst]

I have some display support running for over a year but it is very user unfriendly as it only allows displaying of MQTT messages without user intervention. Displays supported are LCD, Oled, TFT and up to 8 matrices. AT home they run fine.

I might release a branch without support just for you to see what is possible.

[arendst]

See https://github.com/arendst/Sonoff-Tasmota/tree/development_display

This is with NO support.

[rlust]

Got it loaded, not sure how to set options?
I will continue reading code.
I am using a I2C OLED display.
Anyone have any luck here?

[Jason2866]

Hello @rlust,
i am in the same boat. Got it running. Display shows Time and Date after boot.
@arendst could you give me/us just one short example, i am not a programmer so reading code isnt easy for me. But when i get a hint i get things sorted ;-) For testing i have connected a DS18B20 (Temperature is shown on Web Console)
Thx a lot, if you do not, it is 100% fine!! You said NO support ;-)
P.S.
And thank you again for your great pice of software!! With this my long wanted plan realizing
a powerful and inexpensive smart home solution (without a cloud) was made possible.

[arendst]

Currently all displays have the possibility to show life MQTT messages. This probably only works when the default prefixes are used. The display driver receives all tele messages and decodes the JSON text and should display information like

Settings:

14:39:16 CMD: displaymodel
14:39:16 MQT: stat/wemos9/RESULT = {"DisplayModel":2}
14:39:20 CMD: displaymode
14:39:20 MQT: stat/wemos9/RESULT = {"DisplayMode":5}
14:39:33 CMD: displayrefresh
14:39:33 MQT: stat/wemos9/RESULT = {"DisplayRefresh":2}
14:39:45 CMD: power
14:39:45 MQT: stat/wemos9/RESULT = {"POWER":"ON"}
14:39:45 MQT: stat/wemos9/POWER = ON
14:39:56 CMD: displayrows
14:39:56 MQT: stat/wemos9/RESULT = {"DisplayRows":8}
14:40:01 CMD: displaycols
14:40:01 MQT: stat/wemos9/RESULT = {"DisplayCols1":21}

Settings:

15:41:23 CMD: displaymodel
15:41:23 MQT: stat/ticker/RESULT = {"DisplayModel":3}
15:41:28 CMD: displaymode
15:41:28 MQT: stat/ticker/RESULT = {"DisplayMode":5}
15:41:34 CMD: displayrefresh
15:41:34 MQT: stat/ticker/RESULT = {"DisplayRefresh":1}
15:41:38 CMD: power
15:41:38 MQT: stat/ticker/RESULT = {"POWER":"ON"}
15:41:38 MQT: stat/ticker/POWER = ON
15:41:49 CMD: displayrows
15:41:49 MQT: stat/ticker/RESULT = {"DisplayRows":2}
15:41:54 CMD: displaycols
15:41:54 MQT: stat/ticker/RESULT = {"DisplayCols1":32}

Settings:

15:42:46 CMD: displaymodel
15:42:46 MQT: stat/lcd/RESULT = {"DisplayModel":1}
15:42:50 CMD: displaymode
15:42:50 MQT: stat/lcd/RESULT = {"DisplayMode":4}
15:42:58 CMD: displayrefresh
15:42:58 MQT: stat/lcd/RESULT = {"DisplayRefresh":2}
15:43:01 CMD: power
15:43:01 MQT: stat/lcd/RESULT = {"POWER":"ON"}
15:43:01 MQT: stat/lcd/POWER = ON
15:43:07 CMD: displayrows
15:43:07 MQT: stat/lcd/RESULT = {"DisplayRows":2}
15:43:11 CMD: displaycols
15:43:11 MQT: stat/lcd/RESULT = {"DisplayCols1":16}
15:43:24 CMD: displayaddress
15:43:24 MQT: stat/lcd/RESULT = {"DisplayAddress1":39}

Settings:

15:44:10 CMD: displaymodel
15:44:10 MQT: stat/tft/RESULT = {"DisplayModel":4}
15:44:14 CMD: displaymode
15:44:14 MQT: stat/tft/RESULT = {"DisplayMode":5}
15:44:21 CMD: displayrefresh
15:44:21 MQT: stat/tft/RESULT = {"DisplayRefresh":2}
15:44:24 CMD: power
15:44:24 MQT: stat/tft/RESULT = {"POWER":"ON"}
15:44:24 MQT: stat/tft/POWER = ON
15:44:28 CMD: displayrows
15:44:28 MQT: stat/tft/RESULT = {"DisplayRows":2}
15:44:34 CMD: displaycols
15:44:34 MQT: stat/tft/RESULT = {"DisplayCols1":20}

[Jason2866]

THANK you!
More explenations as hoped!
With that the last open point in my Smart Home project is going to be solved.
I need a few simple and cheap devices that displays some parameters (temperature, humidity)😃

[arendst]

I used double sided tape and wire-wrap to mount the wemos to the TFT display:

[rlust]

Thanks so much Arendst, your work is invaluable!
Well done as always!

Jason2886, are you able to work with me on this to understand how you got a display?
My email is rlust_at_mac.com

[Jason2866]

@rlust
Which type of display do you want OLED or LCD Dot Matrix (how many rows and lines)?
To find is really simple. For OLED search for SSD1306 and for LCD with a I2C interface
For example https://www.aliexpress.com/wholesale?catId=0&initiative_id=SB_20180430063646&SearchText=Ssd1306
or
https://www.aliexpress.com/wholesale?catId=0&initiative_id=SB_20180430063755&SearchText=Lcd+i2c

[rlust]

I have an OLED .96 like option 1
128x64
What changes did you make in 06_display.ino?
I am able to scan I2C and see the address 0x3c.

[Jason2866]

@arendst Nice, reliable and quick solution. I like it too. In my very early years it was part of my job. Would be nice to own a electric wire rapp machine for private use...

[arendst]

In my early days, fixing backplanes, I used a battery powered wire-wrap tool too but the battery has left this planet so I have to use an old, once bought from Tandy wire-wrap manual tool which does the job perfectly.

[Jason2866]

@rlust just added in user_config.h
around line 264:
#define USE_DISPLAY // Add I2C code for Diplays

Nothing changed in 06_display.ino
Time and Date is on the display at start. I´m not at home so i can try the commands from Theo
later the day....
Comment from source code 06_display.ino (line 977):
`/*

• Matrix               LCD / Oled                           TFT
  

• 0 = Clear display
• 1 = Text up and time Time
• 2 = Date Local sensors Local sensors
• 3 = Day Local sensors and time Local sensors and time
• 4 = Mqtt left and time Mqtt (incl local) sensors Mqtt (incl local) sensors
• 5 = Mqtt up and time Mqtt (incl local) sensors and time Mqtt (incl local) sensors and time
  */`

[Jason2866]

@arendst I know this hand wrap tool too. Mine still works pretty well after many years!
And it is a good training for the hand muscels ;-)
How do you power your devices? Have you a setup with a low Voltage DC wiring?
Maybe you have a good best practice tipp here too?
I use this little things to (hopefully) safeley power my WeMinis:
https://www.aliexpress.com/item/1pcs-HLK-PM01-AC-DC-220V-to-5V-mini-power-supply-module-intelligent-household-switch-power/32319515750.html?spm=a2g0s.9042311.0.0.4wV9Ez

[rlust]

Got it working!!!
It is picking up all of my temperature readings.
This is fantastic!
Thanks Jason for the guidance!
arendst you made my day, this really is a great feature!!!!!!
Now to pull out my old wire wrap toll and get a larger display.
I also spent to many days back in tech school doing wire wrap :)

[arendst]

I use a 5V/3A power supply feeding the matrix unit. From there I use USB cables to TFT and LCD. The oled is currently fed by a USB to FTDI converter as the onboard USB connector broke off the board within an hour of use ;-(

They all could have been fed by a decent USB power supply.

[ascillato]

Amazing! Thanks for sharing 👍

[sharpn]

Is there a specific build that needs to be uploaded to the device to get this working?

[Jason2866]

Yes, branch development-display

[bollitec]

@arendst, many thanks for your picture with wemos and tft display, can you please send a higher resolution or the pin assignments (wemos - tft) ?

Like to test the branch and have some idea with touch screen display from raspi.

Thanks a lot!

[abaszczok]

Guys... I can not get it running... I setup display mode model etc... I got OLED 128x64 + D1 mini, which device type did you select in config module?? "generic?" .. I put #define USE_DISPLAY.. what else I'm missing/??? I tested this display + D1 on ESPeasy - the depslay is OK.. any hints?

[abaszczok]

Got it working.... pull up resistors 4,7k - ESPeasy you dont need to use them - they are internally proramable..
@arendst - you'r my hero !!! - keep it rolling

[Jason2866]

I received my TFT today. If someone doesnt know how to connect the TFT Display (SPI).
Take a look here:
http://microcontrollerkits.blogspot.de/2015/11/esp8266-wifi-tftlcd.html
CS and DC has to be cofigured over web console in module generic. See picture

I used not GPIO 2 and 5 as in description example. I used GPIO 15 and 16.

[vMeph]

hi @arendst was trying this comands not working

21:04:49 CMD: displaymode1
21:04:49 MQT: stat/sonoff/RESULT = {"Command":"Unknown"}

[Jason2866]

Habe you used the correct branch Development-Display?

[vMeph]

Yes mate
https://github.com/arendst/Sonoff-Tasmota/tree/development_display

[shivasiddharth]

Can you fork https://github.com/gemu2015/Sonoff-Tasmota and upload your changes ? If its too much to ask, may be then you can just zip the folder and attach the zip here.

[dr-apple]

I used double sided tape and wire-wrap to mount the wemos to the TFT display:

Can you please tel me the pin connecting vom esp to the the display ?

And a picture from the tasmota config ?

Thank you...

[arendst]

This sounds correct #2557 (comment) but this also works:

2.2 TFT SPI 240x320 --> Wemos D1 mini
TFT ------   Wemos ------
1 Vcc        3V3
2 Gnd        Gnd
3 CS         D8  GPIO15
4 Reset      Rst
5 DC/RS      D0  GPIO16
6 SDI/MOSI   D7  GPIO13
7 SCK        D5  GPIO14
8 LED        D2  GPIO04 
9 SDO/MISO   D6  GPIO12

with following config:

[dr-apple]

Thank you very much :-) It Works !

[moneybag]

It works for my LCD-Display.
But how can I make published MQTT-Data visible on the LCD?

[red-kooga]

@shivasiddharth, would be a bit long to write it in a post. Essentially I've cloned the ili9341 driver, which basically has the same controls, I've dropped in the Adafruit ST7735 Library and the latest Adafruit GFX 1.3.2. Then added some functions missing in the ST7735 cpp file, such as scrollTo(). Then I've add a new USE_DISPLAY_ST7735 define. I'm thinking of forking the tasmota sources, but it would be near impossibile for me alone to manage that, and I'm not really sure I've done all the things to support the new driver correctly. I'm still learning how tasmota works and something is not really clear, I'm not a full time developer. What do you think is the best way to share the modifications? (I've also integrated the latest IRRemote libraries because I needed the latest ir_Daikin.h)

Hi could you fork and not manage, i have been trying to add a nokia display without success i have several ST7735 displays i was going to try next it would save a lot of work.
Thanks

[raidolo]

@red-kooga @shivasiddharth (cc. @arendst )

I've created a new branch:

https://github.com/raidolo/Sonoff-Tasmota/tree/ST7735-irDaikin

I've forked and committed my changes for these things:

• Added Adafruit ST7735 Display library for the SPI displays:
  Created a new display driver based on the ili9341 driver: xdsp_05_st7735.ino
  You should set SPI CS and DC pins in the module configuration using the web ui.
  (I've set mine to GPIO15 D8 and GPIO16 D0 on my Wemos nodemcu replica)

• Upgraded to the latest IRRemote library for Daikin AC conditioner and implemented Daikin HVAC in xdrv_05_irremote.ino
  You have to use IRHvac commands as all other hvacs systems, all modes supported Auto, Heat, Cool, Dry, Fan, I need to implement Swing modes and Confort modes supported by the new lib

Please try it and let me know the results!

[red-kooga]

Thanks raidolo, I will try soon as I can

[bastelfix]

Hi @raidolo
just tested your fork with an 1,77" 160(RGB)x128 ST7735 SPI-Display.
With v6.4 i got mirrored display content and some obstacles like here: #2557 (comment)
With your forked version it works fine, besides from some lines "eaten" at the top (maybe one or two pixels, may be hardwareproblem with this cheap thing) and crappy green bars. If you need photos please tell me.

Pinout from "1,77" 160(RGB)x128 ST7735 SPI-Display" to Wemos D1 mini
1 – GND – Ground
2 – VCC – 3.3V
3 – SCL – Serial Clock --> D5/SCK/GPIO14
4 – SDA – Serial Data Input --> D7/MOSI/GPIO13
5 – EWA – LCM Reset (bei Betrieb HIGH)
6 – DC – Data/Command Control -->D0/GPIO16
7 – CS – Chip Select -->D1/GPIO5
8 – BLK – Beleuchtung --> ? (theres a toggle button at webgui, anyone know which port it is toggling? do i need to define a led/relay to toggle it?)

[raidolo]

@bastelfix my 1.8” works pretty good.
It’s the original adafruit lib so, I dunno if you have hardware problems. You could try to upload the graphictest sketch first (you have the ino file in the examples for inside the library itself), just to be sure it’s not related to the driver I wrote.
Yeah, post some photos!

[bastelfix]

How to upload that single graphictest sketch within atom/platformio? When i "build", platformio compiles the whole project. If i open the example-folder in Atom, it tells me plattformio.ino is missing in this folder.
€dith means: the examples are written for arduino and i have to hook up the display to an arduino. thx jason2866
all pics: Displaymode 5
Pic 1: Firmware v6_3 prebuild release-bin

Pic2: Firmware raidolo self-compiled; imagerotate 0

Pic 3: Firmware raidolo self-compiled; imagerotate 1

(- don't worry about displaycols not set right)

• green bars only show up at displayrotate 0
• (no pic) displaytext is working well

--> just have to test with this graphictest wether the line at the left and the line at the bottom are hardware-errors (but i think since the "displaymode-5-text" is is postponed one pixel in x and one pixel in y it seems like there is a align-problem in the tasmota-firmware?)

[raidolo]

@bastelfix Uh, the green bars are probably my fault, I’ve set them somewhere in the code while testing! Sorry for that, I’ll fix them tomorrow if I have sometime, but it’s not an issue with the display. I didn’t notice them before the upload because I’m using displaymode 0, to set my own text with the displaytext commands.
The last line at the bottom and the right one to me looks like a rows/cols issue?
Try DisplayMode 0, and then some DisplayText command, I think I’ve messed up a bit the default DisplayMode 4 because I don’t use it, nothing too hard to fix anyway.
Just let me know if the custom text is working fine.

[raidolo]

@bastelfix I've committed few changes to bring back the default behaviour of tasmota 6.3 with DisplayModes 1-5

raidolo@d4c1f26

You still have to set DisplayCols Rows, and Rotation.
Here are mine:

09:56:03 MQT: stat/thermo/RESULT = {"DisplayCols1":27}
09:56:09 CMD: DisplayRows
09:56:09 MQT: stat/thermo/RESULT = {"DisplayRows":15}
09:56:16 CMD: DisplayRotate
09:56:16 MQT: stat/thermo/RESULT = {"DisplayRotate":1}

Hope that helps.

Cheers!

[AalianKhan]

Is It possible to make little icons/picture/drawings for an LCD display? I want to show this icon 🔥 but I only have an LCD display. I also want to show °.

[Edelfalke]

Hello Raidolo,

i have tried your code, but it won't compile.
I've got a lot of errors:

`xdrv_03_energy:169:29: error: invalid use of Boolean expression as operand to 'operator--'

 energy_power_steady_cntr--;

                         ^

xdrv_03_energy:197:95: error: invalid initialization of reference of type 'byte& {aka unsigned char&}' from expression of type 'bool'

 if (EnergyMargin(0, Settings.energy_min_power, energy_power_u, flag, energy_min_power_flag)) {

                                                                                           ^

xdrv_03_energy:139:9: error: in passing argument 5 of 'boolean EnergyMargin(byte, uint16_t, uint16_t, byte&, byte&)'

boolean EnergyMargin(byte type, uint16_t margin, uint16_t value, byte &flag, byte &save_flag)

     ^

xdrv_03_energy:201:95: error: invalid initialization of reference of type 'byte& {aka unsigned char&}' from expression of type 'bool'

 if (EnergyMargin(1, Settings.energy_max_power, energy_power_u, flag, energy_max_power_flag)) {

                                                                                           ^

xdrv_03_energy:139:9: error: in passing argument 5 of 'boolean EnergyMargin(byte, uint16_t, uint16_t, byte&, byte&)'

boolean EnergyMargin(byte type, uint16_t margin, uint16_t value, byte &flag, byte &save_flag)

     ^

xdrv_03_energy:205:101: error: invalid initialization of reference of type 'byte& {aka unsigned char&}' from expression of type 'bool'

 if (EnergyMargin(0, Settings.energy_min_voltage, energy_voltage_u, flag, energy_min_voltage_flag)) {

                                                                                                 ^

xdrv_03_energy:139:9: error: in passing argument 5 of 'boolean EnergyMargin(byte, uint16_t, uint16_t, byte&, byte&)'

boolean EnergyMargin(byte type, uint16_t margin, uint16_t value, byte &flag, byte &save_flag)

     ^

xdrv_03_energy:209:101: error: invalid initialization of reference of type 'byte& {aka unsigned char&}' from expression of type 'bool'

 if (EnergyMargin(1, Settings.energy_max_voltage, energy_voltage_u, flag, energy_max_voltage_flag)) {

                                                                                                 ^

xdrv_03_energy:139:9: error: in passing argument 5 of 'boolean EnergyMargin(byte, uint16_t, uint16_t, byte&, byte&)'

boolean EnergyMargin(byte type, uint16_t margin, uint16_t value, byte &flag, byte &save_flag)

     ^

xdrv_03_energy:213:101: error: invalid initialization of reference of type 'byte& {aka unsigned char&}' from expression of type 'bool'

 if (EnergyMargin(0, Settings.energy_min_current, energy_current_u, flag, energy_min_current_flag)) {

                                                                                                 ^

xdrv_03_energy:139:9: error: in passing argument 5 of 'boolean EnergyMargin(byte, uint16_t, uint16_t, byte&, byte&)'

boolean EnergyMargin(byte type, uint16_t margin, uint16_t value, byte &flag, byte &save_flag)

     ^

xdrv_03_energy:217:101: error: invalid initialization of reference of type 'byte& {aka unsigned char&}' from expression of type 'bool'

 if (EnergyMargin(1, Settings.energy_max_current, energy_current_u, flag, energy_max_current_flag)) {

                                                                                                 ^

xdrv_03_energy:139:9: error: in passing argument 5 of 'boolean EnergyMargin(byte, uint16_t, uint16_t, byte&, byte&)'

boolean EnergyMargin(byte type, uint16_t margin, uint16_t value, byte &flag, byte &save_flag)

     ^

xdrv_03_energy:258:30: error: invalid use of Boolean expression as operand to 'operator--'

       energy_mplr_counter--;

                          ^

exit status 1
invalid use of Boolean expression as operand to 'operator--'`

How can i compile this code?

[grego1981]

Hi all, newbie here! I have compiled the latest developement with following https://github.com/arendst/Tasmota/wiki/Displays and when trying to run display command i get {"Command":"Unknown"} is there something else I must do?

[adamrunner]

@grego1981 - I got the same results, you need to be sure to configure the screen properly first with the correct pin mappings within the Module menu first.

[saikek]

Check that you have tasmota module uncommented in platformio.ini.
I've just tested my 16x2 and 128x32 displays and after few hours they are working!

[maddingamer]

Hi all, I'm trying to use SSD1306 OLED display.
But whatever I do, screen keeps dark.
Using commands like displaytext returning no errors.
GPIOs set in configuration.
I2Cscan finds device at 0x3c.

Any ideas? :)

[saikek]

Hi all, I'm trying to use SSD1306 OLED display.
But whatever I do, screen keeps dark.
Using commands like displaytext returning no errors.
GPIOs set in configuration.
I2Cscan finds device at 0x3c.

Any ideas? :)

Could you try running all commands - like setting mode, resolution, displaymode, displaymodel ?
Start with displaymode that prints just local time.
Also try mqtt_topic/cmnd/POWER off and mqtt_topic/cmnd/POWER on.

That helped me, but i was not able to find patterns for that.

[maddingamer]

reflashed my device after couple of days off.. now it just works magically ^^
Now I only have to figure out on how to increase size of the text displayed and how to display mqtt stuff.. thx tho saikek :)

[ril3y]

I know this thread has some old content in it but is it still required to use the development branch to get OLED i2c displays working?

[saikek]

I know this thread has some old content in it but is it still required to use the development branch to get OLED i2c displays working?

No, it works on release 8.10 version for me.

[Quart666]

Got it working. Struggled a couple of hours yesterday, so I tried a noterh Vemos D1 today and it worked direct, so my old D1 is now in the trash.
How can I get just some of my MQTT topics and messages displayed? Right now it shows all other Tasmota topics and values.

[scargill]

I am struggling with the SH1106 display - compiled tasmota with that display in......

it is appearing at address 3C (correct). in the console I turned power ON.

it is wired correctly - "displaymode 0" (no quotes) produces nothing. "displaymode 1" gives me what looks like it might be a line of time followed by a line of date... but garbled -where the seconds would be is changing every second. "displaytext hello" - indeed "displaytext ANYTHING" does zilch.

[A1121218]

can someone help me I want write coding. but confused where to start, its soo urgent