-
Notifications
You must be signed in to change notification settings - Fork 118
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
Multi-access point: weakest signal chosen #385
Comments
I had a similar problem, though in my case with Ubiquity as the network vendor. Ubiquity allowed me to limit which AP OpenEVSE would associate with. Aruba might have the same? Ultimately I created a unique SSID that only the single AP near the OpenEVSE broadcasts. Obviously both are workarounds, but it's been stable. |
Good workaround idea. |
Looks like default behavior is to connect to the AP with the lowest
channel. Looks like there is a way to scan signal strength also.
https://www.reddit.com/r/esp32/comments/nphj1c/how_to_connect_to_wifi_ap_has_stronger_signal/
…On Mon, Jul 4, 2022, 1:26 PM Giacomo Ferrari ***@***.***> wrote:
Good workaround idea. My Aruba doesn't seem to have such an option, sadly.
—
Reply to this email directly, view it on GitHub
<#385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN5QH4LQ7ZGI5TN5VXKWRDVSMNF3ANCNFSM52SCT24A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Will look in to this, how are you checking the AP that is connected to, from the AP itself? |
From my AP's management interface. |
FWIW I found with mine some time ago it was connecting to the lowest channel number in range of multiple BSSIDs that it saw (regardless of signal strength). My workaround was set up 2 networks - one with the BSSID, another the same SSID and no BSSID at lower priority. That way it roams if the expected AP goes down. Then on the "server side" I have HomeAssistant issue a reboot to ESPHome if it notices an access point go from "down" to "up" on the network (tested by pinging its management interface). Really awful workaround but until they fix the bug for finding the strongest channel dynamically I couldn't find a better way. |
I have a commercial WiFi setup with multiple access points creating a single network (happens to be Aruba Network gear). All my devices correctly connect to the strongest access point, except OpenEVSE - it seems to default to the weakest signal. If I temporarily power down all access points other than the one I want OpenEVSE to use, it does associate with the correct access point.... but then goes right back to the weakest one on reboot. Very strange. Does it somehow remember the MAC of the first access point it saw?
The issue persists even if I associate with a completely different network, then reconnect to the original multi-access-point network.
Aside, as a workaround... is there any way to force association with a particular access point, such as by MAC/bssid?
EDIT: Looks like ESPHome ran into similar issues (not sure why my ESPHome devices work correctly). esphome/feature-requests#731
ESP-IDF has a roaming example, perhaps it could be integrated? https://github.com/espressif/esp-idf/tree/master/examples/wifi/roaming
The text was updated successfully, but these errors were encountered: