tasmota / mgos32-to-tasmota32

ESP32 Mongoose OS to Tasmota32 OTA updates for Shelly
GNU General Public License v3.0
150 stars 10 forks source link

Update-process for Shelly Pro 2PM unclear #39

Closed ChristianWaechter closed 4 months ago

ChristianWaechter commented 8 months ago

Hello,

I'm trying to flash my Shelly Pro 2PM with Tasmota. After searching for it, I found this page: https://templates.blakadder.com/shelly_pro_2pm.html

This lead me to this mgos32-to-tasmota32 repository. In the step by step help it is first recommended to update to the latest firmware. I assume that a update to the latest Shelly fimware is meant.

Prerequisites

  1. ⚠️ Needed ⚠️ Update the device to the latest stable firmware (Internet access!!)

In my case, Shelly firmware 0.14.1 is currently installed and 1.1.0 (Stable) would be available. But I somehow do not want to update, as the Tasmota page notes

WARNING!!! Devices with firmaware v1.10+ cannot be flashed OTA anymore

So what is the correct procedure? I do not want to lock the Shelly just because I updated to version 1.1.0.

Thanks in advance :)

Jason2866 commented 8 months ago

The text you copied is outdated. See actual README

ChristianWaechter commented 8 months ago

The text you copied is outdated.

You mean the text on the Tasmota website?

See actual README

I found in an older commit from 21.23.2023 of this repository that a fix for the Shelly firmware 1.1.0 has been included. So that means that I safely can update my Shelly firmware and than switch to Tasmota :)

ChristianWaechter commented 8 months ago

I was a bit overhasty and answered before actually trying it. Long story short, I cannot flash the Tasmota firmware.

What I did step by step: 1) Powered up the Shelly, only the power is connected to the L and N connector 2) Connected to its Wifi access point and configured it so it can establish a connection to my actual Wifi (Router is directly next to the Shelly). Reconnected with my actual Wifi and again accessed the web interface of the Shelly 3) I did the update of the Shelly firmware from 0.14.1 to 1.1.0 (Stable) via the web interface. After it was done, the Shelly rebooted and I saw clear differences in the web interface. Also the firmware reports with Firmware ID 20231219-133937/1.1.0-g34b5d4f and Webbuild ID 231218152112-8372d8c8-HEAD 4) I downloaded the file "mgos32-to-tasmota32-Pro2PM.zip" from Release v13.3.1 and dragged it into the "Firmware file image"-field in the Shelly webinterface. I also tried to browse and choose the file that way. It shows in the web interface: mgos32-to-tasmota32-Pro2PM.zip: 2127374 bytes 5) I Press the "Update from file"-button. In the very top of the webinterface System update in progress... [View settings] appears. After ~ 5 seconds it disappiers again by its own. Nothing other is shown. The page stays like this for ever. 6) Clicking the "Update from file"-button again shows the exact same behaviour as in 5) 7) I after that I did a complete power cycle of the shelly and tried steps 4 - 6 again with no change.

Am I missing something?

Jason2866 commented 8 months ago

Please post a screenshot from the whole Shelly update web page.

ChristianWaechter commented 8 months ago

grafik

Jason2866 commented 8 months ago

Thx. Looks like, Shelly changed "something", which is different to the changes done to the mini g3 devices. The Tasmota convert firmware is working with Shelly 1.1.0 gen3 devices. The good news, nothing has been altered on your Shelly device.

ChristianWaechter commented 8 months ago

So it is not possible to flash Tasmota onto this device? Where can you see whether or not it's a Shelly 1.1.0 gen3 device?

Jason2866 commented 8 months ago

It is not a gen3 device. In the upper left side there is the exact device name. Converting will be probably possible, i have to look where it fails. Will need some time because i have not much spare time currently.

Jason2866 commented 5 months ago

Bug identified. Working on the fix.

Jason2866 commented 5 months ago

Should be fixed with latest release 13.4.1

Jason2866 commented 4 months ago

Closing since no feedback