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.46k stars 3.09k 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

codmpm commented 1 year ago

Got feedback from one of my customers with the esp32 variant and it seems to work. Thank you @softhack007. I also tried this version for the esp8266 (esp8266_4MB_S) but that did not work for another customer.

Is the esp32_4MB_V4 a newer espressif IDF version than esp8266_4MB_S?

softhack007 commented 1 year ago

@codmdu Thank you for the feedback, very much appreciated 👍

Is the esp32_4MB_V4 a newer espressif IDF version than esp8266_4MB_S?

Indeed, it is. ESP32 is based on ESP-IDF, while ESP8266 has a completely different OS/framework (=not ESP-IDF). MM "esp8266_4MB_S" is using the same 8266 platform framework as in the "vanilla AC" version. So in case there are also problems with 8266 and FritzOS, a different solutions needs to be found.

MM "esp32_4MB_V4" is an experimental build using framework = espressif@5.1.1 (ESP-IDF 4.4.1 / arduino-esp32 2.0.4), while the standard ESP32 build has framework = espressif32@3.5.0 (ESP-IDF 3.3.5 / arduino-esp32 1.0.6.4). Unfortunately we cannot simply upgrade the framework, as there are many subtle differences, breaking changes, compatibility problems, and lots of new bugs in ESP-IDF 4.4.x (like random crashes when AsyncWebServer uses LittleFS) ... So I would not recommend to use a "V4" build for customer projects - unless you have no other options left.

codmpm commented 1 year ago

We still ship 0.13.3 AC. Currently only two of our customers had the OS 7.50 Problem... both using repeaters (IIRC). One is the issue starter @PatricckW. Only ESP32 are sold since a year or something. So, if someone has the issue we can point to the MM-binary for now.

So no sollution for the esp8266 currently. I see that it's not trivial to simply compile with the newer IDF. Maybe I just upgrade him to a newer Controller.

Any ideas on when the newer IDF will land in WLED AC? Thank you.

PatricckW commented 1 year ago

I try it wenn I get it from @codmpm I have no restarts now.

Some other Problems come up as I try restore a Backup from my Controller with13.3 and my Http do not realy work on the update one.

So I change back to the Controller with 13.3

But I will retry it again it I have more time to test.

codmpm commented 1 year ago

For these who want to test, here's the esp32_4MB_V4_S binary. Simply flash it through Manual OTA. But keep in mind what @softhack007 said about maturity of the code..

WLEDMM-0.14.0-b2.19_esp32_4MB_V4_S.bin.zip

WLEDMM_0.14.0-3a294d0852bf8f16534bed3a976493bbaac21aa6_esp32_4MB_V4_S-loxone.bin.zip (Loxone enabled)

DeepflashX commented 1 year ago

hello and good day,

is this fixed now in the latest b3 Build? I saw something about a core update to 5.2.0?

Aircoookie commented 1 year ago

For the record, most my devices are connected to a FritzBox 6490 cable with firmware 7.51-106637 BETA and I do not experience any sort of connectivity or reset issue. I don't recall exactly, but I think it ran 7.50 before, also without issue. Something is definitely fishy here, as the issue seems quite isolated. Perhaps it only affects certain models, like the 7xxx generation, or even certain settings. I even have enabled mesh and same SSID for both 2.4 and 5 GHz and it all works just as it should.

codmpm commented 1 year ago

For the record, most my devices are connected to a FritzBox 6490 cable with firmware 7.51-106637 BETA and I do not experience any sort of connectivity or reset issue.

Dear @Aircoookie, thanks for your reply on this. All customers of mine only report the problem with 7.50 (non-beta) when also using Fritz Mesh Repeaters. I'm currently not a aware of anyone having the issues when not using a repeater.

softhack007 commented 1 year ago

is this fixed now in the latest b3 Build? I saw something about a core update to 5.2.0?

Actually no news. The core update is only for -S3/-S2/-C3, while esp32 still use the same platform as before.

Actually we have an experimental build environment now for platform 5.2.0 on esp32: esp32dev_V4_dio80. This build env is however not recommended for anything but just for developer cross-checking. It may work or not work for you. And it may have new subtle bugs - it seems that espressif is not really good at not breaking previously working functionality.

wled-install commented 1 year ago

For information: the issue was reported by one person running SR WLED 0.13.3 with FritzBox 7590 / Firmware 7.56 / Mesh activated. No issue after downgrade to SR WLED 0.13.2

codmpm commented 10 months ago

We (@codm) are currently investigating the problem as far as we can.

Could not reproduce with WLED 0.13.3, Fritbox 6890 on Fritz!OS 7.57 and Fritz Repeater 1750E with Mesh on Fritz!OS 7.31. I have ordered a newer Fritz Repeater to test this with current firmware on the repeater side.

In the meantime customers of us had succes with the current wled-mm Version: wled-mm-0.14.0-esp32_4MB_V4_s-loxone-mqtt-20231008.bin.zip

codmpm commented 10 months ago

I've created a google sheet to gather the combinations where the error occurs. Would be great if you can add your Fritz!Box/Fritz!Repeater Model, Fritz!Os Version and WLED Version so that we can try to hunt this down:

https://docs.google.com/spreadsheets/d/15Aguj5zU1SwqqeCfna8r94lrWJanPTU4HCkCzvmHt3w/edit?usp=sharing

I still can't reproduce even with Fritz!Repeater 600 or 1200AX on FW 7.57.

fir3drag0n commented 9 months ago

We (@codm) are currently investigating the problem as far as we can.

Could not reproduce with WLED 0.13.3, Fritbox 6890 on Fritz!OS 7.57 and Fritz Repeater 1750E with Mesh on Fritz!OS 7.31. I have ordered a newer Fritz Repeater to test this with current firmware on the repeater side.

In the meantime customers of us had succes with the current wled-mm Version: wled-mm-0.14.0-esp32_4MB_V4_s-loxone-mqtt-20231008.bin.zip

Is there also a version with hue sync?

codmpm commented 9 months ago

@fir3drag0n: Check here on how to compile your own binary: https://kno.wled.ge/advanced/compiling-wled/

somebuddy87 commented 9 months ago

I am using an WT32-ETH01 ESP32 Ethernet Variant without WiFi activated. IT also reboots after 60 Seconds.

somebuddy87 commented 9 months ago

After turning off my Repeater and also turning off WiFi completely in my FritzBox my WT32-ETH01 also reboots every 60 Seconds. So If using ESP32 with Ethernet the Problem ist not related to Fritz WiFi. My WT32-ETH01 only stops rebooting If i Turn Off my Fritzbox completely.

wled-faq commented 9 months ago

After turning off my Repeater and also turning off WiFi completely in my FritzBox my WT32-ETH01 also reboots every 60 Seconds. So If using ESP32 with Ethernet the Problem ist not related to Fritz WiFi. My WT32-ETH01 only stops rebooting If i Turn Off my Fritzbox completely.

What Fritzbox and FritzOS Version do you have?

PatricckW commented 9 months ago

I have no Problems with the OS 7.57 and WLED 0.14.0 b27.31. It runs since 18 Days now

------ Originalnachricht ------ Von "wled-faq" @.> An "Aircoookie/WLED" @.> Cc "PatricckW" @.>; "Mention" @.> Datum 11.11.2023 18:31:47 Betreff Re: [Aircoookie/WLED] Reboot with the new OS7.50 from the Fritzbox 7590 (Issue #2932)

After turning off my Repeater and also turning off WiFi completely in my FritzBox my WT32-ETH01 also reboots every 60 Seconds. So If using ESP32 with Ethernet the Problem ist not related to Fritz WiFi. My WT32-ETH01 only stops rebooting If i Turn Off my Fritzbox completely.

What Fritzbox and FritzOS Version do you have?

— Reply to this email directly, view it on GitHub https://github.com/Aircoookie/WLED/issues/2932#issuecomment-1806872398, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2Q7PMV6MJ33BRD5W2ZTPATYD6ZAHAVCNFSM6AAAAAASYE5QSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBWHA3TEMZZHA. You are receiving this because you were mentioned.Message ID: @.***>

somebuddy87 commented 9 months ago

After turning off my Repeater and also turning off WiFi completely in my FritzBox my WT32-ETH01 also reboots every 60 Seconds. So If using ESP32 with Ethernet the Problem ist not related to Fritz WiFi. My WT32-ETH01 only stops rebooting If i Turn Off my Fritzbox completely.

What Fritzbox and FritzOS Version do you have?

FRITZ!Box 7530 V7.57

wled-faq commented 9 months ago

FRITZ!Box 7530 V7.57

7530 AX or original 7530 (not AX)?

somebuddy87 commented 9 months ago

Original 7530 without AX i guess

PatricckW commented 9 months ago

without AX on WPA2

------ Originalnachricht ------ Von "wled-faq" @.> An "Aircoookie/WLED" @.> Cc "PatricckW" @.>; "Mention" @.> Datum 12.11.2023 13:38:23 Betreff Re: [Aircoookie/WLED] Reboot with the new OS7.50 from the Fritzbox 7590 (Issue #2932)

FRITZ!Box 7530 V7.57

7530 AX or original 7530 (not AX)?

— Reply to this email directly, view it on GitHub https://github.com/Aircoookie/WLED/issues/2932#issuecomment-1807114872, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2Q7PMSBNFSKJK56HHMG45LYEC7L7AVCNFSM6AAAAAASYE5QSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGEYTIOBXGI. You are receiving this because you were mentioned.Message ID: @.***>

DeepflashX commented 9 months ago

Try disabling mdns (leave the field empty) in WLED.

somebuddy87 commented 9 months ago

Try disabling mdns (leave the field empty) in WLED.

My WT32-ETH01 also reboots with blank mdns field.

codmpm commented 9 months ago

@wled-faq have a look at the google-sheet here: https://github.com/Aircoookie/WLED/issues/2932#issuecomment-1757505404 I'm trying to gather information with which combinations the problem exist.

wled-faq commented 9 months ago

Can't reproduce on Fritzbox 7590 (not AX, FW v7.57) and 1200AX Repeater (FW v7.31). 7590 is however connected via WAN to the internet, not via DSL (dont know if it makes a difference).

codmpm commented 9 months ago

The repeater has to be on >7.50 also. But I still can not reproduce, see google sheet.

somebuddy87 commented 9 months ago

I'm quite shure that it's Not only related to WLAN because my WT32-ETH01 connected via Ethernet still rebooting with WLAN completely turned off. Untill i turn the fritzBox off

wled-faq commented 9 months ago

@codmpm No issues even after repeater was updated to 7.57.

@somebuddy87 Do you have something special in the network, maybe some static IP addresses? Some special settings in FritzBox?

somebuddy87 commented 9 months ago

Only a few static adddresses.. nothing Special. With FritzBox turned off.. No reboot at my WLED Controllers.

codmpm commented 9 months ago

@wled-faq same here. Not able to reproduce with different FB's and Repeaters.

Like @somebuddy87 said, should have nothing to do with Wi-Fi, albeit the problems reported to me all occured when a mesh repeater was present and FB was on >7.50. I have to sightings without any AVM Wi-Fi hardware involved (UniFi/TP-Link) - but the FB is used as an internet router there. Same goes for @somebuddy87 as he has Wi-Fi turned of an also has the problem.

Currently have no idea on how to reproduce.

wled-faq commented 9 months ago

@somebuddy87 Has WLED static or dynamic IP?

somebuddy87 commented 9 months ago

@somebuddy87 Has WLED static or dynamic IP?

Tested both.. for Testing without FritzBox i configured a static IP.

codmpm commented 8 months ago

I've just compiled a new version of wled-mm with the current release including loxone and mqtt.

wled-mm-0.14.0-b2732-esp32_4MB_V4_S-loxone-mqtt-20231127.bin.zip

@somebuddy87 Did you try the MM-Version for the Ethernet yet?

Technostyler commented 8 months ago

Hanging me on this Issue because I have the same as problem as @PatricckW

Waiting for the new version of @codmpm with integrated Loxone support.

PatricckW commented 8 months ago

No problem with the reboot now. Fritzbox7590 with wpa2 and mesh Repeater. Not sure what happened with wpa3, but I know our HP printer can't connect to the box in wpa2/wpa3 mode. Von meinem Telefon gesendet-------- Ursprüngliche Nachricht --------Von: Technostyler @.>Datum: So., 26. Nov. 2023, 17:23An: Aircoookie/WLED @.>Cc: PatricckW @.>, Mention @.>Betreff: Re: [Aircoookie/WLED] Reboot with the new OS7.50 from the Fritzbox 7590 (Issue #2932) Hanging me on this Issue because I have the same as problem as @codmpm. Fritzbox 7590, SW 7.57WLED 0.13.3 (problem still with 0.14.0)ESP32Homenetwork with Ruckus AP. So the FB WLAN is not used.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

somebuddy87 commented 8 months ago

I've just compiled a new version of wled-mm with the current release including loxone and mqtt.

wled-mm-0.14.0-b2731-esp32_4MB_V4_S-loxone-mqtt-20231123.bin.zip (Sorry, without loxone/mqtt - will fix shortly)

@somebuddy87 Did you try the MM-Version for the Ethernet yet?

Can you please add the usermod for ds18b20 sensors? I will try as soon as possible.

codmpm commented 8 months ago

Reupploaded new Version with Loxone and MQTT: https://github.com/Aircoookie/WLED/issues/2932#issuecomment-1824625803

@somebuddy87 Get in touch with me to check what you need.

fir3drag0n commented 8 months ago

Where I can find the Ethernet version? I do have the same problem as @somebuddy87 described.

LtMost commented 8 months ago

Hey @fir3drag0n, i just compiled an Ethernet version, i tried it out on a Controller i had around and it worked on mine. here's the File: wled-mm-eth-0.14.0-b27.32-esp32_4MB_V4_S-loxone-mqtt-20231204.bin.zip

hope it helps

chiefjoejj commented 8 months ago

@LtMost You made my day! 😍😍😍

I was struggeling the last few months now and could not use any of my wled-installations after the shitty automatic Fritzbox-update - until I uploaded your image today. Working again. 🚀🚀🚀

But I have some questions now...

White leves work great. But RGB commands dont. Did you change any settings for your Loxone-integration? How do I need to adjust my "out-of-the-box" commands I used so far? I use Loxone as well...

And I have the feeling that the ETH01 doesnt use the wired ethernet connection and instead stays on wifi after the rj45-connection is plugged in. 🤷‍♂️

Update: Ok, I see that the ETH01 gets an additional ip-address for the wired connection via DHCP... Not what I prefer but I dont want to complain. So happy my devices finally stopped booting every minute... 🙈

Hope you can help with that. 😘

Best regard Jörg from meintechblog.de

codmpm commented 8 months ago

Hey Jörg,

@LtMost is our aprentice here @codm. Have a look what MoonModules are: https://mm.kno.wled.ge/moonmodules/what-is-moonmodules/ - these are highly experimental, especially the V4. @Aircoookie is aware of the arising problems for avm users.

We've just compiled the binary for @somebuddy87 with enabled loxone integration. As far as I know there were no changes regarding MM here and all the customers using the Wi-Fi version did not complain.

@somebuddy87 do I remeber correctly that you also use loxone? The Ethernet part is working without any problem in our test here.

Cheers, Patrik

Gargamel8 commented 7 months ago

Ich hatte auch das Problem das der Stripe immer aus ging. Nachdem ich jetzt im Wifi Setup eine feste IP und das Gateway eingetragen habe funktioniert es nun.

codmpm commented 7 months ago

Thats great news! Can someone confirm @Gargamel8's findings with WLED-AC? I still can't reproduce in my side.

edit: If the problem goes away with a satic IP it could have something to do with maintaining DHCP.

somebuddy87 commented 7 months ago

Confirmed! Version b3 and 14.1 Release version with No reboots after 60 Seconds with static IP and empty Mdns name on my WT32-ETH01.

DHCP + MDNS = reboot after 60 Seconds DHCP without MDNS = reboots Static with MDNS = reboots Static without MDNS = No reboots untill now :)

rolandpj commented 7 months ago

HI, I cannot confirm. Tried all combinations from above.. doesn't run stable with FritzOS 7.57 in the same network segment. For me it seems that is worse than before, because most of the times I cannot even reach it and than it reboots after 30seconds. In the past it rebooted after 30s - 2 Minutes.

Same HW/SW Combination on another Hotspot in a different network segment fine.

codmpm commented 7 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?

DeepflashX commented 7 months ago

HI, I cannot confirm. Tried all combinations from above.. doesn't run stable with FritzOS 7.57 in the same network segment. For me it seems that is worse than before, because most of the times I cannot even reach it and than it reboots after 30seconds. In the past it rebooted after 30s - 2 Minutes.

Same HW/SW Combination on another Hotspot in a different network segment fine.

for me as well not confirmed with FritzOS 7.70 and 0.14.1 WLED.

softhack007 commented 7 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.

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.

codmpm commented 7 months ago

Confirmed! Version b3 and 14.1 Release version with No reboots after 60 Seconds with static IP and empty Mdns name on my WT32-ETH01. I cannot confirm. Tried all combinations from above..

So it seems that a "fixed IP" only helps with LAN installations of WLED and does not fix the Wi-Fi problem.

As I still can not reproduce the problem I can not countercheck Wi-Fi and LAN 😔