ESP8266 Community Forum

- Fri Mar 26, 2021 3:41 pm #90940 I have a project on a Wemos D1 Mini that has been running for a year or so with occasional updates by OTA.
The device, by the way, receives and displays data over MQTT, so its WiFi is working. Except for OTA.

This morning I did another update- or I tried- but OTA fails with:
[ERROR]: No response from device

I spent the morning trying to identify if anything in my sketch could have caused this, but nothing looked suspicious. I tried reducing my program to a simple test, but still no OTA. Next, I tried running the BasicOTA example sketch. Again, no connection. I tried on a new Wemos D1 Mini and a new NodeMCU board. No connection.

ESPHome, however, does upload OTA.

The only thing that has changed on my network is that I replaced my router two weeks ago. The old router did not do WPA (yes, it's that old) and I couldn't use the latest Tasmota or ESPHome without WPA2.

Any tips of how to respond this would be appreciated.

Core Version: 2.7.4

- Sun Mar 28, 2021 4:39 pm #90961 Here's an update.
Apparently the router isn't the problem. I downloaded the IDE to an old laptop and uploaded BasicOTA by USB and then again OTA- It works as expected.
Tried it on a second PC- still working.

So OTA isn't working on my main PC. The fail is apparently just coincident with my router upgrade.

Should I delete and reinstall the IDE and the esp8266 core, or does anyone think the problem is somewhere else

- Mon Mar 29, 2021 6:11 am #90966 Did you get a Microsoft ( trade mark) update? Microsoft will without permission make what it believes to be security fixes.
Check if they messed with the firewall or any bridge network you may have. The latest update broke my OTA that was on a different network IP ( my own home network) and bridged to that of my cable router.
Unfortunately there is no way to prevent Microsoft ( trade mark) from eventually ( you can delay it) updating your PC the one you own and that Microsoft ( trade mark) doesn't own but acts as if it did..

- Mon Mar 29, 2021 11:11 am #90971 Found the problem.
For some unknown reason, my network type was set to "Public". Changing it back to "Private" allowed OTA to work.