I use a lot of identical boards with identical code. The specifics for each installation are stored on the ESP8266 ROM and recovered at boot.The first startup uses an auth code to a setup app that allows SSID, password, Human readable device name, Dallas sensor ID and such.
I connect to the network and then connect to a Blynk private server. One board refused to connect to the Blynk server. I suspected the auth code was invalid and re-enabled BLYNK_PRINT and that was in fact the issue. What I am looking for is a programmatic way to trap the “invalid auth code” returned from the Connect sequence. Right now all I could do is use the setup app auth code if the length of the auth code recovered from ROM was not exactly 32 bytes long.
Anybody know if there is a return error code from the Connect sequence and how to hook it up?