Two projects, one NodeMCU

Hello Ladies and Gentlemen,

My current development platform is base on:
• ESP8266 NodeMCU over WiFi
• Smartphone OS : Android 9.0
• Blynk local server
• Blynk Library version : 0.6.0

I am looking for a way to handle to different projects with only one hardware.
I am not sure to be clear so here are the details.

A first project called project1 with authkey1.
A second project called project2 with authkey2.
A single NodeMCU that will handle both projects data and events.

Is it possible to do this with the current Blynk library?
If yes, how to proceed?
Because Blynk instance is declared in BlynkSimpleEsp8266_SSL.h as BlynkWifi<BlynkArduinoClientSecure>.

Should I just create a new instance to the object as below?
BlynkWifi<BlynkArduinoClientSecure> Blynk2(_blynkTransport);

Or is it more complicated?

Or should I proceed differently?

Many thanks in advance for your help.


I have to ask why you’re trying to do this.
Maybe if you explained more about the project and your motivation for doing this we could surest different/simpler options.


maybe possible with an esp32 , but not with a single core

Even then, there’s only one Wi-Fi radio. Not sure you could share it.



you have these choices:

a) merge both projects into one
b) use two pieces of hardware
c) have each project download the other project as an OTA (Over the air) update after a while of running

Hello Pete,

Thanks for your interest in my topic.
Main problem is: two different users with different control rights.


Hello Blynk_Coeur,

Why not single core? It should be possible to connect to the server with two different sockets! So two different instances of BlynkWifi.

My only problem is the fact that each instance connects to WiFI. There is probably a way to reuse an already established WiFi connection.


1 Like

Hello Dale,

a) is not possible because two different users with different control rights.
b) see above
c) I do not understand the strategy you use. Time share for each project?


1 Like

yes, my third option is a time sharing one

The third option can not be used in my application.

On Linux and Blynk as a client, it seems easy. Just another instance of Blynk, as you pointed. My experience is however limited to Lua, which I’m using on two devices with Linux on-board.

1 Like

I really don’t understand why you don’t use two nodemcu.
same WiFi connection, same sketch, same auth is supported !


I would have thought that Bridge was the way to go.