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.74k stars 3.17k forks source link

D1 Mini dropping off the network #1629

Closed psinide closed 2 years ago

psinide commented 3 years ago

The board drops off the network after sometime. The most its stayed on the network is about 5-6 hours. I've tried using the Disable WiFi sleep option, used boards from different brands & also used 3 different WS2812B LED strips. Either a reset, power cycle or even rebooting the Wifi router brings it back on the network

To Reproduce I have reproduced this with the D1 Mini connected to the same power supply as the LED strip, connected to different power supplies, connecting only the D1 Mini to power and also same combinations when connecting to a computer. It has never lasted through out the night

Have also commented in issue #424 and used @gegu 's ping usermod, but face the same issue.

WLED version

Additional context Flashed ESPhome with FastLED on the same boards and the setup is working for 3 days and counting now. Will be trying on a nodemcu board soon.

Thank you for your help!

Travisco29 commented 3 years ago

It's odd sometimes it loses an IP according to my Ubiquiti router. Could just be Ubiquiti being weird but I don't know.

On Thu, Feb 11, 2021 at 10:12 AM Urchin73 notifications@github.com wrote:

... strange. Maybe we have different kind of 'unavailability/disconnections' here ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Aircoookie/WLED/issues/1629#issuecomment-777688214, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHQIIMO64JHUPQLFFC44A3S6QM2TANCNFSM4VXXFO5A .

spinkohass commented 3 years ago

... strange. Maybe we have different kind of 'unavailability/disconnections' here ?

Likely. hah. And just to note - I don't know if these boards have their own issues as I got them and just flashed them to wled out of the box. Also, I'm new to all of this... I have 0 expereience with arduino and these types of things. I have 4 boards (3 deployed to LED strips). I was hoping to flash my last board (Which was the worst offender) to stock arduino and see how it behaves.

Urchin73 commented 3 years ago

Pretty sure the issue doesn't rely on the boards. I considering myself as a newbie as well. Started all this via Home Assistant one year ago. I did a lot of other projects with these boards and no issue on the +10 I have. Also Wled deconnection issues are not happening to D1 mini only but also to NodeMCU. Unsure it is happening to ESP32 tough. The question about ESP32 was already raised in a previous comment but didn't get any answer. It would be nice to have some feedback on ESP32 as well... just to know whether or not we have to consider it as THE board for WLED.

Legsmaniac commented 3 years ago

Also Wled deconnection issues are not happening to D1 mini only but also to NodeMCU.

I have to say, I personally cannot agree with this because I've used WLED for over a year now and use both D1 Mini and NodeMCU 8266's and I never have any WiFi disconnection issues. Sure, there are a small number of people on here complaining of WiFi issues but there are a large number of WLED users. Yet only a small number of people with WiFi problems. Which only make me wonder just what is the connection with their own WiFi network? Sorry, but I can only assume there MUST be something in their/yur setup that causes these disconnections because I and hundreds of other WLED users just don't have any problems so surely there cannot be any issue with WLED and its coding in itself, but with individual users network setups?

Just wish we could get to the bottom of this one.

Urchin73 commented 3 years ago

@Legsmaniac - I follow you ! Most of deconnections issues are related to the network setup in most of the cases for sure. Using 'deconnection' is maybe not the right word because they are still connected to the network (in my case anyway)... they just become unavailable (some of them). I use 4 D1 with WLED and 3 are running just fine. The 4th one has different settings as explained earlier and is at the same place than the other ones. It has even been replaced with another board... same unavailability issues. What I was trying to say in my previous comment: unavailabilities could happen with 8266. What about ESP32 ? What I didn't wrote: running WLED on 8266 will lead to deconnections and unavailability.

WLED is a F.A.N.T.A.S.T.I.C code. The effects are just sooo amazing (fireworks is my preferred one) ! Runnig also the sound reactive version of WLED: mindblowing ! Just like you I hope we could get to the bottom of this one ;-)

@Aircoookie - You rock ! Many thanks for your work and your time !

spinkohass commented 3 years ago

@Legsmaniac - I follow you ! Most of deconnections issues are related to the network setup in most of the cases for sure. Using 'deconnection' is maybe not the right word because they are still connected to the network (in my case anyway)... they just become unavailable (some of them). I use 4 D1 with WLED and 3 are running just fine. The 4th one has different settings as explained earlier and is at the same place than the other ones. It has even been replaced with another board... same unavailability issues. What I was trying to say in my previous comment: unavailabilities could happen with 8266. What about ESP32 ? What I didn't wrote: running WLED on 8266 will lead to deconnections and unavailability.

WLED is a F.A.N.T.A.S.T.I.C code. The effects are just sooo amazing (fireworks is my preferred one) ! Runnig also the sound reactive version of WLED: mindblowing ! Just like you I hope we could get to the bottom of this one ;-)

@Aircoookie - You rock ! Many thanks for your work and your time !

Very well said - agreed on all points.

sansillusion commented 3 years ago

To add to the topic, I run esp32 on two boards, one controls 61 ws2812b behind my tv, receiving data from hyperion (lbrelec on rpi4) and the second drives 21 leds in a custom lamp. Both get polled/controlled by Home Assistant.

I have had many "connection" issues with both board randomly at different times. Never having issues with the two at the same time either. I chased the issue through many versions.

Sometimes little things would help sometimes I couldn't getnitnto be completely stable.

Now I have 0.11.1 running on both boards without issues at all "over 3 weeks uptime now"

What I think did the trick and may point to bad/cheap eeprom is, wipe the eeprom more than once and flash using usb more than once.

I might just be going nuts but I it is now running great and I am almost afraid to update nex release lol.

sansillusion commented 3 years ago

Also I have a script in He Assistant that changes color and effect every 45 seconds and it would always accelerate the crashing/disconnecting when I had issues. Now it's the firs time that I have them running so long and even use my script a couple times for over 8 hours and no issues. It would usually bug out in less than an hour using the script before.

psinide commented 3 years ago

Thanks for these tips! I have't gotten around to working on the LED strips again, life getting in the way. I intend to find some time over the upcoming weeks and test out all the solutions mentioned here. My ESPHOME setup is working flawless. I've noticed its a bit laggy with LEDFX, but it could be because I have my instance of LEDFX running on my RasPi 3B as a HASSOS addon.

Legsmaniac commented 3 years ago

What I think did the trick and may point to bad/cheap eeprom is, wipe the eeprom more than once and flash using usb more than once.

LOL, that's crazy, right? 😆 But hey, if it works for you........ 👍 I honestly would have thought wiping and flashing once only would be enough. I cannot stress more on the importance of wiping though, even if it's a new board just in case it's been used and returned for refund by someone before you received it. I have found that residual junk in the memory can cause problems with ESP's. Another thing is to check your WiFi settings and double check them. I've seen some people leave the DNS blank or set wrongly. Preferably, the DNS should be the same as the Gateway, or use the Google DNS 8.8.8.8, at least to start with. Then if you decide to change it later and you start getting connection issues, you'll know why. I've also found that the use of certain pins for the Data line can cause connection issues, particularly the Rx pin. Another common reason for connection issues is rebooting or bootlooping cause by brownout. This is usually often caused by the board not receiving enough power so power supply issues are another thing to be aware of, especially those who end up adding more things like RPi's, Controller boards, relays, IR, PiR and so on. They all require power and if any one thing (or a combination thereof) intermittently draws more current at any time, it causes a voltage drop for the ESP and so it reboots. The reboot is very quick (unlike Windows computers! lol) as these boards boot very quickly so may go unnoticed. And that's just a few examples of things to be aware of before we even start to go into networking issues! LOL

dredvard commented 3 years ago

Another thing is to check your WiFi settings and double check them. I've seen some people leave the DNS blank or set wrongly. Preferably, the DNS should be the same as the Gateway, or use the Google DNS 8.8.8.8, at least to start with. Then if you decide to change it later and you start getting connection issues, you'll know why. I've also found that the use of certain pins for the Data line can cause connection issues, particularly the Rx pin. Another common reason for connection issues is rebooting or bootlooping cause by brownout. This is usually often caused by the board not receiving enough power so power supply issues are another thing to be aware of, especially those who end up adding more things like RPi's, Controller boards, relays, IR, PiR and so on. They all require power and if any one thing (or a combination thereof) intermittently draws more current at any time, it causes a voltage drop for the ESP and so it reboots. The reboot is very quick (unlike Windows computers! lol) as these boards boot very quickly so may go unnoticed. And that's just a few examples of things to be aware of before we even start to go into networking issues! LOL

As I'm new to WLED, I assumed this issue was more widespread with a particular version but your comments about the the relative low frequency does make it seem like there are various individual issues (assuming most people are using the more recent versions of WLED). Looking through the code, it does seem like a lot of the network commands are stock ESP functions which back to AirCookies comment does seem to make you wonder why it doesn't occur on thinks like Tasmota or ESP Home. Is there a debugging/troubleshooting command that we can deploy that can be use to troubleshoot common networking issues? (e.g. output list Reboots counts, etcs)

Legsmaniac commented 3 years ago

..... why it doesn't occur on thinks like Tasmota or ESP Home.

Fair point. I honestly cannot comment since they all work for me, regardless. So it is a strange one where people say they have no problems connecting with other software yet with WLED they have problems. The only problem I had once when I tried Tasmota was that the WiFi signal from it was so strong, it knocked out my 433Mhz remote controller used for another purpose. I had to abandon Tasmota and go with something else as the 433Mhz controller was important to us.

Just had a thought........ When you set up your WLED, do you set up your own Static IP? Have you tried leaving it for DHCP to assign an IP and if so, do you still have problems? If you haven't tried, could you test it for me please? I have an idea. Go to WiFi Settings and where it says Static IP (leave at 0.0.0.0 for DHCP): do just that, leave at 0.0.0.0

ubutnux commented 3 years ago

Make sure that your wifi is in legacy mode 2.4GHz B or G only, not N

psinide commented 3 years ago

So I tried the erase flash method using esptool.py I erased the same D1 mini which was giving me issues with WLED earlier and flashed the 11.1 binary. Its not connected to any LED strip right now, but its been up for 9 hours. Will keep the forum posted on the progress

psinide commented 3 years ago

Ok, bad news, the D1 dropped off the network after about 17 hours. I've disabled the 20/40Mhz co-existence setting on the router. Will test it further. Also, ticked the WiFi Sleep option this time

WJCFerguson commented 3 years ago

Yeah, erasing flash didn't help for me, but as soon as I built it myself with slightly later code it has been rock solid. Unclear if this was coincidence.

Earlier there was a suggestion that these cheap boards have crappy flash memory and writing it multiple times might somehow imprint it more thoroughly :). This sounds a like it could be voodoo to me, but is at least worth a shot.

I have another D1 mini that I will flash with the released image, to see if it fails and get more data...

psinide commented 3 years ago

Can you share that bin file somewhere? I'll try using it and test again.

Legsmaniac commented 3 years ago

... these cheap boards ...

Could you provide a link to the boards in question? Only I'm curious because I use D1 Minis 8266 with no problems. I thought most all Arduino boards were "cheap and Chinese".

spinkohass commented 3 years ago

... these cheap boards ...

Could you provide a link to the boards in question? Only I'm curious because I use D1 Minis 8266 with no problems. I thought most all Arduino boards were "cheap and Chinese".

I bought these, of the 3, one was dead on arrival. https://www.amazon.ca/gp/product/B07HF44GBT/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1 Then I bought these 2 https://www.amazon.ca/gp/product/B07NNWDDYV/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

Same issues across all 4 boards that I have now. I've tried 3 different releases, wifi settings, static IP, etc. It's always the same issue - the web interface drops offline, but the board stays online (IP address at router) and controllable via sync. It's a bitch when all 3 (I have 3 strips setup) drop offline. Right now, I have a board that will not come back regardless of powercycle. I have to try and reflash it I guess. I have 3 ESP32 boards showing up today... hoping for better experience, but I'm seeing people with those boards having issues too.

spinkohass commented 3 years ago

Mine are all CP2102 based - I wonder if that's where the issue is. I see there's a ch340 chip based ones too, I wonder if they are better.

WJCFerguson commented 3 years ago

I just bought cheap D1 Mini clones from Aliexpress quite a while ago. The actual ESP8266 chip is where the flash is (right?), and that's not a clone, right? They all come from Espressif (?). So that hypothesis is even more suspect now I think of it.

The fact that some people seem to have the problem chronically while others don't suggests it may be triggered by something about the router or some aspect of the wifi network. I'm using a MikroTik router.

I had repeated problems on my first and only board, within well under 24 hours always dead to http and ping, but still refreshing its DHCP lease with the router (very odd - can send/receive UDP for DHCP, but not for ping?) (Edited: strikethrough, I'm very unsure of this now, having just seen it happen with ping remaining active, just http dead) Tried erasing flash just in case; tried turning off wifi sleep; no improvement.

Then I built my own firmware derived from aa242d8 and haven't seen a problem since. I have today dug out another board (same purchase batch), flashed 11.1 and put it on my network, and I'll see if it locks up.

If you want to try a my D1 mini build, and pull a .bin from some rando on the internet ;), then I've put it here. As a bonus it adds control from an Logitech Squeezebox IR remote :).

Legsmaniac commented 3 years ago

@spinkohass I see, they defo look like Chinese boards, not so sure about "cheap" though but I'd have to convert US Dollars to GBP UK. I'm sure I've bought cheaper than that.

May I suggest you try some boards from https://www.az-delivery.uk/ ? It's not a UK site, they are based in Germany and ship from Germany, it's only UK (for me at least) so the site is in English. The prices, I think, are very good and they often do deals on their boards and other products. For example, 3X D1 Minis for just £6, which I think would be about $8.38 for you, plus postage. No idea what the postage would be for you though, think I paid only about £6 shipping last time I ordered. AZDelivery sell their stock on Amazon UK. I checked Amazon US, seems they don't sell on there, which is a shame but there's no reason you cannot buy direct?

Legsmaniac commented 3 years ago

@WJCFerguson I posted earlier that I honestly suspected router setup variations but users then ask why then does their boards work OK with other firmware codes for other projects, such as Tasmota.

Perhaps there one good way to settle this - a board swap. Someone (Lets say person A) who has no problems with their D1 Mini using WLED on their Network swap their board with someone (we'll call them person B) who is having problems with their D1 Mini on their Network. If Person A then sees problems with this board on their Network, we can assume it's the board. Likewise, if Person B has no problems with the swapped board on their Network, this could act as confirmation it's the board. And vice versa but with Network issues at play. Or not in the case of Person A. If you get my drift.

sansillusion commented 3 years ago

Also mabe a clear list of steps to take to debug networking issues, eg: using 20mhz bandwidth on router, trying without leds to dismiss power stability issues, trying a known good firmware, trying a test firmware. Etc...

spinkohass commented 3 years ago

the esp32 boards showed up today, I guess we will see... the first light in this list is an esp8266 flashed with esphome and neopixelbus. 12 hours: wledha

Travisco29 commented 3 years ago

Please keep us updated!

On Thu, Feb 18, 2021 at 7:51 PM spinkohass notifications@github.com wrote:

the esp32 boards showed up today, I guess we will see... the first light in this list is an esp8266 flashed with esphome and neopixelbus. [image: wledha] https://user-images.githubusercontent.com/77295408/108455217-aead9c80-7222-11eb-9eed-a85f103a9cda.JPG

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Aircoookie/WLED/issues/1629#issuecomment-781797172, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHQIIMPGT4N6IWJ4GK3VMLS7XN5TANCNFSM4VXXFO5A .

psinide commented 3 years ago

It dropped off again with the 20/40 co-existence disabled. Set my router to only B/G and trying now. Will test @WJCFerguson firmware on a different board tonight.

WJCFerguson commented 3 years ago

I'm now wondering if the problem is a transient issue. I set up a test board with 11.1 yesterday, and nearly declared it dead after only about 4 hours because I couldn't reach it (http), but then within 30s or so it came back on its own. Its uptime is now almost 24h.

Previously I came to my WLED and it wouldn't respond, I tried to reload once or twice, then declared failure and reset it to get it to work, so it could be that it would have come back on its own if I'd left it. This has nevertheless never happened to me with my later build based on aa242d8.

spinkohass commented 3 years ago

First 3 are esp8266, 4-6 are esp32, 7th is esp8266 (which was the worst offender) reflashed from wled to esphome and neopixelbus. I feel pretty confident about the esp32 modules. Not one drop in 24 hours, which is better than all 4 other esp8266. I will say this - it was a bitch to get the esp32 modules flashed. out of the bag, the Ap wouldn't light up with wled 11.1. I found an post from aircookie that said flash with a bootloader (using the link provided), that didn't work. I found another post by a rando with a recompiled build of 10.2, which worked - then ota update to 11.1.

24 hour history wledha-12 hours 96 hour history wledha-96 hours

Travisco29 commented 3 years ago

Can you link the post that worked? Just ordered some esp32s

On Fri, Feb 19, 2021 at 4:47 PM spinkohass notifications@github.com wrote:

First 3 are esp8266, 4-6 are esp32, 7th is esp8266 (which was the worst offender) reflashed from wled to esphome and neopixelbus. I feel pretty confident about the esp32 modules. Not one drop in 24 hours, which is better than all 4 other esp8266. I will say this - it was a bitch to get the esp32 modules flashed. out of the bag, the Ap wouldn't light up with wled 11.1. I found an post from aircookie that said flash with a bootloader (using the link provided), that didn't work. I found another post by a rando with a recompiled build of 10.2, which worked - then ota update to 11.1.

24 hour history [image: wledha-12 hours] https://user-images.githubusercontent.com/77295408/108576176-7dd87080-72d1-11eb-93b4-120f6cd8bd4b.JPG 96 hour history [image: wledha-96 hours] https://user-images.githubusercontent.com/77295408/108576180-80d36100-72d1-11eb-9e27-176b3aa70fed.JPG

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Aircoookie/WLED/issues/1629#issuecomment-782482466, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHQIIILOOH2DHXUQPQX6HLS74BBDANCNFSM4VXXFO5A .

spinkohass commented 3 years ago

Here you are: I tried the standard Bin first: https://github.com/Aircoookie/WLED/releases/download/v0.11.1/WLED_0.11.1_ESP32.bin

Then I tried the boot loader, then loading the standard bin: https://github.com/Aircoookie/WLED/releases/download/v0.11.1/WLED_0.11.1_ESP32_with_bootloader_beta.bin

That failed, so I used this bin: https://github.com/Aircoookie/WLED/files/5557077/wledEsp32_dump.zip

Found that from this thread: https://github.com/Aircoookie/WLED/issues/1212

That worked, then I just did an OTA to 11.1. I just used the dump.zip bin on the other two modules first and updated after with no issues. Those modules have been online now since I got them.

Good luck!

WJCFerguson commented 3 years ago

Another update / summary.

So, the fact that my later builds appeared to cure the issue on my first unit, but didn't on the 3rd, means it doesn't seem related to code changes between 11.1 and recent master. Why unit 1 started being reliable is mysterious. I have tweaked and changed the firmware on my unit1 frequently but it's remained rock solid on everything it's had since 11.1.

Also of note, the firmware is otherwise still running fine when it goes dark to http - it's responding to the IR remote. The issue is all in the http world.

I erased the flash on all units before flashing firmware. I'm going to try repeatedly re-flashing my unit3 to see if that voodoo actually has an effect. I'll also make sure my unit1 & unit3 have identical firmware.

psinide commented 3 years ago

I've setup a 30 sec ping to the WLED from Home Assistant and its been working great. Haven't had any drops for 2 days now. Will monitor it over the weekend and if it works, will flash the rest of my D1 minis with WLED and setup ping sensors for them as well

Travisco29 commented 3 years ago

Esp32s finally arrived from aliexpress, and the only file i could get to work on it is this one, has been https://github.com/Aircoookie/WLED/releases/download/v0.11.1/WLED_0.11.1_ESP32_APA102.bin its been up for a few hours so far with no issues.

On Wed, Mar 10, 2021 at 11:14 PM psinide @.***> wrote:

I've setup a 30 sec ping to the WLED from Home Assistant and its been working great. Haven't had any drops for 2 days now. Will monitor it over the weekend and if it works, will flash the rest of my D1 minis with WLED and setup ping sensors for them as well

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Aircoookie/WLED/issues/1629#issuecomment-796519191, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHQIIN5NMYI2QUFREWBOTDTDBUV5ANCNFSM4VXXFO5A .

Travisco29 commented 3 years ago

been up 24HR with no issues

On Wed, Mar 24, 2021 at 8:44 PM Travis Shopp @.***> wrote:

Esp32s finally arrived from aliexpress, and the only file i could get to work on it is this one, has been https://github.com/Aircoookie/WLED/releases/download/v0.11.1/WLED_0.11.1_ESP32_APA102.bin its been up for a few hours so far with no issues.

On Wed, Mar 10, 2021 at 11:14 PM psinide @.***> wrote:

I've setup a 30 sec ping to the WLED from Home Assistant and its been working great. Haven't had any drops for 2 days now. Will monitor it over the weekend and if it works, will flash the rest of my D1 minis with WLED and setup ping sensors for them as well

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Aircoookie/WLED/issues/1629#issuecomment-796519191, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHQIIN5NMYI2QUFREWBOTDTDBUV5ANCNFSM4VXXFO5A .

oxivanisher commented 3 years ago

Verry interesting thread! Happy to have found it. :D

So I suffered probably the same basic issue. I use 12 Wemos D1 minis for my lighting. Some of them are for effect lighting in collectables or illuminating shelves, some are for environment lighting. Before I found WLED some months ago, I had a project on my own with the same idea, but WLED is SO MUCH BETTER! :D

I am mentioning this because my project (the same D1 Minis and LEDs) suffered from random reboots too. I always thought, that I have bugs in my (self coded) lighting effects, but now I have the same problem with WLED. Which leads me to the conclusion that it is either a hardware problem, or the core arduino library, which we probably used the same, might be the culprit. Some of my WLEDs are powered via USB, others with a power brick. Some of them use a logic level shifter for the PWM signal, some don't. They range from 2 LEDs to 100+, on some I have the current stable version and on some I tried 13 b2 which makes no difference. All of them randomly reboot sometimes.

The reboots (something is happening and the watchdog reboots them after 30 secs) are happening WAY more if I have a "dynamic" effect running in contrary to just "on". The same was true for my own project, which is IMHO also very intresting thing, since our effect codebase had nothing in common.

All the WLEDs are controlled trough node red over MQTT, so I made a notification for when I recieve a last will message. This fires from the MQTT server, when the client did not talk to it for some seconds. This showed how often they really crash, because for some dynamic effect, you won't realize when it reboots. And I was shocked how often this really happens!

I use the Ubiquiti AP producs and ensured that there is enough WIFI performance by installing an additional AP which also made no change. Also I played with all the settings like band steering, output power, channel width and so on without any change.

Last but not least, I wrote a simple bash script which pings all of them every 30 seconds, but it does not seem to make any change either.

Did somebody else made the obervation that it happens more when using animated effects?

Legsmaniac commented 3 years ago

Did somebody else made the obervation that it happens more when using animated effects?

Not me. I use D1 Minis for my Christmas Lights all over the house inside and out as well as various other projects. Never had any WiFi issues, dropouts or reboots whatsoever.

blazoncek commented 3 years ago

I have ESP01 (on @srg74 custom shield) that has an uptime of 90+ days. Not a single WiFi issue. D1 mini (on @srg74 Wemos shield) has an uptime of 30+ days. Not a single issue.

D1 mini is official Lolin v3 board.

oxivanisher commented 3 years ago

As an update to my post above: I upgraded the two d1 Minis (8266) with the most crashes (always dynamic effects) to ESP32MiniKit Wemos (the esp32 successor, I don't own more at the moment) an they never crashed since then. So its definitely not the surrounding electronics, but either the base library or the Wemos D1 minis.

Legsmaniac commented 3 years ago

but either the base library or the Wemos D1 minis.

The Wemos D1 Minis. I use D1 Minis as I've stated above, no problems. I have come across some cheap and inferior D1 Minis that do have problems so you need some quality ones. If the 32's work for you though........

donnib commented 2 years ago

I have problems and i have given up using my lights. I use Ubiquity network and signal is strong and after reboot the wled device works but dies after a while. 😢

Legsmaniac commented 2 years ago

... the wled device works but dies after a while. 😢

Strange. Poor cheap cards?

blazoncek commented 2 years ago

Giving up is for the weak... 😉 Ubiquiti WiFi works 100% since I have 4 APs around the house. Make sure to disable mesh network since it seems to interfere with ESP WiFi implementation.

donnib commented 2 years ago

@blazoncek I have 5 APs and i have no problems with other ESP devices but this one. I have tried ESP8266 and then swapped it to a ESP32 WROOM model still dropping of the wifi network. I can see i had meshing enabled on only one AP but it was on the AP closest to the ESP, i have disabled it now and i will try again. What is still a puzzle for me is that when it drops i don't understand why the internal AP is not working so i can still connect to WLED, it's my understanding that when WLED cannot connect to the AP then it will fallback and make it's own Hotspot but i can't get in contanct with the WLED when it has dropped from Wifi, i need to power cycle.

Aircoookie commented 2 years ago

@donnib sorry for it dropping off your network, I don't know why that happens. If you want WLED to open the AP when it disconnects, change AP opens in WiFi settings from No connection after boot to Disconnected.

donnib commented 2 years ago

@Aircoookie thank you but this setting is already set, what happens if it get's a signal then the signal dissapears then i guess it won't open up the AP so i guess that's what i see. This seeting says that it will open the AP if there is no No connection after boot but if there is and it then dissapears it won't open the AP.

stale[bot] commented 2 years 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!