Skip to content

FW: use NONOS-SDK branch 2.2.x from 2019-10-24 by default #6724

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Nov 8, 2019

Conversation

d-a-v
Copy link
Collaborator

@d-a-v d-a-v commented Nov 7, 2019

former one is available when using generic board configuration

d-a-v added 2 commits November 7, 2019 16:28
former one is available when using generic board configuration
Copy link
Collaborator

@devyte devyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm ok with this, but I'd prefer to add the latest sdk of two days ago on top.

@Jason2866
Copy link
Contributor

@devyte 100%. Always good to have options to choose from.

@d-a-v
Copy link
Collaborator Author

d-a-v commented Nov 7, 2019

Did I understand the latest one by default for all boards ?

@Jason2866 are you ready for testing this within the next few hours/days ?

d-a-v added 2 commits November 7, 2019 22:11
(previous ones can be selected with the generic board)
@d-a-v d-a-v requested a review from devyte November 7, 2019 21:15
@d-a-v d-a-v changed the title FW: use NONOS-SDK branch 2.2.x from 2019-10-24 by default FW: use NONOS-SDK branch 2.2.x from 2019-11-05 by default Nov 7, 2019
@Jason2866
Copy link
Contributor

Just installed SDK22x_191105 and compiled Tasmota with.
3 devices are running now with. Will post first results tomorrow (it is 11.42 pm here)
image

@d-a-v d-a-v changed the title FW: use NONOS-SDK branch 2.2.x from 2019-11-05 by default FW: use NONOS-SDK branch 2.2.x from 2019-1-24 by default Nov 7, 2019
@d-a-v d-a-v changed the title FW: use NONOS-SDK branch 2.2.x from 2019-1-24 by default FW: use NONOS-SDK branch 2.2.x from 2019-10-24 by default Nov 7, 2019
@d-a-v
Copy link
Collaborator Author

d-a-v commented Nov 7, 2019

@Jason2866 Thanks !
It appears the 191105 version will be an option (but still available).

@d-a-v d-a-v merged commit 1ec3683 into esp8266:master Nov 8, 2019
@Jason2866
Copy link
Contributor

4 devices: 13 hours uptime. Not a single wifi or mqtt reconnect

@d-a-v
Copy link
Collaborator Author

d-a-v commented Nov 8, 2019

@Jason2866 You will need to use PIO_FRAMEWORK_ARDUINO_ESPRESSIF_SDK22x_191105 in your PIO configuration from now with current core-stage/git-version and next release (which is, I believe, happening before Monday).

@Jason2866
Copy link
Contributor

Jason2866 commented Nov 8, 2019

Thx, for the info. Great to hear release is this week :-) It is already there
image

@ascillato
Copy link
Contributor

I have also tested SDK22x_191105 and didn't have any issue so far.

@ascillato
Copy link
Contributor

ascillato commented Nov 20, 2019

I have also tested SDK22x_191105 and didn't have any issue so far.

After a massive update of all my devices to core 2.6.1 and several days of testings, I found the following related to SDKs:

  • SDK22x_190703
    Uses 2k flash less than SDK22x_191105
    No wifi/mqtt disconnections on devices with RSSI >35 (the same as core 2.3.0)

  • SDK22x_191024 and SDK22x_191105
    Uses 2k flash more than SDK22x_190703
    No wifi/mqtt disconnections on RSSI >55
    On RSSI=(35-55) it performs really bad

I tested taking out as many interfering factors as possible. Tested and replicated with different wifi routers (MikroTik, TP-Link and Linksys), with different weather conditions (dry, wet, wind, hot, cold, nice), different ESP8266 boards (itead sonoff basic, sonoff pow R2, sonoff dual, NodeMCU -with proper power source-, MagicHome, Esp01, between others), correct tool-chain and same firmware file (Tasmota) in all devices (to rule out compilation issues - old toolchain produces wifi issues on SDK22x_191105)

So, as a result, Core 2.6.1 SDK22x_190703 performs better than any other core/SDK and should be the default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants