in AT commands 1.4 document it says that when we want to use special character ",/\"" we have to put / or \ infront of it.
This is very clear and works for me very great.
I'm building a event-based library with AT commands where user can also select custom AP name, so AT+CWSAP_CUR or _DEF can be used.
I used like this:
Code: Select all
//All lines ends with \r\n
AT+CWSAP="WIFI SPOT WITH END of \"\,","my\"\,password",3,0 //I send this with special characters included since I wanna have "," and \ in my wifi name.
OK //Respond from device
AT+CWSAP? //I send this since I wanna see new settings
+CWSAP:"WIFI SPOT WITH END of ",","my",password",1,0,4,0 //This is what I received
OK //End of command
So, my computer shows new Wi-Fi spot with name: WIFI SPOT WITH END of ", which is exactly what I wanna have.
Then please take a look at received string from ESP device:
+CWSAP:"WIFI SPOT WITH END of ",","my",password",1,0,4,0
So this big blue commas are real separators from ESP documentation, but take a look at one comma before which has exact pattern "," like separator part.
So there is a problem because there is no way I can know if I have like this:
Wifi name: WIFI SPOT WITH END of ",
Password: my",password
or
Wifi name: WIFI SPOT WITH END of
Password: ",my",password
And maybe some more combinations can be here.
So I think this is unsolved bug. The same should be check everywhere.
I suggest you that you return the same string as we sent (with encode characters).
Btw..when we can expect new AT commands version?