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

WifiNiNA cannot handle when the same SSID is broadcasted from multiple APs #75

Open
borianson opened this issue Sep 9, 2021 · 7 comments

Comments

@borianson
Copy link

We tried multiple MKR1010 boards with multiple different WifiNiNA FW revisions but could not establish a stable connection via wifi (or at the wast majority of the cases even connect). We have a grid of ~20 pcs of well working brand new Ubiquiti UniFi APs broadcasting the same SSID at our facility. Based on other users experience at the Arduino forum and on our experiance we assume something is wrong with how the FW or the module itself handles this specific situation when the device can detect multiple APs broadcasting the same SSID.

@Russell108
Copy link

Yes I have the same issues
We have a network of Access points Unifi I have found even if i get it to connect to the nearest Access point the Arduino MKR 1010 or nano IOT 33 can move to another over time. Usually one with a ridiculously low signal.

@CptHolzschnauz
Copy link

I confirm. I have the same SSID on a 2.4 and 5 GHz band. MKR1010 can't handle the setup. WifiNina Firmware 1.5 WPA2 Personal.

@g6094199
Copy link

g6094199 commented Nov 7, 2023

+1

with mkr1010 an fw 1.5

and a bunch of freifunk/openwrt APs (atheros ath10k based)

on the mkr it looks like this:

I am connected to the network
SSID: 
BSSID: 00:00:00:00:00:00
signal strength (RSSI): 0 dBm
Encryption Type:7

My IP Address: 192.168.xx.114
My MAC address: 30:AE:xx:xx:xx:04

no SSID from WiFi.SSID() and only zeros from WiFi.BSSID(), rssi = 0

same as:
arduino-libraries/WiFiNINA#200

@tmcqueen-materials
Copy link

@per1234 : This seems to be quite a fatal flaw in the current nina-fw, as it makes completely useless boards such as the Nano 33 IoT at home with a mesh network. Since it sounds like the solution is "easy" (change back to WIFI_ALL_CHANNEL_SCAN), can that be done with a small iteration of the firmware so this doesn't break for a situation that is just becoming more common? Thanks!

@nhbn
Copy link

nhbn commented Sep 9, 2024

We also have a multiple AP setup (Ubiquiti). We wanted to use Nano 33 IoT and I have about 20 Arduino sitting in the shelf to make them work. At the moment, we are struggeling with unstable connections (due to this issue).

Being able to use WIFI_ALL_CHANNEL_SCAN could be an option, being able to connect using BSSID would be optimal.

I'm considering switching to ESP32 that allow for that behaviour (though we would prefer the arduino eco system).

Is there a reason why this issue is open for so long?

@Russell108
Copy link

Russell108 commented Sep 9, 2024 via email

@borianson
Copy link
Author

borianson commented Sep 10, 2024

We also have a multiple AP setup (Ubiquiti). We wanted to use Nano 33 IoT and I have about 20 Arduino sitting in the shelf to make them work. At the moment, we are struggeling with unstable connections (due to this issue).

Being able to use WIFI_ALL_CHANNEL_SCAN could be an option, being able to connect using BSSID would be optimal.

I'm considering switching to ESP32 that allow for that behaviour (though we would prefer the arduino eco system).

Is there a reason why this issue is open for so long?

In the mean time we migrated to ESP32 and I suggest you the same. It is a pity that this could not be retified during the many years passed.

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

6 participants