yaourdt / tasmota-to-mgos Goto Github PK

After Flashing the 0x1000 to my Shelly 2.5, the Shelly wifi comes and goes as mg-XXXX but i cant connect to that network. Also the relays are clicking always. Is it broken?

Hi,

how can i download the shelly stock firmware??

Tried to open http://firmware.shelly.cloud/gen1/SHSW-PM.zip in chrome.
Just opens an xml file - tried to download this, but get an error.

Looks like im too stupid..
How can i get the zip file?

thx

Anyone else unable to dowload the this?

https://dl.dasker.eu/firmware/mgos512k-0x7000.bin

Hello I have the following issue:

• device: shelly2.5
• installed firmware: tasmota 11.1.0

When trying to upload this minimal firmware i get the error:

Upload Failed

Not enough space

Any Idea how to fix that?

Sorry new to this stuff but I am getting the following error when I try to run the curl file. I am trying to Flash the Shelly 1L back to the stock firmware. If anyone can help out that would be great. I am using the following lines below, with the error and this is after connecting to the device wifi.

curl -i -F [email protected] http://10.42.42.44/update

curl: (26) Failed to open/read local data from file/application

I have a Shelly Plug S I'm trying to revert from Tasmota to Shellys firmware. I followed the guide and first used the 0x7000 and then rebooted, I connect to the mg-xxxxx wifi, when I try to upload the firmware from Shelly, SHPLG-S.zip. I get an error message.

curl -i -F filedata=@/Users/dariber/Downloads/SHPLG-S.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

Can anyone one help me with what I'm doing wrong?

Thanx

I'm back! After failing with a Shelly1 and then being able to flash other Shellys, I got stuck while flashing a shelly rgbw2

The operations carried out are:

1. flashed the minimal firmware tasmota ota mode http://ota.tasmota.com/tasmota/release/tasmota-minimal.bin
   Completed successfully

2. flashed 0x7000 firmware https://github.com/yaourdt/tasmota-to-mgos/raw/main/binaries/mgos512k-0x7.bin
   Completed successfully

3. connected to the mg wifi network - ????? and once connected:ù in prompt i type:

C:>curl -i -F filedata=@c:\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

curl: (56) Recv failure: Connection was aborted

I am stuck here ... rgb2w.zip file is correct i am sure
If you have any suggestions for me, thank you

The Shelly 3EM / Shelly Pro 3EM is not in the list of devices yet.

What would be the correct address, 0x1000 or 0x7000?

Since this morning the server http://10.42.42.44 is not available and I can not execute the last step in flashing back from Tasmota to Shelly stock firmware.
(curl -i -F filedata=@./fw.zip http://10.42.42.44/update)

Any idea how to solve this problem?
Thank you

Hi,

thanks for providing this OTA helper. Switching to tasmota worked like a charm.
I'm trying to revert back to stock firmware of a Shelly Dimmer 1.

The intermediate firmware was flashed successfully and I can access it via http which returns:

Index of

Name | Modified | Size
hwinfo_struct.json | 01-Jan-1970 00:00 | 112
conf0.json | 01-Jan-1970 00:00 | 3
 
Mongoose/6.18

But curl responds with

curl -i -F filedata=@./SHDM-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

I'm using this firmware http://shelly-api-eu.shelly.cloud/firmware/SHDM-1.zip.

Did I miss something?

Best regards
Andreas

I already flash from tasmota to shelly oficial 1.5.6 version, but upgrading it in app or web goes to 1.9.7 and cant upgrade to newest firmware.
Can you help?

Just wanted to let you know that it is not possible to update stock Shelly firmware beyond 1.9.6 after using tasmota-to-mgos. It's stuck on an "Index of" page.

Tried that with 4 different Shelly Dimmer 2 devices. Flashing a full binary backup from before installing Tasmota the first time, fixes it on all these devices.

Something is different between Stock Shelly Firmware and "Returned-To-Stock" Fimware using tasmota-to-mgos.

BTW: I tried replacing hwinfo_struct.json with the correct one for my Shelly Dimmer 2, but still unable to update to 1.10.

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:

mgos_wifi.c:345         WiFi STA: Connect timeout
mgos_wifi.c:88          WiFi STA: Using config 0 (vtrust-flash)
esp_wifi.c:203          WiFi STA IP: 10.42.42.44/255.255.255.0 gw 10.42.42.1
mgos_wifi.c:270         WiFi STA: Connecting to vtrust-flash
mgos_net.c:86           WiFi STA: connecting
esp_main.c:145          SDK: scandone
mgos_wifi.c:118         WiFi STA: Disconnected, reason: 201
mgos_net.c:82           WiFi STA: disconnected
mgos_http_server.c:180  0x3fff0634 HTTP connection from 10.42.42.50:49252
mgos_mongoose.c:66      New heap free LWM: 43504
mgos_ota_core.c:252     Starting, timeout 600, commit timeout 0, mem 43852
mgos_mongoose.c:66      New heap free LWM: 42288
mgos_mongoose.c:66      New heap free LWM: 41344
mgos_mongoose.c:66      New heap free LWM: 40616
mgos_mongoose.c:66      New heap free LWM: 39784
mgos_ota_core.c:486     FW: switch esp8266 1.0 20210429-100513/v1.10.4-g3f94cd7
esp_ota_backend.c:185   Slot 1, FW: switch.bin -> 0x108000, FS fs.bin -> 0x1bb000
mgos_ota_core.c:504     0.20% total, esp_init_data_default_v08.bin 128 of 128
esp_ota_backend.c:205   Failed to read 64 bytes from 0x1bb000
esp_ota_backend.c:338   Start writing fs.bin (262144) @ 0x1bb000
mgos_mongoose.c:66      New heap free LWM: 38624
esp_flash_writer.c:77   Erase sector 443 (0x1bb000) -> 1
mgos_ota_core.c:811     Update finished, result -12 (Write failed)

Any idea what is wrong?

Hi,

just FYI: I accidentally "bricked" my Shelly 1 by using the 0x7000 instead of the 0x1000. It took me a while, but I was able to recover with OTA only, by moving to the Shelly Plug S Homekit -> Shelly Plug S stock -> Tasmota -> Tasmota minimal -> 0x1000 -> Shelly 1 Homekit -> revert to Shelly 1 stock firmware. Maybe it helps somebody.

Cheers!

Hi!

after flashing tasmota I encountered that the dimming did not work correctly so I wanted to move back to mgos.

From tasmota I went to tasmota minimal, than updated to your intermediate firmware and than used SHDM-2.zip for the shelly dimmer 2. After doing this the hotspot goes online but the webinterface doesn't work.

The only thing it shows is :

when clicking the HTML file I get:

Hi,

managed to OTA mgos512k-0x1000.bin onto a Shelly 1, but when I connect my Mac Mini via WLAN to the newly created mgos AP, curl times out.
Maybe it is an issue with my network settings? What WIFI settings should I configure? I tried it with a manual IP (10.42.42.51 and subnet of 255.255.255.0), but I still could not reach 10.42.42.44

curl: (7) Failed to connect to 10.42.42.44 port 80 after 1 ms: Couldn't connect to server Mac-mini:Downloads Berny$ curl -i -F filedata=@./SHSW-1.zip http://10.42.42.44/update

Hi, could you add the information for the 1L?
If I see it right it should be 0x1000, correct?

For Shelly 1, shelly 1L, Shelly 1PM, Shelly 2, Shelly 2.5, and Shelly EM use 0x1000

Sebastian

Im getting failed with error curl:26 read function returned a funny value

WHen trying to flash I get this error ,so maybe the path i wrong ? I even tried to put the file my local webserver but still no go .
I tried all combinations of C:\temp including double quotes as path.
How do you actually specify the path ?

C:\temp>curl -i -F filedata=@c://temp/shem.zip http://192.168.20.173/update
HTTP/1.1 404 Not Found
Content-Type: text/plain
Server: Tasmota/11.0.0 (ESP8266EX)
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: -1
Accept-Ranges: none
Transfer-Encoding: chunked
Connection: close

File Not Found

URI: /update
Method: POST
Arguments: 0

If I eliminate the F I get
C:\temp>curl -i filedata=@c://temp/shem.zip http://192.168.20.173/update
curl: (3) URL using bad/illegal format or missing URL

C:\temp>curl -i filedata=@c:/temp/shem.zip http://192.168.20.173/update
curl: (3) URL using bad/illegal format or missing URL

C:\temp>curl -i filedata=@http://192.168.20.55/shem.zip/shem.zip http://192.168.20.173/update
curl: (3) URL using bad/illegal format or missing URL

Hi @ all when I want to upgrade my reverted Shelly Device following Message is coming aftter i put in my command to the original FW.ZIP from Shelly:

MACUSER$ curl -i -F filedata=@./Users/macuser/Downloads/fw.zip http://10.42.42.50:80/update/

curl: (7) Failed to connect to 10.42.42.50 port 80 after 8 ms: Connection refused

So I can see the Shelly with the IP: 10.42.42.50 and can connect to its wifi - but not possible to flash the fw.zip via OTA - what I am doing wrong?

Thanks

I need help becouse I flash the tasmota minimal in my Shelly1
after i flash 0x1000 and after i try to flash Shelly firmware with:
curl -i -F [email protected] http://10.42.42.44/update
i receive the message "1 update applied, rebooting" but in the end even after rebooting the same wifi network mg-xxxxx reappears and not a new Shelly ...

Now I don't understand the reason for this problem, but I have a possible hypotheses:
I may have been wrong to flash the 0x7000 file instead of the 0x1000 (I doubt but I consider it as a hypothesis) I read: "Be careful to pick the appropriate version, or the device will be bricked during the first boot of the target firmware!" So if I can access the wifi network and it also starts up, I don't think I broke it so I feel like excluding the wrong firmware right? There is way to check which of the two firmware I have installed

Do you have any advice for me? From here can I try to flash some tasmota in case to bring it back active?