Tasmota 🚀 - wifi/network problems 5.13.1

Hello,
i had the same issue with the 5.12 and the sonoff t2 (4 devices), it has lost many pings.
i flashed back to 5.11, now all t2 working very well.

mpuff on 2 May 2018

Hello,

same problem here! wifi quality is poor with 5.13.1, i have changed not the positions of my sonoffs, after upgrade to 5.13.1 there were not longer reachable via wifi... when i bring them near to my router all works again so there must be an error with the wifi in this update...

maybe it will be fixed?!?! thx for help

KoLSMS on 2 May 2018

Hi,

same problem here with sonoff basic.

octek0815 on 2 May 2018

yes, the same problem...
RSSI is equal? Webserver and mqtt not stabil - why?

Core/SDK Version: 2_4_1/2.2.1(cfd48f3

timtimsson on 2 May 2018

If you compile your firmware by yourself, try switch to lib 2.3.0 instead of the default 2.4.0.

Personaly I still have a lot of Wifi and Web-Interface troubles using lib 2.4.0 and the last binary release was compiled using lib 2.4.0. When I'm using same Tasmota version which causes troubles using lib 2.3.0 all problems are gone. This is not common but try this step.

curzon01 on 2 May 2018

👍2

maybe the devs here compile a new version with lib 2.3.0 because there are many users with the wifi issue?!?! would be great, i am no expert and do not know how to comile a new Tasmota with 2.3.0 lib :(

KoLSMS on 2 May 2018

Having wifi issues also, has become very unstable with the latest releases.

rlust on 2 May 2018

@curzon01
i have compiled my firmware with lib 2.3.0, upload it via web but same issue...
in the platformio.ini i uncomment "platform = [email protected] ; v2.3.0"

alofi198 on 2 May 2018

fyi
when i compile with lib 2.4.1 i have no problems with wifi!

alofi198 on 2 May 2018

My test device works without any problem since 1 day...
screenshot_20180502-193935

Jason2866 on 2 May 2018

This is 5.13.0a and not 5.13.1.......

KoLSMS on 2 May 2018

my Sonoff basic also does wifi very bad with 5.13.1, im back on 5.12.0 and working again.. my Sonoff TH10(with sensor) have no problems.

im using the release bin file sonoff.bin and upgraded through web interface.

i even try'd resetting the 5.13.1 to default settings and setup again.. no luck.

dezral on 2 May 2018

Makes no difference. Compiled 5.13.1a is working too.
I use Arduino 2.3.0. With later Arduino versions i do have problems with wifi (reconnects)
and unresponsive web interface.

Jason2866 on 2 May 2018

went from 5.13.0 -> 5.13.1, lost my sonoff basic connection.
tried all the solutions that i could think off, or posted above, moved the ap closer so it would have 100% signal, disabled my 5GHz ssid, switched 2.4GHz network from N to legacy mode, forced channels from auto to some random values, width from 20MHz to 40MHz, none worked.

it has a sporadic 2 packets ping reply pattern:
Request timed out.
Request timed out.
Reply from 192.168.2.242: Destination host unreachable.
Reply from 192.168.2.243: bytes=32 time=24ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.242: Destination host unreachable.
Reply from 192.168.2.243: bytes=32 time=2ms TTL=128
Reply from 192.168.2.242: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

and if i manage to catch the ping pattern, i can see the web console:
21:38:00 WIF: Connecting to AP1 myap in mode 11N as sonoff02-6440...
21:38:01 WIF: Checking connection...
21:38:01 WIF: Attempting connection...
21:38:02 WIF: Checking connection...
21:38:02 WIF: Attempting connection...
21:38:03 WIF: Checking connection...
21:38:03 WIF: Attempting connection...
21:38:04 WIF: Checking connection...
21:38:04 WIF: Attempting connection...
21:38:05 WIF: Checking connection...
21:38:05 WIF: Attempting connection...
21:38:06 WIF: Checking connection...
21:38:06 WIF: Connected
21:38:06 DNS: Initialized

is there a way to ota flash the device in this state?

C05M1N on 2 May 2018

Same here, after updating from 5.12.0 -> 5.13.1 all sonoff's basics have wifi problems. The sonoff S20 switches no problems.

P.S. Updated through OTA: http://sonoff.maddox.co.uk/tasmota/sonoff.bin

tikkerei on 2 May 2018

👍1

No issues here with the Basics, compiled with "Core-/SDK-Version | 2_3_0/1.5.3"

All my BASIC's are working fine on 5.13.1! WLAN is quite good!

Einstein67 on 2 May 2018

Same here. I want to add that, for me and my Sonoff Basic, problems starts only when I configure it with my MQTT server. Before that, WiFi/web control seems to work properly. No problems at all with 5.12.0

raneri on 2 May 2018

5.12.0 was fine for me either
but
after ota update from 5.13.0 -> 5.13.1 wifi keeps disconnecting

C05M1N on 2 May 2018

@everyone who has problems with 5.13.x. could you check which Arduino IDE core version is used.
No offend! A statement i have problems too, do not help solving the issue. Please give as many
infos you have. Downloaded version? Where? Self compiled version? Which ide? Compile options?
Every info could be helpful. If you manage to get status 0 -> post it!
Everyone here has a big interest to find the reason and get a solution.

Jason2866 on 2 May 2018

👍1

I downgrad to 5.13.0 and the problems stop.

nunoronconcouto on 3 May 2018

I recompiled 5.13a with Arduino 2.3.0 on SONOFF basic Sonoff TH and WEMOS D1 mini, and now they have stayed connected for 10 hours, prior dropping every few minutes. Was using 5.1.3 prior.

rlust on 3 May 2018

My Sonoff Basic, Sonoff S22, Sonoff Dual R2, Sonoff Bridge, Sonoff Touch US are working normally with no WIFI issue.
Firmware info:

Self compiled version 5.13.1 (using latest version of VSC+PlatformIO)
ESP8266 Core version 2.3.0
Tasmota-MQTT

Regards,

wongnam on 3 May 2018

i use Atom with platformio, i have compiled with core lib 2.4.1... no more problems with wifi

grafik

alofi198 on 3 May 2018

Give Tasmota 5.13.1a and ESP V2.4.1 a try. I've been running for two days
straight, no complains.

Previously I was running Tasmota 5.12.1i and V2.4.0 and V2.30, lots of
problems, frequent disconnection, unable to reach web server.

On Thu, May 3, 2018 at 4:32 PM alofi198 notifications@github.com wrote:

i use Atom with platformio, i have compiled with core lib 2.4.1... no more
problems with wifi

[image: grafik]
https://user-images.githubusercontent.com/38906755/39566764-f4d43a02-4ebc-11e8-8ea4-d1e17492f73c.png

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

alton76 on 3 May 2018

I switched back to 5.12.0, will wait for official fix for the wifi problems, maybe in the next release...

KoLSMS on 3 May 2018

Same here. Both of my existing Sonoff Basics are close to their AP (90+%) and ran flawlessly for months on 5.12. Upgraded to 5.13.1 last night and since then, both sporadically drop offline on a regular basis. Updated OTA, first using the minimal variant, then using the regular variant (to overcome flash size issues).

Interestingly, updated a Wemos D1 Mini to 5.13.1 at the same time and have had no connectivity issues. Go figure.

EDIT: as suggested by @alofi198 and @alton76, I recompiled 5.13.1 w/ ESP 2.4.1 and things have looked stable so far.

bachya on 3 May 2018

No Problem with Sonoff Basic, TH and POW. Compiled Version 5.13.1-2_3_0 with Atom and platformio.
Wifi set to Mode N only and minimal Power (4mW). Distance to the AP less than 4m and RSSI Signal 100%.

00:00:00 Project sonoff zwicker (Topic zwicker, Fallback DVES_168B69, GroupTopic sonoffs) Version 5.13.1-2_3_0
00:00:00 WIF: Connecting to AP1 :-) in mode 11N as zwicker...
00:00:11 WIF: Connected
00:00:11 DNS: Initialized
00:00:11 HTP: Web server active on zwicker.local with IP address 192.168.0.1
00:00:12 MQT: Attempting connection...
00:00:12 MQT: Connected
00:00:12 MQT: tele/zwicker/LWT = Online (retained)
00:00:12 MQT: cmnd/zwicker/POWER = 
00:00:12 MQT: tele/zwicker/INFO1 = {"Module":"Sonoff Basic","Version":"5.13.1","FallbackTopic":"DVES_168B69","GroupTopic":"sonoffs"}
00:00:12 MQT: tele/zwicker/INFO2 = {"WebServerMode":"Admin","Hostname":"zwicker","IPAddress":"192.168.0.1"}
00:00:12 MQT: tele/zwicker/INFO3 = {"RestartReason":"Software/System restart"}
00:00:13 MQT: stat/zwicker/RESULT = {"POWER":"ON"}
00:00:13 MQT: stat/zwicker/POWER = ON (retained)
21:04:48 MQT: tele/zwicker/STATE = {"Time":"2018-05-03T21:04:48","Uptime":"0T00:00:20","Vcc":3.178,"POWER":"ON","Wifi":{"AP":1,"SSId":":-)","RSSI":82,"APMac":"00:11:6B:2C:96:0E"}} (retained)
21:05:19 MQT: tele/zwicker/STATE = {"Time":"2018-05-03T21:05:19","Uptime":"0T00:00:51","Vcc":3.178,"POWER":"ON","Wifi":{"AP":1,"SSId":"","RSSI":80,"APMac":"00:11:6B:2C:96:0E"}} (retained)
21:05:49 MQT: tele/zwicker/STATE = {"Time":"2018-05-03T21:05:49","Uptime":"0T00:01:21","Vcc":3.181,"POWER":"ON","Wifi":{"AP":1,"SSId":"","RSSI":80,"APMac":"00:11:6B:2C:96:0E"}} (retained)
21:06:19 MQT: tele/zwicker/STATE = {"Time":"2018-05-03T21:06:19","Uptime":"0T00:01:51","Vcc":3.183,"POWER":"ON","Wifi":{"AP":1,"SSId":"","RSSI":82,"APMac":"00:11:6B:2C:96:0E"}} (retained)
21:06:49 MQT: tele/zwicker/STATE = {"Time":"2018-05-03T21:06:49","Uptime":"0T00:02:21","Vcc":3.178,"POWER":"ON","Wifi":{"AP":1,"SSId":"","RSSI":80,"APMac":"00:11:6B:2C:96:0E"}} (retained)
21:07:25 MQT: tele/zwicker/STATE = {"Time":"2018-05-03T21:07:25","Uptime":"0T00:02:57","Vcc":3.180,"POWER":"ON","Wifi":{"AP":1,"SSId":"","RSSI":82,"APMac":"00:11:6B:2C:96:0E"}} (retained)

Also fine and running for more than 2 day's with Version 5.13.0, 2_3_0/1.5.3(aec24ac9)
vorplatz_2018-05-03_22-14-10

wasi54 on 3 May 2018

One more Test with 5.13.0a, core 2.3.0. Compiled with atom and plattformio.
Also OK and stable.
sonoff-th_2018-05-03_22-29-39

wasi54 on 3 May 2018

TH Module, was OK with 5.13.0a and core 2.3.0. Now failed with core 2.4.1 and compiled with atom and plattformio.

PING 192.168.0.1 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=13 ttl=255 time=810 ms
--- 192.168.0.1 ping statistics ---
28 packets transmitted, 1 received, 96% packet loss, time 27686ms
rtt min/avg/max/mdev = 810.227/810.227/810.227/0.000 ms

Webserver not responding either!

wasi54 on 3 May 2018

Following up: I've been running 5.13.1 with ESP 2.4.1 for 24 hours with no issues.

bachya on 4 May 2018

Did observe the reconnection problem on the version 5.13.1 downloaded from maddox.

JueBag on 4 May 2018

Did some more test:
When using the update as provided by http://sonoff.maddox.co.uk/tasmota/sonoff.bin it uses Tasmota 5.13.1 with Core/SDK Version 2_4_0/2.1.0(deb1901).
On this version I do get connection problems, starting single with MQTT reconnects soon to be reconnects by the minute.
Reverting back to 5.12.0 using 2.3.0 this problem is gone.

JueBag on 6 May 2018

@JueBag if you change two things on same time (prog version and lib version) how can this help to determine what's the reason of failure is? Is it the lib or the program?

curzon01 on 6 May 2018

👍1

Absolutely true!
However both versions used so far are only downloaded ( either from the site posted above or from GitHub as for the 5.12.0 version). Doing the regression test on both did take a while.
Just wanted to point the differences.
What I read in that whole thread a test with 5.13.1 using 2.4.1 could be woth a try. Since I didn't compile with different library's yet, that will take some time.

JueBag on 7 May 2018

I'm also have connections problem after update from 5.12 to 5.13.1, it's happening only with Sonoff basic RF, the rest of the devices are o.k

leranp on 7 May 2018

Are there instructions on how to compile a Sonoff minimal and regular sonoff image for OTA uploads? It looks like using anything other that 2.4.0 seems to resolve the issue. But I really don't want to gather all my Sonoffs up and serially flash them.

apastuszak on 7 May 2018

@apastuszak
Yes, this is described in the wiki. If you use Platformio compiling is really easy

Jason2866 on 7 May 2018

Updated my 5x Sonoffs to 5.13.1 using OTA method from http://sonoff.maddox.co.uk/tasmota/sonoff.bin

2 of them are stuck on the "minimal" firmware and won't connect to my WiFi, the other 3 have updated, and only 1 (a T-1) is working. The others that have at least completed the update are continually rebooting.

I've managed to downgrade these 3 to 5.12, but my other two might need some manual intervention to get them up and running again. Thankfully they're only running my heating, and it's currently blisteringly hot here, so I can spend the next couple of days looking into it, but a shame so many of us seem to have encountered such a serious issue, especially when the OTA update has worked spectacularly well in the past.

Despite my complaints above, I must extend my thanks for the work you put into this :)

