OTA upgrade to 6.1.0 fails with blinking green light on Sonoff Basic #3177
Comments
|
Held the button down for 40 seconds to completely reset Tasmota, Rebooted and now I am not able to see a wifi network at all to connect to. I pressed the button 4 times to start up wifi_manager. Light starts to blink. No wifi network I can connect to. Pressee button 3 times to put it in Smart Config. Used ESP8266 Smart Config. Keeps failing. Not sure how to bring this thing back to life without taking it apart and using a USB to serial adapter. |
|
Every update is a nightmare :D So, now both Basics are "running" 6.1.0, but both are in that loop you're mentioning. They neither connected to the existing wifi, nor they are reachable after a reset... |
|
Miration Path correct? You have to care for that! |
|
Was coming from 5.14., so I don't think the migration path is the issue, or am I wrong? |
|
I was on 5.14. My 5,13 to 5.14 upgrade caused the same issue and I need to flash over serial. |
|
Well, when 40 seconds button pressing reset doesnt help, there is just one way left |
|
I also had issues with one of my 20 devices. The one with the problem was based on core 2.4.1. May be that could make a difference !? |
|
@chriskmn I never had a version with v.2.4.0 or 2.4.1 i tried, that was reliable. I always got minor or major problems with every version (starting from Tasmota v.5.0.x). For me only (is and was) V.2.3.0 is rock solid!! |
|
So, if 2.4.x is problematic, why is the precompiled binary not based in 2.3.0 :( It would help unexperienced users, like me, very much. |
|
Thanks Jason, I‘ll stay with 2.3.0 also now. |
|
@maciboy the precompiled version 6.x are based on core 2.3.0 |
|
@maciboy: Until now I never had issues with the basics. My problem occured on a 4ch pro. May be there are other factors on the basic. Are they switched on while you are updating ? I know that the ESP8266 are very sensitive on supply power. A microwave could make trouble or even a bad AC adaptor somewhere on the powerline..... |
|
Used ESPtool to erase flash. Flashed the pre-compiled binary from the Github. Came up on it's own network. I connected and configured for my wifi. Rebooted the device. It did NOT connect to my wifi, but instead came up on it's own network under the new hostname I gave it. Connected. Reconfigured Wifi, even though it looked right. Device restarted and did not connect to my wifi and now will not go into Wifi Manager mode. Now it's just blinking for about a minute, then goes solid, then the device seems to reboot and start blinking again. |
|
@apastuszak @Jason2866 Then it seems that neither the core version, nor the migration path is the issue... |
|
@maciboy I'll putting 5.14 back on it and just leaving it alone for now. Can I ask what kind of router you're using and what kind of firmware is on it? |
|
That‘s how it looked on my router. Because of this, I resetted both using the 40s button press. Once I was able to connect to the established wifi, entered the credentials, but it did not help. My router is a FritzBox 7490, firmware is 6.93 |
|
@maciboy Does your router do both 2.4 Ghz and 5 Ghz and are both of these networks named the same? |
|
Yes, 2.4 and 5 GHz have the same name |
|
That's the same configuration I have. I wonder if that may be the issue here. Just strange that 6.1.0 minimal works without any issues. |
|
just disable 5ghz and test it, but yep, 5ghz can make problems if both have the same name. |
|
Esp is a 2.4Ghz only device. I use 2.4 Ghz and 5 Ghz at the same time on my Accesspoints (Lancom and Bintec-elmeg). No problem. SSID is the same for all just different channels |
|
Just reverted to 5.14.0 using ESPtool and all my problems are now gone. Wifi works great. |
|
@reloxx13 If I do that, I will have two teenage boys scream at me that their Xboxes suddenly stopped working. |
|
Did you try this: In the user_config.h, find the option CFG_Holder and change from #define CFG_HOLDER 4617 to #define CFG_HOLDER 4618. Result: it works flawlessly as it should. connects instant to the wifi, no more problems. ??? 5.14.0 has another format of that constant. So may be that somehow messes up the config 5.14.0: #define CFG_HOLDER 0x20161209 |
|
What does that setting do? Why isn't it the default in the pre-compiled
binary?
…On Tue, Jul 10, 2018 at 2:17 PM Chris ***@***.***> wrote:
Did you try this:
In the user_config.h, find the option CFG_Holder and change from #define
CFG_HOLDER 4617 to #define CFG_HOLDER 4618. Result: it works flawlessly as
it should. connects instant to the wifi, no more problems.
???
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3177 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADPlXpdoaUjnz5TqHoqK20EP2SyRv5H-ks5uFO_TgaJpZM4VJUOc>
.
|
|
@chriskmn |
|
But shouldn‘t the 40sec reset do the same and set back all values to default? |
|
@maciboy yes holding button for 40 sec. should reset device to defaults (user_config.h) |
|
@Jason2866: yes, that‘s how I understood it as well. So if you flash a new FW without changing cfg holder, that FW uses the stored config from device. If it is changed (like from 5.14.0 to 6.1.0) FW uses NOT the config from the device ?! |
|
@chriskmn |
|
@apastuszak thanks for providing 6.1.0 with Arduino Core 2.4.1 - sonoff-minimal.bin and sonoff-DE.bin |
|
@TasmotaFan Edit: So, I tried the following firmwares: Only 5.13.1 works, all others do not connect to my wifi |
|
Hi! Sonoff Basic OTA update and flash over serial. from 5.14 to 6.11 fails with blinking green light. |
|
@maciboy |
|
WPS problems will be solved in future. Not included anymore in future precompiled builds 😉 |
|
Same problem here (#3056). This has been going on for a while now, and seems to affect many users with Sonoff Basic modules. I'd love to get to the bottom of this. |
|
I'm really new with sonoff. Flashed my devices with 5.9.1. All other versions above caused the "wifi-problem". Meanwhile I've tested all versions above (clean flash). The devices can't connect to my wifi. |
|
Please, see #3224 If your issue is not solved, please reopen it. Thanks |
|
So, what is the fix? |
|
The issue for me is not solved, I just circumvented it by going back to v5.13.1 😞 |
|
how do you downgrade via wifi? or are you all taking the units down and flashing them via Serial? |
|
If you have a blinking light, then that's the only way to go.
I think they're saying the 6.1.1c release fixes the wifi issue, with the
removal of the ESP8266 Smart Config code.
…On Mon, Jul 23, 2018 at 9:42 AM knowsnotmuch ***@***.***> wrote:
how do you downgrade via wifi? or are you all taking the units down and
flashing them via Serial?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3177 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADPlXjPsYemv4urkGoglA_IyxPOznlWxks5uJdLGgaJpZM4VJUOc>
.
|
|
@knowsnotmuch do you refer to my post? Yes, unfortunately I need to do it via serial, no chance to do it via wifi |
|
@maciboy - yes - was referring to that - thanks for clarifying. Have a couple attached to the ceiling fan - too much hassle getting them down :D Thanks both of you @maciboy and @apastuszak |
|
I am having the same problem, where LED is flashing green. If I quickly press 4 times, I see a new WIFI network but when connecting to it I don't get any IP and hence can't connect to it. Any tips on how to fix this also how do you download older Tasmoto versions? I flashed Sonoff bassic straight to v6.3.0 |
|
Once you connect to it, from the device connected to the device AP, Are you able to open a browser and open http://192.168.4.1? If so, that should allow you to configure the Wi-Fi parameters. Once you restart the switch, it should join your Wi-Fi network and you should be able to connect to it via its Wi-Fi IP address. |
|
device doesn't connect to AP and I can't connect to it after pressing 4x reset. It always flashing green. When I press once it doesn't even trigger the relay. |
|
After flashing to an older version, it seems to be working now. |
|
If your first device is still operational after flashing using 5V, you are fortunate indeed! That should have released the magic smoke inside your switch ;-) Having said that, if you notice any strange behavior with the switch, it may be remnants of having connected it to 5V. But that aside,... What Sonoff device are you referring to? What version of TASMOTA did you try to flash? If it was the latest master release (6.3.0), then yes, that has some known connectivity issues. Try using the latest development version. I find the development branch to be pretty stable. If you decide to upgrade and still encounter issues, please go to the web (or serial) Console and type As you have upgraded and reverted firmware versions, you are keenly aware of the nice thing once you have TASMOTA on the device. That is, if one encounters problems with the firmware version, most times one can just flash another version using OTA. I have found that using ESPEasy to upload the firmware is the easiest method. Also, if I'm flashing using the serial interface (i.e., wired), I use Termite to send the initial configuration commands (at least the Wi-Fi config). Dr. Zzs tutorial describes this in detail. It has some of the same information as the video you linked, but is more current and a bit more "compact". Regards. Mike |
|
Mike, B.regards |
|
Rafik, You may want to give the TASMOTA Discord chat a try. Lots of HA enthusiasts that can discuss your scenario interactively and recommend an appropriate device for your surveillance camera use case. You can also give the Sonoff Users Google Groups a go. As for your Sonoff Basic, I would recommend using the latest development version. I began using TASMOTA with version 6.0.x and have just recently upgraded to 6.3.0.16. The web interface operates (i.e., toggle) completely reliably on all my devices. You can easily update the firmware over the air without having to connect to the serial interface. Mike |
|
Mike, Is the same .bin file used to flash any Sonoff device? |
|
Rafik (@rwassily), Glad to hear that you got your devices flashed and working! Can you "reach" the device with the flashing LED? A blinking LED is usually an indication that it has not connected to the Wi-Fi network. A device that successfully connects to Wi-Fi will typically have an LED that is on or off (you can set the behavior with the LEDState command). If you can connect to this device, you should go to the Console to see what messages are being logged. If you can reach the web GUI, go to the Console and enter 'WebLog 4'. If you can only connect to it through the serial interface (that's probably a clue as to a problem), enter 'SerialLog 4'. The messages in the log may give you a clue as to why the device's LED is always blinking. Be sure to set it back to log level 2 after you're done to avoid extra logging workload on the device. "Is the same .bin file used to flash any Sonoff device?" Short answer - yes. But there's a qualifier to my answer. Each precompiled binary has different options set. You can see the differences in each in the "Available Features and Sensors" section of the releases page. For your Sonoff Basic, you should use this development version binary. For most other ESP based devices that TASMOTA supports, you can choose any of the pre-compile binaries "flavors" that best suits the options you need. Once you flash the firmware onto the device, you go to the configuration and select the specific type of device you actually have (it defaults to Sonoff Basic). Once you set the right Module type, different configuration options will be made available based on the Module type. Mike |
|
Mike, I meant 6.3.0.17 :) I checked the logs and seems that it was trying to reach an MQTT server, once I set the parameters, the LED went off. Now to check the advantages of connecting to MQTT and how to access these devices outside my LAN :) B.regards |
|
TASMOTA change log - That will tell you just how much progress is always happening w/ TASMOTA. Careful how you set up external access to your devices. Opening up your LAN to the world is risky. If not done properly it could expose your entire home network to malicious access. All of my MQTT traffic is local to my LAN. I like this setup because it limits my exposure. Also, if my connection to the Internet is down, I can still control everything locally on my LAN. I have a home automation hub (openHAB) where I set up my automations that interface with all of my home's smart devices. openHAB provides a mobile app which can access my hub over the LAN or through a secure cloud connector. This cloud service provides remote access to my automation items. It also integrates with Google Assistant and Alexa to add voice control. There are several home automation hub solutions. If I were choosing today, I'd look at both openHAB and Home Assistant. There are many others. They all have their pros and cons. Your skills may be better suited for one HA hub solution versus another. Mike |
|
Mike, Rafik |
Just did an OTA upgrade 6.1.0. Flashing Sonoff-minimal.bin worked just fine. But when I upgraded to Sonoff.bin after that, I am getting a flashing green light. When I go into my wifi settings, I see that WIFI_MANAGER has kicked in and the Sonoff has it's own network up and running, but I am unable to connect to this network. and reconfigure the device.
The text was updated successfully, but these errors were encountered: