-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Is it valid for wifi.sta.getapinfo() to return a null BSSID? #2025
Comments
Yes, that is an ok condition.
Unless your station was configured with the AP's mac address( ex: The reasoning behind this is that when no BSSID is set during station configuration, the Considering the confusion, maybe it would be prudent to change it to return an invalid mac address( |
Thanks for the explanation. Conclusion: there's no way we could figure out the AP's MAC from Lua land unless we knew it beforehand? |
Improved documentation for wifi.sta.getapinfo fix for nodemcu#2025
Improved documentation for wifi.sta.getapinfo fix for nodemcu#2025
The submitted PR should give you a way to get the currently configured AP's MAC address. |
* Modified wifi.sta.get*config() to return AP's MAC even if bssid_set==0 * Improved documentation for wifi.sta.getapinfo, fixes #2025
* Modified wifi.sta.get*config() to return AP's MAC even if bssid_set==0 * Improved documentation for wifi.sta.getapinfo, fixes nodemcu#2025
Running the example from https://nodemcu.readthedocs.io/en/latest/en/modules/wifi/#wifistagetapinfo I see that I get
nil
for my AP's BSSID. Is that an ok condition or does that signify a bug in the SDK or our mapping to Lua?Maybe something for @dnc40085?
The text was updated successfully, but these errors were encountered: