'tasmota-display' with SSD1306, +Temperature drivers #22897

diyhouse · 2025-01-29T16:26:30Z

diyhouse
Jan 29, 2025

I am trying to compile tasmota-display env,.. with some additional temperature sensor drivers.
The h/w is a simple Nodemcu type board ESP8266 based with a pre-loaded/installed SD1306 display

I am running PlatformIO,.. on a win10 m/c. I am working with source 14.4.1
I have tried using the per-compiled tasmota-display,.. but when I try i2cscan,.. this says there are no I2c devices,.. which is untrue,.. as I have compiled and uploaded the arduino test .ino file for the SD1306,.. which works fine.

I have edited platformio_override.ini as follows:-

; Build variant 2MB = 1MB firmware, 1MB filesystem (most Shelly devices) ;board = esp8266_2M1M ; Build variant 4MB = 1MB firmware, 1MB OTA, 2MB filesystem (WEMOS D1 Mini, NodeMCU, Sonoff POW) board = esp8266_4M2M ;board_build.f_cpu = 160000000L ;board_build.f_flash = 40000000L
In order to capture the board config for a 4meg config so 'Option A3' can be used to ID the display.
and also edit the build environments to build two bin files
; *** Build/upload environment default_envs = ; *** Uncomment the line(s) below to select version(s) tasmota ; tasmota-debug ; tasmota-minimal ; tasmota-lite ; tasmota-knx ; tasmota-sensors tasmota-display ; tasmota-zbbridge

and edited user_config_override.h at the EOF as follows;-
`
#ifndef USE_VEML7700
#define USE_VEML7700 // [I2cDriver50] Enable VEML7700 Ambient Light sensor (I2C addresses 0x10) (+4k5 code)
#endif

#ifndef USE_BMP
#define USE_BMP // [I2cDriver10] Enable BMP085/BMP180/BMP280/BME280 sensors (I2C addresses 0x76 and 0x77) (+4k4 code)
#endif

#ifndef USE_LM75AD
#define USE_LM75AD // [I2cDriver20] Enable LM75AD sensor (I2C addresses 0x48 - 0x4F) (+0k5 code)
#endif

#endif // USER_CONFIG_OVERRIDE_H`

The error messages are as folows:-

`Compiling .pio\build\tasmota-display\lib64c\ESP8266WebServer\detail\mimetable.cpp.o
Archiving .pio\build\tasmota-display\lib64c\libESP8266WebServer.a
Compiling .pio\build\tasmota-display\libd5b\Wire\Wire.cpp.o
F:/Documents/Dev-Projects/PlatormIO/Projects/Tasmota-14.4.1/tasmota/tasmota_xdrv_driver/xdrv_50_filesystem.ino:1692:26: fatal error: ESPFtpServer.h: No such file or
directory

Looking for ESPFtpServer.h dependency? Check our library registry!
CLI > platformio lib search "header:ESPFtpServer.h"
Web > Compiling .pio\build\tasmota-display\libd9f\AT24C256_512\Eeprom24C128_256.cpp.o
https://registry.platformio.org/search?q=header:ESPFtpServer.h

char t[20+UFS_FILENAME_SIZE] = "/ufsu?download=";
^
compilation terminated.
*** [.pio\build\tasmota-display\src\tasmota.ino.cpp.o] Error 1
=================================================================== [FAILED] Took 146.92 seconds ===================================================================

Environment Status Duration

tasmota SUCCESS 00:13:38.097
tasmota-display FAILED 00:02:26.919
=============================================================== 1 failed, 1 succeeded in 00:16:05.016 ===============================================================

The terminal process "C:\Users\mark.platformio\penv\Scripts\platformio.exe 'run'" terminated with exit code: 1. `

I do not understand why it would complain about the ESPFtpServer.h header file as I can confirm the files are present,.. also a I have no spaces in my file PATH.. which is "F:\Documents\Dev-Projects\PlatormIO\Projects\Tasmota-14.4.1"

Is anyone able to offer any suggestions as to why compilation fails.
Many tx

sfromis · 2025-01-29T19:27:25Z

sfromis
Jan 29, 2025

Reading the docs about build customization does tell that you cannot add features to the preconfigured build environments like tasmota-display, you need to start from just tasmota and then add the features you want, in your own custom build enviroment.
https://tasmota.github.io/docs/Compile-your-build/#customize-your-build

