Reboot with the new OS7.50 from the Fritzbox 7590

PatricckW commented 1 year ago

What happened?

The WLED restarted after 59 seconds, since the new software 7.50 is on the Fritzbox and it was rebooted once. I have see this bug still on the Beta Versions from the Router, with the old OS7.29 I have no problems.

To Reproduce Bug

Install the Version 7.50 and reboot the WLED, than it will restart after 59 Sec

Expected Behavior

No reboots

Install Method

Binary from WLED.me

What version of WLED?

WLED 0.13.3 (build 2208222)

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

No response

Anything else?

No response

Code of Conduct

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

DeepflashX commented 9 months ago

Did you try the V4 version linked in this issue?

Below an "official" build of the 0.14.1 release, but with the "V4" framework ( env:esp32dev_V4_dio80 ). Please remember that "V4" is still experimental on esp32, so not recommended for production use.

WLED_0.14.1_ESP32_V4.bin.zip

esp32_bootloader_V4_dio80.zip

Please unzip, then install. For updating a previous installation, you only need to upload WLED firmware and (maybe) the bootloader. For a complete re-install, partitions.bin and app0.bin would also be necessary - not included above.

bootloader install also via wifi over the update menu? any specific order?

softhack007 commented 9 months ago

bootloader install also via wifi over the update menu? any specific order?

Bootloader cannot be modified over Wifi, unfortunately. You need to connect your board to a computer by USB, then use esptool to upload the new bootloader. See KB for more infos.

esptool write_flash 0x0 esp32_bootloader_V4_dio80.bin
esptool write_flash 0x10000 WLED_0.14.1_ESP32_V4.bin

If you want to first try updating WLED without bootloader update, that's possible via WiFi.

DeepflashX commented 9 months ago

bootloader install also via wifi over the update menu? any specific order?

Bootloader cannot be modified over Wifi, unfortunately. You need to connect your board to a computer by USB, then use esptool to upload the new bootloader. See KB for more infos.

esptool write_flash 0x0 esp32_bootloader_V4_dio80.bin

esptool write_flash 0x10000 WLED_0.14.1_ESP32_V4.bin

If you want to first try updating WLED without bootloader update, that's possible via WiFi.

well ok regarding bootloader: although I already used esptool in the past I don't have enough free time atm to do that, all my WLED Sticks are also installed.

I tried the V4 bin. As already with the normal version it took a while until it was accessible at all. Also after powerup --> maybe 5 min or so. But then it runs just smooth, no reboots. Also no reboots without fixed IP.

But as with the normal version inside of the WLED app I get a popup "error connecting to light" and then "Type Error: Cannot read properties of undefined (reading 'on)".

codmpm commented 9 months ago

But as with the normal version inside of the WLED app I get a popup "error connecting to light" and then "Type Error: Cannot read properties of undefined (reading 'on)".

Try the WLED Native App.

softhack007 commented 9 months ago

For most of the problems you still have, I guess that @codmpm might be able to help. It (might) be that you just need "ctrl-F5" to flush your browser cache.

"Type Error: Cannot read properties of undefined (reading 'on)".

This error sometimes happens when you have old presets from 0.13.x. Version 0.14.x internally uses a new format for presets; unfortunately there is no conversion tool for previous presets. It might get better when you run a "Factory reset" in WLED after updating. This erases all previous settings and previous presets, and allows you to "start fresh".

DeepflashX commented 9 months ago

For most of the problems you still have, I guess that @codmpm might be able to help. It (might) be that you just need "ctrl-F5" to flush your browser cache.

"Type Error: Cannot read properties of undefined (reading 'on)".

This error sometimes happens when you have old presets from 0.13.x. Version 0.14.x internally uses a new format for presets; unfortunately there is no conversion tool for previous presets. It might get better when you run a "Factory reset" in WLED after updating. This erases all previous settings and previous presets, and allows you to "start fresh".

after I did a factory reset now the slowness and error messages are gone as well. Now on 0.14.1 V4 with FritzOS 7.70.

rolandpj commented 9 months ago

@rolandpj Which WLED version do you use? 0.14.1-b3 or 0.14.1? Did you try the V4 version linked in this issue?

I flashed 14.1 and 14.0 via this page. https://install.wled.me. Last week i also flashed b3. On each version the same bevaviour. (with Audioreactive option and without)

DeepflashX commented 9 months ago

@rolandpj Which WLED version do you use? 0.14.1-b3 or 0.14.1? Did you try the V4 version linked in this issue?

I flashed 14.1 and 14.0 via this page. https://install.wled.me. Last week i also flashed b3. On each version the same bevaviour. (with Audioreactive option and without)

Try the V4 Version mentioned above.

rolandpj commented 9 months ago

Hi, need some assistance. Just tried to flash this manally by flashing the files to the mentioned addresses. Flash succeeded, but afterwards nothing happens. I would expect to find the WLED Accesspoint to do my WLAN configuraiton.. but it seems that it doesnt come up. Did I miss something?

codmpm commented 9 months ago

@rolandpj Have you tried a flash erase before flashing?

rolandpj commented 9 months ago

@rolandpj Have you tried a flash erase before flashing?

yes

codmpm commented 9 months ago

Confirmed. When erasing and then flashing with the V4_dio80 bootloader with esptool.py -b 460800 write_flash 0x0 esp32_bootloader_v4_dio80.bin 0x10000 WLED_0.14.1_ESP32_V4.bin I get the following via serial on the ESP32:

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371 
ets Jun  8 2016 00:22:57

Flashing using https://github.com/Aircoookie/WLED/releases/download/v0.13.1/esp32_bootloader_v4.bin instead of the dio80 one works.

@rolandpj Could you test with the normal WLED bootloader?

softhack007 commented 9 months ago

When erasing and then flashing with the V4_dio80 bootloader

Hi again. Maybe I was not explicit enough: the files I posted are not enough for a complete re-install after erase_flash. In fact the "standard WLED bootloader" is a combined file, that includes partitions.bin and app0.bin. The bootloader i posted yesterday is the pure bootloader, without these two other files.

codmpm commented 9 months ago

Understood. So write the new bootloader to 0x0 only after you've installed the "standard WLED bootloader" first?

softhack007 commented 9 months ago

Yes, for a complete re-install, the simplest approach is indeed to first install the old "AC standard" bootloader, then upload the V4 bootloader, then upload WLED_V4.

so you additionally need this file: https://github.com/Aircoookie/WLED-WebInstaller/blob/master/bin/release_0_14_1/esp32_bootloader_v4.bin (its also called "V4" however comes from the old "V3" framework)

The complete procedure for fresh install would be:

esptool erase_flash (to wipe your device)
esptool write_flash 0x0 esp32_bootloader_v4.bin (the old bootloader with all parts)
esptool write_flash 0x0 esp32_bootloader_V4_dio80.bin (the new framework bootloader without other parts)
esptool write_flash 0x10000 WLED_0.14.1_ESP32_V4.bin (WLED with new framework)

DeepflashX commented 9 months ago

What If I use the standard Bootloader with new framework as I am atm? I do not seem to have issues.

softhack007 commented 9 months ago

What If I use the standard Bootloader with new framework as I am atm? I do not seem to have issues.

Might or might not work. The bootloader initialized the board before loading WLED. Its better to use the new bootloader that was made for the "V4" framework.

Actually I have never tested the combination of "old bootloader+new framework", but you should expect some very confusing side-effects from this combination. Maybe it works first, but later you possibly have corrupted files, slow UI, not-working microphones, flashing LEDs, or other weird stuff.

My recommendation is clearly to use the right (=new) bootloader when running firmware that uses the new framework.

EDIT: sorry @DeepflashX It seems i've accidentally edited your post, instead of replying. Will try to fix that.

codmpm commented 9 months ago

@softhack007 Thank you very very much for that clarification. Could you check your WLED Discord DM's? Tried to reach you there.

softhack007 commented 9 months ago

Side-topic: you might wonder "why doesn't WLED simply move to the new framework completely"?

Well its true the new framework is needed for -S3/-S2/-C3 any way, while we stay with the older one "just" on classic esp32. Here are a few pro's and con's:

Pro new Framework

esp-idf V4.4.3 + arduino-esp32 v2.0.6 -> actively maintained by espressif
its running stable with new MCU's already (-S3/-S2/-C3)
WLED source code was already adjusted for the new framework when adding support for new MCUs
Better support for modern chip hardware (higher flash speeds, PSRAM, ...)
Better support for newer Wifi features (WPA3, enterprise WPA, etc) --> fritzBox issue solved
I (and other devs) already use it frequently for development on our own esp32 boards
Some annoying bugs finally got fixed by espressif
Some memory leaks in the UDP library finally got fixed
A few new drivers (Ethernet, DMX) are available only when using the new framework
the current "AC standard" is still on esp-idf V3.3.6-16 + arduino-esp32 v1.0.6.4 -> maintained by AC only

Contra (or unclear) for new Framework

Sporadic problems with data from previous WLED installs: flash corruption, bootloader incompatibilities, bootloops
"upgrading" by OTA is not possible (see above) because the bootloader cannot be replaced via OTA, and re-formatting the LittleFS filesystem cannot be done (atm) by WLED
new framework releases regularly break existing functionality ... cough sorry espressif, this is how it looks from our perspective
flash usage: firmware for the new framework is ~300Kb bigger when comparing to exactly the same WLED build with the old framework. For some custom builds, WLED would not fit into 4MB flash any more
More testing needed on classic esp32

BTW, framework versions are not the same as "platform" versions you find in platformio.ini (yeah, confusing)

platform = espressif32@3.5.0 ==> old framework, including ESP-IDF V3.3.6-16 + arduino-esp32 v1.0.6.4
platform = espressif32@5.3.0 ==> WLED "V4", including ESP-IDF V4.4.3 + arduino-esp32 v2.0.6
platform = espressif32@6.3.0 ==> the next possibly stable one - ESP-IDF V4.4.4 + arduino-esp32 v2.0.9

And on top of this, it seems that arduino-esp32 between v2.0.10 and v2.0.14 are broken again so not usable for WLED ....

softhack007 commented 9 months ago

@softhack007 Thank you very very much for that clarification. Could you check your WLED Discord DM's? Tried to reach you there.

Sure, will check 👍 I'm currently not so active on discord, due to time needed for "real life" and "real job"

DeepflashX commented 9 months ago

Yes, for a complete re-install, the simplest approach is indeed to first install the old "AC standard" bootloader, then upload the V4 bootloader, then upload WLED_V4.

so you additionally need this file: https://github.com/Aircoookie/WLED-WebInstaller/blob/master/bin/release_0_14_1/esp32_bootloader_v4.bin (its also called "V4" however comes from the old "V3" framework)

The complete procedure for fresh install would be:
* esptool erase_flash (to wipe your device)

* esptool write_flash 0x0 esp32_bootloader_v4.bin  (the old bootloader _with_ all parts)

* esptool write_flash 0x0 esp32_bootloader_V4_dio80.bin    (the new framework bootloader _without_ other parts)

* esptool write_flash 0x10000 WLED_0.14.1_ESP32_V4.bin   (WLED with new framework)

ok I tried that on one of my devices and according to shell everything went fine. But I don't get the AP coming up.

rolandpj commented 9 months ago

Yes, for a complete re-install, the simplest approach is indeed to first install the old "AC standard" bootloader, then upload the V4 bootloader, then upload WLED_V4. so you additionally need this file: https://github.com/Aircoookie/WLED-WebInstaller/blob/master/bin/release_0_14_1/esp32_bootloader_v4.bin (its also called "V4" however comes from the old "V3" framework) The complete procedure for fresh install would be:
* esptool erase_flash (to wipe your device)

* esptool write_flash 0x0 esp32_bootloader_v4.bin  (the old bootloader _with_ all parts)

* esptool write_flash 0x0 esp32_bootloader_V4_dio80.bin    (the new framework bootloader _without_ other parts)

* esptool write_flash 0x10000 WLED_0.14.1_ESP32_V4.bin   (WLED with new framework)
ok I tried that on one of my devices and according to shell everything went fine. But I don't get the AP coming up.

Agree, same for me

softhack007 commented 9 months ago

ok I tried that on one of my devices and according to shell everything went fine. But I don't get the AP coming up.

Do you get any messages on serial monitor?

I can double-check if my procedure works with a new esp32, but can only do that tomorrow or friday.

codmpm commented 9 months ago

I'm also willing to help and countercheck. But leaving the office now as of the weather conditions in Germany :-)

DeepflashX commented 9 months ago

repeated:

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) invalid header: 0x0ba80020 invalid header: 0x0ba80020 invalid header: 0x0ba80020 invalid header: 0x0ba80020 invalid header: 0x0ba80020 invalid header: 0x0ba80020 invalid header: 0x0ba80020 ets Jul 29 2019 12:21:46

