Already lined up 😉 Stay tuned…

I m agree with that. Why use 2 esp32 ?

There is some restrictions while using wifi and esp now: esp now must keep the same wifi channel and the router change it automatically but unfortunately esp now not. I'd like to use both for my projects, specially thinking OTA firmware updates. Do you have some solution or demo project to workaround this issues?

@@Maertaugh When using only one esp32 module to switch between esp_now and wifi (lan) it will stop receiving data from other esp-now end devices (sensors modules). Imagine this scenario when there are many esp_now devices. Also every wifi routers (even the ones we use at home) are constantly switching channels. This is for security reasons and in response all wifi devices switch to the changed channel to match the router so they can continue to maintain active connections. To be connected to the wifi your ESP_NOW gateway device should be switching the channel appropriately to maintain active wifi connection with your home router. But EPS_NOW mandates that all esp-now (peers) devices/modules should be configured to use the same static channel. Well, if your router switched to a diff channel and yoru esp_now g/w did not, then there is no connection. This is why 2 esp32 modules are used here. 1 to act as a receiver/coordinator for all esp-now peer devices and the 2nd acts as a wifi gateway module to your home wifi network and the two modules are communicating over the RX2 and TX2 pins using UART. Hope this helps.

virtual pins are just channels that constantly update data. they're just observables in the cloud. you can use i think up to 10 virtual pins (paired with a data stream) per template in Blynk cloud, assigning a data type, min-max values, etc. your devices will subscribe to the virtual pin/channel (BLYNK_WRITE), and whenever data changes in the channel, the devices react via their handlers. and your devices can also write values to that channel (Blynk.virtualWrite()) and will update that virtual pin's value and rebroadcast the change.

I have question 1 too. Why did we need a dedicated ESP1?

For question 1; It's doable, using one esp board to handle both espnow and blynk; but it's some what complex; because espnow need the channel to be fixed, like channel 4, but WiFi which access blynk is prone to changing fore instance when using one hotspot to another, that will cause not reliable espnow communication. But having one board handle espnow communication will allow it's channel to be fixed while allowing the other to be free roaming. for question 2; I think you better look for mesh network like topology,

Found any solution

Blynk has a limit for how many devices are connected to it. Also, the amount of data received by Blynk is another limitation.

Hum khud bechte h humari website se

@@techiesms web site ka naam kya hai. Actually maine aap ka channel kal subscribe kia hai. I like these type of projects.

@@techiesms rasberry pie b mil jaae ge

techiesms.com/components/

Monitor temperature augmented reality script is not working