Hi…the name for my network at home is “GoBoo’s Place”. When I attempt to add this to the configuration, it skips everything after the apostrophe. Any way to fix this, or trick it into using that name?
Thanks!!
Will it let you select it from the list? That may force it.
I ran into that as well “¯_(ツ)_/¯” I guess is not the best network name… I’m going to look into it further and see if it is a character validation issue when trying to enter it, or if it’s a deeper issue. No promises, as Maslow currently built on a network stack that isn’t brand new so may have some limitations internally in how various special characters are stored and used throughout the network stack.
1 Like
Yeah, thats what I figured. I was hoping there might be a way to just supply unicode characters or something to get around it. Thats a GREAT network name
1 Like
I dont see any option to choose. I can type in an SSID, but not scan and choose.
1 Like
I haven’t played with it much, but the setup option here has a button that you can click to choose a wifi network from a list
1 Like
Oh! I hadn’t run in to that yet. I will give that a shot. Thanks!
1 Like
There should be a little nub of a button on the right of the Set button for that setting.
You can click that to get a list of available wifi networks that the Maslow can see.
It appears to be restricted to 2.4 GHz
1 Like
Yes, the wifi on ESP32s is restricted to 2.4 Ghz
1 Like
I found the sandwich menu. Sadly I get this…
It definitely doesn’t like the name. I am running 2.4Ghz and 5Ghz, so thats not it.
1 Like
I feel your pain if it helps (probably not). I have had to set up a network for one of my IOT devices that does not even like my space in “Byte Me”…
2 Likes
This is a known issue for many WiFi implementations. Short answer is if you can change the SSID to something that only uses very basic characters (think ASCII, but less) then do that.
1 Like
To be clear… maslow and other ESP32 devices I have connect fine to “Byte Me” so spaces are fine.
3 Likes
Let’s just all go back to Baudot and Teletype
2 Likes
This was my worry. Although this hasn’t been a problem in a long time.
Definitely not going to change my network just to appease an ESP32. I’ve got dozens of whatnots and doodads using my network.
1 Like
Another option is to use the maslow’s network when interacting with the machine.
2 Likes
Yeah, I think that’s what I’ll be doing. Not the end of the world, but it would be nice to just have it on my network. Thanks for your help!
1 Like
I spent some time looking at this today. There are several ways to try to set your wifi network, and none of them seem to work with extended characters, and I think there are multiple failure points.
If you dig through the FluidNC Wiki / manual, there are some references to Wifi networks with “non-US” ascii characters and using % escaping like browser requests.
=========
International Characters and spaces in WiFi SSIDs
The GRBL line protocol only handles US ASCII; it cannot transmit international characters or spaces directly.
If your WiFi SSID contains a non-ASCII character like, for example ä, there is a trick to enter that character when setting the SSID with $Sta/SSID=something . You can replace the character with a special “escape sequence”. This online converter will help.
If you paste the ä in the left box, the right box will show 0xc3 0xa4. Replace the 0x with % and omit the intervening space to enter the sequence in the $Sta/SSID value. For example, if your SSID is Säx, you would write S%c3%a4x in the webUI Sta/SSID field or $Sta/SSID=S%c3%a4x in the commandprompt.
For the usage of a (white)space character in your SSID, just replace it with %20. For example, if your SSID is Flying Pinguin you would write Flying%20Pinguin in the webUI Sta/SSID field or $Sta/SSID=Flying%20Pinguin in the commandprompt.
==========
This doesn’t appear to work for unicode, so it might just be for extended ascii. But it might be worth trying with your specific network name since it’s only the smart quote. and if you replace the smart quote with a single ascii quote, it would work!
I even tried rebuilding it and setting the default station SSID in the code, but that didn’t work either (for my network name). Oddly, it almost worked for the default AP name…
The failure points I think are the following
- Whatever form validation / input validation happening may be flagging some of the special characters
- The command protocol as mentioned is GRBL based so doesn’t do well with the special characters.
- The web server code handling the commands
- The wifi stack itself not fully handling special characters (or at least some combinations).
I’m going to do some more research and see if more recent wifi libraries for ESP32 support any of this any better and work from there. If we can get the wifi portion fully supporting unicode, at least you could build your own firmware and have it work with the network name hard-coded. Beyond that maybe there is a different mechanism we can utilize to pass the unicode / network name back from the popup list (which appears to display it properly) to the device to store it in settings in a way that works…
right now I have to change wifi networks every time I want to switch from making a forum comment to rebuilding/re-downloading the code so the annoyance factor is certainly there!
1 Like