-
Notifications
You must be signed in to change notification settings - Fork 13.4k
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
WiFi.softAP doesn't seem to honor ssid or password #1261
Comments
See #1254 |
Silly question maybe, but I'd guess staging would have the latest fixes? Will this be pushed to the stagingrelease/ tag sometime, or should that branch not be used? |
Yeah, staging will get updated shortly. On Sun, Dec 20, 2015, 22:15 Kevin Mitchell notifications@github.com wrote:
|
Awesome! Is there any documentation about which features are available in staging vs stable? Somebody recently told me that i should be using staging buy obviously it send to behind in certain bug fixes? |
You can check git tags 2.0.0 and 2.0.0-rc2 and commits between them. Also see docs: |
Awesome! I'll RTFM ;) - thanks again, and sorry for the duplicate issue (I looked but somehow missed the duplicate issue!) |
Still having this issue that the AP is open. The SSID is being showed now. But that mybe only works because I tried to create an open AP by purpose as I omitted the password argument. Now after I added the password again it shows the AP but still as open and not secured :/ I have version 2.3.0 through board manager my Sketch:
|
I'm using the "staging" build.
I'm using the example sketch provided here in the repo which when run should result in a AP being created with a particular name, and secured with a password.
Instead, the AP is created with a generic SSID ("ESP_XXXXXXX") and w/o a password.
I'm guessing it doesn't matter, but this is on a ESP-12E.
The text was updated successfully, but these errors were encountered: