Skip to content


ESP32 support is in beta and not all functions or supported peripherals will work reliably.

Due to the scope and activity of development there might be breaking changes and incompatibilities between major and minor versions of Tasmota32. In case of problems first erase flash and serial flash the latest development binary.


Use ESP_Flasher (Windows, MacOS, Linux) or Tasmota Web Installer (Chrome or Edge) to flash.


Requires 3.1 to identify new ESP chips.

With use the following command syntax (replace COM port number!): --chip esp32 --port COM5 --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dout --flash_freq 40m --flash_size detect 0x1000 bootloader_dout_40m.bin 0x8000 partitions.bin 0xe000 boot_app0.bin 0x10000 tasmota32.bin


To flash ESP32-C3 chip with use the following command syntax (replace COM port number!): --chip esp32c3 --port COM5 --baud 460800 --before default_reset --after hard_reset write_flash -z --flash_mode dout --flash_freq 40m --flash_size detect 0x0000 bootloader_dout_40m.bin 0x8000 partitions.bin 0xe000 boot_app0.bin 0x10000 tasmota32c3.bin

You can download precompiled binaries:

OTA upgrade from much older versions of tasmota32 might fail due to significant changes in partition tables.

Use a proper power supply!

ESP32 is power hungry and there's a high chance it will not be able to boot properly off the serial-to-USB power. Power it from a separate power supply that can provide at least 1A.

ESP32 Differences~

All ESP32 systems on a chip (SoC) are 32-bit MCUs with 2.4 GHz Wi-Fi & Bluetooth/Bluetooth LE built in. There are distinct product lines which are different from each other in varying degrees.


Tasmota32 is initially developed and tested with dual core version of ESP32

Module Core Core clock Flash (MB) PSRAM (MB) Touch Sensor Hall sensor
ESP32-D0WD-V3 Dual Core 240 MHz 4,8,16 N/A Yes Yes Bluetooth 4.2 LE
ESP32-D0WD-V3 Dual Core 240 MHz 4,8,16 8 Yes Yes Bluetooth 4.2 LE
ESP32-MINI-1 ESP32-U4WDH Single Core 160 MHz 4 N/A Yes Yes Bluetooth 4.2 LE
ESP32-SOLO-1 ESP32-S0WD Single Core 160 MHz 4 N/A Yes Yes Bluetooth 4.2 LE
ESP32-WROOM-32SE ESP32-D0WD Dual Core 240 MHz 4,8,16 N/A Yes Yes Bluetooth 4.2 LE

Single core SoCs do not work with standard binaries, for those use only tasmota32solo1.bin or compile your own binary using the tasmota32solo1 environment.

ESP32 line is later expanded with ESP32-PICO-V3, ESP32-PICO-V3-02 and ESP32-PICO-D4


A more cost-efficient version of ESP32, cut down to a single core and several dedicated hardware security features (eFuse, flash encryption, secure boot, signature verification, integrated AES, SHA and RSA algorithms). It has 43 available GPIOs. Product page for ESP32-S2

Experimental support in Tasmota


Keeping the security improvements the S3 line now again features the dual core SoC with Bluetooth upgraded to V5 . Product page for ESP32-S3.

Untested with Tasmota


Unlike previous versions, C3 is a single-core Wi-Fi and Bluetooth 5 (LE) microcontroller SoC based on the open-source RISC-V architecture. It will be available as ESP32-C3-MINI-1 and ESP32-C3-WROOM-02 modules. Product page for ESP32-C3

Stable with Tasmota but requires a specially compiled C3 only binary

Exclusive Features~

CPU Temperature Sensor~

Tasmota will create an internal temperature sensor and display the values in the webUI and MQTT.


Hall Sensor~

ESP32 has a built in hall effect sensor that detects changes in the magnetic field in its surroundings. It is located behind the metal lid of the module and connected to GPIO36 and GPIO39.

To enable set in module configuration or template:

  • GPIO36 as HallEffect 1
  • GPIO39 as HallEffect 2

Touch Pins~

ESP32 has 10 capacitive touch GPIOs. More on configuring and using them....

Berry Scripting~

ESP32 introduces Berry language as a more approachable scripting language. Berry is very powerful and you can even code an I2C driver using it.


Use LVGL in conjunction with Berry on devices with displays and touch displays to design your own UI.

Compiling ESP32 Binaries~

Uncomment the tasmota32 build you want to compile in platformio_override.ini. For example, uncommenting tasmota32 will build tasmota32.bin on the next Build task in Platformio.


All binaries will use flags in user_config_override.h if it exists.

Working Devices~

Tasmota Supported Devices Repository has an extensive list of ESP32 based devices.

LilyGO TTGO T-Camera OV2640_V05~

In platformio_override.ini uncomment the line with tasmota32 and set the correct COM port.

In user_config_override.h add:

#define USE_BMP
#define USE_I2C
#define USE_SPI
#define USE_DISPLAY_SSD1306
#define USE_WEBCAM

