@vshymanskyy
But
Will “ArduinoOTA.handle();” still work ??
I worked hard on it to get it to run even if my sketch uses ISR in the background.
I found a solution and would prefer to keep it unchanged.
@vshymanskyy so just WiFi for ESP’s to start with?
As pointed out by @Brummer it will not be very pleasant if it breaks Blynker’s existing implementations of OTA. Another reason we recommend automatic updates of the app to your Smartphone is disabled until such time as the potential damage has been quantified.
Has any testing been done alongside regular OTA procedures and is the Blynk OTA disabled by default i.e if a Blynker doesn’t opt-in to use it that their own OTA system should still work?
One additional question
Is the manual update a must ?
You need to copy them manually to your sketchbook folder.
Find exact sketchbook location in File -> Preferences.
I tried to use the" Blyynk: check for updates" within the tool box
and get thees results below. @vshymanskyy
Is this o.k. ?? ore must I delete it and update manualy ???
I confirm that I was able to compile my sketch and updated it OTA using blynk v 0.4.4 and arduino V 1.8.0
But because I´m using timer interrupt I have to disable it .
I´m doing my OTA in this way:
BLYNK_WRITE(V0) // provide a push button to send the secret number to start the update
{
MY_OTA = (param.asInt()); // send #123 to start the update procedure
Serial.println(F("please start UPLOAD at IDE "));
timer0_detachInterrupt(); // interrupt will block the OTA
while (MY_OTA == 123) // <<<<<<<<< this is to avoid unintended dead loop caused by V0
{
ArduinoOTA.handle();
delay(10); // I observed that there should be a short delay
}
}