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

[Fabien14000]

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.

[demian85]

I used Tasmotizer and flashed the latest stable release. Connected device using serial to USB adapter.

On Tue, May 26, 2020, 03:14 bovirus notifications@github.com wrote:

@demian85 https://github.com/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?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/itead/Sonoff_Devices_DIY_Tools/issues/75#issuecomment-633827462, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADS4ZV77ZAXF6U6ZGDZ3D3RTNM2TANCNFSM4L25RT5Q .

[alexcurtui]

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...

Ok, thank you, valid reasoning. I'm needing it solely for the REST API because I have all the logic in Node-RED, but in this case I definitely agree.

[paublanco]

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

I did the same yesterday with a mini. Now is working smoothly.

[bovirus]

@paulblanco

Has Sonoff Mini the PIN for serial console?

Found this info about Sonoff Mini and serial console

https://templates.blakadder.com/sonoff_mini.htmlù

[paublanco]

@bovirus, I don't know if we can speak of "pin" ;), but you can access some GPIOS: https://user-images.githubusercontent.com/3912017/66733148-dfc3d300-ee5e-11e9-8715-87c8ecb844a7.jpg (Same image you found)

[bovirus]

@paublanco

Thanks for the info.

It's the same info.

It's very intersting for who want upgrade to tasmpota without so many problem using a TTL 3.3V/USB converter.

[Mpalmer4wd]

I purchased 2 Sonoff Minis a few weeks ago. (Both 3.3 firmware and DIY v1) - Very first one flashed no problems via the DIYTool and is working a treat controlling my lights in my kitchen via Openhab / Tasmota. Second one will not flash. Got too hard so tried to solder the pins onto the board and I stuffed the board up. (Waiting on a friend printing a programming jig atm).

Yesterday I received another shipment of 4 x Sonoff Minis and noticed on here that the DIY mode has updated to V2. The first section is a lot simpler not having to setup the temporary AP etc. and I got the units onto my home network with an IP address quite simply. In regards to re-flashing, I have tried all of the above solutions and cannot get the Tasmota firmware to flash onto the Sonoff units. It looks like its flashing and gives me the 200 OK response. The Sonoff then flashes 3 times quickly and a quick pause before repeating. (Before flashing it flashes twice then quick pause - repeat). Any ideas? Im using the temporary web server to host the tasmota files. have done the minimal version then lite, etc. None of these seem to take effect and allow the device to cast a Tasmota IP address to start configuration.

I have a strong preference to go to Tasmota / MQTT over Rest / HTTP but so far the DIY mode isnt achieving this for me. My fingers are crossed the programming jig does the trick.

[paul-777]

@Mpalmer4wd just to be sure have you executed the ota_unlock command before attempting the flash? The ones I have been receiving are 3.0 which I update to 3.5, from there the hardest part is getting them to actually accept any of the REST commands. Details (as far as I have been able to test are above). Once I have got the responding to REST calls the process has been easy. ewelink support have acknowledged there is a problem with 3.5 and the LAN mode doesn't actually enable in the way it should - they say wait for a new firmware but provide no timescale. What seems to work for me is resetting them and joining them to the network by joining the istead network and entering wifi details there - before that I had then on the network but not responding to REST calls.

[Mpalmer4wd]

Paul-777, Yes i have unlocked the ota and verified that it accepted via the info command. Still no luck.

[paul-777]

@Mpalmer4wd The other issue I found was that it needed ip address and port - not a hostname, and http not https. Then it was just making sure I didn't have any firewalls etc blocking the download. I connected my phone to the same VLAN as the device then verified the download url that way. (I'm flashing the tasmota-lite minimal 8.31) The other check is to verify the SHA code you are providing - if that doesn't match your file then obviously it will not upgrade.

[Mpalmer4wd]

@paul-777 I have been using the IP Address and port instead of hose name and is HTTP. I'll double check the firewall aspect though. I'm using a basic web server for chrome to host the files and believe I have the SHA code correct. Am using the https://md5file.com/calculator to obtain the SHA256 code and entering in the post. Ill turn my firewall off today when I have some time and give it another go. Thanks

[Mpalmer4wd]

@paul-777 I turned off the firewall and tried again. No luck. Same response. The 'flash' process seems to only take between 50ms and 100ms which seems short maybe? The unit does change from flashing twice to then flashing three times but does not actually reboot. It stays on my same network address and doesnt change. After I power cycle the unit, it returns to flashing twice (connected to wifi). Ive attached a screenshot of the Rest settings i am using. I am far from an expert in this area so if there is something I have incorrect here, I would appreciate any help. Thanks.

[theOzzieRat]

I solved the problem with the DIY tool by turning off all my other network interfaces. The DIY tool will bind to the wrong NIC if there is more than one. The DIY Tool sets itself up as a little webserver for the Sonoff to connect to, but when it gets the wrong NIC communications is not possible.

[Hackschnipsel]

@paul-777 I turned off the firewall and tried again. No luck. Same response. The 'flash' process seems to only take between 50ms and 100ms which seems short maybe? The unit does change from flashing twice to then flashing three times but does not actually reboot. It stays on my same network address and doesnt change. After I power cycle the unit, it returns to flashing twice (connected to wifi). Ive attached a screenshot of the Rest settings i am using. I am far from an expert in this area so if there is something I have incorrect here, I would appreciate any help. Thanks.

I am having the exact same problem. I tried about everything on two different PC´s. One time in my network and one time via Smartphone hotspot. I tried tasmota-minimal and lite. I tried new hash-codes. No luck. I hope, somebody will find the solution. Somewhere I read, that the 3 times flashing LED indicates, that the Hash is wrong or that there is a problem downloading the fw-file. I also tried to reach the webserver via phone and PC with success. So it shouldn´t be the webserver software either. I have no more ideas.

[theOzzieRat]

Also you must run DIY Tool from a local drive with the firmware in the same directory. If you have it on a network drive it will fail. The DIY tool sets up a webserver on port 776 on a randomly chosen interface (if you have more than one).

[Hackschnipsel]

Also you must run DIY Tool from a local drive with the firmware in the same directory. If you have it on a network drive it will fail. The DIY tool sets up a webserver on port 776 on a randomly chosen interface (if you have more than one).

Even with FW 3.5.0 ?

[theOzzieRat]

Also you must run DIY Tool from a local drive with the firmware in the same directory. If you have it on a network drive it will fail. The DIY tool sets up a webserver on port 776 on a randomly chosen interface (if you have more than one).

Even with FW 3.5.0 ?

Definitely. I just got 2 minis today and had the battle again. If you run it from a network drive it will not listen on port 776 for some reason. It is not the firmware version but the DIYTool that is buggy. The way it works is that the firmware downloads the new firmware file from the DIYTool. The DIYTool doesn't upload to the device, it just triggers the device to make the request.

[bovirus]

For all people that has Mini I suggest

to solder 4 wires for serial console flash the tasnmota firmware via serial consol and TTL converter

If you are using Windows 10 don't use serial TTL converter based on PL2303 because this chispet is not supported by Windows 10.

Then after flashed the firmware you can alsor emove the wires

Sonoff Basic R3 - Serial pinout

https://imgur.com/8UK7NLI

Sonoff Mini - Serial pinout

https://imgur.com/eKYPntd

..

[Hackschnipsel]

Also you must run DIY Tool from a local drive with the firmware in the same directory. If you have it on a network drive it will fail. The DIY tool sets up a webserver on port 776 on a randomly chosen interface (if you have more than one).

Even with FW 3.5.0 ?

Definitely. I just got 2 minis today and had the battle again. If you run it from a network drive it will not listen on port 776 for some reason. It is not the firmware version but the DIYTool that is buggy. The way it works is that the firmware downloads the new firmware file from the DIYTool. The DIYTool doesn't upload to the device, it just triggers the device to make the request.

Nice! Your news give me some motivation. I will give it a try later.

[theOzzieRat]

Also you must run DIY Tool from a local drive with the firmware in the same directory. If you have it on a network drive it will fail. The DIY tool sets up a webserver on port 776 on a randomly chosen interface (if you have more than one).

Even with FW 3.5.0 ?

Definitely. I just got 2 minis today and had the battle again. If you run it from a network drive it will not listen on port 776 for some reason. It is not the firmware version but the DIYTool that is buggy. The way it works is that the firmware downloads the new firmware file from the DIYTool. The DIYTool doesn't upload to the device, it just triggers the device to make the request.

Nice! Your news give me some motivation. I will give it a try later.

Make sure you disable all network adapters except the one that the Sonoff will be able to connect to as well. I have things like Wireshark and VMWare that create virtual adapters that the DIYTool bound to (never going to work). Also disable you local firewall or allow tcp/776.

[Hackschnipsel]

Also you must run DIY Tool from a local drive with the firmware in the same directory. If you have it on a network drive it will fail. The DIY tool sets up a webserver on port 776 on a randomly chosen interface (if you have more than one).

