Followed instructions, entered correct OTA URL for Tasmota (verified as I could pull the ZIP file)
Waited 10 mins.
Restarted several times.

No Tasmota, no WIFI AP.

Will pull out a FDDI next....

I also bricked a shelly dimmer 2 using this script

./flash-shelly.py shellydimmer2-40F5202D7BBC.local -v1 -t tasmota 
app
OS: Linux
manual_hosts: ['shellydimmer2-40F5202D7BBC.local']
target: tasmota
do_all: False
dry_run: False
silent_run: False
exclude: None
verbose: 1

stock_release_info:{'isok': True, 'data': {'SHPLG-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHPLG-1.zip', 'version': '20210115-103101/v1.9.4@e2732e05'}, 'SHPLG-S': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHPLG-S.zip', 'version': '20210429-101611/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHPLG-S.zip', 'beta_ver': '20210514-070847/v1.10.5-rc1-gecc99b7'}, 'SHPLG-U1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHPLG-U1.zip', 'version': '20210429-101656/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHPLG-U1.zip', 'beta_ver': '20210514-070929/v1.10.5-rc1-gecc99b7'}, 'SHPLG2-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHPLG2-1.zip', 'version': '20210429-101742/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHPLG2-1.zip', 'beta_ver': '20210514-071319/v1.10.5-rc1-gecc99b7'}, 'SHSW-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-1.zip', 'version': '20210429-100340/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHSW-1.zip', 'beta_ver': '20210514-065742/v1.10.5-rc1-gecc99b7'}, 'SHSW-21': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-21.zip', 'version': '20210429-100513/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHSW-21.zip', 'beta_ver': '20210514-065912/v1.10.5-rc1-gecc99b7'}, 'SHSW-25': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-25.zip', 'version': '20210429-100559/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHSW-25.zip', 'beta_ver': '20210514-065956/v1.10.5-rc1-gecc99b7'}, 'SHSW-PM': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-PM.zip', 'version': '20210429-101828/v1.10.4-g3f94cd7'}, 'SHSW-L': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-L.zip', 'version': '20210429-100426/v1.10.4-g3f94cd7'}, 'SHAIR-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHAIR-1.zip', 'version': '20210429-101914/v1.10.4-g3f94cd7'}, 'SHSW-44': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-44.zip', 'version': '20201019-110845/v1.6.6_4Pro@bad181e4'}, 'SHUNI-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHUNI-1.zip', 'version': '20210429-102528/v1.10.4-g3f94cd7'}, 'SHEM': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHEM.zip', 'version': '20210429-102232/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHEM.zip', 'beta_ver': '20210514-071759/v1.10.5-rc1-gecc99b7'}, 'SHEM-3': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHEM-3.zip', 'version': '20210429-102318/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHEM-3.zip', 'beta_ver': '20210514-071842/v1.10.5-rc1-gecc99b7'}, 'SHSEN-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSEN-1_build.zip', 'version': '20200717-112934/v1.7.7@a02db0b8'}, 'SHMOS-01': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHMOS-01_build.gbl', 'version': '20210226-072307/v1.1.0@f31e1d2b'}, 'SHGS-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHGS-1.zip', 'version': '20210429-102444/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHGS-1.zip', 'beta_ver': '20210514-072008/v1.10.5-rc1-gecc99b7'}, 'SHSM-01': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSM-01.zip', 'version': '20210413-153317/v1.10.2-gb89901a'}, 'SHHT-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHHT-1.zip', 'version': '20210413-154417/v1.10.2-gb89901a'}, 'SHWT-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHWT-1.zip', 'version': '20210413-155706/v1.10.2-gb89901a'}, 'SHDW-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHDW-1.zip', 'version': '20210413-154021/v1.10.2-gb89901a'}, 'SHDW-2': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHDW-2.zip', 'version': '20210413-154114/v1.10.2-gb89901a'}, 'SHSPOT-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSPOT-1.zip', 'version': '20201124-091104/v1.9.0@57ac4ad8'}, 'SHCL-255': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHCL-255.zip', 'version': '20210429-095824/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHCL-255.zip', 'beta_ver': '20210514-065226/v1.10.5-rc1-gecc99b7'}, 'SHBLB-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHBLB-1.zip', 'version': '20210429-095954/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHBLB-1.zip', 'beta_ver': '20210514-065355/v1.10.5-rc1-gecc99b7'}, 'SHCB-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHCB-1.zip', 'version': '20210429-095910/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHCB-1.zip', 'beta_ver': '20210514-065311/v1.10.5-rc1-gecc99b7'}, 'SHRGBW2': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHRGBW2.zip', 'version': '20210429-101353/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHRGBW2.zip', 'beta_ver': '20210514-070636/v1.10.5-rc1-gecc99b7'}, 'SHRGBWW-01': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHRGBWW-01.zip', 'version': '20210429-100209/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHRGBWW-01.zip', 'beta_ver': '20210514-065611/v1.10.5-rc1-gecc99b7'}, 'SH2LED-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SH2LED-1.zip', 'version': '20210429-100254/v1.10.4-g3f94cd7'}, 'SHDM-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHDM-1.zip', 'version': '20210429-102007/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHDM-1.zip', 'beta_ver': '20210514-071538/v1.10.5-rc1-gecc99b7'}, 'SHDM-2': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHDM-2.zip', 'version': '20210429-102101/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHDM-2.zip', 'beta_ver': '20210514-071630/v1.10.5-rc1-gecc99b7'}, 'SHDIMW-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHDIMW-1.zip', 'version': '20210429-102146/v1.10.4-g3f94cd7'}, 'SHVIN-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHVIN-1.zip', 'version': '20210429-100039/v1.10.4-g3f94cd7'}, 'SHBDUO-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHBDUO-1.zip', 'version': '20210429-100125/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHBDUO-1.zip', 'beta_ver': '20210514-065526/v1.10.5-rc1-gecc99b7'}, 'SHBTN-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHBTN-1.zip', 'version': '20210415-130655/v1.10.3-g23074d0'}, 'SHBTN-2': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHBTN-2.zip', 'version': '20210415-130749/v1.10.3-g23074d0'}, 'SHIX3-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHIX3-1.zip', 'version': '20210429-102402/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHIX3-1.zip', 'beta_ver': '20210514-071924/v1.10.5-rc1-gecc99b7'}, 'SHPLG-UK1': {'beta_url': 'http://api.shelly.cloud/firmware/rc/SHPLG-UK1.zip', 'beta_ver': '20210514-071128/v1.10.5-rc1-gecc99b7'}}}

