ESP8266-01 Login timeout and infinite ping

Hi. I’m trying to connect to my blynk local server with an ESP-01 module. it worked fine until today. I tried swapping to a Wemos D1 mini and it connects at the first time and with 10 ms of ping. I tried changing the hard.socket.idle.timeout in the server.properties because sometimes the ESP connects and after ~10 disconnects. I tried to install Blynk library V6.0 (instead of 6.1) but it doesn’t work.

I’m running the 0.41.3-java8 server on a Pi 3B+ connected via ethernet.

here is the serial monitor

[611258] Heartbeat timeout
[613261] Connecting to 10.0.1.100:8080
[616270] Login timeout
[618270] Connecting to 10.0.1.100:8080
[621279] Login timeout
[623279] Connecting to 10.0.1.100:8080
[626288] Login timeout
[628288] Connecting to 10.0.1.100:8080
[631298] Login timeout
[633298] Connecting to 10.0.1.100:8080
[636307] Login timeout
[638307] Connecting to 10.0.1.100:8080
[641315] Login timeout
[643315] Connecting to 10.0.1.100:8080
[646323] Login timeout
[648323] Connecting to 10.0.1.100:8080
[651332] Login timeout
[653332] Connecting to 10.0.1.100:8080
[656340] Login timeout
[658340] Connecting to 10.0.1.100:8080
[661347] Login timeout
[663347] Connecting to 10.0.1.100:8080


here is the blynk.log (set to trace)

17:24:12.675 TRACE- Incoming id=4, command=Ping, body=''
17:24:12.676 TRACE- Incoming id=5, command=Ping, body=''
17:24:21.049 TRACE- Incoming id=6, command=Ping, body=''
17:24:31.107 TRACE- Incoming id=7, command=Ping, body=''
17:24:51.438 TRACE- Incoming id=8, command=Ping, body=''
17:24:51.439 TRACE- Incoming id=9, command=Ping, body=''
17:24:51.440 TRACE- Incoming id=10, command=Ping, body=''
17:24:51.440 TRACE- Incoming id=11, command=Ping, body=''
17:24:51.442 TRACE- Hardware channel disconnect for UserKey{email='michele@blynk.cc', appName='Blynk'}, dashId 1542572586, deviceId 0, token 50fcf95dc3d4475d9e299cbbe4feb3fc.
17:24:51.442 TRACE- Changing device status. DeviceId 0, dashId 1542572586
17:24:55.051 TRACE- Blynk hardware plain protocol connection detected.
17:24:55.052 TRACE- Incoming HardwareLoginMessage{LoginMessage{id=1, command=LoginHardware, body='50fcf95dc3d4475d9e299cbbe4feb3fc'}}
17:24:55.053 DEBUG- Re registering hard channel. [id: 0xa9858b37, L:/10.0.1.100:8080 - R:/10.0.1.14:64985]
17:24:55.054 DEBUG- completeLogin. [id: 0xa9858b37, L:/10.0.1.100:8080 - R:/10.0.1.14:64985]
17:24:55.055 TRACE- Connected device id 0, dash id 1542572586
17:24:55.055 INFO - michele@blynk.cc hardware joined.
17:24:55.262 TRACE- Incoming id=2, command=Internal, body='ver

am i reading this correctly? the d1 mini connects fine and has no issues, but the esp-01 is acting up ?

I thought it was the other way around… but without any further details like what code used, whether flashing both as ESP Standalone or with AT firmware on the ESP-01 and using it as a shield, etc… no clue.

Yes. It’s like that. But I found a stranger thing. If I choose WeMos D1 in the board manager in the Arduino IDE there are no issues. If I choose generic esp8266 (with the correct settings) it doesn’t work anymore

  1. default ESP8266 standalone adding the auth token SSID and Password, ip of my server and 8080
  2. i’m using both of them as standalone. Using the -01 with at firmware and an Arduino Leonardo it connects with 15 ms of ping and no timeout of any kind

can you post your esp-01 code?

#define BLYNK_PRINT Serial


#include <ESP8266WiFi.h>
#include <BlynkSimpleEsp8266.h>

// You should get Auth Token in the Blynk App.
// Go to the Project Settings (nut icon).
char auth[] = "50fcf95dc3d4475d9e299cbbe4feb3fc";

// Your WiFi credentials.
// Set password to "" for open networks.
char ssid[] = "CASA";
char pass[] = "********";

void setup()
{
  // Debug console
  Serial.begin(9600);

  Blynk.begin(auth, ssid, pass, "10.0.1.100", 8080);
}

void loop()
{
  Blynk.run();
}
1 Like

So is there something wrong by my side?

the sketch seems ok
are you sure IP server is right?

Well, if one device is working and the other isn’t then I’d say it was either:

  • A faulty device
  • A bad flash (this is where we sit back and wait for the flasher memes to start pouring in)
  • An IP address conflict

Pete.

1 Like

I didn’t change the phisical device, i changed the board in the board manager but the esp-01 is still the same. This makes me think that there is something wrong with the esp8266 platform.

I don’t know what happened but now it seems to work. Thank you all anyway.