Even with FW 3.5.0 ?

Definitely. I just got 2 minis today and had the battle again. If you run it from a network drive it will not listen on port 776 for some reason. It is not the firmware version but the DIYTool that is buggy. The way it works is that the firmware downloads the new firmware file from the DIYTool. The DIYTool doesn't upload to the device, it just triggers the device to make the request.

Nice! Your news give me some motivation. I will give it a try later.

Make sure you disable all network adapters except the one that the Sonoff will be able to connect to as well. I have things like Wireshark and VMWare that create virtual adapters that the DIYTool bound to (never going to work). Also disable you local firewall or allow tcp/776.

Thank you! I "deactivated" all Network adapters (interfaces) as you said and only kept the WIFI-adapter activated. And it worked!

[Mpalmer4wd]

Finally today I managed to get my 6 new units flashed. Took about 4 hours of trial and error though. Had to use several different methods to get them all to program. What would work for one wouldn't work for another. Hopefully my 3D Printed programming jig will be ready tomorrow for my next batch. Thanks everyone for your help.

[theOzzieRat]

I think the biggest issue here is the complete lack of response or support from itead. Currently 51 open issues, this thread has 125 comments and not a single one of them is from anyone at itead. The products could be great and easy to use, but the support is non existent. I have been trying to contact them via all sorts of methods and have not had a single response.

[paul-777]

The issue is with ewelink firmware, the LAN mode switch in the UI doesn't work - I have had their support confirm that they are aware of it, but no date for a fix.

However there is a process to get DIY mode 100% of the time.

From a new device, do NOT put the jumper on, power it up 1) Connect to ewelink and upgrade firmware to 3.5 and allow it to reboot 2) Press button for 5 seconds (light pattern changes) 3) Press button again for 5secs (light pattern changes again) 4) Connect to the isteadxxxx AP using pwd 12345678 5) Browse to http://10.10.7.1 6) Enter your SSID and pwd for your LAN - case sensitive and hit Save 7) Wait for device to reboot Device will now be available for DIY RESTful API. You just need to find the IP address it has been assigned and then use a REST tool to send it commands.

This process is (badly) documented on https://sonoff.tech/product-tutorials/diy-mode-to-control-the-sonoff-device

Given that the device appeared on the network after connecting to ewelink and was pingable this all feels strange but it is necessary and does work. I flashed 3 devices yesterday, all of which followed this process with zero issues.

The gotchas are that LAN Mode in the eweLink app is irrelevant and doesn't work and that the jumper is also now to be left off.

I have documented further steps for OTA flashing of tasmota further up the thread. After various trial and error processes, these steps now work 100% of the time. I flashed 3 devices yesterday in very little time.

[Felipetomaz]

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

