Invalid auth token ESP32

Solved
1

Hello folks,

I am new to Blynk and wanted to try the “Simple e-mail example” with an ESP32 D1 mini. Unfortunately I get the following error message:

[648] Connected to WiFi
[648] IP: 192.168.178.42
[649]
___ __ __
/ _ )/ /_ _____ / /__
/ _ / / // / _ / '/
///_, /////_
/__/ v1.0.0-beta.1 on ESP32

[728] Connecting to blynk.cloud:80
[819] Invalid auth token

I did not touch the original code, only entered SSID, password and auth code:

char auth[] = “bOEyio__J07DwSbEuoc2Qxa9-n_Jl4W5”;

// Your WiFi credentials.
// Set password to “” for open networks.
char ssid[] = “xxx”;
char pass[] = “xxx”;

Have had various codes sent to me, but the result is the same.

I have no idea about network technology and am therefore at my wits end. Maybe someone here has a good idea what is wrong.

Thank you in advance.

2

You seem to have the wrong Blynk library installed.
You need to un-install it, then download and install this version…

Pete.

3

Thank you very much for the very fast help!
Yes, that was indeed the cause. Now I can log on to the network, am authenticated and the pressed key is recognized; unfortunately then again an error message:

[720] Connecting to blynk-cloud.com:80
[876] Ready (ping: 44ms).
Button is pressed.
Guru Meditation Error: Core 1 panic’ed (Interrupt wdt timeout on CPU1)
Core 1 register dump:
PC : 0x00060021 PS : 0x00000001 A0 : 0x8008b3a3 A1 : 0x3ff9f870
A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000000 A5 : 0xb33fffff
A6 : 0x00000000 A7 : 0x00000000 A8 : 0x00000000 A9 : 0x00000000
A10 : 0x00000000 A11 : 0x00000000 A12 : 0x00000000 A13 : 0x00000001
A14 : 0x00060121 A15 : 0x00000000 SAR : 0x00000008 EXCCAUSE: 0x00000006
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x3ffc6af4 LCOUNT : 0x00000000
Core 1 was running in ISR context:
EPC1 : 0x4008a886 EPC2 : 0x00000000 EPC3 : 0x00000000 EPC4 : 0x4008c18e

ELF file SHA256: 0000000000000000

Backtrace: 0x00060021:0x3ff9f870 0x4008b3a0:0x00000000

Core 0 register dump:
PC : 0x4008a886 PS : 0x00060034 A0 : 0x8008b069 A1 : 0x3

Any idea what’s going wrong now?

4

Not without knowing many more details about your sketch, hardware, connected devices etc.
In fact, all the details that you were asked to provide when you created this topic.

Pete.

5

“invalid auth token” issue is fixed in v1.0.0-beta.3.
Note that using beta is not recommended for general public, as it is intended to be used only with the upgraded Blynk Cloud (however, most things will work as expected).