tasmota / mgos32-to-tasmota32

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

Convert to Tasmota failed from 1.4.4 - Shelly Pro 4 PM #85

Open cDev1987 opened 1 month ago

cDev1987 commented 1 month ago

Hi, today i received my Shelly Pro 4 PM and i tried to flash Tasmota fw to the Shelly, but after update it came back to my Wifi Network and i still see the Shelly GUI. I read the thread where many users reported to have a bricked device after update from 1.4.2
From 1.4.4 it seems that the update is not possible, but device is not bricked.

20241011-114451/1.4.4-g6d2a586 tried mgos32-to-tasmota32-Pro4PM from latest release 3 weeks ago

cDev1987 commented 3 weeks ago

I saw there is pro 4pm v1 and v2 - is there a difference wrt flashing Tasmota?

Device name: Shelly Pro 4PM V2 Device model: SPSW-104PE16EU

Device name: Shelly Pro 4PM Device model: SPSW-004PE16EU

cDev1987 commented 1 week ago

Tried again to ru the update with latest Version- installation still not possible.

"ts": 1731364285.124,
"level": 2,
"data": "shelly_ota.cpp:182      OTA status success, 100 %",
"fd": 1

}, { "ts": 1731364285.126, "level": 1, "data": "shelly_update.cpp:421 FW signatures: want 07 got 00", "fd": 1 diagnostics-shelly-pro4pm-debug-log (5).txt

Jason2866 commented 1 week ago

"data": "shelly_update.cpp:421 FW signatures: want 07 got 00", The log shows everything okay. We don't have signed firmware. The message is always there when using the convert script The log after this message is the interesting part

cDev1987 commented 1 week ago

Hi @Jason2866 thanks for your feedback. Anything else i could check or i can try? Or is there a way to get more debug data from Shelly device?

Jason2866 commented 1 week ago

Without the device idk how to find the reason for.