Start Nodemsu after deepsleep

Solved
1

In Blynk 2.0, I use a PLUS account.
The time it takes for Nodemsu to start after deep sleep is now at least 20 seconds.
Maybe there is a deep sleep in automation?
In Blynk Legacy, 3-5 seconds were enough.

2

Are you using the Edgent example?

If so, have you considered trying static provisioning?

Pete.

3 
#define BLYNK_TEMPLATE_ID "XXXXX"
#define BLYNK_DEVICE_NAME "XXXXX"
#define BLYNK_FIRMWARE_VERSION        "0.1.0"
#define BLYNK_PRINT Serial
#define APP_DEBUG
#define LMP 13  
#include "BlynkEdgent.h"

BLYNK_CONNECTED()
 { Blynk.syncVirtual(V5);
 }

void setup() { 
    Serial.begin(115200);
    BlynkEdgent.begin();
    pinMode(LMP, OUTPUT);
    digitalWrite(LMP, LOW);
  }

BLYNK_WRITE(V5) 
  { if (param.asInt() == 0)  
      { ESP.deepSleep (15e6);
      }
    else 
      { digitalWrite(LMP, HIGH);
      }
  }

void loop()  
  { BlynkEdgent.run();
  }
4

Pete.

5

Thank you very much Pete for your active help.
I’m looking for static provisioning in Blynk

6

https://docs.blynk.io/en/getting-started/activating-devices/blynk-edgent-static-authtoken

Pete.

7

Sorry for not answering right away, this is how everything works. Thank you very much

8

Pete, good afternoon, I apologize for asking a question in this topic, please specify if the sketch contains a critical error and is uploaded by air, will it be possible to further update by air? Unfortunately, I didn’t find the answer in the help files

9

Like any OTA update, I’d imagine that if you upload a sketch with a fatal error which prevents it from working correctly then future OTA updates will be impossible.
That’s why you should always test your updates on local devices before deploying them via OTA to mission critical remote devices.

I can’t be more specific about Blynk.Air because I don’t use it - because I don’t run Blynk code on my devices so I use Arduino OTA instead.

Pete.