The AT instruction set document should be reviewed and much better documented, focusing on the error messages. For example, documentation shows AT+CIPSTART commands returns "ERROR" or "ALREADY CONNECT", but in fact it returns 5/6 different messages some of them, and sometimes, used for several different non-related errors. Notice here and mixing the final error message with the "status"; for example "ALREADY CONNECT" is not the summary message (that is in fact "ERROR") but to show the kind of problem.
ALREADY CONNECT <= status or whatever you want to call it
ERROR <= summary
But in other cases we can get up to 2 responses for the same not documented, and so on up to 5-6 different messages none of them documented. And sometimes you get the problem description AFTER then "ERROR" string. Similar thing happens with other commands.
It looks trivial but it's not since you can get unexpected responses simply because you don't know they exist. I got some of these just testing one by one the AT commands whilst I was making a library to deal with them. Obviously forced me to increas the sofware complexity to patch these abundant non-regular cases.
So sorry for the inconvenience.
Those messages are logs for debugging. Only "OK" and "ERROR" should be used to check if the operation succeeded. Since ESP8266 AT has already been used by so many customers, we will not change the debugging messages. But for the new chipset ESP32, we will remove all unnecessary messages.
Thanks for your interest in ESP8266!
Who is online
Users browsing this forum: No registered users and 1 guest
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
We also have a RTOS version and a MESH version too!
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!