It is even directly addressing what you are trying to do:

The typical failure is trying to add sensors to tasmota-display or adding displays to tasmota-sensors. The proper way is to add both sensors and displays to tasmota.

1 reply

diyhouse Jan 29, 2025
Author

Yes,.. I have read over that section several times,... but not registered the details,.. what a Muppet am I.
Thankyou for taking the time to respond to me, I shall move forward with plain Tasmota build,.. and add to that,..
Thankyou

diyhouse · 2025-02-02T14:48:20Z

diyhouse
Feb 2, 2025
Author

I am now making progress,.. I have a compiled environment,.. with a 'display.ini' file which is tweaked for my SSD1305 display,.. as copied from the GitHub repository..
I have changed SCL/SDA assignments,.. ( from provided docs ), and now when I 'i2cscan' I get a device found at '3c',.. which is definitely a step in the right direction.
I have also created a 'display.bat' file in the hope of displaying something on my display.

; clr screen
[z]
; draw full screen picture - corona.rgb file must exist in UFS storage
[x0y0P/corona.rgb]
; define index color
[dc19:31000]
; draw transparent text with new index color
[x60y30f2Ci19D2]Tasmota

Unfortunately I have not had success in applying text or graphics to my display.
I have found many forum bits that talk about Udisplay,.. but I suspect these are 'old' as they seem to contradict more recent stuff.
I have scanned youtube,.. for instructional videos,.. normally a mine of information,. but with udisplay,.. nothing,..
I therefore ask is the a worked examples,. showing the features with verified code etc,. .as I can see uDisplay is pretty amazing and powerful,.. if I could but work though some of the hick-ups of my lack of insight/knowledge...
many Tx

1 reply

sfromis Feb 2, 2025

The docs is the place to start looking, instead of running around for posts or videos.
https://tasmota.github.io/docs/Universal-Display-Driver/#migrating-to-udisplay

Details of what you tried doing matter, like if you included the important point of setting an unused GPIO to Option A3

And do check messages after boot to verify that you get messages about it setting up the display.

diyhouse · 2025-02-02T15:55:49Z

diyhouse
Feb 2, 2025
Author

Ah,.. 'display.ini' in boot messages,.. I don't see anything.. Yes option A3 is set..
Yes I have seen the resource about Migrating,.. which is where I see the potential,..as Udisplay is so clever,.. I just need some more dots to join together..
Boot log and status 0 as follows

