Tasmota: OTA upgrade to 6.1.0 fails with blinking green light on Sonoff Basic

[apastuszak]

Just did an OTA upgrade 6.1.0. Flashing Sonoff-minimal.bin worked just fine. But when I upgraded to Sonoff.bin after that, I am getting a flashing green light. When I go into my wifi settings, I see that WIFI_MANAGER has kicked in and the Sonoff has it's own network up and running, but I am unable to connect to this network. and reconfigure the device.

[apastuszak]

Held the button down for 40 seconds to completely reset Tasmota, Rebooted and now I am not able to see a wifi network at all to connect to. I pressed the button 4 times to start up wifi_manager. Light starts to blink. No wifi network I can connect to.

Pressee button 3 times to put it in Smart Config. Used ESP8266 Smart Config. Keeps failing. Not sure how to bring this thing back to life without taking it apart and using a USB to serial adapter.

[maciboy]

Every update is a nightmare :D
I'm experiencing just the same with both of my Basics.
One was working correctly just after the update but failed a few minutes later.
Unluckily, in that time I thought updating my second Basic seems to be safe...

So, now both Basics are "running" 6.1.0, but both are in that loop you're mentioning. They neither connected to the existing wifi, nor they are reachable after a reset...

[Jason2866]

Miration Path correct? You have to care for that!

[maciboy]

Was coming from 5.14., so I don't think the migration path is the issue, or am I wrong?

[apastuszak]

I was on 5.14.

My 5,13 to 5.14 upgrade caused the same issue and I need to flash over serial.

[Jason2866]

Well, when 40 seconds button pressing reset doesnt help, there is just one way left
-> Clean reflashing. To be sure everything is erased do a erase with esptool first.
I did a upgrade from 5.14 to 6.1.0a (self compiled) with no problem and it is rock solid

[chriskmn]

I also had issues with one of my 20 devices. The one with the problem was based on core 2.4.1. May be that could make a difference !?

[Jason2866]

@chriskmn I never had a version with v.2.4.0 or 2.4.1 i tried, that was reliable. I always got minor or major problems with every version (starting from Tasmota v.5.0.x). For me only (is and was) V.2.3.0 is rock solid!!

[maciboy]

So, if 2.4.x is problematic, why is the precompiled binary not based in 2.3.0 :( It would help unexperienced users, like me, very much.
For me every update is pain, since chances are very high that afterwards the Basics are broken - like it is the case now for both of mine.

[chriskmn]

Thanks Jason, I‘ll stay with 2.3.0 also now.

[Jason2866]

@maciboy the precompiled version 6.x are based on core 2.3.0
This is a result of experiences users made.

[chriskmn]

@maciboy: Until now I never had issues with the basics. My problem occured on a 4ch pro. May be there are other factors on the basic. Are they switched on while you are updating ? I know that the ESP8266 are very sensitive on supply power. A microwave could make trouble or even a bad AC adaptor somewhere on the powerline.....

[apastuszak]

Used ESPtool to erase flash. Flashed the pre-compiled binary from the Github. Came up on it's own network. I connected and configured for my wifi. Rebooted the device. It did NOT connect to my wifi, but instead came up on it's own network under the new hostname I gave it. Connected. Reconfigured Wifi, even though it looked right. Device restarted and did not connect to my wifi and now will not go into Wifi Manager mode.

Now it's just blinking for about a minute, then goes solid, then the device seems to reboot and start blinking again.

[maciboy]

@apastuszak
Thats exactlly what I‘m experiencing as well.
No chance for a connection to the exisiting wifi. They just span up their own wifi, with the given hostname. Connecting to that wifi is nearly impossible, just worked once out of a dozen of tries.

@Jason2866 Then it seems that neither the core version, nor the migration path is the issue...

[apastuszak]

@maciboy I'll putting 5.14 back on it and just leaving it alone for now. Can I ask what kind of router you're using and what kind of firmware is on it?

[maciboy]

That‘s how it looked on my router.
The Sonoff connected to the wifi but 20 seconds later, it got disconnected.
This pattern is repeated after every reboot.

Because of this, I resetted both using the 40s button press.

Once I was able to connect to the established wifi, entered the credentials, but it did not help.

My router is a FritzBox 7490, firmware is 6.93

[apastuszak]

@maciboy Does your router do both 2.4 Ghz and 5 Ghz and are both of these networks named the same?

[maciboy]

Yes, 2.4 and 5 GHz have the same name

[apastuszak]

That's the same configuration I have. I wonder if that may be the issue here. Just strange that 6.1.0 minimal works without any issues.

[reloxx13]

just disable 5ghz and test it, but yep, 5ghz can make problems if both have the same name.

[Jason2866]

Esp is a 2.4Ghz only device. I use 2.4 Ghz and 5 Ghz at the same time on my Accesspoints (Lancom and Bintec-elmeg). No problem. SSID is the same for all just different channels
@reloxx13 How should a frequency (5 Ghz) that the ESP isnt capable make problems?
Or is this problem Fritzbox related?

[apastuszak]

Just reverted to 5.14.0 using ESPtool and all my problems are now gone. Wifi works great.

[apastuszak]

@reloxx13 If I do that, I will have two teenage boys scream at me that their Xboxes suddenly stopped working.

[chriskmn]

Did you try this:

In the user_config.h, find the option CFG_Holder and change from #define CFG_HOLDER 4617 to #define CFG_HOLDER 4618. Result: it works flawlessly as it should. connects instant to the wifi, no more problems.

???

5.14.0 has another format of that constant. So may be that somehow messes up the config

5.14.0: #define CFG_HOLDER 0x20161209

[apastuszak]

What does that setting do? Why isn't it the default in the pre-compiled
binary?

On Tue, Jul 10, 2018 at 2:17 PM Chris [e-mail] wrote:

Did you try this:

In the user_config.h, find the option CFG_Holder and change from #define
CFG_HOLDER 4617 to #define CFG_HOLDER 4618. Result: it works flawlessly as
it should. connects instant to the wifi, no more problems.

???

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/3177#issuecomment-403918363,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADPlXpdoaUjnz5TqHoqK20EP2SyRv5H-ks5uFO_TgaJpZM4VJUOc
.

[Jason2866]

@chriskmn
changing cfg_holder deletes every stored setting in the device to defaults in user_config.h.
Overflashing with unchanged cfg_holder keeps stored settings in device.
So in your case bad settings where stored in device and reused...

[maciboy]

But shouldn‘t the 40sec reset do the same and set back all values to default?

[Jason2866]

@maciboy yes holding button for 40 sec. should reset device to defaults (user_config.h)

[chriskmn]

@Jason2866: yes, that‘s how I understood it as well. So if you flash a new FW without changing cfg holder, that FW uses the stored config from device.

If it is changed (like from 5.14.0 to 6.1.0) FW uses NOT the config from the device ?!
And if there is a mistake in the config of the binaries there might be issues with connecting after flashing.....

[Jason2866]

@chriskmn
Function of CFG_HOLDER is not changed by design in latest version.
If behaviour really changed it is a bug

[chriskmn]

Question might be how people migrate there user_config.h from version to version. Just copy-paste might lead to issues. I am always changing the newer config line by line in comparism with the old config - very cautiously.

[reloxx13]

user_config_override

[apastuszak]

I used ESPtool to erase flash and then to flash 6.1.0. That still gave
issues. Should not an ESPTools Erase Flash not have done the same as the
CFG_HOLDER setting?

On Tue, Jul 10, 2018 at 3:03 PM reloxx13 [e-mail] wrote:

user_config_override

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/3177#issuecomment-403931781,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADPlXkMF7IgfqXHPCOSVJxEX0kgEZOmZks5uFPqegaJpZM4VJUOc
.

[chriskmn]

What happens if you tell the FW to use flash config - but you deleted it ? ;)

So if flash is empty you MUST change cfg-holder.

Or am I wrong on this?

I think that‘s the reason why you should erease only sketch when flashing:

[Jason2866]

@apastuszak
Erasing flash with Esptool is the secure way to wipe out the whole flash.
With this 100% nothing is left:
esptool --port COM5 --baud 115200 erase_flash

[Jason2866]

@chriskmn
Dont use Arduino core 2.4.1 or 2.4.0 if you have wifi issues. This 2 versions are known to make problems
Your Arduino Hardcopy suggest that you use it.
I dont use Arduino IDE anymore, it is not a good tool for bigger projects like Tasmota.
Using Platformio or VSC is so much simplier and hassle free. Well preconfigured platformio.ini from @arendst in project included and you dont have to do any setting things

[chriskmn]

@Jason2866: it was just a copy from the wiki. I am back on 2.3.0. but thanks for the advice. I was also looking on platformio.

[apastuszak]

@Jason2866 That's what I did before I installed 6.1.0. Still had Wifi issues.

[chriskmn]

@apastuszak: if you did not change cfg-holder you have a corrupted configuration.

[maciboy]

So, I connected one of the Basics to my Pi (https://github.com/arendst/Sonoff-Tasmota/wiki/Flash-Sonoff-using-Raspberry-Pi)

Thats how the output looks:
`00:00:00 Project sonoff Sonoff (Topic sonoff, Fallback DVES_4F743F, GroupTopic sonoffs) Version 6.1.0-2_3_0
00:00:00 WIF: Connecting to AP1 xxxx in mode 11N as sonoff-5183...
00:00:25 WIF: Connect failed with AP timeout
00:00:26 WIF: Connecting to AP1 xxxx in mode 11N as sonoff-5183...
00:00:50 WIF: Connect failed with AP timeout
00:00:50 WIF: WPSConfig active for 3 minutes
00:01:11 APP: Restarting

ets Jan 8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3fff3888
~ld

00:00:00 Project sonoff Sonoff (Topic sonoff, Fallback DVES_4F743F, GroupTopic sonoffs) Version 6.1.0-2_3_0
00:00:00 WIF: Connecting to AP1 xxxx in mode 11N as sonoff-5183...
00:00:25 WIF: Connect failed with AP timeout
00:00:26 WIF: Connecting to AP1 xxxx in mode 11N as sonoff-5183...
`

In my router I can see, as shown yesterday, that the Sonoff connects for around 20 seconds...

(Also strange that it says 3 minutes in WPSConfig, but reboots after not even 2 minutes)

[apastuszak]

@chriskmn Even if I used esptool to erase_flash, I'm still going to have a corrupt configuration? How is that possible?

[maciboy]

@apastuszak We will see now, I just erase-flashed the Basic and will flash 6.1.0 now. I'm curious if it will work or if I end up like you did

[arendst]

@maciboy while in the serial interface and still waiting for your ap execute the following commands:

seriallog 3
status 0

and provide the output here pls.

[maciboy]

It's alive with 6.1.0 👍 (after 2x flash erase to make sure it is really erased :D)

[apastuszak]

If I backup my config from 5.1.4, can I restore the same config on 6.1.0?

[maciboy]

That's at least what the 'Migration path' wiki says ;)

[arendst]

If you already have problems with your config I would say forget a restore and re-config after uploading 6.1.0.

Moving from a higher version back to a lower version will corrupt the config so that is probably what you did already...

[apastuszak]

@arendst So, do you think that's the issue? The config is working in 5.1.4, but is corrupt? So when I upgrade, it goes FUBAR?

I'll compile 6.1.0 with CFG_HOLDER set to erase config and do an OTA. I assume sonoff_minimal doesn't read the config and that's why it's working?

[arendst]

Minimal still reads the config but it doesn't update the config.

Most released versions will shuffle the config around a bit to accommodate new functionality. The minimal version does not do this shuffle as it doesn't update the config.

For background info look in file settings.ino at the bottom where you see all changes to be made when moving up from previous versions to the latest.

[maciboy]

@arendst
Now I connected the second Basic, which also didn't made the update from 5.14 to 6.1 successfully.

Here is the output you asked for:

seriallog 3
00:02:44 CMD: seriallog 3
00:02:44 SRC: Serial
00:02:44 RSL: Group 0, Index 1, Command SERIALLOG, Data 3
00:02:44 RSL: stat/sonoff/RESULT = {"SerialLog":"3 (Active 3)"}
status 0
00:02:54 CMD: status 0
00:02:54 SRC: Serial
00:02:54 RSL: Group 0, Index 1, Command STATUS, Data 0
00:02:54 RSL: stat/sonoff/STATUS = {"Status":{"Module":1,"FriendlyName":["Sonoff"],"Topic":"sonoff","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"SaveData":1,"SaveState":1,"ButtonRetain":0,"PowerRetain":0}}
00:02:54 RSL: stat/sonoff/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://sonoff.maddox.co.uk/tasmota/sonoff.bin","RestartReason":"Software/System restart","Uptime":"0T00:02:53","StartupUTC":"","Sleep":0,"BootCount":30,"SaveCount":43,"SaveAddress":"F9000"}}
00:02:54 RSL: stat/sonoff/STATUS2 = {"StatusFWR":{"Version":"6.1.0","BuildDateTime":"2018-07-06T21:01:47","Boot":31,"Core":"2_3_0","SDK":"1.5.3(aec24ac9)"}}
00:02:54 RSL: stat/sonoff/STATUS3 = {"StatusLOG":{"SerialLog":3,"WebLog":2,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["ZuHauseLan",""],"TelePeriod":300,"SetOption":["00008009","55818000"]}}
00:02:54 RSL: stat/sonoff/STATUS4 = {"StatusMEM":{"ProgramSize":535,"Free":468,"Heap":18,"ProgramFlashSize":1024,"FlashSize":1024,"FlashMode":3,"Features":["00000809","0FDAE794","0C000000","23B6179E","00000000"]}}
00:02:54 RSL: stat/sonoff/STATUS5 = {"StatusNET":{"Hostname":"sonoff-1172","IPAddress":"0.0.0.0","Gateway":"192.168.2.254","Subnetmask":"255.255.255.0","DNSServer":"192.168.2.27","Mac":"2C:3A:E8:4F:A4:94","Webserver":2,"WifiConfig":2}}
00:02:54 RSL: stat/sonoff/STATUS6 = {"StatusMQT":{"MqttHost":"","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_4FA494","MqttUser":"DVES_USER","MqttType":1,"MAX_PACKET_SIZE":1000,"KEEPALIVE":15}}
00:02:54 RSL: stat/sonoff/STATUS7 = {"StatusTIM":{"UTC":"Thu Jan 01 00:02:54 1970","Local":"Thu Jan 01 00:02:54 1970","StartDST":"Thu Jan 01 00:00:00 1970","EndDST":"Thu Jan 01 00:00:00 1970","Timezone":1,"Sunrise":"07:43","Sunset":"16:03"}}
00:02:54 RSL: stat/sonoff/STATUS10 = {"StatusSNS":{"Time":"1970-01-01T00:02:54"}}
00:02:54 RSL: stat/sonoff/STATUS11 = {"StatusSTS":{"Time":"1970-01-01T00:02:54","Uptime":"0T00:02:53","Vcc":3.103,"POWER":"OFF","Wifi":{"AP":1,"SSId":"ZuHauseLan","RSSI":100,"APMac":"FF:FF:FF:FF:FF:FF"}}}

[maciboy]

Log from connection attempt:

00:00:00 Project sonoff Sonoff (Topic sonoff, Fallback DVES_4FA494, GroupTopic sonoffs) Version 6.1.0-2_3_0
00:00:00 CFG: Saved to flash at F8, Count 44, Bytes 3584
00:00:00 WIF: Attempting connection...
00:00:00 WIF: Patch issue 2186
00:00:00 WIF: Connecting to AP1 ZuHauseLan in mode 11N as sonoff-1172...
00:00:01 WIF: Attempting connection...
00:00:02 WIF: Attempting connection...
00:00:03 WIF: Attempting connection...
00:00:04 WIF: Attempting connection...
00:00:05 WIF: Attempting connection...
00:00:06 WIF: Attempting connection...
00:00:07 WIF: Attempting connection...
00:00:08 WIF: Attempting connection...
00:00:09 WIF: Attempting connection...
00:00:10 WIF: Attempting connection...
00:00:11 WIF: Attempting connection...
00:00:12 WIF: Attempting connection...
00:00:13 WIF: Attempting connection...
00:00:14 WIF: Connect failed with AP timeout
00:00:14 WIF: Patch issue 2186
00:00:15 WIF: Connecting to AP1 ZuHauseLan in mode 11N as sonoff-1172...
00:00:15 WIF: Attempting connection...
00:00:16 WIF: Attempting connection...
00:00:17 WIF: Attempting connection...
00:00:18 WIF: Attempting connection...
00:00:19 WIF: Attempting connection...
00:00:20 WIF: Attempting connection...
00:00:21 WIF: Attempting connection...
00:00:22 WIF: Attempting connection...
00:00:23 WIF: Attempting connection...
00:00:24 WIF: Attempting connection...
00:00:25 WIF: Attempting connection...
00:00:26 WIF: Attempting connection...
00:00:27 WIF: Attempting connection...
00:00:28 WIF: Connect failed with AP timeout
00:00:28 WIF: WifiManager active for 3 minutes
00:00:28 WIF: Wifimanager set AccessPoint
00:00:29 HTP: Web server active on sonoff-1172 with IP address 192.168.4.1

Seems identical to https://github.com/arendst/Sonoff-Tasmota/issues/3150

[arendst]

try command reset 3 pls

[maciboy]

Still several lines of "Attempting connection"

[apastuszak]

@arendst I have a Sonoff Basic still in box with Tasmota on it. If I do a flash upgrade and it fails, I could mail it to you to look at.

[arendst]

@maciboy OK. Try the flash erase as you did before and report back.

@apastuszak Try the flash update. If it fails do the flash erase and try again.

[maciboy]

@arendst
No.2 seems to be fine, at least the console output says it's connected to wifi after this clean flashing

Can confirm, toggling via HomeKit is working

[apastuszak]

Ok, strategy question:

Can I update to sonoff_minimal.bin with CFG_HOLDER set to 4617 and then flash sonoff.bin with CFG_HOLDER set to 4618?

That will make it much easier to find on the network to do the full upgrade.

[arendst]

Should work as the minimal doesn't write config updates.

[apastuszak]

OK, let me go test.

[apastuszak]

Hard coded my wifi userID and password into the user_config.h. Compiled sonoff_minimal.bin using CFG_HOLDER set to 4617. Device has sonoff_minimal.bin on it and is now sitting there with a blinking green light.

My wifi password has special characters in it, specifically an exclamation mark. Could that be causing any problems?

[reloxx13]

My wifi password has special characters in it, specifically an exclamation mark. Could that be causing any problems?

instead of asking you could just change it or make a guest wifi or hotspot with ur mobile and try it.

yes, special chars are not supported or leading to problems

also that's why there is a "did you read the wiki checkbox" on new issues.

https://github.com/arendst/Sonoff-Tasmota/wiki/Troubleshooting#wifi-does-not-connect

[apastuszak]

Was working fine on 5.13 and 5.14. I could change it, but then I need to reconfigure every wireless device in my house. I guess I get to have some fun doing that tonight.

[jjlawren]

I have a wifi password with multiple special chars. Haven't had any issues using it on 5.13, 5.14, or with non-Basics (S20 & POW) on 6.1.0. Only the Basics have been giving me issues connecting to wifi after upgrading to 6.1.0.

[apastuszak]

Don't all these devices use the same ESP8266? Maybe changing the type to somthing other than basic and then trying an upgrade?

[maciboy]

Fu** it :(
I just packed away all the flashing stuff, attached the Sonoffs back to their wires...
The whole time the connection was ok, now again unreachable with my router showing this:

It's like those switches are kiding me. They waited for me to feel on the safe side, now they act-up again 😢

[maciboy]

@arendst @ascillato
Any idea what could cause Tasmota to start having issues with the wifi after some time?
It was the case during my initial update 2 days ago, when the first Basic was up and running 6.1.0, which made me flash the second Basic. Afterwards both were dead.
Now, again I have two one dead Basics, which both were was functioning well right after the update...

Does the firmware degenerate over time? 😆

Update: for now only one of the Basics is stuck in the connection-attempt loop...

[ascillato]

Hi,

Sorry, but I have no clue why is happening that with your router and your Sonoffs Basics. In my case my sonoffs are not doing that with the last firmware. Sorry, I have no idea.

[apastuszak]

My router is running dd-wrt. Anyone else running that?

Andy

On Wed, Jul 11, 2018 at 2:53 PM Adrian Scillato [e-mail]
wrote:

Hi,

Sorry, but I have no clue why is happening that with your router and your
Sonoffs Basics. In my case my sonoffs are not doing that with the last
firmware. Sorry, I have no idea.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/3177#issuecomment-404273948,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADPlXll5OYBQnHyrDLcxap3husv7T0Aqks5uFkmVgaJpZM4VJUOc
.

[maciboy]

Ok, mega weird: both Basics are connected again. I've changed: nothing

So Andy, give it a try, I'm curious what will happen with your Basics and 6.1.0 ;)

[apastuszak]

Still down. It's been blinkig, blinking and then rebooting and doing it
all over again. I'll need to flash over serial.

On Wed, Jul 11, 2018 at 3:23 PM maciboy [e-mail] wrote:

Ok, mega weird: both Basics are connected again. I've changed: nothing

So Andy, give it a try, I'm curious what will happen with your Basics and
6.1.0 ;)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/3177#issuecomment-404282408,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADPlXhiSjmlfZkfkb_U8gG85xGYN0tBDks5uFlC6gaJpZM4VJUOc
.

[jjlawren]

Ok, mega weird: both Basics are connected again. I've changed: nothing

Were they disconnected from power for a period of time?

[maciboy]

Mmh, the fuse was deactivated during the installation.
Between the reappearance of the connection-attempt-issue and the magical wifi-reconnection the power was not disconnected. I didn't even pushed the button a single time.

[apastuszak]

@maciboy What do you mean the fuse was deactivated?

On Wed, Jul 11, 2018 at 3:31 PM maciboy [e-mail] wrote:

Mmh, the fuse was deactivated during the installation.
Between the reappearance of the connection-attempt-issue and the magical
wifi-reconnection the power was not disconnected. I didn't even pushed the
button a single time.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/3177#issuecomment-404284541,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADPlXi94wl-xmZReD3oOO3EW6hYPRaqrks5uFlKTgaJpZM4VJUOc
.

[maciboy]

@apastuszak
I cut the power from the power sockets by deactivating the fuse in the power distribution board

[chriskmn]

Well, no I‘m in trouble. After updating all my 22 devices to 6.1.0 one by one is getting offline and trying to flash back to 5.12 puts them into „blinking mode“. This is really pain in the ass, as I have some hard-wired devices in my electric installation and it seems that I have to take them all out and flash them by serial interface :(((((((((

[maciboy]

Yes, 6.1.0 is like a lottery :D After posting yesterday, that both of mine got magically connected again, they disconnected some time later.
This morning one was connected again, which according to the router log happened at 5am, so it took 5h of connection attempts.
However, that connection did not last until now - it's disconnected again.
Basically, I could write a status update every several hours, but then this thread would be even more crowded and flooded by my "connected - disconnected - connected - disconnected - ..." posts :DD

To sum up, 6.1.0 seems unreliable, no matter how it got flashed and wifi connections are not stable over longer periods of time.

[chriskmn]

Totally agree! It would make sense to somehow take out of the release to beware others of deep trouble ....

[chriskmn]

I figured out a way to safely downgrade by OTA update:

• at 5.x: CFG_HOLDER 1
• bring all the config values (wifi, mqtt etc) to the individual device settings
• compile and copy the binary as „sonoff.bin“ on your OTA server
• compile a second .bin with #define BE_MINIMAL
• copy that file as „sonoff-minimal.bin“ on your OTA server

upgrade the device via web interface

[apastuszak]

@maciboy Can you tell me what revision of the Basic you have? It should say it in the corner of the board. The one I have that says TH_1.1 went to 6.1.0 via OTA without issue going minimal->full. The one that says Sonoff Basic R2 v 1.0 10-11-2017 is the one giving me all the problems.

[apastuszak]

Check out:

https://github.com/arendst/Sonoff-Tasmota/issues/3150

for more details.

[donoo]

I got the latest ifan2 module and I tried to update it with Tasmota using SonOTA. I used all default config and it was updated to 5.x.x version. It connected to wifi fine and everything was fine. Module was set to Sonoff Basic.
After that I used the update option from menu. I tried to update to latest version 6.1.0 to add ifan2 support. The update failed and after the device was restarted it is not connecting to wifi nor I m able to reset it using 40 sec reset option. Also it is not broadcasting its own wifi access point.
Remote is also not working. When I click the wifi button on remote one single beep is played. Not sure how to reset it now?
Anyone faced similar issue to update to 6.1.0 or know how to reset without soldering it?
Thanks in advance!

[chriskmn]

I gave it another try and disabled mDNS feature and used the ntp server of my router. Until now I don‘t have any reconnects or connection issues.

[Jason2866]

@chriskmn
Maybe mDNS cause issues, i remember long time ago i had problems with that.
I dont need it so i disable it always.

[chriskmn]

Ok, did not know that. With mDNS active i get this behavior:

8:30:59 DNS: Initialized
08:31:00 MQT: Attempting connection...
08:31:00 MQT: Connected
08:31:00 MQT: tele/sonoff-19/LWT = Online (retained)
08:31:00 MQT: cmnd/sonoff-19/POWER =
08:32:19 DNS: Initialized
08:32:20 MQT: Attempting connection...
08:32:20 MQT: Connected
08:32:20 MQT: tele/sonoff-19/LWT = Online (retained)
08:32:20 MQT: cmnd/sonoff-19/POWER =
08:33:35 MQT: Attempting connection...
08:33:35 MQT: Connected
08:33:35 MQT: tele/sonoff-19/LWT = Online (retained)
08:33:35 MQT: cmnd/sonoff-19/POWER =
08:34:35 MQT: Attempting connection...
08:34:35 MQT: Connected
08:34:35 MQT: tele/sonoff-19/LWT = Online (retained)
08:34:35 MQT: cmnd/sonoff-19/POWER =
08:36:50 DNS: Initialized
08:36:51 MQT: Attempting connection...
08:36:51 MQT: Connected
08:36:51 MQT: tele/sonoff-19/LWT = Online (retained)
08:36:51 MQT: cmnd/sonoff-19/POWER =

[Jason2866]

@chriskmn
If you disable mDNS it is fine? If yes you found a solution maybe for manys 👍

[maciboy]

I will give it a try :)
What are the downsides of deactivating mDNS?

[Jason2866]

@maciboy
You have to know the IP address if you want to open the Webfrontend -> no friendly name to enter in browser

[maciboy]

Ok that‘s not an issue, since access for me is much faster, when I enter the IP. When entering the hostname, connection setup takes somehow much longer.
Can you give me a hint, where the mDNS setting is hidden, just now I was too blind to find it :D

[Jason2866]

In user_config.h:
`// -- mDNS ----------------------------------------

define USE_DISCOVERY // Enable mDNS for the following services (+8k code, +0.3k mem)

#define WEBSERVER_ADVERTISE // Provide access to webserver by name .local/

`

[maciboy]

No way to do it through the UI or console, without reflashing? 😕

[chriskmn]

No you have to reflash :(

[chriskmn]

@Jason2866: yes, I disabled mDNS and entered IP numbers for the ntp servers. until now everything is fine.

What I also did is „resetting“ cdg_holder to it‘s original value of 4617 to be able to flash upcoming versions without the need to reconfigure everything again.

[Jason2866]

@chriskmn
I have disabled mDNS and i use names for NTP servers. No Problem. The name resolve is done by my router. So no need for that.

[chriskmn]

Are you all using core 2.3.0?

[Jason2866]

I do!

[chriskmn]

I used 2.4.0 but now also back to 2.3.0

[chriskmn]

I just saw in the web console, that one device somehow connected to the weaker wifi signal of my two routers. In conseuqence it was not able to connect to the mqtt broker....
I thought the ESP‘s are using the stronger wifi signal. May be I should use different ssid names on my two routers. Or should they use the same channel ?

I never had that issues before.

[TasmotaFan]

Dear all,
I am new in this forum. I have the same trouble described above.
I use some sonoff basic and some POW. With sonata I was not happy because it works only with old firmware from sonoff. So I got a serial USB link and flash the firmware with ESP8266Flasher.
I flashed first sonoff-DE 5.13.1.bin (this has core 2.4.0) . After restart i use WPS to set my WLAN name and password.
Later i made a firmware update by the integrated webserver to sonoff-minimal 5.14 and sonoff-DE 5.14 (this has core 2.3.0)
Up to here everything works fine for me
Then I try to update the firmware to 6.1.0 by the webserver (first the minimal and then the -DE)
But this software cannot connect to my WIFI, always falls back to WPS mode but never connects.
The same problem is with version 6.1.1
As result I stay on 5.14 but need first flash 5.13.1 and than upgrade to 5.14.
I hope this long report will help other user to recover and the developers to find a solution.
I have to thank the developers for this fantastic software, I cannot imagine how long it took to build it.
I think it is really very complex to manage this versatile thing for all the different applications.
One idea: does it make sense to set the WIFI name and password by the terminal interface to come easy to the websever?
Good luck

[arendst]

You could and can always enter any parameter via the serial terminal.

So to set both ssid and password in one go you would enter:
backlog ssid your-router; password1 your-password; ssid2 your-other-router; password2 your-password

The device will update the parameters, restart and hopefully connect to one of your routers ;-)

[apastuszak]

The thing that continues to work for me on my Sonoff Basic R2 swtches is to use Arduino Core 2.4.1. I have R2 sitting on my desk here. I tried to upgrade to 6.1.1 using the minimal->sonoff.bin path. Minimal came up on the wifi. When I OTA flashed sonoff.bin, it failed to connect and I got a flashing green light, and WIFI_MANAGER never showed an access point I could connect to.

Flashing 6.1.0 back on the device, compiled with Arduino Core 2.4.1 worked right after a reboot. Came right up in WIFI_MANAGER. I connected, configured, and am up and running now.

[chriskmn]

May be a dumb question, but did you also update the new libraries when you switched from 5.x to 6.x ?

btw. I did not realize that there is a 6.1.1 out with referral to this thread......

[apastuszak]

@TasmotaFan Can you compile it your self and try to use 2.4.1. I'm curious if that will fix your problem, like it did mine.

[TasmotaFan]

@arendst thanks for the info, ill try that later. Even the minimal- 5.14 did not always connect to my WIFI althoug ssid is seen in the terminal log.

@apastuszak I'm sorry, I have no IDE installed, I use the released bin files

[chriskmn]

may be you should first enter the correct mqtt settings before you connect to your wifi network. with the standard MQTT lib there should be issues if MQTT broker is not reachable.

I switched to MQTT tasmota

[apastuszak]

@TasmotaFan I can compile one and provide a link. Give me a few minutes.

[TasmotaFan]

btw: I have MQTT disabled in the Webserver UI.

[apastuszak]

@TasmotaFan
I compiled 6.1.0 with Arduino Core 2.4.1 - sonoff-minimal.bin and sonoff-DE.bin.

https://drive.google.com/drive/folders/1Mr369jUIHXYAeHP0jAuxqNe-uwMiBrgo

If anyone else wants another language to test, please let me know, I'll be happy to add it.

[Jason2866]

@apastuszak you can upload files here to ;-)

[maciboy]

I was brave enough now to flash apastuszak's compiled minimal.bin directly onto by basic with 6.1.0+2.3.0...
Was a mistake, now it is stuck blinking with this minimal bin :/

[apastuszak]

6.1.0 compiled with 2.4.1.zip

[apastuszak]

@maciboy I did a serial flash of 5.1.4 binaries from Github and was able to do an OTA upgrade to 6.1.0 using the binaries I compiled on Arduino Core 2.4.1. I wonder if we have an issue with the R2 needing 2.4.1 and older switches needing 2.3.0.

That would suck if that was the case...

What model Basic do you have?

[maciboy]

I only know that at least one of my Basics says TH_1.1 on it. I recognized this by accident the last time I flashed it by wire...
Since I bought both at the same time from the same reseller, I assume both of mine are TH_1.1's...

[apastuszak]

The one I have that saus TH_1.1 on it, I was able to upgrade to 6.1.0 using the provided binaries on Github (which are compiled with 2.3.0). The one I have that says R2 would give me flashing lights after I installed even sonoff-minimal.bin, but worked fine when I installed sonoff-minimal.bin followed by sonoff.bin, both of which were compiled with 2.4.1 instead of 2.3.0.

I'd love someone with an R2 and an older switch to try and duplicate what I am seeing. The TH 1.1 board is in service on an aquarium now, so I can't tinker with it. But the R2 board is loose on my desk. 3 times now, with this board, I have loaded Tasmota 6.1.0 compiled with 2.3.0 and had it not connect over wifi (even with a serial flash), and 3 times I have had no issues connecting to wifi when I flashed 6.1.0 (wifi or serial) using Arduino Core 2.4.1.

EDIT: Found a TH_1.1 still in box with Tasmota on it. I'll try and upgrade that via OTA using some compiled binaries of 6.1.0 with Arduino Core 2.4.1 and see what happens.

[gorgiea]

It would be handy in this case.. if you could upload minimal FW during the WiFi manager time period, so it would not require wire flashing each time.

[TasmotaFan]

@apastuszak thanks for providing 6.1.0 with Arduino Core 2.4.1 - sonoff-minimal.bin and sonoff-DE.bin
I flashed the sonoff-DE.bin and it connects without problems on my sonoff-basic TH_V1.1
Then I made a full reset (press button 40sec). The Wifi Manager starts and I could connect to 192.168.4.1
Then I could set the configuration via the Web-Server. So it looks good

[maciboy]

@TasmotaFan
Does it still look good for you with the bin's provided by apastuszak?
I'm about to give flashing another try, but it's hard to figure out which version I should use 😆

Edit:
Basics both says: TH_V1.1 2017-5-5 (1741)
This Basic is not working properly with the provided 6.1.0-DE with Arduino Core 2.4.1.
It attempts to access the wifi, I can see these attempts in my router (FritzBox), but the fail... (timeout)

So, I tried the following firmwares:
6.1.0-DE with Arduino Core 2.4.1 (by @apastuszak)
6.1.1 as provided in https://github.com/arendst/Sonoff-Tasmota/releases
5.14 as provided in https://github.com/arendst/Sonoff-Tasmota/releases
5.13.1 as provided in https://github.com/arendst/Sonoff-Tasmota/releases

Only 5.13.1 works, all others do not connect to my wifi
Conclusion: it seems to me as if both core 2.3 and v6.1.x are problematic for this Basic individually, since always if at least one of them is present in the firmware, issues appear...

[mrtaxi]

Hi! Sonoff Basic OTA update and flash over serial. from 5.14 to 6.11 fails with blinking green light.
Downgrade to 5.14 over serial.

[TasmotaFan]

@maciboy
my sonoff-basic TH_V1.1 with the 5.13.1 does connect to my Wifi with WPS to my Fritzbox 6490.
When I then flash a 6.1.0-DE with Arduino Core 2.4.1. to it then it connects to my Wifi with the restored ssid.
When I made a full reset (press button 40sec). WPS does not work, but the Wifi Manager starts and I could connect to 192.168.4.1. Then I could set the configuration via the Web-Server.

[Jason2866]

WPS problems will be solved in future. Not included anymore in future precompiled builds 😉
Wifimanager is stamdard

[pReya]

Same problem here (https://github.com/arendst/Sonoff-Tasmota/issues/3056). This has been going on for a while now, and seems to affect many users with Sonoff Basic modules. I'd love to get to the bottom of this.

[all-solutions]

I'm really new with sonoff. Flashed my devices with 5.9.1. All other versions above caused the "wifi-problem". Meanwhile I've tested all versions above (clean flash). The devices can't connect to my wifi.
But I want a possibility to use v6. I found it in the version 6.1.0 from @apastuszak. His version works on Basic and S20 devices for me. Now waiting for the delivery from Banggood for the ordered devices (duo & 4ch)...

[ascillato2]

Please, see #3224

If your issue is not solved, please reopen it. Thanks

[apastuszak]

So, what is the fix?

[maciboy]

The issue for me is not solved, I just circumvented it by going back to v5.13.1 😞
Others seem to have done similar things, like downgrading or building special individual versions that circumvent the issue...

[knowsnotmuch]

how do you downgrade via wifi? or are you all taking the units down and flashing them via Serial?

[apastuszak]

If you have a blinking light, then that's the only way to go.

I think they're saying the 6.1.1c release fixes the wifi issue, with the
removal of the ESP8266 Smart Config code.

On Mon, Jul 23, 2018 at 9:42 AM knowsnotmuch [e-mail]
wrote:

how do you downgrade via wifi? or are you all taking the units down and
flashing them via Serial?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/3177#issuecomment-407062041,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADPlXjPsYemv4urkGoglA_IyxPOznlWxks5uJdLGgaJpZM4VJUOc
.

[maciboy]

@knowsnotmuch do you refer to my post? Yes, unfortunately I need to do it via serial, no chance to do it via wifi

[knowsnotmuch]

@maciboy - yes - was referring to that - thanks for clarifying. Have a couple attached to the ceiling fan - too much hassle getting them down :D Thanks both of you @maciboy and @apastuszak

[rwassily]

I am having the same problem, where LED is flashing green. If I quickly press 4 times, I see a new WIFI network but when connecting to it I don't get any IP and hence can't connect to it. Any tips on how to fix this also how do you download older Tasmoto versions? I flashed Sonoff bassic straight to v6.3.0

[meingraham]

Once you connect to it, from the device connected to the device AP, Are you able to open a browser and open http://192.168.4.1? If so, that should allow you to configure the Wi-Fi parameters. Once you restart the switch, it should join your Wi-Fi network and you should be able to connect to it via its Wi-Fi IP address.

[rwassily]

device doesn't connect to AP and I can't connect to it after pressing 4x reset. It always flashing green. When I press once it doesn't even trigger the relay.
First Sonoff was flashed while on 5v so I switched to 3.3v the second module but same problem, I also tried sonoff-basic.bin and sonoff.bin but neither works.

[rwassily]

After flashing to an older version, it seems to be working now.
https://www.youtube.com/watch?v=MOEmVYn4I8A

[meingraham]

@rwassily,

If your first device is still operational after flashing using 5V, you are fortunate indeed! That should have released the magic smoke inside your switch ;-) Having said that, if you notice any strange behavior with the switch, it may be remnants of having connected it to 5V.

But that aside,...

What Sonoff device are you referring to?

What version of TASMOTA did you try to flash? If it was the latest master release (6.3.0), then yes, that has some known connectivity issues. Try using the latest development version. I find the development branch to be pretty stable.

If you decide to upgrade and still encounter issues, please go to the web (or serial) Console and type Status 0. This will provide us with useful information to help you troubleshoot your issue.

As you have upgraded and reverted firmware versions, you are keenly aware of the nice thing once you have TASMOTA on the device. That is, if one encounters problems with the firmware version, most times one can just flash another version using OTA.

I have found that using ESPEasy to upload the firmware is the easiest method. Also, _if I'm flashing using the serial interface (i.e., wired)_, I use Termite to send the initial configuration commands (at least the Wi-Fi config). Dr. Zzs tutorial describes this in detail. It has some of the same information as the video you linked, but is more current and a bit more "compact".

Regards.

Mike

[rwassily]

Mike,
Thanks for taking the time to explain. I am using Sonoff basic, tried the 6.3.0 and it failed then flashed 5.14.0 and it seems to work. I am only flashing using serial and ESPEasy, once done I log to web interface to set WIFI parameters.
I noticed that the toggle doens't work properly through web interface, works 1/10 times but Yeti seems to work fine so that's my main concern. I'll have to figure out how to connect remotely, for now it just works from local network.
At the moment I am trying to figure out MQTT and the advantages of having it, luckily I already have a Rpi3.
Any modules you know of that has dry contact detection; alarms generated by surveillance cameras are dry contact, that's why I am asking.

B.regards
Rafik

[meingraham]

Rafik,

You may want to give the TASMOTA Discord chat a try. Lots of HA enthusiasts that can discuss your scenario interactively and recommend an appropriate device for your surveillance camera use case.

You can also give the Sonoff Users Google Groups a go.

As for your Sonoff Basic, I would recommend using the latest development version. I began using TASMOTA with version 6.0.x and have just recently upgraded to 6.3.0.16. The web interface operates (i.e., toggle) completely reliably on all my devices. You can easily update the firmware over the air without having to connect to the serial interface.

Mike

[rwassily]

Mike,
Thanks for your help, the version 6.0.17 on the link you shared did work for me; 1 out of 4 Sonoffs is constantly flashing green but seems to be working, not sure if it's an indication of some fault... maybe that's the one I used 5v on, not sure.
OTA didn't work for me so I used serial and it worked right away.

Is the same .bin file used to flash any Sonoff device?

[meingraham]

Rafik (@rwassily),

Glad to hear that you got your devices flashed and working!

Can you "reach" the device with the flashing LED? A blinking LED is usually an indication that it has not connected to the Wi-Fi network. A device that successfully connects to Wi-Fi will typically have an LED that is on or off (you can set the behavior with the LEDState command). If you can connect to this device, you should go to the Console to see what messages are being logged. If you can reach the web GUI, go to the Console and enter 'WebLog 4'. If you can only connect to it through the serial interface (that's probably a clue as to a problem), enter 'SerialLog 4'. The messages in the log may give you a clue as to why the device's LED is always blinking. Be sure to set it back to log level 2 after you're done to avoid extra logging workload on the device.

"Is the same .bin file used to flash any Sonoff device?" Short answer - yes. But there's a qualifier to my answer.

Each precompiled binary has different options set. You can see the differences in each in the "Available Features and Sensors" section of the releases page. For your Sonoff Basic, you should use this development version binary.

For most other ESP based devices that TASMOTA supports, you can choose any of the pre-compile binaries "flavors" that best suits the options you need. Once you flash the firmware onto the device, you go to the configuration and select the specific type of device you actually have (it defaults to Sonoff Basic). Once you set the right Module type, different configuration options will be made available based on the Module type.

Mike

[rwassily]

Mike,

I meant 6.3.0.17 :) I checked the logs and seems that it was trying to reach an MQTT server, once I set the parameters, the LED went off.
Thanks for the clarification about the the bin file and how the flashing is expected.

Now to check the advantages of connecting to MQTT and how to access these devices outside my LAN :)

B.regards
Rafik

[meingraham]

TASMOTA change log - That will tell you just how much progress is always happening w/ TASMOTA.

Careful how you set up external access to your devices. Opening up your LAN to the world is risky. If not done properly it could expose your entire home network to malicious access.

All of my MQTT traffic is local to my LAN. I like this setup because it limits my exposure. Also, if my connection to the Internet is down, I can still control everything locally on my LAN. I have a home automation hub (openHAB) where I set up my automations that interface with all of my home's smart devices. openHAB provides a mobile app which can access my hub over the LAN or through a secure cloud connector. This cloud service provides remote access to my automation items. It also integrates with Google Assistant and Alexa to add voice control.

There are several home automation hub solutions. If I were choosing today, I'd look at both openHAB and Home Assistant. There are many others. They all have their pros and cons. Your skills may be better suited for one HA hub solution versus another.

Mike

[rwassily]

Mike,
I am running everything on a RPI3; using HASS.io at the moment and seems straight forward. Trying to run MQTT from the same server but it doesn't open the configured ports for some reason. On some forums ppl advised to make sure MQTT booted before HASS.io; I am currently still trying to figure this out and trying to find a safe mobile app to connect to HASS.io as well

Rafik