Open Boards Manager from Tools > Board menu and install esp8266 platform (and don’t forget to select your ESP8266 board from Tools > Board menu after installation).
Well, I know it was updating as after one update, weeks ago, it developed OTA issues, which was fixed in the next update… but the file name always stayed the same… so who knows…
Earlier today I ended up wiping it (the espressif folder) out, updating the IDE to 1.8.5, reinstalling the ESP32 core… and all the Blynk libraries for good measure, since the ESP32 showed up on the Serial Monitor as v0.4.8 on Arduino… but after, the Blynk msg still shows as Arduino… so who knows about that.
So now I now have the latest ESP32 core for sure… but the former stability in my 24/7 running project seems to have become mildly unstable… Go figure… next update I guess…
Interesting to see if this file changes next update or not.
We still have some Blynkers running the old 2.3.0 core. Not only is WPA2 compromised, it’s old rubbish. Do yourselves a favour and get on to 2.4.0-rc2.
Not that it’s old rubbish, previous version was much better, it’s full of bugs and using 2.3.0 core made my life total misery in last few days, can’t even describe what I have been trough. Thanks to Costas and 2.4.0rc2 update, problem solved. So do not even try to run your projects on 2.3.0 core.
Hello @Costas, I found (I think) something for not to change to 2.4.0…
I was working yesterday with 2.3.0 version with no problem in all nodemcu and a small esp8266-1
Today I switched to 2.4.0 (also 2.4.0-rc2) version but my “before working project” don’t it does not set the esp8266-1 to AP mode using wifimanager as it does with 2.3.0.
I switched back to 2.3.0 and same code works flawlesly…
This is what I call a weird situation… I found the problem, it was a hardware problem, but it’s very curious…
I see that after some time, the esp runs ok with version 2.4.0 so I check hardware side
Removing the esp8266-1 from the device where it was installed I broke the link between reset and 3.3v
There is no problem programming the esp without 3.3v on it
Also seems that running without this pin to high is not a problem on 2.3.0 version, because it works!
As I said before, after some time, the esp works fine (I suppose that there was some noise on this pin and finally it starts…)