ConfusedTA on 8 May 2018

@Jason2866 Can these be used to do an OTA update?

apastuszak on 8 May 2018

@apastuszak
If you compile yourself you upload it via the webconsole "Upgrade by file upload"

Jason2866 on 8 May 2018

Compiled using Platform I/O using Core 2.4.1. Flashed one switch just now and it's up and running without issues. Granted it has only been 5 minutes, but the provided binaries crapped out pretty much instantly.

Sounds like we may just need binaries. recompiled and rereleased.

apastuszak on 8 May 2018

Running a test with a self-compiled version using 5.13.1 and 2.4.1 on a sonoff th as well. Let's wait till tomorrow.

JueBag on 8 May 2018

@JueBag
What compiler are you using?

@apastuszak
I compiled Core 2.4.1 using Arduino IDE 1.8.5 OSX, ran into MQTT connection issues. It would work for a while and stall. I could I get access to the web browser, console tells me it's connected to MQTT Broker but no incoming messages.

Will get back with a log.
Meanwhile, let us know how it goes...

jeylites on 8 May 2018

VSCode with PlatformIO

JueBag on 8 May 2018

@jeylites I also compiled using Visual Studio Code with Platform IO. I uncommented the line that made it use 2.4.1. It's up a running on one Sonoff Basic.

I'm able to use HomeAssistant to turn the switch on and off, and my automations are working and sending alerts to my phone. I can put my binaries up somewhere if you wan to give them a try.

apastuszak on 9 May 2018

I wonder if the kind compiler used has got any influence in core 2.4.1 reliability? I have yet to toy with Platform Io, seem complicated to set up for me... Will give it a try soon

jeylites on 9 May 2018

When I turned MQTT off (with quite a bit patience, reset unit & then change settings ASAP) I could get wifi back & do OTA downgrade.

hannoHI on 9 May 2018

The sonoff TH semi to be running stable, only one MQTT reconnect since yesterday. The sonoff RF however is showing those now once per hour.
Will continue to monitor.

JueBag on 9 May 2018

@JueBag

The sonoff TH semi to be running stable, only one MQTT reconnect since yesterday. The sonoff RF however is showing those now once per hour.
Will continue to monitor.

good to know, I flashed Sonoff T1 UK 12 hours ago with Platform Io 1.26.1 OSX, so far no MQTT connections problem. Same setup with Arduino IDE 1.8.5 OSX I had MQTT receiving issues couple mins in despite having a solid wifi and broker connection. Not sure what is going on but seem working now. Config as follow. The only problem I have now is web server becomes unresponsive after a while, the only way to gain access is a router reboot or sonoff reboot. During that time, I'm still able to control the switches through MQTT.

Core 2.4.1
Tasmota 5.13.1a

jeylites on 9 May 2018

Status 0

01:27:40 MQT: stat/ve1/STATUS = {"Status":{"Module":30,"FriendlyName":["VE 1","VE 12","VE1 13"],"Topic":"ve1","ButtonTopic":"0","Power":1,"PowerOnState":3,"LedState":1,"SaveData":1,"SaveState":1,"ButtonRetain":0,"PowerRetain":0}}
01:27:40 MQT: stat/ve1/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://sonoff.maddox.co.uk/tasmota/sonoff.bin","RestartReason":"Exception","Uptime":"0T01:27:37","StartupUTC":"","Sleep":0,"BootCount":14,"SaveCount":97,"SaveAddress":"FB000"}}
01:27:40 MQT: stat/ve1/STATUS2 = {"StatusFWR":{"Version":"5.13.1a","BuildDateTime":"2018-05-09T13:43:48","Boot":31,"Core":"2_4_1","SDK":"2.2.1(cfd48f3)"}}
01:27:40 MQT: stat/ve1/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["SUGAR1","SUGAR2"],"TelePeriod":300,"SetOption":["0200A009","55818000"]}}
01:27:40 MQT: stat/ve1/STATUS4 = {"StatusMEM":{"ProgramSize":472,"Free":528,"Heap":17,"ProgramFlashSize":1024,"FlashSize":1024,"FlashMode":3}}
01:27:40 MQT: stat/ve1/STATUS5 = {"StatusNET":{"Hostname":"ve1-1256","IPAddress":"192.168.0.24","Gateway":"192.168.0.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.0.1","Mac":"60:01:94:97:44:E8","Webserver":2,"WifiConfig":4}}
01:27:40 MQT: stat/ve1/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.0.200","MqttPort":1883,"MqttClientMask":"24","MqttClient":"24","MqttUser":"admin","MqttType":2,"MAX_PACKET_SIZE":1000,"KEEPALIVE":15}}
01:27:40 MQT: stat/ve1/STATUS7 = {"StatusTIM":{"UTC":"Thu Jan 01 01:27:40 1970","Local":"Thu Jan 01 01:27:40 1970","StartDST":"Thu Jan 01 00:00:00 1970","EndDST":"Thu Jan 01 00:00:00 1970","Timezone":8}}
01:27:40 MQT: stat/ve1/STATUS10 = {"StatusSNS":{"Time":"1970-01-01T01:27:40"}}
01:27:40 MQT: stat/ve1/STATUS11 = {"StatusSTS":{"Time":"1970-01-01T01:27:40","Uptime":"0T01:27:37","POWER1":"ON","POWER2":"OFF","POWER3":"OFF","Wifi":{"AP":1,"SSId":"SUGAR1","RSSI":100,"APMac":"88:D7:F6:02:18:80"}}}

jeylites on 9 May 2018

@jeylites
Core 2.4.1 with Tasmota 5.13.1a bult with atom and platformio
Yes, the webserver becomes unresponsive after a while on my sonoffs to (Basic, T and Pow). Also MQTT connection remains stable.
And the verry good thing is, every on my sonnoffs can be restartet vie MQTT commands and up/downgradet as well, even while website is unresponsive.
So, no need for router reboot.

wasi54 on 10 May 2018

@wasi54 Have you tried 5.13.1?

apastuszak on 10 May 2018

No longer Problem with the Webserver with
Program Version: 5.13.1a
Build Date & Time: 2018-05-08T00:42:09
Core/SDK Version: 2_4_1/2.2.1(cfd48f3)
Uptime: 1T01:02:22
Free Memory: 20kB

Disabled as mutch as possible which i do not need like sensors which i not have, mDNS Discovery and more to get Free Memory > 20kB.

wasi54 on 10 May 2018

@apastuszak
I have some with 5.13.0 / 2_3_0/1.5.3(aec24ac9) uptime more than 8 day's and stable.
Currently i have no device with 5.13.1 !

wasi54 on 10 May 2018

@apastuszak
grafik

Just now compiled and ota updated. I'll let you know if there is still no problem till tomorrow!
Built with Atom/Platformio and latest updates:
Platform Espressif 8266
--------
Updating espressif8266                   @ 1.6.0          [Fixed]
Updating tool-mkspiffs                   @ 1.200.0        [Up-to-date]
Updating tool-esptool                    @ 1.409.0        [Up-to-date]
Updating tool-espotapy                   @ 1.1.0          [Up-to-date]
Updating framework-arduinoespressif8266  @ 1.20400.3      [Up-to-date]
Updating toolchain-xtensa                @ 1.40802.0      [Up-to-date]

This configuration do not work after a while on my site. The free memory decreases with the time and the webserver is becoming unavailable. Also ping time varies between 500ms up to 2s.
Console snap ones it is reachable:
21:00:02 MQT: Connect failed to mqtt.staffeln:1883, rc -2. Retry in 10 sec
21:00:13 MQT: Attempting connection...
21:00:18 MQT: Connect failed to mqtt.staffeln:1883, rc -2. Retry in 10 sec
21:00:29 MQT: Attempting connection...
21:00:29 MQT: Connected

wasi54 on 10 May 2018

I have all actually used sonoff switches (dual R2, RF and TH) on the self-compiled version 5.13.1 ( using

2_4_1/2.2.1(cfd48f3)).

I see occasional the following log entrys:

13:15:53 DNS: initialisiert
13:15:53 MQT: Verbindungsversuch...
13:15:53 MQT: verbunden
13:15:53 MQT: tele/sonoff_TH/LWT = online (beibehalten)
13:15:53 MQT: cmnd/sonoff_TH/POWER =

As they are not coming more then once an hour I'll stick with this one for the time being.
Have also observed times when the webserver was unresponsive, MQTT commands where performed on time during those occasions.

JueBag on 10 May 2018

Last time all my sonoff used

self compile FW (VSC + PlatformIO)
Tasmota 5.13.1
ESP8266 core version 2.3.0
Tasmota MQTT
wifi signal are in good condition.

My sonoff (Basic, S22, Dual R2, RF Bridge, Touch US) encountered the same issue with the WebServer was unresponsive but MQTT pub and sub were still performed accordingly.

My workaround:

self compile FW (VSC + PlatformIO)
Tasmota 5.13.1
ESP8266 core version 2.3.0
ESPMQTT ( the third library)

Now all sonoff are working normally for a couple of days.
I am still monitoring them.

Regars.

wongnam on 10 May 2018

Had the same problems, I fixed it with recompiling and installing 5.13.1a with arduino ide.

joopy on 13 May 2018

Hello everybody,
I just updated one Sonoff RF to the provided 5.13.1 .bin and have massive Wifi/Mqtt problems like other here reported. It has become unusable. Has anybody a 5.13.1a bin?? Before I was on 5.12 without any problems. Would like test this release.

Tasmota 5.13.1:
Program Size 529kB
Free Program Space 472kB
Free Memory 18kB

brainnex on 13 May 2018

It's pretty easy to compile yourself. I could make you some binaries. But I need to know your timezone and your timezone rules to get it right.

apastuszak on 13 May 2018

Sonoff-Tasmota 5.13.1a by Theo Arends my sonoff bin's.

http://www.dampsap.nl/tasmota/sonoff-TSL2561.bin
http://www.dampsap.nl/tasmota/sonoff.bin

joopy on 13 May 2018

Hi, I also made the bins for testing in all languages at https://github.com/ascillato/Sonoff-Tasmota_KNX/releases/tag/v5.13.1a
Compiled using ESP8266 Board Library v2.3.0 and lwIP v1.4

ascillato on 13 May 2018

thanks Joopy, your version works like a charm. Wifi/mqtt problems are gone. My sonoff kept my Wifi Settings. Just OTA flashed and worked.

brainnex on 13 May 2018

@brainnex good to hear! Enjoy.

joopy on 13 May 2018

Hi @joopy could you make one with timezone = 1 ? Thanks ( I live in spain). I have also problems with webserver (not with mqtt), and I have laready tried both 2.3.0 and 2.4.1 wth any success.

ortegafernando on 13 May 2018

From the console you can type timezone 1 and it will change

El dom., 13 de may. de 2018 16:20, ortegafernando notifications@github.com
escribió:

Hi @joopy https://github.com/joopy could you make one with timezone = 1
? Thanks ( I live in spain). I have also problems with webserver (not with
mqtt), and I have laready tried both 2.3.0 and 2.4.1 wth any success.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/2605#issuecomment-388649650,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ahw-h0CxmbSyBOn_0tmOUKt_0Mb2ZoGxks5tyIdzgaJpZM4TvC0N
.

ascillato on 13 May 2018

I experienced the same problems with 5.13.1a on 17 out of 22 devices. Now back at 5.12.0 and all is stable again

daballiemo on 13 May 2018

Hi,

Reloxx13 have compiled Tasmota using ESP8266 Board Library v2.3.0 at https://github.com/reloxx13/Sonoff-Tasmota-Modified/releases/tag/5.13.1b-mod-1.21.2 for several languages.

You can try also these.

ascillato on 13 May 2018

Considering the amount of wifi problems I will release a new version this week based on core 2.3.0

Sorry for inconveniences you have encountered.

arendst on 14 May 2018

👍9

Please, if you can do it also with lwIP 1.4

ascillato on 14 May 2018

@ascillato AFAIK there is no choise for lwIP 1.4 in core 2.3.0...

If you need it for knx can you pls test knx with core 2.3.0 before I release?

I'm off today so do not expect a release before wednesday.

arendst on 14 May 2018

It is not needed for KNX. It works with all the esp lib versions. You can release it. There is no problems with that. :+1:

Thanks

ascillato on 14 May 2018

So I've turned off auto discovery e.g mDNS in userconfig.h in all Tasmota build since 5.12 and I don't have any MQTT connection issues

mcc05 on 23 May 2018

General question:

Is it really a good idea to compile with Core 2.3.0?
Please remember the KRACK vulnerability!

I think we urgently need a version that runs stable on core 2.4.x

electrontube on 8 Jun 2018

Hi,

Up to now, the core 2.4.1 has a lot of wifi issues. You can compile Tasmota with 2.4.1 and use it, but sleep is disabled (because it hungs the device). It is not stable. Nevertheless, I have few Tasmotas with 2.4.1 for testing. Yes, works, but sometimes it hungs. I also have other small proyects with esp8266 and 2.4.1 and with the same problems.

Hope that the people from esp8266/arduino make a new release of the core soon :+1:

