I've got a LilyGo T8 V1.1 board with a ESP32-S2 chip and a ST7789 display onboard. In the properties for the ST7789 display I can not disable the DC pin st7789-1.jpg The board doesn't seem to have a DC pin attached to the display. The display isn't working maybe because of this non existing pin? htt...

There is a device for the LilyGo Display in the ESP32 range, but not for the S2 version...

This is the pinout..
https://forum.arduino.cc/t/display-reco ... t8/1167185

Could you please add it?

ayhan1 wrote: ↑

Wed Apr 17, 2024 7:25 pm

Thank you for your answer. You have information about the e32 modules you mentioned.

Here you can read about my project with the "E32-868T20D SX1276 868MHz 100mW DIP Wireless Module"
https://www.matrixtsl.com/mmforums/view ... 20D#p95960

I have a few projects that use 'long-range-ish' datatransfer. Not like a few Km's, but for my purpose enough range and reliable. One I use is E32-868T20D (read about it on the V9 forum), the other one is a HC12 module. Both are sufficient for my purposes. Just to send data from one node to each othe...

Thanks for sharing!

Sometimes 3600, sometimes 7200.
This is because of DST

Is this right?

I recently went back to V4.3xx because of issues with V5.x. The reason that most of my projects didn't compile "a-okay", was because of the Bluetooth that wasn't initialised. With that knowledge, my projects compile ok at the moment. I am hesitant to reinstall version 5 because of all the significan...

Is it a bug or a feature? :) When using the RTC from the ESP32 component: shouldn't this update the date accordingly to the chosen offset in the UTC setting? Now the time is updated to the offset in the component properties (or like in my case: the RTC_ESP32_NTP: SetUTCOffset component macro), but t...

Thanks BenR,

Some things didn't work until I found out why.
It was because the macro returns a byte.

Maybe this could solve issues other users have..