I’m trying to create a sauna control panel using an ESP32 display and LVGL. I’ve connected a dallas DS18B20 temperature sensor and have run into the problem that the display image twitches every time the sensor updates.
I have tried with JC8048W550 and 8048s070 display, different GPIOs and also separate power supplies for the display and temperature sensor and always with the same result.
If that module has pullup to Vcc (5V), you are feeding 5V to your gpio pin.
Try powering DS-module at 3.3V, it has a voltage range from 3V to 5.5V so it should work.
The problem persists when powering the module by 3.3V.
I actually started by powering the module by 3.3V at first, but then while searching for the cause of the problem I tried various things and then connected the module incorrectly to 5V.
Anyway, it’s good to know that the gpio pins only support 3.3 volts.
My guess is that the one wire component, which uses timing critical looping functions in IRAM, is hogging bus bandwidth so the RGB driver DMA is starved of data. That would cause the symptoms you describe.
i have too the Guition JC8048W550.
I tryed with your .yaml - code but with no success, the display remains black. But Esphome works on the esp32, because i recive log-infos from the device…
Because i don’t know nothing about “default_16M.csv” i searched it in internet and found one, but i am not sure if it is the same like yours and if it is relevant to my problem.
Or maybe your .yaml-code you pasted here is not complete?
Strange is too, that the "touchscreen: - part isn’t acepted from the “esphome builder” so i commented it out.
Can you send me please your .yaml-code so i can test if i can get working the display with esphome?
The preinstalled example from Guition worked fine, so the display itself should be ok…
Hi Martin, did you ever solve this Dallas twitching problem?
I have the same issue with twitching / flickering screen LVGL graphics during temp update. I have tried on two different Waveshare ESP32 7” and 4.3” touch-screens. I have also tried different GPIO’s and reduced all code to bare minimum with no luck. It seems to be related to the DS18B20 and/or one_wire component in ESPhome. It has been like this for 5-6 months or longer across different ESPhome and LVGL updates.