We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I managed to flash Tasmota on this Lilygo device, here are the steps.
go to : https://tasmota.github.io/install/
In the drop-down, choose : Tasmota32-S3 (QIO Flash/OPI PSRAM)
Connect to the USB port of your USB to TTL
Flash (erase if needed)
Then you need to compile with using those instructions : Compiling Tasmota for ESP32 using Gitpod arendst/Tasmota#18745
Add those line to user_config_override.h #define USE_SHIFT595 #define USE_RTC_CHIPS #define USE_DS3231 #define USE_RTC_ADDR 0x51
Upload the new firmware with the Tasmota web interface
With the updated Firmware, you need to add a new template and apply it Go copy it from https://templates.blakadder.com/lilygo_T-Relay-S3.html
You should now have a fully functional T-RelayS3 with Tasmota
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I managed to flash Tasmota on this Lilygo device, here are the steps.
go to : https://tasmota.github.io/install/
In the drop-down, choose : Tasmota32-S3 (QIO Flash/OPI PSRAM)
Connect to the USB port of your USB to TTL
Flash (erase if needed)
Then you need to compile with using those instructions : Compiling Tasmota for ESP32 using Gitpod arendst/Tasmota#18745
Add those line to user_config_override.h
#define USE_SHIFT595
#define USE_RTC_CHIPS
#define USE_DS3231
#define USE_RTC_ADDR 0x51
Upload the new firmware with the Tasmota web interface
With the updated Firmware, you need to add a new template and apply it
Go copy it from https://templates.blakadder.com/lilygo_T-Relay-S3.html
You should now have a fully functional T-RelayS3 with Tasmota
The text was updated successfully, but these errors were encountered: