Skip to content
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

Feature Request: Wifi Connect to strongest RSSI rather than first one found. #57

Open
pandabear41 opened this issue Aug 13, 2020 · 4 comments

Comments

@pandabear41
Copy link

pandabear41 commented Aug 13, 2020

Been running into problems with the OpenGarage FW where it connects to a weak AP rather that a strong one on same SSID. This is causing issues with delayed Blynk and MQTT.

I believe that WiFi.begin without a channel connects to the first lowest channel it detects on the SSID. A potential solution would be doing a wifi scan and finding the strongest RSSI on the specified SSID instead of letting WiFi.begin select it.

Anyone else having this problem? Agree with solution idea?

@jduff001
Copy link

My local wifi has multiple AP that all broadcast the same SSID (netgear orbit's). I have enabled "fast roaming" that is supposed to have the router move the device to the strongest AP signal, but it does not work. I don't know if the Wifi.begin has the ability to detect the RSSI.
My workaround has been to power on the opengarage when only the nearest AP is operating... that is not really a great workaround.

@teufelhunden0311
Copy link

I know it isn't the greatest solution but I have a multiple AP setup like this with Unifi and to get around this I simply gave the OpenGarage a static IP address and forced it to only connect to the AP I wanted it to. I don't know if this is possible with Netgear products though.

@ares
Copy link

ares commented Dec 30, 2020

This feature would be great

@majorsl
Copy link

majorsl commented Apr 25, 2024

Any chance we'll ever see this? Even if I use my MESH software to force OG to a particular access point, it doesn't stick. OG will latch on to an access point and won't give it up without a reset and re-pairing.

Example: I have a WAP in my garage as part of my MESH network. I updated its firmware and OG went to the next nearest WAP with a very poor signal...and it won't return automatically to the nearest WAP now that it is back on-line.

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

5 participants