Sonoff Mini doesn't go into DIY mode with 3.5.0 update

Fabien14000 commented 4 years ago

I have four sonoff mini diy. They were delivered with the 3.3.0 firmware release built in. I managed to set diy mode (with jumper) and update tasmota firmware for three of them.

But when I connected the last one to eWeLink, it proposed me to update to 3.5.0 release. I've done it without any trouble. But when I put the jumper on, the mini still work in standard mode (it connects to my wifi) and replies to eWeLink. There is no way to make it connect to "sonoffDiy" wifi.

Could it be a material defect or is there an issue with the 3.5.0 release ?

Thanks.

MubiTec commented 4 years ago

OMG!!! IT WORKED. This goes from step 7 So i downloaded the litefrom this link: https://github.com/arendst/Tasmota/releases/download/v8.2.0/tasmota-lite.bin

i downloaded wampserver X86, made a root folder and pasted the bin folder there in my appache httpd-vhost.conf i replaced everything with thi

<VirtualHost *:80> ServerName localhost ServerAlias localhost DocumentRoot "${INSTALL_DIR}/www" <Directory "${INSTALL_DIR}/www/"> Options +Indexes +Includes +FollowSymLinks +MultiViews AllowOverride All Require all granted

i pulled the plug out of my mini and plugge dit back in after 5 secondes i drectly sended the command from the advanced rest client like 2-3 times it goes very very very quick

then the 3 blinks happend i pulle dit out plugge dit back in and looked in my wifi list and suddenly there was a tasmota XXXX wifi network

connected to it and it auto opened tasmota (the flashed sonoff)

ui hope this help someone

Congratulations that it works! What do you me with plug? The little connector pin?

unbreakmat commented 4 years ago

No not the mini that one stays i mean the General power (i hooked it first to an outlet cable SO i could easily cut of the power entirly of the board

MubiTec commented 4 years ago

No not the mini that one stays i mean the General power (i hooked it first to an outlet cable SO i could easily cut of the power entirly of the board

Could you please tell me the checksum? And did you have the bracket between ota and ground?

gvrawake commented 4 years ago

OMG!!! IT WORKED. This goes from step 7 So i downloaded the litefrom this link: https://github.com/arendst/Tasmota/releases/download/v8.2.0/tasmota-lite.bin

i downloaded wampserver X86, made a root folder and pasted the bin folder there in my appache httpd-vhost.conf i replaced everything with thi

<VirtualHost *:80> ServerName localhost ServerAlias localhost DocumentRoot "${INSTALL_DIR}/www" <Directory "${INSTALL_DIR}/www/"> Options +Indexes +Includes +FollowSymLinks +MultiViews AllowOverride All Require all granted

i pulled the plug out of my mini and plugge dit back in after 5 secondes i drectly sended the command from the advanced rest client like 2-3 times it goes very very very quick

then the 3 blinks happend i pulle dit out plugge dit back in and looked in my wifi list and suddenly there was a tasmota XXXX wifi network

connected to it and it auto opened tasmota (the flashed sonoff)

ui hope this help someone

I can't get it done and don't know why.

My sonoff mini is connected to my local wifi network
It has the diy jumper on it and its updated to the newest 3.5.0 firmware.

I set up wampserver. Content of httpd-vhost.conf:

<VirtualHost *:80>
ServerName localhost
ServerAlias localhost
DocumentRoot "${INSTALL_DIR}/www"
<Directory "${INSTALL_DIR}/www/">
Options +Indexes +Includes +FollowSymLinks +MultiViews
AllowOverride All
Require all granted
</Directory>
</VirtualHost>

the tasmota-lite.bin file is downloadable from http://192.168.2.112/tasmota-lite.bin

with ARC I first send http://192.168.2.114:8081/zeroconf/ota_unlock with body {"deviceid":"","data":{}}
response: 200 OK {"seq":2,"error":0}
then I send http://192.168.2.114:8081/zeroconf/ota_flash with body { "deviceid": "", "data": { "downloadUrl": "http://192.168.2.112/tasmota-lite.bin", "sha256sum": "bde52065ba4af5fc16c170321364d056d06961382f739d5d26a32a850b81ecf1" } }
response: 200 OK {"seq":3,"error":0}
the mini led blinks 3 times short
I disconnect the mini, and after 5 seconds I reconnect.
No tasmota ssid shows up. The mini connects to my local wifi network again.

Fabien14000 commented 4 years ago

Please retry with this sha256sum related to tasmota-lite.bin: " 2716fc2b9628b53df8ff040400dda015f82085f470a6b194276ff51abda3425c"

I think it's the good one...

Le mar. 7 avr. 2020 à 23:43, gvrawake notifications@github.com a écrit :

OMG!!! IT WORKED. This goes from step 7 So i downloaded the litefrom this link:

https://github.com/arendst/Tasmota/releases/download/v8.2.0/tasmota-lite.bin

i downloaded wampserver X86, made a root folder and pasted the bin folder there in my appache httpd-vhost.conf i replaced everything with thi

<VirtualHost *:80> ServerName localhost ServerAlias localhost DocumentRoot "${INSTALL_DIR}/www" <Directory "${INSTALL_DIR}/www/"> Options +Indexes +Includes +FollowSymLinks +MultiViews AllowOverride All Require all granted

i pulled the plug out of my mini and plugge dit back in after 5 secondes i drectly sended the command from the advanced rest client like 2-3 times it goes very very very quick

then the 3 blinks happend i pulle dit out plugge dit back in and looked in my wifi list and suddenly there was a tasmota XXXX wifi network

connected to it and it auto opened tasmota (the flashed sonoff)

ui hope this help someone

[image: image] https://user-images.githubusercontent.com/63264046/78610287-d1ca9a00-7864-11ea-800c-76d991198f31.png

I can't get it done and don't know why.

My sonoff mini is connected to my local wifi network

It has the diy jumper on it and its updated to the newest 3.5.0 firmware.

I set up wampserver. Content of httpd-vhost.conf:

<VirtualHost *:80> ServerName localhost ServerAlias localhost DocumentRoot "${INSTALL_DIR}/www" <Directory "${INSTALL_DIR}/www/"> Options +Indexes +Includes +FollowSymLinks +MultiViews AllowOverride All Require all granted

the tasmota-lite.bin file is downloadable from http://192.168.2.112/tasmota-lite.bin

with ARC I first send http://192.168.2.114:8081/zeroconf/ota_unlock with body {"deviceid":"","data":{}}

response: 200 OK {"seq":2,"error":0}

then I send http://192.168.2.114:8081/zeroconf/ota_flash with body { "deviceid": "", "data": { "downloadUrl": "http://192.168.2.112/tasmota-lite.bin", "sha256sum": "bde52065ba4af5fc16c170321364d056d06961382f739d5d26a32a850b81ecf1" } }

response: 200 OK {"seq":3,"error":0}

the mini led blinks 3 times short

I disconnect the mini, and after 5 seconds I reconnect.

No tasmota ssid shows up. The mini connects to my local wifi network again.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/itead/Sonoff_Devices_DIY_Tools/issues/75#issuecomment-610635614, or unsubscribe https://github.com/notifications/unsubscribe-auth/APBHLQQC2B5JZYS347DPFQTRLONALANCNFSM4L25RT5Q .

CaseyRo commented 4 years ago

@gvrawake this is my body with a basic R3;

{
    "deviceid": "10008f967d",
    "data": {
        "downloadUrl": "http://192.168.8.101/tasmota-lite.bin",
        "sha256sum": "aa413f499233901f74502558561a1304e2a3d7ab72259740b377f52775adbb5d"
    }
}

I don't know how important the device ID / checksum is/was, but this worked for me.

unbreakmat commented 4 years ago

i noticed, really strange i think, that each time you download the tasmoto the sha256sum changes. You can easily check it on : https://emn178.github.io/online-tools/sha256_checksum.html

it is important that this one is correct because when you flash it checks it ==> it does his own sha256 and compares it with the one you give. This is an integrity mechanisme used in a lot of software (for example linux packages installing) When the sha doesnt mach the proces doesnt continue!!

I dont know when you flash the device and the sha dont match if an error is generated in your arc software!!

unbreakmat commented 4 years ago

No not the mini that one stays i mean the General power (i hooked it first to an outlet cable SO i could easily cut of the power entirly of the board

Could you please tell me the checksum? And did you have the bracket between ota and ground?

ota and ground? do you mean the jumper cable ==> YES keep it al time conected even when your done flashing and start using the device

unbreakmat commented 4 years ago

for those who want send a respons for a complete manual i will make one then (if there is respons)

Fabien14000 commented 4 years ago

Well in fact if you use a bad sha256sum, you still get a normal 200 ok answer. It's exactly the same when the file is unreachable... that's a pity. But the sonoff is going to blink for 3x times loops endlessly 🙄

Le mer. 8 avr. 2020 à 16:20, unbreakmat notifications@github.com a écrit :

i noticed, really strange i think, that each time you download the tasmoto the sha256sum changes. You can easily check it on : https://emn178.github.io/online-tools/sha256_checksum.html

it is important that this one is correct because when you flash it checks it ==> it does his own sha256 and compares it with the one you give. This is an integrity mechanisme used in a lot of software (for example linux packages installing) When the sha doesnt mach the proces doesnt continue!!

I dont know when you flash the device and the sha dont match if an error is generated in your arc software!!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/itead/Sonoff_Devices_DIY_Tools/issues/75#issuecomment-610987968, or unsubscribe https://github.com/notifications/unsubscribe-auth/APBHLQQ4J6IU2YCUUBJEYA3RLSB2XANCNFSM4L25RT5Q .

unbreakmat commented 4 years ago

Well in fact if you use a bad sha256sum, you still get a normal 200 ok answer. It's exactly the same when the file is unreachable... that's a pity. But the sonoff is going to blink for 3x times loops endlessly 🙄 Le mer. 8 avr. 2020 à 16:20, unbreakmat notifications@github.com a écrit : … i noticed, really strange i think, that each time you download the tasmoto the sha256sum changes. You can easily check it on : https://emn178.github.io/online-tools/sha256_checksum.html it is important that this one is correct because when you flash it checks it ==> it does his own sha256 and compares it with the one you give. This is an integrity mechanisme used in a lot of software (for example linux packages installing) When the sha doesnt mach the proces doesnt continue!! I dont know when you flash the device and the sha dont match if an error is generated in your arc software!! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APBHLQQ4J6IU2YCUUBJEYA3RLSB2XANCNFSM4L25RT5Q .

check if there is no tasmoto-XXXX wifi network !!!! ==> worked for me and did the trick , connect to it, tasmoto will auto open in browser --> change to your regular wifi netwerk an let reboot ==> should work then

gvrawake commented 4 years ago

How do I get my device ID? Is it a unique one? edit I think I have one from the EWE link app. Will try to flash again, and will double check the hash value

gvrawake commented 4 years ago

I did it! Got a tasmota wifi network now. I disabled my firewall (windows, on the laptop from who I send the requests), and noticed my wifi network was identified as 'public' instead of 'private'. So I send the ota unlock and ota flash command both with my device ID (from the EWE link app) and used the checksum from https://emn178.github.io/online-tools/sha256_checksum.html.

After flashing the led blinks 3 times fast, then I WAIT.. WAIT, and suddenly the led blinks one time slow... and there is the tasmota ssid.

finipini commented 4 years ago

Hello, for me after i put my wifi credentials , i open the tool and it still works like with version 3.3. Should it not work? I was in the midlle of making a tutorial for a forum in my country but with this posts, you scare me a bit...

gvrawake commented 4 years ago

Hello, for me after i put my wifi credentials , i open the tool and it still works like with version 3.3. Should it not work? I was in the midlle of making a tutorial for a forum in my country but with this posts, you scare me a bit...

Can you be more clear? In what step are you? Wich tool you open? You mean firmware version 3.3? Then all the info on this page is not for you, its for firmware 3.5, you first have to upgrade the firmware with the ewe link app.

MubiTec commented 4 years ago

then

OH, yes, this would be very good for me!

finipini commented 4 years ago

Hello, for me after i put my wifi credentials , i open the tool and it still works like with version 3.3. Should it not work? I was in the midlle of making a tutorial for a forum in my country but with this posts, you scare me a bit...

Can you be more clear? In what step are you? Wich tool you open? You mean firmware version 3.3? Then all the info on this page is not for you, its for firmware 3.5, you first have to upgrade the firmware with the ewe link app.

I mean with firmware 3.5, i downloaded the last version of the tool and it worked for me. I followed the new steps with firmware 3.5 ( protocol v2.0 ) but after putting my wifi credentials , i went to the tool and the sonoff mini was there. and then i flashed it with sonoff.basic.bin .

My question is - It was luckie for me to able to do that way ? It may not work every time ?

laziukiewicz commented 4 years ago

I still can't get this to work - every command works - I can flip the switch using:

{
"deviceid": "100091075c",
"data": { 
    "switch": "off"
    }
}

but never get any responses after trying to flash

{
"deviceid": "100091075c",
"data": { 
    "downloadUrl": "http://192.168.0.101/tasmota-lite.bin"
    "sha256sum": "bde52065ba4af5fc16c170321364d056d06961382f739d5d26a32a850b81ecf1"
    }
}

Firmware is uploaded to a webserver on my NAS and I can easily access it from other computers on my LAN. I tried with different firmware versions and doublechecked checksums, but still get timeouts. I've never received any reponses on /zeroconf/ota_flash I know this topic is about minis - perhaps this just doesn't work for RFR3?

iMatt1681 commented 4 years ago

Hi,

Please can I have some help. I am having no luck flashing my sonoff mini. I have no programming experience and having trouble getting started with it. Can someone help me with a very simple guide please?

Thank you.

radekposvar commented 4 years ago

Hi, please I need help with the flashing. I am able to send post to my mini, I've unlocked the ota flash, but I am unable to tasmotize it. I use this command: { "deviceid": "1000a4562e", "data": { "downloadUrl": "file://homeassistant/config/www/tasmota-lite.bin", "sha256sum": "bde52065ba4af5fc16c170321364d056d06961382f739d5d26a32a850b81ecf1" } } And I get: { "seq": 12, "error": 0 }

The mini starts blinking trile times, but never stops, no tasmota SSID appears and I have to unplug it to be able to start again. Actually I dont know how you did the thing with appache. I tried upload the .bin file to my web server, or direcly to my Pi, I was able to download it when I pasted the path to explorer, but flash never worked. Please could you give me any advices? Thank you, Radek

CaseyRo commented 4 years ago

@radekposvar for one thing, "file://" will never work - the device itself needs to be able to access the link.

I run with a mac and use the built-in webserver to serve the file to my device;

sudo apachectl start

and upload the bin file to my webserver, use it from there.

AFAIK the sonoff device needs to be able to get the file from a webserver from some reason, and have some particular response/headers to work.

I've tried it in a MAMP setup before, I couldn't get that to work.

"three blinks and nothing" to me always meant it failed, only when it gets irregular it is flashing the firmware.

Hope this helps!

radekposvar commented 4 years ago

@radekposvar for one thing, "file://" will never work - the device itself needs to be able to access the link.

I run with a mac and use the built-in webserver to serve the file to my device;
sudo apachectl start
and upload the bin file to my webserver, use it from there.

AFAIK the sonoff device needs to be able to get the file from a webserver from some reason, and have some particular response/headers to work.

I've tried it in a MAMP setup before, I couldn't get that to work.

"three blinks and nothing" to me always meant it failed, only when it gets irregular it is flashing the firmware.

Hope this helps!

Thank you for your help, suddenly I do not have mac. I've downloaded Simple HTTP Server and modified the command to:

{ "deviceid": "1000a4562e", "data": { "downloadUrl": "http://192.168.100.137:18803/tasmota-lite.bin", "sha256sum": "bde52065ba4af5fc16c170321364d056d06961382f739d5d26a32a850b81ecf1" } }

Also didnt work :-(

Daniel-zhan-itead commented 4 years ago

Hi All,

SONOFF released the DIY MODE 2.0 for BASICR3, RFR3 and MINI with the firmware of 3.5.0.

You can find below links to access related information.

Developers page: http://developers.sonoff.tech/ Video demo: https://www.youtube.com/watch?v=1TmgJnvtV0s Article: https://sonoff.tech/product-tutorials/diy-mode-to-control-the-sonoff-device

Now we optimized the set up procedure as a Access Point, we add device id, firmware version, bssid, signal strength in " get device info" API, correct some tiny bug and error in firmware.

Enjoy the DIY mode.

Daniel-zhan-itead commented 4 years ago

In firmware 3.5.0, to switch into DIY Mode, you don't need to plug-in the jumper anymore.

Just follow the steps from developers page, you can enter the DIY Mode successfully.

Daniel

radekposvar commented 4 years ago

Hi All,

SONOFF released the DIY MODE 2.0 for BASICR3, RFR3 and MINI with the firmware of 3.5.0.

You can find below links to access related information.

Developers page: http://developers.sonoff.tech/ Video demo: https://www.youtube.com/watch?v=1TmgJnvtV0s Article: https://sonoff.tech/product-tutorials/diy-mode-to-control-the-sonoff-device

Now we optimized the set up procedure as a Access Point, we add device id, firmware version, bssid, signal strength in " get device info" API, correct some tiny bug and error in firmware.

Enjoy the DIY mode.

Hi Daniel, thank you for sharing with us these documents and video. However DIY mode could be usefull for many users, I would like still to flash the software with tasmota. I know, there is command for flashing, but I am unable to done it. Could you please explain how to create the url adress to my mini will be able to download the .bin file? It would be great if you could explain it for windows users. Thank you very much, Radek

iMatt1681 commented 4 years ago

@Keesromkes,

Hi Kees, I am also using a MAC. Could you tell me how to upload the bin file to the webserver please?

What should the "downloadUrl" be?

Thank you

Matthew.

CaseyRo commented 4 years ago

@Keesromkes,

Hi Kees, I am also using a MAC. Could you tell me how to upload the bin file to the webserver please?

What should the "downloadUrl" be?

Thank you

Matthew.

This should help you Matthew; https://tasmota.github.io/docs/MacOSX-Server/

iMatt1681 commented 4 years ago

@Keesromkes, Hi Kees, I am also using a MAC. Could you tell me how to upload the bin file to the webserver please? What should the "downloadUrl" be? Thank you Matthew.

This should help you Matthew; https://tasmota.github.io/docs/MacOSX-Server/

Thank you Kees,

I've followed the instructions and stuck with the sonoff flashing 3 times.

Fabien14000 commented 4 years ago

Hi. 3x led flash means either the bin file is unreachable on the local network or the sha256 is not correct 🙄 sorry

Le dim. 12 avr. 2020 à 10:50, iMatt1681 notifications@github.com a écrit :

@Keesromkes https://github.com/Keesromkes, Hi Kees, I am also using a MAC. Could you tell me how to upload the bin file to the webserver please? What should the "downloadUrl" be? Thank you Matthew.

This should help you Matthew; https://tasmota.github.io/docs/MacOSX-Server/

Thank you Kees,

I've followed the instructions and stuck with the sonoff flashing 3 times.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/itead/Sonoff_Devices_DIY_Tools/issues/75#issuecomment-612583899, or unsubscribe https://github.com/notifications/unsubscribe-auth/APBHLQSQVYFJKKVWP4W7PFDRMF6GPANCNFSM4L25RT5Q .

ssancese commented 4 years ago

Hey all,

I am finding extremely difficult to connect to my BASIC R3 ver. 3.5.0 when in AP mode (contnuous short blink). It has worked two times say in 200 tries, so it is definitely possible but definitely not practical....

To be more precise, the process explained in http://developers.sonoff.tech/sonoff-diy-mode-api-protocol.html fails at step number 5 of the example because all my browsers of all my devices can't reach the page. My wifi connection to the AP is OK (DHCP working 10.10.7.2 client address) but "the page can't be reached..."

So I was wondering if someone could offer some help here. Thanks in advance!

demian85 commented 4 years ago

Can someone please explain to me why using Ewelink I cannot upgrade the firmware of my basic r3 to v3.5? The latest showing up is 3.3.... I'm tired of this shit, I cannot use DIY mode because you basically need to be a NASA engineer to understand the steps.

Daniel-zhan-itead commented 4 years ago

Hi All,

As the mini add the function to set external switch type for pulse mode, edge mode and following mode. we got some feedback from users for this firmware.

Now 3.5.0 firmware was closed

it will effect BASICR3, RFR3 and MINI to upgrade to 3.5.0.

SO some people have upgraded to 3.5.0, most still can't see the upgrade for 3.5.0.

We will release soon, sorry for that.

Daniel

nhe050 commented 4 years ago

Thanks for clarifying that @Daniel-zhan-itead. Received a batch of new mini's yesterday which I would like to update and then flash using the new, much easier DIY method as I did with another batch last month (3.5.0 working fine for me).

Could you give a slightly more precise indication of when "soon" will be?

Daniel-zhan-itead commented 4 years ago

Hi All,

3.5.0 firmware is released again.

You can update the firmware via eWeLink application.

Daniel from SONOFF

nhe050 commented 4 years ago

You need two REST calls to perform the flash. Unlock first, than perform actual flash.

curl http://<deviceIP>:8081/zeroconf/ota_unlock -XPOST --data '{"deviceid":"<deviceID>","data":{} }'
curl http://<deviceIP>:8081/zeroconf/ota_flash -XPOST --data '{"deviceid":"<deviceID>","data":{"downloadUrl": "http://<webServer>/tasmota-wifiman.bin", "sha256sum": "<SHAsum>"} }'

And make sure to flash to tasmota_wifiman.bin first. Connect it to your WiFi and then flash to actual tasmota using the wifiman firmware.

nhe050 commented 4 years ago

One way or another the procedure requires the firmware to be available through a webserver. Could be IIS on Windows or nginx in a Docker container or ... After this, subsequent tasmota versions can (and should!) be installed via local file upload.

smingoli commented 4 years ago

I managed to flash tasmota-wifiman on my sonoff mini.... Now, if I understand correctly, I should flash the full tasmota.bin with the "Upgrade by file upload" option in the tasmota menu. Does the mini have enough space to upload the full tasmota.bin? I'm asking because I think I read somewhere sometime ago that it bricks the device.

nhe050 commented 4 years ago

Good question. It won't fit at once but tell you there's not enough space. I had it when I flashed my first. But just a proper message, not bricked. Install tasmota-minimal.bin first. Then tasmota.bin. General advice is to perform a "Reset 5" using the tasmota console between flashes to clean-up any leftovers.

smingoli commented 4 years ago

Thanks @nhe050. As you said flashe tasmota-minimal first and then tasmota.bin with a Reset 5 before flashing each firmware and everything went well :-)

bovirus commented 4 years ago

I have a Sonoff Basic R3 with stock firmware 3.5.0.

The Sonofff Basic R3 has pins for serial console.

Is it possible to flash tasmota firmware using the same system as for Sonoff R1/R2?

Thanks.

paul-777 commented 4 years ago

One critical point of note - on firmware 3.5 if you do have the jumper on DIY mode doesn't work, 8081 gets opened but the REST interface fails.

nhe050 commented 4 years ago

Yes I noticed that as well. The good news being that you just don’t need te jumper anymore and can leave the case closed 😁

scaytrase commented 4 years ago

For anyone who reach here as me trying to flash new devices, I leave a note that it's highly important that firmare link points to local network. I was getting no result with flashing mini with link pointing to thehackbox server and get an immediate success after locating file on local server (in my case it was raspberry pi with nginx, but I'm sure any local docker would work too)

paul-777 commented 4 years ago

So this thread contained a bunch of useful info but it still took me some time to get a new device flashed, so here are the steps I have found to work. Once you get all your ducks in a line it is pretty simple, hopefully someone will make an app that can do steps 5 to 11 just by entering the device IP and selecting a firmware bin to use from github.

1) Connect the Sonoff R3 to eweLink and make sure firmware is 3.5, can take a while to offer the upgrade 2) Do NOT put the DIY jumper on this is not required and actually stops it working 3) to get DIY mode you MUST do this step - enabling LAN mode from ewelink does not work - their support have confirmed as much a. https://sonoff.tech/product-tutorials/diy-mode-to-control-the-sonoff-device b. Press button for 5secs lights change pattern c. Press for 5 sec again lights change pattern d. Connect to the istead??? access point using pwd 12345678 e. Go to http://10.10.17.1 f. Enter your wifi details (SSID and password are case sensitive) 4) Lookup device IP from router or use fing to find it 5) Make new firmware (I used 8.31 tasmota-lite.bin from https://github.com/arendst/Tasmota/releases/tag/v8.3.1 ) available on webserver - must be http not https and ip address not host name, your port may vary e.g. http://192.168.10.30:88/tasmota-lite.bin Chosen new firmware must be <508KB. To use larger ones search for the process around using TasmotaMinimal. 6) Use a site like this one the get the SHA256 of the bin file https://md5file.com/calculator 7) Use REST tool (e.g. https://install.advancedrestclient.com/install) to send commands (change IP as needed 192.168.20.116 is just where mine ended up) 8) Test get info - if this doesn't work nothing else will - check firewalls etc. http://192.168.20.116:8081/zeroconf/info {"deviceid":"","data":{}} 9) Unlock device for OTA firmware upgrade http://192.168.20.116:8081/zeroconf/ota_unlock {"deviceid":"","data":{}} 10) Flash the new firmware (change ip of rest url, download url, sha256) http://192.168.20.116:8081/zeroconf/ota_flash { "deviceid": "", "data": { "downloadUrl": "http://192.168.10.30:88/tasmota-lite.bin", "sha256sum": "7351bd4342b112326472750ad94c9551a16db313715dfc244e078f63d6d14195" } } 11) If successful the device reboots after a minute and the tasmota access point will become available If unsuccessful and the lights keep flashing (mine was sets of 2 flashes) power off for 5sec then power on and try again from step 8. (For some reason after attempting it with a hostname not url and it failing the REST service still worked but the device would not go online again in ewelink.) 12) If successful connect to the Tasmota???? Access Point using laptop or phone 13) Go to http://192.168.4.1 - you should get the tasmota wifi config page 14) Enter your wifi details and save, wait for device to reboot 15) Check router or fing to find IP http://192.168.10.116 (use the ip you just found) you are now in Tasmota 16) If the device does not connect, LED will be flashing (normally it's off), hold the button for 40secs to reset Tasmota and try again from step 13