PS: to be clear, that is putty output when connected via serial only connected to Serial Dongle without external power supply Does it make a difference with external power supply?

rolandpj commented 9 months ago

ok I tried that on one of my devices and according to shell everything went fine. But I don't get the AP coming up.

Do you get any messages on serial monitor?

I can double-check if my procedure works with a new esp32, but can only do that tomorrow or friday.

No.. seems that it run through without any errors

`c:\Temp\1111\flash_download_tool_3.9.5\flash_download_tool_3.9.5 C:\Temp\1111\esp32_bootloader_v4.bin C:\Temp\1111 C:\Temp\1111\esp32_bootloader_V4_dio80\esp32_bootloader_V4_dio80.bin C:\Temp\1111\esp32_bootloader_V4_dio80 C:\Temp\1111\WLED_0.14.1_ESP32_V4.bin\WLED_0.14.1_ESP32_V4.bin 1 kill 2 kill 3 kill test offset : 0 0x0 case ok test offset : 0 0x0 case ok .. Uploading stub... Running stub... Stub running... Changing baud rate to 115200 Changed. FLASH_CRYPT_CNT 0 ABS_DONE_0 False test offset : 0 0x0 case ok . Uploading stub... Running stub... Stub running... Changing baud rate to 115200 Changed. NO XMC flash detected! FLASH_CRYPT_CNT 0 ABS_DONE_0 False Compressed 419992 bytes to 59787...

is stub and send flash finish test offset : 0 0x0 case ok test offset : 0 0x0 case ok .. Uploading stub... Running stub... Stub running... Changing baud rate to 115200 Changed. NO XMC flash detected! FLASH_CRYPT_CNT 0 ABS_DONE_0 False Compressed 17440 bytes to 12108...

is stub and send flash finish test offset : 65536 0x10000 case ok test offset : 65536 0x10000 case ok .. Uploading stub... Running stub... Stub running... Changing baud rate to 115200 Changed. NO XMC flash detected! FLASH_CRYPT_CNT 0 ABS_DONE_0 False Compressed 1439600 bytes to 961990...

is stub and send flash finish `

wled-install commented 9 months ago

WLED 0.14.1 „V4“ (ESP IDF 4.4.3 based) for ESP32 is now available on a unofficial (but well-known) WLED installer https://wled-install.github.io/. Presently as a pure WLED, WLED with Ethernet support and WLED with Audio reactive Usermod.

If you already used this installer before (after April 2023) or your board is from shop.myhome-control.de, you can even use OTA to update to “V4” version downloaded from https://wled-install.github.io/ (however, on your own risk!) since this installer uses most compatible bootloader (in my personal experience) for all versions. There are some specialties, however: 1) Before OTA, please perform “Factory reset” (WLED Config -> Security & Updates -> Factory reset) to minimize the risk. It will erase all your settings. You have to connect to WLED-AP after that. 2) Perform OTA 3) You eventually will NOT have WLED-AP (depending on what previous version you had). But then you will find Hotspot called like ESP_xxxxxx (for example ESP_CA8866). It is WLED but with no password. You can connect to it and make settings as usual (integrate WLED into your Network etc.). After that you can work as usually. 4) There are some risk that you something could fail and you will need to reinstall via USB 5) You will check if it is “V4”: in WLED go to Info and as Environment you should have esp32 v4.4.3

Please test V4 if you have reboot issue, but there still might be some other issues mentioned by softhack007 above. Give the feedback here. If you need version compiled with special options, give me feedback here or via info@myhome-control.de. I will try to include them as soon as I can.

OTA to "V4" actually also might work if you used official WLED installer before with recent 0.14.x version. But I don’t know if it is always the case.

DeepflashX commented 9 months ago

ok so with the device I have and flashed with the procedure before and does not come up with an AP now, is that fixed with that new build? And is Loxone interaction integrated into that build?

wled-install commented 9 months ago

I belive loxone is enabled default, isnt it? I dont know what kind of issue did you have with your device, you cna try this procedure.

DeepflashX commented 9 months ago

I belive loxone is enabled default, isnt it? I dont know what kind of issue did you have with your device, you cna try this procedure.

Well the said it is necessary to also Upgrade the Bootloader Which seems reaonably me to me because all v4 builds From Air cookie run really slow and unresponsive on my devices. So I followed this procedure: https://github.com/Aircoookie/WLED/issues/2932#issuecomment-1895508724 And now There is no AP coming up at all.

