search

tasmota / mgos32-to-tasmota32

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

Shelly Plus Plug S (EU) bricked using the method in the Readme #75

Open zeus86 opened 1 month ago

zeus86 commented 1 month ago

Following the README unfortunately bricked 2 of my shellys.

Steps to reproduce:

can anyone tell me, what i've been missing? i can only assume, that the fact, that i flashed the OG-firmware twice with different versions, that it has different firmwares in both slots before atempting to flash tasmota, which may the problem here.

I flashed a second shelly, because on the first one i had forgotten to do the "autoconfigure" step. "My bad" I thought, and was willing to do it again, but the outcome was exactly the same on the second device. the readme explicitly states first upgrade to 1.4.x, so pleace clarify someone here.

However, it would be really nice, if the Readme would be more specific in this regard, because if serial flashing is the only way to recover from this (and i would like to know if this is the case), this is basically useless because you cannot open these devices without destroying them, which makes them unusable from then on for most people (me included). :disappointed:

PsychoRS commented 2 weeks ago

Exact same issue and same result here, in my case with a Plus 2PM.

bigbutler commented 2 weeks ago

Same on Shelly 4pm

PsychoRS commented 2 weeks ago

Maybe an issue with latest Shelly FW (1.4.2)?

lukesav1 commented 1 week ago

Same on Shelly Plus 1PM (Started with Shelly FW 1.4.2).

zeus86 commented 1 week ago

it would be really nice, if someone from the team could have a look onto this. i don't even know how this behaviour is possible in the first place, now that we have safeboot instead of two mirrored partitions.

With models like 1pm or 4pm or dimmer or something, you at least have the possible route of manually flashing the ESP via it's debug header, but on the plug-s-plus: no way without destroying it physically...

At least a warning in the README would be suitable.

lukesav1 commented 1 week ago

it would be really nice, if someone from the team could have a look onto this. i don't even know how this behaviour is possible in the first place, now that we have safeboot instead of two mirrored partitions.

With models like 1pm or 4pm or dimmer or something, you at least have the possible route of manually flashing the ESP via it's debug header, but on the plug-s-plus: no way without destroying it physically...

At least a warning in the README would be suitable.

I also tried flashing via the serial header after the error but with no luck, it failed with no comms, in my opinion it was properly bricked. I binned it in the end.

From now on im flashing via serial from the start

fawick commented 1 week ago

Last night I ran into the same problem:

After reboot, the Shelly AP appeared again, and now most HTTP requests result in Not found.

However, I made a couple of additional observations that are not yet listed here:

1) In the wifi network provided by Shelly AP, the endpoint http://192.168.33.1/ota is still special. Without any parameters it will complain that it is missing an URL. With one provided (e.g. http://192.168.33.1/ota?url=https://github.com/tasmota/mgos32-to-tasmota32/releases/download/v14.0.0/mgos32-to-tasmota32-PlusPlugS.zip), the plug reponds with something like Installing firmware from https://github.com/tasmota/mgos32-to-tasmota32/releases/download/v14.0.0/mgos32-to-tasmota32-PlusPlugS.zip. However, nothing really happens. 2) The plug is still be found via bluetooth by the Shelly Smart Control App and I can get to the point in which I am asked to provide SSID and wifi passwort. But the actual integration of the device into my wifi is not successful. 3) The endpoint http://192.168.33.1/shelly is also still working

I wonder whether there are other endpoints to try.

fawick commented 1 week ago

Good news: I was unable to unbrick my Plus Plug S (v2).

Here's how:

Hope that helps all of you a bit.

Glotzon commented 1 day ago

Same issue with one out of four Shelly PlusPlugS. Successfully recovered using this method: https://github.com/tasmota/mgos32-to-tasmota32/issues/75#issuecomment-2379974905

Now I need to decide if I'll give it another try, but thank you @fawick for the awesome work to figure out how recovery works.

UPDATE: I gave it another try, but with same result. Device bricks, recovered with the method above. Feels like this might be dependent on the actual device.