I had the same problem with this FW as I do with 6.4.1. Intermittent loss of connection and outright loss of connection to some Gen 1 (sonoff basic) devices.
You do not need to erase / reflash. That procedure is only for people encountering connection issues.
Doing the reset and OTA flash was listed as a supported way to fix in the Wiki originally… It certainly worked ok for me. A lot of people have issues with having to get devices out of nasty places and using a wire to reflash is not practical (or necessary)
There are issues with Fritzbox and mesh networks with 2.3.0 core and 6.3 firmware.
I’m sorry but I’m having trouble following this thread 
I have one sonoff on 6.4.1 one on 6.3 (all the rest are on 6.2.1)
Can I downgrade these two OTA to 6.2.1 or not?
If not is it possible to downgrade using a wire and keep all current settings?
I have only ever flashed from factory, or done an OTA upgrade (using minimal first)
This is essentially the modification I did, using some low cost high-ish gain wifi antenna that is designed for 2.4Ghz
Maybe I’m luck because I have about 5 sonoffs basic still running 5.14.0 and I didnt bothered to upgrade as it just work :-). There’s one that used to disconnect but the wifi signal on that area was weak and the sonoff is inside a fixture. Problem solved when I upgraded my home wifi with a pair of unifi.
Yes you can. If you need to. If they aren’t having disconnection problems there is no point.
Agree with Tom.
I am using a Fritz mesh which is the main reason I wanted to use arduino core 2.5.0. I only fairly recently implemented the mesh as I was previously using a repeater on a different SSID. I had an issue with one sonoff connected to the mesh repeater with it not connecting to WiFi for hours during the night and just flashing in my bedroom till I turned it off. Turned it on the next morning and it started flashing again until I connected to the wifi in the sonoff on my phone and it abruptly connected to the mesh again immediately. I just can’t remember what version of core I was using then. I think this is why I have been compiling new tasmota all the time since 6.4.x trying to find stability again. I get maybe 4 or 5 disconnections from the broker for less than a second every day so it has not caused any error in the performance yet.
As it happens I flashed with a wire for the first time a new SOnoff SV yesterday with the same firmware I put on my other SOnoffs and it is doing exactly the same behaviour so it’s not a flashing OTA issue that I can see.
Last Sunday I prepared 3 exactly the same Sonoff Basic devices with 3 different Sonoff-Tasmota firmwares, see below for the details. Today I see a big difference between the firmware based on the new 2.5.0/3.0.0 dev core and the current firmware based on the 2.4.2/2.2.1 core, in favor of the newest firmware.
Although all firmware’s show disconnections in the HA history, the 6.4.1 with the 2.4.2 core/2.2.1 SDK shows over a ten times more disconnections.
During the measurement (24 hours) the 3 Sonoff basic devices were placed next to each other less than 4 meters away from the WIFI access point.
Erased flash using:
[esptool-2.6]$ esptool.py --port /dev/ttyUSB0 erase_flash
esptool.py v2.6
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP8266
Chip is ESP8285
Features: WiFi, Embedded Flash
MAC: dc:4f:22:d3:63:14
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 4.3s
Hard resetting via RTS pin...
And then installed 6.4.1.9 using serial:
(builded myself from latest development source using VSCODE + PlatformIO plugin on Fedora Linux)
Sonoff Basic Module
basic1
Program Version 6.4.1.9(sonoff)
Build Date & Time 2019-01-20T16:23:56
Core/SDK Version STAGE/3.0.0-dev(c0f7b44)
Uptime 2T01:17:00
Flash write Count 12 at 0xF8000
21 disconnects:
Sonoff Basic Module
basic2
Program Version 6.4.1.9(b5824fc-sonoff)
Build Date & Time 2019-01-18T12:13:06
Core/SDK Version 2_5_0_BETA2/3.0.0-dev(c0f7b44)
Uptime 2T1:30:09
Flash write Count 8 at 0xFB000
17 disconnects:
(builded myself from the 6.4.1 release, using VSCODE + PlatformIO plugin on Fedora Linux)
Sonoff Basic Module
basic3
Program Version 6.4.1(sonoff)
Build Date & Time 2018-12-24T14:41:00
Core/SDK Version 2_4_2/2.2.1(cfd48f3)
Uptime 2T02:11:24
Flash write Count 43 at 0xF9000
Over 200 disconnects (very hard to see, so zoom in):
I found this difference in disconnects quite remarkable. Has any one tested this too?
Sorry, but I did not test with the older firmware’s.
the newest dev firmware work much better than the current 6.4.1 release with the 2.4.2core and 2.2.1 SDK.
You should compare to 6.2.1. No need to erase and it can be done OTA. I get no disconnects with this version.
I have no real issues with Tasmota flashed Sonoffs other than that they do not automatically seem to reconnect to WiFi whenever the AP goes down.
I have 2 Sonoff Dual R2s, flashed with Tasmota classic, connected to Ubiquiti Unifi AP-AC-PRO. Whenever I upgrade the firmware of the AP, the AP is down for about a minute. I have to power cycle the Sonoffs to get them connect to Wifi again. My Sonoffs are easily accessible, so not a big deal, but still…
So 2.5.0beta3 core was released a few days ago - worse that 2.4.2 for me and worse than beta2.
So I’ve surrendered and compiled 6.4.1.12 with 2.3.0 core (that I was using default 6.3.x before the debacle of 6.4.x and 2.4.2 core)
Even though I have a FritzBox and run a Mesh WiFi I have not had a single dropout for about 4 hours now… I do wonder how this can be so screwed up!
Any chance you could make the binary file available?
Yes. It’s totally a minimal binary (by minimal I don’t mean the sonoff-minimal - just it doesn’t have all the devices etc - it’s the full firmware) as I only have Sonoff SV’s and Basic Sonoffs (S22’s).
Not sure if this was mentioned below. If so, I apologize.
You can use latest pre compiled 2.3.0 Tasmota version via OTA using this link:
http://thehackbox.org/tasmota/release/020300/sonoff.bin
had quite a few sonoffs showing this behavior - disconnecting like crazy.
Flashed OTA with 2.3.0 and they are back to normal.
Latest version of tasmota with the 2.3.0 core?
6.2.1 I think.
yes, it’s just an older core version. tasmota itself is up to date.
I am on v6.6 and is having allot of problems with Wifi
Could anyone share a bin file that they have some good experience with?
