Shelly Plus 1 does not connect to WiFi after the partition manager / migration start

[ok11]

Hey all,

observing the following:

• after unlocking the bootloader (the restart and wifi connect was successful) and starting the migration from the partition manager, the device does not seem to connect to the wifi
• the tasmota ap is running, but 192.168.4.1 does not bring up the web ui
• http commands are accepted, but do not work properly
  • for example, http://192.168.4.1/wi?s1=ssid&p1=pwd&save= returns

File Not Found

URI: /wi
Method: GET
Arguments: 3
 s1: ssid
 p1: pwd
 save: 

So, the device is not bricked, but also does not run as expected. What should I do now?

T&R, Oleg

[Jason2866]

You can try to restart your DHCP server (most cases is this the Router) if this does not help recover device by serial flashing Tasmota.

[ok11]

ok. I have a couple of other Plus 1s to brick (struck through) flash, shall I consider something specific? like shelly firmware downgrade to a specific version? Or like not going for ota reflash at all? Maybe asking differently: what exactly could have gone wrong?

[Jason2866]

Bad Internet connection. In general the convert process does work well.

[ok11]

Bad Internet connection. In general the convert process does work well.

Ah ok. Just to rephrase what you said to make sure I get it right: the latest tasmota release was not able to be downloaded, so the migration has stuck?

[Jason2866]

I don't say this was the case, it could be. A short power Interrupt will do harm too.

[ok11]

Sorry to say that, but the same just happened to the second device. Wifi has been stable, no power interrupts. Have been waiting for like 10 minutes, now the tasmota AP has become active as in the first case. I can wait longer, but somehow I have a feeling that it won't work. Surely, I can do serial flashing, but it is like an indication that either I do something consistently wrong, or the migration process does not work as expected. The device is pretty warm.

[Jason2866]

Can't say what is going wrong here. My test Shelly device converts without an issue.

Mhh, you should have no need to connect to Tasmota AP a second time. After the first boot you provide your wifi credentials and Tasmota will connect always to your WiFi for the next steps.
Without this the next steps can not work and the bootloader will not be replaced.
This ends in bricked device.

[ok11]

Mhh, you should have no need to connect to Tasmota AP a second time. After the first boot you provide your wifi credentials and Tasmota will connect always to your WiFi for the next steps. Without this the next steps can not work and the bootloader will not be replaced. This ends in bricked device.

You are right of course. After the first restart I entered the wifi credentials and it joined the wifi network, After that I autoconfigured it, which also worked well, it restarted and came up in the wifi. Only after the next step (partition manager -> start migration) it ended up in limbo. After a couple of minutes of doing something, it starts up the tasmota ap and does not connect to the wifi anymore

[ok11]

Oh. From AP I'm able to come to the safeboot. It seems the same issue as in arendst/Tasmota#19414

[Jason2866]

Provide the Tasmota firmware via local firmware upload (by file) when in safeboot mode.

[ok11]

Provide the Tasmota firmware via local firmware upload (by file) when in safeboot mode.

Not sure how, it offers only "Console", no "Firmware Upgrade"

[Jason2866]

You should see with http://192.168.4.1/up?

[Caleb79]

I've a similar issue with this device and Tasmota.

Flashing was running smooth but as soon as I use auto-config or upload the template it takes about one minute and the device is going to standard settings incl. starting the AP mode again.

I tried to upload the latest tasmota firmware again (file-upload) but the device told me: wrong signature

Is there anything I can do?

[Jason2866]

I tried to upload the latest tasmota firmware again (file-upload) but the device told me: wrong signature

Tasmota does not have a signature check

[Caleb79]

This what I get, trying to update.

[Caleb79]

I could check the console before it falls back to defaults.

[Jason2866]

The file you try to use is corrupt.

[Caleb79]

I used the latest release from this repository here and downloaded it a couple of times.
Even the OTA worked once but also no change on that.

[Jason2866]

If Tasmota is running, you can't and need to load anything from here.
For updates Tasmota needs to be used.

[Caleb79]

Okay, That explains my first update issue.
But nevertheless, even with a download from Tasmota (which worked very well - thanks for that), after changing the configuration, the device falls back to factory settings - again and again.

To be honest, I was thinking, that I might be using the wrong device ;) but no, it's the 1-plus.

A bit frustrating.

[ChristianWittke]

I can confirm the same situation for Shelly Plus 1.
Did all the steps and now my shelly not usuable anymore.
First I updated it to the latest shelly version.
Then I put the latest tasmota zip to go for tasmota.
Tasmota Wifi was started and I added my wifi to it, I went for the mentioned steps, i.e. auto configuration and afterwards I started the Partition Wizard and to do Safeboot Conversion. After magic happens as written in the UI the shelly is starting now, but not connecting to my Wifi, but opening a Wifi which I can connect to, but the UI is not loading.