00:00:00.001 HDW: ESP8266EX
00:00:00.006 UFS: FlashFS mounted with 1976 kB free
00:00:00.064 CFG: Loaded from File, Count 58
00:00:00.070 QPC: Count 1
00:00:00.081 Project tasmota - Tas_Seventeen Version 14.4.1(tasmota)-2_7_8(2025-02-02T13:34:25)
00:00:01.002 WIF: Connecting to AP1 DiyNet0 Channel 4 BSSId 10:0C:6B:5E:3F:47 in mode 11n as tas-Seventeen...
00:00:02.514 WIF: Connected
00:00:02.769 HTP: Web server active on tas-Seventeen with IP address 192.168.3.139
15:37:01.479 MQT: Attempting connection...
15:37:01.517 MQT: Connected
15:37:01.520 MQT: tele/Tas_Seventeen/LWT = Online (retained)
15:37:01.523 MQT: cmnd/Tas_Seventeen/POWER =
15:37:01.532 MQT: tele/Tas_Seventeen/INFO1 = {"Info1":{"Module":"Generic","Version":"14.4.1(tasmota)","FallbackTopic":"cmnd/DVES_D590FE_fb/","GroupTopic":"cmnd/tasmotas/"}}
15:37:01.539 MQT: tele/Tas_Seventeen/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tas-Seventeen","IPAddress":"192.168.3.139"}}
15:37:01.550 MQT: tele/Tas_Seventeen/INFO3 = {"Info3":{"RestartReason":"External System","BootCount":39}}
15:37:01.919 MQT: stat/Tas_Seventeen/STATUS11 = {"StatusSTS":{"Time":"2025-02-02T15:37:01","Uptime":"0T00:00:05","UptimeSec":5,"Heap":24,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"DiyNet0","BSSId":"10:0C:6B:5E:3F:47","Channel":4,"Mode":"11n","RSSI":36,"Signal":-82,"LinkCount":1,"Downtime":"0T00:00:04"}}}
15:37:01.967 MQT: stat/Tas_Seventeen/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota-display.bin.gz","RestartReason":"External System","Uptime":"0T00:00:05","StartupUTC":"2025-02-02T15:36:56","Sleep":50,"CfgHolder":4617,"BootCount":38,"BCResetTime":"2025-01-26T17:11:43","SaveCount":58,"SaveAddress":"1000"}}
15:37:03.274 QPC: Reset
15:37:05.284 MQT: tele/Tas_Seventeen/STATE = {"Time":"2025-02-02T15:37:05","Uptime":"0T00:00:09","UptimeSec":9,"Heap":24,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"DiyNet0","BSSId":"10:0C:6B:5E:3F:47","Channel":4,"Mode":"11n","RSSI":36,"Signal":-82,"LinkCount":1,"Downtime":"0T00:00:04"}}
15:39:01.196 CMD: status0
15:39:01.231 MQT: stat/Tas_Seventeen/STATUS0 = {"Status":{"Module":18,"DeviceName":"Tas_Seventeen","FriendlyName":["Tasmota_Seventeen"],"Topic":"Tas_Seventeen","ButtonTopic":"0","Power":"0","PowerLock":"0","PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0,"StatusRetain":0},"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota-display.bin.gz","RestartReason":"External System","Uptime":"0T00:02:05","StartupUTC":"2025-02-02T15:36:56","Sleep":50,"CfgHolder":4617,"BootCount":39,"BCResetTime":"2025-01-26T17:11:43","SaveCount":59,"SaveAddress":"3FB000"},"StatusFWR":{"Version":"14.4.1(tasmota)","BuildDateTime":"2025-02-02T13:34:25","Boot":31,"Core":"2_7_8","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"412/699"},"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["DiyNet0",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]},"StatusMEM":{"ProgramSize":731,"Free":1316,"Heap":20,"ProgramFlashSize":4096,"FlashSize":4096,"FlashChipId":"1660C4","FlashFrequency":40,"FlashMode":"DOUT","Features":["0809","8F9AC78F","04368001","200004CF","010013C0","C000F981","00005084","00201000","54000020","00000080","00000000"],"Drivers":"1,2,!3,!4,!5,!6,7,!8,9,10,12,!16,!18,!19,!20,!21,!22,!24,26,!27,29,!30,!35,!37,38,!45,50,62,!68","Sensors":"1,2,3,4,5,6,9,26,71","I2CDriver":"7,!10,20,50"},"StatusNET":{"Hostname":"tas-Seventeen","IPAddress":"192.168.3.139","Gateway":"192.168.3.10","Subnetmask":"255.255.255.0","DNSServer1":"192.168.3.10","DNSServer2":"0.0.0.0","Mac":"98:F4:AB:D5:90:FE","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0},"StatusMQT":{"MqttHost":"homeass.local","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_D590FE","MqttUser":"hamqtt","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4},"StatusTIM":{"UTC":"2025-02-02T15:39:01Z","Local":"2025-02-02T15:39:01","StartDST":"2025-03-30T01:00:00","EndDST":"2025-10-26T02:00:00","Timezone":99,"Sunrise":"07:18","Sunset":"16:49"},"StatusSNS":{"Time":"2025-02-02T15:39:01"},"StatusSTS":{"Time":"2025-02-02T15:39:01","Uptime":"0T00:02:05","UptimeSec":125,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"DiyNet0","BSSId":"10:0C:6B:5E:3F:47","Channel":4,"Mode":"11n","RSSI":38,"Signal":-81,"LinkCount":1,"Downtime":"0T00:00:04"}}}
15:39:37.841 CMD: status 0
15:39:37.850 MQT: stat/Tas_Seventeen/STATUS = {"Status":{"Module":18,"DeviceName":"Tas_Seventeen","FriendlyName":["Tasmota_Seventeen"],"Topic":"Tas_Seventeen","ButtonTopic":"0","Power":"0","PowerLock":"0","PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0,"StatusRetain":0}}
15:39:37.889 MQT: stat/Tas_Seventeen/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota-display.bin.gz","RestartReason":"External System","Uptime":"0T00:02:41","StartupUTC":"2025-02-02T15:36:56","Sleep":50,"CfgHolder":4617,"BootCount":39,"BCResetTime":"2025-01-26T17:11:43","SaveCount":59,"SaveAddress":"3FB000"}}
15:39:37.926 MQT: stat/Tas_Seventeen/STATUS2 = {"StatusFWR":{"Version":"14.4.1(tasmota)","BuildDateTime":"2025-02-02T13:34:25","Boot":31,"Core":"2_7_8","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"412/699"}}
15:39:37.946 MQT: stat/Tas_Seventeen/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["DiyNet0",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]}}
15:39:37.982 MQT: stat/Tas_Seventeen/STATUS4 = {"StatusMEM":{"ProgramSize":731,"Free":1316,"Heap":19,"ProgramFlashSize":4096,"FlashSize":4096,"FlashChipId":"1660C4","FlashFrequency":40,"FlashMode":"DOUT","Features":["0809","8F9AC78F","04368001","200004CF","010013C0","C000F981","00005084","00201000","54000020","00000080","00000000"],"Drivers":"1,2,!3,!4,!5,!6,7,!8,9,10,12,!16,!18,!19,!20,!21,!22,!24,26,!27,29,!30,!35,!37,38,!45,50,62,!68","Sensors":"1,2,3,4,5,6,9,26,71","I2CDriver":"7,!10,20,50"}}
15:39:38.001 MQT: stat/Tas_Seventeen/STATUS5 = {"StatusNET":{"Hostname":"tas-Seventeen","IPAddress":"192.168.3.139","Gateway":"192.168.3.10","Subnetmask":"255.255.255.0","DNSServer1":"192.168.3.10","DNSServer2":"0.0.0.0","Mac":"98:F4:AB:D5:90:FE","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
15:39:38.026 MQT: stat/Tas_Seventeen/STATUS6 = {"StatusMQT":{"MqttHost":"homeass.local","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_D590FE","MqttUser":"hamqtt","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
15:39:38.050 MQT: stat/Tas_Seventeen/STATUS7 = {"StatusTIM":{"UTC":"2025-02-02T15:39:38Z","Local":"2025-02-02T15:39:38","StartDST":"2025-03-30T01:00:00","EndDST":"2025-10-26T02:00:00","Timezone":99,"Sunrise":"07:18","Sunset":"16:49"}}
15:39:38.070 MQT: stat/Tas_Seventeen/STATUS10 = {"StatusSNS":{"Time":"2025-02-02T15:39:38"}}
15:39:38.078 MQT: stat/Tas_Seventeen/STATUS11 = {"StatusSTS":{"Time":"2025-02-02T15:39:38","Uptime":"0T00:02:42","UptimeSec":162,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"DiyNet0","BSSId":"10:0C:6B:5E:3F:47","Channel":4,"Mode":"11n","RSSI":38,"Signal":-81,"LinkCount":1,"Downtime":"0T00:00:04"}}}
15:42:05.258 MQT: tele/Tas_Seventeen/STATE = {"Time":"2025-02-02T15:42:05","Uptime":"0T00:05:09","UptimeSec":309,"Heap":21,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"DiyNet0","BSSId":"10:0C:6B:5E:3F:47","Channel":4,"Mode":"11n","RSSI":34,"Signal":-83,"LinkCount":1,"Downtime":"0T00:00:04"}}
15:46:55.230 APP: Serial logging disabled
15:47:05.276 MQT: tele/Tas_Seventeen/STATE = {"Time":"2025-02-02T15:47:05","Uptime":"0T00:10:09","UptimeSec":609,"Heap":21,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"DiyNet0","BSSId":"10:0C:6B:5E:3F:47","Channel":4,"Mode":"11n","RSSI":36,"Signal":-82,"LinkCount":1,"Downtime":"0T00:00:04"}}

0 replies

sfromis · 2025-02-02T16:23:38Z

sfromis
Feb 2, 2025

Boot time messages with working setup.

00:00:00.085 DSP: File descriptor used
00:00:00.086 I2C: SSD1306 found at 0x3c
00:00:00.339 DSP: SSD1306 initialized

Of course, you need the correct build setup to have the universal driver included. As a minimum:

#define USE_DISPLAY
#define USE_UNIVERSAL_DISPLAY

Here's the pertinent section from the precompiled display builds.

Tasmota/tasmota/include/tasmota_configurations.h

Lines 356 to 381 in e8ca960

    
           #define USE_DISPLAY                              // Add Display Support (+2k code) 
        
             #define USE_DISPLAY_TM1637                     // [DisplayModel 15] Enable TM1637 module 
        
             #define USE_DISPLAY_MAX7219                    // [DisplayModel 19] Enable MAX7219 7-segment module 
        
           #define USE_TM1638                               // Add support for TM1638 switches copying Switch1 .. Switch8 (+1k code) 
        
           #define USE_I2C                                  // I2C using library wire (+10k code, 0k2 mem, 124 iram) 
        
             #define USE_DISPLAY_MODES1TO5                  // Enable display mode 1 to 5 in addition to mode 0 
        
             #define USE_DISPLAY_LCD                        // [DisplayModel 1] Enable Lcd display (I2C addresses 0x27 and 0x3F) (+6k code) 
        
             // REMOVED - #define USE_DISPLAY_SSD1306                    // [DisplayModel 2] Enable SSD1306 Oled 128x64 display (I2C addresses 0x3C and 0x3D) (+16k code) 
        
             #define USE_DISPLAY_MATRIX                     // [DisplayModel 3] Enable 8x8 Matrix display (I2C adresseses see below) (+11k code) 
        
             #define USE_DISPLAY_SEVENSEG                   // [DisplayModel 11] [I2cDriver47] Enable sevenseg display (I2C addresses 0x70 - 0x77) (<+11k code) 
        
             // REMOVED - #define USE_DISPLAY_SH1106                     // [DisplayModel 7] Enable SH1106 Oled 128x64 display (I2C addresses 0x3C and 0x3D) 
        
           //  #define USE_DISPLAY_TM1650                     // [DisplayModel 20] [I2cDriver74] Enable TM1650 display (I2C addresses 0x24 - 0x27 and 0x34 - 0x37) 
        
           #define USE_SPI                                  // Hardware SPI using GPIO12(MISO), GPIO13(MOSI) and GPIO14(CLK) in addition to two user selectable GPIOs(CS and DC) 
        
             // #define USE_DISPLAY_ILI9341                    // [DisplayModel 4] Enable ILI9341 Tft 480x320 display (+19k code) 
        
             // #define USE_DISPLAY_EPAPER_29                  // [DisplayModel 5] Enable e-paper 2.9 inch display (+19k code) 
        
             // #define USE_DISPLAY_EPAPER_42                  // [DisplayModel 6] Enable e-paper 4.2 inch display 
        
             // #define USE_DISPLAY_ILI9488                    // [DisplayModel 8] 
        
             // #define USE_DISPLAY_SSD1351                    // [DisplayModel 9] 
        
             // #define USE_DISPLAY_RA8876                     // [DisplayModel 10] 
        
             // REMOVED - #define USE_DISPLAY_ST7789                     // [DisplayModel 12] Enable ST7789 module 
        
           #define USE_UNIVERSAL_DISPLAY 
        
           #define USE_UNIVERSAL_TOUCH

2 replies

diyhouse Feb 2, 2025
Author

Yes,.. now we are getting warm,... the inclusion of '#define USE_DISPLAY',.. now shows the display is present at boot time,..
I assume this also means it is running the display.ini file, as it states 'initialised',...
Getting adventurous I have now set 'DisplayModel 2',.. and tried some displaytext commands,.. which although I understand are legacy,.. should still work,.. but as yet my display does not illuminate with 'any lights',.. or text..
Any Thoughts on how I might 'write' some text
Many Tx

00:00:00.002 HDW: ESP8266EX 00:00:00.010 UFS: FlashFS mounted with 1976 kB free 00:00:00.066 CFG: Loaded from File, Count 61 00:00:00.071 QPC: Count 1 00:00:00.087 I2C: SSD1306 found at 0x3c 00:00:00.218 DSP: SSD1306 initialized 00:00:00.593 Project tasmota - Tas_Seventeen Version 14.4.1(tasmota)-2_7_8(2025-02-02T16:46:49)

sfromis Feb 2, 2025

Well, you should not mess around with DisplayModel, Tasmota telling you that it uses 17 for universal display is the only "right" function with regular pixel displays. It should not even accept 2 (as in telling you what value was set), but just report 17.

Not clear if you made sure to also have #define USE_UNIVERSAL_DISPLAY

And be sure to also power on the display, using command or front page toggle. Nothing will appear if it is off.

diyhouse · 2025-02-02T19:36:19Z

diyhouse
Feb 2, 2025
Author

Ah yes I am currently using two #12602

#define USE_DISPLAY
#define USE_UNIVERSAL_DISPLAY

I was initially only using the USE_UNIVERSAL_DISPLAY,..
Hence one of my problems,.. ( Not using USE_DISPLAY )
Yes Using DisplayModel only reports back using DisplayModel 17,.. so clearly tasmota does NOT want to change it,...
Power,.. oh,.. that's a new one on me,... Display is physically attached to nodemcu type board,... I was wondering where/why/what the toggle was attached to...
have tried the following...
19:24:53.308 CMD: displaytext hello world 19:24:53.321 MQT: stat/Tas_Seventeen/RESULT = {"DisplayText":"hello world"} 19:25:03.275 MQT: stat/Tas_Seventeen/RESULT = {"POWER":"OFF"} 19:25:03.279 MQT: stat/Tas_Seventeen/POWER = OFF 19:25:14.281 CMD: displaytext hello world 19:25:14.293 MQT: stat/Tas_Seventeen/RESULT = {"DisplayText":"hello world"} 19:25:33.653 MQT: stat/Tas_Seventeen/RESULT = {"POWER":"ON"} 19:25:33.658 MQT: stat/Tas_Seventeen/POWER = ON 19:25:45.228 CMD: displaytext hello world 19:25:45.241 MQT: stat/Tas_Seventeen/RESULT = {"DisplayText":"hello world"}

And still the display is blank... BTW I am using the 'given SSD1306 descriptors'
descriptor file as above,.. with one change,.. that top header line that the reset pin is no used
:H,SSD1306,128,64,1,I2C,3C,*,*,-1
Many Tx for your help

2 replies

sfromis Feb 2, 2025

Do check your value for DisplayMode - values different from 0 can only work if the build includes #define USE_DISPLAY_MODES1TO5, but those modes are not very useful if you want to put your own stuff on the display.

BTW. That change you did to the first line makes no sense, as * simply means that it will use it if some gpio is configured for the purpose. Better avoid changes unless you know a good reason for it, as you risk running into extra trouble the further you deviate from the basic setup.

diyhouse Feb 3, 2025
Author

Hi,. Checked current status of DisplayMode,.. and this appeared to be Zero... reverted 1306 driver to 3 Stars,.. and situation remained as before.
Decided to give RAW tasmota-display.bin another go,.. with newly gained knowledge,.. and known i2c pins... did a clean install,.. and even though A3 was set I could not get the additional display file system to show up, i2cscan did show 1306 was present at 0x3C, but that was all, but no additional file system access,.. so gave up on that install, and went back to my previously compiled version with #defines and using the board = esp8266_4M2M (within the platform_override.io file).
Downloaded code,.. reset nodemcu board,.. did a 'displaytext hello world'.
It worked!! I can at least display one simple line of text,.. ( of to try some more adventurous stuff now )
I can only assume something in my configs had gone gaga,.. and the 'full-reset' fixed it.
Many tx for your help,.. and little pointers,. of guidance which helped considerably in my debug quest as to what output 'should be' etc

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

'tasmota-display' with SSD1306, +Temperature drivers #22897

{{title}}

Replies: 5 comments 6 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

'tasmota-display' with SSD1306, +Temperature drivers #22897

diyhouse Jan 29, 2025

Replies: 5 comments · 6 replies

sfromis Jan 29, 2025

diyhouse Jan 29, 2025 Author

diyhouse Feb 2, 2025 Author

sfromis Feb 2, 2025

diyhouse Feb 2, 2025 Author

sfromis Feb 2, 2025

diyhouse Feb 2, 2025 Author

sfromis Feb 2, 2025

diyhouse Feb 2, 2025 Author

sfromis Feb 2, 2025

diyhouse Feb 3, 2025 Author

diyhouse
Jan 29, 2025

Replies: 5 comments 6 replies

sfromis
Jan 29, 2025

diyhouse Jan 29, 2025
Author

diyhouse
Feb 2, 2025
Author

diyhouse
Feb 2, 2025
Author

sfromis
Feb 2, 2025

diyhouse Feb 2, 2025
Author

diyhouse
Feb 2, 2025
Author

diyhouse Feb 3, 2025
Author