Device goes offline automatically in blynk app

#define BLYNK_TEMPLATE_ID "**********"
#define BLYNK_DEVICE_NAME "********"
#define BLYNK_FIRMWARE_VERSION        "0.1.1"

#define BLYNK_PRINT Serial
//#define BLYNK_DEBUG

//#define APP_DEBUG

// Uncomment your board, or configure a custom board in Settings.h

// define the GPIO connected with Relays and switches
#define RelayPin1 5  //D1
#define RelayPin2 4  //D2
#define RelayPin3 14 //D5
#define RelayPin4 12 //D6
#define RelayPin5 2 //D4

#define SwitchPin1 10  //SD3
#define SwitchPin2 D3   //D3 
#define SwitchPin3 13  //D7
#define SwitchPin4 3   //RX

#define wifiLed   16   //D0

//Change the virtual pins according the rooms
#define VPIN_BUTTON_1    V1
#define VPIN_BUTTON_2    V2
#define VPIN_BUTTON_3    V3 
#define VPIN_BUTTON_4    V4
#define VPIN_BUTTON_5    V5
// Relay State
bool toggleState_1 = LOW; //Define integer to remember the toggle state for relay 1
bool toggleState_2 = LOW; //Define integer to remember the toggle state for relay 2
bool toggleState_3 = LOW; //Define integer to remember the toggle state for relay 3
bool toggleState_4 = LOW; //Define integer to remember the toggle state for relay 4
bool toggleState_5 = LOW; 

// Switch State
bool SwitchState_1 = LOW;
bool SwitchState_2 = LOW;
bool SwitchState_3 = LOW;
bool SwitchState_4 = LOW;

#include "BlynkEdgent.h"

  // Request the latest state from the server

// When App button is pushed - switch the state

  toggleState_1 = param.asInt();
  if(toggleState_1 == 1){
    digitalWrite(RelayPin1, LOW);
  else { 
    digitalWrite(RelayPin1, HIGH);

  toggleState_2 = param.asInt();
  if(toggleState_2 == 1){
    digitalWrite(RelayPin2, LOW);
  else { 
    digitalWrite(RelayPin2, HIGH);

  toggleState_3 = param.asInt();
  if(toggleState_3 == 1){
    digitalWrite(RelayPin3, LOW);
  else { 
    digitalWrite(RelayPin3, HIGH);

  toggleState_4 = param.asInt();
  if(toggleState_4 == 1){
    digitalWrite(RelayPin4, LOW);
  else { 
    digitalWrite(RelayPin4, HIGH);

  toggleState_5 = param.asInt();
  if(toggleState_5 == 1){
     digitalWrite(RelayPin5, HIGH);

void setup()
  pinMode(RelayPin1, OUTPUT);
  pinMode(RelayPin2, OUTPUT);
  pinMode(RelayPin3, OUTPUT);
  pinMode(RelayPin4, OUTPUT);
  pinMode(RelayPin5, OUTPUT);
  pinMode(wifiLed, OUTPUT);

  pinMode(SwitchPin1, INPUT_PULLUP);
  pinMode(SwitchPin2, INPUT_PULLUP);
  pinMode(SwitchPin3, INPUT_PULLUP);
  pinMode(SwitchPin4, INPUT_PULLUP);

  //During Starting all Relays should TURN OFF
  digitalWrite(RelayPin1, HIGH);
  digitalWrite(RelayPin2, HIGH);
  digitalWrite(RelayPin3, HIGH);
  digitalWrite(RelayPin4, HIGH);
  digitalWrite(RelayPin5, LOW);
  digitalWrite(wifiLed, LOW);


  Blynk.virtualWrite(VPIN_BUTTON_1, toggleState_1);
  Blynk.virtualWrite(VPIN_BUTTON_2, toggleState_2);
  Blynk.virtualWrite(VPIN_BUTTON_3, toggleState_3);
  Blynk.virtualWrite(VPIN_BUTTON_4, toggleState_4);

void loop() {;
    manual_control(); //Manual Switch Control   

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: ```

Please keep your topic short. Explain the problem being faced in the body of the topic.

Also read this

In short
My nodemcu goes offline automatically after while without any reason and its won’t get connect to the wifi until i press reset button on nodemcu

You’re calling a function (which doesn’t exist in the code you’ve shared) thousands of times per second. This is very bad practice, and instead you should be calling this using a BlynkTimer.

You’ve used some NodeMCU pins that aren’t really useable, and if you take a look in the Settings.h tab you’ll see that the Edgent sketch uses two pins - one for the indicator LED and one for resetting the Blynk credentials. The pins that are used are defined when you choose which board type to use…

If you want to successfully use this many GPIOs then you ought to switch to an ESP32.

Also, your use of the word “automatically” when describing your problem is confusing. Far better to say that the device goes offline, and add information about how long it works for before going offline, and whether any specific actions trigger this behaviour.