wled-install commented 9 months ago

Did you try the WEB-Installer https://wled-install.github.io/ via USB? It erases flash and replaces everything including bootloader when using via USB.

DeepflashX commented 9 months ago

Tried it now and the Procedere worked. WLED AP comes up again. But at least for me the device is very unresponsive. The color wheel Shows up only for a second and disappears then. getting errors in the Web interface like connection to Light failed, type error e.nl, network error when trying to get Ressource.... I am back to the wled mm Modules build v4 b27 Loxone enabled from Patrick, that runs much better

softhack007 commented 9 months ago

Tried it now and the Procedere worked. WLED AP comes up again. But at least for me the device is very unresponsive. The color wheel Shows up only for a second and disappears then. getting errors in the Web interface like connection to Light failed.

You might still need to perform one "factory reset" after installing the V4 bin. This makes sure that the old filesystem get erased and a new one is created (V4 has a new littleFS driver). See https://github.com/Aircoookie/WLED/issues/2932#issuecomment-1894380252

rolandpj commented 9 months ago

Can someone please tell me which version i should flash, I tried a view an after flashing I am still on

Which is the right one:

wled-install commented 9 months ago

Scroll down to the version that have "ESP-IDF 4.4.3 based, EXPERIMENTAL" in description

rolandpj commented 9 months ago

oh thanks.. i didn't see that there is more than the first page 😣 I configured my WIFI after flash and it seemed to be stable BUT after Restarting it did not connect again. After a simple reboot on the GUI it works but if I disconnect from Power Supply and reconnect again it never comes online.

Flashed it several times, always the same behaviour

wled-install commented 9 months ago

oh thanks.. i didn't see that there is more than the first page 😣 I configured my WIFI after flash and it seemed to be stable BUT after Restarting it did not connect again. After a simple reboot on the GUI it works but if I disconnect from Power Supply and reconnect again it never comes online.

Flashed it several times, always the same behaviour

Maybe you have somehting connected to one of the bootstrap relevant GPIOs that prevents start from flash? What board do you have and what is connected to it?

rolandpj commented 9 months ago

I use these boards https://amzn.eu/d/7RurMI3 Nothing connected except USB C power

wled-install commented 9 months ago

I use these boards https://amzn.eu/d/7RurMI3 Nothing connected except USB C power

Which version exactely did you flash? I've just tried again, it works for me.

rolandpj commented 9 months ago

I tried these 2 images

interesting.. it seems that it comes up today. Cant understand it. but runs stable since 20 Minutes 👍

rolandpj commented 8 months ago

it stays stable up and running!.. Thanks! For me it seems if Wifi signal is around -65dbm the ESP has problems to connect to the network. (in the past I had no problems to connect at the same place). Did somebody else encounter connection issues related to signal strength?

Whats the roadmap for this version to leave "experimental" phase?

github-actions[bot] commented 4 months ago

Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs. Thank you for using WLED! ✨

rolandpj commented 4 months ago

Can I upgrade from the experimental to this version? have the changes been merged to this? https://github.com/Aircoookie/WLED/releases/tag/v0.14.4

wladwnt commented 4 months ago

Can I upgrade from the experimental to this version? have the changes been merged to this? https://github.com/Aircoookie/WLED/releases/tag/v0.14.4

No, normal WLED builds for ESP32 are still ESP-IDF 3 based and might have an issue discussed here.

Latest 0.14.4 version builds for ESP32 based on ESP-IDF V4 can be found here: https://wled-install.github.io/

codmpm commented 4 months ago

@wladwnt: Could you add Loxone+MQTT to wled-install.github.io?

wladwnt commented 4 months ago

@wladwnt: Could you add Loxone+MQTT to wled-install.github.io?

Both should be enabled by default in standard versions, I believe. Have you checked them?

codmpm commented 4 months ago

MM did not have them enabled by default. WLED-AC afaik had.

wladwnt commented 4 months ago

Then all WLED-AC versions, including the ESP-IDF V4 based builds (that solve issues discussed here), have Loxone and MQTT integrated.

NiklasH187 commented 2 months ago

I tried these 2 images

interesting.. it seems that it comes up today. Cant understand it. but runs stable since 20 Minutes 👍

I can confirm, installing the new "ESP-IDF 4.4.3 based, EXPERIMENTAL” fixed the issue for me!

Aircoookie / WLED