You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After flashing the firmware on the esp8266 board, and then setting the SSID and PASSWORD of the AP which the board will connect to, the board simply does not connect to the AP if there is an Underscore or Space character in the SSID. The range is not the problem here, as the AP was my phone which was sitting next to the esp8266, neither there the phone is set to 5Ghz band, and neither the phone is set to use WPA3.
The text was updated successfully, but these errors were encountered:
If you want to enter non-ASCII or special characters in the web interface you have to use HTTP-style hex encoding like "My%20AccessPoint". This will result in a string "My AccessPoint". With this hex encoding you can enter any byte value you like, except for 0 (for C-internal reasons).
Again, if you want to enter non-ASCII or special characters you can use HTTP-style hex encoding (e.g. "My%20AccessPoint") or, only on the CLI, as shortcut C-style quotes with backslash (e.g. "My\ AccessPoint"). Both methods will result in a string "My AccessPoint".
After flashing the firmware on the esp8266 board, and then setting the SSID and PASSWORD of the AP which the board will connect to, the board simply does not connect to the AP if there is an Underscore or Space character in the SSID. The range is not the problem here, as the AP was my phone which was sitting next to the esp8266, neither there the phone is set to 5Ghz band, and neither the phone is set to use WPA3.
The text was updated successfully, but these errors were encountered: