Skip to content
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

OTA uprade to 5.14.0 fails with blinkning green light #2774

Closed
3 of 6 tasks
apastuszak opened this issue May 19, 2018 · 9 comments
Closed
3 of 6 tasks

OTA uprade to 5.14.0 fails with blinkning green light #2774

apastuszak opened this issue May 19, 2018 · 9 comments

Comments

@apastuszak
Copy link

apastuszak commented May 19, 2018

Make sure these boxes are checked [x] before submitting your issue - Thank you!

(Please, remember to close the issue when the problem has been addressed)

I am unable to flash 5.14.0 on my switches using OTA. I did a switch last week and after reboot, I the flashing green light telling me I got an incomplete flash.

This afternoon I did another switch. I flashed Sonoff Minimal and after reboot, I got the flashing green light again.

To further experiment, I took another switch and downgraded it from 5.13.1 to 5.12.0 using the minimal followed by sonoff method and that worked fine. As soon as I flashed 5.14.0 minimal in order to upgrade, the switch rebooted and I am once again getting a flashing green light on the switch and no connectivity.

The first switch that failed last week I was able to upgrade using a serial to USB adapter and jumper wires, so I will do the same for the other two. But I don't want to do any more OTA attempts until I figure out what's going on.

Since I can't connect to the switch, and the flashing light followed by occasional reboots indicates a bad flash, I don't even know how to begin to troubleshoot the issue.

@reloxx13
Copy link
Contributor

Blinking green lights means your wifi config is gone and (default) the wps manager is on for a few mins and than the device restarts.

Looks like you flashed soetime ago with another CFG_HOLDER and the new default config holder is clearing your config.

@apastuszak
Copy link
Author

Well, I don't see any new wifi networks with the name Sonoff in them on my network.

I took one of my switches and flashed it using serial to USB adapter and it came up just fine in 2.4.0. Between getting it all setup, giving /dev/ttyUSB0 write permissions, and a 15 year old nagging me for lunch, the whole process took about a half hour.

I went to get switch #2 and the green light was now solid. I went to the switch URL and it was on Tasmota minimal firmware and I was able to upgrade it to Tasmota full.

But the switch was in that blinking rebooting mode for probably a good 10-15 min, and I don't know how long it was that way before I noticed it was solid.

The device is in the basement along with my router, and the two devices are about 5 feet apart from it, so I doubt it' signal strength issue.

@ajanulis
Copy link

@apastuszak , I am pretty sure that IT WAS SIGNAL STRENGHT issue - I am unable to connect to it on the same table - it's just 2 feet :) - if you compiled using last Arduino core - it causes a lot of troubles with wifi disappearing and reappearing (sometimes). Compile using 2.3.0 and everything should be OK

@apastuszak
Copy link
Author

I used the official binaries from Github, which are compiled using 2.3.0. Very odd that one worked and the other didn't. The only one I have left to upgrade is my TH10, which I am nervous to do, since it runs my aquarium heater.

@ajanulis
Copy link

@apastuszak, but you always can downgrade in case of failure

@apastuszak
Copy link
Author

apastuszak commented May 21, 2018 via email

@Jason2866
Copy link
Collaborator

There is really no need to downgrade. Just compile sonoff minimal and flash it if new firmware is to big
for direct flash.
Compile firmware with arduino v.1.5.3 (2.3.0). This is the one and only version that works always...
Just follow this, and you will get a reliable setup with 5.14.x

@ascillato2
Copy link
Collaborator

Hi

Have you managed to solve your issue?

@benjaminprojas
Copy link

@apastuszak are you using MQTT? If so, it is probably related to: #1955. This has nothing to do with OTA, but rather that it cannot reconnect back to your wifi network after the upgrade. Currently the last working version for me is 5.12.0m. I have not been able to get any newer version to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants