search

Aircoookie / WLED

Control WS2812B and many more types of digital RGB LEDs with an ESP8266 or ESP32 over WiFi!
https://kno.wled.ge
MIT License
14.28k stars 3.05k forks source link

Reboot with the new OS7.50 from the Fritzbox 7590 #2932

Open PatricckW opened 1 year ago

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

softhack007 commented 1 year ago

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 commented 1 year ago

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 wled Unbenannt

softhack007 commented 1 year ago

Just to check if the current version works better,

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

PatricckW commented 1 year ago

I try version 14 but it is the same Problem

softhack007 commented 1 year ago

ok, then best to try another ESP32.

PatricckW commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

@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 commented 1 year ago

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

derpate1989 commented 1 year ago

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

image

Lollo79 commented 1 year ago

@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 commented 1 year ago

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

Lollo79 commented 1 year ago

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

PatricckW commented 1 year ago

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 commented 1 year ago

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 2022-12-11 16_23_56-Window

Lollo79 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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

SmartHomeExpert commented 1 year ago

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 commented 1 year ago

2022-12-12 20_14_10-Window on V12 i have leaved empty for no AP works, on V13 the reboots come back.

PatricckW commented 1 year ago

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 commented 1 year ago

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

Janideluxe commented 1 year ago

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

Lollo79 commented 1 year ago

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

PatricckW commented 1 year ago

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

Lollo79 commented 1 year ago

No aktual FW for 7560 is not higher than 7.29

PatricckW commented 1 year ago

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

Lollo79 commented 1 year ago

AVM is not aware of any guilt.

However, the cause of the restarts are errors in your ESP32 WLED controllers themselves. A device should never restart on its own.

PatricckW commented 1 year ago

Something new with this issue?

Lollo79 commented 1 year ago

Nope, I'm waiting for the FritzOS 7.51 to try again, because I have an IoBroker Infrastructur with scripts for the WLED Controller.

PatricckW commented 1 year ago

Fritz OS 7.51?

Lollo79 commented 1 year ago

Development does not stand still

JimlyTheReal commented 1 year ago

Hello fellow sufferers, well now I'm here too. Yes ESP32 with Fritz!OS 7.50 - after 60s reboot. Unfortunately, changing the AP setting didn't help me. Actually I only have the problem with WLED and ESP32. Less with WLED and ESP8266! And not at all, no matter which ESP, with any other software. There are no problems with the guest wifi either. Now I am speechless...

JimlyTheReal commented 1 year ago

But what I don't understand is it only affects ESP32 with WLED and Fritz!OS 7.50. No ESP32 with Tasmota for example - is it really an AVM problem then?

softhack007 commented 1 year ago

The exception dump from here points to mdns, maybe in combination with AP "always off".

It seems to be a null pointer exception deep inside espressif core components, so maybe WLED cannot do much about that. ESP8266 needs different core libraries (platform framework), which explains why only esp32 seems to be affected.

It could help to disable mDNS, by removing the mDNS name in wifi settings. Also setting AP mode to "when disconnected" may help.

softhack007 commented 1 year ago

But what I don't understand is it only affects ESP32 with WLED and Fritz!OS 7.50.

We have only heard of these problems from users of AVM Fritz.box hardware, and some UniFi devices. It seems that all other wifi routers (maybe 98% worldwide) do not cause such problems. So it might be something special that AVM does with the wifi network.

No ESP32 with Tasmota for example - is it really an AVM problem then?

Tasmota does not use mDNS, and has a different architecture, different core libraries, etc. So does not make much sense -technicially- to simply compare the two firmware, and conclude that WLED is buggy.

Edit: Seems that similar problems happen with AP from UniFi.

Holgi001 commented 1 year ago

I have a UniFi AP and the same problem

Holger

softhack007 commented 1 year ago

With FritzBox as the main DSL router, or completely without any wifi hardware from AVM?

JimlyTheReal commented 1 year ago

@softhack007: okay I'm just trying to understand it, neither WLED nor AVM, rather the combination of espressif and mDNS with some routers

softhack007 commented 1 year ago

@softhack007: okay I'm just trying to understand it, neither WLED nor AVM, rather the combination of espressif and mDNS with some routers

Yes, possibly. The exception decoder dump we have seen shows a crash inside mDNS. The root cause is still not clear - bug inside mDNS, or something completely different.

JimlyTheReal commented 1 year ago

@softhack007: okay I'm just trying to understand it, neither WLED nor AVM, rather the combination of espressif and mDNS with some routers

Yes, possibly. The exception decoder dump we have seen shows a crash inside mDNS. The root cause is still not clear - bug inside mDNS, or something completely different.

Okay i removed the default entry from mDNS - and - you said it - it ist still working - no reboort anymore.... 👍 grafik

Holgi001 commented 1 year ago

With FritzBox as the main DSL router, or completely without any wifi hardware from AVM?

I only use the fritzbox for the internet. no wifi.

PatricckW commented 1 year ago

I try that too, remove the mDNS The First time up more than a Minute, but now it reboots again all 60sec.

Take it back on my test Devolo AP and it works fine.

JimlyTheReal commented 1 year ago

I opened a service call with AVM and am in contact with them via email.

JimlyTheReal commented 1 year ago

Sorry, but AVM has closed the service call because no abnormalities can be seen in the diagnostic data. They refer to the developers of the WLED software, they should get the problem under control.

softhack007 commented 1 year ago

developers of the WLED software, they should get the problem under control.

Nice response, meaning something like "no idea - not our problem - live with it" 🤷. Did AVM indicate where to look for potential differences? Handling of network protocols, mDNS, timing of client disconnects/reconnects, 2.4Ghz band support, security (WPA2), etc? Because it must be related to something that the new AVM firmware does differently, as versions before 7.50 seem to work.

Honestly, I have no idea where to look for Wifi related problems in WLED "to get them under control". Wifi support is coming from espressif drivers, its nothing that was created by the WLED team.

Most users have routers from other manufacturers, and 95% of them do not cause such problems. So I prefer to make a recommendation to users for avoiding AVM hardware, as we have no idea what causes the problem neither "how to get it under control". So my suggestion would be to close this WLED problem report, as there is not enough information available to reproduce the problem without AVM hardware.

A workaround exists, as there are a lot of other routers to chose from that do not cause such problems.

softhack007 commented 1 year ago

Actually, if you don't mind to wipe your device before installing, and don't mind to use experimental builds, there might be a last thing you could test.

In the MM fork, we have a buildenv for ESP32 with the newer espressif framework ESP-IDF 4.4.1 / arduino-esp32 2.0.4. Its still experimental, but I use it on a few "standard esp32" devices and it works ok for me. Most important is to erase your device once before uploading, and upload in VSCode, as this also installs the right bootloader, app0 and partition table.

If the problem comes from espressif drivers, there could be a chance that the new platform framework includes a solution.

JimlyTheReal commented 1 year ago

Hi @softhack007,

Sorry for my late reply, but I'm a bit busy at the moment. I had just compiled the recommended version and uploaded it to the ERP32. The thing now runs for over 20 minutes - it never did that before! This could be the solution ;-)