Even with 3.5.0 version, I could use the tool_01DIY85(3.3.0).exe application, but only after I have unlocked the OTA (with ARC, sending http://yourIP:8081/zeroconf/ota_unlock with body {"deviceid":"","data":{}}), I could see the SonOff mini in the tool_01DIY85 and could upload the firmware like I would if I had the last version 3.3.0.

I hope this could help someone.

[mattadams84]

Once you have got your head around it, its actually very simple.

Here is a simple guide to flash the Sonoff R3 Basic (not sure if it works on the mini, i have never tried). This works if your firmware is 3.5.0.

PRE-REQUISITES:

ARC plugin on Chrome (or any other REST tool) XAMPP (or any other webserver tool) tasmota-lite.bin

If your Sonoff Basic R3 is not on 3.5.0 then:

1. Do NOT put the jumper on, power it up.
2. Connect to ewelink and upgrade firmware to 3.5.0 and allow it to reboot.
3. Set up Apache server on your PC (i used XAMPP) put the tasmota-lite.bin file in the server (the file must be accessible by "http://ip/path"). You can test this works by putting the URL in your browser and see that the file downloads.
4. On the Sonoff device press button for 5 seconds (light pattern changes)
5. Press button again for 5secs (light pattern changes again)
6. Connect to the isteadxxxx AP using pwd 12345678
7. Browse to http://10.10.7.1
8. Enter your SSID and pwd for your network- case sensitive and hit Save
9. Wait for device to reboot
10. Find IP address of Sonoff (in your local network).
11. In the ARC in chrome send POST request WITH JSON to:

http://IPofDevice:8081/zeroconf/ota_unlock

You must send it with this JSON:

{"deviceid":"","data":{}}

12. Now send POST to URL:

http://IPofDevice:8081/zeroconf/info

with JSON:

{"deviceid":"","data":{}}

Here you should get some information returned to you. You will be able to see these two important pieces of information

deviceid: xxxxxxxxxx
otaUnlock= True

Copy the device ID and verify that otaUnlock = true.

13. Get the sha256sum of the tasmota-lite.bin file (https://emn178.github.io/online-tools/sha256_checksum.html) Copy the sha256sum

14. In the ARC in chrome send POST request WITH JSON to:

http://IPofDevice:8081/zeroconf/ota_flash

with JSON:

{
"deviceid": "INSERT COPIED DEVICE ID",
 "data": {
"downloadUrl": "http://ip/path_to_file.bin",
"sha256sum":
"INSERT COPIED SHA256SUM"
}
}

15. Wait a moment and you should see a tasmota wifi hotspot created.

JOB DONE.

[Felipetomaz]

Does Anyone know how to flash the POW R2?

Sent from my iPhone

On 18 Jun 2020, at 11:38, mattadams84 notifications@github.com wrote:

 Once you have got your head around it, its actually very simple.

Here is a simple guide to flash the Sonoff R3 Basic (not sure if it works on the mini, i have never tried). This works if your firmware is 3.5.0.

PRE-REQUISITES:

ARC plugin on Chrome (or any other REST tool) XAMPP (or any other webserver tool) tasmota-lite.bin

If your Sonoff Basic R3 is not on 3.5.0 then:

Do NOT put the jumper on, power it up. Connect to ewelink and upgrade firmware to 3.5.0 and allow it to reboot. Set up Apache server on your PC (i used XAMPP) put the tasmota-lite.bin file in the server (the file must be accessible by "http://ip/path"). You can test this works by putting the URL in your browser and see that the file downloads. On the Sonoff device press button for 5 seconds (light pattern changes) Press button again for 5secs (light pattern changes again) Connect to the isteadxxxx AP using pwd 12345678 Browse to http://10.10.7.1 Enter your SSID and pwd for your network- case sensitive and hit Save Wait for device to reboot Find IP address of Sonoff (in your local network). In the ARC in chrome send POST request WITH JSON to: http://IPofDevice:8081/zeroconf/ota_unlock

You must send it with this JSON:

{"deviceid":"","data":{}}

Now send POST to URL: http://IPofDevice:8081/zeroconf/info

with JSON:

{"deviceid":"","data":{}}

Here you should get some information returned to you. You will be able to see these two important pieces of information

deviceid: xxxxxxxxxx otaUnlock= True

Copy the device ID and verify that otaUnlock = true.

Get the sha256sum of the tasmota-lite.bin file (https://emn178.github.io/online-tools/sha256_checksum.html) Copy the sha256sum

In the ARC in chrome send POST request WITH JSON to:

http://IPofDevice:8081/zeroconf/ota_flash

with JSON:

{ "deviceid": "INSERT COPIED DEVICE ID", "data": { "downloadUrl": "http://ip/path_to_file.bin", "sha256sum": "INSERT COPIED SHA256SUM" } } Wait a moment and you should see a tasmota wifi hotspot created. JOB DONE.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[MexicoMatt]

I just wanted to add, cheers to @paul-777 I got three minis today, accidentally updated the first to 3.5 and could not get anywhere until I saw your post. I now want to confirm as well that after following your steps (10.10.7.1 and entering the WiFi details), the device showed up in the DIY tool and flashed fine. The only thing I noticed, and it happened with all three minis, in the DIY tool, after selecting the firmware, then the device, and hitting OK, the buttons greyed out but nothing happened. I then closed the pop-up (X top right) and then switched the device ON and then OFF (with the DIY tool) and then repeated the flashing process and it worked straight away. I am using a win 10 VM on Parallels on MacOS. Anyway cheers @paul-777

[vdiogo]

Cant seem to get the method described above to work:

Using a iMac I followed these steps:

1. Set up local server (http://localhost:1313) - and put the tasmota-lite.bin file in the server root
2. Paired Sonoff with Ewelink and updated it to the newest version (3.5)
3. Delete it from Ewelink.
4. Hold the button for 5 sec. until it starts to blink constantly and connect to the wifi with password: 12345678
5. Go to 10.10.7.1 and set up Sonoff with your local network
6. Find IP address of Sonoff (192.168.86.68).
7. Using Postman send POST Request to "http://192.168.86.68:8081/zeroconf/ota_unlock" to unlock with this JSON: {"deviceid":"","data":{}} Do the same with URL: "http://192.168.86.68:8081/zeroconf/ota_flash" with JSON: { "deviceid": "MY DEVICE ID", "data": { "downloadUrl": "http://http://localhost:1313/tasmota-lite.bin", "sha256sum": "7351bd4342b112326472750ad94c9551a16db313715dfc244e078f63d6d14195" } } After step 7, the device blinks three times and still has the IP previously assigned, but cannot query the FW version. After disconnecting from power, when I send POST request to "http://192.168.86.68:8081/zeroconf/info" with this JSON: {"deviceid":"","data":{}}

I get

{ "seq": 2, "error": 0, "data": { "switch": "off", "startup": "off", "pulse": "off", "pulseWidth": 500, "ssid": "MY SSID", "otaUnlock": true, "fwVersion": "3.5.0", "deviceid": "MY DEVICE ID", "bssid": "DEVICE BSSID", "signalStrength": -54 } }

Any ideas anyone?

[bluefangs]

I tried exactly as per @mattadams84 and am stuck with a similar outcome of @vdiogo

The last step does nothing. I can see thatthe tasmota device is requresting for the file a couple of times. Then nothing happens.

I started a simple python http server to serve the tasmota-lite.bin file present in ~/Downloads dir.

❯ sudo python3 -m http.server 80
Serving HTTP on 0.0.0.0 port 80 (http://0.0.0.0:80/) ...

192.168.0.226 - - [25/Jun/2020 19:55:28] "GET /Downloads/tasmota-lite.bin?deviceid=1000b6c99e&ts=182546393&sign=0f11ff70f44ed2030ccacf4792b6c7e42319ad02fc8506e8f44c8a721cc826f0 HTTP/1.1" 200 -
192.168.0.226 - - [25/Jun/2020 19:55:35] "GET /Downloads/tasmota-lite.bin?deviceid=1000b6c99e&ts=1949118330&sign=0d866949554dfc6acc0019096e95000e5680914216612080959c200914f1d52d HTTP/1.1" 200 -

After the operation completes, nothing happens. All the while, the device's blue light is blinking thrice.

UPDATE:

While the approach to flash via ARC didn't do much, I was however able to see the device on the DIY tool. From there, I proceeded to flash tasmota-lite.bin successfully.

[fabrizioromanelli]

@bluefangs I was able to do the same. You can just POST the http://IPofDevice:8081/zeroconf/ota_unlock with the correct JSON {"deviceid":"","data":{}} and then go with the DIY tool for flashing the tasmota-lite.bin.

[ekraus50]

Yes the Mini DIY Mode is a definite piece of shit. I have struggled trying to flash one with 3.5 on it and am going to get out the soldering iron. I got as far as getting it to connect to my network but thats it! Here is how far i got with http://192.168.1.113:8081/zeroconf/info. NO WHERE! I have been getting "The requested URL can't be reached" yet I am pinging the device.

[CervDotBe]

It's not that hard, put it in DIY mode. Let it connect to your network. Open up the DIY tool and it will appear and you will be able to flash it. Postman and all didn't work for me neither.

[ekraus50]

The DIY tool does not work with 3.5 and the jumper is not used.

[CervDotBe]

The DIY tool does not work with 3.5

Well, actually it does. ;-)

[ekraus50]

Serial is for me. Works no hassles.

On Monday, July 20, 2020, 9:17:20 AM EDT, CervDotBe <notifications@github.com> wrote:  

The DIY tool does not work with 3.5 and the jumper is not used.

Well, actually it does. ;-)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[bluefangs]

I follow the below steps for things to work:

1. Download and install the eweLink app
2. Turn on sonoff mini
3. In eweLink, quick pair. (I don't like it, but you have to give the app location access. At least on iOS)
4. Once the switch appears in eweLink, proceed to do the firmware update to 3.5
5. Once done, delete the device from the app and optionally uninstall the app.
6. Put the jumper on the device and turn on the device
7. You will notice a new wifi hotspot (ITEAD-*). Connect to it with password 12345678
8. Go to 10.10.7.1 and input your home's wifi name and password. Once saved, the sonoff will connect to your home wifi
9. Open the DIY tool. You will find your device listed there.
10. Flash the device with tasmota.lite.bin
11. Once flashed, the device will restart
12. You will now see a new wifi hotspot (tasmota*). It is an open wifi without a password. Connect to it
13. Go to 192.168.4.1.
14. Configure Wifi by providing your home's wifi name and password. THe device will reboot and connect to your home wifi
15. FIgure out the ip address given by your router's dhcp. Once you know the IP, proceed to further configure the device as necessary.

My only gripe with the whole process is the fact that I need to install ewelink app, and share my location. :|

[CervDotBe]

I did it via this simple way:

1. Download and install the eweLink app
2. Quick pair your device
3. Update firmware to 3.5 in the eWelink app
4. Once done, delete the device from the app
5. Put your device into DIY hotspot pairing mode, connect with a device and fill in your WLAN data (via http://10.10.7.1). It will connect to your WIFI network. No jumper needed.

If you want to install tasmota on it, continue with these instructions:

6. Download & open the DIY tool from this GIT. Open it on a computer within the same network (maybe disable your firewall to be sure), your device will appear in the list
7. Download the tasmota-lite firmware (http://thehackbox.org/tasmota/release/), install it trough the DIY tool (I used the log version)

[raffaeler]

I opened a separate issue for DIY not showing the web page. The reason is the previously programmed SSID not being reachable anymore.

[raffaeler]

@bluefangs you can avoid sharing the password of the wifi by opening a temporary WiFi (tethering) as I did. Anyway, I agree the devices should be easily upgradable without the eWeLink app.

[hellAT]

I can confirm CervDotBe way to installation- it worked exactly in that way for my Mini.

But it not for the BasicR2...(3.4.1 still). But this seems to be a different problem

[CervDotBe]

I can confirm CervDotBe way to installation- it worked exactly in that way for my Mini.

But it not for the BasicR2...(3.4.1 still). But this seems to be a different problem

Basic R2 doesn't have DIY mode.

[tonbor]

Warning, new firmware Sonoff 3.6.1. After using ARC all seems ok. Flashing with DIY tools with Tasmota 3.8 minimal all seems still to be ok. But then only wifi with id ITEAD-XXXX and address 192.168.4.1 is left no access to the mini anymore. Any one got a solution out there?

[CervDotBe]

Warning, new firmware Sonoff 3.6.1. After using ARC all seems ok. Flashing with DIY tools with Tasmota 3.8 minimal all seems still to be ok. But then only wifi with id ITEAD-XXXX and address 192.168.4.1 is left no access to the mini anymore. Any one got a solution out there?

What is your question exactly? If you flash Tasmota on your device it will broadcast a tasmota hot spot, which you should connect to. Tasmota needs configuration after installing. Just like any other WIFI IoT device.

[homeconnector]

Followed steps, and entered Sonoff Mini (FW 3.6.0) into pairing, connected to AP Wifi, and deployed tasmota-lite.bin and tried to update

curl -d '{"deviceid":"","data":{}}' http://192.168.1.96:8081/zeroconf/ota_unlock

curl -d '{"deviceid":"","data":{}}' http://192.168.1.96:8081/zeroconf/info {"seq":3,"error":0,"data":{"switch":"off","startup":"off","pulse":"off","pulseWidth":500,"ssid":"AP","otaUnlock":true,"fwVersion":"3.6.0","deviceid":"1000c88bbe","bssid":"fc:ec:da:11:b0:70","signalStrength":-72}}

test:~/Downloads$ curl -d '{ "deviceid" : "1000c88bbe","data": {"downloadUrl" : "http://test:1880/tasmota-lite.bin","sha256sum":"a6ae8f0e9dd6529989efa8a01e1a88d6bef90af2966b263d79527229128e2258"}}' http://192.168.1.96:8081/zeroconf/ota_flash

{"seq":3,"error":0}test:~/Downloads$

appreciate any help

No separate - wifi appears, a reboot shows up 3.6.0

[tonbor]

When you start up the DIY tool you should find your mini, then you can flash the tasmota-lite.bin file, see video.

[tonbor]

This looks very ok -> ":{"switch":"off","startup":"off","pulse":"off","pulseWidth":500,"ssid":"AP","otaUnlock":true,"fwVersion":"3.6.0","deviceid":"1000c88bbe","bssid":"fc:ec:da:11:b0:70","signalStrength":-72}}

[homeconnector]

When you start up the DIY tool you should find your mini, then you can flash the tasmota-lite.bin file, see video.

thanks - unfortunately DIY Tool - isn't finding the device. Also when it boots up - it shows the firmware (Sonoff 3.6)

[tonbor]

That is correct sonoff 3.6, only after flashing you will find tasmota. What wifi name is the mini showing?

[tonbor]

By the way is the mini connected to the same network else the diy tool will not find it.