intermediate_release_info:[['x2.9.1-.*', {'version': '2.9.1', 'rel_notes': 'https://github.com/mongoose-os-apps/shelly-homekit/issues/617', 'rel_notesX': '', 'urls': {'Shelly1': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1.zip', 'Shelly1L': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1L.zip', 'Shelly1PM': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1PM.zip', 'Shelly2': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly2.zip', 'Shelly25': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly25.zip', 'ShellyI3': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyI3.zip', 'ShellyPlug': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyPlug.zip', 'ShellyPlugS': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyPlugS.zip', 'ShellyRGBW2': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyRGBW2.zip'}}], ['.*', {'version': '2.9.1', 'rel_notes': 'https://github.com/mongoose-os-apps/shelly-homekit/releases/tag/2.9.1', 'urls': {'Shelly1': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1.zip', 'Shelly1L': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1L.zip', 'Shelly1PM': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1PM.zip', 'Shelly2': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly2.zip', 'Shelly25': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly25.zip', 'ShellyI3': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyI3.zip', 'Shelly-i3': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyI3.zip', 'ShellyPlug': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyPlug.zip', 'ShellyPlugS': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyPlugS.zip', 'ShellyRGBW2': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyRGBW2.zip'}}]]

device_scan
Probing Shelly device for info...

Valid Hostname: shellydimmer2-40F5202D7BBC.local True
Hostname: shellydimmer2-40F5202D7BBC.local is Online
Device URL: http://172.30.31.84/settings
device_test: [{'host': 'shellydimmer2-40F5202D7BBC.local', 'wifi_ip': '172.30.31.84', 'fw_type': 'stock', 'device_url': 'http://172.30.31.84/settings', 'info': {'device': {'type': 'SHDM-2', 'mac': '40F5202D7BBC', 'hostname': 'shellydimmer2-40F5202D7BBC', 'num_outputs': 1, 'num_meters': 1}, 'wifi_ap': {'enabled': False, 'ssid': 'shellydimmer2-40F5202D7BBC', 'key': ''}, 'wifi_sta': {'enabled': True, 'ssid': 'J&M IOT', 'ipv4_method': 'dhcp', 'ip': None, 'gw': None, 'mask': None, 'dns': None}, 'wifi_sta1': {'enabled': False, 'ssid': None, 'ipv4_method': 'dhcp', 'ip': None, 'gw': None, 'mask': None, 'dns': None}, 'mqtt': {'enable': False, 'server': '192.168.33.3:1883', 'user': '', 'id': 'shellydimmer2-40F5202D7BBC', 'reconnect_timeout_max': 60.0, 'reconnect_timeout_min': 2.0, 'clean_session': True, 'keep_alive': 60, 'max_qos': 0, 'retain': False, 'update_period': 30}, 'coiot': {'update_period': 15}, 'sntp': {'server': 'time.google.com', 'enabled': True}, 'login': {'enabled': False, 'unprotected': False, 'username': 'admin'}, 'pin_code': '', 'name': '', 'fw': '20200629-130515/release-1.7@28744b8b', 'discoverable': True, 'build_info': {'build_id': '20200629-130515/release-1.7@28744b8b', 'build_timestamp': '2020-06-29T13:05:15Z', 'build_version': '1.0'}, 'cloud': {'enabled': False, 'connected': False}, 'timezone': 'Europe/Amsterdam', 'lat': 52.084091, 'lng': 4.31732, 'tzautodetect': True, 'tz_utc_offset': 7200, 'tz_dst': True, 'tz_dst_auto': True, 'time': '18:43', 'unixtime': 1621968237, 'hwinfo': {'hw_revision': 'prod-20200629', 'batch_id': 1}, 'mode': 'white', 'pulse_mode': 1, 'calibrated': False, 'transition': 1000, 'fade_rate': 3, 'min_brightness': 0, 'lights': [{'name': '', 'ison': False, 'default_state': 'off', 'auto_on': 0.0, 'auto_off': 0.0, 'btn1_on_url': '', 'btn1_off_url': '', 'btn1_longpush_url': '', 'btn1_shortpush_url': '', 'btn2_on_url': '', 'btn2_off_url': '', 'btn2_longpush_url': '', 'btn2_shortpush_url': '', 'out_on_url': '', 'out_off_url': '', 'schedule': False, 'schedule_rules': [], 'btn_type': 'one_button', 'btn_debounce': 80, 'swap_inputs': 0}], 'night_mode': {'enabled': False, 'start_time': '00:00', 'end_time': '00:00', 'brightness': 0}, 'warm_up': {'enabled': 0, 'brightness': 100, 'time': 50}}}]
Mode: Stock To Intermediate

parse_info
device_info: <__main__.StockDevice object at 0x7fcf78334a00>
host: shellydimmer2-40F5202D7BBC.local
device: shellydimmer2-40F5202D7BBC
model: ShellyDimmer2
stock_model: SHDM-2
colour_mode: white
target firmware: tasmota
dlurl: http://dl.dasker.eu/firmware/mg2tasmota-ShellyDimmer2.zip
Host: http://shellydimmer2-40F5202D7BBC.local
Device ID: shellydimmer2-40F5202D7BBC
IP: 172.30.31.84
Model: ShellyDimmer2
D_URL: http://dl.dasker.eu/firmware/mg2tasmota-ShellyDimmer2.zip

perform_flash: True

Do you wish to flash shellydimmer2-40F5202D7BBC.local to tasmota (y/n) ? y

write_flash
Now Flashing...
curl -qsS http://172.30.31.84/ota?url=http://dl.dasker.eu/firmware/mg2tasmota-ShellyDimmer2.zip
{"status":"updating","has_update":false,"new_version":"","old_version":"20200629-130515/release-1.7@28744b8b"}
please wait for shellydimmer2-40F5202D7BBC.local to reboot to tasmota.

Hello!

I think there needs to be some adjustment to the downloaded files
as nothing is happening on my shelly dimmer 2 when I try to OTA..
The link itself works because I can manually download the .zip-file.

This is the response i get

{"status":"updating","has_update":false,"new_version":"","old_version":"20200629-130515/release-1.7@28744b8b"}

It's missing "new version" as seen here
https://youtu.be/_oRr8FZyyQ0?t=393

Help my device is not listed!

Tried to flash the Shelly Duo RGBW but the device is not listed.

python3 /usr/local/bin/flash-shelly -t tasmota 192.168.1.145
Probing Shelly device for info...

Host: http://192.168.1.145
Device ID: shellycolorbulb-483FDA927E7C
IP: 192.168.1.145
Model: SHCB-1
Device is not supported yet...

If your device is not listed, please open a new issue so we can try to make it work. Please mention which of the many Shelly firmware files is the right one for your device.

"SHCB-1":{"url":"http://shelly-api-eu.shelly.cloud/firmware/SHCB-1.zip","version":"20210107-122133/1.9_GU10_RGBW@07531e29","beta_url":"http://api.shelly.cloud/firmware/rc/SHCB-1.zip","beta_ver":"20210405-090555/v1.10.2-rc5-gc86c23a"}

Hi,
is there also a chance to support the Shelly UNI?
Thanks for the great work.

Joerg

Hi, first of all, wow! This is very cool!

I have successfully flashed multiple devices as a step toward esphome (sorry for that but for me more flexible with hass).

I wondered if the shelly 1L will als become in you list.

Its such a cool device "without neutral".

https://shelly.cloud/products/shelly-1l-single-wire-smart-home-automation-relay/

it would be great to be able to "unlock" shelly motion for use with tasmota and other firmwares.
the great advantage would be to be able to use some devices that are locked to the master firmware because of a "failed" version that does not allow in any way the upgrade

the reference firmware is this:
"SHMOS-01":{"url":"http://shelly-api-eu.shelly.cloud/firmware/SHMOS-01_build.gbl","version":"20210927-192701/v2.0.1@bd17709f"}

I am available for any information or test

I managed to flash proprietary software Zumungo into Shelly1, thanks to the help form this community and Mark in particular. Thanks again for that.

Now I'm trying to host the working fw.zip in the cloud and it doesn't work from the cloud.

This works fine, where the fw.zip file is hosted locally at ...248 and Shelly is at ...125

http://192.168.1.125/ota?url=http://192.168.1.248/fw.zip

This doesn't work

http://192.168.1.125/ota?url=http://zumungo.com/wp-content/uploads/ShellyOTA/fw.zip

It is the same fw.zip file and it is accessible from a local machine (on the same network that Shelly is connected to) that downloads the file when pointed to the address http://zumungo.com/wp-content/uploads/ShellyOTA/fw.zip

Tried to move the file to the root directory of the remote machine but still no luck. These don't work either.

http://192.168.1.125/ota?url=http://zumungo.com/fw.zip
http://192.168.1.125/ota?url=http://www.zumungo.com/fw.zip

Thanks for the great tool. Wondering if I can flash any .bin file. I'm using zumungo.com ESP software and I like everything to be on the same platform. For example will this work

http://shellyip/ota?url=http://myownwebserver/htdocs/mybinfile.bin

, where mybinfile.bin is the binary file that I want to flash into Shelly. Typically it comes from Arduino IDE compiler - "Export compiled binary" but in the case of zumungo.com it comes from the vendor per-compiled .bin file. Yes, zumungo.com is OTA enabled software so that memory partitions should be observed for OTA.

In the readme it mentions that there is no known way yet to come back from tasmota to the original shelly fw thru OTA but I in this conversation #9 it seems very well be possible ?
Thanks !

Is it possible to convert Shelly TH? I run mine on USB power,so the lack of sleep in Tasmota is not a concern. Thank you!

Hi @yaourdt !

Thank you for the great work!

Is it possible to flash Shelly 1 with ESPHome firmware, similarly how you described it for Tasmota?

One of the possible ways would be => update Shelly’s firmware with Tasmota first, and then use Tasmota OTA to upload ESPHome firmware… but it is a bit complicated when you have a lot of devices to deal with 😅

Thank you,
Alexander

As a lot of the Shelly templates from blackadder are already 9.x versions, I suggest to raise the tasmota-minimal version in your firmware also to 9.x.
If not, and you forget to upgrade to 9.x before utilizing the templates, you might have a messy GPIO configuration.

Thanks again for you excellent work.

Any chance we can add this device ?

I think the firmware is:

shelly-api-eu.shelly.cloud\firmware\SHCB-1.zip

Thanks

    "SHCB-1": {
      "url": "http:\/\/shelly-api-eu.shelly.cloud\/firmware\/SHCB-1.zip",
      "version": "20210107-122133\/1.9_GU10_RGBW@07531e29"
    },

I am trying to flash Tasmota on a stock Shelly RGBW2 with a 12 volt power supply. The Shelly is on a network with internet access and I am using the correct script from your Github for the device. I am able to download the .zip file to my PC that is on the same network as the Shelly. I checked the "old version" of the Shelly software on my device and it matches the string below which I get when entering script URL.

{"status":"updating","has_update":false,"new_version":"","old_version":"20190822-083406/master@4148d2b7"}

The LED on the Shelly flashes a few times so it appears to be flashing and then flashes periodically, but the tasmota device never appears on my network and the Shelly does not update.

Any suggestions on how to do an OTA flash for this device are appreciated greatly.

Thank you!

Could you include these devices too, please? They are supported by Tasmota and Home Accessory Architect:

• Shelly RGBW2.
• Shelly Dimmer.
• Shelly EM.

Thanks!

I successfully flashed a Shelly Plug US with 8.5.0. Thanks!

If I set it as a Shelly 1, the basic functionality works--I can turn it on and off.

What's a good starting point so I can start to figure out how to add support for the power monitoring? I don't mind doing custom Tasmota builds, I just have no idea where to start.

I have a defective Shelly Plug US that I don't mind cutting open if it helps.

Thanks for any pointers!

Hi there

I tried to flash my Shelly 1L; but I got this message in the browser:

File Not Found

URI: /ota
Method: GET
Arguments: 1
url: http://dl.dasker.eu/firmware/mg2tasmota-Shelly1L.zip

What went wrong? - Is there no more Shelly 1L support?

I tried to flash tasmota to a shelly 1 with the python script.

When I refreshed the webpage during flash it showed me a folder with a couple of files

Then it became unreachable and doesn't connect to the wifi anymore.

I also set up a mgos-recover ssid but it's not connecting to it and I also don't see an ssid of the shelly coming online.

stock_release_info:{'isok': True, 'data': {'SHPLG-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHPLG-1.zip', 'version': '20210115-103101/v1.9.4@e2732e05'}, 'SHPLG-S': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHPLG-S.zip', 'version': '20210429-101611/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHPLG-S.zip', 'beta_ver': '20210514-070847/v1.10.5-rc1-gecc99b7'}, 'SHPLG-U1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHPLG-U1.zip', 'version': '20210429-101656/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHPLG-U1.zip', 'beta_ver': '20210514-070929/v1.10.5-rc1-gecc99b7'}, 'SHPLG2-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHPLG2-1.zip', 'version': '20210429-101742/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHPLG2-1.zip', 'beta_ver': '20210514-071319/v1.10.5-rc1-gecc99b7'}, 'SHSW-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-1.zip', 'version': '20210429-100340/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHSW-1.zip', 'beta_ver': '20210514-065742/v1.10.5-rc1-gecc99b7'}, 'SHSW-21': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-21.zip', 'version': '20210429-100513/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHSW-21.zip', 'beta_ver': '20210514-065912/v1.10.5-rc1-gecc99b7'}, 'SHSW-25': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-25.zip', 'version': '20210429-100559/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHSW-25.zip', 'beta_ver': '20210514-065956/v1.10.5-rc1-gecc99b7'}, 'SHSW-PM': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-PM.zip', 'version': '20210429-101828/v1.10.4-g3f94cd7'}, 'SHSW-L': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-L.zip', 'version': '20210429-100426/v1.10.4-g3f94cd7'}, 'SHAIR-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHAIR-1.zip', 'version': '20210429-101914/v1.10.4-g3f94cd7'}, 'SHSW-44': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSW-44.zip', 'version': '20201019-110845/v1.6.6_4Pro@bad181e4'}, 'SHUNI-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHUNI-1.zip', 'version': '20210429-102528/v1.10.4-g3f94cd7'}, 'SHEM': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHEM.zip', 'version': '20210429-102232/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHEM.zip', 'beta_ver': '20210514-071759/v1.10.5-rc1-gecc99b7'}, 'SHEM-3': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHEM-3.zip', 'version': '20210429-102318/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHEM-3.zip', 'beta_ver': '20210514-071842/v1.10.5-rc1-gecc99b7'}, 'SHSEN-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSEN-1_build.zip', 'version': '20200717-112934/v1.7.7@a02db0b8'}, 'SHMOS-01': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHMOS-01_build.gbl', 'version': '20210226-072307/v1.1.0@f31e1d2b'}, 'SHGS-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHGS-1.zip', 'version': '20210429-102444/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHGS-1.zip', 'beta_ver': '20210514-072008/v1.10.5-rc1-gecc99b7'}, 'SHSM-01': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSM-01.zip', 'version': '20210413-153317/v1.10.2-gb89901a'}, 'SHHT-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHHT-1.zip', 'version': '20210413-154417/v1.10.2-gb89901a'}, 'SHWT-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHWT-1.zip', 'version': '20210413-155706/v1.10.2-gb89901a'}, 'SHDW-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHDW-1.zip', 'version': '20210413-154021/v1.10.2-gb89901a'}, 'SHDW-2': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHDW-2.zip', 'version': '20210413-154114/v1.10.2-gb89901a'}, 'SHSPOT-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHSPOT-1.zip', 'version': '20201124-091104/v1.9.0@57ac4ad8'}, 'SHCL-255': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHCL-255.zip', 'version': '20210429-095824/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHCL-255.zip', 'beta_ver': '20210514-065226/v1.10.5-rc1-gecc99b7'}, 'SHBLB-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHBLB-1.zip', 'version': '20210429-095954/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHBLB-1.zip', 'beta_ver': '20210514-065355/v1.10.5-rc1-gecc99b7'}, 'SHCB-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHCB-1.zip', 'version': '20210429-095910/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHCB-1.zip', 'beta_ver': '20210514-065311/v1.10.5-rc1-gecc99b7'}, 'SHRGBW2': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHRGBW2.zip', 'version': '20210429-101353/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHRGBW2.zip', 'beta_ver': '20210514-070636/v1.10.5-rc1-gecc99b7'}, 'SHRGBWW-01': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHRGBWW-01.zip', 'version': '20210429-100209/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHRGBWW-01.zip', 'beta_ver': '20210514-065611/v1.10.5-rc1-gecc99b7'}, 'SH2LED-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SH2LED-1.zip', 'version': '20210429-100254/v1.10.4-g3f94cd7'}, 'SHDM-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHDM-1.zip', 'version': '20210429-102007/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHDM-1.zip', 'beta_ver': '20210514-071538/v1.10.5-rc1-gecc99b7'}, 'SHDM-2': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHDM-2.zip', 'version': '20210429-102101/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHDM-2.zip', 'beta_ver': '20210514-071630/v1.10.5-rc1-gecc99b7'}, 'SHDIMW-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHDIMW-1.zip', 'version': '20210429-102146/v1.10.4-g3f94cd7'}, 'SHVIN-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHVIN-1.zip', 'version': '20210429-100039/v1.10.4-g3f94cd7'}, 'SHBDUO-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHBDUO-1.zip', 'version': '20210429-100125/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHBDUO-1.zip', 'beta_ver': '20210514-065526/v1.10.5-rc1-gecc99b7'}, 'SHBTN-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHBTN-1.zip', 'version': '20210415-130655/v1.10.3-g23074d0'}, 'SHBTN-2': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHBTN-2.zip', 'version': '20210415-130749/v1.10.3-g23074d0'}, 'SHIX3-1': {'url': 'http://shelly-api-eu.shelly.cloud/firmware/SHIX3-1.zip', 'version': '20210429-102402/v1.10.4-g3f94cd7', 'beta_url': 'http://api.shelly.cloud/firmware/rc/SHIX3-1.zip', 'beta_ver': '20210514-071924/v1.10.5-rc1-gecc99b7'}, 'SHPLG-UK1': {'beta_url': 'http://api.shelly.cloud/firmware/rc/SHPLG-UK1.zip', 'beta_ver': '20210514-071128/v1.10.5-rc1-gecc99b7'}}}

intermediate_release_info:[['x2.9.1-.*', {'version': '2.9.1', 'rel_notes': 'https://github.com/mongoose-os-apps/shelly-homekit/issues/617', 'rel_notesX': '', 'urls': {'Shelly1': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1.zip', 'Shelly1L': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1L.zip', 'Shelly1PM': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1PM.zip', 'Shelly2': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly2.zip', 'Shelly25': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly25.zip', 'ShellyI3': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyI3.zip', 'ShellyPlug': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyPlug.zip', 'ShellyPlugS': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyPlugS.zip', 'ShellyRGBW2': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyRGBW2.zip'}}], ['.*', {'version': '2.9.1', 'rel_notes': 'https://github.com/mongoose-os-apps/shelly-homekit/releases/tag/2.9.1', 'urls': {'Shelly1': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1.zip', 'Shelly1L': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1L.zip', 'Shelly1PM': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly1PM.zip', 'Shelly2': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly2.zip', 'Shelly25': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-Shelly25.zip', 'ShellyI3': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyI3.zip', 'Shelly-i3': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyI3.zip', 'ShellyPlug': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyPlug.zip', 'ShellyPlugS': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyPlugS.zip', 'ShellyRGBW2': 'https://rojer.me/files/shelly/2.9.1/shelly-homekit-ShellyRGBW2.zip'}}]]

device_scan

I guess removing the lamp from the ceiling and do a serial flash is my only option....

Flashing other software was accomplished successfully in manual mode. See issue #27
Mark mentioned kindly that he will consider making the process easy and automated as it is for Tasmota.
I'm opening this issue with the goal to follow up and track this effort. No rush and no pressure.

I got three Shelly 1L devices from their Europe store (it was much cheaper than ordering from the US store). I went and flashed devices with Tasmota binaries. Flashing of the first two went well and without any issues. I cannot flash the third one even though I used exactly the same steps. I connected Shelly to my home network but when trying to flash a new binary (cut & paste of the URL with updated IP address of the Shelly device), it does not flash it. It gives me the following message in the browser:

{"status":"updating","has_update":false,"new_version":"","old_version":"20201014-165335/1244-production-Shelly1L@6a254598"}

It does not flash a Tasmota binary. I can still go back to the device and get their original GUI interface. Let me know if you want me to collect any additional data before I used expose pins and USB programmer to flash the binary.

Hi!!

So, first of all, thanx so much for this SW that you have developed. It is helping so much to the community to flash device. Almost everyone is using it to flash these devices.

Regarding the update, would it be possible please to use the last version of fullhaaboot that has been published? Previous contain some bugs that might cause problems during the installation.

https://github.com/RavenSystem/haa/releases/latest/download/fullhaaboot.bin

Last, but not least, would it be somehow possible that the version updates directly form the official repository?

Thanx much!

It’s possible to use this method on a shelly plug https://shelly.cloud/products/shelly-plug-smart-home-automation-device/ ? Thank you

edit: I believe that the device is a SHPLG2-1

Hi. I would like to have Shelly Door Window 2 here to convert to HAA. The Firmware is: SHDW-2.zip

Thanks!

Bricked 2 Plug S.

One i had updated to latest firmware, one was not toched before i tried.

Did follow instructions, after ota device rebooted keeping its ip and you could se a filesystem if you visited the old address.

After quite a long time, 15 minutes or so the device rebooted.

No tasmota, did attach serial, and can se a repeating message sent, but could not decode the baudrate.

Tried 115200, 57600, 74880 could not decode anything.

Pulled GPIO 0 low, got esptool.py working, but flashing tasmota failed.

Hi.

I've been trying to flash a couple of Shelly 1, but no success so far.

I tried two different shelly's, and both were newest firmware available. I can see the JSON output as expected, and the shelly restarts one time (i ping it all the time, so i can see that it dies one time) but nothing more happends.

I saw a closed issue here with something similiar, so i tried to download the zip file to a local web server and changed the URL so that the shelly would download it from there. Then the Shelly restarted one time, and i can ping it, but the shelly web server is now not accessible. Since i downt have a cable here right now i dont want to try that with the second one yet 😄

Any suggestions?

is it possible to OTA firmware for shelly 3 EM with
http://192.168.x.xx/ota?
url=http://dl.dasker.eu/firmware/mg2tasmota-shelly????.zip

Thanks and regards
Thomas

First of all, great idea and great job on this so far!

I had a spare Shelly1 around so I flashed it back to the stock Shelly1 firmware and tried the procedure once I had it on my network. I had a ping session open on it to see if it was going to reboot and such but it seems right after I send the URL it stops pinging for a couple seconds then comes back. So I waited for the 4-5 minutes and refreshed the Shelly1 page, same stock firmware. I tried it again after updating to the latest Shelly1 firmware but I got the same result. Is there some sort of log I can check to see what's going on? View it via serial maybe?

Hi,

I have documented the problem in here: RavenSystem/esp-homekit-devices#1074

But I think it could also be useful to open an issue here. It seems that your method is installing the "HAA Installer 3.2.0" version, maybe because of a local copy on a repository, while the developer of the project has launched "HAA Installer 4.0.0".

Problem is that "HAA Installer 3.2.0" is no longer compatible with "HAA Main" versions since 2.5.2. They are currently at 2.5.7.

So if we update a Shelly with your procedure nowadays, it gets stuck into an update loop and never ends the process. I had to point my Shelly to an older version (2.5.0 in my case) to get it working again.

I copy and paste here my solution from the other GitHub:

Hi again! I solved the problem :) try this, at least it worked for me.

It seems that there are two different things into the HAA: Installer and Main.

In my case, I "flashed" the Shelly 1 vía OTA using a link from the internet, in my case the link was this one:

http://X.X.X.X/ota?url=http://dl.dasker.eu/firmware/mg2haa-Shelly1.zip

Problem with this procedure was that the mg2haa uses a local copy of the HAA Installer and it is still using the 3.2.0 version. The HAA Installer 3.2.0 version is only compatible with HAA Main versions until 2.5.2. Since 2.5.3 this Installer is no longer compatible and the installation will fail and enter into a loop.

Solution for me was the following:

1º) I set my Shelly1 into setup mode.
2º) I accessed the menu and under the "Custom Server for updates" I have set this link:
github.com/RavenSystem/haa/releases/download/2.5.0/
3º) Wait a bit and you will have version 2.5.0 installed of HAA Main, with HAA Installer 3.2.0.
4º) Access again to "Setup Mode" and select "Update all now (HAA OTA v3.2.0)"
5º) Wait a bit and you will end with your device updated to HAA Installer 4.0.0 and HAA Main 2.5.7.

This worked for me! I hope it helps to anyone who has the same problem.

BR!

Hello,
Thanks for providing this solution. Unfortunately I had issues converting a "Shelly Plug S" and a "Shelly 1L" to ESPurna.

Shelly Plug S:
Once connected to WiFi I issued the command "wget http://192.168.179.53/ota?url=http://dl.dasker.eu/firmware/mg2espurna-ShellyPlugS.zip".

The first stage seems to work (ping stopped for ten seconds and then continued), but the process did not proceed after that and did not finish for several minutes. I gave up waiting after about ten minutes.

Current state of the Shelly Plug S:
I can still access the webserver, but it just gives a directory listing with a couple of files. Amongst them some JSON and the index.html.gz. The OTA endpoint is not working anymore (Not Found). Pinging the device works.

Edit 1: Shelly 1L:
I tried the similar procedure with a Shelly 1L, but used the script flash-shelly.py for that - same issue:
$ python3 flash-shelly.py -a -t espurna
It found the device, I confirmed and it started converting the device.

While pinging I could observe that about 8 seconds the ping stops, comes back and just remains available. It seems as if it does not continue into the final firmware. Here is the same state, just a directory listing.

Is there anything I can do besides opening the devices and flashing over-wires? Did I do anything wrong?

Best regards,
Torx

Edit 2: I tried the script with a second Shelly 1L and converted to Tasmota. That worked as expected (no issues, runs Tasmota now), so my issues with the two devices above is that I specified to convert them to ESPurna.

I was successful with moving the final six of the eight Shelly Plug US unit to Tasmota using this method over the weekend. Six of the eight on online, one is in reserve and eighth unit went flakey before any attempts and will not convert.

I am going to see if using the Tasmota software gets these back to a stable operation that I was pretty much seeing with the Shelly firmware prior to some firmware update they did.

I did not have any issues converting 7 of the units, I had to redo two units. I suspect I made missteps during the conversion that forced me to redo, however I am not positive.

The problems that started occurring with the Shelly firmware that brought me to the work here were:

1. Some of my units started to randomly power off for about a second. This seems to have occurred after one of the firmware updates. However I am not able to identify which. This occurred on 3 or 4 of the units starting about November of 2020.

2. Units would drop off wifi and not come back except with a power cycle of the unit, then would stay on for extended period. This would 2 or three of the units, would happen once every three or four months. The attached AC device could still be controlled by button on Shelly.

3. Units would drop off wifi and the Shelly drive would lockup so as to even the button on the device would not operate the attached AC device. Power cycling the Shelly device would recover. This too seems to have started around the November 2020 time frame.

It was item one above that caused me to reach out to Shelly support and resulted in ending up here. Shelly support never responded to my request for help. I am not a Facebook user, but the limited scan I can do on the Facebook Shelly forum seems to show me that others are having similar problems many starting recently.

I am suspicious that my problems might be related to the Shelly device interaction with my wifi configuration. I have a 3 access point mesh Mikrotik setup. That said I have about fifty other IoT devices including many other esp8266 and esp32 devices on this wifi network longer than the Shelly's with no problems. I see that some others on the Shelly forum are reporting similar problems with Unifi based wifi setups.

I hope the Tasmota Shelly path yields a stable power monitoring solution for my HA setup.

On the one Shelly Plug US device that would not convert to Tasmota, here is some info that might interesting to others.

It was 'bricked' prior to me going down this Tasmota route. I think I bricked it in the course of trying setting changes and resetting in the course of experiencing the 'power drop out' problem I described above.

I put this unit 'on the shelf', however after successfully moving the other Shelly Plug US units to Tasmota, I went back to this unit. I was able to 'unbrick' it by some combination of holding the units power button during power on. I am not sure if the sequence that recovered it is to first press the power button before applying AC power or to press the button right after applying AC power. However, by holding the button for maybe 20 to 30 seconds at initial startup brought this unit back to it's state on the Shelly firmware prior to my 'bricking' it.

From this recovery of the unit back to seemly normal operation on Shelly firmware version 1.9.2, I unsuccessfully tried the conversion of this unit to Tasmota. I factory reset it multiple times and the unit would not do the factory firmware update to the latest Shelly firmware either. I tried both and many factory resets with no luck. So in a sense, this unit is still 'bricked', even though it seem to operate on the versions of Shelly firmware (more on this below). I did NOT run this unit for any length of time to see if the original problem of it powering off for a second still is occurring.

On this unit, even though I was NOT able to do the Tasmota firmware conversion or do the normal Shelly firmware upgrade to the latest version :

Current version: 20201128-103019/v1.9.2@e83f7025
New version: 20210415-131130/v1.10.3-g23074d0

I was able to change the Shelly firmware to multiple versions using this web site:

http://archive.shelly-tools.de/

However from NONE of the maybe 5 other version of Shelly firmware I tried from this web site was I able to get this unit to either move to Tasmota or to do the 'normal' firmware upgrade. Also one of the only version that did NOT work on this unit from the web site was the :

v1.10.4-rc1/SHPLG-U1.zip

FYI, good luck!

I used URL => http://xx.xx.xx.51/ota?url=http://dl.dasker.eu/firmware/mg2tasmota-Shelly1.zip on my Shelly 1 v3 and it never came back, I got the confirmation that it was going to do the update, waited 10 minutes and then no Tasmota wifi, neither could not get back from the IP it had, in which it was a static IP

Hi
Awesome OTA update!!
I did notice that in the shelly WIFI settings - if I set a static IP the update does not seem to work?
I have tested with a number of devices - the moment I remove the static IP - it updates perfectly

Rgds
J

Hi Yaourdt,

Just flashed 4 PM2.5.
Script works like a charm!

Thanks,
Jacques-D.

Can I be pointed in the right direction to get this working? flashed OK, can control the relay but I see no EM features, which is sort of the point. Cheers!

OK...not really an issue but hopefully Mark Dornbach or one of the other contributors will reply. I don't write code but would like to make a contribution of a few bucks - buy someone a coffee, paypal, etc. I've used both Mark's shelly to tasmota and tasmota to shelly conversion steps and they have saved me dragging out my usb programmer. I've spent about 20 minutes digging and so far have found nothing.

Is the firmware for the shelly plug S or US compatible with the Shelly plug ??

If not could you create a firmware / template for the big shelly plug ?
the firmware is
http://shelly-api-eu.shelly.cloud/firmware/SHPLG2-1.zip
version":"20210323-105844/v1.10.1-gf276b51"
SHSW-1":

Tried on a Mac running MacOS 11.4.
Error:

Scanning for Shelly devices...
Traceback (most recent call last):
  File "/Users/joschawagner/Downloads/mgos-to-tasmota-main/tools/flash-shelly.py", line 517, in <module>
    device_scan(args.hosts, args.do_all, args.dry_run, args.silent_run, args.target, args.exclude)
  File "/Users/joschawagner/Downloads/mgos-to-tasmota-main/tools/flash-shelly.py", line 438, in device_scan
    zc.wait(100)
AttributeError: 'Zeroconf' object has no attribute 'wait'

I had previously flashed 2 Shelly US plugs without issue, back in late October, and got around to flashing my last 2 tonight, and both of them have failed. I followed the same procedure as I previously did, but this time around they never came up with their own wifi network, and are not sitting on any accessible IP that I can find.

I have tried to reset them with the fast power cycle recovery, and still no luck. Seems odd that what worked in October is no longer working. One plug had been used for the few months with the Shelly firmware, the other sat unused for that time. Any recommendations?

@yaourdt any chance we could see firmware for the Shelly Duo bulb? Looks like it's called "SHBDUO" under the stock firmware listing. Would be happy to help test.

http://api.shelly.cloud//firmware/SHBDUO-1.zip

I have been playing around reverting Tasmota back to the native Shelly mgos firmware via OTA. I think I might of found something. Most of the recovery Shelly FW files are 2MB. I was checking out the issue on the arendst/Tasmota#8436 and looking at the comments. In the comment listed here, the 2MB flash layout was linked here and I noticed something, it has two applications listed in the flash. Once again I was stupidly playing around with flashing my Shelly 2.5, I decided to backup the first 1MB of the native Shelly flash using USB to Serial adapter.

I repeated this steps below 5 times, all successful.

Pre-Steps (To generate a 1MB recovery image)

1. Flash the Shelly with the recovery firmware from this url with USB-to-Serial adapter. https://www.shelly-support.eu/filebase/index.php?entry-download/112-shelly2-5-recovery-firmware-1-5-10/&fileID=152
2. Backup first 1MB of Shelly flash using USB-to-Serial adapter. You can use "esptool.py" with the following command python esptool.py -b 115200 --port COM4 read_flash 0x000000 0x100000 shellyBackup.bin. You can also use Tasmotizer backup checkbox as it only save 1MB of flash.
3. Compress the 1MB .bin file using gzip.

Steps

1. Flash mgos -> Tasmota using http://shellyip/ota?url=http://dl.dasker.eu/firmware/mg2tasmota-Shelly25.zip
2. Connect Tasmota to wifi.
3. Flash the Tasmota Minimal via OTA.
4. Flash the compressed 1MB dump via OTA on Tasmota. If the flash fails you might have to run the following in Tasmota SetOption78 1 console and reboot before trying again. This takes a few mins to complete.

Notes

After reverting Shelly firmware version will be ????, this is fixed after updating.
Tried with more than one Shelly 2.5.

Warnings

Only tested with Shelly 2.5.
This doesn't work if you do a Reset command to clear flash in Tasmota.
During testing only the Shelly recovery firmware image will work. Tried V1.8 and others and got a boot loop.
Also during testing if you don't use the mgos-to-tasmota via Shelly OTA it won't work. You will get a boot loop if you don't use mgos-to-tasmota.
This experiment was a result of drunk coding, so try at your own risk.

Ideas on why this works

mgos-to-tasmota copies app0 to app1. Then it puts Tasmota around first 1MB of memory and doesn't clear entire flash, so I am guessing "rf cal" and "sys params" don't get cleared.

I have released a new version of HAA Installer. Please, update yours with last version from here:

https://github.com/RavenSystem/haa/releases/latest/download/fullhaaboot.bin

I have released a new version of HAA Installer. Please, update yours with last version from here:

https://github.com/RavenSystem/haa/releases/latest/download/fullhaaboot.bin

Many thanks!

RGBW2 doesn't work for me with the default update link.
After opening the link I got a response without new_version:

{"status":"updating","has_update":false,"new_version":"","old_version":"20200827-070157/v1.8.3@4a8bc427"}

Looks like it refuses to parse/read firmware archive.

I have released a new version of HAA Installer. Please, update yours with last version from here:

https://github.com/RavenSystem/haa/releases/latest/download/fullhaaboot.bin

Many thanks!

First of all thank you for great work, It helped me a lot!

I just would like to know is there a way to flash (OTA) ESP devices (other than Shelly) with this method?
The mgos-to-tasmota method would be even better for devices needed soldered GPIO access only. I have flashed in the past some MagicHome devices and it was really cumbersome...
https://tasmota.github.io/docs/devices/MagicHome-with-ESP8285/

Is there a way to build a kind of "general" *.bin and than customize it with corresponding template?

Thank you again,

Lajos

Hi,

Firs of all thanks for your work making this possible. I just encountered an issue with flashing a Shelly Plug S with tasmota.

I've connected the plug WiFi, and then I issued the command : http:///ota?url=http://dl.dasker.eu/firmware/mg2tasmota-ShellyPlugS.zip

I then saw:
{"status":"updating","has_update":false,"new_version":"20210115-103659/v1.9.4@e2732e05","old_version":"20190516-073020/master@ea1b23db"}

The leds on the plug started flashing but stopped after a while, I waited for about ten minutes, then replugged the plug but nothing, it doesn't connect to WiFi or creates an SSID. Also the rings on the led are not flashing. There's only a led on the board (D2) solid red.. (not the ring)

I did exactly the same thing about a week ago with success. the only thing is see in the outut when flashing is new_version":"20210115" I did the succesful flash before 15-01 maybe there's a difference?

Any advise I can do? I'm already looking how to physically connect to the plug to flash it that way.

Hello

I tried this on Three Shelly 1L's.

The first worked perfectly, just as described. Restarted a couple of times and came back with Tasmota in just few minutes and was working great since.

Few days later I tried the exact same procedure on another Shelly 1L that was working fine with stock firmware. This time the device died. It gave me the json answer that says status=updating which is the normal behavior. Then it restarted and never came back. It was inaccessible via wifi and the physical switch did not work either. I thought I did something wrong, so I tried with another one, after all the first one went so well.

Pointed it to the suitable url, this time double checking it's for Shelly 1L, checking that the link is alive and not touching anything during the process. Unfortunately this one also never came back from its restart.

So I do not know exactly what went wrong in the Two last times and what made a difference from the first one, but I will have to flush them manually.

I just got a Shelly Duo bulb. After following the instructions, and the video, I used
http://shellyip/ota?url=http://dl.dasker.eu/firmware/mg2tasmota-ShellyDuo.zip
It returned

status	"updating"
has_update	false
new_version	""
old_version	"20191216-140245/???"

But I never saw the tasmota access point, and now I'm getting nothing from the bulb. I've turned it on and off multiple time since with no luck.

Is my only option left to attempt to open the bulb and solder wires to it? Is there anything else I should try?