bovirus commented 4 years ago

@paul-777

Thanks for the info.

Question:

Is it possible to flash directly the tasmota firmware (<= 508KB) via serial console as I did for basic R1? In the R3 are availble the PIN for serial console.

You mentioned that you have to load tanmota-minimal (<=508KB).

But after that and tasmota minimal was flashed in teh unit is it possible to load a tasmota firmware bigger than 508KB?

Or the limit for the firmware si always inside (R3 has less space for firmware than Basic R1)?

Thanks.

paul-777 commented 4 years ago

Sorry, I'm very new to all of this so can't say for certain, but I think it is still possible to do serial flashing from what I have read and once you go via the tasmota-miniml route larger firmware is still possible - as far as I know the memory on the R3 is the same.

erickkahlke commented 4 years ago

I have a Sonoff Basic R3 with stock firmware 3.5.0.

The Sonofff Basic R3 has pins for serial console.

Is it possible to flash tasmota firmware using the same system as for Sonoff R1/R2?

Thanks.

This would we awesome. Sadly DIY needs a second look from ITEAD. At least Sonoff should get the .bin file from any given address, local or not, ip or domain, etc. Many unnessesary steps. Why tasmota offers me to select a .bin file or link and the default DIY MODE can't?

alexcurtui commented 4 years ago

Question for those who only want to use the REST API: why do you want to flash Tasmota?

demian85 commented 4 years ago

I honestly got tired of this shit and soldered 4 pins directly to the board, flashed Tasmota, and it works like a charm.

Question for those who only want to use the REST API: why do you want to flash Tasmota?

Why not? It's the best generic firmware out there for an ESP8266 chip. You cannot do anything interesting with a simple REST API...

bovirus commented 4 years ago

@demian85

Then you can confirm that you can flash on Sonoff Basic R3 the tasmota firmware using serial console as you can do with Basic r1/R2?

Did you flash directly tasmota full firmware (> 508 KB) or did you use a different way?

itead / Sonoff_Devices_DIY_Tools

Sonoff Mini doesn't go into DIY mode with 3.5.0 update #75