Reboot with the new OS7.50 from the Fritzbox 7590

[PatricckW]

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

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

[softhack007]

Actually WLED does not know what kind of router it is connecting to, as we use the standard Wifi driver from espressif.

To better understand what happens, we first need to see if you get error messages on serial interface. Please connect your device to a Computer (using USB serial), and tell us what kind of messages you get on serial monitor when the restart happens (you can use Arduino IDE serial monitor for this).

[PatricckW]

That is very difficult vor me, it is from Cod.m without USB interface, only Wifi.
I use a Fritzbox 7590 from AVM, one of the most used Routers for Privat in Germany

[softhack007]

Just to check if the current version works better,

please install WLED 0.14 (beta 0) from one of these sites:

• https://wled-install.github.io
• or from https://github.com/srg74/WLED-wemos-shield/tree/master/resources/Firmware/WLED_wemos_shield/v0.14.0-b0

[PatricckW]

I try version 14 but it is the same Problem

[softhack007]

ok, then best to try another ESP32.

[PatricckW]

I wait for a new one yes.
I geht the problem as I try the beta Version from AVM for the Router, wenn I go back to the Release all work fine, no restarts

[PatricckW]

I try it today with an Devolo Repeater, which I have converted as an access point with own WLAN SSID
No it work fine, no Reboots yet

[SmartHomeExpert]

@PatricckW: Had the same reboots after updating to fritzos 7.50.
The only quick solution was to change the WLED WiFi Access Point Setup. Set „AP opens“ to „never“.

Seems like WLED needs some WiFi information which the new fritzos doesn’t brodcast anymore…

[PatricckW]

Thank you, but "to never" means the AP will not appear again?

[derpate1989]

Hey. I have FritzOS 7.50 and 3 Wled ESP32 with no reboot problem and i dont know why, but it works Perfect.

Same with the new 0.14 Beta Update, it works Perfect with FritzOS 7.50

[Lollo79]

@PatricckW: Have the same reboots after updating to fritzos 7.50.

Bought this as a replacement and have the same problem. Is the AP Setting to "Never" can be reset with a factory reset?

[PatricckW]

I try a other Controller today, same problem (I use it with mesh)
It happen if you reboot it on the first time

[Lollo79]

Ich hab das Problem mal AVM geschildert vielleicht haben die noch eine Idee.

[PatricckW]

Ich hab das Problem mal AVM geschildert vielleicht haben die noch eine Idee.

I try that as OS7.50 was on Beta State, but it don´t help much

[Lollo79]

Ich hab das Problem mal AVM geschildert vielleicht haben die noch eine Idee.

I try that as OS7.50 was on Beta State, but it don´t help much

I have Release State OS7.50 on my FritzBox

[Lollo79]

To better understand what happens, we first need to see if you get error messages on serial interface. Please connect your device to a Computer (using USB serial), and tell us what kind of messages you get on serial monitor when the restart happens (you can use Arduino IDE serial monitor for `this).

Log:

Using 'COM3' as serial port.
Showing logs:
[17:37:03]ets Jun  8 2016 00:22:57
[17:37:03]
[17:37:03]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[17:37:03]configsip: 0, SPIWP:0xee
[17:37:03]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[17:37:03]mode:DIO, clock div:1
[17:37:03]load:0x3fff0018,len:4
[17:37:03]load:0x3fff001c,len:1396
[17:37:03]load:0x40078000,len:11536
[17:37:03]load:0x40080400,len:6404
[17:37:03]entry 0x400806b4
[17:37:04]AS: Generic I2S Microphone - left channel only.
[17:37:04]Ada
[17:37:56]Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
[17:37:56]Core 0 register dump:
[17:37:56]PC      : 0x4016c718  PS      : 0x00060930  A0      : 0x8016d0fe  A1      : 0x3ffe2210  
[17:37:56]A2      : 0x00000000  A3      : 0x00000010  A4      : 0x000000a2  A5      : 0x3ffe3e88  
[17:37:56]A6      : 0x3ffe8ab9  A7      : 0x3ffe8b5b  A8      : 0x8016c232  A9      : 0x3ffe21f0  
[17:37:56]A10     : 0x00000001  A11     : 0x3ffe8ab9  A12     : 0x000000a2  A13     : 0x00000001  
[17:37:56]A14     : 0x00060523  A15     : 0x00000010  SAR     : 0x00000010  EXCCAUSE: 0x0000001c  
[17:37:56]EXCVADDR: 0x00000004  LBEG    : 0x4000c349  LEND    : 0x4000c36b  LCOUNT  : 0x00000000  
[17:37:56]
[17:37:56]ELF file SHA256: 0000000000000000
[17:37:56]
[17:37:56]Backtrace: 0x4016c715:0x3ffe2210 0x4016d0fb:0x3ffe2290 0x4016d15b:0x3ffe22c0 0x4008c0ca:0x3ffe22f0
[17:37:56]
[17:37:56]Rebooting...
[17:37:56]ets Jun  8 2016 00:22:57
[17:37:56]
[17:37:56]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[17:37:56]configsip: 0, SPIWP:0xee
[17:37:56]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[17:37:56]mode:DIO, clock div:1
[17:37:56]load:0x3fff0018,len:4
[17:37:56]load:0x3fff001c,len:1396
[17:37:56]load:0x40078000,len:11536
[17:37:56]load:0x40080400,len:6404
[17:37:56]entry 0x400806b4
[17:37:57]AS: Generic I2S Microphone - left channel only.
[17:37:57]Ada
[17:38:56]Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
[17:38:56]Core 0 register dump:
[17:38:56]PC      : 0x4016c718  PS      : 0x00060330  A0      : 0x8016d0fe  A1      : 0x3ffe21d0  
[17:38:56]A2      : 0x00000000  A3      : 0x00000010  A4      : 0x000000a2  A5      : 0x3ffe24dc  
[17:38:56]A6      : 0x3ffe8885  A7      : 0x3ffe8927  A8      : 0x8016c232  A9      : 0x3ffe21b0  
[17:38:56]A10     : 0x00000001  A11     : 0x3ffe8885  A12     : 0x000000a2  A13     : 0x00000001  
[17:38:56]A14     : 0x00060f23  A15     : 0x00000010  SAR     : 0x00000010  EXCCAUSE: 0x0000001c  
[17:38:56]EXCVADDR: 0x00000004  LBEG    : 0x4000c349  LEND    : 0x4000c36b  LCOUNT  : 0x00000000  
[17:38:56]
[17:38:56]ELF file SHA256: 0000000000000000
[17:38:56]
[17:38:56]Backtrace: 0x4016c715:0x3ffe21d0 0x4016d0fb:0x3ffe2250 0x4016d15b:0x3ffe2280 0x4008c0ca:0x3ffe22b0
[17:38:56]
[17:38:56]Rebooting...
[17:38:56]ets Jun  8 2016 00:22:57
[17:38:56]
[17:38:56]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[17:38:56]configsip: 0, SPIWP:0xee
[17:38:56]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[17:38:56]mode:DIO, clock div:1
[17:38:56]load:0x3fff0018,len:4
[17:38:56]load:0x3fff001c,len:1396
[17:38:56]load:0x40078000,len:11536
[17:38:56]load:0x40080400,len:6404
[17:38:56]entry 0x400806b4
[17:38:57]AS: Generic I2S Microphone - left channel only.
[17:38:57]Ada

[codmdu]

I tested it with the WLAN Pixel Controller from cod.m and my FRITZ!Box 7590 (FRITZ!OS 7.50 and Firmware-Version 154.07.50).
I don't have any disconnections with WLED Version 13.3

[PatricckW]

I tested it with the WLAN Pixel Controller from cod.m and my FRITZ!Box 7590 (FRITZ!OS 7.50 and Firmware-Version 154.07.50).

Do you use Mesh on the Fritzbox?

[codmdu]

I tested it with the WLAN Pixel Controller from cod.m and my FRITZ!Box 7590 (FRITZ!OS 7.50 and Firmware-Version 154.07.50).

Do you use Mesh on the Fritzbox?

Yes, with an FRITZ!WLAN Repeater.

[Lollo79]

I Have This one ABC! WLED Controller / ESP32 and This ESP32 Dev Kit C on both the Same Problem.

[SmartHomeExpert]

I have a Wemos MINI D1 ESP32. It‘s connected to a mesh with a Fritz 1200 AX Repeater.
To change the Access Point setting did not solve the problem 100%. After ~1 day I had the reboots again. Since I deactivated and activated „never“ once more, it works again.
Very weird…

[Lollo79]

on V12 i have leaved empty for no AP works, on V13 the reboots come back.

[PatricckW]

I have a Wemos MINI D1 ESP32. It‘s connected to a mesh with a Fritz 1200 AX Repeater. To change the Access Point setting did not solve the problem 100%. After ~1 day I had the reboots again. Since I deactivated and activated „never“ once more, it works again. Very weird…
IF you reboot it manuall, it starts with the reboot again

[Holgi001]

I have the same problem with AP from UniFi. After the last update last week. before everything was ok.

[Janideluxe]

same problem here also with UniFi Access Points. Fritz OS 7.50 on Fritzbox 7590 is running too, but wifi is dissabled.

[Lollo79]

Have a old 7560 as WLAN-Bridge no Mesh own SSID, Configured and no Restarts.

[PatricckW]

It happened after the first restart, do the 7560 still have os7.50?

[Lollo79]

No aktual FW for 7560 is not higher than 7.29

[PatricckW]

With the os7.29 is all fine, that is the problem, it start with OS7.50.
I use a Devolo repeater as AP with own WiFi, and is still working

[rolandpj]

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]

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]

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]

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]

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

[wladwnt]

@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]

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

[wladwnt]

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

[NiklasH187]

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!

[MeisterBoeck]

Had "Reboot Problem with ESP32 controller version V.0.10 from cod.m in combination with FRITZ.BOX router as well!
Controller went off after certain time, not exactly after 60 sec. Sometimes earlier, sometimes minutes later.

Tried two firmware versions to fix it.
a) WLED_0.15.0-b7_ESP32.bin
b) https://github.com/Aircoookie/WLED/files/10897217/WLEDMM-0.14.0-b2.19_esp32_4MB_V4_S.bin.zip

Result:
a) no solution / Problem still exists
b) Problem didn´t occur again -> fixed

Can you pls. work on a fix for the actual firmware?
Many thanks in advance!!!!!

[wladwnt]

@MeisterBoeck
Meanwile you can compile it yourself with few clicks using https://wled-compile.github.io/ and esp32-wrover as basis since it was moved to ESP-IDF V4 recently.

1. Go to online compiler linked above
2. In Step 1 select "original Aircoookie", branch "0_15", Board type "esp32_wrover"
3. in Step 1a tick checkbox "Redefine board type" and enter esp32dev in text field (it is vanilla board type)
4. in Step 5 click "start compile/build", wait a little bit and downlaod resulting wled.bin file.

[codmpm]

Thank you @wladwnt. Could you confirm that the wrover binaries work on wroom modules?

---

I just compiled the current moon modules version with IDF V4, Loxone Support as well as MQTT enabled. WLEDMM 0.14.1-b32.41.dev (build 2411150). These work on the cod.m controllers with ESP32 (V0.8/V0.10)
WLEDMM 0.14.1-b32.41.dev_ESP32_4MB_V4_S-loxone.bin.zip

[PatricckW]

Also bei mir Funktioniert diese Version, wie auch die damalige Beta ohne abbruch über nen AVM Repeater mit 7.58 und dem OS 8 der 7590 Gruß Patrick

…

------ Originalnachricht ------ Von "Patrik Mayer" ***@***.***> An "Aircoookie/WLED" ***@***.***> Cc "PatricckW" ***@***.***>; "Mention" ***@***.***> Datum 27.11.2024 11:21:29 Betreff Re: [Aircoookie/WLED] Reboot with the new OS7.50 from the Fritzbox 7590 (Issue #2932)

Thank you @wladwnt <https://github.com/wladwnt> -------------------------------------------------------------------------------- I just compiled the current moon modules version with IDF V4, Loxone Support as well as MQTT enabled. WLEDMM 0.14.1-b32.41.dev (build 2411150). WLEDMM 0.14.1-b32.41.dev_ESP32_4MB_V4_S-loxone.bin.zip <https://github.com/user-attachments/files/17932706/WLEDMM.0.14.1-b32.41.dev_ESP32_4MB_V4_S-loxone.bin.zip> — Reply to this email directly, view it on GitHub <#2932 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2Q7PMQYE2WF4NUKVGMSNHD2CWMKRAVCNFSM6AAAAAASYE5QSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBTGQ4DONZRGY>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[PatricckW]

I need to downgrad it to 0.14.0.b27
0.14.1.B32 runs stable, without WiFi interruption. However, when I send Http commands via Loxone, it no longer does what it should. With the old version it works again

[wled-compile]

Thank you @wladwnt. Could you confirm that es wrover binaries work on wroom modules?

I havn't tried, but if the board is redefined as esp32dev as I described, then is in't rover binary any more but wroom.

[chrisp1001]

@MeisterBoeck Meanwile you can compile it yourself with few clicks using https://wled-compile.github.io/ and esp32-wrover as basis since it was moved to ESP-IDF V4 recently.

1. Go to online compiler linked above
2. In Step 1 select "original Aircoookie", branch "0_15", Board type "esp32_wrover"
3. in Step 1a tick checkbox "Redefine board type" and enter esp32dev in text field (it is vanilla board type)
4. in Step 5 click "start compile/build", wait a little bit and downlaod resulting wled.bin file.

Can someone tell me what configuration I need to define if I want to keep the 0.14 release? "esp32_wroover" is not available here as Board Type.

I tried this config however the problem persisted:

[env:custom_build] extends = env:esp32dev board = esp32dev build_flags = ${env:esp32dev.build_flags} -D WLED_USE_ETHERNET -D WLED_ENABLE_LOXONE -D WLED_ENABLE_WEBSOCKETS

[wled-compile]

In 0.14.x releases you can try esp32dev_V4_dio80 as a basis enviroment. But I am not sure how good it works. Use only if you have possibility to reflash via USB in case of issues. Eventually redefine flash frequency to 40000000L.

[MeisterBoeck]

thank you @chrisp1001, unfortunately I am still learning and not very much in the technical details to test your version. I am waiting for final "sign off" of @codmpm for the new firmware, as he can ensure that the cod.m board works fine with Loxone in a fritz.box environment

[chrisp1001]

In 0.14.x releases you can try esp32dev_V4_dio80 as a basis enviroment. But I am not sure how good it works. Use only if you have possibility to reflash via USB in case of issues. Eventually redefine flash frequency to 40000000L.

That works like a charme on my controller https://www.tindie.com/products/bong69/8-port-led-distro/. Thank you!

My config for the 0.14.4 realese on https://wled-compile.github.io/:
[env:custom_build] extends = env:esp32dev_V4_dio80 board = esp32dev board_build.f_flash = 40000000L build_flags = ${env:esp32dev_V4_dio80.build_flags} -D WLED_USE_ETHERNET -D WLED_ENABLE_LOXONE -D WLED_ENABLE_WEBSOCKETS

[codmpm]

They key is env:esp32dev_V4* as this uses ESP-IDF V4 where the Problem is fixed.
@MeisterBoeck, what @chrisp1001 uses should work totally fine, but please omit WLED_USE_ETHERNET.

[codmpm]

Sadly 0.15 does not fix the Fritz!Box issue.

WLED 0.15 is still compiled against Espressif IDF V3.5.0: https://github.com/Aircoookie/WLED/blob/main/platformio.ini#L243
WLED-MM with build target esp32_4MB_V4_S - which fixes the problem - currently uses Espressif IDF V6.3.2: https://github.com/MoonModules/WLED/blob/mdev/platformio.ini#L440 (correct me if I'm wrong)

As far as I know, the problem does not occur since Espressif IDF V4.

@softhack007 could give any info if the switch to the newer IDF is planned for mainline WLED?