'(200) Beacon timeout' & '(201) No AP found' #1312
Comments
|
I just (minutes ago) added some quick fix to do a bit more active reconnects. However, if you're getting them Beacon timeout so quickly and so often, there may be some other issue here.
The ESP8266 does not have such a STAstart event. But you could add some delay in the function that actually sets the mode to There are other new insights into wifi that I should use and the wifi code has become too complex in the last few weeks. So please test the last version of the code (or wait 3 hours and you'll have the fresh 025 build) And sometimes it also helps to restart the accesspoint, since beacon timeout should not happen that often, even though there is some logic error in the current code. |
|
I will try the 025 build.. |
|
ESP_Easy_mega-20180425_normal_ESP8266_1024.bin Serial WiFi setupWifidisconnect Cold BootSerial "Reset" - Try again Using second router Set Wifi via serial & saveWifidisconnect & Wificonnect |
|
Ok, may patch may have broken things regarding the AP mode. |
|
Took another known working perfectly module with existing firmware, set as static IP |
|
Trying ESP_Easy_mega-20180425_normal_ESP8266_4096, I setup the wifi via serial, and am seeing this: 520 : WD : Uptime 0 ConnectFailures 0 FreeMem 19728 The ESP_Easy_0 AP is not visible to my laptops or phones. |
|
OK, what was the last version of ESPeasy that simply worked with wifi? There is a patch for the static IP issues, which I will use of course. and some other issues that have been bugging ESPeasy for over a month already. So please, what version did just work? |
|
The best version on my nodes is mega-20180410 |
|
Still, that recent? That's after event based wifi, right @TD-er ? Please report back here more suggestions on releases to pick for the async wifi. |
|
The web interface works very fast so surely the event based wifi. |
|
I hade the same problem all working perfectly on 04102018 after upgrade to
any version after this one I get a bootloop that I can't even downgrade to
previous versions... Need to check how to get out of bootloop on wemos D1.
As far as I understand the 0410 was the last on 2.3 core and after that all
versions use 2.4
…On Wed, Apr 25, 2018, 09:30 melwinek ***@***.***> wrote:
The web interface works very fast so surely the event based wifi.
But this version is on core 2.3.0.
Maybe it's really one problem 2.4.0 and not event based wifi?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1312 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADPy_1flYcxggS14s1bzkN96SvwMQAbFks5tsCYSgaJpZM4TiiWg>
.
|
|
If you back-stepped and tried merging 'important' fixes over the top why not |
|
@sassod You may want to hold the "flash" button during flashing. At least, that's the method I use for NodeMCU. I assume the Wemos D1 also has a reset and a flash button? |
|
I tried a multitude (about 20) of different combinations in the last weeks, all self-compiled, all on Wemos D1 Mini's (about 15 units with different sensors, relays, etc. attached). The observations I did were, that the most resent version of ESPEasy (from tonight) with core 2.3.0 and lwIP 1.4 seems to work stable. Switching to core from GIT or 2.4.0 and using lwIP 2 has issues (does not reconnect / goes directly into AP mode). Switching to lwIP 1.4 self compiled does improve the situation slightly (connects to the network but switches to AP mode 2min. later) so as far as I can tell it seems to be more related to the core version and lwIP and not the ESPEasy event based Wifi. However these are just not really sophisticated observations from a beginner... but probably it helps to narrow down the issues. Let me knwo if I can help and/or provide more information! And keep up the grat work!! Really appreciate it!! |
|
Could you also check if it is possible to connect to the setup page and continue the whole process of setup wifi access, when using core 2.3.0 ? (you probably need clean settings for that) If that's working right now, I will switch back to 2.3.0 |
TD-er
added
Category: Stabiliy
|
as I'm in the office I don't have physical access to the devices right now, but as far as I could see the last days, that worked. switchign to 2.4.0 or git will not bring up the page anymore. connecting to the setup-page of a running unit (2.3.0 ESPEasy from tonight) work also fine and shows me the actual connected IP. Clearing and flashing a unit I could try tonight thoug... PS: what I'm also seeing on my ESP Server (FHEM) is that the messages received often are incomplete when using GIT or 2.4.0 with lwIP 2.0 (Invalid content length (462 != 410)) |
|
OK, that's a big help. I will try to get a 'quick and stable' build this evening. Improvements in speed can always be done later, since I now know what is causing the delays. |
|
I'm flashing a cpuple of units just now with my Core 2.3.0 build from this morning (and ESPEasy master) and see if they run stable throughout the day... |
|
ESPeasy master.... I hope you mean "mega" branch? |
|
yes, sure, sorry... told you I'm a beginner ;) |
|
ESP_Easy_mega-20180410_normal_ESP8266_1024 (the last 2.3 core) |
|
So what is the plan ? Take mega-20180425 and change compile settings ? |
|
I'm not sure there is already a plan :) |
|
Had problems with AP, Page Title loaded.. not much else, then seemed to lock-up even via serial |
0425 compiled in platformIO with 2.3.0 CoreEven though I have tortured the device, trying to crash it, it has stayed UP (1 hour 30 min) |
|
Just for information: The others are running a build from this morning with core 2.3.0 built wirh Arduino on a Mac with a custom plugin set enabled (32 plugins). hope this helps... |
|
It helps a lot. |
|
Does the compilation in PlatformIO require any additional settings in current versions? |
|
0429 flashed over the top, perfect, first try 👍 |
|
Nothing really changed with 0501. |
|
Hello, I also had problems with build 0430 to get it to running on the SONOFF Basic. Reverted back to the one that I flashed before, but that made it not better. The WebIf was very slow and 1 out of 50 request returned nothing. After a while I managed to do a factory reset from WebIf and AP came up again. And after that I configured it again. Now it seems OK again. I can confirm with @Oxyandy that there is some issue with build 0430. |
|
@Barracuda09 |
|
PCB version 1.1
No I have not tried 0429, I used one form begin of April (do not know I
which, have to check that tonight). I did not what to try that much,
because it switches the lights from an aquarium. So I was a bit
disappointed it did not work an reverting back maid me sad that that also
failed.
But the one I have now seems to loss the connection after I reboot the AP.
So thought I should update it, but unfortunately it failed dramatically. So
it time me some time to make it working again.
|
|
PCB dated 5-5-2017 ? If so same revision as me.. |
|
@Oxyandy, OK I will try it again, thanks for the tip |
|
For my hardware (WEMOS D1), version MEGA-20180501 works as expected. |
|
@Oxyandy What Sonoff device? A basic? It must be something in these changes: |
|
Yep, is all I use, I have 40 Sonoff Basics |
|
You can even compare forks :) |
|
@Oxyandy Could you please test the latest version? I changed LWIP from 2.0 to 1.4 due to a bug in the HTTP POST (large rules got mangled when > 1520 Bytes) |
|
INIT : Booting version: (ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 1.4.0-RC2) |
|
I really don't get it... |
|
32 attempts, that's about close to 65 seconds, I guess? |
|
Helps ? |
|
Github release, |
|
That's faster reconnect, right? |
|
Faster than the self-compiled one before the release, yes & looks stable |
|
@TD-er Feedback time, I can click the webpage links (deliberately fast) jumping from page to page, |
|
We're super happy to hear that! :) Our plan is to make this the expected level of responsiveness, and only make it better from here 👍 |
|
I broke it, yay
Excuse the discombobulated timestamps |
|
So LmacRxBlk:1 is something to do with the SDK.. |
|
Good to hear quite some abuse is needed to get it to break ;) There is indeed some limit to the number of connections and as far as I know the function to keep track of the timers can be called more often. But it is a pity it is not recovering on its own. I saw some similar issue myself last night, when the template parse function could fill up all memory. That's also non-recoverable, so there are more use cases for such an auto reboot feature. |
|
Hey a 5 minute fix ? Is there a branch ? |
|
No not a fix, it was just a label to state the wifi is fixed. I guess trying to fix overflowing buffers due to abuse is a different issue ;) Can you open a new issue with the links about this buffer overflow + hang? |
|
Yep, no problem ;) |
Summarize of the problem/feature request
'(200) Beacon timeout' & '(201) No AP found'
Make using the recent firmwares useless, it happens so quickly I can never load a web page.
I happens straight away.
Tried virgin devices, Erase_Flash, nothing changes the outcome.
Tried 2 routers & even my mobile Android hotspot & restarting routers.
Always the same, always instantly a problem.
Simply setting Wifissid & Wifikey, save - problem starts, so using DHCP, not tried static etc
System configuration
Sonoff Basic units with 1M flash PCB dated 2017-5-5 TH_V1.1
ESP8266EX
I can back track this if it helps ?
Not going to back track without being asked to.
Last firmware tried mega-20180424 (ESP82xx Core 2_4_0)
The text was updated successfully, but these errors were encountered: