Skip to content

ESP32 Mongoose OS to Tasmota32 OTA updates for Shelly

License

Notifications You must be signed in to change notification settings

tasmota/mgos32-to-tasmota32

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

⚠️ Currently some devices do fail to convert. Do not use ⚠️

Shelly convert to Tasmota

This guide explains how to convert Shelly ESP32 and ESP32-C3 driven devices to Tasmota (no other firmware!)

⚠️ There is no way back to Shelly firmware if you have initiated the convert process!

The convert workflow provides a safe update. However, it is a risky operation to overwrite the bootloader. If something unexpected happens, it will probably render the device inoperable until it is recovered. To recover a failed convert, flashing Tasmota over a wired serial connection is needed.

Prerequisites

  1. ⚠️ Needed ⚠️ Update the device to Shelly firmware >= 1.4.x (Internet access!!)
  2. For devices where is still no firmware 1.4.x available (-> Mini1G3) use packages from release v13.4.1 to convert!
  3. Download the name corresponding zip package for your device (See release section)

Let’s start

Replace Shelly with Tasmota32 firmware

  1. Connect to your Shelly device via Wi-Fi or LAN
  2. Navigate to Settings > Firmware and drag & drop the convert "zip" in the firmware update area (do NOT update via URL)
  3. Click the Update button
  4. Device is updating, finished in 1-2 minutes
  5. If Shelly Web frontend is back after the update, repeat the steps above.
  6. The Web frontend does not react anymore now.
  7. Connect to the newly opened Tasmota Wi-Fi access point and add the device to your Wi-Fi (full Internet access needed).

⚠️ NEEDED ⚠️ Convert to Tasmota Safeboot and update to latest Tasmota release

  1. Configure the device using Tasmota Auto configuration. (Configuration > Auto-configuration > Select new auto-configuration) Select your device and hit enter. This replaces the locked bootloader (without this step device gets bricked with the next boot).
  2. Wait until the device is online again. Takes 1-2 minutes
  3. Under consoles, open the Partition Wizard and start the Safeboot Conversion by hitting the button "Start Migration". The conversion will update to the latest Tasmota version too.
  4. Wait until the device is online again. Takes 1-2 minutes
  5. Optional: Use Partition Wizard to increase the Filesystem size to its maximum. This removes all obsolete files too.

Supported Devices

Device State
PlusHT ⚠️untested
PlusPlugS tested
PlusPlugUK tested
PlusPlugIT ⚠️untested
PlusPlugUS tested
PlusI4 tested
PlusWallDimmer ⚠️ no Tasmota support
Plus1PM tested
Plus1 tested
Plus2PM tested
PlusRGBWPM tested
Pro1 tested
Pro1PM tested
Pro2 tested
Pro2PM tested
Pro3 ⚠️untested
Pro4PM tested
Pro3EM ⚠️untested
Plus1PMMini tested
Plus1Mini tested
PlusPMMini tested
Plus10V tested
PlusUni tested
Mini1PMG3 tested
Mini1G3 tested
MiniPMG3 tested
Pro4PM is build with LVGL support

If you confirmed an untested device working please open an issue!

What if my device is not listed?

If your Shelly device is not listed, please open an issue with a link to the Shelly Knowledge Base and post a screenshot of the main Web Shelly firmware page.

Credits

I would like to thank Jason2866 for providing help with the custom Tasmota files and s-hadinger for the Berry code fixing startup of Tasmota.

License

This repository is released under the GNU General Public License v3.0. Refer to the LICENSE file for more information.

Copyright (C) 2023 Philipp '3D' ten Brink