ascillato on 8 Jun 2018

Hi,
Tested also my sonoff stuff. Strange results
Images got precompiled from the website
All tested on the same physical sonoff basic modul.

ok:
tasmota version 5.11.1, Core-/SDK-Version: 2_3_0/1.5.3(aec24ac9), Build Date: 2018.01.07 21:51:30, imagename: sonoff-DE.bin
bad:
tasmota version 5.12.0, Core-/SDK-Version: 2_3_0/1.5.3(aec24ac9), Build Date: 2018.02.09 14:55:34, imagename: sonoff-DE.bin
ok:
tasmota version 5.12.0, Core-/SDK-Version: 2_3_0/1.5.3(aec24ac9), Build Date: 2018.02.09 14:58:02, imagename: sonoff-ds18x20.bin
very bad:
tasmota version 5.14.0, Core-SDK-Version: 2_3_0/1.5.3(aec24ac9), Build Date: 2018.05.15 15:18:52, imagename: sonoff-allsensors.bin

AP is 4m away

ok means: WIFI stable, Pings ok
bad means: WIFI stable but with long delay and many packet loses, some pings are working
very bad: No WIFI connection. Connection with tablet 5cm away not possible ("192.168.4.1 mode")

Tested as well with sonoff socket modul
All above tested images run perfect on this device.

Interesting:

Core/SDK Version is equal on all images
different language breaks the WIFI in 5.12.0 on sonoff basic modul. What is different between them ?

Hope it helps to figure out, why 5.14.0 is not working with sonoff basic modul

erwini on 13 Jun 2018

@erwini
Can you check the "Free Memory" for binaries with ok and bad binaries?
Different languages may consume more Memory.
5.14.0 is running since weeks without issues on my side with both core 2.3.0 and 2.4.1 with lwIP 1.4. as long the free Memory is at least 18kB or higher.
Also with:

wasi54 on 13 Jun 2018

Free memory with sonoff basic modul:

5.11.1: 26kB (imagename: sonoff-DE.bin, ok)
5.12.0: 23kB (imagename: sonoff-DE.bin, bad)
5.12.0: 23kB (imagename: sonoff-ds18x20.bin, ok)
5.14.0: ??kB (imagename: sonoff-allsensors.bin, very bad);I was not able to get a connect to see free memory

So with 5.12.0 the free memory was equal regardless of the language.
5.14.0 running on S20 Socket Module and Generic Module with 18kB free memory and Core/SDK Version 2_3_0/1.5.3(aec24ac9) without any problems. Maybe 18kB free memory is not to much for sonoff basic modul, assuming amount of free memory is equal on different platforms if using the same bin file ?!

erwini on 13 Jun 2018

@arendst
Meanwhile i have compiled 5.14.0 with

and

This works fine and stable on a basic, TH and Dual-V2 Module!
While firmware with the Buildflag
only works on TH and Dual-V2.
On the Basic Module it results with:
00:00:10 MQT: tele/sonoff/INFO3 = {"RestartReason":"Fatal exception:28 flag:2 (EXCEPTION) epc1:0x40270f8e epc2:0x00000000 epc3:0x00000000 excvaddr:0x00000000 depc:0x00000000"}

It seems to be stable on the Basic Module to with

wasi54 on 15 Jun 2018

Meanwhile setup platform.io for compilation without luck.
Moved to arduino ide 1.8.5. Compiled there version 6.0.0a
Tested with a sonoff basic modul with english language.
Core/SDK Version: 2_4_1/2.2.1(cfd48f3)
Tested wlan and it works perfect.

erwini on 28 Jun 2018

Compiled with german language. Wlan works perfect. Conclusion: use the newest software.

erwini on 28 Jun 2018

Hi,

Seems that your question has been addressed. Closing this issue. Please, reopen if needed. Thanks.

ascillato2 on 10 Jul 2018

Tasmota: wifi/network problems 5.13.1

Most helpful comment

All 82 comments

Related issues