Upload via USB, then apply the following Template:


The PIR will turn ON/OFF the display and send over MQTT the POWER status. The display shows the sensor data. To make the device work nicely, change the following settings in the Console:

Camera settings to correct orientation (USB on the bottom):

WCMirror ON
WCResolution 6
WCSaturation 0
WCBrightness -1
WCContrast 1

Display Settings (USB on the bottom):

DisplayRotate 2
DisplayCols 21
DisplayRows 7
DisplayMode 2

BME280 Settings (it is not very trustable):

HumOffset 10
TempOffset -15

PIR/Button Settings:

SwitchMode1 1
SetOption73 1


is supported via module. Upload firmware via USB and select module Odroid Go

To make the device work nicely, change the following settings in the Console:

adcparam3 6,0,4095,0,6160

Display Settings:

DisplayRotate 3
DisplayCols 53
DisplayRows 30
DisplayMode 5

Rule for Joystick to dim the display:

on analog#joy2=1 do dimmer - endon on analog#joy2=2 do dimmer + endon


{"NAME":"AITHINKER CAM","GPIO":[4992,1,672,1,416,5088,1,1,1,6720,736,704,1,1,5089,5090,0,5091,5184,5152,0,5120,5024,5056,0,0,0,0,4928,576,5094,5095,5092,0,0,5093],"FLAG":0,"BASE":2}





Denky (Teleinfo)~

{"NAME":"Denky (Teleinfo)","GPIO":[1,1,1,1,5664,1,1,1,1,1,1,1,1,1,1,1,0,1,1,1,0,1376,1,1,0,0,0,0,1,5632,1,1,1,0,0,1],"FLAG":0,"BASE":1}

Olimex ESP32-PoE~

{"NAME":"Olimex ESP32-PoE","GPIO":[1,1,1,1,1,1,0,0,5536,1,1,1,1,0,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,1,1,1,1,1,0,0,1],"FLAG":0,"BASE":1}

M5Stack Atom~

{"NAME":"M5Stack Atom","GPIO":[1,1,1,1,1,1,1,1,1056,1,1,1,1,1,1,1,0,609,1,1,0,641,640,1376,0,0,0,0,608,1,1,1,1,0,0,32],"FLAG":0,"BASE":1}

M5Stack Atom lite~

{"NAME":"M5Stack Atom Lite","GPIO":[1,1,1,1,1,1,1,1,1056,1,1,1,1,1,1,1,0,1,1,1,0,1,640,1376,0,0,0,0,608,1,1,1,1,0,0,32],"FLAG":0,"BASE":1}

LilyGO ttgo-t-eth-poe~

{"NAME":"LilyGO ttgo-t-eth-poe","GPIO":[0,1,1,1,1,1,1,1,1,1,1,1,1,1,5600,1,0,1,1,5568,0,1,1,1,0,0,0,0,1,1,1,1,1,0,0,1],"FLAG":0,"BASE":1}

For working Ethernet, change the following setting in the Console:

EthClockMode 1

these 3 devices are also fully supported, more detailed info will be added later

LilyGo T-OI-PLUS (esp32c3)~

This device is borked, the vReg can't stand normal Wifi or BLE operations. However it is barely usable with the following:

  • Flash with Esp32c3. WifiManager will start but you will not see the Tasmota AP (wifi broken at this point)
  • Reduce the Wifi power to 2dBm (that's very low) with WifiPower 2
  • Connect via the USB-Serial, enter manually the wifi credentials: backlog ssid1 <ssid>; password1 <password>
  • It will reboot and hopefully connect to wifi
{"NAME":"LilyGo T-OI-PLUS","GPIO":[1,1,1,544,1,1,1,1,1,1,1,0,0,0,0,0,0,0,1,1,1,1],"FLAG":0,"BASE":1}

TTGO ESP32 watch~

fully supported with all sensors


fully supported

m5stack CORE2~

is fully supported with all sensors and SD card. Upload firmware via USB and select module core2

all pin definitions hardcoded except GPIO 33,34 for extern SCL,SDA on grove bus
console cmd:

core2shutdown seconds - shut down hardware and wake up after N seconds (>=30)
core2shutdown HH:MM - shut down hardware and wake up on HH:MM time

Heltec WiFi Kit 32~

OLED display needs the following template

{"NAME":"WiFi Kit 32","GPIO":[1,1,1,1,640,1,1,1,1,1,1,608,3840,1,1,1,0,1,1,1,0,224,1,1,0,0,0,0,1,1,1,1,1,0,0,1],"FLAG":0,"BASE":1}


verified support for board plus I2C sensors

to use I2C, set IO21 to SDA and IO22 to SCL

Displays, sensors and other options~

displays: (most probably all I2C displays will work)


sensors: (most probably all I2C sensors will work)



USE_SCRIPT (scripting and all its options)  

Back to top