Replies: 25 comments 66 replies
-
|
Having written this, I wonder, if I should open an Issue? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Thanks for posting all this. The connection issue while you are in Wi-Fi Manager mode is with both of your routers (UniFi and AVM Fritz-Box) ? Are you able to see which Wi-Fi Channel are used by your routers? |
Beta Was this translation helpful? Give feedback.
-
|
Are you using the same Ssid name with both the Fritzbox and the Unify? |
Beta Was this translation helpful? Give feedback.
-
|
My experience is that it is not rare to see a couple of "Connect failed with AP timeout" when booting, but seeing the connection succeeding a bit later, I've not seen it as much of a problem. |
Beta Was this translation helpful? Give feedback.
-
|
Hello,
Strictly speaking, I have the issue when I am done with Wi-Fi Manager and when it first tries to connect to my normal network. Channels are: The SSIDs are different.
To be sure: I can only do that, after my workaround, as I have no access to the commandline before. After reset 3 it will be in Wifi-Manager Mode again, right? So then, I try to connect to Unifi and we will see, if reset 3 fixed my issue. Correct?
It did not connect later. It is also notworthy, that ESPEasy showed the same issue (not sure if the workaround also works there). Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
reset 3 doesn't reset the Tasmota configuration. SSID and Password remains. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, After that, it connected to my Unifi Network again. Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
Proabably the DHCP server had made the issue, with a left entry blocking the reconnect. |
Beta Was this translation helpful? Give feedback.
-
|
I did not restart the DHCP server though. |
Beta Was this translation helpful? Give feedback.
-
|
Anything else I can do in order to isolate the issue? |
Beta Was this translation helpful? Give feedback.
-
|
It is not a Tasmota issue at all. If you find the way/key to fix all wi-fi/network issues go will get rich😀 |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Please, can you test the following version? Is the same Tasmota.bin from the codebase but with the That is to test if the DHCP server don't like for whatever reason that Tasmota checks the connection, restarts and connects again. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, EchoNetz is tze FritzBox Network, that I used as Plan-B/Workaround. Greetings, |
Beta Was this translation helpful? Give feedback.
-
|
As the esp8266/Arduino#817 I have tried your setup that have failed when your UniFi was on channel 6. The Tasmota AP is always on channel 1. But that works fine with my routers. I couldn't make that fail. So having the AP in one channel and attempting Tasmota to connect to a Network on a different channel works as expected. Explanation why this works: https://bbs.espressif.com/viewtopic.php?f=10&t=324 What the ESP8266 does is moving the AP to channel 6 (your connection remains without problems) and then it attempts to connect to the router (This is because the chip can only manage 1 Wi-Fi Channel in both AP + STA modes). I could confirm this using WIFI ANALYZER Android App. You can see there how the Tasmota AP jumps from channel 1 to 6. So, the channel jumping is not the issue. It works fine. Let me do some more tests. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I tried now and used Tazmotizer again to flash Tasmota with Erase Flash. So, it worked like charme. I have no ideas of what the difference could be, between this one and the others. Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for all your testings. This is helping a lot as I don't have any of the routers where this issue shows up. |
Beta Was this translation helpful? Give feedback.
-
|
I need your help. Can you check which Wi-Fi modes are enabled in your Router?, meaning if your Router only accepts 11n and not 11b/g/n. If it accepts ONLY 11n that is the root of the issue. In dual mode, the ESP8266 can only use 11b and 11g. The ESP8266 can only connect to a 11n-ONLY Wi-Fi Network in STA mode (only if the AP mode is turned Off). I can't test that because all my routers let me select the modes b/g/n or b/g or b. I can't select 11n alone. The test should be: If this test ends like that, we can have a solution for this to workaround this ESP8266 hardware limitation. |
Beta Was this translation helpful? Give feedback.
-
|
I have a similar/same issue with NodeMCU v3 boards. I've tried the modified firmware above (RESTART_AFTER_INITIAL_WIFI_CONFIG set to false), no help. If I erase+flash v9.4.0 or v9.5.0, it can't connect to my wifi. If I erase+flash v9.3.1 or older, it can connect, then no erase just flash/upgrade to v9.5.0, and it works! If I erase+flash v9.5.0 again, it can't connect to my wifi again. BUT! Once, the modified v9.5.0 was able to connect. But I wasn't able to reproduce this. I've flashed several times, reseted it, power cycled it, turned off my phone's WiFi, I've spent 2 hours to reproduce this, nothing, the erase+flash never resulted in a successful WiFi connection again, even after entering the credentials multiple times. The |
Beta Was this translation helpful? Give feedback.
-
|
Which router's brand do you have? |
Beta Was this translation helpful? Give feedback.
-
|
Linksys E900 - quite old, n300 router. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Please everyone with connecting problems restart the DHCP server. I still think the issue is a old DHCP entry which is blocking the connect. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, For me, the DHCP is the same server for both WiFi APs. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, i think so. Just try if it solves your issue. |
Beta Was this translation helpful? Give feedback.
-
|
I've power cycled my Linksys E900 router. My v9.4.0 tasmota things restarted, v9.5.0 reconnected.
I modified my WiFi settings from manual channel 1 to manual channel 6.
WiFi: auto channel, 20MHz only. It was running on channel 1 again, checked with WiFi analyzer app.
WiFi: manual channel 6, 20MHz only.
WiFi: manual channel 11, 20MHz only.
Though at the last 2 tests (manual channel 6 and 11) strange behavior happened:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot for your tests. |
Beta Was this translation helpful? Give feedback.
-
|
I've rebuilt v9.5.0 with |
Beta Was this translation helpful? Give feedback.
-
|
The message This other issue could be that the SSId name is not exactly as the Wi-Fi Network name (SSIds are case sensitive). Or that your device is not having enough power to turn on its Wi-Fi Radio. |
Beta Was this translation helpful? Give feedback.
-
|
Look, I copy-paste my WiFi credentials in the past 48h on my phone into Tasmota, so these are correct! My device works with v9.3.1 or lower, so this is not a power issue! "timeout" or "cannot be reached" appears randomly in the log. I did it again. This is a log with timeout. What I've did was exactly the same as previous time: |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. All these tests are super useful. |
Beta Was this translation helpful? Give feedback.
-
|
@ascillato when was the connect mode selection introduced? Maybe setting to mode "n" generates problems? |
Beta Was this translation helpful? Give feedback.
-
|
This problem is in the SDK so other firmwares also have this issue. |
Beta Was this translation helpful? Give feedback.
-
|
As a temporary solution, I will add an extra button in the Wi-Fi initial configuration to just SAVE credentials and restart without checking them (As how Tasmota was before) so as to give a workaround to this issue until we can find another solution or workaround |
Beta Was this translation helpful? Give feedback.
-
|
Isn't "RESTART_AFTER_INITIAL_WIFI_CONFIG set to false" to turn of the dual mode??? The modified firmware also couldn't connect. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, no. The Dual mode is activated in the moment you see That key is only to maintain DUAL mode after the connection to the router is established, so, with that, you can access Tasmota from the AP and from the router at the same time (until next restart) where that mode is turned off. That was just a Test. The main issue here is that for an unknown reason, in Dual mode, some routers don't respond to the connection request from the ESP8266. That handshake is made inside the SDK that is closed source, so we don't have access to it (That is why this particular problem is happening with other firmwares too). Now we are trying to find a workaround to this issue. So far, a temporary solution could be to add an option to not use the dual mode, hence not checking the credentials and just try to connect after a restart, as Tasmota was doing in previous versions. So, if you can't connect, you can try this other option - At least until we find a better solution). I'm working on that extra button now. Stay tuned. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your detailed answer. My 2 cents as a plain user: 99% of users, like me, will not understand/know the background of this option, it can be confusing. If you need it, I'm ready to help with testing this new version. |
Beta Was this translation helpful? Give feedback.
-
|
I need your help. Please, can you check which Wi-Fi modes are enabled in your Router? Meaning if your Router only accepts 11n and not 11b/g/n. If it accepts ONLY 11n that is the root cause of the issue. In dual mode, the ESP8266 can only use 11b and 11g (a hardware limitation). The ESP8266 can only connects to a 11n-ONLY Wi-Fi Network in STA mode (only if the AP mode is turned Off). I can't test that because all my routers let me select the modes b/g/n or b/g or b. I can't select 11n alone. The test should be: If this test ends like that, we can have a solution to workaround this ESP8266 hardware limitation. Please, ensure your Tasmota device has all modes (b/g/n) turned on by going to the console ( http://192.168.4.1/cn ) and typing Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, Please, can you try the following Test firmware? Is the same Tasmota from the actual codebase but when it doesn't receive an answer from the Router, it just saves the credentials and restarts so as to try to connect with STA mode alone (as previous versions did). This firmware is just to test if the theory of an SDK issue while in AP+STA mode is affecting the handshake in some routers/hardwares. Thanks a lot for testing. |
Beta Was this translation helpful? Give feedback.
-
|
Previously erroneous Nodemcu V3: Green message "Successful WiFi connection, redirecting to device address 0.0.0.0" I enter the correct address into the url from my router, and it works. Previously OK nodemcu v2: OK I noticed:
|
Beta Was this translation helpful? Give feedback.
-
Great!!! Thanks for all the testings. |
Beta Was this translation helpful? Give feedback.
-
Ah, yes, that is because I was testing with the same hardware as yours, so I had compiled that binary with a template in user_config_override.h file: #ifdef MODULE
#undef MODULE
#endif
#define MODULE USER_MODULE
#ifdef FALLBACK_MODULE
#undef FALLBACK_MODULE
#endif
#define FALLBACK_MODULE USER_MODULE
#define USER_TEMPLATE "{\"NAME\":\"Module\",\"GPIO\":[32,0,320,0,0,0,0,0,0,0,0,224,0,0],\"FLAG\":0,\"BASE\":45}"
Yes, sometimes if the flash is not blank it initialize in a bad state. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot for all the tests you have done. Very appreciated. Those were very helpful !!!! Last version coming. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot for all the tests you have done. Very appreciated. Those were very helpful !!!! Here is a last firmware to test with the workaround/fix for this problem. If it works as expected, we can merge the PR #12566 to add this. The solution implemented here try to be as easy as possible for new users. What it does is: 1 - After you write the credentials, it test them. In the last step, if it fails, it will depend on the WIFICONFIG setting what is going to happen (just wait to Tasmota to publish its AP again or you need to push 6 times the button <-Default ). Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Hello, it works: and NodeMCU: The Messages could be a bit more self-explaining though (Connection failed.. So why should I store the credentials?). Maybe better: Thanks for the workaround! Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
Excellent !!!! Thank you very much!!! PR is merged now. |
Beta Was this translation helpful? Give feedback.
-
|
I have to thank YOU |
Beta Was this translation helpful? Give feedback.
-
|
About the message, you are totally right. I just used the available strings so as to not use more flash and RAM, but yes, we have to find something short to explain better what is going on. At this moment, when the new approach runs (turning off the AP and making the connection with STA mode alone) it is displayed in the console: |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the late response, I've got home only now... After entering credentials 2nd time and pressing Save, nothing happens. Tasmota GPIO2 LED continue to blink, Tasmota AP is live, but no response from 192.168.4.1, and certainly not connected to WiFi. I've tested this 3 times, consistent behavior. Downloaded again just to be fool proof, flash, test 2 times: same. I have started to write this response, and later it connected successfully! It means: 2nd time I entered the credentials (on the page with the red error message), pressed save, nothing, switched to the console tab, nothing, pressed save again, still nothing, I started to write the response, approx. 1 minute passed, and it tried to reconnect again 3rd time, and it was successful! Strange. During the "nothing happens" I noticed, that my DHCP entry for this device changed, the client name is empty! Very strange. But at least it means it had some communication. After it got connected, certainly the name was correct. 1 more thing:
Sometimes, maybe 1 out of 5 I get "AP cannot be reached", everything else in the log looks the same. Log, when it was successful (it is from the web console, so the end is missing I suppose): |
Beta Was this translation helpful? Give feedback.
-
|
I also had the problem of not being able to connect to a network with multiple TP-Link Deco T9 AP. Wifi connection failed "Please, check your credentials". I bought a Sonoff TH 16 from a store that sells them with Tasmota 9.5.0 already flashed. Eventually I managed to fix this thanks to the comment by @ascillato:
So that comment got me to the idea to dig up an old AVM Fritz!Box, set it to the same SSID and Password as the network created by the TP-Link APs, unplug the TP-Links APs and then connect the device. It successfully connected to the Fritz!Box! Next I unplugged the Fritz!Box and replugged the TP-Link APs and then (after a while) Tasmota also connected to the Decos without any issues. If the "dual mode" does not work properly with some APs it would be very helpful to have an option to turn it off. |
Beta Was this translation helpful? Give feedback.
-
Please, test with latest Tasmota (9.5.0.9). That is being done automatically. If the router is in 11n-Only mode, the dual mode won't work due to a hardware limitation of the chip. Now Tasmota in that case can turn off the AP mode and try to connect directly in STA mode. To trigger that you need to make 3 attempts in a row. The third attempt will be done as you asked. |
Beta Was this translation helpful? Give feedback.
-
|
Hello I have not read all posts so maybe this is already old information. I had the same issue with 9.5.0 on a Sonoff Basic. I was going through the migration path from an older version and for some reason I decided to reset the configs and got stuck at this version. Couldn't connect to my Unify network, wrong credentials error. I tried 192.168.4.1/cs? and the console is there. I just did a reset 3 and things happened like magic. The sonoff immediately connected to the network I was trying before. |
Beta Was this translation helpful? Give feedback.
-
|
This thread was about an issue, that ESP82xx in dual mode (using this dual mode was new in 9.5.x during setup on 192.168.4.1 to get it's new IP address and display it on the web client simultaneously, and then redirect it to this new address) can only use 11b and 11g, but some routers out there are 11n-ONLY (due to config, or design or bug) and Tasmota 9.5.x during setup wasn't able to use dual mode and had to fall back to single mode (plainly restart itself after config and you have to figure out from the router DHCP what it's IP is). I had some different problem, my tasmota 9.5.x failed on some of my HW (NodeMCU v3 clones) and not on others, so it was mainly ESP82xx HW related and not 100% router related, though causing the same "user experience". I think you get the same "user experience" but you are in another situation, see: https://tasmota.github.io/docs/FAQ/#weaker-wi-fi-signal-after-upgrade Eg. lately I upgraded some of my older Sonoffs from 9.1.0 to 10.0.0, and had to issue In summary I think the "Connect failed with AP timeout" at the end of 192.168.4.1 setup process due to dual mode can be caused by several issues:
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, wifi connection problems can have many reasons. Since most of the mandantory source code is closed source, it is guess work, trying around to find a solution :-( |
Beta Was this translation helpful? Give feedback.
-
|
Do we have any updates on this? The logs are always: Sometimes it connects for just a second and then disconnects. The worse part is it connects to my phone hotspot without problems 🤦🏻♂️ I have other 12 devices connected to my 2g network without issues. |
Beta Was this translation helpful? Give feedback.
-
|
I was expecting not to have a router issue, as I said if I create an empty project and write just the code to connect to the wifi, it connects immediately no matter what or how many times I reboot the board, and I never get a timeout problem. Wifi connection code: WiFi.mode(WIFI_STA);
WiFi.begin(WIFI_NAME, WIFI_PASSWORD);
unsigned long start = millis();
while (WiFi.status() != WL_CONNECTED && millis() - start < WIFI_TIMEOUT) {
delay(300);
Serial.print(".");
}
if (WiFi.status() != WL_CONNECTED) {
Serial.println("WiFi connection failed");
return;
}
Serial.println("WiFi connected");
Serial.println("IP address: ");
Serial.println(WiFi.localIP()); |
Beta Was this translation helpful? Give feedback.
-
|
"Router issue" is much more complex than just trying out with some empty project, with a lot of possible differences about software versions, fixes, config and power draw. |
Beta Was this translation helpful? Give feedback.
-
|
FYI: As I remember after initial setup through 192.168.4.1 Tasmota tries to connect to the router in dual STA + AP mode to get new IP and at the same time redirect the phone to it. But this gets complicated, as this needs more power - but some boards has "undocumented" power limits. Or some routers doesn't support the WiFi g mode the ESP firmware uses this time is STA mode instead of n mode - ESP radio limits, ESP CPU limits, and simply disappear - router firmware limits. So a simple one-liner in reality gets more and more complex as more and more workarounds build around it. |
Beta Was this translation helpful? Give feedback.
-
|
@lmagyar Please keep friendly. If you think you have a found solution which keeps all currently functions and is well tested you are invited to contribute. Tasmota is Open Source! We are looking forward to review your PR. |
Beta Was this translation helpful? Give feedback.
-
|
Oh, I didn't want to be unfriendly, I really like Tasmota and those who develop it, I wanted to be just plain neutral, I will rewrite it. :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I just recently ran into same problem, had one of four of my shutters (Sonoff Dual R3 v2) disconnected from my wifi network after half year of running without problems with log Edit: I was too quick with response. After short while it does same thing |
Beta Was this translation helpful? Give feedback.
-
|
maybe it helps someone: with me the response time in the ioBroker/Sonoff adapter was adjusted, set it back to 60 seconds and after that all problems were gone. |
Beta Was this translation helpful? Give feedback.
-
|
In my case Reset 3 command worked, still not clear what actually it does but for now it seems ok. I have a unifi AP's FYI |
Beta Was this translation helpful? Give feedback.
-
|
It doesn't work for me. 00:00:00.001 HDW: ESP8266EX |
Beta Was this translation helpful? Give feedback.
-
|
Did do the reset for other reason but the situation remained the same. Bought a TP-LINK C50 and configured it as range extender but with an different SSID. Presto , all problems gone I thought. But no. Sometimes one of my 15 SONOFF devices decided to quit WiFi and did not reconnect anymore. |
Beta Was this translation helpful? Give feedback.
-
|
FYI For the "2.4Ghz as 11n only" situation: from #12512 (reply in thread)
And for the "quit WiFi and did not reconnect anymore" issue: I use the below rule against this problem on all my devices: And I reboot the router once a week automatically also. :/ |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone!! Platform: SONOFF Basic V1 (ESP8266) Version 8, 9, 10 : No problem, the tasmota reboots and connects with no problem.
I'll have to stay in version 12.2 ;( Hope it helps!! |
Beta Was this translation helpful? Give feedback.
-
|
Another corner case when Tasmota v13.3.0 when both (!) ssid is configured, but only one is available.
Strange exprimental results:
UPDATE: v13.3.0 even with single WiFi setting is unstable, sometimes it takes a minute to connect to WiFi. |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same issue with an old Sonoff v1.1. I had to downgrade as well. Its weird because I have other devices that are working, but the 2 I have on a bench are not. |
Beta Was this translation helpful? Give feedback.
-
|
I just found this - having same issue. Happens with multiple SW stacks on the ESP 8266 (tasmota, esphome,...) -- however esp32 tends to work. Fails to join WIFI quickly (takes many retries: 30 secs to 10 mins) but usually eventually joins. Not DHCP. Rebooting router does tend to help. I suspect something in WPA hashing or something that the router is rejecting device until something times out. Probably (as mentioned above) in the ESP SDK itself. Would love someone to figure out the why.... some other threads have discussed changing "Smart Connect" and TWT settings in router (didn't help me). |
Beta Was this translation helpful? Give feedback.
-
|
I have similar case, that software up to 12_2_1 works (in terms of wifi) and above 12_3_1 (including) will not connect to network. all binaries are from "releases" - tasmota.bin What is most surprising that when I took another NodeMcu, and flashed with newest firmware - works great. from 12_3_1 some output output from version 12_2_1 (I **** names) Any idea what can be the reason? |
Beta Was this translation helpful? Give feedback.
-
|
NodeMCU-V3 340G board? This is the only board I have this type of problems (if I remember correctly). I was afraid to upgrade, but good to know, that a fresh new install has some chance to succeed. |
Beta Was this translation helpful? Give feedback.
-
|
Yes. Just cheapest nodemcu with ch340. But as I said, another board, the same in fact, works. some people suggested that it can be partially problem of router, or generally home networking, but as I said, it doesn’t want to show any results of scan. And in my home at least 4to 6 should easily be discovered… |
Beta Was this translation helpful? Give feedback.
-
Hello,
I had the issue, that I was not able to connect to my network. This is what I did:
On the serial Log, I got:
Connect failed with AP timeoutAnd the AP activated again, asking me for my credentials.
I had a very similar issue with ESP-Easy.
I used two different Boards (Witty-Board and NodeMCU)
As I had tried "everything" i.e. it could not be the Software (I had the issue with both ESPEasy and Tasmota) or the Hardware (two Boards), I assumed that it could be the Access-Point.
I should add, that I had used both boards with an older Version of Tasmota or Espeasy before (but again: I did erase the flash).
Thus, I wanted to rule out the Wifi-Network as the cause.
So I created another Wifi Network with different infrastructure (AVM Fritz-Box instead of Unifi).
Bingo. No issue at all. It connected instantaneously.
So... Next I opened the Web-Interface of Tasmot and connected to my normal network again (Unifi)
Bingo again.
So, what could be the reason?
Either the erease flash did not really work and something was left.
Or, I have the connection issue only in the Wifi-Manager/AP-Mode.
I think it is the second option. I flashed the same Tasmota again - also with erase flash. Same procedure as above. Same outcome.
I just wanted to document this, hoping it is of help for anyone.
Best regards,
Hendrik
I am using the latest release: 9.5.0
Beta Was this translation helpful? Give feedback.
All reactions