WLED icon indicating copy to clipboard operation
WLED copied to clipboard

13.3 OTA on ESP3266 - Unresponsive

Open flyfishUtah opened this issue 3 years ago • 7 comments

What happened?

I did an Manual OTA update via the IP address UI of the ESP3266. Downlaoded the ESP3266 and uploaded, and it said it was successful and rebooting. Never did come onlline and connect to the network. The blue light is not on with the device. A dozen or so of the lights are on (white) with the final light being red. Has worked flawlesssly for a few years. Was on 13.1

To Reproduce Bug

Manual OTA 3266.bin file uploaded via the UI, said it was successful, and was restarting. IP address is not reachable (reserved DHCP), no blue light, with some lights on.

Expected Behavior

UI render and device reachable

Install Method

Binary from WLED.me

What version of WLED?

0.13.1 upgrade to 0.13.3

Which microcontroller/board are you seeing the problem on?

ESP8266

Relevant log/trace output

No response

Anything else?

No response

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct

flyfishUtah avatar Aug 23 '22 03:08 flyfishUtah

Today I upgraded a 8266 device from version 0.13.2 to 0.13.3 via Home Assistant and it became unresponsive / unreachable, too. I was, however, able to flash the binary WLED_0.13.3_ESP8266.bin via esptool and now it's working again.

fritzbkowsky avatar Aug 23 '22 18:08 fritzbkowsky

same here, two of my eleven wled devices misbehaved after I updated them via home assistant. The esp32 froze every 5-10 minutes and the esp8266 one every half an hour when it was turned on. I solved the issue on esp32 by reberting to 0.13.3.2. Unfortunately revelting didn't solve the issue for the esp8266 one

AlexKusnezov avatar Aug 23 '22 20:08 AlexKusnezov

I had 3 devices that became unresponsive as well. I flashed from 13.2 to 13.3 through Home assistant and they never woke up. 2 were d1 mini pro and 1 was d1 mini classic. I manually flashed them with 13.3 and things have been running well after.

mattbruman avatar Aug 23 '22 23:08 mattbruman

I ended up having to manually flash via Esphome flasher to the ESP8266, and finally got 0.13.3 to work; HOWEVER, when I tried to install my back up configs, it said it was successful, but nothing applied. Presets backup worked perfectly.

Did the same thing on my ESP32 and flashed via (via web) and both backup files applied succesfully.

Something is not working well with the ESP8266 image

flyfishUtah avatar Aug 24 '22 03:08 flyfishUtah

After uploading cfg.json immediately reboot ESP. This will be fixed in 0.14

blazoncek avatar Aug 24 '22 04:08 blazoncek

I've ended up reverting the two affected nodemcu esp9266 and nodemcu esp32 to 13.2 and then restarting home assistant. They work now. The only thing that they have both in common are playlists. The other nine devices didn't have any and the update on those went well. Maybe there's something with the playlists.

AlexKusnezov avatar Aug 24 '22 06:08 AlexKusnezov

The only difference between 0.13.2 and 0.13.3 is added support for LPD6803 LEDs and disabled WDT. WDT was causing boot and flickering issues on ESP32.

blazoncek avatar Aug 24 '22 07:08 blazoncek

How to solve this issue? I have an Athom bulb flashed ota with the same issue. Is there a way to connect ota? Do I need to open up the bulb?

thommy86 avatar Sep 22 '22 17:09 thommy86

Is this still an issue?

blazoncek avatar Nov 18 '22 17:11 blazoncek

Is this still an issue?

I reflashed to resolve it. So not an issue for me know.

flyfishUtah avatar Nov 18 '22 19:11 flyfishUtah

I also had this problem and needed to reflash the esp

PiotrMachowski avatar Nov 18 '22 19:11 PiotrMachowski

I am going to close as it was not possible to reproduce and re-flashing solved the issue. It may have been random configuration issue.

blazoncek avatar Nov 19 '22 04:11 blazoncek