Tasmota getting started guide (2026): which build, which devices, flashing safely and first-time setup

Not actually a Hub, Tasmota is an open source firmware for ESP8266 based devices
Post Reply
User avatar
ZerOne
Site Admin
Posts: 216
Joined: Sun Dec 13, 2020 8:21 am

A starting point for anyone new to Tasmota, or coming back after a few years. Based on the Tasmota docs and GitHub release notes as at October 2026. The Tasmota Official Page thread is the link list; this one is the "where do I actually begin" walkthrough. I have not tested every device mentioned, so check the docs for your hardware.

What Tasmota is (and isn't)

Open-source firmware for Espressif ESP chips (ESP8266/ESP8285 and the ESP32 family). It replaces the maker's cloud firmware with a local web UI, MQTT control and support for lots of sensors. It is not a hub: each flashed device is its own web server and MQTT client, so you still want a broker (Mosquitto, or the one in Home Assistant).

Current release

The latest release on GitHub as I write is v16.0.0 "Theo" (16 October 2026). From the release notes:
  • Direct migration from versions before v8.1.0 (Doris) is no longer supported. The docs have a migration path through intermediate releases.
  • Do not upgrade from a minimal build to another minimal build. It will most likely fail eventually and need a serial reflash. OTA to a full build of the same release first.
  • Downgrading has never been officially supported because settings layouts change. Back up your configuration (web UI, Configuration, Backup Configuration) before any upgrade.
Which binary?
  • ESP8266/ESP8285: tasmota.bin is the recommended release binary (1M+ flash). Variants include lite, sensors, ir, knx, display and Zigbee bridge builds.
  • ESP32 family (ESP32, S2, S3, C2, C3, C5, C6, C61, P4 are listed in the release notes): tasmota32.bin is the recommended one, with separate builds for single-core ESP32 and other chip families.
  • ESP32 supports encrypted MQTT (TLS) natively. ESP8266 does not unless you compile a custom build. Keep unencrypted MQTT on your own LAN.
Will my device take Tasmota?
  • Check the Supported Devices Repository (templates.blakadder.com) before you buy. It lists tested devices and the template (GPIO map) for each.
  • Many cheap Wi-Fi plugs and bulbs run Tuya firmware, and whether you can flash them depends on the chip. ESP means Tasmota works. Many newer Tuya-based modules use other chips (for example Beken BK7231), which Tasmota does not run on. A separate project, OpenBeken, describes itself as a Tasmota/ESPHome replacement for those chips. Different firmware, different docs.
  • Over-the-air conversion tricks that worked on old Tuya firmware often fail on newer firmware. Assume you will have to open the case.
Flashing safely

The easy path is the Tasmota Web Installer (Chromium-based browser, USB serial, ESP8266 and ESP32). Other tools in the docs: Tasmotizer, ESP-Flasher, esptool.py.
  • Mains safety. The Tasmota docs say never flash a device while it is connected to mains, and never power one with the case open and the board exposed. Many plugs and switches have a non-isolated board. Flash on the bench, mains cable disconnected, powered only from the adapter's 3.3 V.
  • Check your adapter: the docs warn some adapters switch the data pins to 3.3 V but still put 5 V on the power pin, which destroys the ESP.
  • The ESP needs decent current to flash. Flaky "flash failed" errors are often a weak adapter. The docs recommend CH340G-based adapters or the VoltLink board.
  • Wiring is TX to RX, RX to TX, GND to GND, 3V3 to 3V3, with the chip put into programming mode first (GPIO0 to ground at power-up).
  • In Australia, fitting or modifying fixed wiring is licensed electrical work. Flashing a plug-in device is one thing; installing an in-wall switch or relay is a job for a licensed electrician.
First boot checklist
  • The device starts a Wi-Fi access point (WifiManager). Join it with a phone and enter your SSID and password. Use your IoT SSID or VLAN if you have one.
  • Pick the right template or module (Configuration, Configure Template/Module).
  • Set a web UI password straight away: WebPassword yourpasswordhere The user is admin, 32 character limit. A Tasmota device with no password is an open control panel for anything on your LAN.
  • Configure MQTT with a unique Topic per device and a descriptive Friendly Name (Home Assistant uses it for naming): Backlog MqttHost broker.local; MqttUser user; MqttPassword pass; Topic lounge_plug
  • Give the device a DHCP reservation.
  • Never port-forward a Tasmota web UI or MQTT port. For remote access use a VPN to your network.
Home Assistant

The Tasmota docs call the official Tasmota integration the preferred route: with MQTT working on both sides, devices are discovered automatically. Leave FullTopic at its default, and if you use the Mosquitto add-on with an ACL file, allow devices to write to the discovery topic (the docs spell out the line).

Links
Question for the group: what is your go-to Tasmota-friendly hardware in Australia right now (plugs, relays, dev boards), and where do you buy it? Has anyone found a reliable way to tell, before buying, whether a "smart plug" is ESP-based?
Post Reply

Return to “Tasmota Firmware Discussion”