Open brainrecursion opened 3 years ago
I am also having this error. I was able to get further along by adding -H "Content-Type:application/zip"
% curl -i -H "Content-Type:application/zip" -F filedata=@/<path to file>/RGBW2.zip http://10.42.42.44/update
This seems to work to start the file upload, but after a short pause I get the following error...
curl: (56) Recv failure: Connection reset by peer
I'm using 0x7000 firmware in an attempt to restore an RGBW2 back to stock. Feedback is appreciated @yaourdt
@yaourdt Disregard. I found the solution to my problem at this thread... https://github.com/yaourdt/tasmota-to-mgos/issues/3#issuecomment-996660451
@brainrecursion Ultimately I needed to re-flash the 0x7000 firmware (0x1000 in your case) using a USB-to-Serial adapter and Tasmotizer software instead of the OTA method. (The wired flashing method vs wireless.) Something about OTA seems to break Mongooses curl abilities. I hope this steers you in the right path!
Hi,
i have the same issue. I have flashed a Shelly Duo RGBW and loaded the intermediate firmware. However flashing the end firmware give the write failed error. Not sure how to continue. Don't know how to get back or get to the original shelly firmware.
curl -i -F filedata=@./SHCB-1.zip http://10.42.42.44/update/ HTTP/1.1 500 Internal Server Error Server: Mongoose/6.18 Content-Type: text/plain Connection: close
-12 Write failed
@yaourdt do you what what has happened?
Hey. Has anyone ever figure this out? I am still getting just:
[I] ❰dan❙~/Downloads❱✘≻ curl -i -F filedata=@./SHRGBW2.zip http://10.42.42.44/update
HTTP/1.1 500 Internal Server Error
Server: Mongoose/6.18
Content-Type: text/plain
Connection: close
-12 Write failed
[I] ❰dan❙~/Downloads❱✔≻ curl -i -H "Content-Type:application/zip" -F filedata=@./SHRGBW2.zip http://10.42.42.44/update
curl: (56) Recv failure: Connection reset by peer
I have been having problems converting two shelly2 devices from tasmota v9.4.0 to stock Shelly firmware. I successfully converted a few shelly1 devices but the shelly2 devices are not happy.
I have tried multiple power cycles and flashed back to tasmota via serial and gone round the loop a few times but no luck.
This is using the latest release of 0x1000 firmware. I tried to get a boot log but it doesn't seem to output until initially. The log I have managed to capture is:
Any idea what is wrong?