BLYNK
HOME       📲 GETTING STARTED       📗 DOCS       ❓HELP CENTER       👉 SKETCH BUILDER

NodeMCU 1.0 offline

Hi Pete

I am facing same problem, I am using board as NodeMCU 1.0 Baud rate 9600 and using below code. Uploaded to NodeMCU but in Blynk it is still showing me my project offline. I have also changed Auth, SSID and Pass too. Please help.

#define BLYNK_PRINT Serial


#include <ESP8266WiFi.h>
#include <BlynkSimpleEsp8266.h>
char auth[] = "XXXXXX";
char ssid[] = "XXXXXX"; //Username for wifi
char pass[] = "XXXXXX";// Password for wifi
//char server[] = "171.61.134.20";
//int port = 8080;

void setup()
{
  //Debug Consol
  Serial.begin(9600);
 /* pinMode(D1,OUTPUT);//Extend these to D8 if you are using D8 Relay
  pinMode(D2,OUTPUT);
  pinMode(D3,OUTPUT);
  pinMode(D4,OUTPUT);

  digitalWrite(D1,HIGH);//Make it LOW if you want everything to go off 
  digitalWrite(D2,HIGH);// in case of power cut
  digitalWrite(D3,HIGH);
  digitalWrite(D4,HIGH);*/

  Blynk.begin(auth, ssid, pass);
}
void loop()
{
  Blynk.run();
}

@perveshgoyal please edit your post, using the pencil icon at the bottom, and add triple backticks at the beginning and end of your code so that it displays correctly.
Triple backticks look like this:
```

Pete.

Hi Pete

Check now

IMG_0192 IMG_0191

I am using this NodeMCU

What does your serial monitor say?

Pete.

9600

That’s the baud rate, but what informations appears in your serial monitor?

Pete.

I am able to see this under serial monitor

You should be seeing some debug info in the serial monitor.
Check that you have the correct COM port selected and that your serial cable isn’t faulty.

Pete.

Yes Port is correct I checked in Device manager and same Port I selected and serial cable also not faulty. While uploading code its NODEMCU blinking

Try changing the card rate in your sketch to 74880 and upload it again, the select the same baud rate in your serial monitor.
74880 is probably the default baud rate for your NodeMCU, so this will allow you to see boot messages from the board, plus debug messages from your sketch is the same serial monitor session.

Press the reset button on the NodeMCU and you should start to see something in the serial monitor. If not then reboot your PC and try again.

Post the messages that you eventually see here (copy and paste them using CTRL A to select all and CTRL C to copy rather than posting screenshots).

Pete.

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 3584, room 16
tail 0
chksum 0xb0
csum 0xb0
v2843a5ac
~ld
[64] Connecting to Pervesh_5G

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 3584, room 16
tail 0
chksum 0xb0
csum 0xb0
v2843a5ac
~ld
[65] Connecting to Pervesh_5G

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 3584, room 16
tail 0
chksum 0xb0
csum 0xb0
v2843a5ac
~ld
[66] Connecting to Pervesh_5G

Okay, so your device is in a constant reboot cycle, probably caused by pulling GPIO0 LOW, or GPIO2 or 15 HIGH.

Remove all the connections from your NodeMCU, except the USB cable and try again.

Pete.

getting this message now.

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 3584, room 16
tail 0
chksum 0xb0
csum 0xb0
v2843a5ac
~ld
[65] Connecting to Pervesh_5G
[68] Connecting to Pervesh_5G

Assuming this is an actual 5GHz AP and not just an incorrectly named one… ESP devices only support 2.4GHz

1 Like

its working now, only issue was I was using 5GHz now to 2.4GHz

Thank you so much Pete you are really helpful

1 Like