-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Wifi issues after upgrade to 6.4.0 #4697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I see the same issue with my sonoff basic. Wemos and Sonoff S26 are working fine. Strange. Edit: I'm using OTA firmware. |
Yep...mine are Sonoff T1 1CH and Sonoff T1 2CH...the S20 I have didn't saw the issue as well but they are not used much ... |
Same for Sonoff TH10, TH16 and POW2.. |
I am also having the issue on multiple devices after upgrading to 6.4.0... Sonoff Basic, S31, iFan02, T1 US 3ch & 1ch, and Wemos Mini all went into reconnect loops as shown in the OP's screenshot. After downgrading to 6.3.0 the problem disappeared in all cases. Happy to help in any way I can... just let me know what info is needed. |
There are alternatives also - 6.4.0 was released using core 2.4.2 but the 2.3.0 core binaries (which was used for previous releases) are available from http://thehackbox.org/tasmota/release/020300/ Some users have also reported success with the staged 2.5.0 core binaries which may be found at http://thehackbox.org/tasmota/020500/ - These are daily builds based on the development codebase which appears to be stable. |
All my devices with http://thehackbox.org/tasmota/020500/ Let's see how it goes... |
For me 6.4.0.1 is the same issue (with sonoff basic). Back to 6.3 |
Back to 6.3.0 as well until further news... |
Hi, This issue is duplicated to #4686 Please, try the following as explained in that issue: For anyone having wifi problems, please try:
For anyone having mqtt disconnections, please try:
For anyone having mqtt disconnections with core 2.5.0, please try in the console:
If any of the previous solutions don't work in your network please use Tasmota v6.4.0 with core 2.3.0: Thanks |
@xNuno Please, try the previous solutions. Thanks. |
"sleep 0" fixed it for me. Tested with Sonoff S20 and Basic. |
More Wifi Troubleshooting and Explanations can be found in the wiki at: https://github.com/arendst/Sonoff-Tasmota/wiki/Troubleshooting#wifi-issues-arduino-core-versions-and-expressif-sdk |
All my Sonoff devices is working properly with latest TASMOTA FW with core 2.4.2 now. I'd like to share my case study.
My Sonoff devices include: Sonoff_Basic; Sonoff Touch-US; Sonoff T-1US-2C, 3C. Sonoff Dual R2; Sonoff Bridge; Sonoff S22. I totally have 16 Sonoff devices now. |
Compiled tasmota 6.4.0.1 with core 2.5.0, sleep 50: |
After some trial and error I was able to finally update all of my devices to the official 6.4.0 (2.4.2 core) github release without uninstalling, disassembling or connecting via wire. A few of my Sonoff devices are installed in places that would have required a substantial effort to remove and/or disassemble. I tried using various firmware versions from thehackbox but the only one which didn't exhibit the issue was the version compiled against core 2.3.0 and I really wanted to continue using the official FW from the github release page. The method I used to mitigate the issue takes advantage of the fact that many things get erased when you change the CFG_HOLDER variable.
Hope this helps some folks. |
@mjoshd Good job, and thanks for documenting your process! |
I disassembly and connected with wire and flashed with esptool. Setting it up and working a while, but I noticed the wifi is very poor 8%. Another sonoff basic with 6.3 tasmota 2.3.0 core same far from my router having 78%. So later with the new firmware I can't reach this sonoff basic. 😕 |
Hello, how have you generated this overview site of your Sonoffs??? |
It's a plug-in for hassio. Maybe you can have it as standalone. |
I've just upgraded to 6.4.0.2, seem to be much better on the wifi front |
This comment has been minimized.
This comment has been minimized.
Hi, after I flashed my Sonoff T2 first time to version 6.4.0 and core 2.3.0 i could upgrade to version 6.4.0 with core 2.4.2 |
What is the goal you want to reach hiding SSID? |
@xNuno Have you managed to solve your wifi issue? |
For anyone having wifi or mqtt issues, please check the wifi troubleshooting on the wiki at: Thanks everyone for all the reports and testings. |
@ascillato2, not solved. I'm on 6.3.0 without issues. In my opinion remove 20 sw from wall and open 3 s20 plugs to flash directly is not a good solution... We should focus on solve this other way. |
@xNuno Just a thought - 6.3.0 can run a little hot - have you tried setting sleep to 50 and leave it for 10 minutes or so and then try OTA to 6.4.0? We had this problem with the previous versions of Sonoff Basic's wherein the terminal dissipation of the basic was not good and the extra heat generated by the ESP8266/ESP8285 caused some wifi problems. Just a shot in the dark because 6.3.0.10 and higher solved the thermal issues for the Sonoff Basic modules - I am not sure how the S20 deals with the heat issues we found in earlier firmware issues as I do not have an S2x to test with. |
Hi @andrethomas , I can try if you say that's not good stay with the current 6.3.0... Will give feedback later. Edit: Testing Sonoff-Tasmota 6.4.0.2 from http://thehackbox.org/tasmota/020500/ without any change to my settings (no sleep 50)! |
The S20 doesnt have a heat problem. Version 6.3.0 will run without a problem |
6.4.0.3 with 2.5 is the only version that is suitable for me in a Mesh / Multi Accesspoints environment. All others are heavily unresponsive. |
I had the same problems with 6.4.1.1 multiple issues like wifi & mqtt disconnects on several hardware ( SX20, Basic, Dual, Blitzwolf and also Shelly 1 ). Now im back to 6.3.0.10 and everything is ok. |
Yep I have same issues on multiple sonoff basics. I think if off back to 6.3.0.10 also... |
Having the same issue with SDK 2.4.2 I flashed V6.4.1 with SDK 2.3.0 and it looks OK |
2.4.2 seems a little picky on some network setups - 2.5.0 seems more forgiving... |
same for me 3/3 sonoff basics on 6.4.1 reconnections messages every 30 seconds. all 6.3.0 devices are perfect |
Bad news, looks like it's a problem with some errors in flash (like ascillato wrote). For me, after flash erase and flashing with 6.4.1_2.4.2 by serial console, sonoff basic start working OK for at least 12h... |
i was able to fix it on mine by using 2.5.0 core bin files. But that’s interesting maybe ill try the original again although you think at least one of the 3 would have flashed right |
@IxsharpxI bad flashes via serial is quite possible with some usb serial boards - we have seen this with ones which do not provide sufficient current @ 3.3V - I myself had this problem a number of times and consequently modified by CP2102 board to provide 3.3V via a LD1117-3.3 800mA regulator from the 5V line and out on the same 3.3V pin provided by the CP2012 module. The same solution may work with others also - most of the usb serial converters cannot deliver the 200mA+ spikes demanded by the ESP8266 so its possible that this may cause bad data to be written to the flash (since it is serial data) I have not tried but just adding a 47uF capacitor between the 3.3V and ground pins of the usb serial adapter may also improve results. |
I’ve tried 6.4.1.17 and only with 2.3.0 core the WiFi works. |
Same Problem here after upgrade to 6.4.1 |
IMPORTANT NOTICE
If you do not complete the template below it is likely that your issue will not be addressed. When providing information about your issue please be as extensive as possible so that it can be solved by as little as possible responses.
FAILURE TO COMPLETE THE REQUESTED INFORMATION WILL RESULT IN YOUR ISSUE BEING CLOSED
Describe the bug
A clear and concise description of what the bug is.
After the upgrade to 6.4.0 I see a lot of wifi connection drops...I have around 20 sonoff sw arround the house and they lost connection randomly... I did not see this happen with 6.3.0 so maybe something changed... they have more than 70% of signal most of the cases...
Also, make sure these boxes are checked [x] before submitting your issue - Thank you!
status 0
:To Reproduce
Steps to reproduce the behavior:
Upgrade from 6.3.0 to 6.4.0
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: