Change contrast/brightness of ssd1306 oled display

[pimlie]

Is it possible to change the brightness of a SSD1306 OLED display with the Universal Display Driver? I have added :D,81 to the display.ini but that doesnt seem to change the contrast/brightness at all (the only thing that happens is that the screen turns off when calling DisplayDimmer 0)

More generally, it would be awesome if Tasmota also supported this kind of logic to set the brightness by using a combination of precharge/constrast & vcomdetect. It seems this isn't supported yet or did I miss something?

[s-hadinger]

Definitely a good idea. I'm not familiar with those settings on OLED. What device do you have?

[pimlie]

Currently working on a https://templates.blakadder.com/air-gradient-pro.html, so Wemos D1 Mini :) Also see here

My current build config (used with TasmoCompiler and the `Wemos/NodeMCU` board)

// For sensors
#define USE_I2C

// Sensors
#define USE_SHT
#define USE_SHT3X
#define USE_SENSEAIR
#define USE_PMS5003
#define USE_SGP4X

#ifndef USE_RULES
#define USE_RULES
#endif

// Timers
#define USE_TIMERS
#define USE_TIMERS_WEB

// Control through HA / WEB
#define USE_HOME_ASSISTANT
#define USE_WEBSERVER

// For Internal Filesystem
#define USE_UFILESYS
#define GUI_TRASH_FILE
#define GUI_EDIT_FILE

// Display
#define USE_DISPLAY
#define USE_UNIVERSAL_DISPLAY

#ifdef USER_TEMPLATE
#undef USER_TEMPLATE
#endif
#define USER_TEMPLATE "{\"NAME\":\"AirGradient Pro v3\",\"GPIO\":[1600,1,1632,0,640,608,1,1,1664,1,1696,1,5730,1],\"FLAG\":0,\"BASE\":18}"
// This runs the first time the firmware is installed.
#define USER_BACKLOG "Module 0; DisplayMode 0; PulseTime1 5 Power2 On; Power3 On; Rule1 On; Rule2 On; Power1 On"

// Watchdog keep alive
#ifdef USER_RULE1
#undef USER_RULE1
#endif
#ifndef USER_RULE1
#define USER_RULE1 "On Time#Minute DO Power1 On ENDON"
#endif

// Display sensor values on sensor event updates
#ifdef USER_RULE2
#undef USER_RULE2
#endif
#define USER_RULE2 \
"ON SHT3X#Temperature DO DisplayText [s1l1c1]T: %value%C ENDON " \
"ON SHT3X#Humidity DO DisplayText [s1l1c11]H: %value%% ENDON " \
"ON S8#CarbonDioxide DO DisplayText [s1l2c1]CO2: %value% ppm ENDON " \
"ON PMS5003#PM2.5 DO DisplayText [s1l3c1]PM2.5: %value% ENDON " \
"ON PMS5003#PM10 DO DisplayText [s1l3c11]PM10: %value% ENDON " \
"ON PMS5003#PB0.3 DO DisplayText [s1l4c1]PB.3: %value% ENDON " \
"ON SGP40#TVOC DO DisplayText [s1l5c1]TVOC: %value% ENDON " \
"ON tele-DisplayText [s1l6c1] ENDON"

// Configure display driver
#define DSP_ROM_DESC \
":H,SSD1306,128,64,1,I2C,3c,*,*,*\n" \
":S,0,2,1,0,30,20\n" \
":I\n" \
"AE\n" \
"D5,80\n" \
"A8,3F\n" \
"D3,00\n" \
"40\n" \
"8D,14\n" \
"20,00\n" \
"A1\n" \
"C8\n" \
"DA,12\n" \
"81,9F\n" \
"D9,F1\n" \
"DB,40\n" \
"A4\n" \
"A6\n" \
"AF\n" \
":o,AE\n" \
":O,AF\n" \
":A,00,10,40,00,00\n" \
":D,81\n" \
":i,A6,A7\n" \
"#\n"

[s-hadinger]

Oh. Esp8266...
It would be much easier on esp32 or variant like esp32c3

[pimlie]

Why is that, due to berry support?

[s-hadinger]

Yes. We could add specific Berry code for this. Otherwise that means a Tasmota wide impact for non-OLED displays

[pimlie]

Wouldn't that be a direct result of and a major downside of the move to a universal display driver? A universal driver is fine but it should preferably also still be possible to abstract logic for specific displays ;)

[s-hadinger]

Yes, that's why Berry is the way to abstract specific logic. But ESP8266 makes it impossible to abstract anything

[gemu2015]

this script sets display brightness and inversion with webui on esp8266

>D
p:bright=0
p:inv=0
res=0
i2c=0

>B
i2c=ia(0x3c)
if i2c==0 {
	print device not present
} else {
	res=0x8100|bright
	if inv==0 {
		iw(0 0xa6)
	} else {
		iw(0 0xa7)
	}
	iw2(0x4000 res)
}

>S
if i2c>0 {
	if chg[bright]>0 {
		res=0x8100|bright
		iw2(0x4000 res)
		print setting brightness to %bright%
	}
	if chg[inv]>0 {
		if inv==0 {
			iw(0 0xa6)
		} else {
			iw(0 0xa7)
		}
		print setting display invert
	}	
	
}


>W
sl(0 255 bright "0" "brightness" "255")
ck(inv "invert  ")

[pimlie]

@gemu2015 Awesome, that works for me. Thanks!

[Jason2866]

esp8266 is not the focus when developing new display features. Gemu showed a way to achieve with scripter.
All needed specific abstract drivers are usually developed with Berry. A esp32-c3 is already cheaper than an esp8266. Especially replacing the esp8266 on this board against an esp32-c3 seems a not complicated hardware mod.

[pimlie]

Yeah, but I already got a couple of Wemos D1's lying around :(