yaourdt / mgos-to-tasmota

A minimal firmware for OTA (over the air) flashing Tasmota, HAA, or ESPurna from Mongoose OS or compatible firmware types.
GNU General Public License v3.0
418 stars 67 forks source link

Problem with conversion to haa #73

Open TriderG75 opened 2 years ago

TriderG75 commented 2 years ago

Hi, using this command http://shellyip/ota?url=http://dl.dasker.eu/firmware/mg2haa-Shelly1.zip, instead appearing the hotspot haa-xxxxxx it opens a mongoose page and the shelly 1 stops to work. Using the mg2tasmota command, all is ok. I add the photo of the mongoose page I'm talking about. Is there a way to recover the shelly 1? Thanks

image

getinmybelly commented 2 years ago

Same problem here, though with the Dimmer 2 update.

3DCB8E5A-C04A-4A52-B101-112547237258

jamr200 commented 2 years ago

I have the same problem with shelly1 and shelly 2.5

Tibi-rvb commented 2 years ago

Same for me with a RGBW2

pierrekin commented 2 years ago

This happened to me with Shelly 2.5 :(

marcoscv-work commented 2 years ago

Same thing here with a Shelly 2.5! do you have any news about this?

RavenSystem commented 2 years ago

@yaourdt GitHub did some changes in their SSL certificates and your firmware are not able to download files from its servers. Probably, a new build, compiled with latest SDK, is needed.

michapi commented 2 years ago

If you want to install stock shelly 1 firmware please do this:

  1. Download stock firmware from shelly: https://api.shelly.cloud/firmware/SHSW-1.zip

  2. Execute curl to update firmware on mongoose curl -i -F filedata=@SHSW-1.zip http://shellyip/update

mallito1307 commented 2 years ago

Same issue here! Please solve it 🙏🏻

tokamac commented 2 years ago

Wow, your program "installing" (failling to install) HAA actually bricked the two Shelly Dimmer 2 modules I bought. Now they are impossible to reach or update. And you won't even provide an update, yet alone make a warning statement about HAA on the main install page. Shame. Refund! Ahah juste joking but you seriously pissed me off @yaourdt.

TriderG75 commented 2 years ago

You can use the method posted two messages above to recover the Shellys. Of course you have to use the correct file for your Model

tokamac commented 2 years ago

Thanks, that worked! Using SHDM-2.zip for the Dimmer 2. I see that RavenSystem advises the following in the Third-Party Installation Tools on the HAA install page, for Shelly:

Shelly Devices OTA Version IMPORTANT: Until developer fixes current issue, install Tasmota, then Tasmota Minimal from WebUI, and then fullhaaboot.bin from WebUI.

I put the solution here since it's been weeks this annoying bug exists but the developper won't step in to make at least a statement.

abishur commented 2 years ago

dumb question here, but when you ran the http://shellyip/ota?url=http://dl.dasker.eu/firmware/mg2haa-Shelly1.zip command did you replace the "shellyip" with the ip of your shelly?

TriderG75 commented 2 years ago

dumb question here, but when you ran the http://shellyip/ota?url=http://dl.dasker.eu/firmware/mg2haa-Shelly1.zip command did you replace the "shellyip" with the ip of your shelly?

Of course. If you don't put the ip the command doesn't work and the Shelly remains with the original fw. In this case something changes in the fw and "bricks" the Shelly. Fortunately there is a way to recover it (look some messages above).

arkn666l commented 8 months ago

for me works today, yes i saw this page .. index of.. but minutes later the tasmota wifi appears...