Skip to content

new release needed on esp8266wifi to improve behaviour on multiAP enviroment #6710

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

Closed
teldrive opened this issue Nov 4, 2019 · 12 comments
Closed

Comments

@teldrive
Copy link

teldrive commented Nov 4, 2019

we have detected that esp8266 arduino v2.52 can't connect to closer AP in a multi Ap enviroment(with same SSID), this issue sometimes causes lack of quality link
3 network(s) found:
1: floured, Ch:6 (-54dBm)
2: prueba, Ch:6 (-54dBm)
3: prueba, Ch:11 (-70dBm)
we contacted to espressif support and they have upgraded their sdk, so we need some with the deep acknoledge of theese libraries upgrade it with the new features introduced by espressif

@devyte
Copy link
Collaborator

devyte commented Nov 4, 2019

What are the commits of those upgrades in their repo? Were the changes backported to their 2.2.x branch, which is what we use?

@devyte
Copy link
Collaborator

devyte commented Nov 4, 2019

Also, can you please elaborate on the issue? I have a multiap environment with same ssid, so I would think I would have seen this.
Did you test with our latest git? There are known issues with 2.5.2 which can show as connection issues.

It would be best if you edit your original post and add the issue template with the info fields filled out.

@TD-er
Copy link
Contributor

TD-er commented Nov 4, 2019

I would also like to know a bit more on this issue.
Were you only using the SSID to connect, or does it also happen in the scenario where you perform a scan and then pick the one with the best RSSI and use the BSSID/channel taken from that scan?

So is it a matter of "cannot connect" or "does not choose the strongest AP" ?

@d-a-v
Copy link
Collaborator

d-a-v commented Nov 4, 2019

Currently in master we have as default: nonos-sdk-v2.2.x from 19-07-03
And we have optionally (when generic board and proper fw are selected) as testing: nonos-sdk-v2.2.x from 19-10-24
Check #6672

@teldrive
Can you verify with the available testing firmware which is currently the latest of their 2.2.x branch ?

@teldrive
Copy link
Author

teldrive commented Nov 4, 2019 via email

@teldrive
Copy link
Author

teldrive commented Nov 4, 2019 via email

@d-a-v
Copy link
Collaborator

d-a-v commented Nov 4, 2019

@teldrive
Current development version use more recent nonos-sdk firmwares than last stable release v2.5.2.
I don't understand the rest of the messages above.
You can

In either case, use Arduino IDE, select the generic board, then select the testing firmware (see my previous post, follow the included link).

@teldrive
Copy link
Author

teldrive commented Nov 4, 2019 via email

@d-a-v
Copy link
Collaborator

d-a-v commented Nov 4, 2019

@teldrive

They did, but not today, it was 11 days ago.
This is verifiable on their repository which I just checked.

We already have this update, but not in the latest stable 2.5.2 version you are using.
Please try our latest unstable version.
I gave you the howto-links in my previous message.

@teldrive
Copy link
Author

teldrive commented Nov 4, 2019 via email

@esp8266 esp8266 deleted a comment from teldrive Nov 6, 2019
@devyte
Copy link
Collaborator

devyte commented Nov 6, 2019

@teldrive I asked:

What are the commits of those upgrades in their repo? Were the changes backported to their 2.2.x branch, which is what we use?

We still need to know this. If the changes implemented by Espressif per your reports are in their 3.x branch, but have not been backported to their 2.2.x branch, then we can't pick them up.

Also, what is the status with you testing latest git?

@devyte
Copy link
Collaborator

devyte commented Nov 9, 2019

Latest SDK was included as optional in release 2.6.0.
If that one doesn't include your needed fixes, please request at the Espressif repo that your changes be backported to their 2.2.x branch, then open a new issue requesting an SDK update.
Closing.

@devyte devyte closed this as completed Nov 9, 2019
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

No branches or pull requests

4 participants