Troubleshooting Edgent Dynamic Provisioning Problems

There seems to quite a bit of confusion about how the dynamic provisioning process works in the Edgent sketch examples, and how to re-provision a device with new WiFi credentials. Many people omit to configure the board type correctly in the sketch, and this also causes problems.

Here’s a guide to how the process works, and the things to watch out for…


You start by creating a template, preferably in the web console (

This gives you the BLYNK_TEMPLATE_ID and BLYNK_DEVICE_NAME that you copy/paste into the Edgent example sketch, replacing the existing lines of code that are commented-out.

To do the Edgent provisioning/reprovisioning process correctly need a physical switch and an LED connected to your board. Some boards have these already, some need to have them added by you. This is covered in detail in the “Defining your physical switch and LED” section below.

In the app you then use the “+ Add New Device” option to connect to the device and supply the WiFi credentials.

The WiFi credentials (and the current Auth token) can be cleared by pressing and holding the physical button for 10 seconds. New WiFi credentials and a new auth token can be provisioned to an existing device using the “Reconfigure” option in the app.

Be careful with the length of your BLYNK_DEVICE_NAME

The Device Name is the name that you provide when you create the template, and the Edgent sketch then adds additional characters that are derived from the Chip ID of the device to give the SSID which is used when the app connects to the device during the provisioning phase.
If the device name + Chip ID exceed 32 characters then the provisioning process won’t complete successfully, so keep the template name to a reasonable length.

Defining your physical switch and LED

This is the area that is probably most confusing to new users of the Edgent sketch, especially if they are unfamiliar with the #define, #if defined, #elif and #endif commands in C++

I’ll use the Edgent_ESP8266 sketch as an example, but the same principals apply to the ESP32 sketch as well.
The Edgent_ESP8266.ino file (the first tab in the Arduino IDE) contains the following lines of code:

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

Notice that all of these board types are commented-out by default.

Your first task should be to un-comment one of these board types, then look in the Settings.h tab so that you understanhd what the code is doing, and what additional steps you may need to take.

If the board you are using isn’t listed here then leaving all of the board types commented-out will cause the sketch to use the “Custom board configuration” from the Settings.h tab, and you need to edit this custom configuration to suit your hardware.

This is what the relevant parts of the standard Settings.h file look like:

 * Board configuration (see examples below).

#if defined(USE_NODE_MCU_BOARD) || defined(USE_WEMOS_D1_MINI)

  #define BOARD_BUTTON_PIN            0
  #define BOARD_BUTTON_ACTIVE_LOW     true

  #define BOARD_LED_PIN               2
  #define BOARD_LED_INVERSE           true
  #define BOARD_LED_BRIGHTNESS        255


  #define BOARD_BUTTON_PIN            0
  #define BOARD_BUTTON_ACTIVE_LOW     true

  #define BOARD_LED_PIN_WS2812        4
  #define BOARD_LED_BRIGHTNESS        64

#elif defined(USE_WITTY_CLOUD_BOARD)

  #define BOARD_BUTTON_PIN            4
  #define BOARD_BUTTON_ACTIVE_LOW     true

  #define BOARD_LED_PIN_R             15
  #define BOARD_LED_PIN_G             12
  #define BOARD_LED_PIN_B             13
  #define BOARD_LED_INVERSE           false
  #define BOARD_LED_BRIGHTNESS        64


  #warning "Custom board configuration is used"

  #define BOARD_BUTTON_PIN            0                     // Pin where user button is attached
  #define BOARD_BUTTON_ACTIVE_LOW     true                  // true if button is "active-low"

  #define BOARD_LED_PIN               4                     // Set LED pin - if you have a single-color LED attached
  //#define BOARD_LED_PIN_R           15                    // Set R,G,B pins - if your LED is PWM RGB
  //#define BOARD_LED_PIN_G           12
  //#define BOARD_LED_PIN_B           13
  //#define BOARD_LED_PIN_WS2812      4                     // Set if your LED is WS2812 RGB
  #define BOARD_LED_INVERSE           false                 // true if LED is common anode, false if common cathode
  #define BOARD_LED_BRIGHTNESS        64                    // 0..255 brightness control


The first section starts with #if defined(USE_NODE_MCU_BOARD) || defined(USE_WEMOS_D1_MINI)

In plain English this means, “If you’ve uncommented either the #define USE_NODE_MCU_BOARD or #define USE_WEMOS_D1_MINI lines of code in the first tab of the sketch, then the following settings will be used for the physical button and LED”.

The NodeMCU board has 2 physical buttons:

The button on the bottom left is labelled RST and the one on the bottom right is labelled FLASH.

The FLASH button is connected to GPIO0 (the pin labelled D3 on the board). When the button is pressed, GPIO0 is connected to GND (LOW).

All NodeMCUs that I’ve come across also have a built-in LED (located up near the top right of the board) which is connected to GPIO2 (the pin labelled D4). This LED lights-up when GPIO2 is pulled LOW, so has what is known as inverse logic.
Some NodeMCUs also have an additional LED (down near bottom left of the board) which is connected to GPIO16 (The pin labelled D0). This LED also works in “Inverted” mode – it lights-up when the pin is pulled LOW.

Going back to the standard settings for the NodeMCU/Wemos D1 Mini board, you should now understand these settings in relation to the board, but I’ve added some comments next to each line to explain them further…

#if defined(USE_NODE_MCU_BOARD) || defined(USE_WEMOS_D1_MINI)

  #define BOARD_BUTTON_PIN            0      <<<< The FLASH Button
  #define BOARD_BUTTON_ACTIVE_LOW     true   <<<< Pressing the button pulls the pin LOW

  #define BOARD_LED_PIN               2      <<<< The LED is connected to GPIO2 (D4)
  #define BOARD_LED_INVERSE           true   <<<< The LED lights when the pin is LOW
  #define BOARD_LED_BRIGHTNESS        255    <<<< Make the LED shine at max brightness when lit

If you’re using the Wemos D1 mini, it is very similar:

but you’ll notice that it only has one button labelled RESET (same as the RST button on the NodeMCU).
It doesn’t have the FLASH button, so you’ll need to add a physical momentary push to make button in order to be able to clear the stored credentials if ever you need to re-provision the board.
One side of the physical push button will connect to the pin labelled D3 and the other side to GND (because we have this line set to true:
which means that when the button is pressed the GPIO0 (D3) pin is pulled LOW).

Of course, if you wanted to, you could simply use a jumper wire, bent paperclip or anything else that’s conductive to short-out pin D3 and GND for 10 seconds if you are feeling lazy :wink:

So, if you don’t un-comment one of the pre-defined board types, the custom board type configuration will be used. That looks like this:

  #warning "Custom board configuration is used"

  #define BOARD_BUTTON_PIN            0                     // Pin where user button is attached
  #define BOARD_BUTTON_ACTIVE_LOW     true                  // true if button is "active-low"

  #define BOARD_LED_PIN               4                     // Set LED pin - if you have a single-color LED attached
  //#define BOARD_LED_PIN_R           15                    // Set R,G,B pins - if your LED is PWM RGB
  //#define BOARD_LED_PIN_G           12
  //#define BOARD_LED_PIN_B           13
  //#define BOARD_LED_PIN_WS2812      4                     // Set if your LED is WS2812 RGB
  #define BOARD_LED_INVERSE           false                 // true if LED is common anode, false if common cathode
  #define BOARD_LED_BRIGHTNESS        64                    // 0..255 brightness control

As you can see, this uses GPIO0 (Pin D3) for the physical pushbutton switch, but GPIO4 (pin D2) for the LED. It also has the option to un-comment additional lines of code that allow an RGB or WS2812 RGB LED to be used.

If you didn’t un-comment any board types, and allowed the custom board configuration to be used, then with a NodeMCU the built-in LED wouldn’t flash to indicate provisioning or pulse to indicate normal running. But, pin GPIO4 would still be receiving these pulses from the sketch, and if you had a sensor or relay attached to GPIO4 then this could provide unexpected results.

So, the important points are:

  • Un-comment the correct board type

  • Check the Settings.h file to ensure that the selected board type does actually match your hardware setup

  • Add a physical button to the Wemos D1 mini if needed

  • Use the custom board configuration of you have an unusual type of board, but edit the custom section of Settinsg.h to make it match your hardware.

  • Ensure that you don’t use the GPIOs assigned to the button or LED pins for anything else in your sketch.

Initial Provisioning

Once you’ve added the BLYNK_TEMPLATE_ID and BLYNK_DEVICE_NAME to your sketch, configured the correct board type and uploaded the sketch to your board you are ready to do the provisioning.

It’s always a good idea to have the board connected to your computer and the serial monitor open, so that you can see the debug information that’s being provided in the serial output.

The LED on the board should be flashing quickly.

Open the app and tap the three horizontal bars in the top right-hand corner then tap “+ Add new device”. Choose “Connect to WiFi” and confirm that the device is ready to be provisioned (LED blinking) by tapping “Ready” in the app.

The app will then scan for devices waiting to be provisioned, and show you the device details and ask for permission to join the network (select Join), then ask you to select the SSID and enter the WiFi password.
Once you’ve done this the data is sent to the device and stored in it’s EEPROM, and you can exit the “Add device" when asked (Apply, Done, Exit to App).

The device will then appear in the initial screen of the app, ready to have widgets added to its mobile dashboard.

Troubleshooting the provisioning process

If the LED on the board isn’t doing anything, then go back and check the “Defining your physical switch and LED” section to ensure that the LED and switch are defined correctly, and that you don’t have any peripherals also using the LED or Switch pins.

If the LED is pulsing slowly then the board thinks it’s already provisioned. Follow the instructions in the “Reprovisioning new WiFi credentials” section below.

If the LED is flashing quickly, but the device doesn’t show-up in the app when you tap the “Ready” button in the app then check the following:

  • The Template name isn’t too long (see the “Be careful with the length of your BLYNK_DEVICE_NAME” section above)
  • The template ID and device name in sketch are EXACTLY as they appear in the web console
  • The app is signed-in to the same user account as the web console, or
  • The user has permission to provision new devices.

Reprovisioning new WiFi credentials

If you’re having problems provisioning a device, or you’ve accidentally entered the wrong WiFi credentials, then press and hold the physical button (the one defined in Settings.h for your board type) for 10 seconds. This will clear the stored credentials and te LED will start flashing quickly, and allow you to either repeat the provisioning process, or if the device has already been created in the app you can re-provision it.

To re-provision an existing device, tap on the device in the app, then tap the three dots in the top right hand corner of the app screen. This will bring-up the device information/timeline screen.
Tap on the three dots in the top right hand corner once more, and this will pop-up a dialog that allows you to “Reconfigure”, “Erase all device data”, “Delete Device” or “Cancel”.
Choose “Reconfigure” and this will take you back into the provisioning process described in the earlier section.
If the wrong SSID was selected and/or the password was entered before then take care to enter the correct information rather than using the credentials stored in the app.

PLEASE - Don’t post general provisioning questions in this topic

I’ll leave this topic open for constructive comments, as I’d like to know if there are any mistakes, ambiguities or important areas that I’ve forgotten to cover - or if the process is different in any way when using the Android app (I’m an iOS user).
However, I’d like the topic to be a simple reference for others to follow, so don’t want it to be cluttered-up with “I get this error message, please help me” type of comments. If you post these types of comments then they will simply deleted.


Edgent_ESP32 example not connecting to Blynk with error
Help for EDGENT aplications
Change ssid credentials on blynk edgent
Soil moisture giving false values when connected to 74hc4067 16 channel multiplexer
Help Please, i cannt connect my esp32 to blynk - Invalid auth token
BlynkEdgent Based Sketch Cannot Connect to Wifi
Blynk not working with ESP-01S microcontroler
EDGENT for esp Constantly goes offline
Blynk app can not connect to device(esp8266)
Convert legacy blynk code to blynk iOT
WiFi Credentials not Being Saved
My ESP 32 Device LED is not blinking
Blynk, NRF24l01 and esp handling multiple sensors
Problems with ESP32 and DS18B20
Blynk Configuration problem
Can I use an active high button to reset WIFI provisioning
Problem with ultrasonic+esp8266 when use blynk
ESP32 with Blynk 2.0 facing problem to drive high power 3W led in parallel
ESP8266 problem sketch error
ESP8266 problem sketch error
ESP8266 Stand alone no work
Why can't I send information Powermeter (modbus) (use RS485) to Blynk?
OTA Update - Firmware version mismatch
Wemos lolin32 ESP32 - Arduino Reconfiguration Reset and Led
Esp-07 add device problem
ESP8266 problem with Blynk edgent
Max30100 not working with blynk 2.0
ESP32: SDcard and blynk not functional at the same time
Incorrect ADC values while using blynk
Why Can I not provision Esp 32?
Cant connect any device Blynk 2.0
Please Help Me.I have a problem esp32 with mq2
Blynk.virtualWrite - 'Blynk' does not name a type
Blynk.edgent often sending a Nan value of DHT sensor
Blynk.edgent often sending a Nan value of DHT sensor
Blynk Edgent with DS18B20 on ESP32
My template id is not exist and the APP's display sometimes changes
Weather station blynk 2.0
Problems provisioning board when using Edgent
My first Blynk Project with HX711 & NodeMCU
Changing WiFi network
Connecting to - Secure connection failed
Can't connect new device in Blynk 2.0 application
Problem ESP8266 wifimanager conect Blynk
Problem ESP8266 wifimanager conect Blynk
Help me to reset wifi login pasword from my device
Connecting to
ESP8266-1 standalone will not connect to Blynk
Connecting to
BlynkEdgent.h failed to read sensor
Problem with OTA on ESP32, Error during update
How to "wipe" a device for a new user and new wifi provisioning
Strange i2c behavior with esp32 and Blynk
How to delay the Servomotor Blynk2.0?
Device won't go online
Connection With Device Was Interrupted Blynk 2.0
EDGENT_ESP8266 sample code in Arduino IDE has problems
Problem using multiplexer with NodeMCU v3 and Blynk
ESP8266 network problem
Migrating from using Blynk.begin(auth,.... to Edgent
OTA using ESP8266 working but seems to lose configuration after several hours
D3 and D4 are not working in my project
WEMOS D1 R2 no show temporal wifi
Use blynk anywhere
Wifi reconfigure issues
Blynk disconnects the relay when Wifi disconnects
Blynk 2.0, DS18b20, lcd 20x4 not working

Pete, :pray: your talent is needed to improve our docs! Would you consider? :wink:


@Pavel that sounds too much like work for my liking :grinning:



@PeteKnight This will be helpful for many Blynkers, thank you! If that sounds good to you, we can share via our broader channels as well (eg blog)

That’s fine by me @iryna_l, glad you think it will be useful.


1 Like

Thanks Pete. Fabulous stuff, thanks so much. If you could highlight an obvious but also tricky aspect especially when hotspotting the device, but not only then. The phone might not see the device because it is automatically connected to 5G Wifi. I have a mesh Wifi and the switch between frequencies is not always obvious, hence the phone might be on 5G Wifi, so it is blind to the device.

:grinning: Pete that was the best explanation on how to connect your wemos D1 mini I have seen yet ! thank you for taking the time to help out all our Blynkers…

1 Like

I was having some real difficulty with Edgent and between this guide and a few PMs with Pete, I have solved them all and I am SO THANKFUL.

1 Like

Thanks Pete!

1 Like

Nice work Pete , one issue I had was that on my android phone I had to connect to the 2.4G wifi to get provisioning going. But by default it goes to the 5G wifi - which can be tricky to avoid in some circumstances and if forgotten about is very frustrating in the provisioning process -because it does not work… Other phones might be able to run 2.4 and 5g at the same time but I have not investigated this.

1 Like

That’s a good point, most boards only support 2.4Ghz WiFi connections so it’s worth checking that the SSID you’re choosing is compatible with your device.


Pete - an excellent posting for helping a newbie with this! One thing that might be helpful to add is a short explanation on what’s going on behind the scenes? Sort of a step by step process overview on Edgent? Here’s where I’m still confused even though I’ve successfully got it to work. Going thru the whole process, uploading the Edgent example code to the processor (NodeMCU in my case) then compiling the Blynk functional source code, export the binary file and upload that with the OTA feature on the Blynk web portal. For subsequent Blynk source code OTA updates does that source code also need to contain the ALL the Edgent code found in the example file (ex - BlynkEdgent.begin in void setup, in void loop, tabs like Settings.h, etc)? My confusion is about whether or not the Edgent example code initially uploaded to allow the 1st OTA continues to function with any subsequent OTA updates or does it need to be renewed with each new OTA?

You’ve written that as though you think that both steps are necessary to get Edgent to work.
Using Blynk.Air is totally optional, but as with any OTA system you need to prepare your device to listen for OTA updates by first of all uploading the sketch via USB cable.

Yes. That code is what makes all of the Edgent functionality - including OTA and dynamic provisioning - work. If you try to remove it then the code probably won’t compile, and even if it does it won’t function correctly when uploaded either via USB or OTA.

Personally, I’m not a great fan of Edgent. It has some great functionality, but it’s too complex for most people (including myself) to fully understand. It also takes-up two additional GPIO pins, and if youre using a ESP8266 based board then you may not have useable pins available.
99% of projects that most people create don’t need dynamic provisioning or OTA that works outside of the home network. Even if they do want OTA from anywhere in the world then it’s a simple task to just add that into your sketch like this…

This guide was just written because I was tired of keep explaining the same things about board types and Settings.h and its simper to write it once then link people to it when they have an issue.


1 Like

Thx much! - Excellent response as usual…

1 Like