In fact, this gives us a way to stop using BlynkESP8266_Lib altogether. Instead, with the next Blynk Library v1.3.0, you should be able to replace the AT firmware of your ESP8266/ESP32 with the Blynk.NCP firmware, then upload a simple sketch to your Arduino and use the full power of Blynk.Edgent + even more cool features baked into the NCP.
Let me know your thoughts about this potential shift.
The most common combination of boards when using the existing AT communication system is the original Uno and an ESP-01 or ESP-01S
The original Mega is also a commonly used board with the ESP-01/S.
The topic title says “Any Arduino + ESP8266” but you don’t mention, or have examples for these common combinations of boards.
Are they supported?
Do you have plans to release examples for them if they are supported?
This can be done. In theory, it can even be done for UNO, but OTA update for these boards is not on our roadmap.
BTW, your https://github.com/jandrassy/ArduinoOTA library is used to provide the default/reference OTA implementation for the Primary MCUs.
@Juraj yeah, I edited the post to better express this
Now, regarding Uno R4 WiFi. I was able to port the CDC Bridge and DAP functionality to Blynk.NCP. Looks working fine so far, including the debugger!
This will require a separate NCP build/variant for UNO R4 WiFi, but I’m ok with that (it was needed anyway)